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! :-)

> I've already documented a known problem [5] (at
> the bottom). I just hope it won't bite us later on.
> [5]

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!! 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! :-)


Reply via email to