translation
28 TopicsSwitching between languages in the LMS
Hi everyone, how are you? I used the "Localization" feature in a course. After making the content available, when selecting a language I can't revert to the original language. What am I doing wrong? Choice of language After this, it is no longer possible to change the language. Thank you in advance.97Views0likes4CommentsRise 360: Manually Translate Your Content
This article covers the process of manually translating Rise 360 content into left-to-right languages using XLIFF exports and imports. This method is best suited for single-language translation. Articulate Localization, available as a subscription add-on, allows for seamless creation of multi-language courses within Rise 360. Learn more by visiting the Articulate Localization user guide, or contact our sales team to learn how you can add Articulate Localization to your subscription. Read on for the manual process. Duplicate Your Content Export the Content as an XLIFF File Import Translated Text Translate Your Labels Translate Training into Multiple Languages Step 1: Duplicate Your Content The first step in the manual process is to duplicate the content you want to translate. The duplicate you create is used for the translated version. On the Rise 360 dashboard, hover over the content you want to translate and click the ellipses icon that appears. Select Duplicate. Enter a name for the duplicate content. (We recommend using the original course title, appended with the language code, such as “fr” for French.) Then, click Duplicate to confirm. The duplicate content appears at the top of your Rise 360 dashboard. Note that you'll need to create a duplicate for every language you want to translate your training into. Alternatively, with Articulate Localization, you can translate your content into 80+ languages (including right-to-left languages) and manage all language versions as a single project stack, right from the Rise 360 dashboard. Step 2: Export the Content as an XLIFF File Open the duplicate content you created in the previous step. Click the Settings icon in the upper toolbar. On the Translations tab, expand Traditional XLIFF Translation. If you're following this guide, skip Steps 1 and 2. Under Step 3, 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. Enter the source language in the Set source course language code field if it's something other than U.S. English (en-us). As you type, a list of available language codes appears. Click Export XLIFF File and save the file to your computer. Edit your exported XLIFF file with a web app, computer program, or professional translation service. If Include HTML formatting was selected, you'll see additional HTML tags and extra spaces in your exported XLIFF file. These are there to preserve your formatting when you import your translated file. The following can't be translated using manual XLIFF exports: Code blocks: modify the code for each language after translation. Question banks: Questions drawn from question banks included in knowledge checks and quizzes display in their original language. To translate question banks, add Articulate Localization to your subscription. Tip: Rise 360 uses XLIFF version 1.2. Step 3: Import Translated Text Once you've translated your content, import the file back into Rise 360. Open the duplicate content. Click the Settings icon in the upper right corner. On the Translations tab, expand Traditional XLIFF Translation. Under Import, 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 content,” 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 piece of content 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. 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. Let us know if you have any questions. We’re happy to help! Step 4: Translate Your Labels Once your content has been translated, translate your buttons and other built-in navigational elements. Click Settings in the upper right corner. Select the Labels tab. Follow the instructions in this article. Note: In order for the correct language to be assigned to your training so that assistive technologies can communicate the content with the correct presentation and pronunciation, labels must use the same ISO language code as your translated content. Translate Training into Multiple Languages For multiple-language training, we recommend Articulate Localization. Not only does it provide a streamlined experience for translating training into multiple languages, but it also offers a deep set of features custom-built for your translation needs. Contact our sales team to learn more.28KViews4likes0CommentsLocalization translation of closed captions
Hi - We have just started using the translation features and received this feedback from a reviewer "In general, the translation is good. However, in the section which translates the closed captions of the videos, as it takes only one sentence at a time, it loses all sense and is very difficult to correct." Has anyone had the same experience with the translation of closed captions?84Views0likes1CommentAudio Translation
Hi everyone, I have a question: will a translate audio feature be added to Localization? I'm testing it during the trial period and just noticed that it only translates the text on screen, not the audio, so we have to type or re-record the text in the new language, which is quite time consuming. Thank youSolved482Views1like11CommentsTranslating a course into Farsi
Hi Everyone. I am still pretty new to Articulate and brand new to the world of translating an e-learning. I apologise in advance if I am on the wrong forum as I am not subscribed to Articulate Localisation so my question is not about that service but translation in general. I have spent the whole day researching the best way to translate my small eLearning from English to Farsi, using copilot and ChatGPT as advisors. Various tools like Smartcat, Crowdin, Localise were recommended but the pricing plan felt high for me given I am just starting out and the NGO i am developing my first e-learning for also doesn't have a lot of money to pay out each month. In short, given I already had the content translated into Farsi in a word document, I decided to manually upload the Farsi version into Rise and then align/format the text. For those elements that I was unable to align within Rise (a handful of headings and MCQs), I decided to export a XLIFF copy and using Poedit make the necessary edits/format changes. I then successfully managed to import the updated version of the XLIFF file which I was happy about as I read it can be problematic. However for the headings I was struggling to align/format - instead of correcting them to a RTL alignment it changed the headings to the original heading with the tags as text instead of interpreting them. Regarding the RTL formatting of MCQs ChatGPT said this was not possible as the formatting was baked in within Rise. When I reported back to ChatGPT about my issue with the headings and asked if I used more powerful translation tools like Localazy would I have the same issue, ChatGPT implied yes. I appreciate ChatGPT doesn't know everything. My conclusion at the end of todays research is the best thing is to continue to manually enter my translated material and make the alignment changes I can do within Rise and just accept some things wont be aligned perfectly and thats ok. However before I make this compromise (as I know I might get frustrated with this compromise as the 'test' lesson happened to be relatively simply formatted whereas other lessons have bullets, timelines, image and text blocks, etc.. which might throw up more challenges) I thought I'd seek any advice from this forum of experts. If anyone has any advice, similar experience and solutions (hopefully) or just confirmation that I need to accept this compromise I'd much appreciate it. Many thanks in advance for time and expertise. Kind regards Katheirne49Views0likes0CommentsStoryline 360: Enabling Right-to-Left Language Support
Use Articulate Localization to include right-to-left languages seamlessly in a single multi-language course. 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?1.6KViews0likes0CommentsStoryline 360: Translating Courses
Use Articulate Localization to create single multi-language courses seamlessly in Storyline 360. 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.29KViews0likes0CommentsLanguages missing for Label Translations
Hello, I am new to Articulate/Rise, learning my way through. I need to translate courses into various languages. I have been using the XLIF and Smartcat successfully. I went to select the respective language for the label translations, and the first two were successful. When I went to do this on a third course, the languages available were cut down to 4. I lost all of the extra languages and dialects to choose from. Now it just says 'coming soon' for the extra languages. Is there a reason for this? Anyone else experiencing this? Thanks! Jim133Views0likes4Comments