Forum Discussion
- FelixFrankeCommunity Member
I am still failing to understand why we cannot have a Word Export similar to what we can export from Storyline (or even Excel, for that matter).
It would make so many people's lives so much easier...
- SarahMorrison-7Community Member
We would also love to see XLIFF 2.0. We use DeepL and their requirements are 2.0/2.1.
- DavidArndt-507aCommunity Member
I'd also be interested in seeing XLIFF 2.0/2.1 export options. XLIFF 2.0 has been around for almost 10 years now.
I'm especially interested as DeepL only support XLIFF 2.1.
Cheers,
David- TobiasBrckmannCommunity Member
Same for us. Our company needs an update to 2.1 due to DeepL requirements. Are there any plans today for replacing your 15 year-old version?
Hi Tobias!
While XLIFF 2.0/2.1 support in Rise 360 isn't on the Roadmap yet, we're currently tracking requests for this feature. We'll keep this thread posted for any updates on this feature request.
- TerryHadawayCommunity Member
We are also struggling with this, I have 30 Rise modules to convert and we use DeepL. DeepL will only accept version 2.1 and Rise exports xliff in 1.2. There are many authoring programs already using 2.0, 2.1 etc. When will this be an option for us in Rise?
- jacobMllerCommunity Member
one more for either a XLF update or even better do the same as you do for storyline, a word doc
- FelixFrankeCommunity Member
We are now in 2024 and no effort has been done by articulate to implement xliff 2.1 (because 2.0 is already outdated). Unbeliebable!
Hi Nancy,
Thanks for bringing this up! While we don't have plans to update to export XLIFF 2.0 right now, I'll certainly bring this up to my team!
- MarcoPoggiCommunity Member
So, 4 years later...???
- FelixFrankeCommunity Member
Hi, is there any news on this?
In the forum there are not many recent threads about xliff but it is a very active topic for us at the moment.
Thx
- DavidArndt-507aCommunity Member
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. - ThorstenBreidbaCommunity Member
Hello at all,
we also need XLIFF 2.1 to translate the files directly with DeepL. At the moment we use OmegaT with an Okapi Plugin and a DeepL API to translate the files semi-automatic but this is not a nice workaround. Please develop an export for XLIFF 2.1 or another export file like .xlsx or .docx so that we can directly use DeepL for translation.