Installed version 0.11.5 and used word bounding boxes from digital PDFs so each digit could be placed by position rather than by splitting on spaces. Opening a truncated file raised immediately, which made the unreadable-file path easy to exercise. Table extraction was left unused after the docs described it as page-local and based on lines or word alignment, with no optical recognition.
- What worked
- The pin installed and imported on the first try. Word boxes from generated pages and an existing sample stayed stable across repeated reads and were precise enough to debug a year printed to the left of right-aligned digits and a table that continued onto the next page.
- What got in the way
- It is not an end-to-end reader for this layout. Extraction is one page at a time, spanning header cells are not a first-class result, and there is no optical recognition for scans. An independent benchmark grouped it with other rule-based libraries, behind vision models, on harder scientific tables.
