https://bugs.documentfoundation.org/show_bug.cgi?id=124824

            Bug ID: 124824
           Summary: FILEOPEN: Error rendering page break between two
                    tables in a RTF
           Product: LibreOffice
           Version: 6.3.0.0.alpha0+ Master
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
When generating a RTF with Apache FOP, if I insert a page break between two
tables, it is not rendered correctly in LibreOffice.

I will submit a patch shortly to gerrit, but I'm also opening this bug to
provide a detailed description.



Steps to Reproduce:
Open table_break_table.rtf with LibreOffice Writer

Actual Results:
The two tables appear on the same page. See actual_results.png

Expected Results:
There is a page break between the two tables. See expected_results.png


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
This problem was reported by a Linagora client in 2014. A patch was made back
then, but was not proposed upstream, I don't know why. The developer who made
the patch does not longer work for Linagora.

The client used Apache FOP to generate a document. We have access to his .rtf,
but not to the .fo source. 

The original developer mentioned in our internal ticket system that the problem
is related to a page break between two tables, so I picked a template from
Apache FOP (examples/fo/basic/table.fo) and inserted the page break with 
`<fo:block break-before="page"></fo:block>`. The complete source is attached
(table.fo) and the generated document is table_break_table.rtf. I generated it
with latest Apache FOP version (2.3).

I don't know if this is the correct way of inserting a page break or if it's
the same as the client's.

I can reproduce the issue with both .rtf in latest master.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to