Reviewing a translation is technical work

Localization is not a find-and-replace step at the end of publishing. It is a technical review that happens alongside the English source, with the same standards for accuracy.

What a translation reviewer checks

• Terminology: does “element” mean the same thing in this language as in the spec?
• Code: are identifiers, attribute names and error messages left untouched?
• Direction: does the layout still work when the language reads right-to-left?
• Examples: are names, addresses and currency localised or intentionally neutral?
• Freshness: did the source change after this translation was approved?

Why we ship English and Bengali first

A small number of deeply reviewed locales is more useful than dozens of shallow ones. English and Bengali are our first release pair. Every additional locale needs reviewers, not just a translation file.

The implementation uses a locale registry, stable lesson IDs, a persisted language preference and a visible English fallback. Adding a language is an editorial decision, not a database migration.