Description: In the example, Writer puts more lines on the next page than Word does. Steps to Reproduce: 1. Open the example file Actual Results: Line 33 and 34 are on the next page. Expected Results: Only line 34 on the next page Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 144879 [details] example file
Created attachment 144880 [details] situation in LO Writer
Created attachment 144881 [details] situation in Word
Reproduced in Version: 6.2.0.0.alpha0+ Build ID: 2419fa71d8b2223a50f596d5db7721f6213d4f87 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: threaded and back to Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Created attachment 146022 [details] Example compared MSO LO62+ This is a minor issue with formatting / spacing at "32". Repro with DOC and DOCX. If we open "32" right-click Paragraph and just press OK, "33" moves there.
Dear Patrick Jaap, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still reproducible in current master.
I see people saying this is still a problem, but when I test, I see it fixed in 6.0 with commit 0c8b749e602b6743857a9bc4efb24b6183690311 Author: Caolán McNamara on Date: Tue Sep 5 15:24:26 2017 +0100 Resolves: tdf#107249 round ascent/descent/extleading on conversion to int Specifically, I see 33 and 34 on page2 starting with that commit, and spot checked in 6.2, 6.3, 6.4, 7.0 master all confirm it is "fixed". Testing with Ubuntu 20.04 alpha x64 and bibisect-linux-64-*
Dear Patrick Jaap, 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
Still reproducible in Version: 7.3.1.3 / LibreOffice Community Build ID: 30(Build:3) CPU threads: 12; OS: Linux 5.16; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Debian package version: 1:7.3.1-1+b2 Calc: threaded
FYI: I see a 2019 WIP patch for this bug at https://gerrit.libreoffice.org/c/core/+/62219