When creating a new Journey, you need to specify a primary language for the content to be written. The content is thus created in that language.
Once the primary language is set, it cannot be changed. You can localize a Journey’s content by defining one or more secondary Languages.
These are defined in the Translations tab of Sites. Each Language corresponds to a translation of one source to one target language. For example, if a Journey’s primary language is English, you can define Languages for translations from English to any or all of the supported languages.
For each Language you create, you can export a language package, which you provide to your human language translator(s). The exported language package is a ZIP archive named Translations.zip , which contains one or more .xliff files, each one corresponding to a Journey defined in the Site. If Feedback is enabled, a file containing feedback messages will also be exported.
These translation files are a file type supported by many professional translation software applications. They contain an industry standard XML structure. If no translation software is available, translators can open and edit the file with any XML or text editor application.A syntaxaware editor such as Notepad++ (Windows) or TextMate (Mac) is recommended, as the strings to be translated are easier to identify on these editors.
In the translation files, Journey content is written into two sets of elements:
- <source> - contains content in the primary language of the Journey.
- <target> - initially contains the same content as <source>. Translators should replace it with content translated to the target language.
Here you can see an example, where the source language is English and the target language is Danish, already added to the script by the translator:
When all translation work is complete, you upload the modified .xliff files via the Translations tab of the Site from which they were exported.
IMPORTANT: Do not change the original filenames of the .xliff files. The next sections describe the process for localizing Journey content.
The following screenshot shows an example of the two files (feedback and journey) from English to Danish.
Adding a new language to be translated
1. On the Newired portal, open a site and select the Translations tab:
2. Click on Add language
3. Select the target language for translation of Journey content
Note that translations will not appear inside the Editor, but only in the published content, on the live site.
Exporting a language package
1. On the Newired portal, open a site and select the Translation tab
2. Click on the Download icon on the row of the target language:
3. Save the Translation.zip file to any convenient location on your computer or network. You can either provide the entire language package to your human language translator, or unzip it and just provide one or more .xliff files for them to translate.
Translation of Feedback Messages
If user Feedback is enabled, the exported language package will contain a file named Feedback_to_??_??.xliff (where each ?? pair is an upper or lowercase language identifier - feedback_to_cs_CZ.xliff, for example) .
This file contains all the strings for user feedback messages. Its underlying structure is different from those for Journeys, and the source language is specified as unknown because it is in the default language of the Site, and there is only one possible source for the content. Translators can edit it the same way as the other exported translation files.
Upload Translated Content
After the translation is complete:
1. On the Newired portal, open the Site from which the language package was exported.
2. Select the Translations tab
3. Click on the Upload Translation button, and select a translated .xliff file on your local system.
The portal will automatically check if the files are valid for processing. If a file contains non-critical errors, such as invalid HTML tags or attributes, a warning will display, but you will still have the option to upload the file with errors. If it contains critical errors, such as missing required elements or IDs, or incorrect structure, a message will be displayed and you will not be able to upload the file without addressing those errors.
After the upload, it is possible to export the files again. The language package will contain the cur- rent state of the translation work. For example, if you find you can improve the translation of some content that has already been localized, just repeat the process of exporting a language package and uploading modified .xliff files.
The most important thing to notice regarding translations is that you can select which translation(s) you want to publish. The table on the Publish tab of Sites has a table listing the Journeys and the translations, if any. You can select which language translation(s) you want to publish, including the primary language if applicable, by checking the box in the column of the language(s) on the row of the applicable Journey.
If you click on Select All, you can quickly see which translations are available to publish, and thus proceed to uncheck the boxes for any translation you do not wish to publish.
The process for publishing Journeys is described fully in the section Content Deployment.
After the translations are published, end users of the web application or website will be able to select their preferred language for the Journey content. To do so, they need to click on the language shown on the bottom right of the Journey list:
And then select the Journey and Website language from the list: