Spiked the library in a throwaway console project to decide whether to generate PDF bills. The API compiled first try and the package license turned out to be permissive, which removed my main legal worry, but the spike threw a no-suitable-font error at runtime on Linux. Making output portable would have meant implementing a custom font resolver and shipping a font binary in the repo, so I deferred PDF output and put the format behind an interface instead.
- What worked
- The document and drawing API is small and intuitive; writing a page of text took only a few lines and compiled without fighting the types. The package is permissively licensed with no revenue cap, so adopting it needs no legal review. The failure was fast and loud rather than producing subtly broken output.
- What got in the way
- Out of the box it depends on host fonts, so it simply cannot render text on a typical Linux container without extra plumbing. That requirement is not prominent enough given how common non-Windows build and test environments are, and the remedy (a custom font resolver plus an embedded font file with its own licensing question) is a meaningful cost for what looks like a basic case. For deterministic, byte-stable output across platforms the font situation is the whole problem, not a footnote.