11055 2010-10-14 21:04:17 +0000 BOM confusion 2011-08-04 05:07:30 +0000 1 1 1 Unclassified HTML WG LC1 HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 davidc eliotgra eliotgra mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 41383 0 davidc 2010-10-14 21:04:17 +0000 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). 41849 1 eliotgra 2010-10-29 20:36:06 +0000 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 53151 2 mike 2011-08-04 05:07:06 +0000 mass-move component to LC1 53193 3 mike 2011-08-04 05:07:30 +0000 mass-move component to LC1