Open endolith opened 3 years ago
Yes, this is a consequence of using the Windows ANSI API instead of the wide-character version. I don't really do much Windows programming, and I've never done any I18N work on Windows. I'm not sure how much work it would be to convert VBinDiff to the W API. I'd be interested in a patch if somebody wants to try.
The workaround is to rename the file so it can be represented in the selected codepage.
interesting that this issue gets a reply, but series crash bugs don't.
you can simply compile the program with a manifest to use utf-8: https://docs.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page this is only for Windows 10 1903+ but is basically an effortless change
It returns an error message with them replaced by question marks: