[FOP-1484] RTF Static Content Error In Every Region

• Type: Bug
• Status: Closed
• Resolution: Incomplete
• Affects Version/s: 0.94
• Component/s: renderer/rtf
• Environment: Operating System: other; Platform: Other
• External issue ID: 44317
• Assignee: fop-dev
• Reporter: Peter Ryan
• Created: 28/Jan/08 17:29
• Updated: 28/Jan/08 17:30
• Resolved: 01/Apr/12 13:54

Description

When generating an RTF FOP renders a static content element in every
corresponding region even when this is not reflected in the fo object.

For example if page 1 of a document which uses a simple-page-master that has a
region-before set with a non-zero extent, and has a static content header
defined in the region-before, and page 2 uses a different simple-page-master
where the extent of the region-before is set to 0, the header will still be
rendered in the 2nd page in a .rtf document; in a .pdf the header is correctly
not shown.

The .fo document reflects that the header is not in the 2nd page, but it is
still rendered anyway.

Please see the attached example. Again the generating an RTF is displaying
incorrect behavior and the PDF is the expected output.