Created attachment 373185 [details] PDF with Adobe-Japan1-UCS2 Description of problem: Reading the attached document in okular outputs: Error: Couldn't find ToUnicode CMap file for 'Adobe-Japan1-UCS2' Strace show it looking for the following 'UCS2' files: open("/usr/share/poppler/cMap/Adobe-Japan1/UniJIS-UCS2-H", O_RDONLY|O_LARGEFILE) = 14 open("/usr/share/poppler/cMap/Adobe-CNS1/Adobe-Japan1-UCS2", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/share/poppler/cMap/Adobe-Korea1/Adobe-Japan1-UCS2", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/share/poppler/cMap/Adobe-Japan2/Adobe-Japan1-UCS2", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/share/poppler/cMap/Adobe-Japan1/Adobe-Japan1-UCS2", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/share/poppler/cMap/Adobe-GB1/Adobe-Japan1-UCS2", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/share/poppler/cMap/Adobe-Japan1/UniJIS-UCS2-V", O_RDONLY|O_LARGEFILE) = 14 Version-Release number of selected component (if applicable): poppler-data-0.3.0-1.fc12.noarch
poppler-data simply may not contain the needed data, or the encoding is off? $ rpm -ql poppler-data | grep Japan | grep UCS /usr/share/poppler/cMap/Adobe-Japan1/UniHojo-UCS2-H /usr/share/poppler/cMap/Adobe-Japan1/UniHojo-UCS2-V /usr/share/poppler/cMap/Adobe-Japan1/UniJIS-UCS2-H /usr/share/poppler/cMap/Adobe-Japan1/UniJIS-UCS2-HW-H /usr/share/poppler/cMap/Adobe-Japan1/UniJIS-UCS2-HW-V /usr/share/poppler/cMap/Adobe-Japan1/UniJIS-UCS2-V /usr/share/poppler/cMap/Adobe-Japan1/UniJISPro-UCS2-HW-V /usr/share/poppler/cMap/Adobe-Japan1/UniJISPro-UCS2-V
Ah, I see poppler-data-0.3.1 available, will test that.
OK, not present in 0.3.1. either. But, I have good news and bad news. Good news: poppler-data-0.4.0 released, and seems to include the new encoding, and the error Error: Couldn't find ToUnicode CMap file for 'Adobe-Japan1-UCS2' goes away Bad news: I still see nothing render in the test document. :(
Hi, the PDF looks almost the same as in Adobe Reader 9.3.2 in my updated Fedora 12 (evince-2.28.2-1, poppler-0.12.4-2, poppler-data-0.4.0-1). Could you confirm that? Thank you Marek P.S.: Adobe Reader needs additional fonts from http://www.adobe.com/products/acrobat/acrrasianfontpack.html
Well, I certainly no longer see the CMap message. Text is basically the same, but character spacing is certainly not correct.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.