Forum Discussion
XLF Version 2.1.
I have subscribed to the Advance version of DeepL as a translating tool. DeepL requires an XLF 2.1. version for translation but Rise 360 only export in version 1.2.
Has anyone been able to solve t...
How to change your versioning to translate your XLIFF doc for Rise. This is the process I use and it work.
- Log in to your Rise account using your credentials.
- Search the Rise module that needs to be translated.
- Click on the tree dot in the top right corner of the module.
- Select “Duplicate” and create a copy of the module.
- Access the copied module by clicking on it.
- Click on setting on the top bar
- On the Translation tab, click on “Export XLIFF File” button
- An XLIFF life has been downloaded in “Your Download”
- Open your XLIFF using Notepad++ (Right click on it and choose “Open with”)
- Click on the text on the top of the screen. The firs section will turn yellow, and, in that section, you will need to replace the versioning 1.2 by 2.1 (3 different place as shown in the picture bellow)
- Click on save (third image .. hard drive) You now have an XLIFF version 2.1
- Access your translation engine (DeepL, etc) and download the XLIFF doc for translation
- Once the document is translated, download it back into “Your download”
- The translated document will end with “fr-ca.xlf”
- You need to repeat the same process as #8 and change it back from 2.1 version to 1.2 at the same tree places using Notepad++.
- Click on save (third image .. hard drive) You now have an XLIFF version 1.2
- Access back your copy of the Rise module that you have exported the XLIFF doc and click on “Import Translated text” and select your document that finishes with “fr-ca.xlf”.
- Update the label to “French”
- Close this window by clicking on the “Close” button on the top right corner.
- The module is translated and ready for French QA
Hi Stephane,
thank you for the detailed description. The solution to simply "label" the xliff 1.2 file as an xliff 2.1 file with an editor has been posted in this forum before somewhere.
Nonetheless, I had my IT install notepad++ for me and tried it out, both with and without HTML tags in the xlf file.
Unfortunately, it does not work for me, or at least for my version of Deepl (I have the pro version). I get the message that the xlf file could not be read. Changing the file extension to .xliff does not change that.
Thinking about it, there must be more to different file versions than just a label.
So, it's back to copy-paste, or at least translating frame by frame, which is reasonably quick thanks to Deepl Pro. But it does take a long time...
It would be worth the effort of editing every single xlf file by hand if it worked, because articulate do not seem to have any intentions of changing their version of xlf file. Which in itself is a pretty poor show, if you ask me. But this discussion has been going on for years, and they seem to get away with it. ☹️
Hi all, I found a relative cheap solution for xlf translation: the software "poedit" (around 40USD/year) can support the machine translation with DeepL (through API, with DeepL Pro). The "poedit" tool itself is limited in functionality, it is not a generic CAT tool, because it is limited to software development file formats (.po and others), but works with Rise360 xlf file (tested, translation import back to Ris360 works without problems for me). Do not mix it with "poeditor" online service - that is different (and more expensive).
