Quote:
Originally Posted by Mosu
It is the case. The values to use simply depend on the operating system in question. On Linux/Unix you'll have to use en_US and on Windows it's en or English (both should work). My tools use the same conventions for locale names as the operating system they're running on. They don't try to map Linux-specific locales (en_US) to Windows-specific ones (en) and vice versa.
I've just verified on both Linux and Windows that what I've written above is correct and works. On a German Windows using --ui-language en works (as does --ui-language English); on a Linux with LC_ALL=de_DE.UTF-8 using --ui-language en_US works.
|
That's actually great news! It's a much simpler solution and I already commited it to trunk!
Thanks again!
@djcj
You should try r115+!