Re: http charset labelling

Keld J|rn Simonsen <keld@dkuug.dk> Wed, 14 February 1996 17:01 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18019; 14 Feb 96 12:01 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18014; 14 Feb 96 12:01 EST
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa10105; 14 Feb 96 12:01 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id KAA02640 for uri-out; Wed, 14 Feb 1996 10:49:00 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id KAA02633 for <uri@services.bunyip.com>; Wed, 14 Feb 1996 10:48:57 -0500
Received: from dkuug.dk by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA01121 (mail destined for uri@services.bunyip.com); Wed, 14 Feb 96 10:48:52 -0500
Received: (from keld@localhost) by dkuug.dk (8.6.12/8.6.12) id QAA24621; Wed, 14 Feb 1996 16:48:24 +0100
Message-Id: <199602141548.QAA24621@dkuug.dk>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Keld J|rn Simonsen <keld@dkuug.dk>
Date: Wed, 14 Feb 1996 16:48:23 +0100
In-Reply-To: Masataka Ohta <mohta@necom830.cc.titech.ac.jp> "Re: http charset labelling" (Feb 14, 10:48)
X-Charset: ISO-8859-1
X-Char-Esc: 29
Mime-Version: 1.0
Content-Type: Text/Plain; Charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Mnemonic-Intro: 29
X-Mailer: Mail User's Shell (7.2.2 4/12/91)
To: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>, dupuy@cs.columbia.edu
Subject: Re: http charset labelling
Cc: gtn@ebt.com, uri@bunyip.com
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk

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