http://bugs.winehq.org/show_bug.cgi?id=15253
--- Comment #2 from Giuseppe Adamo giuseppe.adamo@gmail.com 2008-09-16 04:38:39 --- (In reply to comment #1)
There is no need for the test program, it's enough to install the font file, add it to the registry, and run notepad (Edit -> Font).
The problem is that the font is broken from the Wine point of view, it has charset set to 2 (SYMBOL_CHARSET). If Windows handles that, Wine should be fixed, but as a workarond you could set the font charset to 0.
First of all thank you very much for the suggestion. I changed the charset code from 2 to 0 and this way the attached example, BMPFontTest.zip works fine. But, when I tried to use the fixed font with my VB6 program it still had visualization problems. Again I started to simplify the problem and wrote two simple VB6 applications that you can find attached to this thread.
The first one, BMPFontTest_2.zip, simply has a label control dropped on a form with the property font set at DESIGN-TIME. This example has no lines of code and doesn't work.
The second one, BMPFontTest_3.zip, is the same application as the above one but it sets the font name ad size at RUN-TIME. This example works fine !
I don't know the reason of this behavior but settings fonts properties for controls at run time is a good workaround. It seems, but it's only an impression, that all the design-time properties for fonts are ignored or not set. When using bitmap fonts, the problem is evident and visible since nothing or strange characters are printed; but when using true type fonts the result is that, apparently, default fonts with default sizes are used.