Hello Hans,

thanks for the detailed answer.  Now it works!

I didn't realise until now that pdf is also messy. In my job I have enough to do with the fact that some products never work as they should ("Mr Gates has won and now we have to use his products.’ - said our former head of IT). I have nothing to do with IT, I am a scientist.

I am grateful for LaTeX, and of course I thank you, Hans, for ConTeXt!

I can only emphasise that I am just a user who keeps turning to lists for support.

Thank you for your time and patience.

Have a nice weekend
Thomas


Am 13.09.24 um 11:59 schrieb Hans Hagen via ntg-context:
On 9/13/2024 9:51 AM, Thomas Meyer wrote:
Oh, I'm afraid that my “I hope for the future.” has now led to a misunderstanding.

I would like to archive my documents as pdf/A-2a. As a reference to the German Bundesarchiv, which recommends pdf/A-2a in the first instance - and pdf/A-2u in the second.

I simply noticed that, as described in my initial email, the pdf/A-1a and pdf/A-2a variants do not pass the validation test with verapdf.

Since there seems to be no way around this, I will probably have to fall back on the second recommendation.

You cna try this:

\setupinteraction
  [title=TITLE,
   subtitle=SUBTITLE,
   author=AUTHOR,
   keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]

\setupbackend
  [format={pdf/a-2a},
   profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}]

\setuptagging
  [state=start]

\enabledirectives
  [backend.usetags=mkiv]

\starttext

    \chapter[chap:testing]{Testing}

    \input knuth

    \input tufte

\stoptext

This validates in the verapdf that i have installed (1.25.271).

So, you choose some standard (which we try to accomodate as good as possible but who knows ... this one is a bloated one due to the icc profiles). As you want tags we enable that (no need for it as long as one is not finished with the document unless one wants to trace). We also load the the old school mkiv mapping.

You can define your own mappings if needed. After looking into the latest greatest volatile specifications Mikael and I decided that we don't want to be waste too much time on it (at least not now as we hav emore interestign thinsg to work on) and settled for what validates and let users themselves decide. We mostly aim(ed) at making the university enforced tools happy.

Structure in pdf is (to put it mildly) a mess, insufficient and never will be (conceptually) okay, which is probably why it keeps being adapted to what some applications can support or not. We don't want to cripple what structure in ConTeXt we have. For the long time accessibility tagging (there are other kinds of tagging being in use) has been around for a quite vwhile now it has been the domain of acrobat professional toolkit so in a broader context it is kind of useless anyeay.

(One can wonder what organizations demanding it really have in mind, given that older stuff doesn't validate and probably no one ever checked how useful it is. But that's often the case with standrads like this: some checkbox ticks so we're okay.)

So, the best we can do is to provide some flexibility, as usual in tex tools,

Hans


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________