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.
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
Hi Cameron,
I appreciate you reaching out and sharing those details with us.
I've opened up a support case on your behalf so that our team can take a look.
Hi Leslie,
We are having the same issue, with all of the paragraph markings making it practically unusable in Trados.
A simple Word Document download would be appreciated.
Thank you
Hi Leslie,
Did you manage to solve the issue with the XLIFF flies not working in Trados? I've just been told by a translations company that they are also seeing the tags and so can't use the file I sent them.
Any advice on this would be very welcome - we're planning translations into several languages and need a smooth process.
Many thanks,
ToveHi Tove,
Our team is still working on this issue, so we'll let you know as soon as we have more info.
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.
Hello James,
Are you looking for a translation tool? We shared this example in our documentation here.
I tried using this tool as well, but all the boxes are showing up blank with nothing to translate?
This is huge for me. I've been waiting such a long time for this, I need to do multiple translations of every piece of work and it has been painful up until now.
Thanks for delivering! It really makes a big difference to a lot of us out here working with translations.
So glad to hear it's helping you Simon! Please let us know if you need anything else!
YAY!!!! So excited to hear this!!!! We've been waiting to dig into Rise until this feature became available :) Thank you!!!
Great news!
Hi Ashley,
Similar to Cameron I have exported the XLIFF document from my courses and sent them to a pro translation company. They have asked if it is at all possible to receive XLIFF 2.0 (in UTF-8/unicode) where no HTML entities display in XLIFF?
They think there could be a way of working with the current format but the issues they foresee are as follows:
• We can only leverage per <target></target> tag pair, rather than per sentence. This means that you are potentially getting less leverage from the previous TM.
• We would end up with mixture of normal characters (in the newly translated section) and HTML entities (leverage from the previous version).
• File processing will take longer as the process is more complex.Any ideas?
Hi Ivor,
Thanks for reaching out and sharing those details. It sounds similar to an issue we have reported regarding HTML tags.
I'm adding this conversation to the report as we track user impact and so that we can update you here when we can.
