Description: When Paragraph style - line spacing - proportional is set to value smaller than 100%, the spacing between first and the second line in the paragraph is wrong, it is too small. The second line ends up being too close to the first line. It looks very odd. It gets worse is you set "line spacing"- proportional to really small values, like 60% or 50%. Other lines in a paragraph seem to be spaced correctly. All fonts are affected, but on some fonts the error is less noticable. With "liberation serif", the error is smaller. Try "Deja Vu Sans", line height: proportional-57% Try "liberation serif", line height: proportional-50% On some fonts, like "Charis Sil", it gets really annoying at proportional-90% Steps to Reproduce: 1. Type a paragraph of text having at least 3 lines, (5 is better) 2. Change the font of the paragraph to "liberation serif" 3. Right click on the paragraph, select "edit style", go to "Indents and spacing", "Line spacing", set it to "Proportional":50%, click OK Actual Results: The spacing between the first and the second line is smaller than spacing between second and third line. Expected Results: All lines spaced evenly. Reproducible: Always User Profile Reset: No Additional Info: There is an additional bug. When line spacing: proportional is set to small values (<40%), the (rendering of) first line of text get clipped on it's upper part. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Created attachment 128203 [details] Screenshot of Dejavu Sans 57% proportional line spacing Repro. Win 7 Pro 64-bit Version: 5.3.0.0.alpha1+ Build ID: 02e6c1c95993740e0dbea724b3014348c4b6559d CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-10-24_04:01:05 Locale: fi-FI (fi_FI); Calc: group
Created attachment 128204 [details] Test file with Dejavu Sans Created with 5.3
Btw. in LibO 3.5 all the rows are smashed together, even a bit more than the 1st and 2nd line in newer versions.
** Please read this message in its entirety before responding ** 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 repro. Version: 6.0.0.0.alpha1+ Build ID: 1f8c3e3b78e0abb96d06a51eca354ae7ade5deb2 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: group build from 2017-11-01
This has been reported in Ubuntu (https://launchpad.net/bugs/1772430) and I can reliably reproduce the issue with 6.0.6 and 6.1.0.
Dear bugzilla, 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 on: Version: 6.3.1.2 (x64) Build ID: b79626edf0065ac373bd1df5c28bd630b4424273 Threads CPU : 4; OS : Windows 6.3; UI Render : par défaut; VCL: win; Locale : fr-FR (fr_FR); Langue IHM : fr-FR Calc: threaded
*** Bug 127556 has been marked as a duplicate of this bug. ***
Dear bugzilla, 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://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
I just observed this bug in LibreOffice 7.3.2.
Dear bugzilla, 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
I can reproduce this bug today with the following. Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 16; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US 24.2.2-3 Calc: threaded
Created attachment 193881 [details] Screenshot of Hebrew 95% proportional line spacing This is not limited to English, nor to small values. Here you can see it affecting Hebrew noticeably at 95% proportional line spacing.
*** Bug 161053 has been marked as a duplicate of this bug. ***
(In reply to raal from comment #3) > This seems to have begun at the below commit in bibisect repository/OS > bibisect-44max. > Adding Cc: to Michael Stahl ; Could you possibly take a look at this one? > Thanks > 21e12db3d1ea89affb3f5c97bf3625a8be70f1a7 is the first bad commit > commit 21e12db3d1ea89affb3f5c97bf3625a8be70f1a7 > Author: Matthew Francis <mjay.francis@gmail.com> > Date: Sun Mar 15 04:52:13 2015 +0800 > > source-hash-4e223fab04279c3583689e69fa1342966e81de36 > > commit 4e223fab04279c3583689e69fa1342966e81de36 > Author: Michael Stahl <mstahl@redhat.com> > AuthorDate: Wed Oct 29 23:50:21 2014 +0100 > Commit: Michael Stahl <mstahl@redhat.com> > CommitDate: Thu Oct 30 15:56:07 2014 +0100 > > fdo#79602: sw: fix text formatting of proportional line space < 100% > > SwTxtFormatter::CalcRealHeight(): Apply the special treatment of < > 100% > line space shrinking the Height() of the line only to the first line > in a paragraph; the subsequent ones are shrunk again (to the square > of > the desired proportion) 30 lines later. > > Also set the Ascent of the line, as the wrong base-line causes the > lower > part of the line to be clipped. > > (regression from 42532d42bfcdb12df86376cda009e8e315a82153) > > Change-Id: I0424396263293deaa318c80eedc2237cdb01b22b