Translation workflow for Rise

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: https://community.articulate.com/articles/rise-translate-your-course and using folders to store versions https://community.articulate.com/articles/rise-using-your-dashboard-to-manage-courses. I am looking for some more insight from teams who develop and translate courses on a bigger scale. Thanks!  

10 Replies
Yasuyo Kitano

+1

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?

Thanks!

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 (https://articulate.com/support/article/Rise-How-to-Send-a-Copy-of-a-Course-to-Another-Author).

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,

Yas