Exact evidence scope
What the converter release gate is designed to prove
SahayakTools does not treat a successful round trip as universal accuracy evidence. The release gate combines independent mapping evidence, hard expected outputs, generated cases and document-format invariants for the exact legacy mappings the site claims to support.
Published examples
Kruti Dev 010 hard vectors
HkkjrभारतvkSjऔरeq>sमुझेcgqrबहुतilanपसंद25@05@201625/05/2016vkSj eq>s ;s cgqr ilan gSAऔर मुझे ये बहुत पसंद है।The slash case is intentional: in the verified Kruti Dev 010 mapping, the underlying legacy @ glyph represents the visible Unicode solidus /. This is why punctuation cannot be globally protected or replaced without font context.
Release-gate coverage
What must pass before converter changes are release-ready
Kruti Dev 010 primary/reference vectors
Exact forward glyphs and punctuation, contextual words/sentences, visible slash handling (@ ↔ /), reverse semantic checks and generated Hindi combinations.
DevLys 010 reference vectors
Forward and reverse source tables, pre-base matra/reph behavior, punctuation collisions, non-bijective symbol boundaries and semantic round trips.
Standard Chanakya vectors
Primary forward vectors plus semantic reverse checks. Walkman-Chanakya-905/901 is explicitly excluded because it uses a different mapping.
Shree714 vectors
The Shree route is pinned to Shree714. ShreeLipi715, Dev Ratna Universal and Shree Dev 0702 are treated as separate mappings rather than generic aliases.
AMS reference vectors
AMS-TTY / AMS Calligraphy reference examples, table checks and mixed-document behavior. Other AMS-named variants are not inferred from the family name alone.
Document and formatting invariants
Generated Hindi/English/number/punctuation cases, protected-token stress, Word span fragmentation, exact font-run scoping, tables, font size, line spacing and reverse mixed-font export safety.
Not claimed
This is evidence for specific mappings—not “100% accuracy” for every font with a similar name
- Every release or vendor variant inside the Kruti Dev, DevLys, Chanakya, Shree or AMS font families.
- Semantic correctness of names, legal language, addresses or document meaning without checking the source.
- Pixel-identical Microsoft Word wrapping after changing from a legacy font to a Unicode font with different glyph metrics.
- Every private-use symbol, decorative glyph, mathematical notation or proprietary mapping that is not in the evidence register.
- A universal percentage accuracy claim over an independently labelled real-world document dataset.
How to validate an important document
- 1. Confirm the exact legacy font/version or preserve Word font metadata.
- 2. Convert a representative section containing names, punctuation, numbers, conjuncts and tables.
- 3. Compare visible text against the source with the correct legacy font installed.
- 4. For mixed Unicode-to-legacy output, use Copy for Word so separate font runs are not discarded.
Release verification rule
The repository has one local release command that runs lint, TypeScript, architecture/catalog/product checks, the full converter suite, Office regressions and the production build. A converter branch is not considered release-ready until that command has actually completed successfully in a real execution environment.
Open converter directory