Translating a campaign
Overview
To get actionable feedback from your end-users when you publish a campaign, it is essential that the end-users can clearly understand the questions being asked, as well as all the possible answers. The level of clarity and precision required is often only achieved if the campaign is written in a language that the end-user speaks fluently.
In multilingual environments, translate your campaigns to the different languages spoken by your community of end-users to communicate with them in their own mother tongue whenever possible. When an appropriate translation is available, end-users receive the content of the campaign in their language of choice, according to the language settings of their operating system.
Providing translations
When you create a new campaign, you write the questions and possible answers in a particular language. This language is called the base language of the campaign.
To provide a new translation for a campaign, find the Translations section at the bottom of the campaign editor:
Click the link that reads Click here to add a new translation.
Depending on other translations being available:
If this is the first translation of the campaign, specify the base language:
In the dialog, select the language in which you originally wrote the campaign from the Base language list.
Click OK.
If there is at least another translation available, the base language was already defined. No dialog to choose the base language shows up.
In the dialog, select the target language of the translation from the Additional language list.
Click OK. The list of available translations gets updated under Translations.
Optional: Repeat from step one to add as many languages as necessary.
Translating campaign text
Once you have created a new translation, it is displayed in the list in an error state because the translation is incomplete. Indeed, you need to provide actual translations for all text items in the campaign that are visible to the end-user; that is:
The title of the sender.
The header and the footer of the campaign notification.
The displayed text of questions and answers.
The greetings, header, and footer of the first question.
The final message after the last question.
For translating the text of a campaign, Nexthink has adopted the PO format. The translation cycle consists thus in exporting the untranslated text of the campaign to a PO file, provide the translation of all text items to the target language with the help of an editor, and import the edited PO file back into the Finder.
To translate the text items in a campaign:
Under Translations, find the entry in the list of available translations that corresponds to the target language.
Click Export, the first option in the fourth column, to export the translation to a PO file.
Select a destination folder for exporting the translation.
Click OK. The Finder creates a folder with the name of the campaign in the chosen destination folder and a PO file inside it. The name of the PO file has the format
Campaign_name.language_code.po.
Edit the PO file. You can use any of the specialized PO editors available in the market (recommended) or a plain text editor that supports UTF-8 character encoding.
Provide a translation for every text item in the PO file.
Save your changes.
Back to the Translations section in the Finder, click Import, the second option in the fourth column of the corresponding entry in the list of available translations, to get the translated version of the campaign.
Select the PO file with the translated text.
Click OK. The state of the translation in the Finder should be updated to complete and show no errors.
If the translation still shows as incomplete, go back to the previous main step and ensure that you provide translations for all the text items in the PO file.
If the campaign changed while you were editing the PO file, go back to step one.
Optional: Click Preview, the option in the sixth column of an entry in the list of available translations, to inspect how the translated campaign will display in the devices of the end-users.
Optional: Click Remove, the third option in the fourth column of an entry in the list of available translations, to delete it.
Click Save to store your changes.
Before a campaign is published, if translatable text items are created or modified after you provided a translation for the campaign, the translation enters the incomplete error state again. Re-export the translation and provide the appropriate wording in the target language for the missing or modified items.
Default language
When displaying a campaign to an end-user, the Collector tries to find an appropriate available translation that matches the language settings of the operating system in the device of the end-user. If the Collector is not able to find such a translation, it falls back to the default language of the campaign.
By default, the default language of a campaign is the base language. To change the default language, open the campaign editor:
Under Translations, find the entry in the list of available translations that corresponds to the language that you want to set as default.
Click Set as default, the option in the fifth column, to make the language of the translation the default language of the campaign.
Click Save to store your changes.
If the translation selected to be the default is later removed, the editor resorts to the base language as the default language of the campaign.
Language of buttons in campaign notifications
The messages displayed on the buttons in the notifications of campaigns to accept or reject the campaign, ask for a reminder, etc. are also translated according to the language settings of the operating system running on the device of the end-user.
For these messages, however, the set of languages available is predefined by Nexthink and it is not possible to manually provide a translation. This is the list of currently supported languages:
|
|
|
|
Displaying translations in devices with outdated Collectors
For end-users with versions of the Collector prior to 6.9 installed in their devices, campaigns may be displayed only in their base language or not be displayed at all. See the article on the display compatibility of the Collector with campaigns for specific support information by a particular version of the Collector.
RELATED TASK
RELATED REFERENCE
Last updated