Changes for page Development-Localization and Internationalization
Last modified by Pascal Robert on 2015/05/04 04:24
From version 27.1
edited by Ramsey Gurley
on 2010/12/03 13:39
on 2010/12/03 13:39
Change comment:
I'm getting too much credit at this point I think. Removed my name from the heading :)
To version 21.1
edited by Pascal Robert
on 2011/06/10 10:51
on 2011/06/10 10:51
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.r amsey1 +XWiki.probert - Content
-
... ... @@ -64,7 +64,7 @@ 64 64 65 65 {{/code}} 66 66 67 -To make WOFileUpload components working I also had to add the launch parameter WOUseLegacyMultipartParser true to my application. This launch parameter forces the parsing of all form values, the first time WORequest.formValues is called. See the [[apple developer documentation>>http:// developer.apple.com/documentation/WebObjects/Reference/api/com/webobjects/appserver/WORequest.html]] for additional information. Without WOUseLegacyMultipartParser true I had serious problems in my applications using a WOFileUpload component because the bindings //data// and //filePath// have been emptied after a form POST.67 +To make WOFileUpload components working I also had to add the launch parameter WOUseLegacyMultipartParser true to my application. This launch parameter forces the parsing of all form values, the first time WORequest.formValues is called. See the [[apple developer documentation>>http://webobjects.mdimension.com/javadoc/WebObjects/5.4.2/com/webobjects/appserver/WORequest.html]] for additional information. Without WOUseLegacyMultipartParser true I had serious problems in my applications using a WOFileUpload component because the bindings //data// and //filePath// have been emptied after a form POST. 68 68 69 69 With Jesse's code and this extension, you will be able to handle UTF-8 character data correctly in your WO application. 70 70 ... ... @@ -165,7 +165,7 @@ 165 165 166 166 {{code}} 167 167 168 - 168 +@Override 169 169 public WOActionResults performActionNamed(String actionName) { 170 170 if(!context().hasSession()) { 171 171 ERXLocalizer localizer = ... ... @@ -175,7 +175,6 @@ 175 175 return super.performActionNamed(actionName); 176 176 } 177 177 178 - 179 179 {{/code}} 180 180 181 181 That should give the user their browser's default language setting instead of your server's default language setting until a session is created. ... ... @@ -193,3 +193,9 @@ 193 193 ===== Localization presentation from WOWODC West 2009 ===== 194 194 195 195 Guido Neitzer did a localization presentation at WOWODC West 2009 that give a good overview of how to localize your apps. The presentation is available [[here>>http://www.wocommunity.org/podcasts/wowodc/west09/WOWODCW09-Localization.mov]]. 195 + 196 +=== Localized formatters === 197 + 198 +Use this property: 199 + 200 + er.extensions.ERXLocalizer.useLocalizedFormatters=false