Glenn Adams commented on FOP-2293:
Ah, I did not realize this attribute was to be defined on an extension element
(as opposed to an existing FO element). If that is the case, then I agree with
Vincent that fitting-strategy should not be namespace qualified.
However, this raises (in my mind) the question of why fox:best-fit is an
element, as opposed to being treated like a normal FO property for which
inheritance may apply as well as other FO property semantics.
> 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, multiple-feasible-nodes.fo,
> patch.patch, patch-rev1.1.patch, patch-rev1.patch
> I have been working on an extension for whitespace management, similar to
> what's described here:
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira