[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Registration of new charset: UTF-32

To: Martin Duerst <duerst@w3.org>, iana@iana.org
Subject: Re: Registration of new charset: UTF-32
From: Harald Alvestrand <harald@alvestrand.no>
Date: Fri, 12 Apr 2002 09:41:46 +0200
Cc: Mark Davis <mark@macchiato.com>, ietf-charsets@iana.org
In-reply-to: <4.2.0.58.J.20020412152551.00a8d0d8@localhost>
References: <003401c11914$33c5dcd0$0c680b41@c1340594a><003401c11914$33c5dcd0$0c680b41@c1340594a><4.2.0.58.J.20020412152551.00a8d0d8@localhost>

--On fredag, april 12, 2002 15:28:08 +0900 Martin Duerst <duerst@w3.org> 
wrote:

>>> The IETF registration imposes one additional constraint: if there is no
>>> initial BOM then the byte-orientation must be big-endian. That is, in
>>> any stream that does not begin with the (hex) byte sequence <00 00 FE
>>> FF> all of the bytes are interpreted as big-endian.

note: in this paragraph, <00 00 FE FF> needs to be replaced by <FF FE 00 
00> - the example is big-endian.

Apart from that - PLEASE get it done; this has been waiting far too long.

                     Harald

References:
- Registration of new charset: UTF-32
  - From: Mark Davis <mark@macchiato.com>
- Re: Registration of new charset: UTF-32
  - From: Martin Duerst <duerst@w3.org>

Prev by Date: RE: RFC 2279 (UTF-8) to Full Standard
Next by Date: Re: RFC 2279 (UTF-8) to Full Standard
Prev by thread: Re: Registration of new charset: UTF-32
Next by thread: RE: Registration of new charsets: UTF-32, UTF-32BE, UTF-32LE
Index(es):
- Date
- Thread