On 26.04.2005 18:44:38 Luca Furini wrote: > > I've already documented a known problem [5] (at > > the bottom). I just hope it won't bite us later on. > > > > [5] > > http://wiki.apache.org/xmlgraphics-fop/TableLayout/KnuthElementsForTables > > I don't think it is a dangerous problem: it can be recognized and properly > handled, as you wrote, discarding the wrong elements after the first inner > break and collecting the right ones (and this mechanism is needed anyway).
But I think that's going to be a project on its own. Discarding objects means there is overhead which needs to be minimized. And doing that well will not be so easy. I've done some investigation there and I don't want to think about it right now. > It is such an unlikely situation that I don't think we should worry about > it: I really can't think of a real example of table with a monstrous row > that must be broken more than once!! I think it is already quite unlikely > to allow a page break in the middle of a row, which would force the reader > to go back and forth several times, in order to read each cell from the > beginning to the end! :-) What about a blind table for indenting content? Isn't that a frequent work-around for FOP 0.20.5? Fortunately, people will be able to use start-indent with the new code. Jeremias Maerki
