Rise 360 - Default English US when exporting XLIFF

Mar 30, 2020

Hello lovely Articulate community, 

Out team has recently started using Rise to try and expedite the creation of course content for our users. We translate into 15 languages and have a dedicated translations team that imports the files for us into Trados Studio. They are the ones that have noted that the exported XLIFF files are set to source language "en-us" which sadly is a bit of an issue for us, since being based in the UK, all of our translation materials are in "en-uk" as source language, meaning that the files exported from RISE cannot be used for translations. This is less of an issue with labels as those can be created as a custom set, but it would be good to know if there is a similar option for exporting the course as xliff. 

Is there a way to change the default source language in RISE when exporting a course? 

What if a course is created in a different language to begin with, e.g. German? Would the default language of the first course still be set to "en-us" when exporting?

I know xliff flies can be edited with editors such as Note++ but our translations team do not want us to mess with the files directly.

Any and all help is much appreciated.

8 Replies
Alyssa Gomez

Hello, Johanna!

Thanks so much for sharing how this is impacting your team. I can see how not having the ability to change the original source language in the translation options is a roadblock for you. I'll share your thoughts with our team, and we'll keep our eyes out for similar feature requests! 

Thor Melicher

The XLIFF file is text based so you can open it and then change the Source Language to match your course before you send it on.

You should see something like this when you open the XLIFF in the first line:

<xliff xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 http://docs.oasis-open.org/xliff/v1.2/os/xliff-core-1.2-strict.xsd" xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xhtml="http://www.w3.org/1999/xhtml" version="1.2">
<file original="course" datatype="plaintext" source-language="en-US">

Swap out the "en-US" for the language that the course is actually in and then you should be good to go.  I would recommend using an application such as Notepad rather than MS-Word to keep any extra 'interpretation' by MS-Word slipping in.

Hope that helps!