Forum Discussion
Export to XLIFF 2.0 File in Rise
Hi,
Is there a plan to update Rise to export XLIFF 2.0 files? My translation vendor will be requiring this version.
Thank you!
Nancy
105 Replies
Hi. So there are three ways to potentially handle a translation using DeepL and RISE360 and perhaps we can all work on this one.
Method 1 - HEROTRANSLATE. It's a paid app. This method mentions RISE360 and I'm getting an authentication error when trying to use my API key as we have DeepL Pro which includes an API key. Getting that worked out may load the RISE XLIFF export and then translate it into another specified language. It's worth the $20 fee to test this out.
Method 2 - Using XLIFF Manager (free app) to convert the version 1.2 RISE360 XLIFF export into XLIFF version 2.1 then load that into DeepL and back into Rise360. I'm getting an error but this also may work and XLIFF Manager is open source.Method 3 - This is crazy but... it is close to working. Export your XLIFF file in Rise that will output as version 1.2 of XLIFF. Open the file in Notepad and change the text references at the top from 1.2 to 2.1 then save the file. So it may say things like document 2.1 and version 2.1
xliff xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:2.1
when you are done. Note that the file type becomes .txt which is not what we want. Open the file in Notepad again and under the File->Save As option
1. click the save as type dropdown and select All Files
2. Put your file name in quotes. (example "MyXLIFF_Export.xlf")
By putting it in quotes then it literally saves as that file type and overrides the file extension of .Txt
3. Import that file into DeepL under the file upload feature (needs Pro version or higher). It actually translates the file into another language
The problem that I'm getting with Method 3 (or perhaps other methods) is that when I go back into Rise and select Settings->Translations tab->Step 3 Imported translated text and import the version that DeepL translated, then it says "Check Formatting or Re-Export translation". So play with this. I went into the DeepL translated XLIFF and then changed the text at the top from 2.1 to 1.2 and it got a little further now saying, "XLIFF translation file doesn't match the course. XLIFF translation files can only be imported to the same course they originated from. The files are unique to each piece of content."
This method 3 may be close. Perhaps changing the language = "country here" may be involved, I don't know.
If others can help try this out we may be able to find a workaround.I use eLearningTranslator for this as it is built exactly for this use case. I'd be happy to help if anybody has questions.
Hi Nico. Is eLearning Translator the same as Smartcat? Our org is trying to save a bit of money, not that Smartcat is expensive for many orgs.
Yes, the price is way cheaper and there is no subscription needed. You can simply purchase prepaid credits depending on how much you need to translate. It's also directly specialized for the translation of Rise- and Storyline-courses.
