Description: Show different between Microsoft Office 2016 and LibreOffice 7.2.0 Steps to Reproduce: The default.docx is generated by pandoc. Actual Results: The Table caption in second page by Word2016, where begin in first page by LO. Expected Results: See details by docx and pdf. Reproducible: Always User Profile Reset: Yes Additional Info: none
Created attachment 172291 [details] generated by pandoc
Created attachment 172292 [details] default-word.pdf
Created attachment 172293 [details] default-writer.pdf
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 > regression. 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.
Dear 10686639125, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug