- From: Harald Tveit Alvestrand <harald@alvestrand.no>
- Date: Mon, 14 Jan 2002 14:35:22 +0100
- To: toby_phipps@peoplesoft.com, ietf-charsets@iana.org
Two wishes for this registration: 1) Quote verbatim the text from DUTR#26: "It is not intended nor recommended as an encoding used for open information exchange." 2) Specify that the registration refers to the Draft UTR dated 2001-12-12, and is intended to be updated to refer to the final UTR when that document is available. I don't think that we need to wait for final publication before registering the charset label. If the definition changes before final publication, and the final one has to be CESU-8v2, that is a risk the registrant takes. Harald --On 2. januar 2002 01:48 -0800 toby_phipps@peoplesoft.com wrote: > Charset name: CESU-8 > > Charset aliases: csCESU-8 > > Suitability for use in MIME text: No > > Published specification(s): > Unicode Technical Report #26 > "Compatibility Encoding Scheme for UTF-16: 8-bit (CESU-8)" > http://www.unicode.org/unicode/reports/tr26 > > ISO 10646 equivalency table: See specification. > > Additional information: > CESU-8 is an 8-bit Compatibility Encoding Scheme for UTF-16 (CESU) that > is intended for internal use within systems processing Unicode in order > to > provide an ASCII-compatible 8-bit encoding that is similar to UTF-8 but > preserves UTF-16 binary collation. Data encoded in CESU-8 should only > be exchanged when it is labeled as such in a higher-level protocol or > is agreed upon in an API definition. > > Person & email address to contact for further information: > Toby Phipps > tphipps@peoplesoft.com > > Jianping Yang > jianping.yang@oracle.com > > Nobuyoshi Mori > nobuyoshi.mori@sap.com > > Intended usage: LIMITED USE > > > > >
Received on Monday, 14 January 2002 09:48:15 UTC