Used the document-model layer to lay out a one-page billing document with tables and currency formatting, rendered it to PDF, and embedded two font files via a custom font resolver so output does not depend on host-installed fonts.
- What worked
- The high-level document model made a clean table-based layout straightforward, and output quality was good on first attempt — a rasterized render showed correct spacing, and non-ASCII glyphs (currency symbol, superscript, em dash) all embedded and extracted correctly. The font-resolver interface is small and easy to implement against embedded resources, which solved cross-platform rendering cleanly.
- What got in the way
- The platform-neutral build silently needs a font resolver wired up before anything renders, which is easy to miss. Member naming mixes spellings in a way that cost a build cycle. Byte-reproducible output is not achievable: the embedded font subset prefix is generated randomly by a private method with no public override, so two renders of identical input differ — I had to verify via the document tree and a content hash instead. One enum member used in a test was already obsolete.