Hello...I have been trying to import some revised French text into the original French storyline file. (Just some new slides and new text on old slides needed translation.) Our translation department translated the text in the Word document as instructed, but when I import back into the storyline file, it appears to be working and I get the "Congratulations" message but the text remains in English. I reviewed other posts with this issue and tried working on a C drive rather than a shared drive. That didn't help. Is there something else I can try to make this work! I will be doing 3 more courses in this series and don't want to have to put the French text in the slides manually. Thanks!
I'm sorry you're having such trouble importing in the translation. Thanks for already trying it from the C drive, but I'm curious to know if the files were originally stored and being edited while on your shared drive? That could lead to persistent issues in the file, even after you move it off the shared drive - so I'd try importing the .story file into a new project and then using that version to import your translation back in?
I'd also suggest reviewing our best practices for files here to prevent any other odd behavior.
If you're still seeing the Congratulations message, but no translation changes appearing, can you share a copy of your .story file and Word doc with us?
it is because you have changed the name of the export document? Normally during translation the word document created is the same name as the story file. My understanding is this name should not be changed so that once translated the same document is imported back in.
I'd agree with Wendy - you'll want to keep the file name the same so that the translation feature of Storyline can recognize it and import in everything correct. I gave this a quick text on your .story file by exporting a new translation copy, making a few changes and then saving it to import back in.
All that went smoothly and the translated changes were made. Let us know if you're still running into issues after checking that set up!
Interesting. I'm sure I have changed the file names before (our translation dept. gives their documents a job number) and it worked OK. I will ensure going forward that this doesn't happen. Thanks for your help!
Perhaps just one a lucky streak before that with it working? I tried changing the file name, and saw the same as you described...it acted like it was working but it didn't.
6 Replies
Hi Barb,
I'm sorry you're having such trouble importing in the translation. Thanks for already trying it from the C drive, but I'm curious to know if the files were originally stored and being edited while on your shared drive? That could lead to persistent issues in the file, even after you move it off the shared drive - so I'd try importing the .story file into a new project and then using that version to import your translation back in?
I'd also suggest reviewing our best practices for files here to prevent any other odd behavior.
If you're still seeing the Congratulations message, but no translation changes appearing, can you share a copy of your .story file and Word doc with us?
This post was removed by the author
Didn't work after creating a new .story file. Here's my current file and word doc.
Hi Barb
it is because you have changed the name of the export document? Normally during translation the word document created is the same name as the story file. My understanding is this name should not be changed so that once translated the same document is imported back in.
Just my two cents worth.
Hi Barb,
I'd agree with Wendy - you'll want to keep the file name the same so that the translation feature of Storyline can recognize it and import in everything correct. I gave this a quick text on your .story file by exporting a new translation copy, making a few changes and then saving it to import back in.
All that went smoothly and the translated changes were made. Let us know if you're still running into issues after checking that set up!
Interesting. I'm sure I have changed the file names before (our translation dept. gives their documents a job number) and it worked OK. I will ensure going forward that this doesn't happen. Thanks for your help!
Perhaps just one a lucky streak before that with it working? I tried changing the file name, and saw the same as you described...it acted like it was working but it didn't.
Good thing to keep in mind going forward!
This discussion is closed. You can start a new discussion or contact Articulate Support.