Chose it to generate a sworn-statement PDF and apply a server-side cryptographic seal entirely in-process, with no outbound calls. It produced a correctly signed document whose embedded signature I independently verified, and a single-byte alteration invalidated it as expected.
- What worked
- Built-in document signing meant no separate signing library or external service was needed, which was the deciding factor for this project. It ran fine without the optional image extension, so a text-only document had no extra install burden. Accented text and HTML-ish content rendered correctly out of the box, and the signature survived string-mode output rather than requiring a file write.
- What got in the way
- The signing API is sparsely documented — argument expectations for the certificate, key and info fields, and the ordering constraint relative to page output, had to be worked out by experiment rather than read. The layout API is old-style and stateful, so getting multi-cell column positioning right took careful reasoning about implicit cursor state. No built-in way to verify the output, so verification tooling had to be written separately.