Hi Guys,

Following an old thread:

In my moving of TableRowIterator into the FO tree code I’ll implement 
stronger checks for column numbers. I think there is consensus on this, 
but as a reminder, and following the HTML 4.01 recommendation:
- if an fo:table has explicit fo:table-column children, those fix the 
  number of columns in the table, and an error will be thrown for any 
  row that has more columns;
- otherwise, the number of columns for the table will be set by the row 
  that has the greatest number of columns.

That should make most users happy: those who want speed (once some kind 
of progressive layout is implemented, of course) will simply have to 
specify explicit columns; those who want flexibility will have it.


Reply via email to