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

Re: Content-Disposition (new issue?)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 20 Jun 2008 13:42:19 +0200
Message-ID: <485B979B.2010900@gmx.de>
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
CC: ietf-http-wg@w3.org

Frank Ellermann wrote:
> ...
>> 3b) Support 
> * <http://greenbytes.de/tech/webdav/rfc2231.html#rfc.section.4>,
>> but only use UTF-8 encoding in producers.
> 
> -1  Tiny mazes, all different... :-(  The us-ascii example is
>     perfect, and if 2616bis sticks to its iso-8859-1 "default"
>     this relic and its more popular windows-1252 incarnation are
>     also plausible.  I can see a "strongly RECOMMENDED", but no
>     MUST utf-8 here, and "default" iso-8859-1 there, and a big
>     mess everywhere.   
> ...

Well, we need one encoding that can represent all Unicode code points, 
and UTF-8 comes to mind for that. Support for RFC2231 in UAs would be 
totally pointless if we couldn't require recipients to understand it. So 
why produce anything else?

BR, Julian
Received on Friday, 20 June 2008 11:43:00 GMT

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