W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1996

Re: Issue: CHARSET, character sets and charset

From: Paul Hoffman <paulh@imc.org>
Date: Mon, 8 Apr 1996 17:51:02 -0700
Message-Id: <v03005b1dad8f62f3831d@[]>
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/202
>>   charset = "US-ASCII"
>>	| "ISO-8859-1" | "ISO-8859-2" | "ISO-8859-3"
>>	| "ISO-8859-4" | "ISO-8859-5" | "ISO-8859-6"
>>	| "ISO-8859-7" | "ISO-8859-8" | "ISO-8859-9"
>>       | "ISO-2022-JP" | "ISO-2022-JP-2" | "ISO-2022-KR"
>>       | "UNICODE-1-1-UTF-8"

Listing these charsets by name seems like a slippery slope to me. For
example, the brand new RFC 1922 describes ISO-2022-CN and ISO-2022-CN-EXT,
which will probably appear in the IANA registry around the same time we get
this spec out, if not sooner.

Should we exclude the Chinese while leaving in the Japanese and Koreans?
Why are some charsets "specifically recommended for use within MIME charset
parameters." These are rhetorical questions, not to be discussed on the
HTTP WG at this late date. However, I think we might want to come up with a
more open, or possibly a much shorter, listing of the "initial preferred
Received on Monday, 8 April 1996 17:55:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:16 UTC