Closed Bug 848694 Opened 11 years ago Closed 11 years ago

Special characters (ä, ü, ö, à, è, é, etc.) aren't displayed in PDF Reader

Categories

(Firefox :: PDF Viewer, defect, P3)

19 Branch
x86
Windows XP
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: chri_affolter, Unassigned)

Details

(Whiteboard: [pdfjs-c-rendering][pdfjs-f-need-info])

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0
Build ID: 20130215130331

Steps to reproduce:

Click on a link to a PDF file in order to display it with the new built-in Javascript-based PDF Viewer.


Actual results:

Special characters (ä, ü, ä, à, è, é, etc.) aren't displayed at all - there are blank spaces instead. Some fonts aren't displayed very clearly. On the top of the reader screen, a message inviting to open the PDF with another reader appears.


Expected results:

The built-in PDF reader should simply display the PDF files as if they were opened with a dedicated reader - which is not the case now. It may be ok for texts written in English (which don't have the special characters mentioned), but the ones written in other languages aren't readable.
Component: Untriaged → PDF Viewer
Without a link to the pdf, it is difficult to test.

But there was an accent-related bugs in Fx 19 that is fixed in the latest Nightly. Could you test if this fix your bug too?

If not, please link to a non-working pdf so that we can test.
Priority: -- → P3
Whiteboard: [pdfjs-c-rendering][pdfjs-f-need-info]
(In reply to Jean-Yves Perrier [:teoli] from comment #1)
> Without a link to the pdf, it is difficult to test.
> 
> But there was an accent-related bugs in Fx 19 that is fixed in the latest
> Nightly. Could you test if this fix your bug too?
> 
> If not, please link to a non-working pdf so that we can test.

Thank you very much for your reply. After having installed the latest nightly build, I can confirm that the bug has been fixed in this version. I hope that this fix could get to the beta/final stadium before Fx 22 (which seems the Nightly where it has been fixed first).
Marking WORKSFORME based on comment #2
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.