On Jul 30, 2007, at 12:55 PM, Alastair Houghton wrote:
As long as you just pass the -AppleLanguages option as an argument
of the main kiosk program, it will work fine and will only affect
the application you started. We do something just like that for a
language selector we wrote for use on bootable CDs.
To see the effect, go to Terminal and enter the following
If you enter it literally, you'll see that TextEdit starts with
everything in Korean, even the Apple menu.
Amazing ! Even if - for me - the localization affects only but the
Apple menu (not the Menus bar), which becomes Korean enough when
TextEdit is the active window, and immediately back to English
Apple Menu when I click another - say Terminal - window.
If you make TextEdit active, all of TextEdit's menus should be
Korean. Other apps should be unaffected.
If you aren't seeing the menus in Korean, it could be because you've
removed some of the language resources; some users do that to save
disk space, or perhaps it's just that you aren't activating the
application (I don't think it will activate automatically if you run
it like this, but that's pretty easy to work around if you find it's
happening when you code up your language selector app).
In italian, it's as complete as korean - not more ( TextEdit Menus
bar has not changed to italian ).
When I do the same with 'fr', the localization is more completely
achieved ( TextEdit Menus bar has changed to french, and some
TextEdit strings are translated ).
Is it because being french, I happened to have chosen 'french' as
the preferred language in 'International' prefs, so that "it" knows
now more about ( I keep 'English' as preferred language when
working with computers ) ? Or ... :)
AFAIK there should be no difference, since you've replaced---
outright---the user's preferred list of languages by specifying the
command line option. All the resources work the same for me.
Anyway, this is useful to me and I expect the same for others.
