- From: <bugzilla@jessica.w3.org>
- Date: Thu, 05 Jul 2012 12:59:55 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15359 --- Comment #8 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2012-07-05 12:59:55 UTC --- (In reply to comment #7) > (In reply to comment #6) > Appendix F.1 first - in the first table - discusses how to sniff the encoding > when there is a BOM. This is simple: Ifone parses an XML document which > _contains_ the BOM as something other than UTF-16, UTF-8 or UTF-32 (UCS-4), > then the BOM is not a BOM but an illegal character = fatal error. By the way: In that case it is an illegal character per HTML5 as well: A UTF-8 document with a BOM would be would bring the browser into Quirks-Mode if the browser reads the document as - for example - ISO-8859-1. So even if we look squarely at HTML5, it makes no sense to permit the encoding to be overridden whenever there is a BOM: To permit the encoding to be overridden when there is a BOM would be like permitting users to shoot themselves in the foot. PS: I now consider this subject to be debated to death. I am not going to give any more explanations. And if I give any more replies, then they will be short and to the point. -- Configure bugmail: https://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 Thursday, 5 July 2012 12:59:57 UTC