[ 
https://issues.apache.org/jira/browse/PDFBOX-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299754#comment-14299754
 ] 

Maruan Sahyoun commented on PDFBOX-2624:
----------------------------------------

For PDF/A-1 
{quote}
For all CIDFont subsets referenced within a conforming file, the font 
descriptor dictionary shall include a CIDSet stream identifying which CIDs are 
present in the embedded CIDFont file, as described in PDF Reference Table 5.20.
{quote}

as PDF/A-2 clarified it a little more I’m adding the bit too for reference
{quote}
If the FontDescriptor dictionary of an embedded CID font contains a CIDSet 
stream, then it shall identify all CIDs which are present in the font program, 
regardless of whether a CID in the font is referenced or used by the PDF or not.
NOTE 3 The above requirement makes normative the statements in ISO 
32000-1:2008, 9.8.3.1, Table 124.
{quote}

If I’m not mistaken we need to validate the content of the CIDSet too.


> "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, cidset.patch
>
>
> 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]

Reply via email to