Re: format nego in HTML/10646?

Gavin Nicol (gtn@ebt.com)
Tue, 9 May 95 11:20:50 EDT

>As I thought I said before, "unicode-1-1-ucs-2" is not registered as
>an encoding with IANA (maybe you will want to); either register it or
>use a different name for the encoding you want.

It's interesting to note that the character sets recognised in IETF
documentation include:

Name: ISO-10646-UCS-2
Source: the 2-octet Basic Multilingual Plane, aka Unicode
this needs to specify network byte order: the standard
does not specify (it is a 16-bit integer space)

Name: ISO-10646-UCS-4
Source: the full code space. (same comment about byte order,
these are 31-bit numbers.

Name: ISO-10646-UTF-1
Source: Universal Transfer Format (1), this is the multibyte
encoding, that subsets ASCII-7. It does not have byte
ordering issues.

Name: UNICODE-1-1 [RFC1641]
Source: RFC 1641

Name: UNICODE-1-1-UTF-7 [RFC1642]
Source: RFC 1642