[Poppler-bugs] [Bug 9905] New: Embeded CID Type 2 fonts not read

bugzilla-daemon at annarchy.freedesktop.org bugzilla-daemon at annarchy.freedesktop.org
Wed Feb 7 09:09:12 PST 2007


           Summary: Embeded CID Type 2 fonts not read
           Product: poppler
           Version: unspecified
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: splash backend
        AssignedTo: poppler-bugs at lists.freedesktop.org
        ReportedBy: Hloupy.Honza at centrum.cz

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.

Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the Poppler-bugs mailing list