W3C home > Mailing lists > Public > ietf-charsets@w3.org > April to June 2001

Re: Registration of new charsets UTF-32, UTF-32BE, UTF32LE

From: Mark Davis <mark.davis@us.ibm.com>
Date: Wed, 09 May 2001 14:33:40 -0700
To: ned.freed@mrochek.com
Cc: ietf-charsets@iana.org
Message-id: <OF0DE82293.930B5208-ON88256A47.00766372@rchland.ibm.com>

Sorry, I missed that. Do you want me to resubmit, or could you just make
that change?

Mark
___
Mark Davis, IBM GCoC, Cupertino
(408) 777-5850 [fax: 5892], mark.davis@us.ibm.com, president@unicode.org
http://maps.yahoo.com/py/maps.py?Pyt=Tmap&addr=10275+N.+De+Anza&csz=95014



ned.freed@mrochek.com on 05-09-2001 09:54:09

To:   Mark Davis <markdavis34@home.com>
cc:   ietf-charsets@iana.org
Subject:  Re: Registration of new charsets UTF-32, UTF-32BE, UTF32LE



> Charset aliases:

> NONE

> Suitability for use in MIME text:

> YES

Sorry. UTF-32, like UTF-16 is NOT suitable for use in MIME text. In
particular,
it uses octets with a value of 0. Additionally, CR and LF aren't
represented in
the same way as in ASCII.

The answer to this question is therefore NO, not YES.

> Published specification(s):

> http://www.unicode.org/unicode/reports/tr19/

> ISO 10646 equivalency table:

> Also in http://www.unicode.org/unicode/reports/tr19/

> Additional information:

> Mark Davis
> 2509 Alpine Road, Menlo Park, CA 94025
> mark@unicode.org

> Intended usage:
> LIMITED USE

> (This template was taken from http://www.normos.org/ietf/bcp/bcp19.txt.
If
> any additional information needs to be supplied, please let me know.)
> ----------
> http://www.macchiato.com
Received on Wednesday, 9 May 2001 17:37:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 5 June 2006 15:10:51 GMT