translation
30 TopicsRise 360: Translate Your Content
There are almost as many ways to say “Hello” as there are ways to make Rise 360 content. That’s why we make it easy to export your content to an XLIFF file for localization into left-to-right languages and scripts with double-byte character sets. Step 1: Duplicate Your Content The first step is to duplicate the content you want to translate. The duplicate you create will become the translated version. Translating into more than one language? You can make a copy for each one or try out the alternate method below. Step 2: Export the Content as an XLIFF File Open the duplicate content you created in the previous step. Click Settings in the upper right corner and go to the Translations tab. If you don’t need to preserve formatting you’ve applied to your text, deselect Include HTML formatting. This exports your content in easy to translate blocks of text. However, it doesn’t contain the coding necessary to maintain any formatting you’ve applied to that content. To change the source language for your course enter the language code in the field. As you type, a list of available language codes appears. The default is U.S. English (en-us). Click Export XLIFF File and save the file to your computer. Then use a web app, computer program, or professional translation service to edit your XLIFF file. If Include HTML formatting is selected above, you'll see additional HTML tags and extra spaces in your XLIFF file. Don't panic! These are there to preserve your formatting when you import your translated file in Step 3. Tip: Rise 360 uses XLIFF version 1.2. Step 3: Import Translated Text Got your newly-translated file? Great! Open your duplicate content again. Click Settings in the upper right corner, go to the Translations tab, and click Import Translated Text. Select your translated XLIFF file and click Open. A message displays when your text is successfully imported. Why am I seeing an error? If you see an error message that says the “Translation file doesn’t match this course,” make sure you’re in the content from which you originally exported your XLIFF file. The XLIFF file is content-specific, so it can't be exported from one deliverable and imported into another. If you see a different error, the XLIFF file may be incomplete or corrupt. Download a fresh copy of the file and try again. If downloading a fresh copy doesn't work, make sure there aren't any blank section or lesson titles in your course. All section and lesson titles have to have content. Where did my formatting go? If you deselected Include HTML formatting in step 2, any formatting you applied to your content prior to importing the translated file is not retained. And let us know if you have any questions. We’re happy to help! Step 4: Translate Your Labels Don’t forget to translate your buttons and other built-in navigational elements. Click Settings in the upper right corner and go to the Labels tab. For more information on how to translate labels, click here. Translate Training into Multiple Languages Need to translate your training into more than one language? One method is to make multiple copies of the course, then translate those copies. But we like this alternate method since you don't have to keep track of which XLIFF file goes with which training copy. Export your XLIFF file as described in Step 2 above and then duplicate the training so you have a copy in the original language. Translate your XLIFF file into all the languages you need. Import one of the translated XLIFF files to the original training. Duplicate your translated training to have a separate copy. Repeat steps 3 and 4 for all additional translations. Voila! We find it's quicker and easier to just "overwrite" your original file and make copies. We think you will too!11KViews4likes0CommentsStoryline 360: Translating Courses
Do you need a course in multiple languages? Storyline 360’s translation features can help with that. Export the Original Text Translate the Exported Text Import the Translated Text Localize the Storyline Player Step 1: Export the Original Text First, export a copy of the text from your Storyline 360 project. Go to the File tab on the Storyline ribbon, scroll to Translation, and select one of these export options: Export to XLIFF XLIFF is a file format commonly used for translation services and computer programs. Give your file a name and click the ellipsis to select the location where you want to save it. Choose the Source Language that you used to create the course. Choose the XLIFF Version required for your translation service or program, either 1.2 or 2.0. Click OK to complete the export process. Export to Word Word documents are great for machine translation—and they’re even better for human translation. Exporting to Word (DOCX) provides an easily readable list of text for translating text manually. Give your file a name and click the ellipsis to select the location where you want to save it. If you’d like, choose one of the following options: Include slide thumbnails for reference to add screenshots of each slide and layer to the supporting text for visual context. Export as a single table to create a single table of the entire course for computer-aided translation. Click OK to complete the export process. Note: By default, the February 2021 update and later for Storyline 360 use enhanced Word translation. If you prefer the legacy translation workflow, view this guide on how to switch back. Step 2: Translate the Exported Text After exporting the text from your course, use the resulting Word document or XLIFF file to translate it into other languages. You can use professional translators, an online translation service, or a computer program. When translating content, keep these important items in mind: As of June 2021, you can apply basic font formatting (e.g., bold, italics, underline, strikethrough, superscript, subscript) to translated text in the Word document, and Storyline 360 will import the changes back into your project file. Visit this article to learn more. If you’re using the Export to Word option, only modify text in the column titled Translation in the resulting Word document. Leave all other text unchanged. Don’t translate result slide variable references. Closed captions can’t be translated using this process. They’ll need to be translated separately and imported back into Storyline 360. Trigger conditions and player text labels can’t be translated using this process. They’ll need to be translated manually in Storyline 360. Variable names can’t be translated using this process. (Variable values can be translated, just not their names.) As a result, you shouldn’t translate variable references in the exported file unless you also plan to translate the variable names manually in Storyline. Otherwise, translated variable references won’t match their corresponding variable names. Step 3: Import the Translated Text When the translation is ready, import the Word document or XLIFF file back into Storyline 360: Create a copy of your original project file to contain the new language and open it in Storyline 360. Go to the File tab on the Storyline ribbon, scroll to Translation, and select Import. Browse to the Word document or XLIFF file that contains the translated text and click Open. When you see the congratulations message, click OK. Review the imported text to be sure it fits properly in your course and make adjustments as necessary. Some languages use longer words and phrases, so you may need to allow more room for the expanded text or reduce the font size. Step 4: Localize the Storyline Player While the translation feature in Storyline 360 lets you modify the slide content, you may also want to customize the player’s text labels. Text labels let you localize buttons, messages, and other player elements for different languages.7.9KViews0likes0CommentsHow to Create One Storyline 360 Course with Multiple Languages
One of the most powerful benefits of e-learning is the ability to reach learners wherever they are—anywhere in the world. But that perk also presents an additional question: How do you create and manage e-learning content when your audience speaks different languages? Many organizations tackle this challenge by building multiple courses—one for each language they support. While that approach works, it often increases production time and costs. And it can lead to frustrating reporting headaches if you’re tracking completions. Instead, why not streamline development by creating one course for everyone? Thanks to the power of layers, variables, states, and triggers, you can quickly fulfill this linguistic feat of e-learning awesomeness all within a single Storyline 360 course! Not only that, Storyline 360 offers multiple ways to make this work. So let’s take a closer look at three of the most popular methods you can try. The Branching Method Many folks use the branching method to create different scenes in their projects, one for each language. When the course begins, learners choose from one of several language options. That choice then prompts a “jump to scene” trigger that directs them to the appropriate scene. Watch this short video to see how this method works. Pros: Branching is probably the simplest way to provide learners with language-specific content. This method also allows you to use layers and states to create a more interactive experience. Storyline 360 can now track multiple quizzes, so you can create an assessment for each language branch. No matter which one a learner takes, the course will send its completion data and results to your LMS. Cons: This approach may significantly increase your project’s file size if your course has a lot of audio, video, or animations. Branching is also useful for creating interactive stories, scenarios, and content. But using it for both content choices and supporting multiple languages can make development complex. In those situations, the two techniques below are often a better fit. The Layers Method When branching isn’t the best option, you can instead add layers on your course slides—one for each language you support. Similar to the previous process, learners select their preferred language at the start. But instead of branching to a different scene, this approach uses true/false variables and a few simple timeline triggers to show the appropriate layer throughout the course. Watch this short video to see how this method works. Pros: All your content is streamlined across one set of slides. You can use custom states to keep things from feeling too static. Cons: Typically, layers are used to add interactivity to your course. But this gets complicated when you also have multiple layers on each slide for different languages. Because of that, this method works best when you can create the course interactivity you need without additional layers. The States and Triggers Method The states and triggers technique is similar to the previous one, but it uses object states instead of layers to display content in each language. It begins much like the others—with learners choosing their preferred language on the title slide. Thanks to true/false variables and triggers, each slide in the course then automatically shows the correct object states. This one’s a bit easier to see than to explain, so here’s a video demonstrating how it works. Pros: Much like the layers approach, with states all your content is streamlined across one set of slides. This technique leaves your layers free, making it easier to create interactive content. Once you’ve built an object with all the correct states and triggers, it’s quick and easy to copy and paste and carry over the triggers. Cons: Adding translated text to object states can be a bit tedious. Changing object states means using more triggers as well—more than the other two methods. This approach tends to get in the way of using object states for other interactivity functions, such as adding a hover effect to your translated buttons. Additional Considerations Regardless of which method you choose, here are a few more things to keep in mind when creating a single Storyline 360 course with multiple languages: Course Player Labels: You can only choose one language for the course player text labels (the menu, the resources tab, the navigation buttons, etc.), which can be a challenge if some of your learners don’t understand that language. In those cases, try these workarounds: Create a navigation primer in your course for each language. Check out this article to see some examples and learn more. Skip the built-in course player menu altogether. Instead, build a custom menu on your slides with navigation buttons for each language your course supports. Check out this free download for some custom menu design inspiration. If you’re comfortable working with Javascript, this forum thread offers codes you can use to change the course player button labels on a slide-by-slide basis. Text Expansion: Content in one language may take up more or less layout space when translated to another. For instance, German copy can take up as much as 35% more space than the same information in English. So when planning your layout, base it around the lengthiest language to ensure each translation will fit. Production Schedule: Even with the help of these time-saving approaches, a multi-language course will always take more effort to create than a monolingual one. So make sure your timeline takes the additional steps into account. For example, consider the time it takes to get translations, hire voice talent for each language, and have fluent speakers review your translated storyboards and scripts. When Separate Files Are More Efficient: The methods in this article work best if you plan to include up to three languages in a single course. If you need to support more than three languages, separate project files may be the more efficient option. Summary Thanks to the flexibility of Storyline 360, you’ve got several options for creating content in multiple languages—each with its own strengths and drawbacks. So before you start building your course, consider which one is the best fit for you and your learners’ needs. Want to learn more about translating and localizing content? Browse through these articles for even more tips: Planning Your Localized E-Learning Projects Top 10 Writing Tips for E-Learning Localization The Hidden Project within Your Project: Translating Your E-Learning Materials Storyline 360: Translating Courses 4 Tips for Optimizing the Translation of Your Storyline 360 Courses Rise 360: Translate Your Course What’s your preferred method for working with multiple languages? Any tips or tricks you’d like to share with others? Leave them in a comment below. Want to try something you learned here but don’t have Articulate 360? Start a free 30-day trial, and come back to E-Learning Heroes regularly for more helpful advice on everything related to e-learning. If you have any questions, please share them in the comments.1.2KViews0likes15CommentsStoryline 360: Enabling Right-to-Left Language Support
You can enable right-to-left language support for player features when you're using a right-to-left language, such as Hebrew or Arabic. Here's how. Enabling Right-to-Left Orientation for Player Elements Enabling Right-to-Left Orientation for Slide Content Moving the Sidebar to the Right Side of Your Course Saving Player Changes Enabling Right-to-Left Orientation for Player Elements Here’s how to change the text direction for player elements, such as navigation buttons, sidebar tabs, and pop-up messages. First, make sure you're using a player font that supports right-to-left text, such as Arial Unicode MS or Microsoft Sans Serif. Next, select a language for your player text labels (such as Arabic or Hebrew) or customize your text labels in another language (such as Farsi or Urdu). Then, follow these steps: Go to the Home tab on the Storyline ribbon and click Player. When the player properties appear, click Other on the ribbon. Use the Text is read from drop-down list to select Right to Left. Click OK. Player elements switch positions for right-to-left languages to give learners a more intuitive experience. Enabling Right-to-Left Orientation on Slide Content To display your slide content in a right-to-left orientation, make sure the Right-to-Left Text Direction button is selected when you enter or edit text. You'll find the right-to-left button on the Home tab of the Storyline ribbon, but it'll only show if you have a right-to-left keyboard input language installed on your computer. Moving the Sidebar to the Right Side of Your Course If your player includes a sidebar, you might also want to move it to the right side of your course. To make this change, click Features on the player properties ribbon and select On Right from the Sidebar drop-down list. Saving Player Changes When you click OK to close the Player Properties window, Storyline 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. To learn more about the Current Player options, see this user guide. You Might Also Want to Explore: Interactive Demo: Which classic player features are supported on tablets and smartphones?498Views0likes0CommentsStoryline 3: Translating Courses
Do you need a course in multiple languages? Storyline 3's translation features can help with that. Here's how. Export the Original Text Translate the Exported Text Import the Translated Text Localize the Storyline Player Step 1: Export the Original Text First, export a copy of the text from your Storyline project. Go to the File tab on the Storyline ribbon, scroll to Translation, and select one of these export options: Export to XLIFF XLIFF is a file format commonly used for translation services and computer programs. Give your file a name and click the ellipsis to select the location where you want to save it. Choose the Source Language that you used to create the course. Choose the XLIFF Version required for your translation service or program, either 1.2 or 2.0. Click OK to complete the export process. Export to Word Use Word if you're translating text manually. It's easier to read than XLIFF (which is formatted for computer programs). Give your file a name and click the ellipsis to select the location where you want to save it. Mark the box to Include "Original Text" column for reference if you want to always see the text in its original language as you translate it. Click OK to complete the export process. Tip: Use XLIFF for Lists and Custom Paragraph Spacing We recommend using XLIFF to translate your course when it has bulleted lists, numbered lists, or custom paragraph spacing. Word can break formatting and spacing for these features. Step 2: Translate the Exported Text After exporting the text from your course, use the resulting Word document or XLIFF file to translate it into other languages. You can use professional translators, an online translation service, or a computer program. Here are some important things to remember when translating content: Only modify text in the column titled Translate this column. Leave all other text unchanged. Don’t translate result slide variable references, such %Results.ScorePoints%. If you change the text formatting in any way (font, size, color, style, alignment, etc.), those changes will also be reflected in your course when you import the file back into Storyline. Closed captions can't be translated using this process. They'll need to be translated separately and imported back into Storyline. Trigger conditions can’t be translated using this process. They’ll need to be translated manually in Storyline. Variable names can’t be translated using this process. (Variable values can be translated, just not their names.) As a result, you shouldn’t translate variable references in the exported file unless you also plan to translate the variable names manually in Storyline. Otherwise, translated variable references won’t match their corresponding variable names. Step 3: Import the Translated Text When the translation is ready, import the Word document or XLIFF file back into Storyline: Create a copy of your original project file to contain the new language and open it in Storyline. Go to the File tab on the Storyline ribbon, scroll to Translation, and select Import. Browse to the Word document or XLIFF file that contains the translated text and click Open. When you see the congratulations message, click OK. Review the imported text to be sure it fits properly in your course and make adjustments as necessary. Some languages use longer words and phrases, so you may need to allow more room for the expanded text or reduce the font size. Step 4: Localize the Storyline Player While the translation feature in Storyline lets you modify the slide content, you may also want to customize the player's text labels. Text labels let you localize buttons, messages, and other player elements for different languages.299Views0likes0CommentsPlanning Your Localized E-Learning Projects
In this age of globalization and multinational organizations, companies want to deliver online training that will reach worldwide audiences. The result is e-learning content that needs to be tailored specifically for each cultural group. If you’ve ever had to design or develop a multilingual e-learning course, you know firsthand that developing content for multiple languages can be a heavy lift. This is especially true if you haven’t put in place early the proper planning measures to make the process smooth and effective. This article will identify what you need to know up front (long before any development begins!) to effectively localize or tailor e-learning content for a variety of cultural audiences. Understand the concept of localization When it comes to getting a course out in multiple languages, it’s a common misconception that all you need to do is translate the written content. There’s often confusion about the differences between translation and localization. Translation is the process of translating text and words from one language to another without making any adaptations. Localization is the process of translating and adapting content for a specific culture. It often involves making changes not only to the text but also to imagery, tone, colors, currencies, and more, to account for cultural and regional differences. In many situations, simply translating the text in a course is not enough; you need to adapt the content in order for it to make sense for learners across cultural barriers. For example, let’s say you’re developing an e-learning course for a multinational delivery service. The course is for delivery staff based in the US and India on how to safely deliver packages on time. In addition to translating the text from English to Hindi, you need to adapt the content itself to take into account local driving and workplace safety laws. You should also consider updating the imagery to more accurately reflect the learner's home environment. For example, the American version of the course might show background images of busy streets in New York City. For the Indian version of the course, those could be swapped out with images of the streets of Mumbai. The two cities look very different and each have distinct architectural styles, roadways, and vehicles. Additionally, an image of a delivery vehicle in the American course might show a cube van or bicycle; the Indian version might be a tuk-tuk or a rickshaw. These changes in imagery make the course more meaningful and relevant to the learner. Plan for localization up front The key to a successful localized project is to plan every step of the localization process from the get-go. You want to keep your multicultural audience in mind from the beginning to avoid quality issues, save time, and ensure a smooth localization process. Things to consider when you’re in the project planning phase include: Identify the target markets and languages you want to localize for You need to determine early on which languages you’ll be localizing for. Keep in mind that even though your learners may speak the same language, you may need to create multiple courses to take into account regional differences. For example, a course developed in Spanish might not work for both Mexico and Spain. Why not? In addition to the many linguistic differences between Mexican and Iberic Spanish, there are regional differences that need to be considered, for example: different products, procedures, laws, technical standards, and currencies. Plan to build in one language first It’s a good idea to plan to design, develop, and deliver the course in one language BEFORE localizing the course into other languages. If you develop all of your courses in tandem, you’ll find yourself doing a lot of re-work. To illustrate: imagine a Subject Matter Expert asks you to change two paragraphs in your course. It’s a lot easier (and more cost effective!) to do it in one language than in five different languages. Once the first course is complete, you can save time by localizing your course into the other languages at the same time. Plan extra time for development and testing It might seem obvious, but you’re going to need more development time when you’re building a course in multiple languages. In addition to developing the course in the first language, you’ll need time to adapt it to every other language, which will include development, testing, and review steps. It’s a good idea to plan for the localization process by adding in extra development and testing time to your project plans and timelines. Find the right localization resources Having the right resources in place can make the translation and localization process run more efficiently and smoothly. Resources include the tools and the people you’ll bring on board for your localization process. Authoring tool When you’re going to be translating an e-learning course into multiple languages, it’s a good idea to investigate ahead of time what translation features and multilingual options are available within the authoring tool you’re using. For example, Articulate Storyline 360 offers the ability to export text for translation and then re-import it, saving lots of development time. This is good to know up front, so you can plan your project and allocate time and resources accordingly. Translators The quality and experience of your translation team will have a huge impact on the caliber of the final localized output. When it comes to working with translators, it helps to find translation professionals who have experience with your industry or subject matter. When the translation team has even a basic understanding of the content they are working with, it makes a huge difference in helping them ensure it all makes sense and works. In terms of hiring translators, your options are generally a professional agency or a single contractor or freelancer. They each come with their own set of pros and cons. Professional Agency Pros Cons They will handle all the project management for all the languages. They often offer voice-over professionals for all languages. They sometimes offer to do the translation directly in your tool of choice. The quality is often not as high. Because at a large agency the translators do not know you personally and are not that invested in your project. Also, you work with a variety of translators who may each have a slightly different style, which could be reflected in the final output. Freelancer/Contractor Pros Cons The quality tends to be higher, as usually freelancers need to provide a good service in order to maintain a good reputation, stay in business, and ensure repeated business and future contracts. It’s often cheaper to work directly with a translator because they don’t have high overhead costs to cover. Takes more time to find, hire, and manage freelancers than it does to work with an agency. They may not offer project management, voice-over services, and more. Voice-Over or Narration Professionals If your project includes narration, you’re going to need resources to narrate in a variety of languages. If you’re working with a localization agency, as noted above, they may offer narration or voice-over services. If not, you’ll need to recruit voice actors for each language. Keep in mind when you’re on the hunt for a voice actor that differences in local dialects and accents can make a huge difference to your learners. For example, Australian and New Zealand accents may sound similar to an outsider, but to the locals they are completely different! Finding the right voice for your project can take time, so account for this in your project plans, as well as the time required to record in multiple languages. QA Testers Testing and quality assurance review is an important part of creating an effective and high-quality multilingual course. During the project planning phase, identify resources for the testing and quality assurance phase of your course development. What should you look for in your testers? They should be proficient in both the original course language as well as the language they are testing, so they can compare both versions and ensure the message is consistent. The tester also needs to be a good writer, with strong spelling, punctuation, and grammar skills, so they can spot mistakes in the written content. These are just some of the things to consider when planning a localized e-learning project. Remember that up-front planning will eliminate a lot of headaches and help ensure a smoother process and better end result. What tips of your own do you have about planning for localized projects? Let me know in the comments! Follow us on Twitter and come back to E-Learning Heroes regularly for more helpful advice on everything related to e-learning. If you have any questions, please share them in the comments.199Views0likes11CommentsXLF translated files error message
Hi team, I am trying to upload xlf-files, translated by ChatGPT. I have made about 20 attempts with all kinds of different configurations (with html and without, with lessons and without, with a different file name and with an identical file name, before and after having the file checked with an xml checker), but I keep getting the same error message: Check formatting or re-export translation. I get this error message when ChatGPT translates only a single sentence in the file. I even get this error message when ChatGPT gives me back the exact same xlf file, without any changes, just saved again. The only time I don't get this error message, is when I upload the identical file that I downloaded. Obviously, I am following the instructions, so I've made a duplicate of the course, downloaded the xlf file from there, and am uploading in the same location. Clearly, I am missing some sort of information here that's crucial to this process. Please assist as this is getting highly frustrating. Thanks, Chantal131Views0likes3CommentsReplay 360: Changing the Interface Language
You can change the Replay 360 interface to any of these four languages: English, French, German, or Spanish. Click the Articulate 360 desktop app icon in your computer’s system tray (by the clock). Click the drop-down arrow in the upper right corner of the desktop app and choose Preferences. Select your preferred language from the Language drop-down list. Click Save, then close and reopen all your Articulate apps, including the Articulate 360 desktop app, for the change to take effect. (To exit the Articulate 360 desktop app, right-click the icon in your system tray and choose Quit.) Tip: The language setting controls the interface language for the Articulate 360 desktop app, Storyline 360, Studio 360, Replay 360, and Peek 360 for Windows—all at the same time.101Views0likes0CommentsStoryline: Multilingual Course with Text-to-Speech
Text-to-Speech voiceover audio makes localizing courses in multiple languages a snap. And with Storyline 360, creating Text-to-Speech is a snap. Check out this example and this tutorial to get an idea for how to set up your own multi-lingual courses.99Views0likes27Comments