Forum Discussion
Issues importing Korean translation
I'm using Storyline 2 and have successfully imported several languages into Storyline to create the translated version of my learning. But whenever I try to import the Korean language, I received the following error message:
Not a valid Word doc
I've tried to re-create the Word document; I've asked the translation vendor for a different document, but nothing seems to work. Any ideas?
Hi there, Tara! For translation, you'll need to use Microsoft Word 2007 or later (32-bit or 64-bit). That's the first thing I would check!
If the Word version isn't the culprit, we're happy to have a look at your original .story file. You can attach it to this discussion. I did a quick test with Korean text, and it allowed the Word doc to import.
Let me know!
Please find attached the .story file and the Word document for that we are to use. The file is Microsoft Word 2016, but there is definitely something odd about the file and I cannot figure out what it is. Please have a look and let me know what you find.
Thanks, Tara!
It looks like you're trying to import a .docx Word Document. Instead, you'll want to use a .doc Word document. You can read more about the document files types here.
After changing the file type in Word, I was able to successfully import the translation into Storyline 2.
Try importing the attached document, and let me know how it goes!
Hi Alyssa,
I see your reply above is from over a year ago. My question is whether Articulate plans to enable .docx files to be acceptable file types for the translation import in Storyline 360 any time soon? Since .docx is the newer version of word docs, our translators currently face an extra step in saving the .docx file they translate into a .doc file for Storyline which is a bit time consuming.
Please let me know if anyone is working on adding .docx as an accepted format.
Thanks,
Jen
Hi Alyssa,
Thank you for helping me! I used the file and successfully imported the file; however I could not preview any of the translated slides , I receive an error message apologies that something went wrong with Articulate Storyline and it might close . When I click on the player, I receive an error message 'ERROR: Could not load the file 'story_content/data.xml''.
I've restarted my computer, shutdown Articulate, and re-imported the file. Any idea why I'm getting this error message?
Hello Team,
I do have the same issue of importing the Korean .doc translation file. I receive an error " Not a valid Word doc". I also tried importing the attached doc's in this thread, but none are working.
Kindly help me on this issue ASAP.
Thanks
Prasath
Hello, Prasath! It looks like you're using Storyline 3. What version of Word do you have installed? If you'd like me to have a closer look, I'd be happy to!
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
Hi Crystal,
Due to the privacy policy, I am cannot share the office projects with third parties. So, kindly let me know how to overcome this issue.
Thanks for letting me know, Lakshmi. I've opened a case with our support engineers to see how else we can help!
Hi Jen!
Good question!
We are still supporting .doc as an acceptable file and haven't made any announcements to start accepting .docx.
If we do, I'll report back to this discussion with an update!
Hi Lauren,
Thanks for getting back to me! Does that mean that it is under consideration at the moment and just hasn't been announced or that it is not being considered? I'm just curious to hear if enough people have been asking for .docx for it to be considered sometime in the near future or if it is considered a low priority for a feature enhancement at this point and may not be implemented at all?
Thanks,
Jen
Hello there, Jen!
Thanks for taking the time to help us understand the need for .docx support! It's not something we've planned for yet, but we'll share this with the right team and let you know of any changes.
Here's an inside look into our process of prioritizing feature requests!
