[
https://issues.apache.org/jira/browse/FOP-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758866#comment-13758866
]
Pascal Sancho edited comment on FOP-2293 at 9/5/13 8:01 AM:
------------------------------------------------------------
> Regarding your suggestion Pascal, do I have to define the fitting-strategy
> property twice in FOPropertyMapping? One with the fox namespace and an other
> without it.
This is outside my knowlegde; I guess you should handle the 2 cases.
In current fop extensions, I see no examples that have the double scope
(inside/outside fox element).
But there are some examples for the 2 cases:
FOX attribute inside a FOX namespace element:
fox:destination/@internal-destination
FOX attribute inside a non-FOX namespace element:
@fox:transform, all prepress attributes
HTH.
was (Author: psancho):
> Regarding your suggestion Pascal, do I have to define the
fitting-strategy property twice in FOPropertyMapping? One with the fox
namespace and an other without it.
This is outside my knowlegde; I guess you should handle the 2 cases.
In current fop extensions, I see no examples that have the double scope
(inside/outside fox element).
But there are some examples for the 2 cases:
FOX attribute inside a FOX namespace element:
fox:destination/@internal-destination
FOX attribute inside a non-FOX namespace element:
@fox:transform, all prepress atributes
HTH.
> 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
