Forum Discussion
Problem with exporting XLIFF file for translation from Rise
A big +1 from me on including XLIFF 2.1 export.
However, I have been successfully using DeepL Pro to translate Rise courses by utilizing the DeepL CAT plugin in MemoQ Translator Pro, translation management/editing software.
All of my content is highly technical, so the AI translation frequently needs significant "massaging" from my internal Subject Matter Experts.
The workflow goes as follows:
- Duplicate course in Rise - Tag new course with appropriate language ID
- Export XLIFF from Rise course
- Import XLIFF into MemoQ
- Use MemoQ "Pre-Translation" feature with DeepL CAT integration to do the initial translation
- Export 2-column Word doc (original segments and translated segments) for SME Review
- Import SME-edited Word doc back into MemoQ
- Export translated XLIFF from MemoQ
- Import XLIFF into Rise course
- Publish Rise course to Review360 (or just preview link) for SME on-screen/formatting review (especially important for non-Roman character languages like Chinese)
MemoQ maintains a translation memory database with the edits, and you can still use glossary files with DeepL - it's been pretty reliable, although it's a lot of careful, detail-oriented work. MemoQ is pretty cheap, at 360 Euro / $400 a year.
The new integrated translation feature that's coming in Rise looks pretty good, and would eliminate a lot of the "extra" file-management labor in the process. The one killer feature that is currently missing is making the translations integral to the course in Rise - currently, when you publish the translated courses, they all end up as separate packages. It would be awesome to have the option to have a language selector in the cover page, or as a menu item within the course itself - since a lot of LMS platforms are super-difficult with properly displaying translated courses.
Related Content
- 7 months ago
- 6 months ago
- 7 months ago