GNOME Bugzilla – Bug 343564
Japanese fonts not displayed.
Last modified: 2010-07-06 00:52:24 UTC
Please describe the problem: PDF documents created with Microsoft office with Japanese fonts do not render correctly (at all). As if the font was missing. Steps to reproduce: 1. Create a document in MS Office using Japanese characters. 2. Export as PDF 3. Open in Evince. Actual results: File is open with no text. Expected results: Rendered japanese fonts would be visible as when the document was created. Does this happen every time? Yes. Other information: Seems to be the same bug as http://bugzilla.gnome.org/show_bug.cgi?id=320866 Simple test documents created in OpenOffice work as expeceted. This problem also affects Xpdf making me thing it's a font issue.
Output from evince is : evince Desktop/バリューコマース株式会社様 御見積書12.pdf Error: could not create truetype face some font thing failed Error: could not create truetype face some font thing failed Error: could not create truetype face some font thing failed Error: could not create truetype face some font thing failed .. Xpdf prints this : xpdf Desktop/バリューコマース株式会社様 御見積書12.pdf Error: Couldn't create a font for 'MS-Gothic' Error: Couldn't create a font for 'MS-PMincho' Error: Couldn't create a font for 'MS-PMincho' Error: Couldn't create a font for 'MS-PMincho' Error: Couldn't create a font for 'MS-PMincho' ... and so on repeating the same error. msttfontcore is installed. Problem persists with current dev tree versions of evince/xpdf.
Created attachment 66582 [details] Screenshot of the issue. Evince + xpdf showing problems.
Hi, this looks like a bug with the PDF backend. Could you please follow these instructions to help get this bug fixed. Thank You. http://live.gnome.org/Evince/PopplerBugs#poppler
Thanks, I've opened a big with popplar : https://bugs.freedesktop.org/show_bug.cgi?id=7093
## https://bugs.freedesktop.org/show_bug.cgi?id=7093 ## -- Additional comment #3 from merlin@ds2.uw.edu.pl on 2006-06-03 10:09 [reply] -- .. Issue stated here is an evince bug, not a poppler one. Xpdf relied on xpdfrc file for font substitution while handling non-emmbedded fonts. Poppler still does, but now you have to explicitly call GlobalParams metod to read that file. In fact if you add in pdf/ev-poppler.cc something as simple as: #include <GlobalParams.h> in poppler include block and globalParams = GlobalParams (""); in pdf_document_init (PdfDocument *pdf_document), xpdfrc gets to be read (.xpdfrc in $HOME , if you have it, /etc/xpdfrc otherwise), and if that file contains correct entries those japanese pdfs are displayed correctly. Of course, only required entries are cidToUnicode and cMapDir, as the rest is handled by fontconfig (Cmaps are often installed with ghostscript, cidToUnicode files have to be taken from xpdf). ..
It's not evince bug. We don't going to use GlobarParams in our code since it's not a public API