Do you need your Motis to be available in multiple languages? ๐
No problem - we got you covered! You can easily create language specific versions of a Moti, and users will automatically be shown the version corresponding with their preferred language.
Once you have completed your Moti in the default language, you can start creating translations. You will still be able to make changes to the default language version after, but we recommend you complete the Moti as much as possible before you start translating it in order to make the process as streamlined as possible. Choose whether you want the entire Moti to be automatically translated, or if you would rather do it yourself. Either way, you conveniently manage the various translated versions within the same Moti in Studio.
Jump to:
-
Automatic Translation
-
Manual Translation
- How to change the title and description of the Moti for a language/translation
Automatic Translation:
Translating your Motis have never been easier - by opting for Automatic Translation, the whole job is handled for you and only takes a few minutes. This is all you have to do:
- First identify any words or lines of text that you don't want to be translated. This might be company names, phrases or words that might make sense to keep in English (ie. During your onboarding you will be assigned a "Buddy"). Simply highlight such text, then use the 'Do not auto-translate' option as illustrated below.
You can also wrap text that shouldn't be auto-translated as such:%nt{but this text should not be translated}
Here you can see an example of the result after auto-translating the Moti to Polish:
Please note:
This feature to exclude text from auto-translation does not support text in Moti titles, Moti descriptions or Chapter titles.
-
Navigate to the Moti Settings, and click on Add Language.
-
In the popup that appears, toggle Automatic translation ON.
When enabled, the Title and Description fields will be locked and automatically translated. -
Click Add in order to start the automatic translation of the whole Moti.
While the translation is in progress:-
The Editor tab will be disabled.
-
A loading icon will appear next to the new language in the Settings tab.
-
-
Once completed, you should review the translation and ensure it is all correct.
While AI tools are great assistants, they can make mistakes. This means that we are subject to the same limitations that the AI tools we rely upon for the automatic translation feature. All auto-translated content should therefore be reviewed before publishing.
Some graphical elements might also need replacing if they are not accessible for translation (ie. pictures with text in a Gallery block). -
Once you are satisfied that the translation is correct, you can approve the translation.
Translating New Content
If a Moti has already been translated into one or more languages, and new content is added to the default language version, a translation update can be performed in order to translate the new content.
Simply go to the Settings tab within the Moti, find the language section, and click the "Refresh" symbol next to each language you want to update the translation for.
Please note that this method only applies to new chapters and/or new blocks. If content within an existing block is updated, this will not be picked up using this method. In such cases, it might be best to delete the whole translation, and then auto-translate the entire Moti again.
Don't forget to approve all the translations once you have reviewed them and confirmed everything is correct โ
Limitations to Consider
-
Character Limits:
-
No support for chapters exceeding 50,000 characters.
-
Weekly translation limit per organization: 2 million characters.
-
-
Translation Scope:
-
Auto-translate only works for new content blocks.
-
Modifications within existing blocks will not be automatically translated.
-
-
Language Restrictions:
-
Azure does not support Norwegian Nynorsk or Northern Sรกmi.
-
-
Editor Responsibilities:
-
Ensure proper alignment of elements (e.g., Posters) in auto-translated languages.
-
Verify the accuracy of proper nouns, as they may or may not be translated depending on the provider.
- Consider using placeholders / dynamic variables ( ie. %{OrganizationName}) in order to ensure that certain names and values does not get translated automatically.
-
-
Access Restrictions:
-
The Editor tab will be inaccessible while the translation is in progress.
-
Best Practices for Editors
-
Always review translations before publishing.
-
Manually update key terms if necessary, especially proper nouns.
-
Use full re-translation when major content changes occur.
-
Keep track of character limits to avoid exceeding the weekly quota.
Manual Translation:
- You can add a translation to a Moti that is in Edit-mode, or one that's already Published. To add a translation to a Moti which is in edit mode, just go to the Editor and then click Translate:
If you want to add a translation to a Moti which has already been published, go to the Editor and click Create a draft, and then Translate. The next steps are identical to both options.
- You will first be asked to select the language are you translating the Moti into, then you ensure to leave the "Automatic translation" option disabled, before you manually enter the translation of the Moti title and description. Click Add.
- Nicely done ๐๐ผ You can now switch between the different language versions via the drop-down menu at the top.
- Ensure the new language version is selected and click Edit chapter. You will see all the blocks in the original language, and you can start translating the chapter, one block at a time. Update every text object, and note that images containing text might also need updating/replacing. You will also see that blocks are locked to the original version - you can't add or remove them, only translate. If you want to add or remove blocks, this needs to be done by editing the original language version.
- When you are done, hit Save.
- Don't forget to also translate your chapter titles!
-
Look at you go!! When you're happy with your translation, repeat for the rest of your chapters.
- When you're done, it's time to finish up.
โ๏ธIf your Moti was already published when you started, you can simply click Approve and publish in the top right corner.
โ๏ธIf your Moti was in Edit-mode you switch back to the original language and go ahead and approve the original version. Once that's done, it's time to approve the new translation. This is done by either switching to the new language again and clicking Approve, or by going to the Settings page and scrolling down to Languages.
Click the Options button for the language which will be In Progress, and click Approve translation:
Note that unless you are Chief Editor, you'll need to request the approval and wait for the Chief Editor to approve for you.
Finally click Publish to roll the Moti out to the employees that's been assigned to it.
-
Now give yourself a pat on the back ๐
Your translation is now completed, approved, and published ๐
To make changes to a translation, go into the Editor and repeat the process. You can also delete translations completely from the Languages section of the Settings page.
How to change the title and description of the Moti for a language/translation:
Changing the title and description of your Moti is very straightforward when there is only one language - you simply update these details at the top of the Settings tab of the Moti. Once your Moti has more than just one language however, following the same procedure will only update the title and description for the default language version, and not for any of the translations.
In order to change the title and description for a translation, you go to the Settings tab of the Moti, then scroll down to the Languages section and then click the options button [...] for the language in question. In the menu that opens, click Edit title and description.
Please note:
- You should never translate a Moti with several editors simultaneously. If you want a colleague to help you out, ask them to do so once you are done and have saved your changes.
- Adding translations to Packages and Learning paths are made in similar ways and is even easier.
Check out the following related articles as well: