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 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. 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. 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. 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. If you have AI Assistant and the target language is supported, you can create AI-generated text-to-speech from translated text. Here’s how Include a text version of your narration in the course, either in the block or as an audio transcript. Translate your course or microlearning. Publish your course to Review 360 for validation. Validators will also see the transcripts as they review the whole course. When the validation process is complete, follow these steps to generate text-to-speech for each audio asset in the target language or languages: To use text from the audio transcript: Click the Options (...) icon on the right of the audio player and select Edit transcript. Select the transcript text, press CTRL+C to copy, and then click X or Cancel to exit. Click the Options (...) icon again, then choose Edit audio. Paste the copied text into the script field. Choose your preferred voice from the Voice drop-down menu. Click Generate Speech at the bottom. Click Insert to add the audio to your course. To use text from the block: Click the Options (...) icon, then choose Edit audio. Click the insert block text link above the script field to add the block’s text. Choose your preferred voice from the Voice drop-down menu. Click Generate Speech at the bottom. Click Insert to add the audio to your course. For language-specific media assets, upload them directly to the target language to avoid affecting other languages. Learn more about adding 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.Storyline 360: Adding Result Slides
Result slides give learners dynamic feedback at the end of quizzes and surveys. They also send reporting and tracking information to learning management systems, including learners' responses and scores. You can use multiple result slides in a Storyline 360 course and even combine them for a composite score. In this tutorial, we'll look at adding result slides to a project and configuring their properties. Add a Result Slide Choose a Quiz Type Identify the Questions to Be Tracked Enable the Quiz Timer (Optional) Name Your Quiz Define the Passing Score (for Graded Results) Score Only Viewed Questions (Optional) Choose Result Slide Features Format Result Slide Buttons Step 1: Add a Result Slide First, do any of the following: Go to the Home tab on the ribbon, click New Slide, and choose Results. Go to the Slides tab on the ribbon and click Results. In Story View, right-click anywhere in the workspace, scroll to New Slide, and choose Results. In Slide View or Form View, right-click anywhere in the Scenes panel, scroll to New Slide, and choose Results. When the Insert Slide window appears, choose the type of result slide you want to add. Use the filters on the left side of the window to narrow your choices. There are four result-slide types: Graded: Choose a graded result slide when you want to track the score for the quiz. You'll have options to show the learner's score, the passing score, and passed/failed feedback. Survey: Choose a survey result slide for non-graded questions. Blank: Choose a blank result slide when you need to send completion data to an LMS/LRS but want to design the slide from scratch. For example, you might want to disguise it as a summary, thank you, or standard content slide. Combined: Choose a combined result slide when you want to combine multiple quiz results into one final result slide where learners must pass all quizzes to pass the course. Tip: As of June 2022, accessible-by-default templates are available in the gallery of result slide templates in addition to legacy and Content Library 360 templates. Click Insert Slide to add the result slide to your course. The Quiz Settings window appears, as shown below, where you can name your quiz, identify the questions you want to track, define the passing score, enable the quiz timer, and more. Step 2: Choose a Quiz Type Use the drop-down list in the upper left corner of the Quiz Settings window to choose one of these quiz types: Final Assessment: Creates a standard “submit results” trigger on the result slide. This is the default quiz type. A final assessment can be scored and tracked by your LMS/LRS, and it’s automatically added to your LMS/LRS tracking options. Pre-Check: Creates a conditional “submit results” trigger, which depends on the learner passing the quiz. A pre-check quiz can be scored and tracked by your LMS/LRS only if the learner passes. If they fail, the quiz won’t get reported to your LMS/LRS, and the learner has an opportunity to pass another quiz later in the course. Pre-checks are automatically added to your LMS/LRS tracking options. (Even though a failed pre-check doesn’t get reported, the question data still gets submitted to the LMS/LRS. Depending on your LMS/LRS, you might be able to see how a learner responded to a failed pre-check.) Knowledge Check: This quiz type isn’t scored or tracked by your LMS/LRS. Therefore, a “submit results” trigger isn’t created. A knowledge check simply gives the learner an opportunity to test their knowledge and reinforce what they learned. Step 3: Identify the Questions to Be Tracked A result slide can track question slides or other result slides. Use the Calculate results for drop-down list to select one of the following, then mark the boxes for the question slides or result slides you want to track. Questions Use this option to track individual question slides and question draws. Result Slides Use this option to combine other result slides into a final result slide. Then decide how you want to score the combined quizzes, using the scoring options that appear: User must pass each quiz: Require learners to pass each child quiz. If they fail any quiz, then they fail the entire course. Combine points from each quiz: Add the points from all child quizzes together as the final score for the course. Then enter a percentage in the Combined Passing Score field at the bottom of the window. In this scenario, a learner could fail one or more quizzes and still pass the overall course. When combining multiple quizzes into a final result slide, learners will need to visit each of the child result slides in order to complete the course. Otherwise, the course status will be marked incomplete. Step 4: Enable the Quiz Timer (Optional) You can set a time limit for your quiz, using the options in the upper right corner of the Quiz Settings window. Mark the Quiz Timer box, then enter the number of minutes you want to allow for the quiz. Click the stopwatch icon to choose when the timer should start counting down and how you want it to display. (Note: The responsive mobile player always uses the time remaining format.) Learners will see the quiz timer in the upper right corner of the player frame. In the modern player, you can hide the quiz timer by turning off the menus and controls. However, there’s no option to hide the quiz timer in the classic player. Step 5: Name Your Quiz As of August 2022, you can assign unique names to quiz result slides, making it easy to identify the corresponding built-in variables for each quiz. For example, a quiz named Time_Management generates variables such as Time_Management.PassPercent and Time_Management.ScorePoints . Use letters, numbers, and underscores to name your quizzes. Spaces, hyphens, and special characters aren't allowed. Quiz names won't show in your published course. They're only visible in your project file. Step 6: Define the Passing Score (for Graded Quizzes) If you're tracking graded questions, enter a percentage in the Passing Score field at the bottom of the Quiz Settings window. Step 7: Score Only Viewed Questions (Optional) As of September 2020, you can allow learners to skip quiz questions without negatively affecting their score by grading only the questions they view. Simply check the box to Only score viewed questions. For example, you might branch learners to different questions based on their answers to previous questions, which means they could skip some questions along the way. Unviewed Questions vs. Unanswered Questions Unviewed questions and unanswered questions are treated differently. When you score only the questions learners view, they won’t be penalized for questions they don’t see. However, if learners visit questions and then skip them without answering, those questions will count against their quiz score. Step 8: Choose Result Slide Features Finally, choose the features you want to display on your result slide. If the Quiz Settings window is open, click OK to close it, then go to the Result Tools—Design tab on the ribbon. Choose from the following features, and click the slide where you want them to appear. You can add features to the base layer of the result slide or to the success/failure layers. For example, you might add a review button to the base layer so learners can review the quiz whether they pass or fail. And you might add a print button to the success layer so learners who pass the quiz can print their results. You could also add a retry button to the failure layer so they can retake the quiz if they fail. Passing Percent Add a placeholder that displays the percentage required to pass. Format the text box any way you like. User Percent Add a placeholder to your slide that displays the percentage the learner achieved. Format the text box any way you like. Passing Points Add a placeholder that displays the number of points required to pass. Format the text box any way you like. User Points Add a placeholder to your slide that displays the number of points the learner earned. Format the text box any way you like. Review Button Add a Review Quiz button to your result slide, which lets learners go back and review the answers they submitted (but they can't change their answers). To give learners visual feedback on their performance, double-click the Review results trigger in the Triggers panel and mark the box to Show correct/incorrect responses when reviewing. To let learners review only the questions they got wrong, mark the box to Review only incorrect questions. Note: The review button is disabled for combined result slides. Print Button Add a Print Results button to your result slide, which lets learners print out a summary of their results. To include the learner's name on the printed report, double-click the Print results trigger in the Triggers panel and mark the box to Prompt the user for their name. Pro Tip: Learners can choose Save as PDF from the print dialog's Destination drop-down list to make the text searchable. Retry Button Add a Retry Quiz button to your result slide, which gives learners an unlimited number of attempts to retake the quiz. (To limit the number of quiz attempts, review this user guide.) If the quiz drew a subset of questions from a question bank, learners will see a different subset of questions each time they retake the quiz. To let learners retry only the questions they got wrong, double-click the Reset results trigger in the Triggers panel and mark the box to Reset only incorrect questions. Note: The retry button is disabled for combined result slides. Tip: You can adjust the passing score and timer settings on the ribbon or in the Quiz Settings window, as described above Step 9: Format Result Slide Buttons You can format buttons on your result slide to match the rest of your course design. Select a button on your slide, go to the Button Tools—Format tab on the ribbon, and make your design selections. You can add icons, change the button style, adjust the colors, and add effects. To learn more about working with buttons, review this user guide. Can I Edit My Result Slide Later? Absolutely! Open your result slide in Slide View. Then go to the Result Tools—Design tab on the ribbon and click Quiz Settings.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. The author will be able to see any changes that you make, as you make them. A green checkmark icon here means the author has imported 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. 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. Note: Closed captions are included in the validation table, but you might not see them automatically. To show captions: Rise 360: Play the video, click the CC button in the lower right corner, and select the language. Storyline 360: Click the CC button at the bottom of the player. Suggestions for captions are also not automatically reflected in the course preview. 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. 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: 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.Storyline 360: Customizing the Text Labels
Customizing the default text for buttons, messages, screen reader instructions, and other player controls is easy. You can even switch your text labels to a different language all at once. Working with Text Labels Customizing Individual Text Labels Saving Custom Text Labels Switching to Another Language or a Set of Custom Text Labels Saving Player Changes Working with Text Labels To customize your text labels, go to the Home tab on the ribbon and click Player. When the player properties appear, click Text Labels on the ribbon. You can customize individual text labels, change all labels to a different language, or switch to a previously-saved set of text labels you created. Customizing Individual Text Labels On the left side of the window, Storyline 360 displays a list of all the text labels you can edit. For any item you want to change, type your preferred text in the Custom Text column. To see your updated text labels in the preview area on the right side of the window, click Update Preview. If you’d like to send all the text labels to someone else to customize or translate, download this spreadsheet, which contains a complete list. Once you have the revised list, you can update the Custom Text column with the new text labels. Don’t Modify Variable References If you’re using 360° images, only modify the actual text in the Custom Text column. Don’t change variable references, such as %count% and %total% . Saving Custom Text Labels When you customize text labels, the changes become part of the current project. If you want to use the same text labels in other courses, do this: Click the Save button to the right of the Language drop-down. When prompted, enter a name for your new set of text labels and click Save. This saves your text labels in Storyline 360’s default location, but you can choose a different location if you need to share them with other developers. If you select a location other than the default, saved text labels won’t appear in the Language drop-down for other courses you build. In that case, you’ll need to use the Load button (the folder icon to the right of the Language drop-down list) to locate the *.xml file and add it to your language library. Switching to Another Language or a Set of Custom Text Labels To switch to a completely different language or a set of custom text labels you previously saved, use the Language drop-down to make your choice. Custom labels appear at the top of the list, and 75 built-in languages appear below that. Here’s a full list of the built-in language options: Afrikaans Albanian Amharic Arabic Armenian Azerbaijani Bangla Bosnian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French (Canada) French (France) French (Haiti) Georgian German Greek Gujarati Hausa Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Kannada Kazakh Kiswahili Korean Latvian Lithuanian Macedonian Malay Malayalam Maltese Marathi Mongolian Norwegian Pashto Persian Persian (Afghanistan) Polish Portuguese (Brazil) Portuguese (Portugal) Punjabi Romanian Russia Serbian Sinhala Slovak Slovenia Somali Spanish Spanish (Mexico) Swedish Tamil Telugu Thai Turkish Ukrainian Urdu Uzbek Vietnamese Welsh If you saved a custom label set but don’t see it in the list, you’ll need to browse for it. Click the Load button (the folder icon to the right of the Language drop-down list), then select the custom label set you previously saved. Tip: Storyline 360 adds a language code for screen readers to your published story.html file based on the language you select for your text labels. Saving Player Changes When you click OK to close the Player Properties window, Storyline 360 saves your changes in the current project file. If you’d like to use the same customizations in other projects, click Current Player on the ribbon and choose Save. Enter a name for your custom player if prompted, and click OK. Learn more about the Current Player options. You Might Also Want to Explore: Translating ContentArticulate 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.Storyline 360: Hiding the Player Frame for a Chromeless Design
Want to turn off all the player features and hide the player frame to give your course a chromeless look? Storyline 360 can help with that! Here’s how. How to Hide the Modern Player How to Hide the Classic Player How to Hide the Modern Player It’s super easy to hide the modern player frame. Just go to the Home tab on the Storyline ribbon, click Player, then set the Menus & Controls option to Off. That’s it! Your course won’t have a player at all. You'll see a solid background color behind your course. You can change the page background color on the Colors & Effects tab in your player properties. When you turn off the menus and controls, it overrides the previous, next, and submit buttons for each slide in your course. And since your slides won’t have any built-in navigation buttons, be sure to add your own custom navigation features, such as buttons, links, or hotspots. How to Hide the Classic Player The Menus & Controls property described above only applies to the modern player. It’s grayed-out for the classic player. You can still hide the classic player frame. It just takes more work than the modern player. Follow these steps. Step 1: Turn Off the Player Features Go to Home tab on the Storyline ribbon and click Player. Go to the Features tab on the ribbon and uncheck all the player options. Step 2: Make the Player Border Transparent Also in the player properties, click Colors & Effects on the ribbon. Click the link to Show advanced color editing. From the Edit item drop-down list, select the following items and make them 100% transparent. Base >> Main Background Base >> Main Border Base >> Slide Background Step 3: Turn Off the Previous, Next, and Submit Buttons for Each Slide By default, each slide in Storyline will either have previous and next buttons or a submit button. You'll need to turn them off to make your player completely invisible. Go to Story View. Press Ctrl+A twice to select all the slides in your course. Uncheck the Prev, Next, and Submit boxes in the slide properties panel, and make sure all the player features are also unchecked. Be sure to add your own custom navigation features to each slide, such as buttons, links, or hotspots.
