Articulate Localization – A Licensing Trap?
Our Situation During the previous billing term, we purchased Articulate Localization credits and used them to translate several courses. However, while our subscription was still active, the licensing terms were fundamentally changed. When our current billing term began, we decided not to purchase additional Localization credits because of these new conditions. At that point, we discovered that the translated courses we had already paid for could no longer be used as expected. What We Find Problematic We paid for the translation of our courses. Nevertheless, without an active Localization license, we can no longer use the translated content in the way we originally anticipated. Most importantly, it is no longer possible to save projects to individual languages or export a translated courses in a single lanuage as SCORM packages. From our perspective, this raises several concerns: Changes to the Licensing Terms The licensing terms were changed during our contract period. As a result, we now have no real options for working with translations that we already paid for than we had at the time of purchase. Previously Paid Translations Are Effectively Locked The translation service was delivered and paid for. However, the translated content can no longer be freely exported and used. From our perspective, it feels as though we are being required to pay again just to access and use content that we already own. Furthermore, the full translation cost is incurred again for every change after the current billing term - even if only a few words need to be updated or a single-language course simply needs to be re-exported. Lack of Transparency Before Purchase Our official Articulate reseller did not inform us that projects created using the Localization feature would become significantly restricted once Localization credits were no longer available. Had we known this in advance, we would most likely not have purchased the Localization feature. No Opportunity to Adjust Our Subscription We made several attempts to change our existing billing term to an annual subscription. Unfortunately, this option was not made available to us. As a result, we were placed under significant time pressure and were unable to properly assess the impact of the licensing changes before making renewal decisions. Our Conclusion We paid not only for the translation of our courses but also with the expectation that the translated content would remain available for long-term use. Discovering that courses that had already been translated could not even be exported as single-language courses once the localization license had expired was neither transparent nor foreseeable. Clear and transparent information about these restrictions would have significantly influenced our purchasing decision and could have prevented a great deal of frustrationLocalization Validation Tools for English Course/Project
Clearly the Localization Validation tools are great for other languages, but why don't they exist for the published English version? These tools and their capabilities for simplifying the review process would be great for any course, no matter the published language. How about some support to get those validation tools implemented as standard to Review 360?French Canada Translation export
Hello E-Heroes, I am experiencing an issue with Storyline 360 translation exports and would appreciate your comments/help. Smartling (translation platform) claims their .xliff is ok Issue Summary I have successfully created and translated multiple language versions of the same Storyline course (approximately 10 languages) without any issues. However, the French (Canada) version behaves differently. Steps Performed Open the original English (.story) file. Export Word for Translation → Success. Create a copy of the English course using Save As. Export Word for Translation from the copied course → Success. Import the translated FR(CAN) XLIFF file. Translation imports successfully and all content appears correctly translated. Export XLIFF from the FR(CAN) version → Success. Export Word for Translation from the FR(CAN) version → Fails with the message: "The translation export failed." Thank you!!!Automatic Selection of preferred language in LMS/SCORM-Package
Hi there, I have a question about the localisation feature in Articulate Rise and would be grateful if anyone with similar experience could help me. 😄 My use case is as follows: Our course content is inside an Articulate Rise course and is exported as a SCORM 1.2 package to a Moodle platform. When the SCORM package is clicked, the user is directed to a pop-up containing the course contents. I understand that Articulate Localisation is the best way to generate and export Rise courses in multiple languages, as demonstrated in the following article and e-learning course: Articulate Localization: Publish Multi-Language Rise 360 Courses | Articulate - Community https://rise.articulate.com/share/wbbxvTJyDgfSsfVryNBVDjvmjdX8agsK#/ The best method I have found is to allow the user to select their preferred language at the beginning of the SCORM package using a dropdown menu, as demonstrated in this article: Multi-SCO SCORM Package with Language Select | Articulate - Community Is there any way to skip the dropdown menu and automatically display the correct course language based on the user's browser language or, alternatively, based on the user's Moodle profile fields? Ideally, this would not require much coding or a custom solution and would not change the current user flow when accessing course content. Any help or feedback on this issue would be much appreciated. 🙏 Best regards, FelixEnglish state overwritten with changes in other language, quiz questions, storyline 360
We've come across a weird bug. Storyline 360 (version from 6/9 - we can't upgrade due to the closed caption issues in 6/16 and 6/23) File is in 10 different languages with English as the source language. I have question slides. Originally, answer options just had normal, hover and selected states. I added a disabled state to each option and set that as the default. Once audio is over, I set the states to normal. When I edit the disabled state for a non-English language and then flip back to English, the button now reads in that other language in the disabled (default) state! This is causing all kinds of grief and thank goodness we notices before delivering to the client. I should have to go back and recheck English when I'm adding another localized language to the file. Has anyone else experienced this? Know of a work around? Reported it as a bug? Any advice is helpful! Thanks, LoriLocalization Glossary Behavior
I have a question about how the localization glossary handles acronyms and partial word matches. For example, I added the acronym CRISP to my localization glossary because I do not want it translated when translating from English to Spanish: en es-419 CRISP CRISP If I apply this glossary during translation localization: How would the words "crispy" and "crispiness" be translated? Does the glossary entry for CRISP → CRISP affect the translation of "crispy" or "crispiness" because those words contain the character string "crisp"? Or does the glossary only apply to exact term matches (for example, the standalone acronym CRISP) and not to words that merely contain the same sequence of letters? I want to confirm whether adding CRISP → CRISP could unintentionally impact the translation of related words such as crispy or crispiness.Assistance Required: Audio Playback Issue on Client LMS
Hi Team, We created and delivered the Storyline modules to the client around six months ago, and at that time all the audio worked correctly. Recently, we made some updates to the modules and shared the revised versions with the client. However, after uploading the updated modules to their LMS, none of the audio files are playing. Could you please let us know what might be causing this issue and if there are any known reasons or troubleshooting steps we should check? Thank you in advance for your assistance.Copy of a localized (multi language) file cannot be published to a NEW review name
HELP! I created a file and localized it with English/Spanish. I published for review. It went great. Now I need to make a similar file, so I started with my existing file and made a copy of it. Made a whole bunch of changes, updated translations, etc. But when I go to publish to review 360, it wants to publish to the original review. But this is a NEW file. How do I fix this? Do I have to start over every time with a non-localized file and redo all the formatting (getting rid of scroll bars, etc) again? I should always be able to publish as a NEW review when I want to. Please advise.Rise: Problems publishing localised courses
Hello, I’m reaching out for help because I’ve run out of ideas on how to solve this issue myself. We translated a Rise course into four languages, and for the past three days I haven’t been able to export the localized SCORM packages. What’s interesting is that I can export the English version of the same course, and I can also export localized versions of other courses. However, with this particular course, I simply can’t get the export to work. I should also mention that a colleague successfully exported everything from this course about a week ago without any issues and without using any special settings. I’ve already tried clearing cookies, exporting from a different account, opening the course in another browser, creating copies of the course, and similar troubleshooting steps. Do you have any idea what could be causing this problem? Many thanks in advance 🫶 P.S. I have problems publishing any of the items of localised versions: LMS, Web, PDF, Quick share :-(
