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"
In some cases, you may find that translating Articulate Storyline content via XML Localization Interchange File Format (XLIFF) doesn't work as expected. You may receive a successful (congratulations) message but find that your course is still in the original language. See this article for more information.
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!
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!
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.
Hi there German, thanks for letting us know what's happening. Could you share your original .story file and the translation file with us by clicking here? I'd like our Support Engineers to take a closer look. Thanks!
Was there ever a resolution for this? I've just continued using the Word doc option for translations and haven't had time to troubleshoot this. But, it's coming back to haunt me now, and I wondered if there was a fix? Thanks?
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?
HI I am also having the same issues. My XLIFF file was returned from translation as XLF file. When I import it back in, it removes all text an leaves slide blank of text. This is for translating from English to French (CDN)
Thank you for reaching out and I am sorry that you are hitting this snag.
I see that you are in good hands with our Support Engineer, Anna! While Anna continues to investigate, please let us know if you have any additional questions!
Please ensure that the imported file has the same name as the exported file. Here, I observe that you have created a copy of the original Xliff file. I hope that should work.
I am currently trialling Articulate and trying to translate a story file using the XLF File. I am also getting a congratulations message but no new language.
19 Replies
Welcome to Heroes, Heidi!
Just to be sure, can you confirm that you followed the steps as outlined in this tutorial and the below Screenr?:
Heidi, out of curiosity, what are you using to translate Storyline generated .xliff files?
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"
Heidi, did you ever find an answer to this problem?
I'm having the same issue with Storyline 2, was a fix for this ever found?
Hi Lauren!
In some cases, you may find that translating Articulate Storyline content via XML Localization Interchange File Format (XLIFF) doesn't work as expected. You may receive a successful (congratulations) message but find that your course is still in the original language. See this article for more information.
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!
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!
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.
Hi there German, thanks for letting us know what's happening. Could you share your original .story file and the translation file with us by clicking here? I'd like our Support Engineers to take a closer look. Thanks!
I already sent to Support through a separate ticket opened a couple o months ago for this issue.
Dr. Germán Basterra [cid:image001.png@01D2F740.69849570] I [cid:image002.png@01D2F740.69849570] <https://thenest.my.salesforce.com/
Thanks for letting us know German.
It looks like you've recently been in touch with Abel in your case as well :) You're in good hands.
Looks like your email signature came through when you replied via email! You can remove that if needed - quick Peek video here if you need help.
Was there ever a resolution for this? I've just continued using the Word doc option for translations and haven't had time to troubleshoot this. But, it's coming back to haunt me now, and I wondered if there was a fix? Thanks?
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?
HI I am also having the same issues. My XLIFF file was returned from translation as XLF file. When I import it back in, it removes all text an leaves slide blank of text. This is for translating from English to French (CDN)
Here is the fle returned from translation.
Hey Sally,
Thank you for reaching out and I am sorry that you are hitting this snag.
I see that you are in good hands with our Support Engineer, Anna! While Anna continues to investigate, please let us know if you have any additional questions!
Please ensure that the imported file has the same name as the exported file. Here, I observe that you have created a copy of the original Xliff file. I hope that should work.
I am currently trialling Articulate and trying to translate a story file using the XLF File. I am also getting a congratulations message but no new language.
James
Hi James,
So sorry you ran into a snag during the import process in Storyline. A few questions and thoughts to start us off:
This post was removed by the author
This discussion is closed. You can start a new discussion or contact Articulate Support.