Subject: Re: Win98 i18n Unicode fonts trouble possibly solved.
From: Saint-Denis (stdenisg@cedep.net)
Date: Sat Jan 06 2001 - 13:17:57 CST
From: Lukas Pietsch <pietsch@mail.uni-freiburg.de>
> 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!
On Win95, symbol fonts need to be specified as SYMBOL_CHARSET or else they
appear either as boxes or as regular characters. In the microsoft article,
it is mentionned that "In furture versions of Windows 95 and Windows NT, the
multilingual specification will be merged into both platforms". From what I
can see in you comment, Win98 must be such a version.
> 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.
The hexFF character is shown as a box character.
Gilles
This archive was generated by hypermail 2b25 : Sat Jan 06 2001 - 13:20:01 CST