Re: http charset labelling

Gavin Nicol (gtn@ebt.com)
Fri, 9 Feb 1996 16:19:01 -0500


Date: Fri, 9 Feb 1996 16:19:01 -0500
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

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