Closed
Bug 835661
Opened 11 years ago
Closed 11 years ago
pdf.js:Small portions of some Japanese PDFs are garbled with Latin characters.
Categories
(Firefox :: PDF Viewer, defect)
Tracking
()
RESOLVED
FIXED
Firefox 21
People
(Reporter: rshimazu, Unassigned)
References
Details
(Whiteboard: [pdfjs-c-rendering][pdfjs-f-fixed-upstream] https://github.com/mozilla/pdf.js/pull/2624)
User Agent: Mozilla/5.0 (Windows NT 6.0; rv:19.0) Gecko/20100101 Firefox/19.0 Build ID: 20130116072953 Steps to reproduce: Please acess to the following urls. http://www.nii.ac.jp/userdata/shimin/documents/H23/111005_4thlec02.pdf http://www.elpr.bun.kyoto-u.ac.jp/essay/tatsuo~miyajima.pdf#page=2 http://www.dnp.co.jp/news/__icsFiles/afieldfile/2012/08/09/120809_3.pdf http://www.jsda.or.jp/katsudou/kisoku/files/a032.pdf Actual results: Not all but some characters changed themselves into latin characters. Expected results: Since those latin characters are not included in the original documents, original characters or simple space should be showed there.
Comment 1•11 years ago
|
||
This is because our cid-to-unicode mapping table doesn't consider cids for hankaku-latin glyphs.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•11 years ago
|
Component: Untriaged → PDF Viewer
OS: Windows Vista → All
Hardware: x86 → All
Updated•11 years ago
|
Whiteboard: [pdfjs-c-rendering][pdfjs-f-fixed-upstream] https://github.com/mozilla/pdf.js/pull/2624
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Depends on: 835954
Resolution: --- → FIXED
Target Milestone: --- → Firefox 21
Comment 2•3 years ago
|
||
Hey! I also encountered such a problem in PDF files, but then some good people told me that this was due to the fact that the collation table was cid-to-unicode, as the commentator said above. Also, these people have their own service https://www.livepaperhelp.com/pay-for-paper.html for writing texts, abstracts and other types of essays, it helps students a lot. In this way I also learned the English language of the texts already started.
You need to log in
before you can comment on or make changes to this bug.
Description
•