Translation workflow for Rise

+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!

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.

Hi Yasuyo,

Collaborators don't necessarily need to be part of your team, they just need to have an Articulate 360 Teams subscription. To add them, simply enter their email address in the Add Collaborator field.

Let me know if you have any trouble getting this to work!

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. 

I see what you mean, Jakub. Another option would be to create folders for each language, so the folders could have the language name without impacting the name of the title.

Hopefully, this solution will work for you!

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

I'm glad you found a system!

And yes, that is correct, Yasuyo. You have to import the xliff file into the same course you exported it from.

Thank you so much for sharing your best practices! This is very useful! 

Hi Yasuko,

What kind of format adjustment do you still need to do? It seems to me that RISE does not require any of it.

Ewa

It seems that the source language in the exported XLF file is always set to en-US. I can't find a setting to change this?

source-language="en-US">

Hi Lärbyrån,

Unfortunately, there's not currently a way to change that. Would you be up for logging a feature request to tell us more about your specific needs?

In the meantime, if there’s anything else I can do to help, please let me know! 

following - still not sure on a great process - anyone else have anything to add?

Hi Donna! Share some specifics about your translation projects: How many courses and languages are you tackling? How do you think you'll be sharing files with your translation provider?

Just for reference, here's our tutorial on translating Rise 360 content.

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...

Thanks!

Hey Donna! I'd love to hear more about your tagging feature idea. What kinds of tags would you use? Where would you want to insert the tag?

Hello Allison,

do you have any updates concerning the problem that you cannot change the source language (source-language="en-US")? I have been searching the discussions for quite some time now and couldn't find an answer.

Thanks,
Max

Hi there, Max. The source language will still default to English for now. We'll monitor this request and let you know if we make a change. 

Okay. Thanks for the quick answer!

I am following this topic. We are looking at translating more than 100 courses to 15 different languages. And the duplicating of classes to work with the identifiers as some of you mentioned above is a bit of a pain. Has anyone tried Crowdin with Rise exported files? 

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?

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!

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.

Thanks for those thoughts, Jigsaw. We're tracking requests for folder enhancements, and I can let you know if we make any changes that will help. 

When we export files for translation, for some reason <g> tags are also included in the strings. 

Example:

<g id="hnXh8TsnC8mg_kuL" ctype="x-html-p">Herzlich willkommen zur Datenschutz-Schulung!</g>