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 the problem when exporting for translation?
Can Articulate update Rise export XLF files for translation to a 2.1. version?
Thanks
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
+1 The Rise XLIFF files need to be ready for the future (which has already arrived). Please update to 2.1.
Hello SL staff,
We'd like to have Storyline and Rise xliff formats updated too. We are currently manually translating our home-made courses and it takes forever.
Accessing to IA translation via DeepL or similar is a must nowadays !
Please take this one level higher on your priority list 👍
Cheers for your great apps !!
Hello,
Please bump this on the feature request roadmap.
We are in the middle of globalization and specific countries have translation requirements. All training assets and then some.
Thank you,Erin
Does anyone have a tool that translates the Rise courses? I tried SmartCat but cannot figure it out.
I've used SmartCat with XLIFF files exported from Rise many times and it works well
Hi Carlos,
I am trying SmartCat now. How long does it take to import the translated file back into Rise for you? My exported original Rise file is a .xlf and the SmartCat translated one is .xliff. Importation does not seem to ever end for me.
Thanks for your help!
Caroline
Bump for this feature!!
I also want to emphasize that we urgently need Rise and Storyline courses to be exported into XLFF files on the version 2.1 to be processed by deepl.
Wanted to pitch in. We really need Articulate to support 2.1 XLIFF. This is the feature that we need the most right now
Same here. Support for XLIFF 2.1 would make working with Articualte so much more efficient for us. We often translate into 12 languages.
While we wait to hear back from Articulate, I have a solution available now that uses DeepL to translate Rise 360 XLIFF 1.2 files. Not much will change what you do now (ok, maybe saving those extra work/hours!) - export the XLIFF from Rise 360, use the solution to make the translation, and then import back into Rise 360. The solution also supports Storyline courses, too.
If you would like more information, please let me know by either a private message or reach out to me on LinkedIn (usually the best as sometimes I don't get private messages from the forums).
Thor
Hi Everyone :)
Following this thread because this issue causes an incredible amount of extra work/hours. I'd be so grateful if this could be solved so we can use Rise and DeepL.
Fingers crossed for your engineering team's efforts!
Florian
Hi Stephane,
Support for XLIFF 2 has been logged as a feature request with our engineering team. We'll update this thread as soon as we hear more from our team about this feature.
In the meantime, check out this workaround that David Arndt shared in another post.
Am I correct that per David's post, there is no functioning workaround? We are also using DeepL.
- David Arndt
Sorry for the confusion. Apparently the offered workaround does not work with Rise XLIFFs since the structure is simply not like normal XLIFF files.
My fault, I hadn't tested properly.Hi Jennifer. I emailed you from my work account. Please let me know.
