Summary: | Font not being rendered in evince 3.22.1-3 | ||
---|---|---|---|
Product: | poppler | Reporter: | shirishag75 <shirishag75> |
Component: | cairo backend | Assignee: | poppler-bugs <poppler-bugs> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | shirishag75 |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | pdf document about music industry |
For the record, the PDF comes from http://www.politicalavenue.com/108642/US-MAGAZINES/Music%20Tech%20-%20October%202016.pdf (see http://unix.stackexchange.com/q/335466/86440 for the brief discussion which led to this bug report). -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/184. |
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.
Created attachment 128796 [details] pdf document about music industry I downloaded a pdf file and have unable to view it properly in evince 3.22.1-3 in Debian stretch, although the same document is rendered perfectly in okular. Have shared the pdf document. ─[$] pdffonts Music\ Tech\ -\ October\ 2016.pdf [1:13:40] Syntax Warning: Could not parse ligature component "facebook" of "facebook_sign" in parseCharName Syntax Warning: Could not parse ligature component "sign" of "facebook_sign" in parseCharName name type encoding emb sub uni object ID ------------------------------------ ----------------- ---------------- --- --- --- --------- OUYRDP+Akkurat Type 1C WinAnsi yes yes no [none] TGDSFA+OpticalBeta Type 1C Custom yes yes no [none] PVKQNR+Akkurat-Bold Type 1C WinAnsi yes yes no [none] OGKWQO+DINOT-CondBold Type 1C WinAnsi yes yes no [none] QSWCQY+DINOT-CondLight Type 1C Custom yes yes no [none] EOEYOT+Akkurat-Bold-Identity-H CID Type 0C Identity-H yes yes no [none] QKRTJM+Akkurat-Light Type 1C WinAnsi yes yes no [none] SECIQX+Akkurat-LightItalic Type 1C WinAnsi yes yes no [none] VOWOQW+DINOT-CondBold-SC700 Type 1C WinAnsi yes yes no [none] ZSFBVW+OpenSans-Bold Type 1C Custom yes yes no [none] Hope the above helps