Re: Registration of new charset "UTF-16"

In message "Re: Registration of new charset "UTF-16"",	Ned Freed wrote...
> True, but whether or not a charset is suitable for use with MIME text
> is one of the things that's required in a registration. See RFC 2278,
> Section 3.1.

In message "Re: Registration of new charset "UTF-16"", Chris Newman wrote...
> The rule to mention whether a charset was suitable for text media types
> was added with the RFC 2278 registration rules.  The registry hasn't been
> fully updated yet to reflect those rules, but new registrations have to
> meet them.

Thank you for pointing this out. > Ned and Chris.  
I modified the proposal as below:

-----------------------------------------------------------------------
We propose to register UTF-16 as a charset in IANA.  UTF-16 should be 
sent in network byte order (big-endian).  However, recipients should be 
able to handle both big-endian and little-endian.

This character set is not permitted for use with MIME text/* media types.

Charset name(s): UTF-16

Published specification(s): 

UTF-16 is defined in Appendix C.3 of [UNICODE] and Amendment 1 of [ISO-10646].

[ISO-10646] ISO/IEC, Information Technology - Universal Multiple-Octet Coded 
Character Set (UCS) - Part 1: Architecture and Basic Multilingual Plane, 
May 1993, with amendments 1 through 7.

[UNICODE] The Unicode Consortium, "The Unicode Standard -- Version 2.0", 
Addison-Wesley, 1996.


Person & email address to contact for further information:

Tatsuo L. Kobayashi
Digital Culture Research Center, JUSTSYSTEM Corp.
Email: Tatsuo_Kobayashi@justsystem.co.jp

Murata Makoto (Family Given)
Fuji Xerox Information Systems,
KSP 9A7, 2-1 Sakado 3-chome,
Takatsu-ku, Kawasaki-shi,
213 Japan
Email: murata@fxis.fujixerox.co.jp 



[Thu, 14 May 1998 13:04:51 +0900]

Makoto
 
Fuji Xerox Information Systems
 
Tel: +81-44-812-7230   Fax: +81-44-812-7231
E-mail: murata@apsdc.ksp.fujixerox.co.jp

--Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)

Received on Thursday, 14 May 1998 06:42:14 UTC