English App on Japanese OS
-
Hey, I am looking for a solution to an eternal problem. We get complaints that our software does not look good in English when running on a Japanese OS. Most of the problems revolve around the wizards and property pages not sizing correctly. This is because I cannot find a way for the MS PropertySheet and PropertyPage to use a more English favorable font. Does anyone know a way to force the MS controls to use the current dialogs font and sizing and ignore the OS specifications? I should say and do this without affecting the users OS in a deterimental way. I don't want to change things on the OS out from under a user obviously. Just as a side note, the applications are not MFC but Win32 API. Thanks, Brian If you start a fire for a man, he will be warm for a day. If you start that same man on fire, he will be warm for the rest of his life.
-
Hey, I am looking for a solution to an eternal problem. We get complaints that our software does not look good in English when running on a Japanese OS. Most of the problems revolve around the wizards and property pages not sizing correctly. This is because I cannot find a way for the MS PropertySheet and PropertyPage to use a more English favorable font. Does anyone know a way to force the MS controls to use the current dialogs font and sizing and ignore the OS specifications? I should say and do this without affecting the users OS in a deterimental way. I don't want to change things on the OS out from under a user obviously. Just as a side note, the applications are not MFC but Win32 API. Thanks, Brian If you start a fire for a man, he will be warm for a day. If you start that same man on fire, he will be warm for the rest of his life.
Are you concerned about just the appearance, or about how DBCS characters appear in your UI, or about handling DBCS strings in general? From your description it sounds like #2, but have you even tested #3? If not, #2 is the least of your troubles. The quick answer for fixing #2 is to make these changes in all your dialog resources:
- Use
MS Shell Dlginstead ofMS Sans Serifas the font - Change all
DIALOGresources toDIALOGEX - Add the
DS_FIXEDSYSdialog style
--Mike-- LINKS~! Ericahist | 1ClickPicGrabber | CP SearchBar v2.0.2 | C++ Forum FAQ | You Are Dumb Magnae clunes mihi placent, nec possum de hac re mentiri. Strange things are afoot at the U+004B U+20DD
- Use
-
Are you concerned about just the appearance, or about how DBCS characters appear in your UI, or about handling DBCS strings in general? From your description it sounds like #2, but have you even tested #3? If not, #2 is the least of your troubles. The quick answer for fixing #2 is to make these changes in all your dialog resources:
- Use
MS Shell Dlginstead ofMS Sans Serifas the font - Change all
DIALOGresources toDIALOGEX - Add the
DS_FIXEDSYSdialog style
--Mike-- LINKS~! Ericahist | 1ClickPicGrabber | CP SearchBar v2.0.2 | C++ Forum FAQ | You Are Dumb Magnae clunes mihi placent, nec possum de hac re mentiri. Strange things are afoot at the U+004B U+20DD
Thanks I will try that... Not worried about handling DBCS strings. We build our software in all UNICODE, with a few exceptions where the interfaces call for DBCS. Then we worry but I have a good handle on that. I also wrote a quick application to allow me to actually psudeo translate all the resources and insert DBCS characters in preparation for actually localizing the software. The only thing I couldn't figure out was why the property pages and the wizards would always truncate the English version of the dialog boxes when running on a Japanese OS. The strings which would normally be wide enough on an English wizard would be too wide for the Japanese wizard. If I expand the size of the English dialog resources without expanding the controls, then they would fit. However this made it look bad in English. I think this solution will help and I will try it. Thanks, Brian If you start a fire for a man, he will be warm for a day. If you start that same man on fire, he will be warm for the rest of his life.
- Use