Skip to content

v0.1a.2: tolerate PDF spacing differences in reference lookup - #15

Merged
drdeepaksatheesh merged 5 commits into
mainfrom
fix/v0.1a-pdf-spacing
Sep 15, 2026
Merged

drdeepaksatheesh merged 5 commits into
mainfrom
fix/v0.1a-pdf-spacing

Conversation

@drdeepaksatheesh

@drdeepaksatheesh drdeepaksatheesh commented Sep 15, 2026 •

Copy link
Copy Markdown
Owner

Fixes #14.

The Windows smoke test showed that PDF.js can extract visually separated word runs as joined text (a given -> agiven). The v0.1a reference engine previously used exact normalized-text lookup and therefore rejected a supported passage.

Fix

  • keep SourceAnchor text and quote hashing unchanged for provenance fidelity;
  • introduce a reference-engine-only lookup key that removes punctuation/whitespace while preserving ordered alphanumeric content;
  • add a regression test reproducing the exact agiven extraction seen in the smoke test;
  • bump local reference engine to 0.1a.2 and app package to 0.1.0-alpha.2.

This is deterministic normalization, not semantic/fuzzy matching: unknown content must still return unsupported.

CI evidence

GitHub Actions run 34926919222: PASS.

  • frontend/version checks: PASS
  • unit tests including the agiven regression: PASS
  • production build: PASS
  • critical dependency audit: PASS
  • Windows NSIS build: PASS
  • installer validation + checksum: PASS
  • artifact upload: PASS

Merged after CI passed.

@drdeepaksatheesh
drdeepaksatheesh merged commit 8088f88 into main Sep 15, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: PDF text-layer spacing causes supported Hindi reference passage to be rejected

1 participant