Localisation Step 1 - Translation of XLSform

[dave-mills]

Teams can download an Excel file for each of their xlsforms. The file contains only the columns that require translating from the xlsform, and space for the translated strings. The teams can complete the Excel file offline, then upload it into the system. The translations will be added to the xlsform and be made available within ODK Collect.

Notes / Requirements

• Teams should select the language(s) they will work in before downloading the Excel file, so we can make sure the column headers are correct.
• Ideally, existing translations will be offered to teams. E.g., if Team A adds a Malagasy translation, Team B should be offered that translation as a starting point if they also choose Malagasy. Technicall, I see 2 options for this.
  • If the translations are linked to the specific Team (via Xlsform), then we would offer to copy that translation over to Team B if they choose to use the one made by Team A.
  • Or, the initial translations done as part of Localisation Step 1 can be linked to the XlsformTemplate instead of the Xlsform. This approach is more logical if we want to encourage the idea that there is this collection of translations for the core HOLPA tool that teams select from. When a team selects a language that doesn't already exist, they will then be asked to create the translation, with the agreement that their translation will become the 'default' starting point for future teams using that language.

[dave-mills]

This issue will be complete once we have the ability to do the following on the admin panel:

• list the available languages for any XlsformTeamplate
• get the downloadable translation Excel file for any XlsformTemplate
• upload a completed translation Excel file and have it populate the database (and validate that the translations are complete)
• highlight translations that need updating after a template is updated.