Subject: Re: Win98 i18n Unicode fonts trouble possibly solved.
From: Lukas Pietsch (pietsch@mail.uni-freiburg.de)
Date: Thu Jan 04 2001 - 04:55:50 CST
Thanks to Gilles for the Win9x patch.
I've played around on my Win98 machine a bit, and I find that not
even the Symbol fonts seem to need special treatment, in
principle. In a little test programme I wrote, everything got
displayed just fine, no matter which font. As long as you use
ExtTextOutW, it apparently doesn't even matter what fdwCharset
you specify for CreateFont. I did my best trying to make Windows
display things the wrong way, and I simply couldn't!
The knowledge base article you quoted must be wrong (well
actually, it's self-contradictory anyway, isn't it?)
The only difference is: If a string contains characters >hexFF,
if you use ExtTextOutW with a symbol font, the extended
characters will just disappear. If you use WideCharToMultibyte
and ExtTextOutA, they will probably be displayed with some
replacement glyph, right? You may be right, this may actually be
preferable.
Lukas
>
> The patch I am proposing is making some ground for Win9x. It
now support
> usuals, unicode and symbol fonts. Symbol fonts are detected
automaticaly.
> Characters widths are evaluated correctly.
>
> >From my Microsoft knowledge base reading, on Win9x the gliphs
displayed will
> be dependent on the actual code page used on the computer. I do
not know if
> it is a good thing or not. My machine use code page 1252 and
results are ok
> for differents fonts I tested.
>
> Gilles
>
This archive was generated by hypermail 2b25 : Thu Jan 04 2001 - 04:58:15 CST