Master List of Language/Crowdin Issues

[ErikSin]

Background

We are updating our translation process with the intention of creating an easier workflow for people translating our app through crowdin. To do this we are:

• Objective 1: Classifiy string in crowdin as primary and secondary so translators know which string to prioritize. In Crowdin we are creating separate folders called primary and secondary, primary will contain the strings that have been indicated as necessary to understand the basic functionalities of the app (eg, taking an observation, joining a project etc). All other strings will be put into secondary. This will help translators know which strings to prioritize.
• Objective 2: Creating 1 crowdin project where translators can translate strings for both this mobile app and comapeo desktop to allow ease of access. In order to be able to translate, people need to be approved by a crowdin admin. This is to remove the barrier of having to be approved for both projects.

In the process we are also going to take this opportunity to update some of the tooling used for the translation process, with the hopes of streamlining the workflow for the developer and optimizing the app.

Order of Operations

The work must be done in this order to properly migrate translation from one crowdin project to another

1. Prep Crowdin Project
2. Mark Primary Strings and Update Extraction Script
3. Turn On Github Crowdin Integation (Upload Only)
4. Migrate Translated Strings to new Crowdin structure
5. Update Compile Messages Script and how message are consumed by App
6. Crowdin Email Reminder