[
https://issues.apache.org/jira/browse/PDFBOX-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952216#comment-15952216
]
Tilman Hausherr edited comment on PDFBOX-3740 at 4/1/17 1:11 PM:
-----------------------------------------------------------------
Strategy 1 is the correct one, you must embed the font or a subset. It isn't
the count of errors that is important, it is the content. Test3 has only one
font related error but that one is a major one, "FontFile entry is missing", so
it can't go further.
Your problem in test1 is "3.3.1 : Glyph error, The character code .... in the
font program "Times-Roman" is missing from the Character Encoding on page 1",
and yes, when looking at it with PDFDebugger, the glyphs are missing. Open your
file and look at {{Root/Pages/Kids/\[0]/Resources/Font/F55}} . So either it is
really missing, or there's a bug so that the glyphs aren't found in the binary
part of the type1 font. Or this isa "how to" question, these are better asked
on the user mailing list.
was (Author: tilman):
Strategy 1 is the correct one, you must embed the font or a subset. It isn't
the count of errors that is important, it is the content. Test3 has only one
font related error but that one is a major one, "FontFile entry is missing", so
it can't go further.
Your problem in test3 is "3.3.1 : Glyph error, The character code .... in the
font program "Times-Roman" is missing from the Character Encoding on page 1",
and yes, when looking at it with PDFDebugger, the glyphs are missing. Open your
file and look at {{Root/Pages/Kids/\[0]/Resources/Font/F55}} . So either it is
really missing, or there's a bug so that the glyphs aren't found in the binary
part of the type1 font. Or this isa "how to" question, these are better asked
on the user mailing list.
> 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
>
>
> 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]