Docs: installed fonts in the font menus (gaps, parity, ROADMAP, README, architecture)

gaps.md records the Windows report and its fix under real-user experience and G2; parity.md's
Text row, the ROADMAP's reliability note and the README's Text bullet say text can use any
installed font; architecture.md says when the system font scan runs.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019EjTYdt76hTG4Kh2CJFnCr
This commit is contained in:
Claude
2026-10-06 15:14:55 +00:00
parent dda9961889
commit 0ffa2470b3
5 changed files with 12 additions and 9 deletions
+3 -2
View File
@@ -551,8 +551,9 @@ What keeps it fast:
- **Lazy open.** A project file carries its footage metadata, so File ▸ Open is read + parse +
swap. Nothing is decoded until a frame needs it, expressions compile on first evaluation
(cached by text), and system fonts are scanned only when a text layer asks for a family that
isn't bundled. The footage files are checked afterwards in the background (`footage.check`, a
(cached by text), and system fonts are scanned on first need (a text layer asking for a family
that isn't bundled, or a font menu or `text.fonts` listing the families); the desktop app starts
that scan on a background thread at launch, reading name tables only. The footage files are checked afterwards in the background (`footage.check`, a
"Checking footage" job in the Progress panel): missing items are flagged, items saved without
metadata are probed, and the project is not marked modified. The desktop app does this after
every open (`Session::check_footage_on_open`); headless sessions run `footage.check {wait:true}`.