[
https://issues.apache.org/jira/browse/PDFBOX-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952701#comment-15952701
]
Tilman Hausherr commented on PDFBOX-3740:
-----------------------------------------
Some news:
1) both fonts have the symbolic flag set - why?
2) the reason why the files are rendered differently in PDFBox is because in
{{PDType1Font.readEncodingFromFont}} the standard 14 AFM is used if the name
matches. However you are using your own names, like "char_141". After changing
this logic, both files render properly and validate too.
> Standard 14 and Encoding
> ------------------------
>
> Key: PDFBOX-3740
> URL: https://issues.apache.org/jira/browse/PDFBOX-3740
> Project: PDFBox
> Issue Type: Bug
> Components: Preflight
> Affects Versions: 2.0.5
> Environment: linux
> Reporter: Wolfgang Hamann
> Attachments: test1.pdf, test2.pdf, test3.pdf, test42-Roman.pdf,
> test42-Romax.pdf, test4.pdf
>
>
> before I attempted to become PDF/A compatible, I was happy with just an
> Encoding entry for the standard 14...
> I have made a few tests:
> 1 - full embedding of font
> 2 - just Encoding
> 3 - complete font descriptor
> rendering results and preflight warnings
> gs acro xpdf preflight
> ok ok bad many
> ok ok ok 2
> ok bad ok 1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
