- From: <bugzilla@jessica.w3.org>
- Date: Sun, 14 Aug 2011 12:06:03 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13771 --- Comment #6 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-08-14 12:06:02 UTC --- (In reply to comment #5) That page does not mention XML. For HTML, the concept of 'fatal error' doesn't exist. As such, when the charset doesn't match, one must follow a different strategy from that of XML. And Win-1252 make some sense, because this will also for the most part avoid questions marks for unmappable characters - et cetera. However, there is no guarantee that a "US-ASCII" labelled page actually is Win-1252 encoded. For example, it could just as well be UTF-8 encoded. It could even be US-ASCII encoded ... Btw, I forgot to quote this, as part of the justification for this bug: ]] It is a fatal error if an XML entity is determined (via default, encoding declaration, or higher-level protocol) to be in a certain encoding but contains byte sequences that are not legal in that encoding. [[ -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Sunday, 14 August 2011 12:06:04 UTC