"Troy Rollo" wine@troy.rollo.name wrote:
Did you test specifically A->W conversion of the message data or something else?
I tested the CP_ACP conversions and the GetACP call.
Actually you didn't answer the question. GetACP() by itself shows nothing, only actual API tests could show something useful.
I also disassembled kernel32.dll to see how it populated CP_ACP (if I recall correctly it populated it from a registry key under either HKEY_CURRENT_CONFIG or HKEY_LOCAL_MACHINE, so perhaps a change in the registry could cause the same behaviour as a process calling SetCPGlobal, but threads within a single process can never have a different CP_ACP).
I don't believe it, especially since SetThreadLocale exists.
And ...
Even if it doesn't work on current Windows platforms I don't see why Microsoft can't fix it and make it work in future versions.