Glenn Adams commented on FOP-2293:

I disagree with this analysis for the following reasons:

(1) if the notion of "one element, one function" were articulated in XSL-FO, 
and it isn't, then the function would be layout based, and not semantic based; 
the actual specification of what is permitted by extensions is found in Section 

"The presence of such [extension] attributes must not change the behavior of 
XSL elements and functions defined in this document. This means that an 
extension attribute may change the processing of an FO, but only provided that 
the constraints specified by XSL on that FO remain satisfied."

(2) the suggested extension on multi-switch does not violate any constraint 
specified by XSL;

(3) the suggested extension on multi-switch retains and precisely uses the 
intended semantics of multi-switch: to select between alternatives;

(4) the specification does not preclude using a alternate selection mechanism 
than multi-toggle or using such a mechanism to imply semantics similar to 

(5) resorting to defining a new element which almost completely overlaps the 
semantics of an existing element is architecturally unsound, and leads to 
proliferation of variation rather than harmonization of use;

Consequently, I find your conclusions unfounded.

> 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, FO_multi-switch.patch, 
> FO_multi-switch_test.fo, multiple-feasible-nodes.fo, multi-switch_bestfit.fo, 
> patch.patch, patch-rev1.1.patch, patch-rev1.patch, patch-rev2.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 was sent by Atlassian JIRA

Reply via email to