This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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).
In the 29 October editor's draft, I changed the relevant part of section 3 to the following: Using <meta charset="*"/> has no effect in XML. Therefore, polyglot markup may use <meta charset="*"/> provided the document is encoded as UTF-8 and the value of charset is a case-insensitive match for the string utf-8. And fixed that typo. I believe that satisfies the requests in this bug. Thanks for the feedback! Eliot
mass-move component to LC1