On 2023-11-14 15:41, Magnus Ihse Bursie wrote:
However, I'd like to have some more investigation into how cl.exe
picks the language.
Is it a hard-coded behavior that it always picks English if it is
installed? If so, it does not really make sense to have more than one
language pack installed. Or is there some way to tell cl.exe which
language to pick? Perhaps we send those signals without realizing it,
like if it happens to look at LC_ALL. If that is the case, we need to
know about this, so we don't inadvertently break it.
It seems that setting the environment variable VSLANG=1033 should do the
trick. Some reports on the Internet indicates that this perhaps needs to
be coupled with a "chcp 437".
Can you please test if that works? If you try setting VSLANG=2052, does
that force cl.exe to use the Chinese locale? If it does, happens if you
combine VSLANG=2052 with chcp 437?
If we are lucky, then this will boil down to
a) instructions in the documentation to install the English language
pack of Visual Studio, and
b) adding VSLANG=1033 to the makefiles.
but I'd like to get some confirmation that VS really works like that.
I have a vague memory of a discussion about VSLANG=1033 before, that it
did not help, but maybe the core issue at that time was that the
language pack was not installed, which made VS ignore the VSLANG variable.
/Magnus
