#1106 epub: Invalid XHTML for "intentionally left blank" comment

output: ePub
open
XSL (1066)
5
2011-08-28
2010-04-12
No

In xhtml-1_1/table.xsl, the following section in <xsl:template match="row"> produces invalid XHTML (line 523):

<tr><xsl:comment> This row intentionally left blank </xsl:comment></tr>

Instead, there should be something like the following:

<xsl:choose>
<xsl:when test="ancestor::thead">
<tr><th/><xsl:comment> This row intentionally left blank </xsl:comment></tr>
</xsl:when>
<xsl:otherwise>
<tr><td/><xsl:comment> This row intentionally left blank </xsl:comment></tr>
</xsl:otherwise>
</xsl:choose>

Discussion

  • Keith Fahlgren

    Keith Fahlgren - 2010-04-12

    Would you please provide a short snippet of DocBook content that will reproduce this validation error? With that, I'll try to reproduce it and add it to the regression suite.

     
  • Keith Fahlgren

    Keith Fahlgren - 2010-04-12
    • labels: 1168228 --> XSL
     
  • Sanders Kleinfeld

    Hi Keith,

    Sure thing. A snippet of <table> markup is attached. This is actually kind of a bad example, in that the bogus @cols attribute of 0 on the table triggers the "intentionally left blank" comment. But that's the only "in the wild" sample I had.

    Anyway, the "intentionally left blank" comment is invalid XHTML (the <tr> needs a <td> or <th>), which throws the following validity error:

    ERROR: /work/spaces/sanders/ajax_on_rails/current/book.xml.epub/OEBPS/ch05s02.html(43): unfinished element

    Let me know if you need more info,
    Sanders

    > Would you please provide a short snippet of DocBook content that will
    > reproduce this validation error? With that, I'll try to reproduce it and
    > add it to the regression suite.

     
  • Mauritz Jeanson

    Mauritz Jeanson - 2011-08-28
    • summary: Invalid XHTML for "intentionally left blank" comment --> epub: Invalid XHTML for "intentionally left blank" comment
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks