Writer has a markdown import/export filter in Collabora Online, see the post from December for more info about the filter in general.

This post is meant to detail a recent improvement when a markdown snippet is on the clipboard and it's pasted into an existing Writer document.

Motivation¶

Writer import filters operate in two modes: normally an empty model gets populated by reading user input from a file, in a certain format. You can also paste similar data from the clipboard, in which case the target model is not empty and this introduces some complexity.

The markdown import was missing some tweaks which were there already in the ODT and RTF paste code. Additionally, given that markdown only allows limited formatting, it makes sense to inherit more formatting from the paste position, so the pasted content's formatting is consistent with the formatting of the surrounding content.

Results so far¶

The document from the issue had bullets with text "A" and "B", the first problem was that pasting before "A" resulted in a mix of existing vs pasted content:

After fixing that, the problem was that the bullet format from markdown and in the existing document was different:

Once that got fixed, the paragraph style was still bad:

Which lead to the correct paste result:

As a bonus point, undo for the paste now works correctly, too.

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:

• cool#15535 sw markdown import: handle pasting into an existing paragraph
• Related: cool#15535 sw markdown import: use matching num rule if possible
• Related: cool#15535 sw markdown import: use matching paragraph formatting

Want to start using this?¶

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition.

The document compare view in Collabora Online Writer allows comparing documents side by side, see the first post for more info about the feature in general.

This second post is meant to give you an update on what happened in this area in the last month.

Motivation¶

Collabora Online core supports showing or hiding tracked changes in document content, we have a UI button for that, see the notebookbar's Review tab, the Tracking section's Show button.

Entering doc compare mode or leaving it works by clicking on the View Changes button, in the same section.

But this means that you can show/hide changes (modifies the document layout, affects everyone) and also view them (only affects your view), and they do quite different things. :-)

Results so far¶

The new UI has a button with a drop-down: the button is toggle that reflects if you compare change side-by-side or not. And if you click the drop-down next to the button, it's clear that show/hide is for inline rendering in the document layout while the other option is to render changes side-by-side:

While this used to look like this:

There were also a number of other smaller improvements: now side-by-side rendering works nicely if you use IME to type characters, a missing invalidation is sorted out and side-by-side rendering is better with comments.

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. Core side:

• tdf#171191 sw redline render mode: fix crash on IME input

COOL side:

• browser, document compare: annotate overriding functions with 'override'
• cool#14940 document compare: merge Show and View Changes buttons into a single menu button
• cool#14990 document compare: fix lost mode=2 full invalidations
• cool#15195 document compare: fix bad vertical position of comments on scrolling
• cool#15195 document compare: fix bad horizontal position of comments

Want to start using this?¶

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition.

If you have two documents or two versions of a document to compare, then traditional tracked changes is too late, the untracked changes are already in the document.

This work for Collabora Online adds interactive a non-interactive document compare to create tracked changes after the fact, finally introduces a document compare view, to better understand these changes.

Motivation¶

Collabora Online's core already contained a document compare feature, but this was never integrated with the SDK (REST API) or with the browser UI.

Additionally, while some users took a training in understanding track changes (or: redlines), the usage of underlines for inserts and strike-throughs for deletions may not be obvious. An alternative of this is a side-by-side view, which is now available in Collabora Online for text documents.

Results so far¶

Non-interactive document compare¶

See the SDK, now you can convert e.g. an editable (new) docx file to PDF in a way that your request references your old docx file as a parameter, and the resulting PDF shows the differences:

curl -k -F "data=@new.docx" -F "compare=@old.docx" -F "format=pdf" -o out.pdf https://localhost:9980/cool/convert-to

Interactive document compare¶

Technically this is a bit similar to image insertion: once you open your new document, you can compare its content with an old local or remote document:

Just use the Compare button on the Review tab on the notebookbar.

Document compare view¶

We worked with Gokay to build this. The LOK API now provides "tile modes" for text documents, similar to how presentations already have tile modes for slide content, master pages and notes. The default tile mode is unchanged for text documents, but the Review tab of the notebookbar has a View Changes button and then the new left hand side, right hand side tile modes allow you to show the changes side by side:

Removed content is colored with a red-like color, added content is colored with a green-like color. The matching content on the other side is gray. This is not only for text, e.g. images have a frame with a similar color.

Now that the LOK API could provide tiles either left or right hand side mode, Gokay built a whole new tile layout on the browser side, so these are shown nicely side by side.

To better understand what you see on your screen, now there are also labels at the top of the first pages:

This describes the purposes of the two sides, and in case you're right after a document compare action, also shows you the file names, modification dates and author names.

For integrators, it's possible to start in this mode by default, if you append &comparechanges=1 to COOL's iframe URL.

Finally if you hover over a tracked change with your mouse, now you get a highlight for that piece of text on both sides, to match the same parts of the old and new version better. A deletion looks like this:

This also works for inserts:

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. Core side:

• cool#13574 sw lok: introduce a redline render mode view option
• cool#13574 sw lok: improve non-standard redline render mode colors
• cool#13574 sw lok: increase saturation of non-standard redline render mode
• cool#13574 sw redline render mode: add uno command to switch from standard
• cool#13574 sw redline render mode: send LOK status
• cool#13574 sw redline render mode: invalidate both omit modes together
• cool#13574 sw redline render mode: avoid coloring, set lightness
• cool#13574 sw redline render mode: extract SwTextPaintOmitter from text painter
• cool#13988 sw redline render mode: handle anchored images
• cool#13574 sw redline render mode: somewhat color ins/del as green/red
• cool#13988 sw redline render mode: handle inline images
• cool#13988 sw redline render mode: add colored border for anchored images
• cool#13988 sw redline render mode: add colored border for inline images
• cool#13988 sw redline render mode: handle moves
• cool#13988 sw redline render mode: table row redlines
• cool#13988 sw redline render mode: handle number portions
• cool#13988 sw redline render mode: handle tab portions
• cool#13988 sw redline render mode: expose old/new author/date when comparing
• cool#13988 sw redline tooltip LOK API: expose anchor range

COOL side:

• cool#4535 convert-to compare option: introduce 'additional files'
• cool#4535 convert-to compare option: insert old reference doc before save
• cool#4535 convert-to compare option: add testcase
• cool#13574 redline render mode: send statusupdate with mode=2 when entering doc compare mode
• cool#13574 redline render mode: fix missing invalidate after the 2nd enter
• cool#13574 redline render mode: extract sendTileCombineMessage() from sendTileCombineRequest()
• cool#13574 redline render mode: request mode=1 tiles on requesting mode=2 tiles
• cool#13988 browser: fire comparedocuments event on selecting a file for doc compare purposes
• cool#13988 browser, on comparedocuments: send insertfile websocket message
• cool#13988 kit, insert file: handle the comparedocuments type
• cool#13988 doc compare: add testcase
• cool#13988 doc compare, browser: add a new Action_CompareDocuments PostMessage
• cool#13988 doc compare, kit: handle comparedocumentsurl file insertion
• cool#14093 browser: show the user name of other text cursors on mouse hover
• cool#14093 add testcase
• cypress, cursor header section: improve testability
• cool#14299 redline render mode: change notebookbar button type to bigcustomtoolitem
• cool#13988 redline render mode: add a HTTP parameter to activate this mode on load
• cool#13988 redline render mode: fix TilesMiddleware.getMissingTiles()
• cool#13988 redline render mode: improve TilesMiddleware.updateTileDistance()
• cool#13988 redline render mode: fix the HTTP GET parameter
• cool#13988 redline render mode: add missing tiles testcase
• cool#13988 redline render mode: add a new CompareChangesLabelSection
• cool#13988 redline render mode: scroll CompareChangesLabelSection
• cool#13988 redline render mode: labels can be now multiline
• cool#13988 redline render mode: display author / modification date for both sides
• cool#13988 redline render mode: deduplicate the label setup code for the two sides
• cool#13988 redline render mode: center the title vertically when we have no subtitle
• cool#13988 redline render mode: avoid doc name when just viewing tracked changes
• cool#13988 redline render mode: switch to gray/blue backgrounds for the labels
• cool#13988 redline render mode: show the old file name in the old label after local compare
• cool#13988 redline render mode: try to avoid DOM node touch while drawing
• cool#13988 redline render mode: show the old file name also with a remote compare
• cool#13988 redline render mode: fix insert/delete tooltip
• cool#13988 redline render mode: extract common code from ContentControlSection to CanvasSectionObject
• cool#13988 redline render mode: add a new TooltipAnchorSection
• cool#13988 redline render mode: add dynamic color for the tooltip anchor section
• cool#13988 redline render mode: don't highlight redline ranges by default
• cool#13770 windows: use LOK's new registerFileSaveDialogCallback()
• cool#13988 redline render mode: highlight both sides
• cool#13988 redline render mode: adjust highlight color to text color
• cool#13988 redline render mode: work with last used tile mode when showing tooltip
• cool#13988 redline render mode: add tooltip anchor section cypress test
• Related: cool#14716 document compare: fix position of the context toolbar
• Related: cool#14716 document compare: add context toolbar position test
• cool#14716 document compare: fix bad tile position after zoom change

Want to start using this?¶

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition.

If you have a commented text range, which gets deleted while track changes is on and you later save and load this with Writer's DOCX filter, that works now correctly.

This work is primarily for Collabora Online, but the feature is available in desktop Writer as well.

Motivation¶

It was already possible to comment on text ranges. Comments were also supported inside deletes when track changes is enabled. These could be already exported to and imported from DOCX in Writer. But you could not combine these.

With the increasing popularity of commenting text ranges (rather than just inserting a comment with an anchor), not being able to combine these was annoying.

Results so far¶

Here is how a commented text range inside a delete from DOCX now looks like, note the semi-transparent comment hinting it's deleted:

As a side effect, this also fixes the behavior in desktop Writer, which crosses out deleted comments:

In the past, the "is this deleted" property was not visible in the render result:

And it was also bad in desktop Writer:

This required changes to both DOCX import and export: a comment could be deleted or could have an anchor which is a text range, but you couldn't have both.

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. Core side:

• cool#13988 DOCX import: fix missing delete flag on deleted comments with ranges
• cool#13988 DOCX export: fix missing delete flag on deleted comments with ranges

Want to start using this?¶

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition. 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 (26.8).

The bullet support in Impress got a couple of improvements recently, some of this is PPTX support and others are general UI improvements.

This work is primarily for Collabora Online, but the feature is available in desktop Impress as well.

Motivation¶

Probably the most simple presentations are just a couple of slides, each slide having a title shape and an outliner shape, containing some bullets, perhaps with some additional images. Images are just bitmaps, so let's focus on outliner shapes and their outliner / bullet styles.

What happens if you save these to PPTX and load it back? Can you toggle between a numbering and a bullet? Can you return to an outliner style after you had direct formatting for your bullet?

Results so far¶

The first case was about bullet editing of this document:

If you pressed enter at the end of 'First level', then pressed <tab> to promote the current paragraph to the second level, nothing happened. The reason for this was that our PPTX export was missing the list styles of shapes, except for the very first list style. And the same was missing on the import side, too. With this, not only the rendering of the bullets are OK, but also adding new paragraphs and using promoting / demoting to change levels work as expected.

The second case was about this document, where the second level had a numbering, not a bullet:

We only had UI to first toggle off a numbering to no numbering, then you could toggle on bullets. Now it's possible to do this change in one step.

The last case was about styles. Imagine that you had a master page with an outline shape and some reasonably looking configuration for the first and second levels as outline styles:

Notice how the last paragraph has a slightly inconsistent formatting, due to direct formatting. Let's fix this.

Go to the end of the last bullet, which is currently not connected to an outline style, toggle bullets off and then toggle it on again. Now we clear direct formatting when we turn off the bullet, so next time you turn bullets on, it'll be again connected to the outline style's bullet configuration and the content will look better.

Note how this even improves consistency: Writer was behaving the same way already, when toggling bullets off and then toggle on again resulted in getting rid of previously applied unwanted direct formatting.

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. Core side:

• PPTX export: fix missing non-first level list style for outline shapes
• sd doc model dump: allow invoking this from outside sd/ in a debugger
• sd doc model xml dump: show styles
• tdf#168559 PPTX imp: fix missing custom level list style for outline shapes
• tdf#168559 PPTX imp: fix missing list style for outline shapes on master pages
• tdf#89365 sd UI: fix transitioning from a numbered list to a bulleted list
• tdf#169275 sd UI: clear direct format when turning off bullet/num
• sd: extract FN_TRANSFORM_DOCUMENT_STRUCTURE handling to a new function
• sd, FuBulletAndPosition: avoid magic number for bullet toggle
• Related: tdf#89365 sd UI, from numbering to bullet: fix defaults

Want to start using this?¶

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition. Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect the core of this work will be available in TDF's next release too (26.2).

Writer recently got a new markdown import option to take styles from a template, leading to much prettier output when converting markdown to PDF, DOCX or ODT.

This work is primarily for Collabora Online, but the templating feature is available in desktop Writer as well.

Motivation¶

A previous post mentioned recent improvements to the markdown import/export in Writer.

But if you convert some markdown to e.g. PDF, all the headings just have the default look, wouldn't it be nice to take your organization template and add colors and other formatting there, automatically?

Also, wouldn't it be nice if you could paste as markdown in COOL or copy the current selection as markdown? Which would enable all sorts of interesting use-cases, like using an external API to turn the selection into a summary or translating it to a different language.

Results so far¶

Here is a sample input markdown:

# heading 1

body text

Here is how it looks like if you template it using the core.git sw/qa/filter/md/data/template.docx sample:

curl invocation for this:

curl -k -F "data=@/path/to/test.md" -F "template=@/path/to/template.docx" -F "format=pdf" -o out.pdf https://localhost:9980/cool/convert-to

Or example desktop command-line:

soffice --infilter='Markdown:{"TemplateURL":{"type":"string","value":"./template.ott"}}' test.md

While it would look like this by default:

The other part is the PostMessage API of COOL, if you want to copy and paste as markdown. What's newly possible:

• Copy the current selection: set MessageId to Action_Copy and the value to {"Mimetype": "text/markdown;charset=utf-8"}
• Paste at the current cursor position: set MessageId to Action_Paste and the value to something like {"Mimetype": "text/markdown;charset=utf-8", "Data": "foo _bar_ baz"}

You can read more about the PostMessage API in the COOL SDK.

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. Core side:

• tdf#169316 sw markdown import: add a TemplateURL parameter
• tdf#169316 sw markdown import, template: handle non-ODF formats as well
• cool#13468 sw markdown paste: add UNO command parameter to skip the detection
• Related: tdf#169251 sw markdown export: fix crash on OLE with no graphic

Online side:

• cool#13419 convert-to template option: handle multiple streams in ConvertToPartHandler
• cool#13419 convert-to template option: pass it to doc broker
• cool#13419 convert-to template option: pass it to the kit process
• cool#13419 convert-to template option: more strict param name, generalize filenames
• cool#13419 convert-to template option: add testcase
• cool#13468 PostMessage API: allow copying the current text selection

Want to start using this?¶

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition. Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect the core of this work will be available in TDF's next release too (26.2).

Writer has some support for interdependent (or hierarchical) tracked changes: e.g. the case when you have a delete on top of an insert. See the third post for background.

This work is primarily for Collabora Online, but the feature is available in desktop Writer as well.

Motivation¶

Interdependent changes mean that the UI shows one type of change on top of another change, e.g. formatting on top of insert. Writer knows the priority of each type, so in case you have an insert or delete change and on top of that you have a formatting, then the UI will look "through" the formatting and work on the underlying insert or delete when you navigate with your cursor to a position with multiple changes and you press Accept on the Review tab of the notebookbar.

Usually this is what you mean, but what if you want to work on the formatting at the top, directly? You can now open the Manage Changes dialog using the Manage button on the Review tab of the notebookbar and if you go to the formatting change row of the dialog, then pressing Accept there will accept the formatting change, not the insert or delete change. This is possible, because the dialog gives you a way to precisely select which tracked change you want to work with, even if a specific cursor position has multiple tracked changes.

Results so far¶

Here is a sample ins-then-format.docx document from the core.git testcases, the baseline has an insertion, and part of that is covered by an additional formatting change on top:

If you just go in the middle of the document and press Accept, that will work with the more important insert change, so the result looks like this:

But now you can also open the Manage Changes dialog, to be more specific by directly selecting the formatting change:

And when you accept the formatting change directly, the result will be just the insert change:

You can save and load the results in both DOCX and ODT, as usual.

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. Core side:

• tdf#166319 sw interdependent redlines: allow accept/reject for fmt on ins/del
• tdf#166319 sw interdependent redlines: fix redo of accept for fmt on ins/del
• tdf#166319 sw interdependent redlines: fix redo of direct reject for format

Want to start using this?¶

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition. 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 (26.2).

Writer recently got a Markdown import & export filter and there were a number of improvements to that.

This work is primarily for Collabora Online, but the feature is available in desktop Writer as well.

Motivation¶

Ujjawal Kumar contributed a markdown import to Writer, as part of Google Summer of Code (GSoC) this summer. Mike Kaganski of Collabora also created a minimal markdown export in Writer. I looked at the feature differences between the two, and filled in various gaps in the markdown export. I also added a few general markdown import/export improvements relevant for normal Writer documents, like embedded image support.

Results so far¶

Here is a sample case of a document using inline code spans:

Exporting this to markdown & loading back to Writer, the code span was lost:

And now it's preserved:

This also works with code blocks.

Second, here is a document with lists:

Exporting this to markdown & loading back to Writer, the lists were lost:

And now they are preserved:

This also works with nested lists.

Third, here is a document with an image:

Exporting this to markdown & loading back to Writer, the image was lost:

And now it's preserved:

This also works with embedded and anchored images.

Fourth, here is a document with a table:

Exporting this to markdown & loading back to Writer, the table was lost:

And now it's preserved:

This also works with table alignments and nested tables (to the extent the markdown markup allows that).

Fifth, here is a document with a quote block:

Exporting this to markdown & loading back to Writer, the quote's paragraph indentation was lost:

And now it's preserved:

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. Core side:

• desktop lok, doc save: register .md for Markdown
• sw markdown export: handle code
• tdf#168152 sw markdown export: handle lists
• tdf#168172 sw markdown export: handle images
• tdf#167564 sw markdown export: handle tables
• sw markdown export: handle block quote
• tdf#168317 sw markdown export: handle code block
• sw markdown export: handle table cell adjustment
• tdf#168341 sw markdown filter: handle links on images
• sw markdown export: handle line breaks
• tdf#168446 sw markdown export: improve image name/description/title handling
• tdf#167564 sw markdown export: handle multi-para table cells
• tdf#167564 sw markdown export: handle nested table cells
• tdf#168617 sw markdown filter: map tasks to checkbox content controls and back
• sw markdown filter: import images with 'data:' URLs
• sw markdown filter: export non-linked inline images
• tdf#168662 sw markdown export: extract inline image export functions
• tdf#168662 sw markdown export: handle anchored images

Want to start using this?¶

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition. 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 (26.2).

Writer has some support for interdependent (or hierarchical) tracked changes: e.g. the case when you have a delete on top of an insert. See the second post for background.

This work is primarily for Collabora Online, but the feature is available in desktop Writer as well.

Motivation¶

With the already mentioned improvements in place, the area of format redlines with character style or direct formatting changes were still lacking: Writer's original model here was just marking a text range as "formatted" and then either accept the format redline as-is, or reject reverting back to the paragraph style (default formatting), losing the old character style or old direct formatting.

Results so far¶

Here is a sample case of a document where the old character style is Strong (~bold) and the font size is 24pt, while the new character style is Quote (~italic) and the font size is 36pt. The rest of the document uses no specific character styles and has the font size of 12pt:

Rejecting that format redline resulted in just the defaults, i.e. no character style and 12pt font size:

But now we track the old character style & direct format:

This required changes in the DOCX import, ODF import and ODF export, too.

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. Core side:

• sw: document DocumentRedlineManager
• sw: document IDocumentRedlineAccess
• sw doc model xml dump: show the item set of a format redline
• tdf#166319 sw interdependent redlines: fix redo of accept of ins-then-fmt's fmt
• tdf#166319 sw interdependent redlines: handle deleting a self ins-then-fmt
• tdf#166319 sw interdependent redlines: fix redo of reject of del-then-fmt's fmt
• tdf#167194 sw redline reinstate: fix handling of self-inserts
• tdf#167761 sw format redline: register the item set in the autostyle pool
• tdf#167761 sw format redline: implement ODF export
• tdf#167761 sw format redline, char props: implement ODF import
• tdf#167761 sw format redline, char style: implement DOCX import
• tdf#167761 sw format redline, char style: implement ODF import
• tdf#167761 sw format redline, char style: fix missing encode in ODF filter
• tdf#167761 sw format redline, char style+direct: add ODT export
• tdf#167761 sw format redline, char style+direct: add ODT import

Want to start using this?¶

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition. 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 (26.2).

This post is part of a series to describe how Writer now gets a feature to handle tables that are both floating and span over multiple pages.

This work is primarily for Collabora Online, but is useful on the desktop as well. See the 11th post for the previous part.

Motivation¶

Previous posts described the hardest part of multi-page floating tables: making sure that text can wrap around them and they can split across pages. In this part, we'll look at a conflicting requirement. On one hand, headings want their text to not split across pages (and shapes anchored into paragraphs are considered part of the paragraph, too). On the other hand, it should be OK to have a floating table at the bottom of a page and the following heading to go to the next page.

It turns out, Writer gave "keep together" a priority, while Word gave "floating tables are OK to split to a previous page" a priority.

Note that if you have a shape (e.g. a triangle) and not a floating table, then both Word and Writer prevents the move of that shape to a previous page (if the shape is anchored in a heading); this difference was there just for floating tables.

Results so far¶

Here is how the tdf#167222 bugdoc looks like now in Writer:

And here is how it used to look like:

And here is the reference rendering:

This means that we leave layout for shapes unchanged in general: shapes anchored in headings are still considered to be part of headings and don't split. But for floating tables, we now allow them to split and use space at a previous page if they fit there.

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:

• tdf#167222 sw floattable: allow split of fly and its keep-together anchor text
• Related: tdf#167222 sw floattable: fix split of fly and its 'keep' anchor text
• Related: tdf#167222 sw floattable: fix split of fly and its heading text w/ ftn
• sw: fix assertion failure in SwFrameShell::Execute()
• Related: tdf#167222 sw floattable: fix split of fly and heading text fit check

Want to start using this?¶

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition. 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 (26.2).