Localisation issues
Hi, I am trying to upload individual language videos into each language section of my courses, but every time I do, it changes the video for ALL language sections. Eg. If I upload a French video to the French video of the course, ALL other language sections also change. The issue is now also impacting embedding videos and ANY content changes I make to an individual language. This seems to be a recent issue - is anyone struggling? It renders the function pretty pointless if this is a new change to the localization/localisation feature.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!Localization Error: "Translations Not Synced"
Hi E-Learning Heroes! Wondering if someone has ever come across this issue. Our organization is new to using Localization and I tried to search for this particular error in the available training guides and materials with no luck. Any help or insight would be appreciated!Switching 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.An English language audio file with English and Arabic closed captions
I seem to remember reading a while back about a work-around that enables one audio file (English) to have two languages as closed captions (English & Arabic), with the user able to choose a version. I think it involved creating a silent audio file, but I can't remember the details. Or did I imagine it? Thanks in advance if anyone can help.Localization File Issue
I’m hoping someone can help me troubleshoot an issue I ran into with the localization tool. Last week, I used the localization feature to translate one of my courses into French. While working on the version saved to my desktop, I was able to switch back and forth between the English and French versions without any trouble. I published the course to Review 360 on Wednesday for feedback from my boss, and I didn’t return to update the file again until this morning. Now, the option to switch to the French version has completely disappeared. I’ve checked my desktop and our shared folders, but I can’t locate the French version anywhere. I’ve attached a screenshot of what I’m currently seeing in Storyline in case it helps diagnose the issue. If anyone has experienced this before or has ideas on how to recover the translated version, I’d really appreciate your help!Localization proxy language hack in Storyline 360: what can break?
Hi everyone, I’m using the Articulate Localization Add-on in Storyline 360 and I ran into a limitation: the target language I need (Papiamento) isn’t available in the Localization language list. So I’m considering a “proxy language” workaround and I’d love to sanity-check it with the community. What I’m trying to do In Localization, I add a supported language as a placeholder/proxy (e.g., English or Dutch — same script, LTR). I don’t rely on AI translations. Instead, I replace all translated strings manually with my own Papiamento translations (copy/paste). The goal is that the multilingual interface (language selector + localized content) shows Papiamento content everywhere, even if the internal language entry is technically a proxy. In other words: the course would display Papiamento text everywhere (content + questions/answers + feedback), but the language slot is a listed language. Main question Is there anything that could go wrong with this approach? I’m trying to identify pitfalls beyond “it’s not officially supported”. Questions / possible pitfalls (please confirm/deny) Metadata / language tagging: does the published output get tagged as the proxy language (e.g., HTML lang attributes, player language settings, LMS reporting)? Player UI strings / system messages: are those fully editable via Localization, or could some UI strings remain tied to the proxy language? Layout / text expansion: do you see UI/layout regressions when the real strings differ in length from the expected proxy language patterns? Accessibility: could screen readers behave incorrectly if lang metadata remains the proxy language? Maintenance: any gotchas when updating the source course later (re-sync overwriting manual edits, harder diffs, etc.)? What I’m looking for If anyone has tried something similar (using a listed language as a container for a non-listed language), I’d appreciate: What actually breaks (if anything) Best practices to minimize risk Whether you’d recommend a different workflow Context: I’ll publish to [SCORM 1.2 / SCORM 2004 / xAPI / Review / Web]. Thanks in advance!You can now Localize Text to Speech on Rise and Storyline!
We’re thrilled to announce an exciting enhancement for all Localization Pro users! When you translate your course, the script will be automatically translated and new audio will be generated and re-inserted in the target language, saving you time and effort. What’s New With this update, translation now includes: Automatic translation of the script (the text that powers Text to Speech). Automatic generation and insertion of localized audio in your translated course. Validator updates: Validators can now update the script, and importing their suggestion will automatically update the audio as well. This functionality is now live in both Rise and Storyline. Important Note for Storyline Users This update applies to both AI Text to Speech and Legacy Text to Speech shapes. You’ll no longer need to manually replace audio after translation, it’s all handled automatically during the translation process! 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.
