liteparse · Issues· 31 open

Node and Python bindings silently accept invalid output formats

Grouped sparse rows split into separate Markdown tables and place a prose note under Unit Cost

[Parsing] Wide table rows are truncated on the right: nine columns emitted as four, dropping row totals

[Parsing] Invisible text detected only via render mode 3; three other mechanisms leak into output

[Parsing] Images nested in Form XObjects are not detected

Text near the edge of rotated pages is dropped since 2.12.0 (regression, likely #412)

[Parsing] Image identification failed

[Feature] PDF Attachments

Side-by-side ruled tables still share projected text lines

[Parsing] Same-row headings above side-by-side tables are merged

[Parsing] Preserve PDF visual revision markings: text color and highlighted text in JSON/Markdown output

[Bug] npm CLI `lit parse --format text` omits the `--- Page N ---` separators the cargo and pip CLIs emit

target_pages 100-page worker splits stall inside parser.parse, while full-PDF parsing gives better Markdown

[Feature] Rotated page detection

[Feature] Control Log Level