[Bug 29345] New: Failure to close empty elements makes use of XML-based tools for proofing overly difficult - Serialization

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29345

            Bug ID: 29345
           Summary: Failure to close empty elements makes use of XML-based
                    tools for proofing overly difficult - Serialization
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Serialization 3.1
          Assignee: cmsmcq@blackmesatech.com
          Reporter: patrick@durusau.net
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

>From XSLT and XQuery Serialization

[FODC0002] "file:/home/patrick/working/w3c/XSLT-XQuery-Serialization3.1.html"
(Line 75): The element type "link" must be terminated by the matching end-tag
"</link>".

[FODC0002] "file:/home/patrick/working/w3c/XSLT-XQuery-Serialization3.1.html"
(Line 75): The element type "meta" must be terminated by the matching end-tag
"</meta>".

2 non-closed <meta> elements

[FODC0002] "file:/home/patrick/working/w3c/XSLT-XQuery-Serialization3.1.html"
(Line 76): The element type "img" must be terminated by the matching end-tag
"</img>".

1 non-closed <img> element

[FODC0002] "file:/home/patrick/working/w3c/XSLT-XQuery-Serialization3.1.html"
(Line 86): The element type "br" must be terminated by the matching end-tag
"</br>".

138 non-closed <br> elements

[FODC0002] "file:/home/patrick/working/w3c/XSLT-XQuery-Serialization3.1.html"
(Line 809): The end-tag for element type "col" must end with a '>' delimiter.

4 non-closed <col> elements

[FODC0002] "file:/home/patrick/working/w3c/XSLT-XQuery-Serialization3.1.html"
(Line 5099): The element type "hr" must be terminated by the matching end-tag
"</hr>".

2 non-closed <hr> elements

I make that to be 148 edits that must be made to use XML based tools on the
most recent XSLT and XPath Serialization 3.1 Candidate draft.

I realize this is a production error but it is one that significantly impacts
the review of this draft.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 17 December 2015 20:09:36 UTC