In a message dated 2001-11-18 19:49:08 Pacific Standard Time,
jameskass@worldnet.att.net writes:
> Surely, the browser's lack of ability in being able to handle
> UTF-8 for Plane One, while handling UTF-8 for Plane Two
> just fine (on W2K), is a bug that should be fixed. It also
> illustrates that non-BMP support is still rather new, still
> under testing, and still being developed. Hopefully, future
> updates of MSIE/Uniscribe will resolve these issues.
The time is NOW for all manufacturers of Unicode-enabled software, Microsoft
and everyone else, to test their products with supplementary characters or
code points and fix any problems. Supplementary characters are part of
Unicode TODAY.
Delaying this support any further will only cause headaches for the CJK users
who can't view or print their personal name logographs encoded in the SIP,
and who will find some way to blame Unicode for this.
-Doug Ewell
Fullerton, California
This archive was generated by hypermail 2.1.2 : Mon Nov 19 2001 - 00:51:40 EST