Articulate Localization: Streamline Language Validation With Review 360
Articulate Localization leverages the collaborative workflows in Review 360 to speed up the process of human validation for AI translations. Once you publish your multi-language course to Review 360, you can assign validators to review the AI translation and keep track of their progress. Watch this video to learn about the validation experience for authors and validators using a multi-language Rise 360 course. Then read on for more detailed steps. Publish to Review 360 Request Validation Publish to Review 360 To get started, publish your multi-language project to Review 360. Refer to these user guides for specific details on the publishing process: Rise 360: Publish Content to Review 360 Storyline 360: Publishing a Course to Review 360 As shown below, you can choose to include all project languages or just a subset when you publish after translating with Articulate Localization. When publishing is complete, launch your Review 360 dashboard. The source and target languages are presented as a single "stack" tile. Clicking the tile opens an overview page that lists all the current languages in a sidebar and allows you to preview each language. Note: Multi-language courses can only have one corresponding stack in Review 360. Republishing to Review 360 creates new versions of the languages in the stack. Duplicating content in Rise 360 creates a new course, resulting in a new stack in Review 360 when published. However, Storyline 360 preserves the link between the project file and the Review stack when you create copies of the file—for example, using Save As or sharing the file with other authors. If you need a new stack in Review 360, use Save Translation As to create a copy of the source language, translate or add the languages you need, and then publish. Request Validation To request a language validation, click the Request Review button on the top right for each target language you want validated. Then, follow the standard Request Review workflow. Note that: Language validators do not need to be Articulate 360 seat holders. As with any other Review 360 item, reviewers only need an email address. For a validator, each language in the stack functions like its own Review item. They will not see the stack or be able to access other target languages unless they are also an Articulate 360 seat holder with appropriate permissions. The request review status is displayed on the sidebar and on the top right button for the corresponding target language. The status can be: Request Review: You haven’t assigned any reviewers. In Review: You have assigned reviewers who haven’t completed the review. Review Complete: All assigned reviewers have completed their review. If you share the item in team folders, editors will see the overview page and can assign reviewers for target languages. Here's a comparison of how an author and a validator see a Review 360 item for validation. Validators can suggest text changes and preview those changes in real time. To learn more about the validation experience from the perspective of a validator, check out this guide for language validators. You can also share it with your validators for their reference. Once a validator has finished their review, you can import their suggestions. Instructions for importing validator suggestions can be found in this user guide: Articulate Localization: Import Suggestions from Language ValidatorsArticulate Localization: Import Suggestions from Language Validators
When the validation process is complete, Articulate Localization allows you to look over validator suggestions and make choices about what to import, right from Rise 360 or Storyline 360. Watch the video to see how this works using a multi-language Rise 360 course, and then read on for more details about importing suggestions in each app. Import Suggestions in Rise 360 Import Suggestions in Storyline 360 Review Suggestions in Review 360 Import Suggestions in Rise 360 When you open a translated course stack from your Rise 360 dashboard, badges display for languages with pending updates. You can review or reject these suggestions by clicking Review > View in Review 360 and following these steps to review validation suggestions. Once you’re ready to import the pending suggestions, click the ellipses (...) beside the language and choose Import Suggestions. Note: Course managers and editors with access to Articulate Localization can access course stacks, but only course managers can import validation suggestions. Import Suggestions in Storyline 360 When suggestions are available for import, a blue dot appears on the language menu at the top right. Review or reject these suggestions by hovering your mouse over any language in the File > Localization menu, selecting View in Review 360, and following these steps to review validation suggestions. Once you’re ready, you can choose to import suggestions for all languages at once or for one language at a time. To import suggestions for all languages, click the language menu and choose Import All Suggestions or navigate to File > Localization > Language Validation and select Import All Suggestions. To import suggestions for just one language, go to File > Localization, hover the mouse over the language you want to import, and choose Import Suggestions. Review Suggestions in Review 360 Review 360 lets you filter the translation table so you can easily see the segments with validator suggestions. From there, you can decide whether to import the suggestions to Rise 360 or Storyline 360 or reject them using the Reset option. Follow these steps: Launch the Review 360 stack for your course or project. Click the filter icon from the toolbar above the validation tables and select Unimported edits only to see all the segments with suggestions that haven’t been imported into your course. If you find a suggestion that you don’t want to import, click the corresponding segment in the target language column, click the reset icon that appears at the bottom right, and choose Reset. Repeat step 3 for the other segments you want to reject. Suggestions that remain are ready to be imported. When you’re done reviewing all the suggestions, import them to Rise 360 or Storyline 360 as described above.Articulate Localization: Get Started with Language Validation in Review 360
Articulate Localization language validation results in higher-quality translations with fewer rounds of feedback, streamlining and speeding up the localization process for Rise 360 and Storyline 360 courses. Validators use Review 360 to review AI translations in the context of the course, and they can preview their changes in real time. Course authors send a link to access the translated course via email and ask a validator to review it. Validators can suggest changes to any of the text in a course, see a preview of their changes as they’re made, mark lessons or slides as validated to avoid duplicating work, and indicate to the course author when validation is complete. Watch the video for a quick demo of the process. Validators can follow the steps below to get started. Course authors may also want to read on to learn how the process works for validators. Signing In Validating Courses and Tracking Progress Adding Comments Completing Your Validation Tool Tips Search Function and Find and Replace Tool Translation Table Filter Advanced Tag Format Editing Signing In Once you receive a validation request email from a course author, use your email address to sign in. You need to provide at least an email address to comment or suggest changes to the translations. Depending on the permissions set on the course, you may also need to sign up for a free Articulate ID using your email address before you can validate. Validating Courses and Tracking Progress When you open a translated course in Review 360, you'll see a Translation tab in the comments sidebar. This tab contains the validation table with all the text in the course in both the source and target language. The numbered areas in the image below are the different features you’ll use in validating. Refer to the table that follows to learn more about each feature. # Feature Description 1 Course Preview See the translation as it appears in the course. 2 Course Overview Navigation Dropdown Jump to a specific course or access an overview of the validation progress. 3 Validation Progress Overview See which lessons or slides have been validated and which still need to be reviewed. 4 Progress Tracking Mark a lesson or slide as validated to avoid duplicating work. 5 Quick Navigation Navigate quickly between lessons or slides. 6 Adjusted Styling for Legibility Text segments with low visibility on a standard white background, such as white or other very light fonts, are displayed with background fill in the validation table to improve legibility. 7 Search Function and Find and Replace Tool Find words in the source or target language or replace words in the target language. Learn more about the search feature. 8 Translation Table Filter Filter the translation table for edited text segments in the target language. Learn more about filtering. 9 Advanced Tag Format Editing Use tags to adjust existing text formatting. Learn more about tag format editing. Ready to start validating? You can navigate the course translation in one of three ways: Use the course preview on the left. Click the course navigation dropdown above the validation table and jump to a specific lesson or slide. Select the previous or next arrow below the table on the right. When you’re ready to make a suggestion, follow these steps: Click the text segment you want to change in the target language column on the right. The course preview on the left will scroll to the relevant part of the course. Edit the target language text with the preferred translation. The course preview automatically reflects how the course will look after your suggestions have been applied. Click outside of the segment to save your suggestion. A blue pencil icon appears on the right to indicate the suggestion was saved. A green checkmark icon here means the author has accepted your suggestion. (You can hover the mouse over the icon to see who made the last update and when.) To restore the original AI translation, click the edited segment. Then click the reset icon at the bottom right and choose Reset from the prompt that appears. The author will be able to see any changes that you make, as you make them. When you finish validating a lesson or slide, click the Mark [lesson/slide] Validated button to track your work and avoid conflicts when collaborating with others. Click the course navigation dropdown above the validation table to get an overview of the course structure and the validation status of each lesson or slide. Adding Comments If you have feedback on the course that does not relate directly to specific text or want to add context to your suggestions, you can use the Comment tab to share more general feedback. Comments are attached to the slide in Storyline 360 projects or lessons in Rise 360 content. Learn more about using Review 360. Completing Your Validation Once you finish making suggestions, email the course author or post a comment and tag them so they know you've completed your review. If you're an assigned reviewer, you can expand the Review Assigned To You drop-down and click Finish Review. This doesn't prevent further edits—it simply signals to others that you have completed your validation. Note: Once validation is complete, the author will need to open the course in Storyline 360 or Rise 360 and import the suggestions into the course. Course authors can consult this user guide for the next steps: Import Suggestions from Language Validators. Tool Tips Search Function and Find and Replace Tool Quickly find specific words throughout the course in either the source language, the target language, or both. Here’s how: Click the magnifying glass icon from the toolbar above the validation table. From the Search tab, type in the keyword you want to find in the Search field and press Enter. If you want to filter the results by source or target language, click the Source and target dropdown above the search field to choose Target or Source. By default, results are filtered by the current lesson/slide. To remove the filter, use the Current Lesson/Slide dropdown and select All Lessons/Slides. Use the Find and Replace tab to locate and change all instances of a specific term in the target language. Follow these steps: Click the magnifying glass icon from the toolbar above the validation table. Click the Find and Replace button, type in the word you want to change in the Find in target field, and press Enter. Results are filtered by the current lesson/slide by default. You can use the Current Lesson/Slide dropdown and select All Lessons/Slides to remove the filter. Type the new term in the Replace with field. Choose from these two options: Replace all: Click this button to update all instances of the word currently displayed, for example, in the current lesson/slide or in all lessons/slides. Replace: Click this button to update the currently selected instance of the word. Translation Table Filter Filter the rows of the translation table based on the status of the target language text segment. To use, click the filter icon from the toolbar above the validation table and choose one of the following: Filter by Description Imported edits only Shows all the rows with edited text segments that were accepted by the author. These rows have a green checkmark on the right. Unimported edits only Shows all the rows with edited text segments that the author hasn’t accepted yet. These rows have a blue pencil icon on the right. All edits Shows all the rows with edited text segments. This filter combines both options above. A blue dot appears on the filter icon to let you know when a filter is currently in use. Advanced Tag Format Editing (Experimental) Formatted text—text that is bolded, italicized, or in a different size or color—shows up differently in the validation table for Rise 360 and Storyline 360 users. In Rise 360, the formatted text and plain text appear in one segment, with the formatting visible, as shown in the image below. In Storyline 360, formatted text is indicated by a separation from plain text, which divides the segment into multiple fields or spans. The formatting itself is not visible, as the image below illustrates. You can use advanced tag format editing to easily see formatted text and adjust which text gets formatted. Follow these steps to make an adjustment: Click the <>Off icon from the toolbar above the validation table to switch tag format editing on. Select the text segment you want to change in the target language column. When enabled, the text in the segment is standardized. The formatted text turns purple and is enclosed with square brackets [...] called “tags.” (Click the images below to see examples in Rise and Storyline.) Click and drag the square brackets to add or remove texts in these tags. Click the <>On icon to disable tag format editing.Articulate Localization: Create Multi-Language Rise 360 Courses
With Articulate Localization, you can translate course and microlearning content into 70+ 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 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 boxes, 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. 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. 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. 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 done to the source won’t be applied moving forward. 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 project has already been validated, follow the tips in this article to request validation for only the updated content. 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. 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. 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. Localizing Video and Audio Assets Localize video assets automatically by adding closed captions before translation. Captions translate along with other course text when you add new languages. For audio blocks: Use text blocks or accordion interactions to display transcripts, which will also translate automatically. For existing translated assets: Upload them directly to the target language without affecting other languages. Learn how to add closed captions and create language-specific media. 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.” 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.Articulate Localization: Publish Multi-Language Storyline Projects
With Articulate Localization, you can effortlessly publish multiple language versions of a project in Storyline 360. For a fully integrated experience, publish your multi-language training to Reach 360 so learners automatically see content in their preferred language. If you’re publishing for LMS or web, you can choose between publishing a single package that contains selected language versions or separate packages per language version. How to Publish Follow the steps to publish a regular Storyline project, but note the following additional options when using Articulate Localization: Use the Language dropdown to choose whether to publish all or a subset of your course languages. Click the globe icon beside the Title to edit titles for other languages. Reach 360 If you’re publishing to Reach 360, all language versions are sent directly to your Reach account and packaged as a single training after you click Publish. Learn more about how multi-language training works in Reach 360. LMS and Web For LMS or web output, choose one of the following package types, then click Publish: Single package containing selected languages Separate packages per language Single Package Option The “Single package containing selected languages” option lets you upload one zip file to your LMS or one set of published files to your web server. When learners launch the course, they can choose their preferred language, as shown below. Separate Packages Option The “Separate packages per language” option creates a subfolder for each published language inside a main folder named after the project. You’ll need to upload or zip the content of each subfolder to your LMS or web server. Note for LMS output: Storyline 360 reports the language the learner chooses to the LMS. 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 xAPI and cmi5: context.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. Video and Word If you’re publishing a video file or to Microsoft Word, Storyline creates one file for each selected language.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: Reach 360, LMS, Web, and PDF. Find more details for each type below. Reach 360 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. We're working on enabling this capability for xAPI and CMI5, and we’ll update this guide when it’s available. 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.Articulate Localization: Overview
Develop high-quality localized courses seamlessly with Articulate Localization, a localization solution integrated right into Articulate’s unparalleled authoring platform. This overview covers the basics of Articulate Localization and explains how to access it. What Articulate Localization Does What Languages Are Available What Gets Translated How to Access Localization What Articulate Localization Does Articulate Localization helps you upskill your global learners more quickly and efficiently with three primary processes: One-Click AI Translation Instantly translate Rise 360 and Storyline 360 courses into 70+ languages with fully integrated AI translation. Upload custom glossaries to maintain consistency and incorporate specialized terminology. In-Context Language Validation Verify the accuracy of localized content with a new language validation experience in Review 360. Validators can preview their changes in context, and authors can import them directly back into the source project. Multi-language Workflow Management Streamline end-to-end localization for your Rise 360 and Storyline 360 courses. Manage all your languages in a single project, keep track of the validation process in Review 360, and publish all languages at once to Reach 360 or your LMS. What Languages Are Available Translate your content into over 70 languages, including certain regional variations such as Canadian French and Brazilian Portuguese. Afrikaans Farsi (Persian) Kannada Russian Albanian Filipino, Tagalog Kazakh Serbian Amharic Finnish Korean (Standard South Korean) Sinhala Arabic (Modern Standard Arabic) French Latvian Slovak Armenian French (Canada) Lithuanian Slovenian Azerbaijani Georgian Macedonian Somali Bengali German Malay Spanish Bosnian Greek Malayalam Spanish (Mexico) Bulgarian Gujarati Maltese Swahili Catalan Haitian Creole Marathi Swedish Chinese (Simplified) Hausa Mongolian Tamil Chinese (Traditional) Hebrew Norwegian Telugu Croatian Hindi Norwegian (Bokmål) Thai Czech Hungarian Pashto Turkish Danish Icelandic Polish Ukrainian Dari Indonesian Portuguese (Brazil) Urdu Dutch Irish Portuguese (Portugal) Uzbek English Italian Punjabi Vietnamese Estonian Japanese Romanian Welsh Note: Many languages available for one-click translation also offer different degrees of formality. Articulate Localization defaults to Automatic, which determines the best formality level based on your content. However, you can adjust the formality of the translation based on your organization’s communication style. Tool Tip: Use our language lookup tool to see which target languages are supported for your source language and if the language pair supports glossary, formality, and right-to-left. Here’s how to use it: Launch the language lookup tool in a separate browser window. Select your source language from the Select a Source Language dropdown. A table displays all the supported target languages for the chosen source language with columns for glossary, formality, and right-to-left. A green checkmark in these columns means the corresponding target language supports it. What Gets Translated The following chart explains which parts of courses are translated and how: Part Behavior On-slide text, including slide notes and text variable values (Storyline 360 only) Automatically translated Block text (Rise 360 only) Automatically translated Closed captions (video, audio) Automatically translated Text labels in Rise 360 and player text labels in Storyline 360 Default text labels for each target language are automatically assigned. Custom text labels are not translated. However, in Rise 360, you can assign custom label sets to individual language versions after translation. Alternative text Automatically translated for customized alternative text but not default alt text generated by the app Question banks Questions drawn from question banks are translated together with the course. How to Access Localization Articulate 360 owners and account admins can start a free trial by clicking the Start a Trial button under the Localization section of the Manage Subscription page. To purchase directly, contact our sales team. During a trial, all seatholders are automatically given the ability to translate content in Rise 360 and Storyline 360 and start the localization workflow. Account owners and account admins can remove an author’s translation access via the Localization section on the Manage Team page. Translation access settings are retained when purchasing from a trial. When Localization is purchased directly without a trial, seatholders aren’t given the ability to translate by default. An account admin must navigate to the Manage Team page to grant translation access to specific seatholders. Those seatholders must start any localization workflows. Once Articulate Localization is enabled, seatholders with translation access immediately see the Translate option when they click the more (...) icon of any content tile in the Rise 360 dashboard. If it’s not showing right away, simply refresh the page. For Storyline 360, seatholders with translation access see a Translate Course option when they navigate to File > Localization. They must use Storyline version 3.94.33593.0 or later. Here’s how to check the Storyline 360 version and how to update to the latest version of the app.Articulate Localization: Distribute Multi-Language Training With Reach 360
Accommodating global audiences in Reach 360 is easy when you use Articulate Localization! Simply publish your multi-language training to Reach 360, then enroll learners. That's it! Learners see the course in their preferred language (if available) and can select other languages without disrupting their training progress. To get started, add a published multi-language Rise 360 or Storyline 360 training to your training library as you would any other course. The available languages display on the course detail page, as shown below. The learner automatically sees the translated course based on their preferred language interface, if available. For example, here’s the learner interface in German: Current languages include: Brazilian Portuguese English (UK) Mexican Spanish Canadian French Finnish Norwegian Danish French Portuguese Dutch German Spanish English (US) Latin American Spanish Swedish Learners don't have to remain in the same language while taking training. They can select a different language from the drop-down menu at the top of the screen without resetting their current progress. Reach 360 seamlessly tracks learner progress across languages as it would a single training session. Question-level reporting also supports multiple languages. Even if a learner switches between languages for each question, all responses are included in the report. Admins, managers, and reporters can use the drop-down menu at the top of a learner's report to see all the languages in which answers were recorded.
