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
DeepL work around for Storyline:
If you export version 2.0, you can open the file in Notepad and change the version number in the header information to 2.1, save the file and then drop it into DeepL. Then take the translated file and open it in Notepad and change the version number in the header back to 2.0. Then you can import the translated file into your Storyline course.
Don't have a work around for Rise courses, however, as can't get an edit to a 1.2 version file to work the same way. The header is built differently, and it doesn't work the same way.
...AND... we have a few hundred Rise courses we need to translate and are under a tight timeline...so not sure what to do about that... We REALLY need to have Rise able to export version 2.1 immediately!!
+1 really needed here, too. Must work with deepl.
Any update on these requests for version 2.1?
Has someone found an alternative solution?
Hi Hans!
Thanks for checking in on this!
I don't have any updates to share at this time as our development team has been prioritizing other features. I've included you in the feature report being tracked and will update this discussion as soon as we have news to share. If you'd like to stay up to date, you can bookmark our Feature Roadmap.
In the meantime, for your reference, here's a deeper look at how we manage feature requests.
Hi Steven, this is quite a basic feature (Rise / XLIFF version 2.1) and the request has been made years ago. What is the problem in getting this implemented? When will this be done? Or has it been done in the meantime? Thank you!
It is utterly unacceptable that Rise and Storyline can't output to XLIFF 2.1 for two reasons:
- It's almost 2024 and XLIFF was released in February of 2008; XLIFF 2.1 was released February 2018 - almost 6 years ago.
- XLIFF 1.2 is no longer maintained by the OASIS Technical Committee.
Please be sure to prioritise this update to Articulate software.
Likely allowing for XLIFF 2.1 output is NOT a priority for Articulate - 100% sure they are working on an integrated solution instead (at an extra cost, of course). In this scenario you create a course in your main language, let's say English for this instance, then the user would be able to select a "Translate Course" button with a language drop down menu.
Hi, @ShawnConnelly. Of course it could help a lot.
Thank you very much.
Greetings all,
I am new to Articulate Rise 360 and so far, I am not liking what I am seeing. :(
I am a consultant and I was asked to build Rise 360 training for a new initiative. But so far, two of the important requires that I was asked to solve are:
1. Hand the business the source files so that in the future, they can potentially hand the files to a new team for editing. - I don't think this fundamental ability is available in Rise 360!
2. Localize the training in multiple languages. But now I learn that Rise 360 exports to a nearly 10-year old xlf 1.2 specification. :( And translation tools like DeepL require xlf 2.1, which is a fundamentally different spec.
Judging by other requests, it appears that Articulate won't update their output anytime soon.
******
But I may be able to help the community. A few years back, I created an xlf parser which I may be able to modify as a bi-directional converter.
The caveat is that I say this without knowing anything about the Articulate implementation of xlf 1.2. Additionally, while it's relatively trivial to convert 1.2 to 2.1, there are no equivalent elements when converting back to 1.2 for import into Articulate. Therefore, it is possible to encounter data loss.
If I was able to accomplish this task, such an application auto-sense the xlf version then automatically convert one or more files to the other format. At some future point, it would be cool to understand DeepL's API endpoints and perform direct translations... saving another step. But that just a distant future thought.
I'm just thinking out loud right now, but I am curious if others might be interested if I proceed with such an endeavour. I'd do it for free as my introduction to this community. :)Commenting to join the others in showing that there is demand for updating Rise to support XLIFF 2.1. This should be escalated in the roadmap considering how old 1.2 is.
We also urgently need the support of XLIFF 2.1. When can this be expected?
Please we need Rise to support XLIFF 2.1 !!!!
Hello,
+1 to have a clean XLIFF in the good version to translate it with DEEPL.
ACOLAD company developped an interface similar to DEEPL that translate Articulate XLIFF. I tested it with Rise XLIFF and it's work well. You must contact an Acolad contact to have access to the application because it's not available from website. https://www.acolad.com/fr.html
DEEPL good points : Intuitive, respect RGPD, no to expensive => very important criteria because people using RISE are business expert and not IT expert nor instructional designer. And it is the target of Rise and argument. Then XLIFF extrated from RISE must work in a tool dedicated to this same target (intuitive too) => ACOLAD have similar propreties.
An other solution for Articulate could be : propose an add on to connect Deepl API key to Articulate account to propose the translation uploaded in RISE directly.
The structure of the XLIFF from Articulate is not terrible : according to my IT, there is no <closing tag>. You know the tag is closed when you see the next <opening tag>.
Hope Articulate will be able to give us a planning for the upgrade as soon as possible !
