Translation XLIFF format

how to fix it?

Hi Raymond and welcome to E-Learning Heroes! Looks like we got some duplicate posts from the pause in moderation

I'm not sure if Michael is subscribed to this thread, so you may want to reach out to him via Private Message.

could you tell me how to fix it？

Hi Raymond,

I looked into Michael's case, and saw Cleo shared his troubleshooting steps was to systematically import the slides per scene from the old file. After each scene import, he then exported the translation to .XLIFF. It seems that there were two particular scenes that were causing a crash, and causing a corruption issue that once it's been imported into Storyline could not be removed. So Cleo suggested that Michael work with those specific scenes to see what was causing the corruption. 

Hi everyone! 

I know it's an old thread and I should probably create a new one (because I couldn't find one that answers my question).

I'm having trouble importing the XLIFF file back into our Storyline Project (360). I don't think the issue is on our translator side, because I just tried importing the export right from Storyline and I always get the same issue, this popup : 

then this one, but nothing is going on :


What are we doing wrong? We tried on 3 different computers and we always get the same result. We are supposed to be able to fast track our process using these files, but now they are no good for us... Will we have to ask our translator to repeat the process with the .doc files (extra charge for us) or is there a way to get the XLIFF to work?

Thanks for the help!

Hi Cynthia, 

Have you already confirmed that the files are saved and being imported from a local source? Working off a network/shared drive is known to cause some odd issues with importing files into a project, so I'd definitely start there. Take a look at these tips on working locally and ensuring that the file name/path is also within the specifications set by Microsoft. 

Another thing to check is that you're using the latest update of Storyline 360, we're now on update 12. If you use the "Check for Updates" from the desktop tray application that'll check and start the update installation for you. 

Also, if you're seeing that error message in Storyline for a number of projects, and are on the latest update you could also look at the repair options. 

Hi Ashley,

Yes we are working locally and don't have any special characters in name/path.
See what I did here, I just exported it and tried reimporting it and it doesn't work:

https://360.articulate.com/review/content/f420f48d-ade4-492d-89f5-9d07389f88fb/review

the .doc format is working fine, but our translators would prefer working with a Xliff file.

I have the latest update installed.

If all else fails, I'll resintall the program, in a less busy period. As I said, we tried on multiple computers, so I'd be surprised that all of our computers have the same issue... 

thank you!

Hi Cynthia,

Thanks for that video -it all looked normal to me as well, although I did wonder if you could try with a much shorter file path? Look to see if those files on your desktop provide the same error message. It's at least one more thing to rule out!  

Do you also see the same error message if you attempt to import a .xliff file that you made changes too (not the one your translators used)? I'm wondering if something happened to a file on their end. Even trying to import in the same file you exported would be a good step. 

If those ideas above and the repair don't resolve it, I'll definitely want to have you work with our Support Engineers! They can test out some copies of your files to see what else they could spot which would cause such an error. 

Hi Learning Agency,

If you're running into the same issue, I'd like to have our Support Team take a look. Can you share a copy of the .story file and your XLIFF file with us by uploading it here?

Let me know and I can follow along as you work with the team! 

Hi Nathalie,

If you're stuck we're happy to do some additional troubleshooting with you too - reach out to our Support Team here and they'll talk a look at what's going on! If we can narrow it down further, I'll be sure to share any updates here in ELH.