I'm a big fan of the function export and import translation. I don't use it for a translation, but for easy correcting the text.
But: sometimes it doesn't work to import a word-document, while it still has the same features (still a 93-2003 word document for example).
I get the error: 'Not a valid word document.' Extremely annoying! is there somebody who knows the solution? It will save me a lot of work and makes me very happy.
Have you changed the Word document's settings, format, file name, location? Without seeing the Word doc or corresponding Storyline file - it's difficult to pinpoint it exactly. You'll want to make sure you're following the guidelines here in regards to working locally, adhering to file paths well under the 260 character limit, and file names that don't contain special characters or symbols. Also, please confirm you're following the steps outlined here to translate content and import that translated file into Storyline.
I was running into the same issue. It was happening because the doc I was working from was a read only document. I resaved them locally and was able to get them to work.
Right click on translated document [.doc] file in file browser, go to 'Properties' and if you see a Security warning at the end of the dialog box which looks like below attached pic, then click on 'Unblock' and that will solve the issue. It did for me.
Ladies and Gentleman, and in particular Deepa Pai.
This is the first time I have experienced this issue. Have been working with Storyline since day 1. I right clicked on the file, clicked on properties and clicked on Unblock this file... All is well now. Thanks.
12 Replies
Hi Annemieke,
Have you changed the Word document's settings, format, file name, location? Without seeing the Word doc or corresponding Storyline file - it's difficult to pinpoint it exactly. You'll want to make sure you're following the guidelines here in regards to working locally, adhering to file paths well under the 260 character limit, and file names that don't contain special characters or symbols. Also, please confirm you're following the steps outlined here to translate content and import that translated file into Storyline.
Hi Asley,
Thank you so much! It helped to story it locally. What a relieve
Annemieke
Hi Annemieke,
Thanks for the update - and I'm glad your files are working back to normal.
I was running into the same issue. It was happening because the doc I was working from was a read only document. I resaved them locally and was able to get them to work.
That's an interesting point to share here Madison - although it's an older discussion it's much appreciated for anyone else who may come across it.
saving locally worked for me.
Thanks for the solution!
That's fantastic, Chris! Thanks for popping in to share here, love when these older discussions are still able to lend a hand :)
Right click on translated document [.doc] file in file browser, go to 'Properties' and if you see a Security warning at the end of the dialog box which looks like below attached pic, then click on 'Unblock' and that will solve the issue. It did for me.
Thanks for that great tip, Deepa!
Ladies and Gentleman, and in particular Deepa Pai.
This is the first time I have experienced this issue. Have been working with Storyline since day 1. I right clicked on the file, clicked on properties and clicked on Unblock this file... All is well now. Thanks.
That's it! Thank you!
Glad that this conversation was able to help you as well, Carina. Thanks for chiming in to share.
This discussion is closed. You can start a new discussion or contact Articulate Support.