When the thread for a fallback font search could not be created, the
characters taken for that search were lost. Characters no font covered
were already removed from the retry list, and characters met that frame
were already marked seen, so neither was looked for again. Now the
characters no font covered go back to the retry list, and the ones met
that frame are looked for when they are painted again.
A web test also checks that a face fetched again after a failure is not
fetched a second time at once, whether the interface asks for its
script again or the retry timer fires.
The demand-font retry deadlines were read from the wall clock. If the
system clock went back after a fetch failed, the retry timer fired but
the deadline still lay ahead, so the face was never fetched again that
session. The deadlines now use the monotonic clock (now_ms), and a retry
also starts when the clock reads earlier than the failure.
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.