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

Re: text/* types and charset defaults [i20]

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 22 Jan 2008 13:39:00 +0100
Message-ID: <4795E3E4.3030506@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: 'HTTP Working Group' <ietf-http-wg@w3.org>

Mark Nottingham wrote:
> If it does, that can be a separate issue (this text is lifted directly
>> from 2616).

+1

>> So my proposal would be:
>>
>> - drop paragraph 4 (ISO-8859-1),
>>
>> - add a note covering Larry's points 1) and 2), and
>>
>> - mention this is a normative change in 
>> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p3-payload-01.html#changes.from.rfc.2616>. 
>>
> 
> 
> To be clear, we're talking about removing 
> <http://tools.ietf.org/id/draft-ietf-httpbis-p3-payload-01.txt>, section 
> 2.3.1, the entire forth paragraph (i.e., the last one in that section). 
> This includes removing both the defaulting and the MUST-level 
> requirement for labeling text/* in a charset other than ISO-8859-1.

Right.

> What should happen to section 2.1.1? Given the changes above, the only 
> still-relevant part of it seems to be:
>> HTTP/1.1 recipients MUST respect the charset label provided by the 
>> sender; and those user agents that have a provision to "guess" a 
>> charset MUST use the charset from the content-type field if they 
>> support that charset, rather than the recipient's preference, when 
>> initially displaying a document.
> The most straightforward thing to do may be to extract the text above 
> and put it at the end of 2.3.1, removing the rest of 2.1.1.

Sounds good to me.

BR, Julian
Received on Tuesday, 22 January 2008 12:39:28 GMT

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