Skip to Content
Last modified by Pascal Robert on 2015/05/04 04:24
From version 33.1
edited by Johan Henselmans
on 2009/11/10 06:43
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,6 +132,8 @@
132 132  
133 133  Your layout would end up something like this:
134 134  
137 +[[image:ERXLocalizerEclipseLayout.png]]
138 +
135 135  ===== Localized EOAttributes =====
136 136  
137 137  In Wonder, it is also possible to localize attributes. There are two requisites:
... ... @@ -146,6 +146,8 @@
146 146  
147 147  Then, for the attribute you'd like to localize, add the ERXLanguages key to the UserInfo for that specific attribute:
148 148  
153 +[[image:ERXLocalizerUserInfo.png]]
154 +
149 149  ===== Direct Actions =====
150 150  
151 151  If you are defaulting to direct actions, you may not have a session. If you do not have a session, the server will return the default language specified in the Properties mentioned above. If you're using direct actions and you don't like that behavior, you can stick this in your direct action class:
... ... @@ -165,8 +165,10 @@
165 165  
166 166  {{/code}}
167 167  
168 -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.
169 169  
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 +
170 170  ===== Database setup =====
171 171  
172 172  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: