Forum Discussion
How to do translation of question bank
Dear Articulate team,
There is a bug in Rise regarding question bank translation. When create a xlif file for translation and import the respective translated xlif into their respective language ...
Hello, I'm facing exactly the same problem with translating a question bank!
I’m trying my best to navigate through a completely incomprehensible XLIFF file, copying and pasting in all directions…I believe my eyes can no longer see.
There is a significant area for improvement concerning translation. Why not create a multilingual module, with a menu to activate that allows changing the language of the module at the user’s request?
Hi Matthieu,
that is my dream, too, being able to create a module with several languages to switch from one to another (It would be doable with Storyline, JavaScript and a lot of programming I guess, but... really?).
Unfortunately, that does not rid you of the task of translation, which is what the xliff file is meant to help with. But as you have exoperienced, it is an xml formatted file, which is almost unreadable by humans. You ned a translation program for it. Then, it works, more or less. I am not a professional translator, they work much faster.
The problem with that is that those translation programs read xliff 2.1 these days, and Articulate software still exports the long outdated xliff 1.0
So for translating Rise360 Modules, you need to open a side window and have a translation program or ChatGPT or whatever open and edit it. Deepl works very well, necause it writes the translation directly into editable fields in open websitzes. But still, I have to do that myself, as the owner of the Articulate license. Works for German, English and Spanish (in my case), but what about Korean, Chinese, Japanese?
I'm happy to chime in, Felix. I will also add your vote for a multilingual module feature in Rise, and we'll update this thread if it becomes available in a future release.
Thank you for your suggestions!
