[
https://issues.apache.org/jira/browse/PDFBOX-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120154#comment-14120154
]
John Hewson commented on PDFBOX-2312:
-------------------------------------
The PDF spec is ambiguous on how to handle the PDF, the problem is that the PDF
includes an embedded symbolic TTF with an empty Encoding dictionary, the spec
says that "for a symbolic font, it is the font's built-in encoding" but it does
not explain how to determine what that encoding is, and for TTFs there may be
several built-in encodings, or none.
Acrobat can render the text but OS X Preview cannot. I've added a workaround so
that the empty Encoding is ignored and the code to GID mechanism continues as
it would do for any other symbolic TTF.
> IllegalArgumentException: Built-in Encoding required for symbolic font
> ----------------------------------------------------------------------
>
> Key: PDFBOX-2312
> URL: https://issues.apache.org/jira/browse/PDFBOX-2312
> Project: PDFBox
> Issue Type: Bug
> Components: PDModel
> Affects Versions: 2.0.0
> Reporter: simon steiner
> Assignee: John Hewson
> Attachments: out.pdf
>
>
> java -jar ~/pdf-box-svn/app/target/pdfbox-app-2.0.0-SNAPSHOT.jar PDFToImage
> out.pdf
> Exception in thread "main" java.lang.IllegalArgumentException: Built-in
> Encoding required for symbolic font
> at
> org.apache.pdfbox.encoding.DictionaryEncoding.<init>(DictionaryEncoding.java:84)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
