Closed
Bug 864847
Opened 12 years ago
Closed 10 years ago
PDF viewer displaying PDF in wrong language
Categories
(Firefox :: PDF Viewer, defect, P3)
Tracking
()
RESOLVED
FIXED
People
(Reporter: sean.beard, Unassigned)
References
Details
(Whiteboard: [pdfjs-c-rendering][pdfjs-d-font-conversion][pdfjs-f-fixed-upstream]https://github.com/mozilla/pdf.js/pull/4068)
Attachments
(1 file)
(deleted),
application/pdf
|
Details |
User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0E; .NET4.0C)
Steps to reproduce:
Display a PDF in Firefox PDF Viewer
Actual results:
showing in an incorrect language (eg. Greek/Arabic) within the Firefox PDF viewer
Expected results:
Should display in English (uk) - We have checked the document in Adobe and Foxit and these applications all show correctly
I was able to replicate this problem in Firefox 20.0. The text of the pdf shows in Greek in the PDF Viewer. If I save the file and open it with Preview on a Mac, it shows in English.
It also is in Greek in the Nightly build, 23.0a1.
Status: UNCONFIRMED → NEW
Component: Untriaged → PDF Viewer
Ever confirmed: true
Summary: PDF viewer displaying wrong langauge → PDF viewer displaying PDF in wrong language
Updated•12 years ago
|
Priority: -- → P3
Whiteboard: [pdfjs-c-rendering][pdfjs-d-font-conversion]
I'd like to request that the priority on this issue be moved up. This means that public users viewing PDFs on our website using FireFox's internal PDF viewer are seeing Russian or Greek or such. Even posting orgCharts in our online personnel system is reeking havoc with our Personnel department as they can't read the org charts. We can't tell the entire public user base to reset their default PDF viewer to Adobe.
Updated•11 years ago
|
Whiteboard: [pdfjs-c-rendering][pdfjs-d-font-conversion] → [pdfjs-c-rendering][pdfjs-d-font-conversion][pdfjs-f-fixed-upstream]https://github.com/mozilla/pdf.js/pull/4068
Updated•10 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•