Re: http charset labelling
Gavin Nicol <gtn@ebt.com> Fri, 09 February 1996 22:09 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa28152; 9 Feb 96 17:09 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa28148; 9 Feb 96 17:09 EST
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa15221; 9 Feb 96 17:09 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id QAA11260 for uri-out; Fri, 9 Feb 1996 16:21:19 -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 QAA11253 for <uri@services.bunyip.com>; Fri, 9 Feb 1996 16:21:06 -0500
Received: from ebt-inc.ebt.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA28782 (mail destined for uri@services.bunyip.com); Fri, 9 Feb 96 16:21:03 -0500
Received: (from gtn@localhost) by ebt-inc.ebt.com (8.6.12/8.6.9) id QAA04343; Fri, 9 Feb 1996 16:19:01 -0500
Date: Fri, 09 Feb 1996 16:19:01 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Gavin Nicol <gtn@ebt.com>
Message-Id: <199602092119.QAA04343@ebt-inc.ebt.com>
To: mohta@necom830.cc.titech.ac.jp
Cc: masinter@parc.xerox.com, keld@dkuug.dk, uri@bunyip.com
In-Reply-To: <199602090116.KAA25128@necom830.cc.titech.ac.jp> (message from Masataka Ohta on Fri, 9 Feb 96 10:16:15 JST)
Subject: Re: http charset labelling
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk
>> Nor should there be. People map from a glyph to a *character*, which >> is quite different to a character code. I have enough trouble mapping >> some glyphs to characters. > >Then, why do you think you can force people to perform the >troublesome mapping? I'm not proposing to force anyone to do anything, but rather, simply give them a choice. You *are* trying to force people to use a non-natural representation. >> If anyone speaks to you in anything other than English, reject the >> sentence. Quite an appealing idea. > >Sigh... You don't even understand the difference between English and >ASCII. > >My mail address is in ASCII but NOT English, though non-ASCII mail >addresses are rejected all around the Internet. I was simply paraphrasing your sentence. If you understood the nuances of English, you would have understood that I find limiting URL's to ASCII to be a sensible as limiting the worlds languages to English.
- 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