On Feb 4, 2008, at 18:03, Puppala, Kumar (LNG-CON) wrote:
Hi
Thanks for the quick reply. I tried both the suggestions and am
still having issues. Listed below are my findings:
What if you add two empty cells, or simply leave out the empty row?
If I add two empty cells, the renderer complains that the number of
cells in the row overflows. The error message is as shown below:
“org.apache.fop.fo.ValidationException: Error(67/15): column-number
or number of cells in the row overflows the number of fo:table-
column specified for the table.”
OK. This still seems understandable to me, although it does not help
your case, but...
If I leave out the entire row, I see different results between fop
0.94 and fopTrunk. In fop 0.94, it renders but the borders on the
top for the two cells are missing (attaching the pdf doc). However,
in fopTrunk, I get the following validation exception:
“org.apache.fop.fo.ValidationException: A table-cell is spanning
more rows than available in its parent element.”
This seems to be a bit too strong to me. I'd prefer a warning and a
fallback to the number of available rows, instead of throwing a
ValidationException in this case... Maybe I'm missing some parts of
the XSL-FO Rec, but it does not mention this explicitly as an error.
What do others think?
OTOH, now I'm wondering why you would create a table with only one
row, and a cell in that row that spans two rows, or even: why you
would in that case want to add another row, just so the cell can span
two rows... It seems more correct to omit the number-rows-spanned
property in that case, but of course, I have no idea if this is
simple to achieve by altering your stylesheet.
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
