Ten-Language Telegram UI, 1:1 Parity

The ten languages

The three rules the codebase enforces

• One catalog, ten columns. A key exists in every language or the parity audit fails — there is no partial translation state in a release.
• No hardcoded language branching in UI code. Labels resolve through the translation helper with an explicit language, and English is the only fallback. Persian is never used as a default.
• RTL correctness is checked, not assumed: the audit verifies that English values contain no RTL script, so a copy-paste slip cannot leak Persian into the English interface.

Audits you can run yourself

atf i18n                  # catalog parity, placeholders, RTL leakage
atf validate              # includes the catalog checks in the standard gate
atf validate --deep       # adds the repository's own cross-language audits

Adding a language

Add the column to the catalog, and the audits will tell you exactly which keys are missing and which placeholders do not match. Placeholder parity matters as much as key parity: a translation that drops {count} breaks the message it renders.

Frequently asked