W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 1996

Re: Accept-Charset support

From: Chris Lilley <Chris.Lilley@sophia.inria.fr>
Date: Wed, 18 Dec 1996 01:21:58 +0100 (MET)
Message-Id: <9612180121.ZM7371@grommit.inria.fr>
To: Keld J|rn Simonsen <keld@dkuug.dk>, Klaus Weide <kweide@tezcat.com>, www-international@w3.org
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2101
On Dec 18, 12:03am, Keld J|rn Simonsen wrote:

[in amongst generally good stuff ]

> Of cause it complicates matters
> with yet another parameter, but it could help in chosing an
> appropiate font, and then it is the right concept.

Sequences of bytes, sequences of characters, and sequences of glyphs
are not the same thing. The charset does not, necessarily, map 1:1 to
the font encoding vector. The characters might not even be displayed
visually - they might be spoken for example.

> I note that a MIME charset identifies a repertoire,

Not necessarily. It identifies a mapping from  (one or more)
bytes to characters. In the particular case of HTML it does not identify
a repertoire at all. It is possible to write a document that contains the
entire character repertoire of 10646, and have it correctly labelled as
US-ASCII - just using numeric character references.

Chris Lilley, W3C                          [ http://www.w3.org/ ]
Graphics and Fonts Guy            The World Wide Web Consortium
http://www.w3.org/people/chris/              INRIA,  Projet W3C
chris@w3.org                       2004 Rt des Lucioles / BP 93
+33 (0)4 93 65 79 87       06902 Sophia Antipolis Cedex, France
Received on Wednesday, 18 December 1996 00:09:49 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:00 UTC