xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Pepping <spepp...@leverkruid.eu>
Subject Re: [Xmlgraphics-fop Wiki] Update of "GoogleSummerOfCode2006/FloatsImplementationProgress/ImplementingSideFloats" by VincentHennebert
Date Fri, 18 Aug 2006 20:16:02 GMT
On Fri, Aug 18, 2006 at 07:04:56PM +0200, Vincent Hennebert wrote:
> Hi Simon,
> 2006/8/17, Simon Pepping:
> >Rule 7a is logically correct, but I would say that the rule simply
> >states that a start float should not stick out at the end side, even
> >if it is not the one that is flush with the start side. Then x + ipd
> ><= ipd(ref-area) follows even without the condition ipd <=
> >ipd(ref-area).
> Hmmm. If the ipd of a float is greater than ipd(ref-area), then it /is/
> allowed to stick out at one side (end-side for start-floats, start-side
> for end-floats). On the contrary, if ipd <= ipd(ref-area), then the
> float is not allowed to stick out at any side. That's why there is the
> condition. Don't you agree?

I had not looked at it from that point of view. That makes sense.

> >> One issue is that some legal pagebreaks are unknown until paragraphs are
> >> laid out (because of widows/orphans, for example). So the "for each
> >> legal pagebreak" is not that simple and might involve some backtracking.
> >
> >Yes, there is a problem there. The solution could be as follows: When
> >the legal pagebreak is in a paragraph, it is also the considered legal
> >linebreak. It is tested whether this linebreak could end the last line
> >of the page.
> And deactivate the node if it turns out that this linebreak corresponds
> to (e.g.) the next-to-last line of the paragraph? Hmmm, that could work.
> I'll think about that.

That is right, the layout on the following page might invalidate this
pagebreak. One can only know after the whole paragraph has been broken
into lines. Awkward.

Regards, Simon

Simon Pepping
home page: http://www.leverkruid.eu

View raw message