Forum Discussion
Return to previous versions of Rise lessons after edits have been made
Hello everyone, 🎉
I'm happy to let you know we released a new update for Rise 360! This update adds the following feature:
- Save and restore your work with a click via an easy-to-access version list that captures manual saves and export events.
There's nothing to install for web apps. New features and fixes are immediately available, though you might need to export your Rise 360 course again.
Let me know if you have any questions about this update.
Hi All,
Hope you're doing well & safe?
My team and I are experiencing a problem with some of the translations.
I understand that we could only import .xlf file for translations onto the original file that we had chosen to export the .xlf file from.
Currently, by chance, the original file that was used to import the translated .xlf file got revised and now we are unable to import any other languages.
Could someone please advise if there is a way for us to resolve this?
I tried researching on the internet; however, there doesn't seem to be much help on replacing content in .xlf file to make it compatible with a different copy of the working file.
I was hoping that we could probably be able to solve this if there was an option to revert to the previous version (as I presume there are some unique identifiers that are aligned with that version)
Thanks for your attention.
Prabhath
Bangalore, India
Prabath:
Hello!
Personally, I found that copy-pasting the contents of the Rise module to Word manually, getting that translated, and then copy-pasting the translation into a copy of the training works better than the .xlf file for this.
Some translation software, such as Trados, do not deal well with that .xlf file.
Basically, what I understand the problem to be is that translation software is pretty good at reading simple HTML files and stuff like that, but a Rise or Storyline project has very dynamic content generated through functions and stuff like that, so the contents are not as readily available as the contents of an HTML file.
Hi Alexandre,
Thanks for your suggestion...
Though, I was hoping Articulate would enable an option to revert to a chosen version or at least ease the process of converting .xlf files from different versions..
Currently, due to the limitations, we might end up with lots of rework/wait time.
Why can't it be simplified like how it's done in Storyline 360?
If I must compare Rise 360 with Storyline 360, the latter is a walk in the park kind of easy to work with while exporting/importing translation files..
Hope someone from Articulate could help us get this reviewed and implement a change that would benefit many users...
Moreover, with the current process, no matter how much control we try to implement, such problems are bound to recur..
I wonder why this problem isn't addressed in so many years...
