![]() ![]() ![]() The resource files use Windows 932 encoding, and I have added 2 Kanji characters (日本 = Nihon = Japan) to all text elements. 6 dialogs with 6 fonts in different classes: 2 Western fonts (“Arial” and “Comic Sans MS”), one Japanese font described by it’s English and Japanese name (“MS Gothic” and “MS ゴシック”), and two generic fonts (“MS Shell Dlg” and “MS Shell Dlg 2”).3 lines of text (displayed in WM_PAINT using DrawText) with 3 different fonts ( DEFAULT_GUI_FONT, “MS Gothic” and “MS ゴシック”).The UI tries to cover the most common elements containing text: It is the basic Win32 as created by the Visual Studio 2005 wizard, adapted to load resources from a dll (name provided in the command line). You can download the code and see for yourself. This is where this article is trying to help. Fortunately my system doesnt really use Tahoma for most text. Usually the answer points to one of the following elements: OS version, OS system code page (or “ANSI code page”), if the application is Unicode or ANSI, how was the resource file encoded and compiled, fonts.īut trying to figure out exactly what is wrong might require a lot of back and forth, with successive questions and answers, working to narrow down the exact problem. I think your second MS Shell Dlg is a typo for MS Shell Dlg 2. Maybe one of the most common question asked in newsgroups is the one above. There are many elements affecting this, but the most important are described below. I am trying to create a Japanese application and I get corrupted characters/question marks. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |