-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question marks everywhere #3
Comments
Technical detailsWhy is this happening?This is because ANSI version of Windows API functions are used. It is a must in order to keep compatibility with Windows 9x, which exists in the 32-bit binary release. When using ANSI version of Windows API functions, Unicode text stored in resources are converted to the text encoding of the current codepage of your Windows environment before they are displayed. Only characters supported by your current codepage can be displayed properly, the rest are converted to question marks (?). The question marks in your snapshot are Japanese kana and kanji characters, which are unsupported in Windows-1252 and other Latin-1 compliant codepages. Therefore they are all converted to question marks. How to fix it?This can be fixed by changing the Windows API functions in the source code to their Unicode versions and building a binary without Windows 9x support. I may build one some day and put it under the release. In this case UnicoWS can be used to preserve Windows 9x support but it is not perfect. Font support on Windows 9x is tailored to only what its codepage (depending on Windows language) supports. Those characters are still unable to be displayed properly if the system does not contain Japanese fonts. What do they mean?The texts in your snapshot are defined in the resource file: Lines 19 to 32 in 6ea03ec
Here is a brief translation: Caption
Checkboxes
Buttons
|
How to fix those text labels, where are those string stored in the code (i haven't built it, i downloaded from releases) or at least what do they mean
The text was updated successfully, but these errors were encountered: