Translation for Custom Blocks, Code Blocks, and Text-to-speech
I was just on David's call and these new features in Rise look really great. I can see a lot of possibilities—if I can get them translated. What are the translation options, processes, and limitations for each of these features? For example, are text boxes in Custom Blocks included in the XLIFF exports? What about text in a Code Block? During the call, David inserted a calculator using a code block. The calculator had a heading at the top. How would I go about getting that heading translated? Finally, if I use the text-to-speech feature, how do I go about getting that text translated so I can generate the speech in other languages? Is it included in the XLIFF file? I'm loving these new features, but everything I do needs to be translated and I'm trying to avoid creating extra work and opportunities for things to get missed. Thanks!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 frustrationArticulate Localization - Shrink Text on Overflow Bug
Hi all, Articulate Localization is a dream come true that my team and I have been waiting for for years. We are however running into an issue/bug in Storyline 360 with 'shrinking text on overflow' Currently we use the settings you see below. The text of each box is 'wrapped' and if there is too much text the size of the text automatically decreases. This functionality is essential, because it allows you to easily manage multiple translations because if there is too much text then the text simply slinks a little bit to still fit in the box. As a result you don't need to make ridiculously large boxes for lengthy languages like Ukrainian and Bulgarian (these versions of the training then simply have text that has smaller font). However, Articulate Storyline 360 breaks this functionality when there are multiple translations. Here is the Ukrainian Translation for example: As you can see, suddenly, scrollbars have appeared. This should not be possible but it still happened, if you Publish or Preview the Project the scrollbars are still visible. Therefore, our trial of Articulation Localization has come to a very short end because we cannot use this for our clients if the text of each text box does not shrink in other languages other than the source language. Is anyone else experiencing this bug and/or can this bug be resolved so we can use this feature as well. Secondly, when using Upgraded Project Text the option to 'Shrink text on Overflow' disappears whilst this feature is 100% necessary for running multiple translations in the same Storyline file. Japanese uses about 50% of the space Bulgarian uses, so making huge text boxes for everything just because there are languages that need a lot of room means there is also a lot of empty space on other languages. In short, it's MUCH better if Storyline simply reduces the font size of these languages so you don't need to leave insane amounts of room. We are excited about Articulate Localization, but it needs to work perfectly in Storyline 360, because we (on average) would like to have twenty languages running in one file. Best regards. Kaj DekkersArticulate 360 User Guides are Moving!
Hey, everyone! As we get ready to say goodbye to 2025 and hello to 2026, we're setting you up for even greater success in the new year. In the next few weeks, we’re moving the user guides you know and love in ELH over to our other documentation database in Product Support! That means you’ll soon have a “one-stop shop" for all of your Articulate 360 documentation needs. This change will also improve the accuracy and responsiveness of Artie, our AI support agent. (Did you know you can ask Artie to find documentation for you instead of searching?) Unifying our databases enables us to analyze usage more deeply so we can better tailor our documentation to meet your needs. Plus, it gives us more options for translating user guides into other languages to serve our global community. Once everything has been transferred, the directories for the individual user guides you depend on (and may have bookmarked), like those for Storyline 360 and Rise 360, will remain available in ELH for your convenience. When you follow the links to the individual articles, they’ll take you to the Product Support knowledge base. We'll have landing pages for each Articulate 360 product there as well. We have a few more things to put in place before flipping the switch, but the transition should be seamless for you when it happens in the next few weeks. Let us know if you have any concerns or questions in the meantime.Localization News!
Hello, I just wanted to take a moment to share a couple of announcements that I'm super excited about! The big news is that we just launched Articulate Localization, which allows you to translate, validate, and manage your courses from within the Articulate 360 platform. 😍 Check out this article for more information. Along with that, I'm happy to share that we just launched a new Localization group where you can ask questions, discuss localization best practices, connect with others who work with localization, and more. Just hit the Join Group button to get started! I'm curious, have you started a trial of Articulate Localization yet? Let us know in the comments!Localization 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?Query and Feature Request: Pop up when a localization credit will be used
In my last billing cycle I created a localized e-learning in 8 languages (elearning 1). In the new billing cycle I initially didn't have localization as an add-on and so couldn't open the file, instead I was prompted to save the languages as individual storyline files. Then a different project has been assigned 10 credits so localization is back as a feature but I only want to use those credits for a specific project that Omniplex are working on and not my original file (elearning 2). What I cannot tell is, if I make edits to one of the exported language files from my original e-learning (elearning 1), that I created when I didn't have localization enabled, will I be charged a credit when I publish that individual language file? And if I am not the admin of the account how do I know if a credit is about to be used / has been used? Could we please have a feature in Storyline that gives you a pop up when a credit is about to be spent? It would help a lot in trying to manage credits that have been allocated for certain projects, especially if you have a centralized account with one admin, as then users could see if and when they are at risk of spending credits they don't have allocated. Thank you for any support.Introducing Custom Block Localization (Public Beta)
We’re thrilled to announce an exciting enhancement for all Localization users! You can now translate Custom Blocks in Rise! What’s New With this update, Rise translation now includes Custom Block elements, including: Text Text to speech audio This functionality is now live. Next Steps We’d love to hear your feedback and learn about your experience using this new feature. Your insights are invaluable as we continue refining how teams create localized learning experiences. Refer to the documentation here for more information!Introducing Localized Timelines!
We heard your feature requests loud and clear! If you’ve ever localized a course, you know that different languages often require timeline adjustments due to variations in syntax, word order, and text length. Until now, making those changes meant impacting your source version. ✨ What’s new? You can now adjust timelines for individual target language courses directly within Storyline, without affecting the source language version. That means: Greater flexibility when localizing Cleaner workflow between source and translated courses No more timeline workarounds to accommodate narration expansion For more detail on how this works, check out the user guide. Install the March 2026 Storyline update (or later) to set per-language timing and duration for each object, cue points, and slide duration, including those on layers and slide masters. Note: Localized timelines are currently in public beta; functionality may change based on feedback.
