Issues with translating using XLIFF file

Hi Everyone, 

We have hit a major stumbling block with translating Storyline 360 courses  to the point where we won't be able to use Articulate for developing our courses unless we can get this resolved. Our courses need to be translated into approx. 30 languages and we use native speakers for translation. The Word version is not an option so we have to use the XLIFF process. The process that we have used which works fine with other authoring tools is as follows: 

  • Export the XLIFF file
  • We have a Java program that converts the XLIFF content into a spreadsheet that we share with translators
  • Another Java program converts it back into the XLIFF file 
  • We then import the translated XLIFF file back into Articulate and manually fix any text formatting required.

This works just fine with Captivate and HTML courses but when we try it with Articulate it says import successful but nothing has changed, it just has the original English version. 

We've been in contact with Articulate support but they told us it was out of scope so I'm putting it out here in case anyone has had similar issues and can offer any ideas on how we can work around this. 

Thanks everyone!

6 Replies
Thor Melicher

Lots to unwrap here but let's start with some simple checks:

1. Look at your translated XLIFF file - does it have any TARGET elements?  If you only have SOURCE elements that are translated, this could explain why you're getting the successful import but no translations.

2. Which XLIFF type are you using, 1.2 or 2.0?  In my experience, the 2.0 standard is more closely adhered to by Storyline 360 than 1.2.  This is mostly formatting but once you get the translation part working, this could potentially cause problems.

3. Start with a 1 to 2 slide course and then go through your process.  See if you can get a successful import.  It's a bit tedious but it will be quicker to determine where the problem might be.

Last insight - Storyline 360 does 'double-duty' with XLIFF files.  Not only do they use it for translating but also for placement (font, position, size, color, etc.)  An ingenious solution but it does make it a tad more difficult to get a properly formatted XLIFF file.

I hope that helps as a starter.  Feel free to post what you learn.

Thor

Mary T. Collins

We've had some trouble identifying where we're going wrong with this. 

I have created a one slide project with one text element (Hello World) as a test for this. Here is the .xlf File

 

<?xml version="1.0" encoding="utf-8"?><xliff srcLang="en-US" version="2.0" xml:space="preserve" xmlns="urn:oasis:names:tc:xliff:document:2.0"><file canResegment="no" id="Hello_x0020_World"><unit canResegment="no" id="65Dv4wdOu5h.Name" type="Articulate:PlainText"><segment canResegment="no"><source>Untitled Scene</source></segment></unit><unit canResegment="no" id="5zwlYb9VHtI" type="Articulate:DocumentState"><segment canResegment="no"><source><pc id="block_0"><pc id="span_1">Hello World</pc></pc></source></segment></unit><unit canResegment="no" id="6pMh8dnWnBS.Name" type="Articulate:PlainText"><segment canResegment="no"><source>Untitled Slide</source></segment></unit><unit canResegment="no" id="5v92wk0lwK7.Name" type="Articulate:PlainText"><segment canResegment="no"><source>Question Bank 1</source></segment></unit><unit canResegment="no" id="ProjectTitle.Title" type="Articulate:PlainText"><segment canResegment="no"><source>Hello World</source></segment></unit><unit canResegment="no" id="5ih9dSuLXeV.Name" type="Articulate:PlainText"><segment canResegment="no"><source>1 Untitled Scene</source></segment></unit><unit canResegment="no" id="5tQZNbkgYdN.Name" type="Articulate:PlainText"><segment canResegment="no"><source>1.1 Untitled Slide</source></segment></unit></file></xliff>

 

I wish to translate the text "Hello World" in the above to

"Salut tout le monde". 

Would it be possible for you to return me the edited .xlf that will achieve this?