What Shipping Hebrew RTL Actually Takes: Anatomy of an 11-Language Release

Shipping Hebrew as an 11th language requires more than just translating menu strings. It involves creating a full right-to-left (RTL) experience with behavioral tests, addressing 1,458 translation keys, 270 landing page keys, and 66 chat keys. The Windows installer uses MUI_LANGUAGE to carry all 11 languages, while macOS bundles declare CFBundleLocalizations = 11 to match the OS-level language picker.

RTL is not just a layout change; it requires flipping the writing direction and handling left-to-right assumptions. Every left-to-right element, such as icons, progress bars, and numbers, needs explicit handling. The test suite ensures actual RTL behavior, not just the font loading.

Translation quality is tested through 278 i18n-related tests, forming a regression baseline of 3,790 passing tests. Two key checks include cross-parity to prevent deleted features from leaving orphaned strings and rendered-layer scanning to catch raw key names leaking into the UI.

The release fixed 30 stale default model IDs within the i18n_translations.json file, demonstrating that translation files can become outdated like code. The process becomes an ongoing operation rather than a one-time task. Per-language health badges are displayed, making missing coverage visible and assignable. Community contributors can focus on specific languages and identify what's missing.

Localization became a maintained aspect with its own CI story. The September batch backfilled 65 pages, turning localization into a sustained effort. The registry-plus-badges pattern provides a cheap upgrade path for projects stuck at English plus machine-translated Spanish. Identifying locales that competitors overlook can present an opportunity.