It's also not true for the relevant Microsoft products. Arabic, Hebrew, and
Thai Windows 98 and Windows NT obviously don't assume a 1-1 Unicode
character to glyph model. All versions of Windows 2000 (new name for
Windows NT 5.0) will be able to display these complex scripts (our name for
those that *require* an n to m character->glyph model) correctly.
F. Avery Bishop
Program Manager, Multilingual Developer Communications
> -----Original Message-----
> From: Werner LEMBERG [SMTP:firstname.lastname@example.org]
> Sent: Wednesday, December 23, 1998 8:59 AM
> To: Unicode List
> Cc: email@example.com
> Subject: Re: News of AFII: international standard registry of glyp...
> >The overlapping of the Private Use Area and the Corporate Use
> >Subarea is only a concern if you want to do a 1-to-1
> >Unicode->Glyph mapping (e.g. for unknown glyphs or glyphs which
> >can't be handled by your rendering system) -- of course, it's a
> >shame that even recent software written by Apple, Adobe, or
> >Microsoft still rely on the 1-to-1 Unicode->Glyph model...
> Huh? What recent software written by Apple relies on the 1-1
> Unicode->Glyph model? Our Unicode imaging system in Mac OS 8.5
> (ATSUI) certainly doesn't.
> Oops! Sorry for that. This was a contraction of two sentences -- one
> with Microsoft and the other one with Apple and Adobe :-) My fingers
> were faster than my brain.
> Nevertheless, can you explain the reasons why you need some area in
> the CUS? For backward compatibility? Adobe and MS probably have the
> same reasons...
> Most likely, Unicode level 2 isn't implemented yet...
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:43 EDT