Closed mhertz closed 4 years ago
You probably had some windows environment with char > 128 (e.g. some accented, probably é or something similar like ò, à, ù ...) and this gives the decoding error.
We can ignore the wrong character but if the character goes in the vs installation path (this can happen if you install it in your document & setting folder and your user name is not all ascii char) we cannot do anything: you must reinstall it in the default path or in a 'old' one (the old ones are the one I used from the 8.3 times of DOS, so my documents folder is DOC and I install the visual studio 2019 in the C:\dev\vs2019, never using spaces in names :)
I push a commit to fix the problem. See if it works.
With best regards
I owe you several beers for all the help you have given me Danny! :) Thank you so much once again, really appreciate it, and was reported by affected user to work correctly now. Thanks again mate.
I have 2 installations of msvc, the community 2019 and 2022 version, installed in the default paths and this occurrs. I could bypass it by enabling the "beta" of utf-8. The paths do not contain any ascents or special symbols. Only ASCII symbols.
I hope it's okay I forward a report by other user here. I haven't the issue personally, but am then guessing it's a localization issue possibly? Affected user is using msvc 2019 buildtools just installed yesterday or so, so newest version, and py 3.8.3 and newly updated msys2, on win10 x64. All components installed and setup from unattended script I made, which affected user also installed from, so we have exact same setup, except maybe different locales where I have US.
This is exact error:
I believe there's options for selecting to only install non-localised versions of msvc, from cmd-line options, so am thinking if that would help maybe, but still is then an issue which many would be bitten from seemingly.
I couldn't find previous reports for this here or online(vcvars parsing UnicodeDecodeError specifically), but as general issue there is several, and states to change encoding to e.g. windows-1252 or latin etc. It's seems 0x92 is a smart quote character from windows-1252, which some say can be problematic reading/decoding through utf-8, and some stated fixed by changing encoding to windows-1252, or resaving file in question in utf-8, but dunno, have no experience with such personally, but sounds like the issue however. Just strange something like that could occure i.e. other localization introducing smart/curly quotes???
Many thanks in advance for any feedback/help.
Ohh, this is full log of command-line run and output:
Edit: When only searching unicodedecodeerror solely, here, then I found this earlier ticket, not related to this issue here specifically(vcvars), but does however suggest localisation issues could be occuring since happened before, though in other component(meson), and other unicode char issue:
https://github.com/wingtk/gvsbuild/issues/247