[
https://issues.apache.org/jira/browse/FOP-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933044#comment-17933044
]
Martin Leitner commented on FOP-3230:
-------------------------------------
I am unsure how to reproduce the behaviour with the attached files. I can
confirm that rendering [^194061_simple.fo] into a PDF with [^fop.xconf] will
produce [^test.pdf], which is PDF/UA compliant according to PAC.
However, when I "attach to that fo the path for another PDF that is PDF/UA
compliant too" (as well as I understood that phrase, I created
[^includePdf.fo]) and then render that to a PDF via
{code:java}
call fop -fo includePdf.fo -c fop.xconf -pdf includePdf.pdf{code}
then I get [^includePdf.pdf], for which PAC reports "Content in an inadmissible
location".
I used the SNAPSHOT version of fop and fop-pdf-images from March 5, 2025.
Could you please provide an fo example that reproduces the behaviour, or review
the fix?
> PDF Images - PDF/UA template with PDF attachments not PDF/UA
> ------------------------------------------------------------
>
> Key: FOP-3230
> URL: https://issues.apache.org/jira/browse/FOP-3230
> Project: FOP
> Issue Type: Bug
> Reporter: Joao Goncalves
> Assignee: Joao Goncalves
> Priority: Major
> Fix For: main
>
> Attachments: 194061_simple.fo, Arial.ttf, Arialbd.ttf, Arialbi.ttf,
> Ariali.ttf, fop.xconf, includePdf.fo, includePdf.pdf, test.pdf
>
>
> When attaching a PDF that is PDF/UA compliant to a PDF/UA template, 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.
> Attach to your fo the path for another PDF that is PDF/UA compliant too.
> The result must be a PDF/UA compliant PDF
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
