Translation workflow for Rise

Nov 06, 2018

Hi, we are just starting our adventure with Rise and we love the software. We create a lot of courses and most of them are translated into multiple languages. We are currently building our first course in Rise - to be translated in Q1 2019.

Can anybody share their best practices on how to share the source files with external translation company? Can we set some sort of common space to store final English versions and then duplicate these for language versions? Is there a way to limit access to these so that the final files are safe and we know that the translated xliff will match? Can you mark file versions without changing the course title? (e.g. with language code and version?)

I understand the process of course duplication: and using folders to store versions I am looking for some more insight from teams who develop and translate courses on a bigger scale. Thanks!  

27 Replies
Yasuyo Kitano


I am also trying to establish a collaboration process with our localization vendors on Rise courses. I also understand how to translate the course (duplicate a course, export XLIFF, translate XLIFF, import it back to the duplicated course). 
But I would like to know what options we have in terms of handing off course content for localization. I understand we need to share it as a collaborator, if we want them to edit the content, but if they are not in the same team, how can we make them a collaborator?
Or any other way to collaborate with localization vendors?


Allison LaMotte

Hi Ewa,

I think the best way to do this is to actually change the file names (which won't impact the ability to import them). For example:

  • Course_Name_EN (for English)
  • Course_Name_FR (for French)
  • Etc.

You could share these files with your translator vendor via a shared server or just email them the files and add them to your server when they're done.

Jakub Lelek

This would be good but unfortunately changing the file name is equal to changing its title that is visible once the course is published.  I suppose that splitting the course title and the file name into two separate variables would solve the problem. It’s a shame that RISE does not support this functionality yet. 

Yasuyo Kitano

I think so far the following process makes most sense for our team and vendor who both have Articulate 360 subscription.

1. Create a copy for each target language (add the language in the course name). For instance, if we localize into Japanese, French, and Spanish, we will have 3 copies.

2. Send a copy to our vendor (

3. Our vendor exports .xlf file, translate it, and import it to Rise, translate labels, adjust format accordingly, do QA, and return the localized copies back to me. 

Here, I would like to clarify... When I create two copies from the same course, Copy A and Copy B. The .xlf file exported from Copy A cannot be imported into Copy B, correct?

Thank you,




Donna Westwood

Hi Crystal,

Thanks, I know how to do the translation - this is more about organising my files and preventing mishaps!

I will be translating 34 courses into 8 languages = so 272 courses total created... As you can tell this is a big project so I want to get my process nice and tidy before I start, and was hoping for some best practices from the community.

We are sending Xliffs to the translation provider and importing them back in.

I really wish Rise had a tagging feature for organising course files as well - that would certainly help...


Miguel van den Branden

Hello, my translation partner also asks about the source language settings (source-language="en-US"). Are there any updates about this request?

This was the feedback of the translation company after sending them the translation file:

A small note, we see that the .xlf file has source language en-US. We had to change this to nl-NL (the language codes are also read in by our software); would it be possible to change that in a subsequent file?

Alyssa Gomez

Hello, Miguel!

While we can't provide support for modified published output, you can try changing the language attribute from EN to NL in the index.html file, saving the file, and then uploading the edited package back to your web server or LMS.

Also, be sure you translate your label set in Rise 360 before exporting the file. Here's how to do that!

Jigsaw Learning

We have requested this feature on another thread. Tagging course features would be useful, but we would also like a standard file organisation structure which would physically move RISE courses into different locations – the current 'smart folder' layout makes version control and archiving very difficult.