Re: NSLocalizedString fails rarely?
Re: NSLocalizedString fails rarely?
- Subject: Re: NSLocalizedString fails rarely?
- From: p3consulting <email@hidden>
- Date: Mon, 15 Dec 2003 21:41:48 +0100
On 15 dic. 2003, at 19:02, Douglas Davidson wrote:
On Dec 13, 2003, at 4:55 PM, Daniel Jalkut wrote:
The symptom some users are seeing is that the menu items for things
like the "Quit" item are showing up as "QUIT_ITEM", etc. These
correspond to the clunky names I gave the "keys" to all my localized
strings. Basically, instead of the localized (in this case, English)
string, the user is getting the key. I think this is the fallback
behavior when NSLocalizedString fails to locate and/or load the
localized string for the key.
This is so rare that I've never witnessed it on my own machine. I've
had 3 separate users report the same behavior, and none of them seems
to be running anything super unusual. One of the users noticed the
bug coincident with upgrading to Panther, but others were seeing it
before, with Jaguar.
Typically this sort of problem occurs when there is something wrong
with their AppleLanguages preference. Many apps won't exhibit it,
because they make value = key in the development localization. Have
the user go to the localization pref pane and rearrange some of the
lower-down items; if the problem goes away, then that is what it was.
Beyond that, there might be something corrupted in the install of your
app, perhaps something non-obvious like a corrupted .strings file.
maybe the "corruption" is just forgetting to save it in UTF-8 format...
Pascal Pochet
P3 Consulting
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.