193 Hindi rows outside the plug-in messages said something other than
their English: "a number of points" read as "many digits", swatches as
clocks, crop as a harvest, resolution as a resolve, and saving used
words the glossary replaces. Others left English prose in place,
dropped a clause ("to keep them all", "what follows it") or ran the
sentence backwards.
- Rows use सेव, स्वॉच, क्रॉप, रिज़ॉल्यूशन, पाथ and टाइप (for a text
object) as docs/localization-hi.md sets them.
- Values a command reads (enum values, preset names, OpenType tags)
stay as the English writes them.
- A test checks those terms and the point unit in every Hindi row, and
another pins rows whose quantity or clause was lost.
- docs/localization-hi.md, docs/localization-parity.md and
docs/target-app-parity.md carry the new counts and a wording note.
The web build had no face for Hangul or Devanagari, so a Korean or Hindi
interface, and a layer or file name in either script, drew as
missing-glyph boxes.
- crates/text/web-fonts.txt gains a `demand` kind: NanumGothic Regular
and Noto Sans Devanagari Regular are served beside the wasm like the
other web faces, and fetched only when the interface language or the
interface's own text needs their script. They are not fetched at
startup or in the background queue.
- The interface reports the characters no loaded font covers
(`on_missing_glyphs`), and keeps them so that they are looked for again
when the font database changes. The frame after a face arrives adds it
to the interface fonts, and the frame after that draws the characters
painted before it with that face.
- After a failed fetch the next try comes about 30 seconds later, and the
wait doubles after each further failure, for at most five tries.
- A new test checks that the two faces cover every Hangul and Devanagari
character the catalogs use, where craft-fonts has them.
Docs: gaps.md, localization-hi.md, localization-parity.md,
target-app-parity.md.