Just found this unanswered. Sorry.
On 27.04.2005 18:28:55 Andreas L. Delmelle 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). > > > > 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? Possibly, yes. A row-group in this context is formed because at least one cell has row-spanning. Therefore, you have the possibility that a cell span over more than 2 pages. > 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...) Well, less likely simply means that it can happen and sooner or later we'll have to deal with it. Jeremias Maerki
