# Re: http charset labelling

Keld J|rn Simonsen (keld@dkuug.dk)
Wed, 14 Feb 1996 16:48:23 +0100

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Larry Masinter: "Re: Bracketed URLs"
- Previous message: Masataka Ohta: "Re: http charset labelling"
- Next in thread: Masataka Ohta: "Re: http charset labelling"
- Reply: Masataka Ohta: "Re: http charset labelling"
- Reply: Masataka Ohta: "Re: http charset labelling"

    Message-Id: <199602141548.QAA24621@dkuug.dk>

    From: keld@dkuug.dk (Keld J|rn Simonsen)

    Date: Wed, 14 Feb 1996 16:48:23 +0100

    In-Reply-To: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>

    To: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>, dupuy@cs.columbia.edu

    Subject: Re: http charset labelling

Masataka Ohta writes:

> Thank you Alex for the summary.
>
> > There have been a few proposals for dealing with code
> > mapping; I'm not totally convinced that they all of them will work well in
> > practice with existing browsers that are unaware of character codes.
>
> With browsers, URL can be labelled by any text or picture.
>
> So, code mapping proposal which is proven not to work on paper is,
> IMHO, almost useless. Maybe, URLs in e-mail are rare exceptions.

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.
And as the likelihood of the html doc using URLs adressing
the same server as the one sending out the html doc is very big,
the problem of old servers and old clients using nonstandard
encodings should not be big.

keld

- Next message: Larry Masinter: "Re: Bracketed URLs"
- Previous message: Masataka Ohta: "Re: http charset labelling"
- Next in thread: Masataka Ohta: "Re: http charset labelling"
- Reply: Masataka Ohta: "Re: http charset labelling"
- Reply: Masataka Ohta: "Re: http charset labelling"