Localizing JSON-based apps can be straightforward, but there are several pitfalls to watch out for:
- Unclear or cryptic keys: keys like
"msg1" or "btn2" may give very little context to translators, leading to inaccurate translations. Always provide descriptions or context notes.
- Inconsistent placeholders: failing to preserve
{variables} or %s placeholders can break runtime messages. Use Localazy’s placeholder highlighting and QA checks to avoid this.
- Ignoring plural forms: many languages have complex plural rules. Translating only the English singular or plural can result in incorrect messages in other locales.
- Broken JSON syntax: missing commas, braces, or quotes can make JSON files unreadable by the app, which results in an error message stating that the file cannot be uploaded.
- Divergent key structures across environments: differences in key hierarchy or naming between repositories can lead to confusion or duplicate translations. Localazy’s connected projects and duplicity linking help reuse translations across projects, but they don’t replace disciplined key naming and repository practices.
- Overwriting translations: Manually editing JSON files without tracking changes can overwrite previous translations. Using Localazy ensures a single source of truth for all languages.