Rise 360, part of the Articulate 360 package, is a web-based app for authoring online courses.
After we were asked to translate a course created with it, we learned that it can export and import xliff files. Great, we thought, just the ticket. But later when we started processing the xliffs, we discovered that things were not quite as rosy as we’d hoped.
The way that the xliff files are structured creates segmentation issues (problems with the breakdown of the source text into smaller units for translation). One aspect of this is that <g> tags masking html paragraph tags are used throughout the translatable text. Ideally these structural parts of the file should be hidden for editing, but because <g> tags are normally used for formatting in xliff files, they are not:
![]()
Here the inner <g> tags indicating bold should be visible, but the outer ones should not.
This unnecessarily large number of tags makes the job of translators and reviewers working on the text more difficult, and potentially causes confusion and problems further down the line. It also makes cross-referencing between similar text items more difficult.
However, we are happy to report that, after some R&D, we now have an automated solution which deals with the segmentation issues and keeps unnecessary tags out of the translatable text. Problem solved! That certainly keeps the translators happy – and makes the process more transparent for everyone.
So feel free to contact us if you have any Articulate Rise 360 courses you need translated. You can be sure we’ll make the process efficient for all involved.
