Created attachment 118307 [details] Test document with password as rahu8152 Hi, While discussing a bug in Okular, it seems that the bug lies in poppler. I have a document which shows blank contents when rendered with Okular whereas is perfectly rendered using Google Chrome. I have attached the document and the screenshot of the document as rendered by google chrome. The bug discussion for Okular can be seen at https://bugs.kde.org/show_bug.cgi?id=352697 Okular version : 0.20.0 Poppler version: 0.26.5
Created attachment 118308 [details] Google Chrome's rendered document snapshot
Freetype doesn't want to render one of the fonts attached, i've asked them if the file can be made to work or we should workaround it.
The document is malformed, has an embedded font that is not valid. i thought we had a "if freetype can not open font default to doing font substitution", but it seems not? Probably a patch to fix this would also fix https://bugs.freedesktop.org/show_bug.cgi?id=92048
Hi all, Please find the discussion from Albert's query to FreeType developers. http://lists.gnu.org/archive/html/freetype-devel/2015-09/msg00025.html The embedded font lacks "hmtx" table which TrueType and PDF spec classified as required table, so it should not be loaded. FreeType2 developers think such font is dealt as unusable. In fact, Adobe Reader complains as some resources of the PDF could not be loaded, and the most texts are not displayed. I'm afraid that Chromium browser silently substitutes the incompletely-embedded font and display the text by other fonts. I will check how Chromium handles the incompletely-embedded fonts.
The patch for bug 92048 solves also this bug in the splash backend.
*** This bug has been marked as a duplicate of bug 92048 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.