>Herman Miller scripsit:
>
>> Unfortunately, TrueType under Windows doesn't have that capability, so
>> going to 16-bit character sets doesn't help. Yet another short-sighted
>> implementation on Microsoft's part.
>
>Try this. Download the CODE2000 Unicode font
>from
http://http://home.att.net/~jameskass/CODE2000.ZIP and install it.
>Make it your Unicode font in Netscape. Then visit
>
http://www.unicode.org/unicode/reports/tr15/NormalizerChart.html ,
>which displays composed and decomposed characters side-by-side in
>columns 2 and 3. On my Windows NT 4.0 system, they are identical in
>form, showing that the decomposed sequence is converted by the font
>engine to the correct glyph.
Hmm.... It looks like Netscape's using the precomposed characters that
already exist in the font. The Code2000 font doesn't do anything special in
Word. (Windows 98, Word 2000). My Thryomanes font, which doesn't have any
special support for ligatures, also shows column 2 and 3 as identical
(Netscape Communicator 4.72).
But thanks for the link to the CODE2000 font; it looks like a really useful
one to have.
--
languages of Azir------> ----<