Skip to Content
Last modified by Pascal Robert on 2015/05/04 04:24
From version 32.1
edited by Ramsey Gurley
on 2008/11/28 11:37
Change comment: My advice was a little excessive there I think...
To version 33.1
edited by Johan Henselmans
on 2009/11/10 06:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ramsey
1 +XWiki.johanhenselmans
Content
... ... @@ -93,6 +93,23 @@
93 93  
94 94  {{/noformat}}
95 95  
96 +Note that if you need to customize the locale for a language, such as Canadian French, you can do so with this property:
97 +
98 +{{noformat}}
99 +
100 +er.extensions.ERXLocalizer.French_CA.locale = fr_ca
101 +
102 +{{/noformat}}
103 +
104 +The other changes are then in the er.extensions.ERXLocalizer.availableLanguages and ERXLanguages:
105 +In the above case after adding canadian french these would change in:
106 +
107 +{{noformat}}
108 +
109 +er.extensions.ERXLocalizer.availableLanguages=(English,Japanese,French_CA)
110 +
111 +{{/noformat}}
112 +
96 96  ===== Localized strings and components =====
97 97  
98 98  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:
... ... @@ -99,6 +99,7 @@
99 99  
100 100  Project->Resources->English.lproj->Localizable.strings
101 101  Project->Resources->Japanese.lproj->Localizable.strings
119 +Project->Resources->French//CA.lproj->Localizable.strings//
102 102  
103 103  As mentioned earlier, it's recommended that these be in UTF-16 format. You can do that by right clicking on the file in WOLips and selecting "Properties." In the resources panel, change from the project default encoding to UTF-16.
104 104  
... ... @@ -112,6 +112,22 @@
112 112  
113 113  and then right-click->Copy it from English.lproj and right-click->Paste it into Japanese.lproj. At this point, when you open the component in WOLips, there will be a tab at the bottom of the component editor view that allows you to switch back and forth between different localized versions of that component.
114 114  
133 +Your layout would end up something like this:
134 +
135 +===== Localized EOAttributes =====
136 +
137 +In Wonder, it is also possible to localize attributes. There are two requisites:
138 +
139 +First add ERXLanguages to your Properties file:
140 +
141 +{{noformat}}
142 +
143 +ERXLanguages = (en,jp,fr_ca)
144 +
145 +{{/noformat}}
146 +
147 +Then, for the attribute you'd like to localize, add the ERXLanguages key to the UserInfo for that specific attribute:
148 +
115 115  ===== Direct Actions =====
116 116  
117 117  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: