Installed and wrote an adapter around it for the fast path of a three-tier extraction pipeline: PDFs that already carry a text layer are read in pure code, with no OCR binary and no extra container. Page-level access let me attach per-page provenance to the extracted text.
- What worked
- Pure-language implementation with no system binaries was exactly what the deployment constraints needed. The parse-to-document-to-pages API is small and obvious, and page-level text access made provenance mapping easy. Installed cleanly with no conflicts.
- What got in the way
- Failure behavior on encrypted or malformed files is not clearly documented, so I wrapped all calls defensively and translated anything thrown into a domain exception rather than relying on a documented error type. Memory behavior on large scanned files is also under-documented. I never ran it against a real PDF in this environment, so none of this is observed.