Closed
Bug 925985
Opened 11 years ago
Closed 9 years ago
pdf not displaying trademark character and renders poorly
Categories
(Firefox :: PDF Viewer, defect, P3)
Tracking
()
RESOLVED
FIXED
Firefox 30
People
(Reporter: vroudenko, Assigned: Snuffleupagus)
References
Details
(Whiteboard: [pdfjs-c-rendering][pdfjs-d-standard-font][pdfjs-f-fixed-upstream] https://github.com/mozilla/pdf.js/pull/4362)
Attachments
(1 file)
|
52.65 KB,
application/pdf
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.59.10 (KHTML, like Gecko) Version/5.1.9 Safari/534.59.10 Steps to reproduce: Went to the link http://www.biolegend.com/pop_pdf.php?id=7731 inside of Firefox using the integrated pdf viewer. Actual results: PDF page opens, but displays a square instead of the trademark character wherever it appears in the document. Poor rendering of fonts when printing. The result looks like a bad photocopy. General inconsistencies pronounced around the lowercase letter 'i' and italicized lowercase 'L'. Expected results: PDF should display the trademark character and correctly render all fonts. Output results should appeared the same as printed from Chrome, IE or using the Adobe plug-in.
Component: Untriaged → PDF Viewer
OS: Mac OS X → Windows XP
|
||
Comment 1•11 years ago
|
||
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 Reproduced on latest Aurora build (20131013004004)
Status: UNCONFIRMED → NEW
Ever confirmed: true
|
||
Comment 2•11 years ago
|
||
Seems to be windows only issue.
Priority: -- → P3
Whiteboard: [pdfjs-c-rendering][pdfjs-d-standard-font]
|
||
Updated•10 years ago
|
Whiteboard: [pdfjs-c-rendering][pdfjs-d-standard-font] → [pdfjs-c-rendering][pdfjs-d-standard-font][pdfjs-f-fixed-upstream] https://github.com/mozilla/pdf.js/pull/4362
|
|
||
Updated•10 years ago
|
Assignee: nobody → jonas.jenwald
|
Assignee | |
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Depends on: 979909
Resolution: --- → FIXED
Target Milestone: --- → Firefox 30
You need to log in
before you can comment on or make changes to this bug.
Description
•