Re: http charset labelling
Masataka Ohta <mohta@necom830.cc.titech.ac.jp> Wed, 07 February 1996 03:57 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03701; 6 Feb 96 22:57 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03697; 6 Feb 96 22:57 EST
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa19058; 6 Feb 96 22:57 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id WAA17485 for uri-out; Tue, 6 Feb 1996 22:35:34 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id WAA17477 for <uri@services.bunyip.com>; Tue, 6 Feb 1996 22:35:31 -0500
Received: from necom830.cc.titech.ac.jp by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA06689 (mail destined for uri@services.bunyip.com); Tue, 6 Feb 96 22:35:21 -0500
Received: by necom830.cc.titech.ac.jp (8.6.11/necom-mx-rg); Wed, 7 Feb 1996 12:20:08 +0900
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>
Message-Id: <199602070320.MAA18632@necom830.cc.titech.ac.jp>
Subject: Re: http charset labelling
To: Gavin Nicol <gtn@ebt.com>
Date: Wed, 07 Feb 1996 12:20:06 -0000
Cc: masinter@parc.xerox.com, keld@dkuug.dk, uri@bunyip.com
In-Reply-To: <199602061504.KAA13675@ebt-inc.ebt.com>; from "Gavin Nicol" at Feb 6, 96 10:04 am
X-Mailer: ELM [version 2.3 PL11]
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk
> I guess you, I, and a lot of other people, think that if people really > want to be global, they should avoid using kanji, or whatever, in > URL's. However, as a persoan at Astec said, and I agree, people *will* > put kanji into resource names, and they *will* expect it to work. As > such, I think it better to design a system that can handle *all* > cases, as users expect them to be handled. Just make viewers bounce any URL with the 8th bit set or, at least, mask the bit. '%' notation should still be accepted. It is also a good idea to do the same thing at the protocol specification level that: 8th bit of URL MUST be 0. Should a malformed URL is found, its 8th bit MAY be masked to be 0. Otherwise the URL MUST be rejected. Then, non-ASCII URLs will disappear. You can see that no people are using mail address with kanji, which is why we can communicate internationally. Masataka Ohta
- Re: URN to URC resolution scenario Mitra
- Re: Library Standards and URIs Terry Allen
- Re: Library Standards and URIs Terry Allen
- Re: URC formats vs interfaces Ronald E. Daniel
- URC formats vs interfaces Daniel LaLiberte
- no child-of-URI groups at Dallas IETF? Larry Masinter
- Re: no child-of-URI groups at Dallas IETF? Ronald E. Daniel
- Re: html, http, urls and internationalisation Keld J|rn Simonsen
- Re: http charset labelling Larry Masinter
- Re: http charset labelling Keld J|rn Simonsen
- Re: http charset labelling Keld J|rn Simonsen
- Re: http charset labelling Larry Masinter
- Re: http charset labelling Keld J|rn Simonsen
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Gavin Nicol
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Gavin Nicol
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Gavin Nicol
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Gavin Nicol
- Re: http charset labelling Gavin Nicol
- Re: http charset labelling Masataka Ohta
- Re: http charset labelling Gavin Nicol
- Re: 8 bit characters in DNS names (and URNs?) Keld J|rn Simonsen
- Re: Typeable characters Keld J|rn Simonsen
- Re: UTF-8 and URLs Keld J|rn Simonsen