Description: The amount of expanded spacing between characters is affected by non-base characters, such as diacritical marks Steps to Reproduce: 1. Install David CLM font (available as fonts-hebrew package or at culmus.sf.net) 2. Open the attached ODT file 3. Observe different spacing between the two lines of text Actual Results: Line 1 is more expanded than line 2, despite having the same letters Expected Results: Line 1 should have the same total length as line 2 Reproducible: Always User Profile Reset: No Additional Info: Looks like non-base characters (diacritical marks under the letters) affect the spacing between characters, while in fact they should be ignored Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; Locale: he-IL (en_US.UTF-8); Calc: group User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Created attachment 138599 [details] Demo ODT document
Created attachment 138600 [details] Bug screenshot
Created attachment 138601 [details] Bug screenshot
Can you test with 5.4.4 to see, if the problem remains? A quick way is to use an AppImage http://libreoffice.soluzioniopen.com/ Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Reproduced with AppImage "full" 5.4.4.2
I can confirm with Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) and 6.1; Linux
Still seeing this with Version: 6.2.0.0.beta1 Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18 CPU threads: 4; OS: Linux 4.9; UI render: default; VCL: gtk3; Locale: en-US (en_IL); UI-Language: en-US
Dear Maxim Iorsh, 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
Bug still manifests with: Version: 7.1.0.3 / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 4; OS: Linux 5.9; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US Drats!
Appears fixed in 7.4.2.3
Appears fixed Version: 7.4.2.3 / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: he-IL (he_IL.UTF-8); UI: en-US Calc: threaded
This got fixed somehow, as it was indeed a bug even last year. So changing resolution. And also verifying - the bug does indeed seem to be gone now.
(In reply to Eyal Rozenberg from comment #12) > This got fixed somehow, as it was indeed a bug even last year. So changing > resolution. And also verifying - the bug does indeed seem to be gone now. We don't know the commit, so we use worksforme resolution.