[jira] [Commented] (FOP-3245) fox:external-document - PDF/UA template with PDF/UA attachments not PDF/UA

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

Martin Leitner commented on FOP-3245:
-------------------------------------

[~jgoncalves] I disagree insofar as I think the examples attached to the ticket do not try to concatenate FO documents. They try to append existing PDF documents, and they use {{fox:external-document}} exactly in the way it is supposed to be used.

Concatenating FO documents would be attaching page2.fo rather than page2.pdf. This will not work, regardless of PDF/UA or not, and rightfully so, because this is not what {{fox:external-document}} is supposed to do.

However, I do take the point made in the linked FOP-3230, that {{fox:external-document}} never even tries to add the structure tree, so the effort to fix this may be very high compared to the gain.

> fox:external-document - PDF/UA template with PDF/UA attachments not PDF/UA
> --------------------------------------------------------------------------
>
>                 Key: FOP-3245
>                 URL: https://issues.apache.org/jira/browse/FOP-3245
>             Project: FOP
>          Issue Type: Bug
>          Components: renderer/pdf
>    Affects Versions: 2.10
>            Reporter: Martin Leitner
>            Priority: Major
>         Attachments: arial.ttf, arialbd.ttf, arialbi.ttf, ariali.ttf, fop.xconf, page1.fo, page1.pdf, page1_and_doc.fo, page2.fo, page2.pdf, page2_and_doc.fo
>
>
> When attaching a PDF that is PDF/UA compliant to a PDF/UA template via fox:external-document, the result is a PDF that is not compliant with PDF/UA
>  
> Replication Steps:
> Set accessibility to true, and add PDF/UA profile to the pdf part of the fop config.
> Produce a simple PDF/UA, e.g. by using the attached files and running
> call fop -fo page1.fo -c fop.xconf -pdf page1.pdf
> Then render a different FO that includes an existing PDF/UA like this:
> call fop -fo page2_and_doc.fo -c fop.xconf -pdf page2_and_doc.pdf
>  
> The resulting PDF should again be PDF/UA, but it is not. It seems that the structure tree from the referenced PDF is not added to the result at all.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)