xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Radek Bidlo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FOP-2826) PDF/A validation error: CIDset in subset font is incomplete
Date Wed, 28 Nov 2018 13:29:00 GMT

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

Radek Bidlo commented on FOP-2826:
----------------------------------

Thank you, Chris, but I'm still a little confused, why the subset option would be available
in FOP, when an invalid PDF/A document is actually generated with it. As I understand it,
the subset option gives the opportunity to generate documents of smaller size comparing to
the full embedding mode, but still fully in agreement with the PDF/A requirements. Thus my
original motivation to create this issue was a suspicion of missing characters in the embedded
subset.

> PDF/A validation error: CIDset in subset font is incomplete
> -----------------------------------------------------------
>
>                 Key: FOP-2826
>                 URL: https://issues.apache.org/jira/browse/FOP-2826
>             Project: FOP
>          Issue Type: Bug
>    Affects Versions: 2.3
>            Reporter: Radek Bidlo
>            Priority: Major
>         Attachments: samples.zip
>
>
> When the PDF/A documents generated by FOP *with the font embedding-mode="subset"* are
validated for PDF/A conformance by validators based on Adobe Preflight, these validators report
the following error:
> *CIDset in subset font is incomplete*
> More precisely, the attached samples are the PDF/A-1b documents, but the same issue occurs
also for other PDF/A variants.
> This issue occurs also in PDF/A documents generated from previous versions of FOP.
> Please see the attached [^samples.zip], where you can find:
> - TTF fonts used for the samples
> - FOP configuration files with both the full and subset embedding mode
> - sample FO input file for FOP
> - resulting PDF/A documents subset.pdf (of which validation reports the error) and full.pdf
(which is without errors)
> This issue complicates the document processing, where the PDF/A conformance validation
is performed and the no error result is expected to allow further processing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message