Show different between Microsoft Office 2016 and LibreOffice 7.2.0
Steps to Reproduce:
The default.docx is generated by pandoc.
The Table caption in second page by Word2016, where begin in first page by LO.
See details by docx and pdf.
User Profile Reset: Yes
Created attachment 172291 [details]
generated by pandoc
Created attachment 172292 [details]
Created attachment 172293 [details]
Reproduced 7.2+ and back to LO 3.5. Not with 3.4 for DOCX so could be a regression.
Except I'm not sure what happens here (not a matter of fonts).
If DOCX saved as DOC in MSO, repro also 7.2+ and OO 3.3.
Looks like an "every TWIP is important" kind of bug.
I'm guessing it is somehow related to line spacing being EXACTLY 28pt - which is a rather odd setting. It is probably affecting the un-editable footnote separator and causing it to take up a bit more space than normal.
LO handles the footnote separator in a completely different way from Word, so no matter what the ultimate cause, it shouldn't be surprising that there is a sizing difference in the amount of space available on the page. LO isn't wasting as much space, so one row of the table still fit on the first page.
Created attachment 172330 [details]
DOCX compared in MSO and LO
Not sure it's about 28 pt. Same with 20.
LO has "Allow table to split across pages and columns". It turned off, table goes to page 2.
Can't see what's MSO equivalent.
MS(In reply to Timur from comment #6)
> Can't see what's MSO equivalent.
There is no direct MSO equivalent. The way they do it is to mark every first-column cell's 1st paragraph as "keep with next paragraph" IIRC.
> Not sure it's about 28 pt. Same with 20.
This is specified on the Normal paragraph style, so it probably affects the separator line itself, and not only the footnote. I didn't figure out how to edit the separator line(s). (Perhaps it is only possible by editing the footnotes.xml file itself.)
(In reply to Timur from comment #4)
> Reproduced 7.2+ and back to LO 3.5. Not with 3.4 for DOCX so could be a
To be sure, I checked with oldest of bibisect-43all (which predates 3.5 a bit), and indeed the bug is there already, setting preBibisect.