All documents (LO Writer) have been corrupted formatting after upgrade OS to Ubuntu 18.04 LTS. Font metric (Liberation Sans) slightly decrease, consequently on page more strings arranged. For example, on page with settings: A4 (210x297), left border 3cm, right/up/bottom border 1.5cm, paragraph settings without indentations and 1.0 line interval, font settings Liberation Sans 12 - on one page 54 strings can be to place in Ubuntu 17.10 and earlier versions, and 59 string can be to place in Ubuntu 18.04. Therefore in multi-paged documents strings have been flow to up, to other pages, corrupt document formatting. Printing this documents is impossible now!
Font metrics slightly shrinked, on ordinary page can be place slightly more strings than usual
Font metrics exactly equal to ordinary strings
User Profile Reset: No
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Created attachment 141869 [details]
Text example with enumerated strings and pages
Thanks for filing, but need some additional information...
Could be either font metrics (leading / scale), or paragraph metrics (spacing before, after, from printer toggle).
Prepare a test document from prior build--save to "flat" .FODT format, and same from current. Please post them as attachment, and screen clips of on page spacing (seeing text in paragraphs with a background color set is useful here).
Also need the LO installation details, before & now? (Obtain from Help -> About dialog.)
Created attachment 141872 [details]
Screenshot on Ubuntu 17.10 comp
Created attachment 141873 [details]
Screenshot on Ubuntu 18.04 comp
This is the same document. All document settings is the same.
Created attachment 141874 [details]
Text example in FODT format
Created attachment 141875 [details]
Text example in FODT format in Ubuntu 17.10
Created attachment 141876 [details]
Text example in FODT format in Ubuntu 18.04
Hmm, line by line check of the .fodt documents appear identical (just different view ports between them).
And to get similar "shrinkage" of the Default style single space, I had to adjust spacing to be Proportional at 94% on a Windows install of 188.8.131.52
FWIW do notice in the screen clips a change in the rendering engine from VCL gtk2 -> gtk3 between Unbuntu 17.10 and 18.04--is that the difference?
(In reply to V Stuart Foote from comment #9)
> Hmm, line by line check of the .fodt documents appear identical (just
> different view ports between them).
So given the movement of the soft page breaks the different line height calculation as rendered to canvas--and written at the appropriate line in the flat ODF--does seem a valid graphics issue that needs attention.
Thanks for the report. So this can either be that LO calculates the line spacing differently in LO 6 than in LO 5.4.
Or the font metrics have really changed.
From where did you get the Liberation Sans font? I guess it came with your Ubuntu installation?
Can you paste the output of "apt search fonts-liberation" on both systems here? There seem to be two different Liberation packages.
You could also try to run LO 5.4 on 18.04 and see if the behavior is the same.
Feel free to use the appimage versions for that: https://www.libreoffice.org/download/appimage/
On Ubuntu 17.10:
fonts-liberation/artful,artful,now 1:1.07.4-2 all [установлен]
Шрифты с теми же метриками, что и Times, Arial и Courier
fonts-liberation2/artful,artful,now 2.00.1-3 all [установлен, автоматически]
Fonts with the same metrics as Times, Arial and Courier (v2)
ttf-mscorefonts-installer/artful,artful 3.6ubuntu2 all
Установщик базовы TrueType шрифтов Microsoft
On Ubuntu 18.04:
fonts-liberation/bionic,bionic,now 1:1.07.4-5 all [установлен]
Fonts with the same metrics as Times, Arial and Courier
fonts-liberation2/bionic,bionic,now 2.00.1-5 all [установлен]
Fonts with the same metrics as Times, Arial and Courier (v2)
ttf-mscorefonts-installer/bionic,bionic 3.6ubuntu2 all
Installer for Microsoft TrueType core fonts
There is a difference between font version:
Ubuntu 17.10 - 1:1.07.4-2, 2.00.1-3
Ubuntu 18.04 - 1:1.07.4-5, 2.00.1-5
What has changed with fonts?
(In reply to Samuel Mehrbrodt (CIB) from comment #11)
> Thanks for the report. So this can either be that LO calculates the line
> spacing differently in LO 6 than in LO 5.4.
> Or the font metrics have really changed.
Looking at the screenshots, Lant is using the same LibreOffice version in both Ubuntus, the only difference is that one uses gtk2 other gtk3 which I don't think is relevant here
People! Can you open this example document (text example 1st attach) - on other OS's (forex. Windows)? On other office applications (MS Office, OpenOffice etc)?
After `sudo apt remove fonts-liberation`, `sudo apt remove fonts-liberation2`, and installing LiberationSerif-Regular.ttf from Windows box, I have the test document showing 54 lines per page.
* installed font version is 2.00.1; the removed packages have versions 1.07.4 and 2.00.2.
Also, installing libreoffice-gtk2 and starting LibreOffice with gtk2 (`SAL_USE_VCLPLUGIN=gtk libreoffice`) does not fix the problem by itself.
Both Ubuntu Bionic and Debian Sid contain the same 2.00.1-5 version of the package:
... and both contain the TTF fonts having version 2.00.2 (the version bump happened at https://salsa.debian.org/fonts-team/fonts-liberation2/commit/4a51c801d30ff165517563c2375b7540dd06589c; not necessarily this specific commit has something to to with the problem).
So, this isn't an Ubuntu problem (apart from it taking not-thoroughly-tested packages).
Rene: could you raise this against the font package maintainers please?
(In reply to Mike Kaganski from comment #18)
> So, this isn't an Ubuntu problem (apart from it taking not-thoroughly-tested
See also bug 116498 - it is at least _possible_ LibreOffice started to be more sensitive to otherwise benign changes in font tables.
And worth a different bug report - unless LibreOffice itself ships the font (and makes sure it's the first to be used during unit tests), it's probably a bad idea anyway to rely on anything from the system, for something as fragile as Writer layout...
FYI rebuilding the fonts-liberation2_2.00.1-5_all deb with this patch  seems to solve the problem for me, at least under Ubuntu 18.04. So it appears to be the same problem as in Bug 114434.
(In reply to Thorsten Behrens (CIB) from comment #20)
> unless LibreOffice itself ships the font
> (and makes sure it's the first to be used during unit tests), it's probably
> a bad idea anyway to rely on anything from the system, for something as
> fragile as Writer layout...
I politely disagree.
We use many OS-provided functions. And using a font that has a strong guarantee to be metric-compatible with MS fonts (and which thus should provide predictable layout results) seems reasonable. I'd say that if in this case maintainers would not simply ignore the unit test results and silenced the relevant tests , it would be noticed and acted upon earlier. Otherwise, it's unclear why would maintainers want to run unit tests at all - they would only need to ensure that LO simply builds (reasoning that "it's upstream's responsibility to make tests working")? IMO, the tests had shown broken distro support rather early, which is generally important for LO and the impression it produces.
(In reply to Maxim Monastirsky from comment #21)
> So it appears to be the same problem as in Bug 114434.
I forgot to mention that LO on Ubuntu 18.04 shows the same problem with any of the package (1.7, 2.0) installed alone; so the 1.7 packaged fonts must also be affected on Ubuntu.
(In reply to Mike Kaganski from comment #22)
> I politely disagree.
Thx for all the links, indeed this seems silly to do to the Liberation Fonts.
That said - for the LibreOffice developer experience, what we have now is fragile. This sucks, and leads to people ignoring test breakage beyond distro maintainers.
You have a point though wrt distros - if they separate out the fonts into OS packages, _that_ then should be part of any test run (and as you point out would have caught the problem early on). But that's a downstream problem IMO.
FWIW, I checked your document on Windows (with Liberation fonts downloaded from Ubuntu bionic repo):
* MS Word 2013 displays page 2, strings 1-5 on the first page as well
* OpenOffice 4.1.1 displays only strings 1-54 on the first page as expected (although I'm not sure if they bundle their own copy of the Liberation fonts).
I also investigated when this "ReallyUseTypoMetrics" setting was changed in Liberation fonts. It has always been like it is since "first commit" in 2010. I don't know why it changed now in Ubuntu and why it was different before.
Also this isn't related with bug 116498. Using the win metrics here doesn't change anything.
(In reply to Samuel Mehrbrodt (CIB) from comment #24)
> I also investigated when this "ReallyUseTypoMetrics" setting was changed in
> Liberation fonts. It has always been like it is since "first commit" in
> 2010. I don't know why it changed now in Ubuntu and why it was different
See Caolán's comments in rhbz#1526510. It seems that old fontforge versions had a bug which prevented it from reading/writing this bit correctly. So I guess that problems started after debian/ubuntu updated their fontforge to the fixed version, and that version was later used to build the liberation packages.
(In reply to Maxim Monastirsky from comment #25)
> See Caolán's comments in rhbz#1526510. It seems that old fontforge versions
> had a bug which prevented it from reading/writing this bit correctly. So I
> guess that problems started after debian/ubuntu updated their fontforge to
> the fixed version, and that version was later used to build the liberation
Ok, understood, makes sense now.
Then this is a Debian/Ubuntu problem and needs fixing by them.
Closing as NOTOURBUG.
I am using LO-W 1:6.0.3-0ubuntu1 on Lubuntu Next 18.04, and found when opening a previously-created document, that the pages did not line up.
Searching for LO-W bugs that referenced line-spacing, led me to this bug.
It sounded promising, and in reading the information in your site, and following the breadcrumbs, I finally found the debian bug report:
where they reported that the bug had been:
"Fixed in version fonts-liberation/1:1.07.4-6"
The version I had was 1:1.07.4-5
So, I snagged the "cosmic" package (not yet available for "bionic")
and tried it, and it definitely solves the problem.
Thank all of you for investigating this, and helping lead me to a solution!
*** Bug 119892 has been marked as a duplicate of this bug. ***