Bug 36829 - PDF with non embedded fonts rendered suboptimally
Summary: PDF with non embedded fonts rendered suboptimally
Status: RESOLVED DUPLICATE of bug 94054
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-04 03:19 UTC by Nicola Ruggero
Modified: 2016-02-19 05:01 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
pdf with artifacts (48.41 KB, application/pdf)
2011-05-04 03:19 UTC, Nicola Ruggero
Details
ghostscript result 001 (114.42 KB, image/png)
2011-05-05 00:17 UTC, Nicola Ruggero
Details
Okular result 001 (336.72 KB, image/png)
2011-05-05 00:17 UTC, Nicola Ruggero
Details
ghostscript result 002 (113.89 KB, image/png)
2011-05-05 00:18 UTC, Nicola Ruggero
Details
Okular result 002 (308.38 KB, image/png)
2011-05-05 00:19 UTC, Nicola Ruggero
Details
Example of non-embed Bitstream Charter font where Adobe Acrobat 8.0 opened PDF (31.74 KB, image/png)
2011-05-26 00:42 UTC, Edmund Laugasson
Details
Example how looks original document with Bitstream Charter font. (27.49 KB, image/png)
2011-05-26 00:44 UTC, Edmund Laugasson
Details

Description Nicola Ruggero 2011-05-04 03:19:08 UTC
Created attachment 46312 [details]
pdf with artifacts

Opening the attached PDF (commercial invoice), you can see some artifacts on fonts rendering in 3 specific fields. Specifically the fields "n. fattura", "data fattura" and "totale fattura" contain the problem.

I am using okular with libpoppler 0.16.5.

Running "gs <filename>.pdf" on the same linux machine I can see the PDF correctly.
Comment 1 Albert Astals Cid 2011-05-04 11:06:38 UTC
Can you please attach a screenshot highlighting what you think is wrongly rendered?
Comment 2 Nicola Ruggero 2011-05-05 00:17:21 UTC
Created attachment 46344 [details]
ghostscript result 001
Comment 3 Nicola Ruggero 2011-05-05 00:17:57 UTC
Created attachment 46345 [details]
Okular result 001
Comment 4 Nicola Ruggero 2011-05-05 00:18:39 UTC
Created attachment 46346 [details]
ghostscript result 002
Comment 5 Nicola Ruggero 2011-05-05 00:19:09 UTC
Created attachment 46347 [details]
Okular result 002
Comment 6 Albert Astals Cid 2011-05-07 14:58:02 UTC
It's a PDF that does uses non embedded fonts, the results can be obviously improved but in fact if you want good results in a PDF you need to embed the fonts.
Comment 7 Edmund Laugasson 2011-05-26 00:42:37 UTC
Created attachment 47173 [details]
Example of non-embed Bitstream Charter font where Adobe Acrobat 8.0 opened PDF

The original .odt file has been created using LibreOffice 3.3.2 and Ubuntu Linux 10.04 LTS with all latest updates.
Comment 8 Edmund Laugasson 2011-05-26 00:44:12 UTC
Created attachment 47174 [details]
Example how looks original document with Bitstream Charter font.

Created using LibreOffice 3.3.2 and Ubuntu 10.04 LTS with all latest updates.
Comment 9 Edmund Laugasson 2011-05-26 00:51:03 UTC
Comment on attachment 47173 [details]
Example of non-embed Bitstream Charter font where Adobe Acrobat 8.0 opened PDF

And I marked the checkbox "Embed standard fonts" to embed all fonts when I exported that PDF. My question is - which of fonts are "non-standard"? I would like to embed ALL fonts, not just standard ones.
Comment 10 Jose Aliste 2011-05-26 06:26:25 UTC
(In reply to comment #9)
> (From update of attachment 47173 [details])
> And I marked the checkbox "Embed standard fonts" to embed all fonts when I
> exported that PDF. My question is - which of fonts are "non-standard"? I would
> like to embed ALL fonts, not just standard ones.

Yeah, but that's a different issue. For this you should probably file a bug to libreoffice so the PDF export embeds all fonts.
Comment 11 Jason Crain 2016-02-19 05:01:12 UTC

*** This bug has been marked as a duplicate of bug 94054 ***


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.