Sorry if this was answered before -
Microsoft Windows Win32 APIs up to and including NT 5.0 beta 2 ignore or even
mistreat surrogate pairs and other representations (UTF-8) of non-BMP
Conversions between UTF-8 and UCS-2 yield incorrect results for non-BMP
characters, at least if "correct" means UTF-16 as specified in Unicode 2.0 .
Non-BMP characters are destroyed in these conversions.
I don't know if the OpenType technology supports this.
PS: Microsoft advertises compliance with Unicode 2.12 . I expect them to
fulfill it eventually...
Markus Scherer IBM RTP +1 919 486 1135 Dept. Fax +1 919 254 6430
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:42 EDT