On 11/11/25 18:27, Kyle Auble wrote:
> [...]
>> What kind of documentation are you thinking about?
> 
> Mainly basic contributor's notes: design overview (maybe with a
> diagram or two), process details, tips for trickier parts of the code,
> where to find the PDF standard reference, things like that.

This could be also enhanced with references to validators (mainly
veraPDF for the Arlington PDF model), how to generate certificates for
testing digital signatures, how to generate blank PDF documents with
certain features...

I cannot provide code, but I could add info about testing and some tools
(as just an average computer user).

A sample of what could be added on how to generate a self-signed
certificated was already added to the “Papers” testing documentation
(https://gitlab.gnome.org/GNOME/papers/-/blob/main/TESTING.md#digital-signatures).


Many thanks for your help,

Pablo

Reply via email to