[Bug 13392] i18n-ISSUE-72: BOM as preferred encoding declaration


--- Comment #6 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-07-28 11:59:27 UTC ---
Unless I misremember, Polyglot Markup already points to a I18N text that
reccommends a visible enc decl. So that issue should be covered. 

To not include the BOM means that a HTTP charset from the server can override
the (undeclared) UTF-8 encoding without there being a fatal error in the XML
parser. That's a bad thing. But when BOM is present, this mislabeled HTTP
charset header can be discovered both in XML parsers (which should get fatal
error) and in HTML5 parsers (which should land in quirksmode).

That some tools do not handle BOM properly, is a problem with those tools.
Without more explatation, I fail to see that it is relevant.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug.

Received on Thursday, 28 July 2011 11:59:29 UTC