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

The MeshCtx project shipped Hebrew as its 11th fully supported language, completing a right-to-left localization effort for the open-core AGPLv3 memory layer for AI agents. The release added 278 i18n-related tests within a 3,790-test regression baseline, per-language health badges, and a fix for 30 stale default model IDs in its translation file.

Everybody "supports multiple languages." Almost nobody ships Hebrew. When we closed the v3.131.x line on MeshCtx https://github.com/LucyAndLuna2023/meshctx — an open-core AGPLv3 memory layer for AI agents — the headline feature wasn't a model integration or a new API. It was making the 11th language, Hebrew, real: not Google-translated menu strings, but a full right-to-left experience with behavioral tests. Here's what that actually involved, with numbers from the public changelog. MUI LANGUAGE — and yes, there was a bug where page translation binding required MUI PAGE . That class of installer-level i18n bug never shows up in your app code. CFBundleLocalizations = 11 Arabic and Hebrew flip the writing direction, and every left-to-right assumption breaks: dir attribute dir=ar|he 278 i18n-related tests live inside a regression baseline of 3,790 passing tests . Two checks worth stealing: signup.title instead of text" class of bug, caught before release. One release fixed 30 stale default model IDs inside i18n translations.json itself — proof that translation files rot like code does. The UI shows per-language health badges , so missing coverage is visible and assignable — community contributors can pick a language and see exactly what's missing. A single September batch back-filled 65 pages . Localization became a maintained surface with its own CI story. MeshCtx is AGPLv3, downloads for Windows/macOS/Linux on the releases page https://github.com/LucyAndLuna2023/meshctx/releases . If your project is stuck at "English plus machine-translated Spanish," the registry-plus-badges pattern above is the cheapest upgrade path. Which locale does your tool ignore? It's probably the one your competitors ignore too — that's the opportunity.