This indeed changed the application language off my system default
language, and worked exactly as expected with one exception - it
doesn't take effect until the application restarts.
Yes, that's correct.
I suppose some internal settings need to be flushed or something
for NSLocalizedString to update the strings file it reads from, I
don't know how or if it's possible to change that.
Not as far as I'm aware, though I haven't checked.
Alastair asked my reasons for supporting such an option. I don't
have a particular need for it in my current project - it's just a
feature that I like and want to include. Which should be enough
reason.
Well no, not really. The user expects to be able to set his or her
language setting in System Preferences, and if individual
applications need to be altered to behave differently, as Charles
Steinman pointed out, there is Finder's "Get Info" panel.
If you're going to duplicate existing system functionality like this,
you need to have a good reason for doing so. I can think of a few
reasons that you might need to mess with this (e.g. bootable CD
environments, restricted environments such as kiosks, apps for
localization courses, demos), but you really shouldn't be doing this
for an ordinary application.
In this case, either behavior listed above is acceptable since it's
not vital to the program, but I'm still gonna play with
NSUserDefaults some more.
