Description: Running LibreOffice 5.2.3.3 (x64) release, build ID d54a8868f08a7b39642414cf2c8ef2f228f780cf, on Windows 10 Pro x64, gives invisible fonts output when trying to export as PDF. I used the open source Merriweather Sans font family, available at "https://www.fontsquirrel.com/fonts/merriweather-sans" and only the Book and Regular variants were exported correctly: Bold, Italic, Bold Italic, Extra Bold, Extra Bold Italic don't appear. Also, the exported text is scrambled on parts of the PDF when trying to select, copy and paste the text inside the PDF. There is a similar bug with the Aller font at "https://www.fontsquirrel.com/fonts/aller", but it happens only when printing (PDF Export is always correct) and sporadically. I don't know how to reproduce it. Steps to Reproduce: 1. Install the Merriweather Sans font family (all of them) on Windows. 2. Open LibreOffice Writer and edit an existing document with Merriweather Sans font family and format some of the text as the font variants. 3. Sometimes the PDF is exported correctly, sometimes not. Actual Results: After the document start to be exported incorrectly once, every time it is exported there will be invisible fonts on the exported PDF. It depends if the document already has Merriweather Sans Book on it and later some characters are formatted as Book Italic, Regular, Italic, Bold or Bold Italic. Expected Results: LibreOffice should export a document as PDF just as it shows on the screen. Reproducible: Sometimes User Profile Reset: No Additional Info: I attached the documents I used to test the bug and created two PDFs, one by exporting as a PDF and the other by printing with PDF Forge virtual printer (http://download.pdfforge.org/). Although using a virtual printer is an easy workaround, there are people unaware of this bug that may send the incomplete documents. I was lucky I started previewing the PDFs after I noticed some printed documents had characters missing from a font I use on the Page Header, or else I wouldn't discover the invisible fonts on the middle of a PDF. That could have caused a lawsuit to be lost as the judge wouldn't have read the PDF correctly on the electronic process of law. User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:3.0) Goanna/20161201 PaleMoon/27.0.2
Created attachment 129434 [details] document where this bug appears
Created attachment 129435 [details] exported PDF from original document where this bug appears
Created attachment 129436 [details] PDF generated with a virtual printer
Created attachment 129437 [details] contents of the exported PDF when copy-pasted from SumatraPDF
Clarification: If the document was already saved on disk, or created another from its copy before it was opened for editing, and it already was used the Merriweather Sans Book on it and later it was used the other variants as Book Italic, Regular, Italic, Bold, Bold Italic, Extra Bold, Extra Bold Italic, then the exported PDF would have invisible text on it, as only the Regular and Book variants from the font would appear on the exported PDF.
Created attachment 129438 [details] This is a document with many fonts and always trigger this bug on my system. I has other open source or freeware fonts which I'll add the download locations on a comment
Don't have Merriweather fonts installed, but font fallback remains challenged through 5.2 builds, perhaps see if the new HarfBuzz layout and reworked font handling for the 5.3.0 and current master behave better for you. On a Windows 8.1 Pro 64-bit en-US system with recent master Version: 5.4.0.0.alpha0+ Build ID: a238c829b209d0708714aa753fb686525411825f CPU Threads: 8; OS Version: Windows 6.29; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-12-08_10:37:27 Locale: en-US (en_US); Calc: CL The PDF is generated with clean font fall back. While on the same system a 5.2.3.3 build chokes on the export.
I attached a relatively complex document which uses other fonts and always trigger this bug on my system. The used fonts are: Aller - https://www.fontsquirrel.com/fonts/aller Asap - https://www.fontsquirrel.com/fonts/asap Merriweather Sans - https://www.fontsquirrel.com/fonts/merriweather-sans Open Sans - installed with LibreOffice Permian Sans - https://www.fontsquirrel.com/fonts/permian-sans Permian Slab - https://www.fontsquirrel.com/fonts/permian-slab I also attached an exported PDF which shows some of the characters formatted with Aller as missing (one can see on the top of the first page the sentence "AEIOU & ABCDEF Advogados" is incomplete).
Created attachment 129439 [details] exported PDF from complex document which triggers this bug On this file, even some characters (but not all) formatted with Aller font are missing.
(In reply to João Paulo from comment #8) > I attached a relatively complex document which uses other fonts and always > trigger this bug on my system. The used fonts are: > > Aller - https://www.fontsquirrel.com/fonts/aller > Asap - https://www.fontsquirrel.com/fonts/asap > Merriweather Sans - https://www.fontsquirrel.com/fonts/merriweather-sans > Open Sans - installed with LibreOffice > Permian Sans - https://www.fontsquirrel.com/fonts/permian-sans > Permian Slab - https://www.fontsquirrel.com/fonts/permian-slab > > I also attached an exported PDF which shows some of the characters formatted > with Aller as missing (one can see on the top of the first page the sentence > "AEIOU & ABCDEF Advogados" is incomplete). I was downloading the 5.3 Beta 3 at "http://dev-builds.libreoffice.org/daily/libreoffice-5-3/Win-x86_64@62-TDF/2016-12-08_16.10.30/" to test this issue and couldn't reproduce it after I installed it on my system. Maybe 5.3 Dev have it solved?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170628
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170727
I tried it on LibreOffice 5.3.6.1 x64 on Windows Pro x64 (build 15063.540) and couldn't reproduce it anymore. I think the bug was solved when LibreOffice was updated to version 5.3.
OK then -> WFM