[ 
https://issues.apache.org/jira/browse/PDFBOX-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171702#comment-15171702
 ] 

Petras commented on PDFBOX-2428:
--------------------------------

I stumbled myself on this exception too. I use the latest v1.8.12-SNAPSHOT I 
also get this exception with the attached file "ttsubset_pdfa.pdf". It seems 
the patch proposed 
[above|https://issues.apache.org/jira/browse/PDFBOX-2428?focusedCommentId=14328941]
 was not applied yet to the v1.8 branch. When applied, errors are gone and only 
these errors are registered:
{code}
3.1.5 : Invalid Font definition, The Encoding should be missing for the 
Symbolic TTF
3.1.5 : Invalid Font definition, The Encoding should be missing for the 
Symbolic TTF
7.11 : Error on MetaData, PDF/A identification schema 
http://www.aiim.org/pdfa/ns/id/ is missing
{code}
Could the patch also be applied to the v1.8 branch? Thank you.

> An error occured when reading table hmtx
> ----------------------------------------
>
>                 Key: PDFBOX-2428
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-2428
>             Project: PDFBox
>          Issue Type: Bug
>          Components: FontBox
>    Affects Versions: 1.8.8, 2.0.0
>            Reporter: simon steiner
>            Assignee: John Hewson
>             Fix For: 2.0.0
>
>         Attachments: ttsubset_pdfa.pdf
>
>
> java -cp 
> pdfbox/preflight/target/preflight-1.8.8-SNAPSHOT.jar:pdfbox/app/target/pdfbox-app-1.8.8-SNAPSHOT.jar:pdfbox/xmpbox/target/xmpbox-1.8.8-SNAPSHOT.jar:lib/commons-io-1.3.1.jar
>  org.apache.pdfbox.preflight.Validator_A1b ttsubset_pdfa.pdf
> SEVERE: An error occured when reading table hmtx
> java.io.EOFException
>       at 
> org.apache.fontbox.ttf.MemoryTTFDataStream.readSignedShort(MemoryTTFDataStream.java:139)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to