- From: Roy T. Fielding <fielding@avron.ICS.UCI.EDU>
- Date: Mon, 08 Apr 1996 18:48:11 -0700
- To: Paul Hoffman <paulh@imc.org>
- Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
>>> 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.
This is a chicken and egg issue. We wouldn't need a list in HTTP if
there were a list of short, charset-friendly, preferred names kept
by IANA. However, there isn't.
...Roy T. Fielding
Department of Information & Computer Science (fielding@ics.uci.edu)
University of California, Irvine, CA 92717-3425 fax:+1(714)824-4056
http://www.ics.uci.edu/~fielding/
Received on Monday, 8 April 1996 19:03:20 UTC