Description: When using some fonts it is almost indispensable to alter the line spacing. For instance, this is the case with the Adobe Source Sans 3 font that in LibO gives an extremely loose distance between lines. Unfortunately, when adjusting the line spacing (e.g., to proportional 80%), the alignment of bullet points to the text in bullet lists gets lost. With a reduced line spacing, the bullet appears too high. The opposite occurs with an enlarged line spacing. This is particularly visible in presentations. Steps to Reproduce: 1. Open a new presentation 2. Insert some text in the slide space where a bulleted list is pre-arranged 3. Change the formatting to use a font with a loose line spacing (e.g. Source Sans 3) 4. Fix the line spacing with paragraph properties, reducing it Actual Results: See the bullet loosing the vertical alignment to the text going too high Expected Results: The bullet should stay aligned to the text Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: PresentationDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
Created attachment 179087 [details] Screenshot showing the issue Note that both the dash and the round circle are too high wrt the following text. Setting the line spacing to 100% fixes this issue, but gives a too loose line spacing with this font.
Created attachment 184458 [details] Example file with Source Sans Pro
Bibisected with linux-64-6.1 to https://git.libreoffice.org/core/commit/a7e6e4b220089a2d8a58ff10393d598a8b796fa5 tdf#114628 correct line spacing for impress Still repro with Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 88ebc324a51f16df0248d6a0d53d2169b1995dda CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Jumbo Built on 3 January 2023
Just noted that also the text cursor is vertically misaligned in this case.
Dear Callegar, 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