Chose this permissively licensed library for in-process PDF table extraction because the data could not leave the region. Wired it behind an interface, drove it with page iteration plus both the ruling-based and the text-position extraction algorithms, and verified it against PDFs generated inside the test suite. It did extract multi-column invoice rows correctly, but getting there took real archaeology.
- What worked
- Table-level abstraction (pages, tables, rows, cells with coordinates) is exactly the right altitude for column-indexed parsing, and far better than hand-rolling on a raw text extractor. The ruling-detection check for whether a page is genuinely tabular is a nice built-in heuristic. Extraction results on generated documents were consistent and correctly ordered.
- What got in the way
- API documentation is thin enough that I ended up reading the library source on the code host to confirm method signatures. The published release is years old with no security updates since. It drags in a second logging binding that collides with the host framework's logger, and an old transitive PDF core version that falls inside a published CVE range. Worst of all, a command-line argument library that looks purely CLI-only is actually referenced on the extraction path, so excluding it compiles fine and then fails at runtime with a class-not-found error. Row cell types are raw, forcing warning suppression.