Revised proposal for UTF-16

Here is the revised verion of the proposal.  Have we reached a consensus?

Makoto
-----------------------------------------------------------------------
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.
However, the MIME-like mechanism of HTTP may use this character set for text/*, 
since this mechanism is exempt from the restrictions on the text top-level type
(see section 19.4.1 of HTTP 1.1 [RFC-2068]). 

   [RFC-2068] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, T. Berners-
   Lee. "Hypertext Transfer Protocol -- HTTP/1.1" UC Irvine, DEC,
   MIT/LCS. RFC 2068. January, 1997.


Charset name(s): UTF-16

Published specification(s): 

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

As long as the character repertoires and code point assignments of 
ISO 10646 and those of Unicode are in sync, and as far as they are
not being reallocated, this charset refers to the latest version of
Unicode/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 



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 Monday, 18 May 1998 15:03:14 UTC