Re: http charset labelling

Masataka Ohta (mohta@necom830.cc.titech.ac.jp)
Tue, 6 Feb 96 11:12:57 JST


From: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>
Message-Id: <199602060213.LAA15162@necom830.cc.titech.ac.jp>
Subject: Re: http charset labelling
To: gtn@ebt.com (Gavin Nicol)
Date: Tue, 6 Feb 96 11:12:57 JST
Cc: masinter@parc.xerox.com, keld@dkuug.dk, uri@bunyip.com
In-Reply-To: <199602051710.MAA09220@ebt-inc.ebt.com>; from "Gavin Nicol" at Feb 5, 96 12:10 pm

> >Then, all we can do for them is to write an informational, or BCP,
> >RFC on why localized URL can't be used for internationalization.
>  
> Or fix the problem by allowing specification of the encoding used for
> the URL's.

That's no fix.

If you allow specification of the encoding, what we can see on paper
is resulting lengthy specification of the encoding concatenated with
lengthy 7bit encoding of the URL body.

> Yes, there is an Internet directory put out by Gakken (I forget the
> name) that had such an article last month.

Then, Gakken should be wrong. Or, you may be confusing URL and
text content.

								Masataka Ohta