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.
Created attachment 21439 [details] This fo demonstrates the problem
I've done some experiments, even manually modified the RTF file. I don't get MS Word Viewer to reset the top margin to 0 after it has once been set to a non-zero value. If you move the last page-sequence in your demo file as the first, you'll see that the first page is handled correctly with no margins. IMO, this is a bug in Word. FOP has a lot of limitations concerning RTF output. Some of them come from the incomplete implementation of the RTF output but even more come from limitations of the RTF format itself or from the way the RTF is interpreted by word processors.
batch transition to closed remaining pre-FOP1.0 resolved bugs