Used the document-model layer to lay out an invoice-style PDF with a header, a details table and totals, plus a custom font resolver backed by fonts embedded in the assembly. Output rendered correctly and I verified the text by decompressing the content stream and checking the numbers against the calculation code.
- What worked
- Permissive license with no in-code license declaration, which made it an easy choice when a commercial alternative's licensing was unresolved. The document-model API is pleasant for table-and-paragraph layouts. Pluggable font resolution made it straightforward to embed fonts and get host-independent rendering.
- What got in the way
- On Linux there is no usable default font resolution, so the first render failed outright; worse, the library also demands that a specific legacy fallback family resolve, and the failure message does not make it obvious that your resolver must answer for families you never asked for. The default text encoding silently dropped a non-ASCII dash from the output instead of erroring or substituting — a real content defect I only caught by extracting the rendered text. Each render also stamps several random identifiers (font subset prefixes, document ID, metadata UUIDs), so byte-identical output is not achievable without patching.