nanogui: New Microwindows font support
Subject:
Re: New Microwindows font support
From:
"Greg Haerr" ####@####.####
Date:
21 Mar 2000 21:37:48 -0000
Message-Id: <072e01bf937c$fcd72850$3017dbd0@censoft.com>
For Nano-X/Microwindows purpose I'd say the best would be to exchange data
: in UTF-8 and convert to UTF-32 (the subset of legal Unicode scalar values
: from UCS-4) for display.
The 0.88pre4 implementation allows applications to specify
text in ASCII, UTF8, UCS16 or UCS32, depending on the flag
word to GrText. Win32 api allows either 8-bit codepage ASCII
or UCS16 only, since there is no flags word. Microwindows
could, for the win32 api implementation, assume ASCII really
UTF8, since the low 128 code points are identical.
: it would perhaps be just as easy to just make the conversion functions
available
: to the font renderer and let it decide how to deal with the conversion - I
: don't see why there should be any need to convert it until as late as
possible
: before the values will be used. UTF-8 is becoming so commonplace that it's
: certainly conceivable that font renderers that handle the conversion
internally
: will start popping up.
This is exactly how 0.88pre4 implements it: the conversion is handled as
late
as possible, and is actually specified by the font renderer, and converted
just before passing to the "rendervendor_drawtext" routine.
:
: As for the actual use for surrogate pairs, there is work underway to add
glyphs
: that will require them for UTF-16... So ignoring it will be a problem at
some
: point, allthough it likely isn't *now*.
Hopefully Morten added that in the utf8_to_ucs16 converter he just wrote.
Regards,
Greg
