[
https://issues.apache.org/jira/browse/PDFBOX-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291452#comment-14291452
]
John Hewson commented on PDFBOX-2624:
-------------------------------------
It's an educated guess: because most of PDFBox's content generation features
aren't PDF/A compliant, and it's not something we hear many questions about on
the mailing list, so it's safe to assume that it's not widely used. Compare
this with non-PDF/A embedding of TTFs where we get frequent questions and bug
reports.
2.0 may or may not attract new users to create PDF/A, but one thing is for
sure: we have a large number of current users using PDTrueType font who need to
migrate. We also have a large number of people on the mailing list who are
already using Type0 fonts in 2.0, and not a single complaint that Type0 font's
don't support PDF/A. We must not put hypothetical future user's needs before
that of a large, and very real group of current users.
> "CIDSet entry is missing for the Composite Subset" when creating PDF/A-1b
> file with PDType0Font.load()
> ------------------------------------------------------------------------------------------------------
>
> Key: PDFBOX-2624
> URL: https://issues.apache.org/jira/browse/PDFBOX-2624
> Project: PDFBox
> Issue Type: New Feature
> Components: PDModel, Utilities
> Affects Versions: 2.0.0
> Reporter: Tilman Hausherr
> Fix For: 2.1.0
>
> Attachments: PDFBOX-2624.pdf
>
>
> PDTrueTypeFont.loadTTF() is deprecated. So I tried to change CreatePDFA.java
> to call PDType0Font.load() instead, but the preflight validation fails:
> {quote}
> 3.1.11: Invalid Font definition, AAAXQL+LiberationSans: The CIDSet entry is
> missing for the Composite Subset
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
