Created attachment 87337 [details]
An example where the error occurs.
If I write a sentence of more than one line, where the first word is short (e.g. two letters) and then follows an italicised block, and the paragraph is justified, the spacing between the letters of the first word is too wide.
Steps to reproduce:
1. Write a paragraph of more than one line, beginning with a short word and possibly long words at the end of the line to intensify the effect of justification.
2. Justify the paragraph and italicise the first few words starting from the second.
Letters of first word are spaced too widely.
Normal spacing like in the rest of the paragraph.
Operating System: Mac OS X
Version: 184.108.40.206 release
Created attachment 87339 [details]
Incorrect rendering of the example.
thanks for the issue. I do not see the problem (tried with three fonts) on Ubuntu.
Maybe someone else, different OS, has the same problem?
Or could you attach your file?
thanks for the reply. Yes I tried on Ubuntu and the problem doesn't show up.
Probably it's related to this bug, that got fixed:
And it only shows up on LibreOffice 4.1 so that seems to confirm that they are the same issue.
Hi Alessandro..just a ping since it's been reported months ago. Does it still happen in LO 220.127.116.11 or 18.104.22.168 with OSX machine ?
If resolved please change status to RESOLVED WORKSFORME, unless UNCONFIRMED
Created attachment 102359 [details]
Kerning error with LibreOffice 22.214.171.124
(In reply to comment #4)
> Hi Alessandro..just a ping since it's been reported months ago. Does it
> still happen in LO 126.96.36.199 or 188.8.131.52 with OSX machine ?
> If resolved please change status to RESOLVED WORKSFORME, unless UNCONFIRMED
thanks for asking. Unfortunately the bug hasn't been solved yet, as you can see from the screenshot. By the way I can now also confirm it for OpenOffice, which apparently also merged your code, and didn't have the problem at the time I filed the bug report.
Tested ODT under GNU/Linux (FreeType v2.4.9-1.1) using:
v184.108.40.206 OOO330m19 Build: 401
v220.127.116.11 OOO340m1 Build: 602
v18.104.22.168 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b
v22.214.171.124 Build ID: e183d5b
v126.96.36.199 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24
v188.8.131.52 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a
v184.108.40.206 Build ID: 3fd416d4c6db7d3204c17ce57a1d70f6e531ee21
v220.127.116.11 Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d
I do not see the kerning issue reported. These are the versions of Times New Roman used:
- TTF v3.00 from WinXP
- TTF v5.01.3x from MacOS 10.6.8
Issue is possibly specific to the MacOS build.
Dear Owen, thanks for checking. I can confirm again the bug on the latest release (v18.104.22.168 Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d) with my Mac OS installation.
I am now running Mac OS X v. 10.9.4, and I agree this is system dependent as I am not experiencing the same bug under Linux, but if I remember well this behaviour started with an update of LibreOffice (OpenOffice did not show the same bug at the time, now it does, so maybe they imported the buggy code).
I can confirm the bug also on an older version of OSX, but probably not as old as 10.6.8 (I don't remember).
Confirming, this is OSX specific
I see the problem in
Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d
However, the problem isn't present in my master build of LO 440, so it would appear at least to be fixed there.
Created attachment 107172 [details]
Kerning error with LO 4.3.2 and LO nightly 2014-10-1
I don't think the current nightly build is solving the problem although I see that things are moving in the right direction:
As you can see from the attachment I glued together the rendering of the offending file in LO 4.3.2 and the latest nightly build, as well as their PDF outputs.
The latest nightly is at least recognizing that there is an issue with the kerning on OSX, and fixing the problem on the first word, but the rendering of the entire line has now other kerning issues. The "r" in "Ernest" and the "e" in "completely" have very weird kerning.
The PDF output is then totally different and I hope that in the future it will again look like the rendering by LibreOffice.
(In reply to comment #12)
> I don't think the current nightly build is solving the problem although I
> see that things are moving in the right direction:
> As you can see from the attachment I glued together the rendering of the
> offending file in LO 4.3.2 and the latest nightly build, as well as their
> PDF outputs.
> The latest nightly is at least recognizing that there is an issue with the
> kerning on OSX, and fixing the problem on the first word, but the rendering
> of the entire line has now other kerning issues. The "r" in "Ernest" and the
> "e" in "completely" have very weird kerning.
> The PDF output is then totally different and I hope that in the future it
> will again look like the rendering by LibreOffice.
Agreed. I had only looked at the beginning, as this was the initial bug you raised. The PDF export is yet another problem IMHO, for which you should open a separate report.
** 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 on a currently supported version of LibreOffice (5.0.1 or preferably 22.214.171.124 or later)
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
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)
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: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
The bug is still present in LibreOffice 126.96.36.199/MacOS, and I have put the keyword regression since the bug was not present with LO 3.3.
Adding keyword 'bibisectRequest'.
This regression can be bibisected with http://dev-downloads.libreoffice.org/bibisect/mac/Bibisect_MacOSX10.6%2b_lo-4.1_to_lo-4.2.tar.bz2
Created attachment 128529 [details]
No kerning error in latest nightly 2016-11-06
This is fixed by the new layout engine in bug 89870, see screenshot. Kerning in other parts of the text also look fine, not like comment 12
Resolving as fixed
Build ID: 17e9dc436bc6ad8d3a5bbde15d4d47262650aa2c
CPU Threads: 2; OS Version: Mac OS X 10.12; UI Render: default; Layout Engine: new;
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2016-11-06_01:25:01
Locale: en-US (en_NO.UTF-8); Calc: group