A guide to translating content within the Learn platform. This video covers how to enable translations, manage different language versions, and maintain consistency across materials.
You can watch this video for an overview to learn about this topic or keep reading the article below.
Translating Learn content
Learn is designed to be used by all audiences, in any country and in any language, and as such all content in the app can be translated to ensure end users view content in their native language.
After creating content in the app in its default language, content can then be translated, and depending on the content type translations can be applied in one of two ways:
- Per-block translations
- Apply to the following:
- Article stages
- AV stages
- PDF stages
- Resources
- Apply to the following:
- Page-wide translations
- Apply to the following:
- Quiz stages
- SCORM stages
- Missions
- Levels
- Pathways
- Notifications
- Apply to the following:
PER-BLOCK TRANSLATIONS
Per-block translations are applied to the individual blocks used to make up the content of stages, using the language button in each block's toolbar:
The default language of all blocks is English. To add more language options for translations, contact your system administrator and they will be able to add more languages following the steps in the Global Languages stage.
Clicking the language button in a block will show the list of all languages available to translate content into, and after selecting a language, the block will save the content it currently contains as the "English" content, and will clear the block for you to add the "translated" content.
Once cleared you can then add the translated content for the chosen language in the block.
In this way, the block will have versions of its content added under each translation option, which it can then present dependent on the language of the user's device.
Each translation of the text is saved in the block
PAGE-WIDE TRANSLATIONS
For pieces of content that don't use blocks, translations are instead set across the whole page in one blanket applications, using the Language section of the publication section in the top right of the page:
Selecting an option from the list of available languages will refresh the page, and then show the content of all fields in the page with their current content greyed out, over which you can add translations, as shown in the mission’s example below:
The original English title
Once the language is changed to French, the field empties and shows a greyed out version of the English content.
The French translation, added in the field to appear when on a French device
HOW DOES THE APP APPLY TRANSLATIONS IN THE FRONT END?
The front-end app will attempt to present content in the same language as the standard language of the device it is being used on. For example, if a user's phone is set to use French as its language for all system settings, the app will also try and show content in French.
When trying to present content to the users, the app will again try and show content that has been set under the device's system language. If, however, there is not a version of content in the language, it will instead use the version of content in the default language. For this reason, to ensure users always see a version of the content in their own language, the most important version of content is in the default language.
All structure text in the app, such as button and navigation text, supports translations into 18 languages. If the language used on the device is not supported the text will instead be shown in English.
The introduction of 5G will allow consumers fast access to necessary information, aiding mobile purchasing as well as browsing on-the-go. For stores offering free Wi-Fi, there will be the expectation that these speeds will be matched.