Glenn Adams commented on FOP-2293:

We need to distinguish between the FO tree, the LM tree, and the Area tree. My 
point is that we should not alter the structure of the FO tree in order to 
handle constraints at the LM tree or Area tree levels. My reading of your 
suggested approach was that the FO tree should be modified, and my conclusion 
is that is the wrong way to handle this.

Conceptually, this should be no different from the handling of fo:marker and 
fo:retrieve-marker, since fo:marker can contain block or inline content, and 
areas generated by inline content would need to be parented there in a similar 
fashion. However, I see there are a few bugs registered against the current 
support for fo:marker that appear to be related to the problem you are seeing.


> Whitespace management extension
> -------------------------------
>                 Key: FOP-2293
>                 URL: https://issues.apache.org/jira/browse/FOP-2293
>             Project: Fop
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: trunk
>            Reporter: Seifeddine Dridi
>            Priority: Minor
>              Labels: XSL-FO
>             Fix For: trunk
>         Attachments: bestfit.fo, doc.pdf, FO_multi-switch_test.fo, 
> FO_multi-switch_with_best-fit_extension.patch, multiple-feasible-nodes.fo, 
> multi-switch_bestfit.fo, patch.patch, patch-rev1.1.patch, patch-rev1.patch, 
> patch-rev2.patch
> I have been working on an extension for whitespace management, similar to 
> what's described here: 
> http://wiki.apache.org/xmlgraphics-fop/WhitespaceManagement
> The logic of the extension is very simple: the user defines a set of 
> alternatives that he wishes to insert at the end of a page, then if there is 
> enough space left, FOP will pick the alternative that best matches the user's 
> selection criteria (first fit, smallest fit, biggest fit).
> This is my first work on FOP and it took me almost 2 months to reach this 
> stage in development. But it's not the end of course, so I'm relying on your 
> feedback to improve it.
> Thank you

This message was sent by Atlassian JIRA

Reply via email to