I want to write a Foundation Tool that allows me to get the localized
versions of expressions used in Cocoa apps.
For instance, I might want to know what word the Finder uses for
"Archive" in the user's current language.
The respective key in the Finder's string tables is "AR40", so
basically, the code for this task is:
id bundle = [NSBundle bundleWithPath:@"/System/Library/CoreServices/
Finder.app"];
id string = [bundle localizedStringForKey:@"AR40"] value:nil table:nil];
However, in a Foundation Tool, this code *always* displays the
English variant ("Archive"), no matter what the user's preferred
language. (Of course, the Finder itself has string files in all
languages.)
If you use this code in a Cocoa app, the result is the same *unless*
you add resources for languages other than English. Then, all these
languages are considered, too, so if the user's preferred language is
among them, it will be displayed instead of "Archive".
In other words, [bundle localizedStringForKey:<string>] first and
foremost does *not* consider the languages available in bundle, but
rather those of its own process. God knows if this is a bug or a
feature. :-/
So how can I make a Foundation Tool think it has more languages
available than English? Any ideas anyone?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
