CString::LoadString() issue in Release build
My Unicode project loads the correct strings in debug version (either English or Chinese based on settngs) but in release build it doesn't load the chinese strings. It displays them as questions marks like ????. I have simple test code to load a string.
Code:
CString test;
test.LoadString( ID_FILE_NEW );
AfxMessageBox( test );
The project settings are the same for debug and release build. The release build does show menu in Chinese but the LoadString() functions display only ????? marks.
I think I can safely rule out fonts as debug version works fine and partially the release version as well. What could possibly be wrong?
Re: CString::LoadString() issue in Release build
Where are the Chinese strings: in exe or dll?
If you open this Release exe or dll in some Unicode editor - do you see Chinese texts or "????" ?
Re: CString::LoadString() issue in Release build
Quote:
Originally Posted by
VictorN
Where are the Chinese strings: in exe or dll?
If you open this Release exe or dll in some Unicode editor - do you see Chinese texts or "????" ?
Chinese strings are in dll. I see the text fine in Chinese in Visual Studio editor. All the strings/resources are in the single .rc file. Moreover the menus load fine and are correctly displayed in Chinese but only whatever I load with LoadString() comes up as ????
Re: CString::LoadString() issue in Release build
Quote:
Originally Posted by
zspirit
Chinese strings are in dll. I see the text fine in Chinese in Visual Studio editor. All the strings/resources are in the single .rc file. Moreover the menus load fine and are correctly displayed in Chinese but only whatever I load with LoadString() comes up as ????
And if you load dll as a resource in VS - are the Chinese string OK?
And if you open this Release exe or dll in some Unicode editor - do you see Chinese texts or "????" ?
Re: CString::LoadString() issue in Release build
My bad! I thought I checked it many time yet release project settings were Multibyte instead of Unicode! that change fixed it.