Forum Discussion
Rise 360 users: What are your localization pain points?
Hi Rise 360 users!
We’ve been hearing that course localization can be a painful, time-consuming process. We hate that it’s such a frustrating experience, so we’re working on some ideas to make it much easier. But to do that, we need your help!
If you can spare five minutes, we’d love for you to complete this short survey to help us understand your localization needs.
We look forward to hearing from you!
15 Replies
First of all, thanks for this intiative! :-)
A list of languages with button translations would be a good start.Thanks for the feedback! If you have a moment, we'd love it if you could take the survey linked above. :)
For us it is definitely the missing right-to-left support within Rise. We translate all our courses in Arabic and Hebrew, which makes using Rise a real challenge. Sometimes we can use a workaround and on other occasions I have to build a separate course in Storyline just for Arabic and Hebrew.
Agree with Dominik, Right to left support is vital for Arabic and Hebrew translated courses.
BTW, I filled out the survey, but I forgot to include my most significant pain point.
Rise360 outputs using a dated version 1.2 XLIFF. To better support modern automated translation tools and streamline the localization process, it's important to utilize the latest version of XLIFF, 2.1. Ideally, providing an option in Rise360 to save in either version might be the best solution for all.
I've considered making a parser/conversion tool xliff 1.2 <-> 2.1, but I haven't had the time to tackle this project yet.
My other pain point is that Rise360 cannot support multiple languages within a single course. Rather, I must clone each language version, which means that when course updates happen, each course must be updated individually. :(How do you export your XLIFF for translation? In the Settings - Translation tab, I click on export XLIFF button but what exports is XLF. I have a Mac Book Pro, if it matters. Would love an XLIFF file instead. Thanks!
Hi Anita,
That sounds like a simple variation in the file type conventions and it should import into your translation tool normally. This is similar to a .DOC or a .DOCX file for Microsoft word. If you run into any trouble with it let us know - our Articulate Support team is always standing by!
Thank you for filling out the survey and providing these additional insights, everyone! It's so helpful. :)
Setting target and source langauges on export would be a good update. Also supporting the idea to have multiple languages in the same course. It is great being able to have localized versions with specific content but in most cases having all languages in one package is preferrable.My company blocks access to google docs so I can't take the survey; however, I support the idea multiple translations within a single course as mentioned above.
Embedding audio in way that narrates each section to give users with visual disabilities alternate means of receiving the content in a more wholesome way. Sure such users can use screen readers or embedded an audio blocks but either of these options (in sense) limits or segregates the users having to rely on additional technology or reliant on activating.
When using Rise 360, is there a way to embed and audio block in Edit mode, with a triggered start time editable by the creator. For example 2 secs after the user navigated to a specific section the audio/ narration will be queued and start automatically once 2 secs elapsed.
The creator of the course content can have the option of hiding this block from the user (similar MS Excel feature where rows/ columns can be hidden) or having it visableTranslation capabilities
Narratation of sections
Please update the Rise360 output from outdated XLIFF version 1.2 to the actual version 2.1. All of our automated translation tasks fail because of this problem, and Rise users have been demanding an update to this really annoying problem for a long time: https://community.articulate.com/discussions/rise-360/xlf-version-2-1
