Closed
Bug 1488618
Opened 6 years ago
Closed 3 years ago
PDF viewer prints fuzzy; save-as-PDF results in garbled PDF.
Categories
(Firefox :: PDF Viewer, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1269023
People
(Reporter: bjacob, Unassigned)
Details
(Whiteboard: [pdfjs-c-printing])
Attachments
(1 file)
345.65 KB,
application/pdf
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180807170231
Steps to reproduce:
In Firefox's built-in PDF viewer, I opened a PDF paper from arXiv, such as
https://arxiv.org/pdf/1610.08364.pdf
I tried printing it on my printer; and I also tried saving-to-PDF.
Actual results:
When printing on my printer, it looked fuzzy. Each letter looked surrounded by a thin stippled pattern, as if it was bordered by 'gray' pixels (which my black-and-white printer renders stippled). It looks a bit as if rasterized at a too low resolution.
When saving-as-PDF, I got the attached, garbled file, firefox.pdf. It looks the same, equally garbled, no matter in what application I open it: in Firefox's own PDF viewer, in Chrome's, and in Mac's "Preview". Specifically: the fonts are wrong, the glyph positioning is wrong.
Thus, it really seems that what Firefox's PDF viewer does when printing-to-printer and what it does when saving-to-PDF, are two separate things, and they are both wrong but in different ways.
Expected results:
Both print-to-printer and save-as-PDF should look the same and should look sharp and use the right fonts.
Reporter | ||
Updated•6 years ago
|
Attachment #9006420 -
Attachment description: firefox.pdf → Garbled PDF produced by save-as-PDF
Updated•6 years ago
|
Component: Untriaged → PDF Viewer
Updated•6 years ago
|
Priority: -- → P3
Whiteboard: [pdfjs-c-printing]
Comment 2•3 years ago
|
||
I haven't tested printing to paper, but printing to PDF seems to be working well now.
Flags: qe-verify?
Updated•3 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
Updated•2 years ago
|
Flags: qe-verify? → qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•