The formatted text (italic) in odt file, kept the exact same formatting in the versions LO 3x, 4x, 5x, also in OO 3x and 4x.
After the update to LO 18.104.22.168 the same file opened has a drastically changed formatting of one line in italic. All changes the structure of the document. No visible/known changes in the formatting, same parameters.
Steps to Reproduce:
1. Type a full length line in LO Writer 4.x or 22.214.171.124, using Palatino Linotype font type;
2. Change it to italic,
4. Open in the newest LO 126.96.36.199 Writer
The same line is much longer in 188.8.131.52 Writer.
Effect is that a carefully designed booklets change the layout, formatting, and so on.
There should be no difference in line length, as it has been for years.
User Profile Reset: Yes
Keep the same way of displaying and rendering the fonts as it dit for years.
Created attachment 161147 [details]
The difference between the versions.
There are subtle differences in how the operating system and window manager will render text--e.g. handling the font metrics for font height and leading, likewise font ligatures and OTF/Graphite smart font features. Could have some impact here.
But start with a direct examination of the document. You can do it with a "Zip" utility--an ODF archive is just a .zip file; but you'd have to spend a little more time figuring out the folder structure and configuration.
Work against a copy of the original, and from LO 6.4.4 or 7.0.0 'save as' Flat ODF. That will allow you to conveniently examine the various formatting in the document with a text editor like NotePad++ or similar.
Likewise you can install in parallel  one of the older LO release builds . With that accomplished, again open a copy of the original in that build--and save as Flat ODF.
You can then examine the text spans and ODF structure side-by-side for any differences in formatting or styles that may be affecting layout in current builds of LibreOffice
Good luck and let us know what you find, or if you need more assistance.
Thanks a lot Stuart.
I know about .zip files, use this feature on daily basis, easier to copy styles or changing colors in files.
Will let you know what N++ says :)
Regarding system/rendering. So far, if it is open in older version, 5x or so, works fine.
Also, if it is open in OpenOffice Writer, 4.1.7, also fine on Win 10 and 8.1.
Therefore, the only changing factor is the software itself, not system rendering, graphic card and so on.
Hence, this part you can consider clear: the system/hardware does not influence this change. It is sofware rendering, I believe. If so, there should be an official warning then:
"As of XXX version you can loose some of your formatting" or so.
A sample file would be nice :-). The default font rendering changed with LibreOffice 5.3. So if 5.2 is good and 5.3 is 'bad' ..
(In reply to Telesto from comment #4)
> A sample file would be nice :-). The default font rendering changed with
> LibreOffice 5.3. So if 5.2 is good and 5.3 is 'bad' ..
This might be the clue, I use on Vmware Win XP with 184.108.40.206 for printing (HP drivers issue :)
will check it out on 5.3 then.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to Telesto from comment #4)
> A sample file would be nice :-)
Created attachment 161337 [details]
Example file with too long line
I kept the cover, as this is style "first page", so I did not change the structure of the document.
See on page 1, the line starting with "Prices...", for years it's been in one line.
It is also visible on page 3, same line, it's different point of the offer.
So we have around 17 such pages which now have one line more in due to "new rendering".
I've opened you file in LO 220.127.116.11alpha1 and also in LO 18.104.22.168, but couldn't see a difference.
(In reply to Dieter from comment #9)
> I've opened you file in LO 22.214.171.124alpha1 and also in LO 126.96.36.199, but
> couldn't see a difference.
LO 5.3 - absolute disaster with font rendering compared to <5.2, not only this one case with Palatino Linotype italic, but also with Trajan Pro and other fonts.
This might be the result of the change in font rendering issue since 5.3, as mentioned above by Telesto. Therefore, 5.4 would keep this new rendering.
LO 7.0, I am curious - was the line "Prices..." taking two lines? Or was it in one line?
The latter would be great.
(In reply to Piotr from comment #10)
> LO 7.0, I am curious - was the line "Prices..." taking two lines? Or was it
> in one line?
> The latter would be great.
No, also two lines. From your initial bug report I thought, 5x is fine, but didn't see that only 5.1 has been good. Sorry.
(In reply to Dieter from comment #11)
> (In reply to Piotr from comment #10)
> > LO 7.0, I am curious - was the line "Prices..." taking two lines? Or was it
> > in one line?
> > The latter would be great.
> No, also two lines. From your initial bug report I thought, 5x is fine, but
> didn't see that only 5.1 has been good. Sorry.
Thanks, Dieter, that sets me somehow, as I know what to implement.
Here is another hint, and the bug, actually:
this "new" rendering, since 5.3 is somehow badly calibrated.
take the example .odt file here, mark all the line "Prices..." > Character > Position > set Kerning to -0.1 pt (the lowest possible).
The whole line shrinks around 17%. From a DTP point of view this is absolutely a disaster, if 0.1 pt kerning affects the line that much. Never seen something like this, and I worked on Ventura, PageMaker, Word Perfect and mostly, on OO and LO Writer.
My guess is, these are the programmers who are working on LO, glory to them, but the software is used by people like me, from DTP. And the programmers naturally cannot know how DTP should work.
So this is the whole thing with rendering too much or whatever, I am not a programmer. :)
OK, an issue against Harfbuzz but I think where we left things is that can't do much more until bug 103322 is solved.
LibreOffice now uses unhinted glyph advances instead of hinted ones. Unhinted glyph advances are stable and don’t change based on OS or hinting settings, so that line breaks are stable. Current behavior should match MS Office (ligatures might need to be enabled in MS Office or disable is LO to get the exact same line breaks, since the default differs in both).
The bad inter-charcter spacing is related to bug 103322, but orthogonal to the line breaking. Fixing bug 103322 will not change the line breaks.