On 4/4/25 17:34, Pablo Rodriguez via ntg-context wrote:
> [...]
> I will report back as soon as I have found out what may not be
> working here.
After some testing, it seems we have two main issues with PDF/A-3a
validations.

First, PDF/A-2 and PDF/A-3 both require "/MarkInfo << /Marked true >>",
the same way as PDF/A-1 does.

https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-6722-1
is just for reference.

lpdf-tag.lmt contains on line 590:

        if version == 1 then

It isn’t clear to me whether "version" here refers to PDF/A version. If
that were the case, /MarkInfo is a requirement for all versions prior to
PDF/A-4 (according to
https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Part-4-rules).

Second, /Namespace, /NS and /RoleMapNS are only allowed in PDF-2.0
(https://github.com/pdf-association/arlington-pdf-model/blob/master/tsv/latest/Namespace.tsv).

Since we have PDF/A-3a (and not PDF/A-4F [at least, yet]), I’m afraid
the dictionary has to be /StructTreeRoot here.

There is a third issue, PDF-1.7 doesn’t allow /DocummentFragment as
standard structure type. Only Part, Art (article), Sect (section) or Div
would match here
(https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/PDF32000_2008.pdf#nameddest=G13.2348782).

Hans, I’m afraid this is the way to go. If my writting isn’t clear, let
me know.

Ulrike, in case you are listening, I would like to ask you some
questions about PDF validation and tagging.

Many thanks for your help,

Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

Reply via email to