Rise translation - Trados 2017 issues?
Jun 24, 2019
Does anyone experience a buggy behavior when importing translated Rise course (done in Trados 2017) back into Rise course? Did you manage to overcome this somehow?
We encounter a problem, where even if we follow the exact steps advised by Articulate to export (including enabling the option Do not store segmenation... before starting the project) , translate and import back the Xlif file - it behaves erroneously and replaces chunks of our Rise course with [object] tags.
I have been in contact with support and got an explanation that the cause for this lies in the <g> tag that Rise uses in its file, which does not cause any trouble with Trados 2019, however does not work with Trados 2017.
Our company will not buy the new Trados licenses, so we need a workaround for Trados 2017 to be able to use the Rise translation feature.
Is there any solution that works for you?
@Articulate Team - could you please enable the export to Word from Rise for translation, just like in Storyline? It is a huge hurdle to copy-paste manually the translation into Rise for the courses.
Thank you very much!
This discussion is closed. You can start a new discussion or contact Articulate Support.