http://bugs.winehq.org/show_bug.cgi?id=59127 --- Comment #1 from Andreas Mohr <andi@rhlx01.fht-esslingen.de> --- "The activeCodePage manifest element can be used for more than just setting UTF-8 as the active code page" https://devblogs.microsoft.com/oldnewthing/20220531-00/?p=106697 appears to be exactly about describing that behaviour: "If you specify an activeCodePage of Legacy, then you’re saying that your application actively hates UTF-8. It will be given the system default locale, provided a system default local exists and it isn’t UTF-8. In those exceptional cases, you get code page 1252 as a fallback. You can also specify a locale name such as en-US or ja-JP, and the application gets the code page corresponding to that locale. If the locale is not recognized by the system, then you get UTF-8 as a fallback.". So, this: - appears to confirm my writing - most likely is what this implementation ought to do -- 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.