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
82 Replies
- LiisaBradeCommunity Member
Hey - just out of curiosity, which authoring tool have you transitioned to?
- MammoetAcademyCommunity Member
We have moved to FlowSparks and Easy Generator, but still have some content in Articulate Rise. As an international organization, the need for translations is significant. In the past, translating content was often difficult, time-consuming, and expensive. However, with tools like DeepL and AI, we can now translate and localize content much more easily.
I’ve always been a fan of the simple translation functionality in Articulate Rise, but I’m also quite disappointed that it still doesn’t support the industry standard XLIFF 2.1 (introduced in 2014).
- MammoetAcademyCommunity Member
What is Articulate's roadmap for this? Two years ago they mentioned it is on their development list.
We now moved to another authoring tool and we work with many languages.
- MammoetAcademyCommunity Member
Is the issue after 2 years solved?
- StuartOrson-a5bCommunity Member
Hoping that this can be fixed in an update soon?! 😏
- ThaïsCommunity Member
I tried this solution and i'm not able to upload it into deepl :( . anyone who experienced this as well?
- FelixFrankeCommunity Member
Hi Thais,
You are right, it does not work for many people. Has been discussed in some of the 66 answers above. If it was so easy, we would not have so many threads about this issue. Or if articulate got their behinds in gear and catapulted the export format into the 2020s. xliff 1.2 has been deprecated since 2014 (see here and links on that page)
I just stumbled across this: Maxprograms - XLIFF Manager
Haven't tried it, because I have just had HERO Translate installed on my computer, I think my IT will eat me alive if I ask them to install another program with the same purpose 😂😂
- TJBarber-a1e652Community Member
This is extremely upsetting to learn. Though I'm not surprised, I have been using Storyline in some capacity for 10 years and I have not once ever seen Storyline update a feature based on these user boards. It doesn't matter how significant of an issue it is, or how out of date their settings may be, the company just does not support it's user base who pay a predatory premium for the product.
- TomWhite-c03a2eCommunity Member
Hello, can anybody advise if the posted soultion from Stephanie does work as I cannot get this work when following the steps. Many thanks
- MaryKohlmannCommunity Member
For others who are struggling with this, I'll note that I tried the HeroTranslate solution Thor Melicher mentioned upthread and it's been working for translating my Rise courses. (Haven't experimented with Storyline.)
- FelixFrankeCommunity Member
Hi Mary, that is very good to know, my IT dept. have been vetting this for ages now, I hope I can get it soon. It would make translations so much easier...
- HansVerdoodtCommunity Member
Hi All,
I've been proposed a solution by Herotranslate that makes the link between Rise360/StoryLine and Deepl. Basically, this little software takes care of the concersion V1.2 - V2.1 in both directions and interfaces with Deepl for the translation. You need the Deepl API to be installed.
The free version of the Deepl API covers 500.000 characters per month and was sufficient for 6 language copies from my e-learning.
Herotranslate can be purchased through the Microsoft store for 20USD.
It works for me, this is a video that explains the process : Thor's HERO Apps - YouTube
- StephaneRajotteCommunity Member
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
- SabineStaufferCommunity Member
This solution does not work for me. - It's not a valid solution.
- ZsoltImre-fe8b0Community Member
PLEASE REMOVE the "Marked as Solution" - it is not a solution, it simple does not work.
- ZsoltImre-fe8b0Community Member
I propose to remove "Marked as Solution" - this big green stamp is misleading, the explained solution does not work for most cases. The two versions of XLIFF (2.1 and 1.2) are both structurally and technically different, XLIFF 2.1 by definition does not provide backward compatibility with XLIFF 1.2 (version 2.1 is only backward compatible with version 2.0).
See: related official document, "Backward compatibility"):
- ErinGreenCommunity Member
ZsoltImre-fe8b0 I fully agree with you. I am posting this on LinkedIn.