Description: I get spurious line breaks in the footer of a letter template I have. This is a regression. LO 5.1 used to get those line breaks correctly. Actual Results: Expected Results: Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
Created attachment 132849 [details] The document in question
Created attachment 132850 [details] The document as rendered by LO 5.1.3
Created attachment 132851 [details] The document as rendered by MSOffice
Created attachment 132852 [details] The document as rendered by LO 5.4.0.0.alpha0+
The problem is in the footer. In the center block that starts with 'Besucheradresse', LO 5.4 has spurious line breaks, e.g., in front of the '14'. Also, the phrase "Kein Zugang für..." should be on a single line, but is actually on two.
Hi Oliver, Thanks for filing. I see the same problem in version 4.4.7, 5.1.6, and a recent master-build. The issue is that the font is not available and the chosen replace font has a different rendering, so that the lines do not fit in the give width of the frames. Is attachment 132850 [details] / 5.1.3 on the same computer as the other one?
To be honest I am not absolutely certain anymore. When filing the bug I was thinking that all LO renderings are from the same (Linux) machine. But now that I think of it the LO 5.1.3 one may actually come from a windows machine. And thinking of it some more: that particular windows machine does have the missing font, and my Linux one doesn't. If the font replacement really is the culprit, is there anything that can be done? The original font is proprietary, and it is to be expected that many people at my institution will want to use the document without having to install the font first.
I installed the missing fonts, and indeed the problem disappears. I don't know enough about fonts to judge whether this is a bug nonetheless. Feel free to deal with it as you please. Thanks!
(In reply to Oliver Sander from comment #8) > I installed the missing fonts, and indeed the problem disappears. thanks for testing and reporting! > I don't know enough about fonts to judge whether this is a bug nonetheless. > Feel free to deal with it as you please. Thanks for confirming Oliver. Proper fonts (original or a replacement with similar metrics..) are - in quite some cases - crucial for proper rendering.