Exporting, importing, and copying over workspace translations

You can easily manage your workspace translations via Backstage.

To do so, in the workspace main menu, go to Settings > Translations > Translations management tab:

Here you can:

1. Click on Export XLSX.
   This will generate and download a .xlsx spreadsheet containing all the translations for the workspace:
   
   In this spreadsheet you will find a first column containing unique keys that are used to identify each piece of UI text (label) in the workspace, and then individual columns for each existing language/translation for that key. More information on the default languages available.
   
   Using this spreadsheet, you can edit the existing default translations in the workspace, add entire new columns for new translations in the workspace, and then re-import the spreadsheet as explained below.
   
   To add new columns to the export, with new languages, you will need to add the language code in the first line of the report. The primary language code to be used must be in ISO 639-1 format, and can be followed by an optional second code that corresponds to the regional code (in ISO 3166-1 Alpha 2 format). It must be formatted as follows: "en", "en_US", "en_GB", "fr",  "fr_FR", fr_CA, etc.).
   
   
2. Click on Choose file, select the updated report, then click on Import XLSX. This will re-upload the selected .xlsx spreadsheet containing any new or updated translations for the workspace.

You can also Copy over the translations from the existing workspace into a new workspace.
This will allow you to Select an existing workspace using the dropdown, and then click on Copy to {{event name}} in order to take all the translations from the workspace you have open and copy (overwrite) them into the selected one:

Notes and best practices

• Translations can be exported from any given workspace in an Excel format.
• Translations can be imported into any given workspace in an Excel format.
• Any file that is imported using the Excel import tool will overwrite any previously existing labels. Any existing workspace-specific fields that are not included in the new translation import file will not be overwritten.
• All label translations must always be linked via the keys column in the Excel file. The "keys" column should therefore always be included/populated cor the file will not import correctly.
• It is best practice to keep the English translations so that, in case a translation is not added for that key it will display the English label.
• The importing of languages does not remove the requirement to set the target language for the workspace, under Settings > General > Language.