Hi,

----- original Nachricht --------
Betreff: Problem converting pdf page w/ fully embedded TTF font, Identity-H 
(CID)
Gesendet: Mi, 02. Jun 2010
Von: Armando Singer<[email protected]>

> I'm running into an issue when trying to convert a pdf page to an image.
> Conditions:
> 
> - Pdf file with TrueType font fully embedded
> - Encoding: Identity-H (CID)
> 
> Although the FontFile2 stream is present, I get (I added extra info
> logging):
> 
>  .... <SNIP>
> test with:
> 
> java -jar pdfbox-app-1.2.0-SNAPSHOT.jar PDFToImage -imageType png -startPage
> 1 -endPage 1 -color rgba -resolution 108 hello-DroidSans-Identity-H.pdf
> 
> Attached is a sample pdf with one of the droid fonts fully embedded in the
> above manner (free, Apache 2 license):
> 
> http://android.git.kernel.org/?p=platform/frameworks/base.git;a=tree;f=data/
> fonts;hb=HEAD
Due to some restrictions (binary) attachements aren't allowed. Is the mentioned
pdf the same than that one attached to PDFBOX-738? What tool did you use to
create that pdf?

> I'm wondering if this is a known issue, and if would would be appropriate to
> follow the chain to the TrueType font file stream to load the AWT font.
Hmm, strange stack trace. It seems that something is really mixed up...

> Currently PDType0 font extends PDType1 font. Perhaps we can special case for
> Identity CID fonts? Does that seem like a good idea?
AFAIU CID-fonts we don't need a special font class for those. It is "only" a 
question
of character decoding. I'm working on that issue and I hope I will have a 
solution soon.

> (I was able to hack fix by changing PDType0 to extends PDTrueTypeFont, but
> that seems like a terrible hack).
That's really a terrible hack. I'll have a deeper look into that issue later

Please file an issue on JIRA with all the information from your mail incl. the 
pdf in question.

BR
Andreas Lehmkühler


Reply via email to