Articulate Localization: Create Multi-Language Rise 360 Courses
With Articulate Localization, you can translate course and microlearning content into 80+ languages and manage all the language versions as a single project, right from the Rise 360 dashboard. Watch the video to learn how to translate and share the translations with validators. Then read on for more details on managing multi-language courses. Translate a Course Early-Access Course Stacks Translate Text Updates Manage Languages Add or Replace a Language Remove a Language Capture Course Stack Versions with Snapshots Save a Copy of a Language Localize Media Assets Localize Video Assets With Closed Captions Localize Audio Assets With Transcripts Generate Translated AI Text-to-Speech Tips Add Collaborators Localize Video and Audio Assets Understand Question Banks Include Right-to-Left Languages Translate Storyline Blocks for Use in Rise 360 Courses Translate a Course Before translating your course, run through this checklist to avoid common issues. Prepare your course for AI translation with the following best practices: Avoid using all caps to emphasize certain words. AI translation often interprets this as an acronym and won’t translate it. Avoid splitting a sentence into multiple text blocks, as this removes necessary context for effective translation. Avoid using emojis. Their meanings can vary across cultures, and machine translation tools may not interpret them accurately. Use proper grammar. Simplify formatting. Complex formatting can create challenges for all forms of AI translation. Here are some best practices: Don’t format spaces. Let Rise 360 handle text wrapping. Using shift+enter to manually insert line breaks will impact other languages, where it won’t always be appropriate. Scan through your content one more time for terms that might need to be added to the AI translation glossary. The glossary specifies how terms are translated—or not translated. For example, you might have a specific term for “service” in a particular language. Or you may want to make sure your brand name does not get translated. Include closed captions with video assets, and add transcripts to blocks with audio so they can be translated automatically. You can also add AI-generated captions with AI Assistant. If you have AI Assistant and the target language is supported, add your narration with AI-generated text-to-speech to automatically generate translated versions. Once you’ve double-checked your course, follow these steps to get started with Localization: In your dashboard, hover over the content tile for the course you want to localize, click the more (...) icon, and select Translate. A translation dialog will appear. You can confirm the source language, select one or more target languages, and adjust the formality if the languages support that option. Choose a glossary for the translation run. This glossary will be used for all succeeding translations for this course, including updates. Click Translate. Rise 360 will create a multi-language course with all the language versions presented as a single course “stack”. The course stack tile on the dashboard indicates how many languages are in the stack, as shown below. Multi-language courses share the same theme and structure. If you add, move, or delete a block, lesson, or section in one language, those changes will apply to all other languages in the course. Other factors to note: Clicking the tile opens an overview page that lists all the current languages in a sidebar and allows you to preview each language. Click EDIT COURSE to make changes to any language version. The language dropdown on the top left lets you switch between languages while authoring, as shown below. Here are some guidelines to keep in mind when choosing a language from the dropdown: Stay in the source language if you want to make changes in all languages, such as updating course content, adding new blocks, lessons, or sections, and changing themes. Switch to a target language if you want to make language-specific changes, such as replacing media assets, editing existing text, and changing course labels. Custom label sets are not translated, but translated courses will automatically have default label sets for each target language. If you prefer to use custom label sets, you can assign them to individual language versions after translation. Similarly, code blocks will be the same across all languages after translation. You can have language-specific code blocks by modifying the code for each language after translation. If you accidentally choose the wrong glossary, translate the course again and select the current languages to enable the Glossary field. Custom blocks are not currently supported for Localization. Early-Access Course Stacks Multi-language courses created during our early-access program will have an [Early Access] tag on the course tile and course stack. This older version has the following differences: When you add languages to a Rise course, each translated language becomes a separate copy of the original course, so changes you make to one language version will not affect other languages. To edit an individual language, switch to it in the sidebar and click the Edit button in the top navigation bar. Any changes you make affect only the language you are currently editing. There’s no option to translate updates to the source language and publish a single-package, multi-language output. Learn more about the early-access version of multi-language Rise 360 courses. Refer to this user guide when working on this version. Translate Text Updates Rise 360 detects text changes made to your source language after the last translation run. It allows you to translate these changes without affecting other portions of the course. If the unchanged portions have imported validation suggestions, these will be preserved. Here's how it works. Update existing text or add blocks to your source language. A blue notification dot appears on the language dropdown on the top left. Click the language dropdown and select Back to Stack. From the course stack, click Update Translation to translate only the text updates you made for all existing target languages. When the translation run completes, the Update Translation option disappears. Additional information: Text updates are determined by translation units called text segments. A text segment breaks down the source text into smaller parts while retaining its meaning in context. Segments can vary in length and structure—from single words to complex sentences or even short paragraphs, depending on context. In Rise 360, a segment is typically the text in a block. Any text change in a segment will retranslate the whole segment. You can see how your course is broken down into segments when you publish to Review 360 and view the translation table. If your course has already been validated, follow the tips in this article to request validation for only the updated content in Review 360. Importing validation suggestions or updating text in the target languages will not enable the Update Translation option. Adding blocks, lessons, or sections to any target language will also apply to other languages, but they won't get translated. If you accidentally added them to the target language, simply delete them and recreate them in the source language. You can’t duplicate or send a copy of the multi-language course until all pending translations are updated. Translating updates within the same Articulate 360 subscription contract term does not affect your total purchased translation. Manage Languages You can add or remove languages from a multi-language project and create snapshots at any time. You can also save a copy of a language as a separate course. Add or Replace a Language To add or replace (retranslate) a language, re-run the translation tool by selecting Translate from the stack tile option in the dashboard or clicking Translate at the bottom left of the stack overview. If the language exists in the course stack or the Archived Translations folder, click Translate again to overwrite existing versions. Note: Retranslating or using AI translation for existing languages in a multi-language course within the same Articulate 360 subscription contract term does not affect your total purchased translation count. However, if you duplicate the multi-language course or send a copy to someone else, any new translations on the copy—including translating text updates—will be counted. Remove a Language To remove a language, click the ellipses (...) beside the language from the stack overview, and choose Archive. The language moves to the Archived Translation folder at the bottom left. You can restore or permanently delete the language from the Archived Translation folder. Retranslating archived languages will also permanently delete the versions in the Archived Translations folder. Capture Course Stack Versions with Snapshots Create and manage snapshots of your multi-language courses by selecting the Snapshots menu next to the course title in the course stack overview page. Similar to single-language snapshots, versions are automatically generated whenever you publish a multi-language course. You can also save different versions and restore them as needed. Key points to remember: Snapshots are not available in early-access versions. Snapshots created before you translated the course are still included. While you can't revert to these pre-translation versions, you can save them as a new course or microlearning. Restoring an earlier version won't impact your translation count. If any languages are removed during a restore, retranslating them is free, as long as you do this within the same billing period. Save a Copy of a Language To save a language as a separate course or microlearning, click the ellipses (...) beside the language from the stack overview, and choose Save as. Give the copy a name and click Save. The copy is saved in the same folder as the multi-language project and includes the default label set for the corresponding language. The label set is also added to the list of built-in label sets under Course Settings. Localize Media Assets Images, audio, and video assets will be the same across all languages after translation. Any changes you make to the media—such as alt text or image alignment—in the source language will be applied to all target languages. You can have language-specific media by modifying the media asset in the target language. Remember that editing a target language disconnects the asset from the source language, so any changes made to the source won’t be applied moving forward. For audio assets, you can reset the target language audio by clicking the Options (...) icon on the right of the audio player and selecting Revert to source audio. Localize Video Assets With Closed Captions Localize video assets automatically by adding closed captions before translation. Captions translate along with other course text when you add new languages. They’re also included in the validation process when you publish to Review 360 for validation. Validators can play the video and click the CC button to display the captions. Learn how to add closed captions to videos or add AI-generated captions with AI Assistant. Localize Audio Assets With Transcripts For blocks with audio, you can add transcripts after recording or uploading your narration. These transcripts will be translated automatically. To include a transcript: Enable the Transcribe audio file toggle when you upload or record audio. Or, generate text-to-speech with AI Assistant, which automatically includes transcripts. Read on for instructions on using AI Assistant to generate audio and transcripts. Generate Translated AI Text-to-Speech If you have AI Assistant and the target language is supported, you can generate translated, AI-generated text-to-speech when translating your course. Here’s how: Generate text-to-speech narration with AI Assistant. Translate your course or microlearning to generate text-to-speech narration for supported target languages. If you need to modify the narration, recreate it in the source language. Then, click the language dropdown and select Back to Stack. From the course stack, click Update Translation to generate narrations for the target languages. When you publish your course to Review 360 for validation, validators will be able to see the text-to-speech scripts as they review the whole course. If there are edit suggestions for the script, importing suggestions generates a new text-to-speech audio file with the suggested text. Note: Text-to-speech translation is currently in beta. Functionality may change over time. Based on feedback and feature stability, some options could be modified and others removed. Tips Add Collaborators You can add collaborators to your multi-language course in three ways: Click Share > View collaborators from the course stack or while editing the course to add them via course settings. From your Rise dashboard, hover over the content tile for the course, click the More (...) icon, and select Share to add them via share settings. If the course already has collaborators, a Share Settings option displays instead. Hover over the content tile for the course from your Rise dashboard, click the More (...) icon, and select Move to move the course to a team folder. Everyone who has collaborator access to the team folder you choose will have the same access to the course. You can add anyone with an Articulate 360 Teams subscription, but they must be on a subscription with Articulate Localization to access course stacks. Note that course managers and editors can view and edit multi-language courses. However, only course managers can manage languages. Course managers can also initiate course translations or add new languages if they have translation access within the same subscription. Collaborators without access to Articulate Localization can’t access the course stacks, but course managers can save separate copies of each language to their account when they try to launch the course stack. Understand Question Banks Questions drawn from question banks are translated together with the course. When publishing to Review 360 for validation, we recommend including all the questions from the question bank so validators can review them. Learn more about using question banks in knowledge checks and quizzes. Include Right-to-Left Languages Rise 360 supports multi-language courses with both left-to-right and right-to-left language versions. In edit mode, right-to-left language versions are in a left-to-right layout, but they will automatically adjust to right-to-left layouts when the course is previewed, reviewed, or published. Translate Storyline Blocks for Use in Rise 360 Courses Storyline blocks must be translated and validated through Storyline 360 before the translated versions can be embedded in Rise 360 content. Here’s one approach we suggest: Finalize your Rise 360 course and Storyline blocks in your source language. Translate, validate, and import suggestions for the Rise 360 course in Rise 360. Translate, validate, and import suggestions for the Storyline blocks in Storyline 360. After completing the Localization workflow in Storyline 360, publish the final version of the multi-language Storyline course to Review 360. Embed each Storyline language version to the corresponding language in the Rise 360 course. Follow these steps: Launch the Rise 360 course and click Edit Course. Click the language dropdown on the top left and select one of the target languages. Navigate to the Storyline block and click the pencil icon to edit. When the sidebar opens, click Change and select the Storyline course for this language. Each language version will have the title suffixed with the language code, such as “Onboarding Course - FR” or “Onboarding Course - DE.” If you use a single Storyline file for multiple Storyline blocks, you can publish the whole project to Review 360 for validation. Consider these options to ensure your validators are aware of the different slides/scenes: Instruct them to use the course overview navigation dropdown in the Translation tab in Review 360. (Note: The Translation tab isn’t available in the source language.) Enable the Storyline 360 player menu during the validation process. After validation, hide the player menu and republish the final version for embedding these scenes/slides as Storyline blocks. To publish slides or scenes as separate Review 360 items, save each language as a separate file—including the source language—to turn them into single-language project files. The Review 360 items can then be inserted as separate Storyline blocks. However, localization features like course updates, language validation, and multi-language workflow management won't be available for these copies.Rise 360: Manage Integrated Comments
Once you've published your content to Review 360, you can reply to and resolve comments right in Rise 360. You can even add suggested images directly from comments! Here's how it works. View Comments Add Images from Comments Post Comments Resolve and Reopen Comments View Comments Review 360 comments only appear in content you've published to Review 360. Click the comment icon in the upper right corner to expand the Comments panel. All comments for the currently selected item appear in the panel. For courses, click the lesson title above the comment to jump to that lesson. Each comment includes a screenshot of how the content looked when the stakeholder added feedback, providing context for your edits. Click the screenshot to maximize the image. Linked Review 360 Items If you post multiple Review 360 items for a course, you can see comments and address stakeholder feedback for each from the same interface. Once you upload a new version to Review 360, the Comments panel displays a drop-down menu where you can easily switch between items. Add Images From Comments You can quickly add images attached to comments to your lessons. Navigate to the lesson that contains the comment with an image, hover over the image, click the magnifying glass icon that displays, and click the arrow icon that displays next to the enlarged version of the image. This adds an image block to the bottom of the that lesson. You can also download or delete the image from the comment. Post Comments Continue collaborating with stakeholders without leaving Rise 360 by adding a new comment or replying to an existing one, then clicking Post. If you change your mind, click Cancel. Your comments automatically sync with the discussion in Review 360. Hover over your posted comments for edit and delete options. Keep in mind that comments are organized by lesson and sorted by when they were originally posted, with the newest comments for each lesson at the top of the list. Note: Unlike with Review 360, screenshots aren't automatically created when you start a comment thread in Rise 360. Resolve and Reopen Comments As comments are addressed, resolve them to keep the comments panel from getting cluttered. Hover over an individual comment or the first comment in a discussion thread, then click the checkmark icon that appears. You can also reopen a comment or discussion that was previously resolved. Select the Show resolved option, then hover over the comment and click the green Reopen checkmark icon.Articulate Localization: Publish Multi-Language Rise 360 Courses
Articulate Localization makes publishing multi-language Rise 360 courses easy. Publish all language versions as a single package for your LMS or web server, and let learners choose which language to view when they launch the course. Or publish each language separately as its own package for LMS export if that’s what your LMS supports. For the best experience, publish your multi-language training to Reach 360 so your learners automatically see content in their preferred language. To start, click Publish on the top right of the course stack or while authoring a multi-language course. Choose from the following output types: Quick Share, Reach 360, LMS, Web, and PDF. Find more details for each type below. Quick Share Use Quick Share to easily distribute multilingual training directly from Rise 360 via a URL. QuickShare includes a per-course dashboard that tracks training views and, when the guestbook function is enabled, collects the names and emails of learners. Here’s more information about publishing courses to Quick Share. Learners select their preferred language from those available when they launch the URL. However, you can choose a default language by navigating to that language version first, then clicking Publish > Quick Share. Reach 360 Publishing to Reach 360 lets learners see the course in their preferred language (if available) and allows them to switch to other languages without disrupting their training progress. You can use the Language dropdown in the publishing options page to choose whether to publish all or a subset of your course languages. Then, select the same settings as you would when publishing Rise 360 content to Reach 360. Click Publish at the bottom to send all language versions directly to your Reach account packaged as a single training, as shown below. Learn more about how multi-language training works in Reach 360. LMS Publishing to LMS gives you the same LMS settings as when publishing Rise 360 content to the LMS. You also get the option to choose which languages to include and whether you’ll have a single package or separate LMS packages for each selected language. Click the Language dropdown to deselect any language you want to exclude. All languages are selected by default. Choose between publishing a single LMS package with all the languages you selected or publishing separate packages for each language. Each option is explained below. The Publish selected languages as a single LMS package option lets you upload one zip file to your LMS. Learners can choose their preferred language when they launch the course, as shown below. The Publish separate LMS packages for each selected language option lets you download one zip file containing several other zip files, one for each language. You’ll need to unzip the main zip file, then upload each language zip file to your LMS. Click Publish at the top right to proceed with your chosen option. Rise 360 reports the language the learner chooses to the LMS when the course is published for AICC, SCORM 1.2, and SCORM 2004. For both single and separate package output, the learner’s language code is reported in the following fields: AICC: cmi.learner_preference.language SCORM 1.2: cmi.student_preference.language SCORM 2004: cmi.learner_preference.language If you need this information, check with your LMS admin to see if your LMS supports these fields. Cmi.student_preference.language, for example, is not a mandatory element in SCORM 1.2, so some LMSs might not support it. xAPI and CMI5 statements include language tags to indicate the source language (the parent element) and the language the learner selected when the data was sent, as shown below. Note: Does your multi-language course have an [Early Access] tag? That means it was created in the early-access version of Articulate Localization and can’t be published as a single package with all the selected languages. Refer to this user guide for help using the early-access version. This article explains more about the new features available in the updated Rise 360 version of Articulate Localization, including how to convert your courses to the newer version. Web-Only The web-only output gives you a single course with all the available languages. Learners can choose their preferred language when they launch the course. Simply unzip the zip file provided and upload the contents to your web server. When the files are uploaded, give learners a link to the index.html file. PDF The PDF output gives you one zip file containing one PDF file for each language available in the multi-language course.
