[
https://issues.apache.org/jira/browse/PDFBOX-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291030#comment-14291030
]
Andreas Lehmkühler commented on PDFBOX-2624:
--------------------------------------------
{quote}The problem here is that very few people are using PDFBox to create
PDF/A files, e.g. the CreatePDFA example has been broken for years. Making them
call a deprecated method will inconvenience 0.0001% of our users.{quote}
Interesting argument but where are these figures from? I never saw a report
about that? However, this is just a snap-shot about the current situation. I
expect that the new 2.0 version will attract more users and who knows what they
are going to do with it? Most likely a lot of them will use the new rendering
capabilities, others will be glad to use the unicode support and I'm pretty
sure that there will be another group which will use it for PDFA-1b purposes.
> "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]
