> While this sounds like it makes implementation much easier than bypassing
> these APIs, it does not sound like justification to redefine UTF-16, have
> Microsoft and everyone else update their APIs so as to minimize the
> on the implementation of this editor and associated tools.
this project may be going to run into another problem:
win32 api functions do not implement utf-16, but ucs-2. this is true up to
nt 5.0 beta 2, at least.
this means that anything surrogate is ignored by windows. typically, you
are ok for as long as you display your glyphs as you need them, which the
editor here seems to be doing anyway. however, never try to convert to or
from utf-8: to utf-8, surrogates are incorrectly converted as single 16b
characters, and beyond-bmp utf-8 characters are truncated to 16b.
the world of (16b) unicode implementations is not even quite utf-16-ready
yet, it seems...
Markus Scherer IBM RTP +1 919 486 1135 Dept. Fax +1 919 254 6430
Unicode is here! --> http://www.unicode.org/
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:45 EDT