Skip Menu |

This queue is for tickets about the PDF-API2 CPAN distribution.

Report information
The Basics
Id: 65582
Status: resolved
Priority: 0/
Queue: PDF-API2

People
Owner: Nobody in particular
Requestors: simon [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 2.026



Subject: TTF embedding type mismatches
I'm using CFF OpenType fonts, and looking at the generated PDF, ghostscript is reporting mismatches, like so: % pdffonts test.pdf name type emb sub uni object ID ------------------------------------ ----------------- --- --- --- --------- Error: Mismatch between font type and embedded font file TimesNewRomanMTStd-Bold Type 1C yes no no 12 0 According to http://www.typophile.com/node/71297, Type 1C is for name-keyed fonts, whereas the right subtype for CID-keyed fonts would be CIDFontType0C. However, when I change PDF/API2/Resource/CIDFont/TrueType/FontFile.pm:478 to reflect this, although pdffonts is now happy and not reporting mismatches, ghostscript can't find the font any more, so I'm not sure what is the right fix here.
Recognizing that fully five years have gone by since you created this report, are you still able to reproduce the problem? I've been running into something similar with OpenType fonts not showing up in certain PDF viewers (most notably Apple's Preview app). Changing the subtype from Type1C to CIDFontType0C fixes the problem for me -- thanks for the lead. When I made the change, pdffonts was happy, as you found. However, in my case, Ghostscript worked fine both before and after the change. I'll dig into it a bit more before creating a release with this change -- if you have a breaking test case, that would be handy.
This fix will be in the next release. Please reopen if you have an example of it breaking. Thanks!