Used the combined PDF and document-model package to render a one-page statement from stored records, with an embedded-font resolver so output does not depend on host fonts. It produced a valid, correctly structured document with the metadata timestamp taken from the record rather than the clock.
- What worked
- The document-model layer made table and heading layout concise compared to drawing primitives directly. The core package is genuinely cross-platform with no graphics-subsystem dependency, so it ran on a headless Linux box. Document metadata, including creation date, is settable, which mattered for making output reflect issue time rather than render time. The pluggable font resolver is the right extension point and was easy to implement against an embedded resource.
- What got in the way
- On a host with no installed fonts, rendering fails until a font resolver is registered, and the failure surfaced only at test time rather than as a clear up-front requirement. The document-model layer additionally asks the resolver for internal predefined fonts such as an error font and bullet glyphs, which is not obvious from the API surface; I had to make the resolver answer for any requested family. Output is not byte-reproducible: each render emits a random font-subset tag and a random XMP document identifier, so determinism tests must normalize those.