Jan Tošovský updated FOP-1760:
    Attachment: patch_against_rev_1776640_2016-12-30.patch

Addressing two remaining issues:
(1) change bar height for inlines now matches the actual line height (this 
height is determined when entering change-bar-start element and stored directly 
in the change bar object so it can be accessed when rendering the bar)
(2) change bar placement now follows the actual writing mode. It is passed to 
the rendering stage via Traits (BLOCK_PROGRESSION_DIRECTION, 

All the stuff has been updated to the current trunk revision.

In total there are 8 new layout engine test cases. All those with all standard 
tests are passing.

> [PATCH] FOP doesn't support change bar generation
> -------------------------------------------------
>                 Key: FOP-1760
>                 URL: https://issues.apache.org/jira/browse/FOP-1760
>             Project: FOP
>          Issue Type: Bug
>          Components: unqualified
>    Affects Versions: trunk
>         Environment: Operating System: All
> Platform: All
>            Reporter: Stephan Thesing
>         Attachments: change-bars.fo, change_bars_diff.txt, changebar.diff, 
> changebar_20110308.diff, changebars.fo, changebars.pdf, 
> changebars_20110512.diff, diff_1691612.diff, diff_2010_03_06.txt, 
> fop_20120507.diff, fop_changebars_20120506.diff, 
> patch_against_rev_1686494_2015-06-19.patch, 
> patch_against_rev_1690781_2015-07-19.patch, 
> patch_against_rev_1755460_2016-08-07.patch, 
> patch_against_rev_1776640_2016-12-30.patch, test.fo, test.pdf
> In order to produce change bars along the columns for changed contents,
> FO supports the fo:change-bar-begin and fo:change-bar-end elements.
> These are not supported by FOP.
> Support for change bars should be added.
> Effort needed
>  - add parsing and validation of fo: elements
>  - determine fo elements under influence of one or more change bars
>  - when creating areas from such affected fo elements, create additional areas
>     representing the change bars as defined in the FO standard.

This message was sent by Atlassian JIRA

Reply via email to