> -----Original Message----- > From: Luca Furini [mailto:[EMAIL PROTECTED] > > > Jeremias Maerki wrote: > > > I'm a bit concerned about the increasing complexity of this. It takes > > considerable time just to understand and play through all these examples > > and after that implementing it so that the code is still readable. Of > > course, we documented our findings pretty well, although a newbie will > > surely be totally lost. > > The matter is so complicated that I would be suspicious of a simple > solution! :-)
Fully agreed with Luca here. Well, maybe making it less complex would also make it less flexible, which, in the long run, makes it even more difficult to understand. Anyway, the documentation is indeed extensive enough to give those interested a clear idea of the logic behind it. As for the really 'green' newbies: *if* they absolutely insist on figuring it all out by themselves, they will probably never understand... either that or their iq's off the scale :-) > > > 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). > > 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!! BTW: Does this problem pose itself only if a single cell or row spans more than two pages, or also when an entire row-group does so? Just asking because, in the latter case, it may turn out to be less unlikely/more dangerous than it seems at first glance, albeit only a tiny bit. (apart from the already mentioned common workaround for start-indents in 0.20.5...) Cheers, Andreas
