Re: Can HTTP content-type charset disagree with its contents XML encoding? from Bjoern Hoehrmann on 2003-04-29 (www-international@w3.org from April to June 2003)

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 30 Apr 2003 01:58:55 +0200
To: Chris Lilley <chris@w3.org>
Cc: www-international@w3.org
Message-ID: <3ee51138.470107719@smtp.bjoern.hoehrmann.de>

* 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.

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

Received on Tuesday, 29 April 2003 19:59:10 UTC