- From: <bugzilla@jessica.w3.org>
- Date: Thu, 14 Oct 2010 21:04:18 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11055 Summary: BOM confusion Product: HTML WG Version: unspecified Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) AssignedTo: eliotgra@microsoft.com ReportedBy: davidc@nag.co.uk QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org, eliotgra@microsoft.com section 3 of http://dev.w3.org/html5/html-xhtml-author-guide/WD-html-polyglot-20101019.htm When polyglot markup uses UTF-16, it must not include a BOM. When polyglot markup uses UTF-16, it must include the BOM I assume the first UTF=16 was intended to say UTF-8 It goes on to say Therefore, polyglot markup may use <meta charset="*"/> in combination with BOM, If there is a BOM, then this would be some flavour of UTF-16 but that would be invalid HTML5 according to the current draft http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#attr-meta-charset says If the attribute is present in an XML document, its value must be an ASCII case-insensitive match for the string "UTF-8" (and the document is therefore forced to use UTF-8 as its 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 Thursday, 14 October 2010 21:04:19 UTC