Re: Localization problem, hello world too
Re: Localization problem, hello world too
- Subject: Re: Localization problem, hello world too
- From: Guido Neitzer <email@hidden>
- Date: Mon, 1 Dec 2008 09:51:44 -0700
Hi Phil,
did you check that you get the localized components in the correct
spots in the built application? Not that one localization overrides
the other or so?!
cug
On 01.12.2008, at 07:33, phil wrote:
Hi,
To Ramsey:
Yes I'm sure I'm using session, cause I'm NSLogging from my
Session.java, extension of ERXSession...
I tried to create a new Application, following the Hello World
tutorial.
As long as my only localizations are Strings in Localizable.strings,
this works, browser preferencies allow me to choose english or german.
But when I include localized components into the mix, localization
stop working immediately and use only one language (German even if
English is the default)
So this makes me think that either I'm missing something or
something is broken...
Does anybody use localized components successfully? Is this totally
unsupported?
In our legacy apps, the former developper made heavy use of
localized components :-(
PHiLippe
Ramsey Lee Gurley a écrit :
Are you sure you have a session? If you don't have one, the app
will go with the server's default language no matter what you set
in the browser.
http://wiki.objectstyle.org/confluence/display/WO/Web+Applications-Development-Localization+and+Internationalization
Try the method near the bottom of the page there and see if that
helps.
On Nov 28, 2008, at 5:15 AM, phil wrote:
Hi
I'm in the lasts steps to port an XCode WO 5.3.3 application to
Eclipse.
I also updated the wonder framework (not the latest,
wonder-5.0.0.8273)
I'm able to compile the application and run it from eclipse or
deployed. The only thing that is still a problem is
translation/localization.
This app is available in three languages: French/German/English.
We use
a mix of String/components localization with three directories:
French.lproj / German.lproj / English.lproj which contains all a
Localizable.strings and a bunch of localized components .wo files.
This worked for years. (with XCode)
Now the application only uses German. If I delete the
.woa/Content/Ressources/German.lproj it then only uses English and
if I
delete English.lproj it then uses French. So I conclude that all the
files are at the right place, with right permissions.
We both detect the language from the browser and permit users to
force
it to one of their choice.
I verified in the Session that the localizer used is the right one:
2008-11-28 10:43:55 CET] <WorkerThread0> Session language: French
[2008-11-28 10:43:55 CET] <WorkerThread0> Session localizer:
<er.extensions.localization.ERXLocalizer French>
so the choosen language seems successfully set. But the wo files
used
are alway those from the German.lproj ???
Does someone have an idea of what I'm missing?
Best regards
PHiLippe
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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