Bug 116664 - installing 5.4.5.1 completely messed up typeface and lines in a document just created
Summary: installing 5.4.5.1 completely messed up typeface and lines in a document just...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.4.5.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-27 16:50 UTC by David Edwards
Modified: 2018-06-04 09:19 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
images of document as it should be from saved pdf and as 5.4.5.1 opens it. (71.75 KB, application/pdf)
2018-03-27 17:01 UTC, David Edwards
Details
report which opens correctly in 5.3.3.2 (21.31 KB, application/vnd.oasis.opendocument.text)
2018-03-27 18:25 UTC, David Edwards
Details
report which still needs some correcting in 5.3.3.2 (23.64 KB, application/vnd.oasis.opendocument.text)
2018-03-27 18:26 UTC, David Edwards
Details
pdf of doc still requiring correction when opened in 5.3.3.2, made yesterday with earlier LO (81.33 KB, application/pdf)
2018-03-27 18:28 UTC, David Edwards
Details
an older example as requested (72.11 KB, application/vnd.oasis.opendocument.text)
2018-03-30 18:44 UTC, David Edwards
Details
another, slightly older (50.17 KB, application/vnd.oasis.opendocument.text)
2018-03-30 18:47 UTC, David Edwards
Details
LibreOffice 6.1 master (95.17 KB, application/pdf)
2018-05-02 09:42 UTC, Xisco Faulí
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Edwards 2018-03-27 16:50:47 UTC
Description:
I updated LibreOffice so as to have the best & most secure version while working on a report using a standard form copied from document to document for years. Before I never had any problem with it. 5.4.5.1 completely altered typeface and messed up line returns. It radically degraded the document. I will now uninstall and will try to revert to an older version, hoping to recover correct functioning. Very surprised at this - as if standard typefaces lost or not properly interpreted when it opens the document. I had already saved a pdf of the document so there is a record of the degradation. I will try to use the add an attachment feature to send the images of pdf and LO 5.4.5.1 versions.

Steps to Reproduce:
1.open the document
2.
3.

Actual Results:  
All I did was open the file, to be horrified by what I saw.

Expected Results:
typefaces and layout altered (degraded)


Reproducible: Always


User Profile Reset: No



Additional Info:
Produced a document that looked exactly as it did in the previously installed version of Writer.

Version: 5.4.5.1 (x64)
Build ID: 79c9829dd5d8054ec39a82dc51cd9eff340dbee8
CPU threads: 4; OS: Windows 6.19; UI render: default; 
Locale: en-GB (fr_FR); Calc: group


User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 OPR/52.0.2871.37
Comment 1 David Edwards 2018-03-27 17:01:05 UTC
Created attachment 140918 [details]
images of document as it should be from saved pdf and as 5.4.5.1 opens it.

The correct version is at the top of the image. The police was simply Times Roman as I remember, nothing unusual. I find this degree of mishandling of the file difficult to comprehend. It has been fine in version after version of Writer.
Comment 2 David Edwards 2018-03-27 17:36:43 UTC
I have installed 5.3.3.2 and it correctly opens the address, but transforms the telephone numbers and email websites lines into Liberation Serif, and the word 'websites' to 14 point from 12. If I change these back to Times New Roman 12 point the document displays correctly. Maybe I have to revert to an even earlier version to get it to open without need for these modification. I think I had 5.2.7.something before, when I did not have any of these problems.
Comment 3 V Stuart Foote 2018-03-27 18:14:37 UTC
Please attach .ODF document and a PDF of document with original style/fonts assigned.

There have been substantial changes to Windows font handling 5.2 -> 5.3 -> 5.4

And legacy bitmap fonts, and PS Type 1 fonts have been dropped.

Unmanaged font substitution for invalid fonts can cause this type of visual change as replacement fonts often will not have matching metrics and the document composition will change.
Comment 4 David Edwards 2018-03-27 18:25:25 UTC
Created attachment 140920 [details]
report which opens correctly in 5.3.3.2
Comment 5 David Edwards 2018-03-27 18:26:45 UTC
Created attachment 140921 [details]
report which still needs some correcting in 5.3.3.2
Comment 6 David Edwards 2018-03-27 18:28:31 UTC
Created attachment 140922 [details]
pdf of doc still requiring correction when opened in 5.3.3.2, made yesterday with earlier LO
Comment 7 V Stuart Foote 2018-03-27 19:42:24 UTC
Font replacement Liberation Serif for Times occurs on Windows 10 Ent 64-bit en-US (ver 1709) with
Version: 6.0.3.1 (x64)
Build ID: 62abb169b0efa1520d7bee1f586865354060b989
CPU threads: 8; OS: Windows 10.0; UI render: GL; 
Locale: en-US (en_US); Calc: group

But document is reasonably formatted, none of the mono-spacing shown in attachment 140918 [details]
Comment 8 David Edwards 2018-03-27 19:58:42 UTC
Thanks for this. It looks as if the end of your remarks was lost. 

Does what you say mean that I have to revert to an even earlier version of LO and stay with it or have to manually reformat everything that is in Times Roman? It is a very commonly used font and I will be perpetually annoyed if the LO/Win 10 64 combination alters it all to the horrible Liberation Serif. Out of interest, is the 'fault' (and in consequence I suppose the remedy) with Windows or LO?
Comment 9 V Stuart Foote 2018-03-27 22:24:17 UTC
(In reply to David Edwards from comment #8)
> Thanks for this. It looks as if the end of your remarks was lost. 
> 

Its just the link to the first pdf attachment with the screen clips.

> Does what you say mean that I have to revert to an even earlier version of
> LO and stay with it or have to manually reformat everything that is in Times
> Roman? It is a very commonly used font and I will be perpetually annoyed if
> the LO/Win 10 64 combination alters it all to the horrible Liberation Serif.
> Out of interest, is the 'fault' (and in consequence I suppose the remedy)
> with Windows or LO?

No, Liberation Serif is metric equivalent to Times New Roman, while Liberation Sans is metric equivalent to Arial.  

The issue looks to be in the styles applied to the ODF documents--they were incomplete and so LibreOFfice defaults get applied.

attachment 140921 [details] shows meta as authored with
LibreOffice/5.2.7.2$Windows_X86_64

attachment 140920 [details] shows meta as authored with
LibreOffice/5.3.3.2$Windows_X86_64

So, suspect problem predates these builds of LibreOffice and these versions of the file "reports". 

One more sage with replacing ODF styles would need to comment (Regina?), but believe issue is that there is no font assignment to the "Police_20_par_20_défaut" and "Internet_20_link" styles across multiple text spans in the content, you pick up current LO defaults. 

I think we would probably need even older versions of the files to see what the original style specified for font. Then in Writer (or other affected module) use Tools -> Options -> LibreOffice Writer:  Basic Fonts (Western) dialog to adjust the defaults. Pick a better font (old bitmap fonts like "roman", or PostScript Type 1 fonts if installed will not show on the list box) that renders the reports without too much distortion.

Going forward, work up a better Style to apply to the paragraphs of the reports.
Comment 10 David Edwards 2018-03-27 23:22:30 UTC
Thanks. I shall have to do some research to understand all this erudite detail. I think the original address, website, etc. information would have been copied from a colleague's Word original - years ago.

5.3.3.2 is what I have installed now and 5.2.7.2 will be what I had yesterday. Up until today's installation of 5.4.5.1 the Times Roman fonts opened as Times Roman and everything looked as it should. I have probably been using these documents (one as a template for the next) for about four or five years.

Hopefully if I recreate all the top part of the page (common to all the reports I'll create) afresh in LO, things should be OK henceforth. But it would seem there has been a step backwards in compatibility if documents with elements imported from Word which used to display properly no longer do so.
Comment 11 Timur 2018-03-30 10:36:47 UTC
I didn't look into files, but this must be decided: if bug then we must know what exactly needs to be changed based on experienced/expected results (and I can't see it defined) or this can be closed (preferably with David's consent).
Comment 12 David Edwards 2018-03-30 10:50:52 UTC
I am not a technically competent person - what I was flagging up was that a document using Times Roman which in previous iterations of LO opened in Times Roman and had correct line lengths etc. in the latest version of LO opened in Liberation Serif with altered spacing and a line which ran on. Lower down it opened in something which looked more like typewriter script. As in the past this document always displayed correctly I felt something was wrong. If for you this behaviour of LO is correct/normal there's no bug. The fact is that it now alters the document, requiring correction of the font and spacing whereas in the past this was not necessary. As I probably originality imported the address etc from a Word document, some compatibility appears to have been lost. But it sounds as if this reflects a decision made as to how to deal with certain fonts and for you it's normal.

My instinct as a user would be to go back to an earlier version of LO where these problems don't occur, whilst not liking doing that. (Interestingly the one I picked at random 5.3.3.2 causes big delays in scrolling in a large Calc file (>20 000 lines) so I shall probably go back further, to 5.2.7.2 !)

But if you want to say it's not a bug and close it, that's OK by me. I'm not competent to argue!!
Comment 13 V Stuart Foote 2018-03-30 13:21:29 UTC
(In reply to David Edwards from comment #12)
> ...
>
> My instinct as a user would be to go back to an earlier version of LO where
> these problems don't occur, whilst not liking doing that. (Interestingly the
> one I picked at random 5.3.3.2 causes big delays in scrolling in a large
> Calc file (>20 000 lines) so I shall probably go back further, to 5.2.7.2 !)
>
> ...

Actually, before you do that, we really do need to understand the cause of the formatting changes. It probably is a font replacement issue gone awry (either a PS Type 1 or a bitmap font), but that has already happened in the two example files you'd posted.

We won't be able to do much for dropping those fonts--but there may be a chance to manage the filter import font assignment to the resulting styles for the documents.

To do that we need a couple of your older documents, hence the NEEDINFO. If you have some reports from several years ago. You can open a document archive, it is just a zip file, in a Zip utility and look at the the "meta.xml" file to identify what version of LibreOffice or OpenOffice had created the ODF document. 

p.s. in a bit of irony, the scrolling issues in Calc were also a DirectWrite font handling issue that has been fixed in more recent releases (5.3.7 or 5.4.3 w/default GDI rendering bug 112486, or 5.4.4 for OpenGL rendering bug 113347).
Comment 14 David Edwards 2018-03-30 13:31:21 UTC
Oh, sorry - I already installed 5.2.7.2, which indeed solved the scrolling problem.

But I will have some old reports of this type, and presumably if I don't open them they will not be transformed in any way and give you the information you need. 

I'll try to send what you ask for. (I am busy working on other matters right now, so it may be a few hours before I can get round to it; I hope that's OK. If I need to temporarily update to the latest version again for any reason, I'll do that too of course.)
Comment 15 David Edwards 2018-03-30 18:44:29 UTC
Created attachment 140987 [details]
an older example as requested
Comment 16 David Edwards 2018-03-30 18:47:06 UTC
Created attachment 140988 [details]
another, slightly older
Comment 17 David Edwards 2018-03-30 18:48:35 UTC
I didn't really understand how to open an archive and Zip the files so I hope simply sending you a couple of older ones will help.
Comment 18 V Stuart Foote 2018-03-30 19:16:16 UTC
(In reply to David Edwards from comment #15)
> Created attachment 140987 [details]
> an older example as requested

That was last edited in LO 4.3.2.2 2014-12-03

(In reply to David Edwards from comment #16)
> Created attachment 140988 [details]
> another, slightly older

and that was last edited in LO 3.4 2013-06-26

Should be what we need.

Thanks!
Comment 19 Xisco Faulí 2018-05-02 09:42:29 UTC
Created attachment 141830 [details]
LibreOffice 6.1 master

I can't reproduce the problem in

Version: 6.1.0.0.alpha1+
Build ID: 43af818557904450b13839350c65ad865b9ee9d2
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Comment 20 Xisco Faulí 2018-05-02 09:43:35 UTC
Same behaviour in

Version: 6.0.3.2
Build ID: 1:6.0.3~rc2-0ubuntu0.16.04.1~lo2
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 21 David Edwards 2018-06-03 13:13:07 UTC
Heavens! Sorry for forgetting about this in the pressure of work.
Last night I installed 6.0.4.2 and have just opened one of the reports saved in 2015 - and it's fine. So certainly the latest version does not produce the problem. I have not gone back and tried with whatever the link you supplied would provide, but I guess it's not necessary and that this answers your question.

Again, many apologies for very late response,
David
Comment 22 Xisco Faulí 2018-06-04 09:19:34 UTC
Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.