- From: <bugzilla@jessica.w3.org>
- Date: Sat, 05 Mar 2011 00:49:47 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12062 Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #11 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-03-05 00:49:46 UTC --- (In reply to comment #10) > I made the changes and published the updated version. Thanks. > Anything else? ;-) Yes, of course. ;-) 1) I noticed that HTML5 uses the phrase "Byte Order Character character". Also, HTML5 - and all other specs that talk about the BOM - usually introduces it with its un-abbeviated name before it introduces the BOM-abbreviation. Currently, the Polyglot Markup draft does not explain what BOM means. Therefore I suggest to a) say "Byte Order Mark (BOM) character" the first time that the Polyglot spec refers to the BOM: ]] When polyglot markup uses UTF-16, it must include the Byte Order Mark (BOM) character[[ b) when possible, try to add the word "character" after each occurrence of 'BOM' or 'Byte Order Mark' 2) After the sentence 'When polyglot markup uses UTF-16 [snip]", then please add this sentence: ]] The BOM character can also be used with the UTF-8 encoding. [[ 2) Add this comment at the end of/after the paragraph which begins 'Using <meta charset="*"/> has no effect in XML.": ]] The BOM character can be said to be the most polyglot encoding declaration: Unlike the encoding declaration inside the HTTP Content-Type header, it isn't part of a construct that differs for XML and HTML. And unlike the <meta charset="UTF-8"/> declaration of HTML and the UTF-8 encoding default of XML, the BOM character works in both XML and HTML.[[ Somewhere you could also add a link to HTML5's permission to use the BOM character: http://dev.w3.org/html5/spec/syntax.html#writing Good weekend. ;-) -- 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 Saturday, 5 March 2011 00:49:48 UTC