From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050224 Firefox/1.0.1 Fedora/1.0.1-1.3.1 Description of problem: evince cannot display most of my pdf files correct. The files are loaded ok but the chinese characters turn out to be random meaningless symbols. Running in terminal, I can see a lot of error output such as ===== Error: Unknown character collection 'Adobe-GB1' Error: Unknown character collection 'Adobe-GB1' Error: Unknown font tag 'F5' Error: Unknown font tag 'F5' Error: Unknown font tag 'F5' Error: Unknown font tag 'F8' Error: Unknown font tag 'F3' Error (205398): No font in show/space Error: Unknown font tag 'F8' Error (205407): No font in show/space ===== and my system turned very slow when loading these files. These files are produced by Acrobat Distiller 5.0 (Windows) and/or CTeX suite (Windows) It can render some pdf files very well, which are produced using pdflatex in tetex-latex-2.0.2 or dvipdfmx(20031207), the source file is in UTF-8. Version-Release number of selected component (if applicable): evince-0.1.9-1.1.fc3.nr How reproducible: Always Steps to Reproduce: 1. open a terminal 2. run evince 3. load a file that contains chinese characters Actual Results: If the pdf file is created using adobe distiller under windows, then there would be alot of Error output, no chinese characters can be seen, but a lot of strange symbols. Since most of my pdf files are produced that way (adobe distillers + windows) and the source files(ppt, doc, etc.) are lost(bad luck!), I cannot reproduce them under OOo. Most of the times, acroread displays them well. Expected Results: nothing should happen in the terminal, and the page displays correctly, like acroread (with CHSKIT, language pack of acroread installed) does. Additional info: My default locale is zh_CN.UTF-8 when I switch to zh_CN.GB2312, the problem remains the same, so does the output on terminal.
Hi, thanks for the bug report. We're going to track this bug upstream because it looks like a similar problem they are seeing. Feel free to comment on it there. See the link to GNOME Bugzilla below.