Repository navigation
fix(ci): localize the chat font family search keywords - #33715
Conversation
#33687 added English-only search keywords and a code sample to the chat font setting, which fails main's localization coverage check.
|
No actionable comments were generated in the recent review.
|
stablyai#33687 added English-only search keywords and a code sample to the chat font setting, which fails main's localization coverage check. (cherry picked from commit 5dfaee0) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…33715 The cherry-picked upstream fix adds two en.json keys that upstream has not translated yet; fork-locale-parity counts them as fork keys until a release carries them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…33715 The cherry-picked upstream fix adds two en.json keys that upstream has not translated yet; fork-locale-parity counts them as fork keys until a release carries them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…33715 The cherry-picked upstream fix adds two en.json keys that upstream has not translated yet; fork-locale-parity counts them as fork keys until a release carries them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ELI5
Main's localization check fails because the new chat font setting (#33687) added search words that are only in English. This makes them translatable like the rest of Settings.
What Changed
translateSearchKeyword. They reuse the existing "Chat" and "Font family" strings and add two new English strings ("typeface", "typography"), which are indexed alongside the English words.fontFamilytext in the font preview is a CSS property name shown as code, so it's added to the localization allowlist as a reviewed exclusion.Verified
verify:localization-coverage,-catalogs,-catalog,-runtime-catalogand-extractionall pass.pnpm tc:web, oxlint and oxfmt are clean.