Re: URL character set

Fisher Mark (fisherm@tce.com)
Fri, 6 Mar 1998 09:58:11 -0500


Message-ID: <83C932393B88D111AED30000F84104A70A1F5C@indyexch_fddi.indy.tce.com>
From: Fisher Mark <fisherm@tce.com>
To: Larry Masinter <masinter@parc.xerox.com>,
Cc: "uri@Bunyip.Com" <uri@Bunyip.Com>
Date: Fri, 6 Mar 1998 09:58:11 -0500 
Subject: RE: URL character set

>Again, I'm confused of what URI syntax is for. Is it for what specified
in
>the HTML document, or it is for the URI that get transferred over the
wire?
>Could we make it more clear in the draft? But even it is the syntax for
what
>get transferred over the wire, I think it's still up to the scheme
specific
>service to decide what the syntax is, not the URI itself.

Maybe this is belaboring the obvious, but when it comes to the character
encoding, it seems to me that this is just exactly when the character
set issue is important.  You will want a U.S.-English-ASCII server to be
able to handle a URI sent by a JIS-browser, so the choice of translating
JIS to UTF-8, then hex-encoding the UTF-8 into ASCII, is a Good Thing.
Unicode offers all browsers and servers the chance to have at least one
character set in common.
==========================================================
Mark Leighton Fisher          Thomson Consumer Electronics
fisherm@indy.tce.com          Indianapolis, IN
"Browser Torture Specialist, First Class"