[Bug 51451] New: Many Windows 10 VMs are incompletely localized
https://bugs.winehq.org/show_bug.cgi?id=51451 Bug ID: 51451 Summary: Many Windows 10 VMs are incompletely localized Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The localized w10pro64* VMs don't have the right UserDefaultLCID and are sometimes missing even more: w10pro64 fr_FR SystemDefaultLCID 040c UserDefaultLCID 0409 <--- should be 040c ThreadLocale 0409 ??? SystemPreferredUILanguages 040C,0409 UserDefaultUILanguage 040c ThreadUILanguage 040c w10pro64 ar_MA SystemDefaultLCID 0c01 UserDefaultLCID 0409 <--- should be 0c01 ThreadLocale 0409 ??? SystemPreferredUILanguages 0409 <--- should contain 0c01 UserDefaultUILanguage 0409 <--- should be 0c01 ThreadUILanguage 0409 <--- should be 0c01 w10pro64 he_IL UserDefaultLCID 0409 <--- should be 40d w10pro64 hi_IN Being a Unicode-only language means setting the system locale to Hindi was not possible in older Windows versions (up to early Windows 10). Now it is but it's considered Beta and uses the UTF-8 encoding in ANSI APIs. So it's not clear if it should be changed (and how to do it programmatically). SystemDefaultLCID 0409 <--- Unicode-only language UserDefaultLCID 0409 <--- should be 0439 ThreadLocale 0409 ??? SystemPreferredUILanguages 0439,0409 UserDefaultUILanguage 0439 ThreadUILanguage 0439 w10pro64 ja_JP UserDefaultLCID 0409 <--- should be 411 w10pro64 ko_KO UserDefaultLCID 0409 <--- should be 412 w10pro64 pt_BR UserDefaultLCID 0409 <--- should be 416 w10pro64 ru_RU UserDefaultLCID 0409 <--- should be 419 w10pro64 zh_CN UserDefaultLCID 0409 <--- should be 804 This prevents testing how Windows behaves when formatting and parsing their currencies in oleaut32:varformat for instance. Strangely enough the w7u* VMs don't have this issue: w7u de_DE SystemDefaultLCID 0407 UserDefaultLCID 0407 ThreadLocale 0407 SystemPreferredUILanguages 0407 UserDefaultUILanguage 0407 ThreadUILanguage 0407 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51451 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|wine-bugs(a)winehq.org |fgouget(a)codeweavers.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51451 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- The TestBot sets the locale settings using SetWinLocale [1] when preparing the live snapshots. Then to run a task it reverts the VM to the live snapshot and calls SetSystemTime() to update the VM's clock. If this moves the clock more than 24 hours forward Windows 10 resets the UserDefaultLCID, ThreadLocale and Country settings to their pre-SetWinLocale values. The reason for that is unknown. So now the TestBot sets these specific local settings again after updating the VM's clock. It's really ugly but at least it works. [1] https://gitlab.winehq.org/winehq/tools/-/blob/master/testbot/bin/SetWinLocal... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla