Hans, compiling the following source: \setupbackend[format=pdf/ua-2] \setuptagging[state=start] \setupstructure[state=start] \setupbackend [format=PDF/A-3a, intent=sRGB IEC61966-2.1, level=0] \setupexternalfigures[location=default] \starttext \externalfigure[cow][label={this is a cow}] \stoptext I’m afraid that veraPDF warns about ua-1 missing metadata info (https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFUA-Part-1-rul...). This should be the reason why veraPDF cannot autodetect that the output from the sample above is PDF/UA-2 (althought it passes this validation profile when specified). I see that lines 600 to 750 from lpdf-fmt.lmt include these metadata (even with WTPDF-1.0 accesibility and reuse), but somehow they don’t end up in the output PDF document. Could you take a look at this? Many thanks for your help, Pablo
Am Sat, 5 Apr 2025 09:33:58 +0200 schrieb Pablo Rodriguez via ntg-context:
compiling the following source:
\setupbackend[format=pdf/ua-2] \setuptagging[state=start] \setupstructure[state=start] \setupbackend [format=PDF/A-3a, intent=sRGB IEC61966-2.1, level=0]
\setupexternalfigures[location=default] \starttext \externalfigure[cow][label={this is a cow}] \stoptext
Unrelated to context, but you shouldn't mix UA-2 with A-3. UA-2 is for pdf 2.0 and should be used together with pdf/A-4 -- Ulrike Fischer http://www.troubleshooting-tex.de/
On 4/5/25 09:53, Ulrike Fischer wrote:
Am Sat, 5 Apr 2025 09:33:58 +0200 schrieb Pablo Rodriguez: via [...]
\setupbackend[format=pdf/ua-2]
\setupbackend
[format=PDF/A-3a,
Unrelated to context, but you shouldn't mix UA-2 with A-3. UA-2 is for pdf 2.0 and should be used together with pdf/A-4
Many thanks for your comment, Ulrike. I agree, it would be desirable to have at least PDF/A-4f. Many thanks for your help, Pablo
participants (2)
-
Pablo Rodriguez -
Ulrike Fischer