Seifeddine Dridi updated FOP-2293:
I implemented basic support for handling multiple alternatives. Basically, if
the current alternative's content is too short to fit into a page, it gets
deactivated and replaced by another one. This process happens recursively until
we either run out of alternatives or find a good one.
It would be great if someone knowledgeable about the Knuth algorithm can
validate my approach.
Following-up, I have to revise my implementation of FO multi-switch and improve
the handling of dynamic content in presence of space-specifiers.
> 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: FO_multi-switch_best-fit_ext_rev2.patch,
> FO_multi-switch_best-fit_ext_rev5.patch, FO_multi-switch_test.fo,
> FO_multi-switch_with_best-fit_extension.patch, bestfit.fo, doc.pdf,
> multi-switch_bestfit.fo, multiple-feasible-nodes.fo, patch-rev1.1.patch,
> patch-rev1.patch, patch-rev2.patch, patch.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 was sent by Atlassian JIRA