Attached are two PDFs with embedded urw-core35-fonts of two different versions. Somehow LO does not embeded the fonts of new version correctly anymore for AT LEAST latin alphabets with grave accent. According to a ghostscript dev, this might have something to do with differences array for the encoding. Although this happen only to fonts get updated in the latest version, it doesn't seem like it's an issue of the fonts themselves, since others programs (goffice, chromium, firefox...) seem to have no problem on embedding them. Since this is the commit of the fonts the problem occurs: http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commit;h=c983ed400dc278dcf20bdff68252fad6d9db7af9 And this is the last commit working with LO: http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commit;h=e5b3fce0aadb091699b409be325468c682bd436d The two attached PDFs are produced with them respectively.
Created attachment 119822 [details] problematic embedding
Created attachment 119823 [details] working embedding
Created attachment 119831 [details] broken pdf from LO with one string in Roman Regular For easier debugging
Created attachment 119832 [details] working pdf from LO with one string in Roman Regular For easier debugging
Created attachment 119848 [details] broken pdf from LO with one string in Roman Regular uncompressed with `qpdf --stream-data=uncompress`
Created attachment 119849 [details] working pdf from LO with one string in Roman Regular uncompressed with `qpdf --stream-data=uncompress`
Created attachment 119850 [details] fixed roman.pdf by replacing/injecting objects It seems like LibreOffice has always been including useless BaseFont and CMap objects. Since they the only ones roman.pdf have, the font cannot be rendered correctly. But in roman-old.pdf, extra useful BaseFont, Encoding and CMap objects are included in addition so the pdf works fine. Since the embedded font stream is fine, as long as I put the useful objects into roman.pdf, it will basically work again. Attached is a fixed version of roman.pdf created with simple editing in emacs. I just replaced the BaseFont and CMap objects, added the Encoding object, change the relevant object indexes; I also need to change "<E0>2<E8>-5<EC>3<F2F9>" to "<00>2<01>-5<02>3<0304>" in object #5. Somehow LO no longer includes the useful objects when it deals with the newer version of fonts. Also see this bug report: http://bugs.ghostscript.com/show_bug.cgi?id=696263
I have such a bug when using Nimbus family font and 5.1.1.3 version.
(In reply to David Kremer from comment #8) > I have such a bug when using Nimbus family font and 5.1.1.3 version. However, with most of the family fonts I used, everything went fine except the Nimbus one.
(In reply to David Kremer from comment #8) > I have such a bug when using Nimbus family font and 5.1.1.3 version. Close enough, so setting to NEW
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Support for Type 1 fonts was dropped a few versions ago.