nanogui: displaying latin1, latin2 or european Unicode characters.
Subject:
Re: displaying latin1, latin2 or european Unicode characters.
From:
"Greg Haerr" ####@####.####
Date:
25 Jan 2001 20:25:50 -0000
Message-Id: <0ece01c0870e$692d6b10$6817dbd0@censoft.com>
: > I assume that you're running using GrText(..., MWTF_UC16);
: > It seems we may need to load various truetype/T1 fonts w/separate
: > decoding .enc files, something that we might need an additional API
: > for. Try loading a different .enc file for each of the fonts that
: > you are trying to display.
:
: OK, this is second step. First step is that if I want to use GrText(...,
: MWTF_ASCII) Latin1 encoding is not loaded. May I do direct T1lib calls
: from the client?
Not easily, unless you use LINK_APP_WITH_SERVER=Y
:
: > : I can accept the need to write all input text in unicode, but how to
match
: > : unicode characters to the fonts?
: >
: > Isn't that what the .enc file does? It's my understanding that you
: > ask T1lib for a glyph using a unicode index. Certainly Microwindows
: > carries the unicode index down to that level.
:
: The problem is T1lib does not accept unicode indices. It accepts 0-255
: index and uses currently loaded encoding to display it. So to do it
: correctly Microwindows would need to have a map of "unicode-index : font
: and encoding to use in T1" and reconfigure T1 dynamically. Or just load
: fonts with different encoding as different fonts.
I think the fix here is to always load a .enc file, like you patch
suggested, and then basically T1lib look like it supports unicode
indices. I would suggest that we patch Microwindows to always
attempt to load a matching .enc file, and then if MWTF_UC16 is specified,
to use unicode indices.
Regards,
Greg
