Skip to Content
Last modified by Pascal Robert on 2015/05/04 04:24
From version 36.1
edited by Johan Henselmans
on 2009/11/10 06:49
Change comment: There is no comment for this version
To version 55.1
edited by Ramsey Gurley
on 2010/02/02 23:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.johanhenselmans
1 +XWiki.ramsey
Content
... ... @@ -1,5 +1,7 @@
1 1  == Unicode ==
2 2  
3 +See also: [[UTF-8 Encoding Tips]]
4 +
3 3  To Enable Unicode for your WO app, add the following to your application constructor:
4 4  
5 5  {{code}}
... ... @@ -132,7 +132,7 @@
132 132  
133 133  Your layout would end up something like this:
134 134  
135 -[[image:ERXLocalizerLayout.png]]
137 +[[image:ERXLocalizerEclipseLayout.png]]
136 136  
137 137  ===== Localized EOAttributes =====
138 138  
... ... @@ -148,7 +148,7 @@
148 148  
149 149  Then, for the attribute you'd like to localize, add the ERXLanguages key to the UserInfo for that specific attribute:
150 150  
151 -[[image:ERXLocalizedUserInfo.png]]
153 +[[image:ERXLocalizerUserInfo.png]]
152 152  
153 153  ===== Direct Actions =====
154 154  
... ... @@ -169,8 +169,10 @@
169 169  
170 170  {{/code}}
171 171  
172 -That should give the user their browser's default language setting instead of your server's default language setting until a session is created.
174 +That should give the user their browser's default language setting instead of your server's default language setting until a session is created.
173 173  
176 +[[^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.
177 +
174 174  ===== Database setup =====
175 175  
176 176  Outside of this, if you are using a database, you'll need to make sure that is encoded properly as well. I'm using MySQL, so I have in my EOModel: