Yes, I agree. I've even thought about that for tables, too. I guess
it's a matter of taste whether we do that or not. I don't think the
Rec says anything about it. Anyway, I'd do it like you did for lists,
but tables may be less important in this respect. We can add it later if
necessary.
On 15.04.2005 18:56:38 Luca Furini wrote:
> I wrote:
>
> > Creating a combined list for label and body
>
> I forgot to mention that this work is mainly based on Jeremias' code for
> tables.
>
> There is only a significant difference while computing the first step:
>
> + if (backupHeights[0] == 0 && backupHeights[1] == 0) {
> + // this is the first step: choose the maximum increase, so that
> + // the smallest area in the first page will contain at least
> + // a label area and a body area
> + step = Math.max((end[0] >= start[0] ? partialHeights[0] :
> Integer.MIN_VALUE),
> + (end[1] >= start[1] ? partialHeights[1] :
> Integer.MIN_VALUE));
> + } else {
> + // this is not the first step: choose the minimum increase
> + step = Math.min((end[0] >= start[0] ? partialHeights[0] :
> Integer.MAX_VALUE),
> + (end[1] >= start[1] ? partialHeights[1] :
> Integer.MAX_VALUE));
> + }
>
> I'm not sure whether it's explicitly stated somewhere in the
> recommendation or not, but it would seem very strange to me if a page
> break could separate the label from the body.
>
> Do you agree?
>
> Regards
> Luca
>
>
Jeremias Maerki
