Re: Can HTTP content-type charset disagree with its contents XML encoding?

On Wednesday, April 30, 2003, 1:58:55 AM, Bjoern wrote:

BH> * Chris Lilley wrote:
>>It is in that specification that the precedence is defined (and other
>>unfortunate things, such as a mandatory default of US-ASCII when no
>>charset is provided in the HTTP, regardless of what the XML encoding
>>declaration says).
>>
>>This is very bad. As a member of the TAG I find this very broken,
>>architecturally speaking. Tim Bray agrees, and I have proposed wording
>>in the architecture document that spells this out.

BH> Many (if not most) XML processor toolkits don't even implement the
BH> US-ASCII default for text/plain...

This is also true.

And if someone is handling an xml media type as text/plain, then
encoding is the least of their worries.

-- 
 Chris                            mailto:chris@w3.org