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 transl...
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
