11905 2011-01-28 12:04:35 +0000 Escaping of "<" and "&" in Polyglot Markup 2011-08-04 05:07:44 +0000 1 1 1 Unclassified HTML WG LC1 HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) unspecified PC All CLOSED FIXED http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html P2 major --- 1 xn--mlform-iua eliotgra davidc eliotgra mike public-html-admin public-html-wg-issue-tracking shadow2531 xn--mlform-iua public-html-bugzilla oldest_to_newest 44827 0 xn--mlform-iua 2011-01-28 12:04:35 +0000 It is a well-formed requirement in XML 1.0 that "<" and "&" are escaped whenever they are not used in entities or in tags or occur inside CDATA sections. In contrast, in HTML, the "&" in general does not need to be escaped. Whereas the "<" does not need escaping inside attributes. Exact XML rules: http://www.w3.org/TR/REC-xml/#syntax Conclusion: State that "<" and "&", when used as character, always needs to be escaped, except when inside CDATA. (You may also want to see Bug 11904.) 44828 1 davidc 2011-01-28 12:19:46 +0000 (In reply to comment #0) > Conclusion: State that "<" and "&", when used as character, always needs to be > escaped, except when inside CDATA. I don't think this document should try to explain the requirements of being xml well formed (or of being html valid) If it states such rules in full, it becomes vastly larger and if just summarizes them it will get details wrong in edge cases. I think the document should just state the _additional_ constraints that need to be met given a document that is xml well formed and html valid, for it to give equivalent DOM trees whether parsed as xml or html. David 44843 2 xn--mlform-iua 2011-01-28 16:43:45 +0000 (In reply to comment #1) > I don't think this document should try to explain the requirements of being xml > well formed (or of being html valid) If it states such rules in full, it > becomes vastly larger and if just summarizes them it will get details wrong in > edge cases. > > I think the document should just state the _additional_ constraints that need > to be met given a document that is xml well formed and html valid, for it to > give equivalent DOM trees whether parsed as xml or html. Then perhaps you should look at what Polyglot Markup already says, right now, and file bugs if you think it says too much already? Are there things that it should take out? I must say that it becomes - to myself - illogicall if the document goes into the nittygritty of how to make sure that attributes are kept DOM equal (by taking into consideration XML whitespace normalization in attributes) on one side, but on the other side ignores to say the farm more important thing that "<" and "&" have to be escaped. I think that for most authors that want to use polyglot markup, the DOM equality of attributes, is not of very great importance. However, I do think that it would be nice if Polyglot Markup summed up its principles in one section of the document, including pointing to the definining specs (XML 1.0 and HTML5) for its principles. You did not comment on bug 11904 regarding <plaintext> and <xmp>. That Polyglot Markup gives special (but incorrect) rules for how to use <>& inside those elements, is an example - IMHO - on what happens because the entire Polyglot Markup document is lacking a) guiding principles and b) looks at the details instead of listing the general rules. In my view, the need to escape < and & is - by the way - so basic, that we do no need to land in the error of failing ot be accurate enough just because we say it. 45427 3 eliotgra 2011-02-12 00:46:43 +0000 In the Editor's Draft of 11 February 2011, I have added the following content to section 8. Named Entity References: ]] Polyglot markup always uses character references for the less than sign (<) and ampersand (&) when they are used as characters, except when those characters appear inside a CDATA section. [[ Thanks very much for this feedback. Cheers, Eliot 45454 4 xn--mlform-iua 2011-02-13 19:36:04 +0000 Satisfied. Closing. 53185 5 mike 2011-08-04 05:07:24 +0000 mass-move component to LC1 53213 6 mike 2011-08-04 05:07:44 +0000 mass-move component to LC1