# Re: http charset labelling

Gavin Nicol (gtn@ebt.com)
Fri, 2 Feb 1996 09:28:25 -0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Ronald E. Daniel: "Re: Archive of uri@bunyip.com?"
- Previous message: Masataka Ohta: "Re: http charset labelling"
- In reply to: Masataka Ohta: "Re: http charset labelling"
- Next in thread: Masataka Ohta: "Re: http charset labelling"
- Reply: Masataka Ohta: "Re: http charset labelling"

    Date: Fri, 2 Feb 1996 09:28:25 -0500

    From: Gavin Nicol <gtn@ebt.com>

    Message-Id: <199602021428.JAA02019@ebt-inc.ebt.com>

    To: mohta@necom830.cc.titech.ac.jp

    In-Reply-To: <199602020655.PAA17951@necom830.cc.titech.ac.jp> (message from Masataka Ohta on Fri, 2 Feb 96 15:55:35 JST)

    Subject: Re: http charset labelling

>So, the available choices of representation on our namecards are:
>
> 1) pure ASCII
> 2) a few % notations embedded in ASCII
> 3) a lot of % notations
> 4) MIME QP with charset labelling
>
>Obviously, 1) is the best both for recognizing and for typing in.

The only problem is that people *expect* to be able to use whatever
encoding they like in URL's. If you look at some of the magazines
in Japan with articles on creating WWW sites. Many of them have URL's
that contain Kanji. If you look even closer, you can see than browsers
display this as junk.

- Next message: Ronald E. Daniel: "Re: Archive of uri@bunyip.com?"
- Previous message: Masataka Ohta: "Re: http charset labelling"
- In reply to: Masataka Ohta: "Re: http charset labelling"
- Next in thread: Masataka Ohta: "Re: http charset labelling"
- Reply: Masataka Ohta: "Re: http charset labelling"