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

Re: HTTP Working Group 'issues' list

From: <kennykb@cobweb.crd.ge.com>
Date: Mon, 19 Feb 96 15:25:33 -0500
Message-Id: <9602191525.AA03005@cobweb.crd.ge.com>
To: Nickolay Saukh <nms@nns.ru>
Cc: HTTP-WG Mailing list <http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>

nms@nns.ru said:
> >    * QUERCHAR      What is the character set of URI query after ?   
> >   Response: ISO-8859-1.

> Are WWW going to be named LWW (Latin1 Wide Web)? :-)

No, but the query-string mechanism is inadequate for i18n.  Other charsets
in forms are handled with RFC 1867.  The only functionality that then can't
support non-Latin-1 charsets is <ISINDEX>, and the same effect can be achieved
with properly designed forms.

A URL was originally supposed to be an opaque sequence of octets, and
therefore the charset was relevant only in that it had to be representable
as CDATA.  Unfortunately, that isn't how the world has turned out.

Other character sets could be represented in URL's using a convention
similar to the one laid out in RFC 1522, but I have not seen any *formal*
proposal to do so.

--
73 de ke9tv/2, Kevin KENNY   GE Corporate Research & Development
kennykb@crd.ge.com           P. O. Box 8, Room KWC273
                             Schenectady, New York 12301-0008 USA
Received on Monday, 19 February 1996 07:40:46 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:31:45 EDT