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.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.AI TTS Translations
See Storyline’s localization AI in action. This quick demo shows how you can translate and generate audio across languages faster—without rebuilding your course. Go behind the scenes with the team behind Storyline’s new localization text-to-speech feature. In this interview, they explain how it helps you quickly generate natural-sounding audio in multiple languages—without re-recording voiceovers.Copying Storyfile with a language stack...Issue
Hi all, I have a serious issue (i already submitted a ticket) which puzzles and bothers me. My workflow: Working on multiple-multi language projects. Some have a similar, multiple scene, setup. After i finished one (Project A), i used the new localization process to create a stack with 5 languages. So far no issues. Since the next project had quite a few similatities in setup i did what i usually did: I renamed the existing project to the name of my next project (thus copying it, "Project B"). After editing, adjusting, deleting, adding etc i finished and saved Project B again. Ready for the localization. Upon creating the new stack i was prompted with a warning: Translations will be overwritten. That seemed expected behavior, thinking i copied the translations from the initial Project A. Ok. Continue... And then it went wrong: At parts of the new project the (slide)notes were missing at the new translations (Thus also not translated) and the source languages notes (English) were placed at another language (Dutch). I use these notes extensively for text to speech and CC. If i wanted to publish Project B for review the option 'Create a new item' is missing. Only the option: 'Publish a new version of an existing item' is presented but greyed out and has my initial (other) project (Project A) name prefilled in. I fear that when i publish the partly untranslated Project B that will ruine Project A. It's a complete mess and it costed me 5 valuable tokens as well. Anyone advice on how to proceed on here? Or had similar behavior?End of the Year Feature Release
This video highlights key moments and accomplishments from the past year, showcasing major milestones, progress, and impact across the organization. Which feature from this year improved your workflow or helped you the most, and how did it make a difference for you? Let us know in the comments!Localization Closed Captions not appearing on Layers - HELP!
I have a file created in English and translated to French using the localization feature. Due to timeline management, some slides have layers for french vs english. When published, the CCs for only the SECOND layer in the order of layers shows up. So if English is selected as the language, English CC shows. If French is selected, French CC does NOT show. But on this slide below, only the English CCs show upProblem with the screen recording in Articulate. HELP!
Hi everybody. Ok, there is a big problem which I am facing. 😬 Screen recording I have. Screen recording as simulation was done by me by selecting an 'x' size of screen size, which is never a trouble maker. Now I put that same recording as simulation where slide by slide test mode was selected by me. Now my smart colleague chose to change the screen size to 720x540. I had kept it 960x540 earlier. Now she wants me to simply copy and paste the slide as shown in below screenshots for ref. I 'simply' copy it and by doing ctrl+v I could duplicate the slide.😒 (Note: this is happening for any slide that I try to duplicate). As shown below in the SS, the recording size or ratio gets distorted and goes out of the slide size or canvas. Since its a recording, I get no option to fix this by adjusting the edges of it like how we increase or decrease the picture or image size. It 'simply' doesn't allow me to have a clean duplicate file or slide of the ones created. Therefore, I seek for help from anyone who could do some miracle. Else, I have to redo everything or to think about some something else. Because these things aren't in my control. Watch the SS attached carefully. Thanks. 😇
