Hide the Image ALT Text in the Localization
Hello Articulate Community, Is there a way to prevent the language validator from seeing and flagging image alt text for translation in Storyline when using the built-in Translation feature? In our project test of the Storyline Localization feature, all alt text for each image (across states/stages) appears in the Translation tab, which makes the interface cluttered and confusing for validators. Is there a recommended best practice to manage or exclude alt text from translation tab, or to streamline how alt text is surfaced during validation? Thank you!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!Translating text-to-speech in Storyline
Hi, I have a Storyline file that includes text-to-speech audio. I need to get this files translated but the text-to-speech does not appear in the translation Word file (not tested with XLIFF). Is there something I'm missing? My work around would be to put the script into the Notes (which is not ideal) but I was wondering if anybody else had a better solution. Thanks SarahStoryline 360( localization file) crashes when try to copy/paste
Every time I try to copy and paste (Ctrl+C) a regular box or a text box in a localization file, the program crashes. I have tried uninstalling and reinstalling, but that hasn't resolved the issue. This issue only occurs with the localization file. Any ideas?Language selection screen doesn't reappear
I just exported a SCORM package from Rise with a multi-language option. When testing it in the LMS, I noticed that the language selection screen doesn't reappear once you exit and re-enter the course. Is there any additional setting I need to enable? I’m asking because, in another SCORM I tested a few days ago, it did allow me to select the language each time I reopened the package. Please, I need a quick solution, the client is wating for the package. Thank you :)Rise Single-Font Limitation for Localization
I might be missing something, but during localization testing in Rise, it seems you can only select one font for the entire course. If you change the font in the Theme of one language in the stack it changes it for all courses in the stack. This isn't a big issue for courses that only use standard Latin characters but does become a problem with Asian scripts. Our usual font pairing uses Inter but Inter doesn’t support the character set for Japanese or Simplified Chinese. I’ve seen recommendations for Noto Sans, but that’s not a built-in option in Rise. And unless you use the CJK variant, it still won’t cover all characters. (And the CJK version isn’t a single font file—it’s multiple versions—so it would likely have the same issue.) How are others dealing with this limitation? Any best practices for keeping the course readable and visually consistent across English, Japanese, and Chinese would be greatly appreciated!DeepL translations and xlf files don't work
When I export an xlf or xliff file from a Rise course and then drop it into the DeepL translator (Pro version), it displays an error message: Course Title.xlf This file couldn’t be translated due to a technical issue. (unsupported_document_version) Anybody know why this happens or knows of a workaround? Thanks.RISE/Storyline free translation?
When will translations/AI be free features? I have had the chance to demo 3 different authoring products in the past 48 hours that include AI assist and Translation either free or very minimal cost compared to Articulate. When will you look to move to this to remain competitive? I am currently evaluating tools that will more closely meet our needs and at the moment the platform is lacking - I have been a big supporter of Storyline from way back in the BETA testing days and would like to stay with Articulate, but the market is certainly offering a lot more of what I need for less cost. Granted some of these tools do align more with RISE in terms of the feature set (which would certainly tick MANY boxes for what we need at the moment) but I would like to think Articulate are able to show that they lead the market in having access to translation/AI features as standard not as an expensive addition.
