Re: Using UTF-8 for non-ASCII Characters in URLs from Michael Kung <MKUNG.US.ORACLE.COM> on 1997-05-01 (uri@w3.org from April 1997)

From: Michael Kung <MKUNG.US.ORACLE.COM> <MKUNG@us.oracle.com>
Date: 30 Apr 97 17:06:29 -0700
To: owner-uri@bunyip.com
Cc: uri@bunyip.com
Message-Id: <199705010017.RAA27111@mailsun3-fddi.us.oracle.com>

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 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Forwarded message 1

From: Larry Masinter <masinter@parc.xerox.com> <masinter@parc.xerox.com>
Date: 29 Apr 97 21:09:42
Subject: e: Using UTF-8 for non-ASCII Characters in URLs
To: ichael,Kung,<MKUNG.US.ORACLE.COM>,<MKUNG@us.oracle.com>
Cc: ri@Bunyip.Com

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.

Received on Wednesday, 30 April 1997 20:18:50 UTC