Learners can select a different language for viewing your enablement site. To provide
localized versions of your learning content for supported languages, work with a localization team
or vendor.
Required Editions
| Available in: Enterprise, Performance, and
Unlimited Editions
|
| User Roles |
| This topic supports these enablement site
roles: |
- Release Managers
- Localization Team or Vendor
|
- Considerations for Languages on Your Enablement Site
The default language for any enablement site is English, but other languages are supported. A user can select a different language, but the extent to which content is available for any language depends on whether you’ve localized and published content for that language.
- Give Content Files to a Localization Team or Vendor
To add localized content, send the backpack to your localization team or vendor. The backpack is a ZIP file, downloaded from Trailmaker, that contains the module or trail’s source files. You can send the backpack ZIP file or give the vendor access to your version control system (VCS) to download the backpack. After the vendor translates your content, the vendor can upload the backpack—updated with the localized files—to your VCS. Then, you can publish the localized content.
- Guidelines for Localizing Files in a Backpack
Your localization team or vendor can localize only certain trail, module, unit, and quiz information in your backpack’s files.
- Preview and Publish Localized Content
After you receive the localized backpack and confirm that the appropriate updates are complete, set up a release and preview the translated content. Then, publish the release.
- Troubleshoot Localized Content That Appears in the Wrong Language
Did you localize enablement site content for a particular language and a user selected that language, but the content still appears in the source language? Most likely, the number of units in a module differs between the source and localized files. When content isn’t available for a selected language, an enablement site falls back to the source language. To resolve this issue, work with your localization team or vendor to correct the number of units in a module in the localized files.
