On 11/3/25 19:35, Pablo Rodríguez wrote: > Dear list, > > I’m experiencing an issue with some signature fields that, after signed > with `pdfsig`, “Acrobat” cannot recognize (and asks to save, disabling > the signature in the output document).
After some testing, I think I can reply to this myself. > 1. Can the signature field define the annotation as a child or must > signature field and widget annotation be only one object? According to the Arlington model (as checked with https://software.verapdf.org/develop/arlington/), signature fields cannot have kids. Signature field and widget annotation should be the same object (or I couldn’t make it work as parent and child). > […] > 3. Is there anything else I may be missing for these signature field? The document itself contains a `/NeedAppearances true` in the `/AcroForm` dictionary, which also prevents the signature display in “Acrobat Reader”. Before anyone comments it, `pdfsig` adding a `/NeedAppearances true` to the signed document seems to be no issue to “Acrobat”. This is all I found out to make it work. Also another LaTeX document had the same issue with `/NeedAppearances true`. As far as I understand it, the issue is not `pdfsig`, but not well-formed PDF documents. Sorry for the noise and many thanks for your patience, Pablo
