Localization issues with Greek in Storyline 360?
Is anyone else localizing from source of English to localized in Greek as well as other languages in the same file? We're running in to a few issues with Greek. I have a file that has now 10 languages in it: English, Chinese-simplified, Czech, French-France, German, Greek, Japanese, Korean, Portuguese-Brazil, Spanish. The two issues When I run the layout issues finder, it keeps claiming there are issues with a number of Greek text boxes. They sometimes look a little funky , like text is spaced out, but mostly they look fine There are no scrollbars added as the layout issue finder is claiming. And on publish, run locally as well as in SCORM cloud, they are just fine. On my client's system, No matter which language my client picks, upon exit, they see the exit message in GREEK! The lesson displays in the proper language. It's just the Exit message that's messed up. It should be "The content is over. You can close this window." for English for example. I have mentioned both to support but they don't have any idea what's going on even though I've sent videos and explained repeatedly. I thought others might be running in to the same issues. Since both are only occuring with Greek, I'm suspecting something may be wrong with Storyline's Greek translation module/software/feature. Thanks for any insight, -- LoriCopy 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 Voice Availability Differences Between Storyline and Rise – Anyone Else Noticed This?
Hi there, While working with AI voices in Storyline and Rise, I noticed a small inconsistency in the voices available between the two tools. Some voices that appear in Storyline don’t seem to show up in Rise, and vice versa. For example, voices like Jessica — Woman | Young | English | American accent | Dialogue | Cute and Brittney – Social Media Voice – Fun, Youthful & Informative are available in Storyline but don’t appear in Rise (at least in my environment). It’s not necessarily an issue, but it does make it a bit challenging to maintain voice consistency across courses, especially when some modules are built in Storyline and others in Rise. I’ve already raised a support case with Articulate regarding this, but I was curious to check with the community as well. Have you noticed similar differences in AI voice availability between Storyline and Rise? If so, how are you maintaining consistency across projects? Would love to hear your experiences! Thanks!How to get Wordcount in a Storyline localized file?
Is there any way to generate a wordcount, notes and/or CCs, plush text on screen for a Storyline 360 file that has been localized? I need this to give to my proofreaders. Because I've used Storyline's localization feature, I no longer am able to export to XLIFF/Word. I can publish a "print" document, but that brings in slides as images and so the text on screen doesn't get counted. Any ideas? Thanks, LoriPer Language Videos just launched in Storyline!
Coming in with another hot Storyline Localization release! I'm excited to share that Per-Language Videos is now available in Storyline. 🎉 This removes a long-standing pain point for authors: previously, replacing a video asset in one language would overwrite that video across every language version of the course. With Per Language Videos, authors can now swap and manage video assets independently for each language, making localization workflows far more flexible. Check it out and let me know what you think! See how it works: https://www.articulatesupport.com/article/Articulate-Localization-Create-Multi-Language-Storyline-360-Projects#community-1204357-local-audio Feel free to leave any questions or feedback you have below!Storyline 360 Multi language timelines changing on publish
Hi, Running the latest (May 12/2026) version of Storyline, but this was happening prior to that as well. I have an English file I've translated to Spanish. So 2 languages. I adjust the timelines per language so that the timelines end at the end of the audio track thus giving the user an accurate seekbar based on language. This used to be just fine a couple months ago. Now, if I publish, it extends the English (shorter) timeline to be the same length as the Spanish thus leaving "dead air" at the end of the English timeline. This only happens if I publish. Before I publish I have this: After I publish I have this: If I save, close and reopen the file I have this: Anyone else have this issue and how did you fix it if you do? Thanks, LoriWhy does the course language label change to English after copying a course?
Hello heroes, we often copy existing courses in Rise and use them as a base for building new ones, updates or different versions. Most of our courses are in German and we give them the German label in the settings. But every time we make a copy of a course with a German label, it reverts back to English. This is kind of annoying, because we tend to forget this happens, and then users complain that there is "Please answer the question to continue" instead of "Damit es weitergehen kann, müssen Sie die Frage beantworten." (Because why would a copy of a german course suddenly have an english language flag?) Only the course owner can change this setting and that is not always the one who is currently working on that course (/working at same time as the one working on the course). My question: Is there a way to fix this? Like a setting that allows copied courses to keep their original language label? Or a way to give course Managers the rights to change language labels?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.
