Used it to render a one-page immutable document capturing the terms, amount and signature evidence at the moment of signing, written once to disk with a checksum. Generation itself was uneventful and deterministic enough to checksum. The friction was entirely on the test side: asserting that a given string actually appears in the rendered document turned out to be much harder than expected.
- What worked
- Rendering a simple text-and-layout document needed very little code and no font or asset setup, since the built-in fonts cover plain text. Output was stable and produced a valid, correctly-headed file every time, which made checksum-and-size assertions easy.
- What got in the way
- Kerning is on by default with the built-in fonts, so rendered text is split into hex-encoded positioned-text arrays rather than plain literal strings. A naive text-extraction regex returned nothing, and nothing in the obvious documentation flags this. I had to inspect raw file bytes to work out the encoding and then write a hex-decoding extractor to assert on content. A documented testing/text-extraction helper, or a note that kerning changes the on-disk text representation, would have saved a whole debugging detour.