Translating the Posters
We upload the current spreadsheet with translations in XSLX-Format into the new posters project on crowdin and set it up so that all languages are properly recognized. So we would have get all existing translations in Crowdin https://support.crowdin.com/csv-xlsx-configuration/#multilingual-spreadsheets
Then we would create one Google Sheet file per poster, so that it becomes simple to provide context to the translators via uploading images of the posters and mapping the texts https://support.crowdin.com/translation-process-overview/#upload-screenshots (that would be a tremendous hassle in one large file). We would download those files as XLSX and import them to Crowdin (see idea for automating this below).
Proposed Source File Format for one Poster (trivial):
| String | Context |
|---|---|
| BG_4 Dimensions_EN | Filename of the poster |
| Four Dimensions | Title of the Poster |
| ... | ... |
- Tracking changes When working on the posters, changes would be tracked either in a changelog, or directly in the google sheets that contain the source strings.
-
Upload to crowdin We could automate uploading the google sheets to crowdin (wget the document
/export?format=xlsx, upload via crowdin CLI) as a new branch). - (optional) Attach strings to screenshots of the posters
- Translation Translators are notified when new untranslated strings are available. They translate them.
- Proofreading When the project is fully translated, proofreaders are notified, and they proofread. We might even add a second proofreading step (so that each lead translator for the practical guide could then proofread their language as well)
- Updating Grafio files When proofreading for a language is complete, proofreaders would notify the people who update the files. They then review all translations that have been added (or updated) after they last updated the file directly in Crowdin, and update the Grafio files (see below Identify updated translations)
- Export Grafio files are exported to PDF.
- Celebrate
That is a pretty simple and foolproof workflow, because: any changes in the posters that somehow have not been tracked would be identified when mapping strings to images of the posters.
Crowdin supports the following bilingual file formats:
- XLSX: supports multilingual spreadsheets (one column per each language), see https://support.crowdin.com/csv-xlsx-configuration/#multilingual-spreadsheets
- CSV
- XLIFF (contains translation status for each string, untranslated strings are marked with state="needs-translation" attribute)
- QT TS
To find out for which strings the translations have been updated, just set a filter in the editor:
Place any important onboarding information for translators in the public description field in Project Settings
The information placed in this field appears on the main page of a project, so every translator will notice this info
