[
https://issues.apache.org/jira/browse/PDFBOX-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290070#comment-14290070
]
John Hewson edited comment on PDFBOX-2624 at 1/23/15 10:02 PM:
---------------------------------------------------------------
{quote}
Why would they do that? The call is deprecated. No developer would create a new
class with a deprecated call.
{quote}
Of course they will, because they will copy and paste our example. We've shown
them the way, ugly as it may be.
{quote}
Either the declaration should be un-deprecated, and/or there should be a
javadoc explaining that the other one is not to be used for PDF/A, but that is
useful for normal documents and makes smaller files thanks to subsetting.
{quote}
Just because we don't provide an alternative doesn't mean that
PDTrueTypeFont.loadTTF() isn't deprecated - it is, and it _will_ be removed,
but not before CIDSet is supported for Type0 fonts.
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.
However, a very large number or people are currently using PDTrueTypeFont to
embed TTF files and have opened many JIRA issues related to its lack of Unicode
support and we need to direct those users to PDType0Font. If we don't deprecate
PDTrueTypeFont.loadTTF() then they will continue to use it, which will harm
99.9999% of our users.
So the "less bad" choice is to deprecate PDTrueTypeFont.loadTTF().
was (Author: jahewson):
{quote}
Why would they do that? The call is deprecated. No developer would create a new
class with a deprecated call.
{quote}
Of course they will, because they will copy and paste our example. We've shown
them the way, ugly as it may be.
{quote}
Either the declaration should be un-deprecated, and/or there should be a
javadoc explaining that the other one is not to be used for PDF/A, but that is
useful for normal documents and makes smaller files thanks to subsetting.
{quote}
Just because we don't provide an alternative doesn't mean that
PDTrueTypeFont.loadTTF() isn't deprecated - it is, and it _will_ be removed,
but not before CIDSet is supported for Type0 fonts.
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.
However, a very large number or people are currently using PDTrueTypeFont to
embed TTF files and have opened many JIRA issues related to its lack of Unicode
support and we need to direct those users to PDType0Font. If we don't deprecate
PDTrueTypeFont.loadTTF() then they will continue to use it, which will harm
99.9999% of our 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)
