http://bugs.winehq.org/show_bug.cgi?id=19821
--- Comment #8 from Thomas Heckel thomas.heckel@gmx.net 2009-08-31 05:40:37 --- (In reply to comment #7)
(In reply to comment #6)
If "Nls" key is 0409 (English) then Autohotkey reports to the scripts which are using the internal AHK variable "A_Language" they're under an english environment. Which is not the case, as other apps show correctly. But the - maybe wrong - assumption of AHK with using "Nls" key works well under Windows.
That can't work under Windows. For instance my version of XP is English (and InstallLanguage is 409), but the locale is Russian (419). So Wine can be treated as an English OS with Russian locale/language pack.
I'd suggest to report the bug to AutoHotKey developers.
I've reported it to Chris Mallett from Autohotkey and maybe it would be changed to a more precise way in a future major release. And from my own research I agree to you. It seems to be possible to take another system language for the dialogs after installation (and done so by Multilingual-User-Interface Editions of Windows like Windows Embedded).
AFAIK from MSDN resources and infos from Chris the registry keys "InstallLanguage" and "Default" will contain the default language code page of the CD or that was selected during Windows installation. ( http://msdn.microsoft.com/en-us/library/dd374098(VS.85,printer).aspx , http://technet.microsoft.com/en-us/library/cc957158(printer).aspx 's comment of "Default" entry under topic "LanguageID REG_SZ Filename" ).
On the other way, "MUI products are available only through volume agreements from Microsoft. They are not available through retail channels." (from Wikipedia Multilingual_User_Interface)
As I mentioned in bug opening comment, AHK's quirked approach (yes it should have better used something like GetThreadLocale ) works well under my retail Windows XP. So it's probably a question of compatibility: should Wine imitate MUI features or should it better present as a "windows" which was installed with current LC* environment settings.