# Re: http charset labelling

Gavin Nicol (gtn@ebt.com)
Sun, 18 Feb 1996 20:01:09 -0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Paul Francis: "Ingrid ready for initial testing..."
- 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: Sun, 18 Feb 1996 20:01:09 -0500

    From: Gavin Nicol <gtn@ebt.com>

    Message-Id: <199602190101.UAA09669@ebt-inc.ebt.com>

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

    In-Reply-To: <199602160930.SAA17385@necom830.cc.titech.ac.jp> (message from Masataka Ohta on Fri, 16 Feb 96 18:30:24 JST)

    Subject: Re: http charset labelling

>> To me it means that the URL is hidden and can be anything so it
>> does not matter then if it is encoded in a special charset or not.
>
>On browsers, yes, it is hidden. So, it is meaningless to use
>a special charset.

The point is that if I receive a URL, by whatever means, and then I
type it into the "go to" field of any browser, then when it is sent to
the server, the server has no idea what encoding is being used.

The actual indication of the encoding should be hidden from the user,
but it is still important for it to be there, because even for ASCII
names, maybe the user entered it in zenkaku.

- Next message: Paul Francis: "Ingrid ready for initial testing..."
- 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"