Using xpdf (3.01-r8 in Gentoo) with poppler (0.5.4) I miss parts of text in several pdfs, and get ``Couldn't create a font for...'' messages instead. Related to (probably identical with) bugs #6728, #8472 and #8070 (several example pdfs there). Though bug #8070 says it's a freetype bug, fixed in freetype cvs before 2006-12-03, upgrading to freetype 2.3.1, released 2007-01-31, did not help. Neither helps installing freetype from cvs. pdffonts identifies all the problematic fonts as CID TrueType, embedded, sometimes subset and with unicode mapping, sometimes not, the splash backend tries to manage them in the case fontCIDType2 block in poppler/SplashOutputDev.cc, and the deepest source of error I've tracked so far is in splash/SplashFTFontFile.cc in SplashFontFile *SplashFTFontFile::loadTrueTypeFont FT_New_Memory_Face returning unknown file format error. I'm not sure if poppler passes wrong data to freetype or freetype fails to handle correct data.
There were recently a few changes in the top-of-tree (git repository) relating to font handling. Is there any change you can test that version? (note: 0.6.x doesn't have these fixes, but if that is all you can test, it would still help us to identify the problem). Alternatively, if you can attach a problematic PDF file (one that shows the problem with poppler 0.6), that would help us to verify.
No answer since a year and a half ago, closing as INVALID. Honza, if you happen to be reading this please test with a new poppler/attach a PDF file and reopen the bug.
(In reply to comment #2) I'm sorry for my behaviour with respect to this bug. The specific document I had problems with was my FCE results sheet: xpdf failed to display the gray bands marking the results there. Not wanting to attach it I probably should not file this report at all. Later I did not experience similar problems with any other document and did not go on for CAE to get another Cambridge English exam result sheet. If I find the old file I may test whether it is displayed correctly now. You may have access to one from another source -- at I really should have mentioned at least this. I've almost forgotten this; luckily at least my browser remembers my username and password here.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.