nanogui@linuxhacker.org
nanogui@linuxhacker.org
: Does that means that UNICODE is supported in MWin?
Yep. For Nano-X, the GrText entry point has had another
parameter added, which is the text string data type. The following
are legal values:
TF_ASCII 8 bit ascii
TF_UC16 16 bit unicode
TF_UC32 32 bit unicode
TF_UTF8 UTF8
The Microwindows engine translates from the input format to the
format requested by the font renderer. Currently, we have 3 font
renderers, and their requested data format:
CoreFonts (compiled in fonts) - currently TF_ASCII
FreeType (truetype fonts) - TF_UC16
T1lib (Adobe type 1) - TF_ASCII (I'd like to see this change to TF_UC16)
Microwindows doesn't yet have unicode<->codepage tables loaded,
but these should be fairly easy to add if not using a unicode font renderer.
For the Microwindows api, I'll soon be adding DrawTextW and ExtTextOutW,
which take 16-bit unicode.
Regards,
Greg
nanogui@linuxhacker.org