Re: Using UTF-8 for non-ASCII Characters in URLs

Michael Kung (MKUNG@us.oracle.com)
30 Apr 97 17:06:29 -0700


Message-Id: <199705010017.RAA27111@mailsun3-fddi.us.oracle.com>
Date: 30 Apr 97 17:06:29 -0700
From: "Michael Kung <MKUNG.US.ORACLE.COM>" <MKUNG@us.oracle.com>
To: owner-uri@bunyip.com
Subject: Re: Using UTF-8 for non-ASCII Characters in URLs
Cc: uri@bunyip.com


--=_ORCL_10648021_0_11919704301826100
Content-Transfer-Encoding:quoted-printable
Content-Type:text/plain; charset="iso-8859-1"

Agree on the 'key words'.  But this rule also implies that I cannot put any 
=
double byte English Alphabet in my company name (or I have to change my 
company name for URL). 
 
Regards, 
 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++=
 
Michael Kung					 
40P-972                                         Phone:      (415) 506-6954 
Manager, Server Globalization Technology	Fax:        (415) 506-7225 
Languages and Relational Technology		Email: mkung@us.oracle.com 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

--=_ORCL_10648021_0_11919704301826100
Content-Type:message/rfc822

Date: 29 Apr 97 21:09:42
From:"Larry Masinter <masinter@parc.xerox.com>" <owner-uri@Bunyip.Com>
To:Michael,Kung,<MKUNG.US.ORACLE.COM>,<MKUNG@us.oracle.com>
Subject:Re: Using UTF-8 for non-ASCII Characters in URLs
Cc:uri@Bunyip.Com
Organization:Xerox PARC
X-Mailer:Mozilla 3.01Gold (Win95; I)
References:<199704292148.OAA04694@mailsun2.us.oracle.com>

Sender:owner-uri@Bunyip.Com
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding:7bit
Content-Type:text/plain; charset="us-ascii"

This isn't just a "small point", it's essential:

The only way to guarantee "round trip" is to stick to the smallest
repertoire of characters. Clearly you shouldn't enter "http" as
wide characters, and if you have 'wide characters' that need
to be distinguished from ascii characters, you should encode them
in hex-encoded-UTF8 always.

--=_ORCL_10648021_0_11919704301826100--