Export to XLIFF 2.0 File in Rise

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.

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.

Okay, to summarize, DeepL is the seemingly best AI translation tool.  At least, it is favored (by some of us).  Rise only exports in an old XLIFF version that will not work with DeepL (which is what many of us use). We do not wish to have to send source files to a paid translation servicer who perhaps has RISE 360. Even they would prefer to have a format that makes translation faster for them rather than having to manually import an unsupported XLIFF file and doing manual edits in Rise 360.  We need to be able to use the AI translation ourselves. This saves us both time and money. Currently, I need to copy and paste every text area manually into DeepL and then paste it back in, which is unacceptable overall.  Exporting to a newer version of XLIFF does fit into Articulate's vision of using AI and being a cost-effective solution if you support higher versions of XLIFF on export. We waste time and money as corporate or consulting-centric users of Articulate without this feature. I have recently tried a non-Articulate less-featured tool that auto-translates on the fly so Articulate needs this feature for competitive reasons.

This doesn't work for us, we have expert translators for Medical terminology and consistency throughout our modules.  We need the ability of exporting this xlif.

Hi, Funny how things are moving. Rise just included, sorry, added as an option an in system translation. I just tried it and it works pretty well and ultra fast. Pricing is not mentionned but it is a huge progress. To be confirmed how much it will cost if not included.

Any update on this?

Hi, still no development of the XLIFF 2.1? This has been hanging now for years, what is happening on your development? Is everything completely on hold? The standard is well defined, please just add this ASAP as this "function" now is rendered completely useless. You  might as well just remove if it does not work at all with online services.