Used the document-model layer to render a one-page A4 invoice with a table, computed totals and currency formatting, then verified the output independently. The rendering model itself is pleasant and the result was a valid, correctly laid-out PDF. Getting there cost far more than expected: picking the right package, discovering there is no font resolution outside Windows, writing a custom font resolver, and confirming by experiment that output cannot be made byte-identical.
- What worked
- The document-object model is expressive and predictable for invoice-style layouts; column widths, table styling and page setup behaved as written. Permissive license on the current major line. Internal document identifiers are settable, which removes one source of per-render drift.
- What got in the way
- The cross-platform build silently has no font resolution, so first render throws unless you supply a resolver; discovering the resolver interface shape required reflecting over the assembly because I could not find it documented clearly. The bundled embedded font is a proprietary family, so it is not a usable default for customer-facing output. Member naming is inconsistent with the surrounding localized vocabulary, costing a build error. Most significantly, every render emits a random font-subset prefix with no public control, so reproducible output is impossible without post-processing — I had to drop a property I had promised.