[jira] [Updated] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seifeddine Dridi updated FOP-2293: -- Attachment: patch-rev1.patch *Changelog (revision 1):* * Code refactoring: ** Improved FittingStrategy as suggested by Vincent ** Removed some unnecessary code from BestFitPenalty ** Deleted AlternativeManager and moved its logic to BestFitPenalty. The best alternative is now stored inside BestFitPenalty and BestFitLayoutManager has a reference to it. ** Removed the fox namespace from fitting-strategy ** Fixed some checkstyle warnings * Fixed a bug when fox:best-fit is the last element in the document flow And many other minor changes. 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.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
Re: [GUMP@vmgump]: Project xml-fop-test (in module xml-fop) failed
FYI, this is caused by missing unlimited strength jurisdiction policy files in the Gump server. I have asked Stefan@gump to update the files, which he expects to do soon. On Tue, Sep 3, 2013 at 2:02 AM, FOP Gump Nightly Build fop-dev@xmlgraphics.apache.org wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project xml-fop-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 54 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - xml-fop-test : XSL-FO (Formatting Objects) processor Full details are available at: http://vmgump.apache.org/gump/public/xml-fop/xml-fop-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/xml-fop/build/test-reports The following work was performed: http://vmgump.apache.org/gump/public/xml-fop/xml-fop-test/gump_work/build_xml-fop_xml-fop-test.html Work Name: build_xml-fop_xml-fop-test (Type: Build) Work ended in a state of : Failed Elapsed: 2 mins 51 secs Command Line: /usr/lib/jvm/java-7-oracle/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only -Dant.build.clonevm=true -Xbootclasspath/p:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/srv/gump/public/workspace/xml-xalan/build/serializer.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml gump-test [Working Directory: /srv/gump/public/workspace/xml-fop] CLASSPATH: /usr/lib/jvm/java-7-oracle/lib/tools.jar:/srv/gump/public/workspace/xml-fop/build/classes:/srv/gump/public/workspace/xml-fop/build/codegen-classes:/srv/gump/public/workspace/xml-fop/build/test-classes:/srv/gump/public/workspace/xml-fop/lib/build/asm-3.1.jar:/srv/gump/public/workspace/xml-fop/lib/build/mockito-core-1.8.5.jar:/srv/gump/public/workspace/xml-fop/lib/build/qdox-1.12.jar:/srv/gump/public/workspace/xml-fop/lib/fontbox-1.8.0-SNAPSHOT.jar:/srv/gump/public/workspace/xml-fop/build/fop.jar:/srv/gump/public/workspace/xml-fop/build/fop-sandbox.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/li b/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/packages/apache-attic/avalon-framework-api-4.3.jar:/srv/gump/packages/apache-attic/avalon-framework-impl-4.3.jar:/srv/gump/public/workspace/apache-commons/io/target/commons-io-2.5-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-20130903.jar:/srv/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/batik-slideshow.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/batik-svgpp.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-anim.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-awt-util.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-bridge.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-codec.jar:/srv/gump/public/workspace /xml-batik/batik-20130903/lib/batik-css.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-dom.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-ext.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-extension.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-gui-util.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-gvt.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-parser.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-script.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-svg-dom.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-svggen.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-swing.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-transcoder.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-util.jar:/srv/gump/public/workspace/xml-batik/batik-20130903/lib/batik-xml.jar:/ srv
[jira] [Commented] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756597#comment-13756597 ] Seifeddine Dridi commented on FOP-2293: --- I couldn't find a way to edit the Wiki page on whitespace management. It seems to be immutable. Can anyone handle that issue? I'd like to add some new content to it. 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.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
[jira] [Commented] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756603#comment-13756603 ] Glenn Adams commented on FOP-2293: -- Is the fitting-strategy attribute used in an FO instance file or in an FOP XCONF file? If it is used in the former, then you need to restore use of the fox: prefix. If the latter, then no change is needed. 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.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
[jira] [Commented] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756608#comment-13756608 ] Seifeddine Dridi commented on FOP-2293: --- It is only meant to be used in FO instance files. Needless to say, the fitting-strategy property is only relevant to fox:best-fit. Should I restore the fox prefix? 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.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
[jira] [Commented] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756613#comment-13756613 ] Glenn Adams commented on FOP-2293: -- In that case, you need to restore it. I'm not sure what Vincent was thinking, but we need any extension attribute to be namespace qualified, either using the fox binding (if integrated directly into apache fop sources), or using a third party binding (if only used on a third party fork of fop sources). The issue of whether an extension attribute applies to only one FO element type or multiple FO element types is not related to the need to use namespace qualification. 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.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
[jira] [Updated] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seifeddine Dridi updated FOP-2293: -- Attachment: patch-rev1.1.patch Added the fox namespace to the fitting-strategy attribute 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
[jira] [Commented] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756641#comment-13756641 ] Glenn Adams commented on FOP-2293: -- Regarding introducing new properties to control whitespace and line fitting, we also need to consider what is happening in CSS in this regard. Please take a look at [1] to see if it would be appropriate to reuse some of the new properties/values proposed there. [1] http://lists.w3.org/Archives/Public/www-style/2013Mar/0183.html 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
[jira] [Commented] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756688#comment-13756688 ] Pascal Sancho commented on FOP-2293: In addition to namepsace discussion: in XML 1.1 REC ยง6.2, para 2 [1]: A default namespace declaration applies to all unprefixed element names within its scope. Default namespace declarations do not apply directly to attribute names; the interpretation of unprefixed attributes is determined by the element on which they appear. [1] http://www.w3.org/TR/2006/REC-xml-names11-20060816/#defaulting 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
[jira] [Commented] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756682#comment-13756682 ] Pascal Sancho commented on FOP-2293: regarding the following construction: fox:best-fit fox:fitting-strategy=biggest-fit best-fit element is in the fox namespace. so, the default namespace for all attributes set on such element is fox namespace. You just have to specify it on carrier element. In that case, the correct construction is: fox:best-fit fitting-strategy=biggest-fit Note that double setting same namespace (both on element and on attribute) can produce unexpected behaviour with some xml parsers 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
[jira] [Commented] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756669#comment-13756669 ] Seifeddine Dridi commented on FOP-2293: --- Interesting read! The proposal is indirectly related to what I'm doing and it would useful to add such features to FOP. However, I'm not sure if the current design of FOP allows such flexibility in the choice of the text-breaking algorithm since the layout engine seems to be mainly tied around the Knuth Plass implementation. 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
[jira] [Commented] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756699#comment-13756699 ] Seifeddine Dridi commented on FOP-2293: --- What you have said is true Pascal but extension properties in FOP are defined separately regardless of their host element (see FOPropertyMapping). 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
[jira] [Commented] (FOP-2293) Whitespace management extension
[
https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756781#comment-13756781
]
Seifeddine Dridi commented on FOP-2293:
---
{quote}
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.
{quote}
Because the type of content a fox:best-fit element should represent is very
specific, I think. The purpose of the extension is to help managing the
whitespace at the end of a page, and any content that can be put there is
usually not very important. It may be a signature or some advertisements...
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
[jira] [Commented] (FOP-2293) Whitespace management extension
[ https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756893#comment-13756893 ] Glenn Adams commented on FOP-2293: -- In that case, I will have to oppose this change, since it is attempting to introduce a new semantic specific container type. We should not be introducing new FO element types as extensions. 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
