XLIFF Import Issue

Jan 02, 2013

While importing XLIFF with localized content back into Storyline we are seeing that the file imports. But the localized content does not appear.

It simply pulls the English content back into the file.

Is there some specific that needs to do be done in either exporting the XLIFF from Storyline or in updating the target text?

Thank you!

19 Replies
Heidi  H

Hi Peter, yes we have.

We are able to import word documents without issue.

The XLIFF file is not importing the translated content. We thought it might be characters in the translation but it is not because we tried using the English content in the Target code and slightly modifying it. It still only imports the English content - source xml:lang="en-US"

Brigitte Cahill

Hello -

This is the first time I'm attempting to import a French translation into my Storyline 360 file using an .xliff format instead of a Word doc format. Problem: I attempt to import the translated .xliff file into Storyline 360 and I get no error, says the import is complete, but nothing in my SL file is translated. All is still English. I've read the article above, and did what my translator suggested: delete all instances of approved="no" in the translated .xliff file. But the import still does not work. The .xliff file the translator sent to me is attached. (Note: they sent back an .xlf file, and I had to change format back to .xliff for SL to recognize it. Not sure if this matters.) Any ideas?? Thanks!

Ashley Terwilliger-Pollard

Hi Brigitte,

Are they able to make the changes in the correct file format? I wonder if something did change when they changed it to an .XLF? You could test the same thing by using your original export copy and make a few changes yourself to import back in ( I'd do it on a duplicate of your .story file). 

Let me know if that doesn't change what you're seeing - and we'll want to take a look at your original .story file too! 

German Basterra

I have had similar problems with Xliff export/import both with the first Storyline 36o and with the latest upgrade launched about one month ago. I find that the xliff export generates a tag where German appears as the source language, even though the source is English. I have tried with Trados and the MadCap Lingo translation editors. I am able to translate with both but not able to import back the translation.

Leslie McKerchie

Hi Brigitte,

I scrolled up to see what you originally reported and it seems that you were experiencing this error:

You may receive a successful (congratulations) message but find that your course is still in the original language.

This was an issue we had reported for Storyline 2, but I do not see a report of this for Storyline 360. Were you ever able to work with your translation team using the correct file format as Ashley mentioned above?

Katie Riggio

Hi James,

So sorry you ran into a snag during the import process in Storyline. A few questions and thoughts to start us off:

  • Saving to a shared drive can cause strange behavior like this. Let's make sure that both files are saved to a local c: drive.
  • What translation tool are you using?
  • Are you comfortable with sharing the .story file and translated document with us for testing? You can use this secure upload link.

This discussion is closed. You can start a new discussion or contact Articulate Support.