Re: Localization Help! (was Localizer Default vs. Browser)
Re: Localization Help! (was Localizer Default vs. Browser)
- Subject: Re: Localization Help! (was Localizer Default vs. Browser)
- From: Lachlan Deck <email@hidden>
- Date: Fri, 13 Jun 2008 11:53:35 +1000
On 13/06/2008, at 9:46 AM, Rams wrote:
Have you set your application encoding? I'm using UTF-8. It works
fine for Farsi. I may be wrong, but I don't think there's any
reason you need to use UTF-16, except in your Localized.strings
file... that has to be UTF-16. So in my properties file I set,
# Localization
er.extensions.ERXLocalizer.defaultLanguage=English
er
.extensions
.ERXLocalizer
.fileNamesToWatch=("Localizable.strings","ValidationTemplate.strings")
er.extensions.ERXLocalizer.availableLanguages=(English,Japanese)
er
.extensions
.ERXLocalizer.frameworkSearchPath=(app,ERDirectToWeb,ERExtensions)
And last but not least
# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF8
That should be UTF-8
And in my Application's constructor
WOMessage.setDefaultEncoding("UTF8");
If you're using Wonder then the above property does this already (or
more actually).
If using Wonder and you don't set the property you want this in your
app constructor:
if
( ERXProperties
.stringForKey( "er.extensions.ERXApplication.DefaultEncoding" ) ==
null )
setDefaultEncoding( "UTF-8" );
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden