[FOP-2004] Fop doesn't handle CID TrueType fonts in PostScript output

• Type: Improvement
• Status: Resolved
• Resolution: Fixed
• Affects Version/s: 1.0
• Component/s: font/unqualified
• Environment: Operating System: Linux; Platform: PC
• External issue ID: 52338
• Assignee: fop-dev
• Reporter: Craig Ringer
• Created: 15/Dec/11 07:32
• Updated: 22/Jun/12 18:11
• Resolved: 22/Jun/12 18:11

Description

I'm using fop 1.0 and am having issues with a TrueType CID font - all the Myriad Pro family in TrueType.

I can embed them in PDF and get perfect results from fop. Unfortunately, I have to include some other resources that're supplied as EPSs or PDFs. PDF-in-PDF embedding via Jeremias's fop-pdf-image ext works but has font duplication problems that mean I can't use it, so I have to use PostScript output from FOP with embedded EPSs then chuck the result through Distiller.

That's where the problem arises. All the text using CID fonts, like Myriad Pro, comes out either as "[X]" boxes in the final PDF with the occasional odd random glyph scattered through it.

The same fonts embed and work perfectly in FOP's PDF output.

I can't attach the fonts for licensing reasons, but I can supply for testing purposes to anyone interested. The fonts were converted from OpenType versions (which fop doesn't support) using FontForge, so they're not studio originals, but they work perfectly in PDF embedding and other applications.

I've filed this under "fonts" but it should possibly be "ps" instead.

I'll test with latest svn trunk and report on that.