anydoc-wasm still ships pdf-inspector 1.14.2 — the RTL extraction fix (pdf-inspector#440) isn't included
- Dominant language
- Rust
- Stars
- 21.5k
- Forks
- 1.3k
- Avg merge
- 42m
- Merged PRs (30d)
- 17
Description
`Cargo.lock` on `main` pins `pdf-inspector` to `1.14.2`:
```
[[package]]
name = "pdf-inspector"
version = "1.14.2"
```
That predates [pdf-inspector#440](https://github.com/firecrawl/pdf-inspector/pull/440) (merged 2026-08-21, fixed visual-order RTL text extracting character-reversed) and [#441](https://github.com/firecrawl/pdf-inspector/pull/441) (merged same window, fixed digit-only Arabic lines voting RTL and reversing). Both landed in `pdf-inspector 1.16.0`; latest is `1.19.0`.
Concretely, `@firecrawl/anydoc-wasm@0.2.4` (published 2026-08-27, after both fixes existed upstream) still reverses Hebrew/Arabic text stored in visual order, because the vendored engine predates the fix — `pdf-inspector`'s own `tests/fixtures/hebrew_visual_order.pdf` / `hebrew_logical_order.pdf` both now extract correctly on `pdf-inspector` `main`, confirmed against the real fixtures in that repo.
Could you bump the `pdf-inspector` dependency to `1.16.0` or later and cut a new `anydoc-wasm` release? Evaluating anydoc for a PDF-to-Markdown use case and this is the blocker.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with Cargo.lock and the pdf-inspector dependency declaration, then compare the pinned version with the upstream 1.16.0 release containing fixes #440 and #441. Verify extraction against the mentioned Hebrew visual-order and logical-order fixtures, update the dependency, and cut a new anydoc-wasm release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 75/100