[ 
https://issues.apache.org/jira/browse/FOP-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365393#comment-16365393
 ] 

Chris Bowditch commented on FOP-2136:
-------------------------------------

Hi Mark,

FOP is an open source project, so if you need a feature then feel free to 
develop a patch and submit it for consideration by the committers

When Luis developed the table markers implementation, it was deemed too 
complex/difficult to accommodate markers whose BPD could change, and it was 
felt that a single line value met the most common use cases in tables, e.g. sub 
totals in statements

> [PATCH] support for retrieve-table-marker
> -----------------------------------------
>
>                 Key: FOP-2136
>                 URL: https://issues.apache.org/jira/browse/FOP-2136
>             Project: FOP
>          Issue Type: Improvement
>          Components: unqualified
>    Affects Versions: trunk
>         Environment: Operating System: All
> Platform: All
>            Reporter: Luis Bernardo
>            Assignee: fop-dev
>         Attachments: examples.tar.gz, retrieve-table-marker.patch
>
>
> This patch adds support for retrieve-table-marker. The patch is extensive and 
> very likely there is room for improvement, but it does what it is supposed to 
> do and was tested with non trivial examples.
> The implementation has a main constraint: the resolution of the 
> retrieve-table-marker element needs to be an element that does not change the 
> BPD of the containing cell. In practical terms this means that the height of 
> the table header or footer where the retrieve-table-marker element is placed 
> cannot change once the retrieve-table-marker is replaced by the resolved 
> content. In the end this is not a serious constraint since in most cases the 
> retrieve-table-marker element is meant to be replaced by a line of text (and 
> there is already adjacent text, or the height of the cell is specified).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to