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.
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:
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...
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.
No unfortunately, we just switched to the Word format and didn't try it again ever since. Not all Storyline were causing this issue either. Pretty weird!
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!
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.
Hello, I am also having issues with the XLIFF file import. I've sent the file to our translators and they sent back the translated content. When I import back into Storyline360, all my text disappears and the slides have no text whatsoever. What are we doing wrong?
I am getting this error msg when I try to export to an XLIFF file that windows couold not find a program to open the file format. I dont want to open it on my machine, I just want to email it to our translators....
Hi Lauren, I currently have a ticket open with Anna from articulate. For some reason, when I try to export in XLIFF format, windows tries to open the file in Adobe!!!! I have attached a screenshot below.
Once I get the file back from translators, the translated file that I import back removes all text from the slides. Anna suggested trying a different translation tool such as Smartcat but now instead of having no text, it returns the English text with no translation and with some text missing from certain shapes.
Can you explain a bit more about what you're experiencing? It looks like you've exported your course for translation into an XLF file and need to get it translated to import back into your course.
Here are some detailed steps about exporting a file to XLIFF and what to do with it:
XLIFF is a file format commonly used for translation services and computer programs. When the translation is ready, import the Word document or XLIFF file back into Storyline
Let us know if you are running into issues re-importing, and we'll go from there!
While exporting into XLIFF, it gives error of variance in project version and storyline version (in which the project is being opened) - while both are SAME 3.53.25436.0.
Thanks for reaching out and sharing the helpful screenshot. I'm sorry to hear you're hitting this snag!
From here, I'd recommend connecting with one of our support engineers so they can help determine why you see this error, then they will reach out with the next step!
44 Replies
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.
Hello Cynthia dit you find a solution to this problem?
Hello,
No unfortunately, we just switched to the Word format and didn't try it again ever since. Not all Storyline were causing this issue either. Pretty weird!
Thank you for the answer this is really strange.
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 Cynthia,
did you get any solution for this issue? Because we have exactly the same Problem...
Thank you!
Hi Nathalie,
Unfortunately no. We just switched to .doc after that and never tried Xliff again. Sorry I can't help.
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.
Hello, I am also having issues with the XLIFF file import. I've sent the file to our translators and they sent back the translated content. When I import back into Storyline360, all my text disappears and the slides have no text whatsoever. What are we doing wrong?
Thank you for your help.
I am getting this error msg when I try to export to an XLIFF file that windows couold not find a program to open the file format. I dont want to open it on my machine, I just want to email it to our translators....
Hello Sally!
Sorry you're running into this! Can you confirm that you've imported the XLIFF file the same way this article states?
Could you also share a screenshot of the error message? That will help us get a better understanding.
Hi Lauren, I currently have a ticket open with Anna from articulate. For some reason, when I try to export in XLIFF format, windows tries to open the file in Adobe!!!! I have attached a screenshot below.
Once I get the file back from translators, the translated file that I import back removes all text from the slides. Anna suggested trying a different translation tool such as Smartcat but now instead of having no text, it returns the English text with no translation and with some text missing from certain shapes.
Hi Sally,
Thanks for letting us know that you are working with Anna directly.
I shared your additional comments with her in your case :)
Help,
I export out using the correct steps. Says successful and nothing changes. Please help. I have uploaded both files
Hi Digital,
Can you explain a bit more about what you're experiencing? It looks like you've exported your course for translation into an XLF file and need to get it translated to import back into your course.
Here are some detailed steps about exporting a file to XLIFF and what to do with it:
Storyline 360: Translating Courses
Let us know if you are running into issues re-importing, and we'll go from there!
This post was removed by the author
Hi,
While exporting into XLIFF, it gives error of variance in project version and storyline version (in which the project is being opened) - while both are SAME 3.53.25436.0.
Screenshot is attached for reference.
Requesting a prompt support!
Many thanks
Hi Manuela,
Thanks for reaching out and sharing the helpful screenshot. I'm sorry to hear you're hitting this snag!
From here, I'd recommend connecting with one of our support engineers so they can help determine why you see this error, then they will reach out with the next step!