Vincent, please consider the case where a table cell is long, or even longer than a page. In this case it should break it anyways. Also, consider these cases:
+------------+ | 0.25 pages | +------------+ | 1.5 pages | +------------+ | 0.25 pages | +------------+ +-----------+ | 0.5 pages | +-----------+ | 0.9 pages | +-----------+ | 0.5 pages | +-----------+ both of them I'd prefer to see split onto two pages. So imo a high penalty is better btw: does the fop spec not specify that a table should be closed when broken? e.g. +---------+ | much | | content | +---------+ to: +---------+ | much | +---------+ ----------------------------pagebreak +---------+ | content | +---------+ ? just my 2 cts. Max On Mit, 2008-01-09 at 14:27 +0000, Vincent Hennebert wrote: > Hi, > > The title may be a little cryptic for those who aren’t familiar with the > table layout code :-\ But basically it corresponds to the following: > > When a row starts at the bottom of a page, there may not be enough > remaining room to allow every cell to put a part of its content: > ———————————————————————————————————— > | Cell 1 | | > > ----------------- Page break --------------- > > | | This text doesn’t fit | > | | on the previous page | > ———————————————————————————————————— > > Currently, a 900 penalty is assigned to such a break possibility, to > avoid as much as possible this situation from occurring. > > However, it doesn’t completely prevent it, as we have seen recently on > fop-users. My proposal is to forbid it, as anyway the output is so ugly > that one would probably prefer some extra blank space at the bottom of > the page instead. > > Is there anyone against me applying this change? > > Thanks, > Vincent > >
