W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1994

Re: character sets in HTTP: translation tables

From: Simon E Spero <ses@tipper.oit.unc.edu>
Date: Thu, 29 Dec 94 17:12:00 -0500
Message-Id: <9412292212.AA04211@tipper.oit.unc.edu>
To: Chuck Shotton <cshotton@oac.hsc.uth.tmc.edu>
Cc: Gavin Nicol <gtn@ebt.com>, masinter@parc.xerox.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, www@unicode.org
There are several places where character set issues do impact the design of 
HTTP; One example of this is in human readable meta data such as titles and
author names. HTTP-NG defines all human readable headers to be variable length
strings of bytes - I've argued for making all such text be UTF-* encoded 
UCS-2 or UCS-4. 

You're right in that the bitstream sent over the data channels is not
an HTTP issue; however, using UCS-* as the preferred charset for HTML would
probably be a really good idea.

Received on Thursday, 29 December 1994 14:14:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:16:10 UTC