Re: Adding more localized *.strings
Re: Adding more localized *.strings
- Subject: Re: Adding more localized *.strings
- From: James Blair <email@hidden>
- Date: Tue, 1 May 2007 10:11:54 -0500
Laurence Harris <email@hidden> wrote on
04/30/2007 09:13:57 PM:
> > To test each of these
> > localizations, I switched my preferred locale in System
> > Preferences, logged out and back in, and then ran my
> > application.
>
> You shouldn't need to log and and back in for this. I can run my
> application in any supported language just by moving that language
to
> the top of the list in International and launching my application.
I
> don't even have to close System Preferences.
Good to know. SysPrefs warns that changes won't take
effect until I logout and in, but skipping that step will save testing
time once I solve this issue.
> > The problem is the correctly localized strings
are only displayed
> > when I'm running in the originally supported
> > locales, but never in the newly supported ones. So, English and
> > French display the correct localizations, but
> > Italian does not (it falls back on English). The question is,
why?
>
> I'm a little confused. Does the copy of your application that you're
> running contain the Italian resources everywhere they're supposed
to
> be? If so it doesn't sound like an Xcode issue. If not, then there's
> no point in trying to run in the missing languages.
Sorry for the confusion. To be clear, I'm not
building an application, I'm just building a framework that can be used
by many applications. The localized bundle Contents do contain all
of the localized directories, as well as the correctly localized *.strings
files. If this isn't an XCode issue, what should I explore next as
the possible problem?
Thanks,
James _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden