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

Martin Leitner commented on FOP-3230:
-------------------------------------

[~jgoncalves] I can confirm that all the examples in this ticket with PDF 
images now render to valid PDF/UA.

The issue with fox:external-document remains, as shown by [^page1_and_doc.fo] 
and [^page2_and_doc.fo] (render page1.pdf and page2.pdf first, they are 
referenced by these examples). The resulting PDFs fail the PDF/UA check with: 
Text object not tagged

>From these simple examples it appears that fox:external-document simply does 
>not import any tags from the referenced documents.

I am not sure if the issue with fox:external-document is still in the scope of 
this ticket or if I should create a new ticket.

I will continue with checking other examples, but the space of possible 
combinations (multiple pages, tables, images, overlays, ...) is huge, so it may 
take some time.

> 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: 
> 0001-FOP-3230-Skip-paragraph-type-elements-when-merging-s-1.patch, 
> 194061_simple.fo, Arial.ttf, Arialbd.ttf, Arialbi.ttf, Ariali.ttf, fop.xconf, 
> imgs_and_table.fo, imgs_in_table.fo, includePdf.fo, includePdf.pdf, page1.fo, 
> page1_and_doc.fo, page2.fo, page2_and_doc.fo, simple_table.fo, 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)

Reply via email to