Forum Discussion
NEW in Rise: Export for Translation
If you need to create courses in multiple languages, you’re going to love this new Rise feature. It allows you to export your course text to an XLIFF file* and then reimport it once it’s been translated. Like magic: all your text is replaced by the translated text. It’s that easy!
*XLIFF files are a translation industry standard, so if you’re working with professional translators, then you shouldn’t have any issues. But what if the translations are being done by a fellow coworker or friend? No problem! If you do a quick Google search, you’ll find a ton of free tools that allow you to easily edit XLIFF files.
I’m so happy I want to cry! Great job!
Found this online editor for exliff files
Seems to work fine, but requires a twitter account
Hello - the XLIFF implementation seems to be crippled when using translation software like Trados. Translatable text is displayed along with tags as opposed to filtering out tags.
Here is what I was told by Trados:
"This is not a correct XLIFF. The best way to deal with it would be creating an XML file type with embedded content.
For the XML file type set //* to not translatable and //target to always translatable. Enable "Paragraph" as structure info for //target, set both //* and //target as structure elements.
In the embedded content part use CDATA and Paragraph as those parts, where tags are to be parsed and chose HTML 5 as parser. This way you will have a clean file as it should be."
Can this be looked at/implemented? Trados is an industry standard so compatibility is very important for us.Thank you Cameron for your comment! Our translation team cannot open the XLIFF file or if it does open, it's almost impossible to read with all the tags--very frustrating. Our department uses Trados. Rise support suggested using free web editors, but long term, we can't rely on that solution.
@Cameron Campbell
SDL Trados is correct. The implementation is poorly done. The XLIFF exported by Rise is equally problematic in memoQ (for whom I work). This has created issues with one of our best customers. The Rise developers apparently failed to realize that many professional translators and Rise customers use translation tools like SDL Trados and memoQ. In failing to understand this and implement usable XLIFF export, they have shot themselves in the foot.I would be happy to work with your developers to show them the problem. If this can be fixed, it would benefit our mutual customer.
Richard Sikes
Solution Architect, memoQ
Warning : a critical issue seems to be unsolved and make Articulate Rise unusable for multilingual contents. See here : https://community.articulate.com/discussions/rise-360/xlif-problems
I wish I'd known before choosing Rise for a project in 15 languages...
Hi Julien,
I'm sorry this issue is causing so much trouble for you. We're looking into it and will share any updates here. Since you're subscribed, you'll be automatically notified.
In the meantime, if there's anything else I can do to help, please let me know!
Why are you not implementing the same feature via word as available in Storyline? Frankly speaking the xliff method is not easy and it forces to go to a professional translator. I found various tools but it is a nightmare to use them.
Great work, Articulate team. This is so timely for us. Thanks and keep the updates coming.
Which Windows program do I need to open the XLIFF file? I found Omega T as a free service for uploading the XLIFF file into to work on the translation, but I can't figure out what program to use to open the actual XLIFF file. Can you please walk someone who's not tech savvy through on how to use this translation feature? Thanks.
Thanks, Irina. That seems to be the same across a few users so I'll keep you posted here when there is an update from the team.
Am I the only one who feels that the bugs and problems reported on this forum systematically seem to be answered by bots? Always the same answer "we will forward to our support", under the understanding that with a little luck a member of the community will bring free solutions. Hey Articulate, your product is a commercial product that you sell expensive, your customers are entitled to get concrete answers to the problems that your product imposes on them. A bug is not a request for functionality to prioritize according to your development backlogs, they are problems to solve all the more quickly as they are blocking for YOUR CLIENTS!!!! The problem described above by Julien has been lying around for months on your forum and has still not been solved. It involves very high manual intervention costs, and for any answer Articulate answers "we are looking into it"??? It's not serious and personally I wonder if we can really continue to recommend Articulate to our customers. Other solutions exist on the market and offer serious support. It would be time for Articulate to rebalance their staff between marketing and developers. The latter must not be very numerous....
BR
a customer for many years but who is at the end of his patienceHi Sven,
No you are not the only one. The issues that Articulate have introduced with the supposed improvement to the translation feature have resulted in a massive amount of manual work for us and a huge translation bill due to previously built-up translation memory being more or less rendered useless.
We've had to give up on the translation feature and gone back to manually duplicating the courses and applying translation section by section.
We are already now looking to move away from Articulate altogether which is a real shame as we've invested a lot of time into the products over the years but the recent issues seem to suggest that they are completely detached from the pressures being experienced in the field.
Thanks,
Matt
Hi Amy! Correct, the XLIFF file should show the source language and the target language of the course.
