If a table has rowsep=1 (default), then when an entry
has @morerows attribute such that it occupies also the
remaining rows (i.e., a vertical span to the bottom of the
table), it will have rowsep=1 (internally), so it will be
drawn a rowsep line below this entry (if
$table.borders.with.css=1).
This contradicts the DocBook specs, which says that
the lines after the last rows/columns are to be controlled
with the @frame attribute of the table.
This bug can be easily eliminated, see attached diff file
on xhtml/table.xsl of the docbook-xsl-1.68.1 distribution.
Also attached the example xml and output xhtml files,
and an xsl file (to be put in the xhtml dir; this only
imports docbook.xsl and sets table.border.with.css=1).
Example test xml
Example output
docbook xsl with table.borders.with.css=1
diff on xhtml/table.xsl (3 more lines to $rowsep of entry match)
Logged In: YES
user_id=1244561
it seems that it's not only an (x)html output problem, so
changed the group spec.
Logged In: YES
user_id=193218
A fix for this issue has been added to the current codebase.
Please test the fix with the latest snapshot from:
http://docbook.sourceforge.net/snapshots/
Logged In: YES
user_id=1244561
Since I didn't found any changes regarding this issue in the
codebase snapshot (nor in xhtml/table.xsl either in
html/table.xsl) - assuming a fault in the fixing workflow or just
an erroneous entry by bob - I reopened this issue.
Logged In: YES
user_id=193218
Ack, my CVS checkin didn't make it. It is checked in now,
and the patch is in the latest XSL snapshot version. I'll leave
it at Pending until I hear that is working.
Logged In: YES
user_id=1244561
Checked and it seems that it's working (hopefully with no
side-effect - actually tested the patch before). Thank you!