Estimated read time: 5 minutes
Writer now has continued steps to handle tables that are both floating and span over multiple pages.
The previous post finished with crash testing: the interesting subset of that testing tool is to take hundreds of thousands of documents and in the Writer case import them into a document model and layout them. If any of this crashes, mark that for future investigation. In this post, we'll see what else started to work during the past month.
Results so far¶
The feature is enabled by default and now the DOCX/DOC/RTF import makes use of it if. This allows stress-testing the layout code with complex user documents, hopefully with the found breakage fixed before it would be released in a stable version.
On the positive side, core.git repository has has 37 files now which are focusing on correct handling of floating tables (abbreviated as "floattables"). Also, there are additional tests that quickly build a specific multi-page floating table in the memory and do some operation on it, e.g. delete the last row and assert what happens.
Here are some screenshots from the effort so far:
The first case is about multi-column sections: in this case Word doesn't try to split them between pages. What you can see on the screenshot is that Writer lays out content on the previous page so that remaining space is left, but we don't try to split the table between the first and the second page, even if there would be space on the first page and even if this means the table overlaps with the second column, matching what Word does.
UI to enable split of floating tables were added quite early: this is a new checkbox on the frame properties dialog. However, disabling the split of floating tables was broken, the already created layout was not updated to properly move back "follow" fly frames from later pages to the current page, which is now fixed.
Writer already had a feature to split content in a frame into multiple frames, but that one required creating those frames in the model explicitly, such chaining is a feature that is useful in other use-cases and is parallel to multi-page floating tables. The UI now ensures that the user can split frames only in case chaining is not used, to avoid confusion.
This is now also true in the other way around: if split of a floating table is allowed, then we disable the frame chaining UI to avoid trouble later.
At this point I went back to crashtesting & crash bugreports, and the latest reported crash was for a document that is visible on the above screenshot. This was a bit tricky: it required 3 fixes to make it not crash and also a layout loop fix.
Next was a mini-feature: even if floating tables normally split across pages by default, Word has a document-level compatibility switch to turn this split on or off by default, at a layout level. Floating tables from RTF are not split by default, DOC and DOCX split them by default.
What you can see on this screenshot is that a DOCX document may have this flag enabled, and then you allow splitting on the UI / at a document model level, but Writer may still decide to not split them, to provide the correct layout.
The previous post already mentioned the problem area of overlapping tables. A first step in this direction is to fix this bug document with Arabic text and 2 overlapping tables, making them unreadable.
And in this case here is the fixed version, where reading the table now depends on your language skills. :-)
In this case, the problem was a lost section break of type next page, when a section started with a floating table, which is a corner-case.
And that's where we stand. Certainly more work is needed to fix more unwanted overlapping of floating tables, but we get there step by step.
How is this implemented?¶
If you would like to know a bit more about how this works, continue reading... :-)
As usual, the high-level problem was addressed by a series of small changes:
- sw floattable, crashtesting: fix PDF export of forum-mso-en3-26783.docx
- sw floattable: don't try to set various character properties as table property
- sw floattable, crashtesting: fix PDF export of ooo9470-1.doc
- sw floattable: fix UI for turning fly split off
- sw floattable: fix UI / property dialog for shape containing table
- sw floattable: disable UI if the frame is chained already
- sw floattable: disable chain UI if the frame is allowed to split already
- sw floattable: fix missing table join when moving master fly to next page
- sw floattable: fix legacy max height of split flys with negative vert offset
- sw floattable: fix assert fail when object formatter gets the wrong anchor
- tdf#155002 sw floattable, split but not yet moved follow: fix GetNextFlyLeaf()
- sw floattable: add a DoNotBreakWrappedTables compat flag
- sw floattable: handle
<w:doNotBreakWrappedTables>in the DOCX filter
- sw floattable: handle fDontBreakWrappedTables in the DOC filter
- sw floattable: handle \nobrkwrptbl in the RTF filter
- tdf#150769 sw floattable: fix lost PageDescName if section starts with a table
Want to start using this?¶
You can get a snapshot / demo of Collabora Office 23.05 and try it out yourself right now: try the unstable snapshot. Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF's next release too (7.6).