[
https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761864#comment-13761864
]
Glenn Adams commented on FOP-2293:
----------------------------------
Not at all. I call it using its purpose. The only mechanism defined in XSL-FO
for changing the currently-visible-multi-case is to use a fo:multi-toggle which
specifies, using the switch-to property, an fo:multi-case to become the new
value of currently-visible-multi-case.
In the case at hand (best-fit), you would simply be defining an extension that
introduces an implicit process that has the same effect as fo:multi-toggle.
If this content arrives on an FO processor that doesn't support the extension,
then, unless some fo:multi-case has an explicit starting-state='show', then no
content in the fo:multi-switch would be displayed, which is what would be
expected. If the same content arrives on an FO processor that supports the
extension, then, since the semantics of this support would serve the same
function as fo:multi-toggle, where each fo:multi-case effectively has an
implied toggle that selects itself into the switch.
In my mind, this is exactly what an extension does: preserve existing semantics
when not supported, and introduces new semantics when supported. It couldn't be
a more natural fit.
> 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:
> 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 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
