Overhaul translations setup #499
Description
Details
There are a variety of limitations with how our translations are set up at the moment. Gregor and I started experimenting with a few improvements to our process as an org and how it maps to the technical pieces of integrating translations. Some takeaways (so far):
Consolidation of the desktop and mobile projects on Crowdin
Mostly for the sake of Crowdin project management. The only anticipated technical consequences are:
- updates to the repo's crowdin config
- updates to the github integration
- updates to the repo's message extraction tooling
We need to introduce some kind of category indicating importance of a given message
The early idea was to have 3 categories: core, primary, and secondary. These indicate a message's importance to the usage of the app and can be used as a concrete measurement of how "ready" a language is to be used within the app. For example, we could define a usable language as a language that has all core messages translated, meaning that it will be surfaced as an option for the language settings. Having the additional categories of primary and secondary is mostly useful for translators to understand prioritization.
We can potentially use this feature in formatjs in order to facilitate categorization of messages and how they're extracted for usage in Crowdin.
Designs
N/A