Skip to Content
Last modified by Pascal Robert on 2015/05/04 04:24
From version 28.1
edited by Ramsey Gurley
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 56.1
edited by David Holt
on 2011/06/10 19:20
Change comment: Moved latest addition to the "properties" section

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ramsey
1 +XWiki.dholt
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  
... ... @@ -103,8 +103,13 @@
103 103  
104 104  {{/noformat}}
105 105  
106 -The other changes are then in the er.extensions.ERXLocalizer.availableLanguages and ERXLanguages:
106 +{{color value="#333333"}}
107 +The other changes are then in the er.extensions.ERXLocalizer.availableLanguages and ERXLanguages:
108 +{{/color}}
109 +
110 +{{color value="#333333"}}
107 107  In the above case after adding canadian french these would change in:
112 +{{/color}}
108 108  
109 109  {{noformat}}
110 110  
... ... @@ -112,6 +112,16 @@
112 112  
113 113  {{/noformat}}
114 114  
120 +{{color value="#333333"}}
121 +Localized formatters use this property:
122 +{{/color}}
123 +
124 +{{noformat}}
125 +
126 +er.extensions.ERXLocalizer.useLocalizedFormatters=false
127 +
128 +{{/noformat}}
129 +
115 115  ===== Localized strings and components =====
116 116  
117 117  For each language available, you will need a corresponding Localizable.strings file. This file should be located in Projects->Resources->"Lang".lproj directory. In these directories, you'll store localized resources such as Localizable.strings files and localized components. So, continuing with the above example, you should create two new Localizable.strings files in the following places in your project directory:
... ... @@ -165,7 +165,7 @@
165 165  
166 166  {{code}}
167 167  
168 - @Override
183 +@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,7 @@
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]].
210 +
211 +=== ===
212 +
213 +