Re: Registration of new charset "UTF-16"

• From: Chris Newman <Chris.Newman@INNOSOFT.COM>
• Date: Mon, 18 May 1998 10:01:15 -0800 (PST)
• To: "Martin J. Duerst" <duerst@w3.org>
• Cc: MURATA Makoto <murata@apsdc.ksp.fujixerox.co.jp>, erik@netscape.com, ietf-charsets@ISI.EDU, murata@fxis.fujixerox.co.jp, Tatsuo_Kobayashi@justsystem.co.jp
• Message-id: <Pine.PMDF.3.95.980518095401.538969665G-100000@INNOSOFT.COM>

> Something else that should be added to the registration information
> is that UTF-16 always should refer to the newest version of Unicode/
> ISO 10646. This has been discussed on the unicore list, but not here,
> but it is very crucial.

I suggest that you simply say that UTF-16 tracks the same version of the
standard that UTF-8 does as defined in RFC 2279.  The text in RFC 2279 was
wordsmithed carefully.

In particular, the charset label should only track the addition of new
characters to 10646 and should not track incompatible changes to that
specification without an explicit decision by the IETF.

		- Chris



--Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)

Received on Monday, 18 May 1998 11:07:53 UTC