W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2008

Re: PROPOSAL: i74: Encoding for non-ASCII headers

From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Fri, 28 Mar 2008 12:40:06 +0100
To: ietf-http-wg@w3.org
Message-ID: <fsin5d$ut7$1@ger.gmane.org>

Jamie Lokier wrote:

> An issue I have with RFC2047 is it seems to imply every "proper"
> implementation of a HTTP reciever, which does something with received
> TEXT (such as display it), needs to have a _large_ table of known
> character set names and conversion routines.

No, by design MIME works if the other side has no clue what it is.

It would then see gibberish like =?us-ascii*en-GB?Q?hello_world?=
and don't know that this an odd way to say "hello world".  It is
not forced to know what "encoded words" are, and if it knows this
it is not forced to support each and every charset.
 
> may I suggest that it be recommended to _only_ designate the 
> "utf-8", "iso-8859-1" and "us-ascii" character set in RFC2047
> encodings in HTTP?

It's an idea, but I think we're not forced to explicitly say this.

If some communities use koi8-r or some older charset popular in
JP this is the same issue as in ordinary Web browsers or e-mail:

I cannot read Cyrl or Jpan scripts, it is irrelevant from my POV
how that is encoded.  

 Frank
Received on Friday, 28 March 2008 12:10:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:37 GMT