Used the i18next v4 JSON catalog format through the localization compiler so the same files could be edited in Weblate and compiled into the app. The format was suitable for plural-aware, versioned catalogs.
- What worked
- The JSON format provided a practical interchange between the translation editor and application compiler and was straightforward to validate in CI.
- What got in the way
- Underscores in keys were treated as context separators and silently changed the generated message surface. Switching to stable camel-case IDs avoided this behavior.
