Skip to Content
Last modified by Pascal Robert on 2015/05/04 04:24
From version 57.1
edited by Pascal Robert
on 2012/02/11 08:39
Change comment: There is no comment for this version
To version 52.1
edited by Johann Werner
on 2010/12/03 08:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.probert
1 +XWiki.jw
Content
... ... @@ -64,13 +64,13 @@
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://wocommunity.org/documents/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.
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.
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  
71 71  If you use localized strings in your UTF-8 application you may also check out Project Wonder's [[ERXLocalizer>>WOnder-ERXLocalizer]] class.
72 72  
73 -=== Project Localization tips ===
73 +=== Project Localization tips [[~~ramsey]] ===
74 74  
75 75  The following are some tips and suggestions for localizing a project in WOLips using Project Wonder.
76 76  
... ... @@ -103,13 +103,8 @@
103 103  
104 104  {{/noformat}}
105 105  
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"}}
106 +The other changes are then in the er.extensions.ERXLocalizer.availableLanguages and ERXLanguages:
111 111  In the above case after adding canadian french these would change in:
112 -{{/color}}
113 113  
114 114  {{noformat}}
115 115  
... ... @@ -117,16 +117,6 @@
117 117  
118 118  {{/noformat}}
119 119  
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 -
130 130  ===== Localized strings and components =====
131 131  
132 132  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:
... ... @@ -180,7 +180,7 @@
180 180  
181 181  {{code}}
182 182  
183 -@Override
168 + @Override
184 184   public WOActionResults performActionNamed(String actionName) {
185 185   if(!context().hasSession()) {
186 186   ERXLocalizer localizer =
... ... @@ -190,11 +190,12 @@
190 190   return super.performActionNamed(actionName);
191 191   }
192 192  
178 +
193 193  {{/code}}
194 194  
195 195  That should give the user their browser's default language setting instead of your server's default language setting until a session is created.
196 196  
197 -[[WO:Development-Localization and Internationalization^LocalizerTest.zip]] is an example application demonstrating the sessionless use of the localizer with localized strings and localized components, storing the language state in a cookie.
183 +[[Development-Localization and Internationalization^LocalizerTest.zip]] is an example application demonstrating the sessionless use of the localizer with localized strings and localized components, storing the language state in a cookie.
198 198  
199 199  ===== Database setup =====
200 200  
... ... @@ -207,7 +207,3 @@
207 207  ===== Localization presentation from WOWODC West 2009 =====
208 208  
209 209  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 -