Import translation doesn't work
Feb 21, 2016
Hi,
I have a module in English I need to translate to 12 languages.
I've exported the translation, and now when importing back it just doesn't work.
I import, a window open showing me the progress of the translation (goes very fast...) and than I get a congratulation message - but when I view my slides nothing changed and all the texts are still in English.
did anyone came across something like this? this is not the first time I work with the translation, but it is the first time something like this happens.
thanks.
Michelle
31 Replies
Hi Michelle!
In some cases, you may find that translating Articulate Storyline content via XML Localization Interchange File Format (XLIFF) doesn't work as expected. You may receive a successful (congratulations) message but find that your course is still in the original language.
If you plan to translate text manually, we recommend using one of the Microsoft Word (DOC) export options in Storyline.
Select the XLIFF export option if you're using a translation tool for automatic or professional translation services.
If you're using XLIFF with a translation tool and your course still doesn't translate as expected, make sure your translation tool is updating caption states properly. You can tell by opening the XLIFF file in a text editor, such as Notepad, and searching for "state."
Initially, the state for each caption in an XLIFF file is "new." When a caption is translated, your translation tool should update the state to "translated."
When you import the XLIFF file back into your course, Storyline will update captions that have a state of "translated." All other captions will be skipped.
If your translation tool isn't updating caption states in XLIFF files, please ask your translation vendor for assistance.
This post was removed by the author
Hi,
thanks for your answer.
I'm using the translation tool of storyline - first exporting as word file and then importing back.
some files worked great, some didn't work at all. couldn't find any difference between them.
is there something I need to instruct the translation company, so this wouldn't happen?
Hi Michelle!
Did you go through the troubleshooting above to see if the captions were updating?
I am having the same issue. I used google translate to translate the document Articulate Storyline 2 provided upon export. (It is a .doc file). I copied the translated piece from google into word, saved that (as a .doc) and imported that into Storyline, but nothing changed. It indicates it was successful, But the translated text never appears. I am new to using this feature, so it could easily be user error, any help anyone can provide is much appreciated.
Thanks,
Hi Rhona!
Do you have the .story file and translated .doc file for us to take a look?
You didn't change anything in the ID column, right? Here is our documentation.
Hi!
I did the same thing. I exported the translation document, my colleague translated only the middle line of the document and when I tried to import it is not working. I'm having to put everything in manually.
I'm attaching my documents here.
Hi Heather - Sorry to hear that you are having difficulty with this as well. Are you getting an error of some sort? Do you have the .story file so that I could take a look?
I'm not getting an error. As many of the people say above, it says completed, but it doesn't do it.
Here is the story file after I tried to import the translations and then started to put them in manually.
Hello Heather - Thanks for the update. I just did a bit of testing with your file and I'm not having an issue.
I was able to export the translation, edit, and re-import. At this point, I was able to save the new file and re-open your original file, export translation, and import the translated information as well.
Have you also reached out to our Support team? They can often spot something in a system log or error message that we can’t see here in ELH. If you would like to open up a case you can reach out to them here, and if you do let me know so that I can follow along in your case!
Hi Leslie,
I opened a case:
Got it, Heather
We'll be in touch to help you ASAP
We’ve opened case number 01040663 for you.
I linked this thread as well.
Thanks for your help!
Heather
Thanks so much for sharing Heather. Looks like you are working with Miker and he's e-mailed you a response. I will continue to follow along.
Just popped in to check on things and looks like you are back to good Heather :)
Hi!
I'm all set. Thanks for the help!
Best,
Heather
Glad to hear it Heather. Just wanted to mention that replying to the forums via e-mail attaches your signature. You are welcome to pop in and edit if needed.
Thanks!
Absolutely Heather - it's no worry on our part, but I do like to be sure that users are aware just in case :)
So? Any valuable lesson learned here?
Glad you are all set! What was the problem? Can we benefit from your experience?
I am having the same issue 16 out of 17 modules are ok with export/import from .doc files.
The faulty one looks like the others. Our translators used our guidelines throughout their translation process...
Cheers!
Hi Rich
The main thing I learned was to use a C drive rather than an S drive.
Because this was a collaborative project, I was keeping the files on an S drive. Once I moved it to my C drive it worked perfectly.
Hope this helps you!
Heather
Hello Rich - Glad that Heather was able to chime in and share her experience with you here.
If you need us to take a look at anything, please feel free to share the files you are having difficulty with.
Thanks Heather!,
One more clue in my research for great translation!
My problem is still there. Even on the C:
Thanks again for sharing!
For multiple languages, I had to duplicate the scene for every language because the import would only copy over scene 1. This was not in the directions and should be added.
Hi Kristina,
I'm not sure I understand the issue you ran into. When exporting your file for translation, it only included one scene in the export?
Hello Ashley thank you for the quick response!
My course set up is a beginning slide that branches into 4 scenes, each scene is the course in a different language. Originally it was one scene and I exported the translation document.
When I imported the translation document, the translation would over-write my english. I checked the directions for the translation document and there was no guidance for how to import multiple languages - if you can edit the directions - it would be great to add a section for multiple languages.
The fix:
Duplicate the english scene --> english becomes scene 1 and 2, import the translation document --> translation overwrites scene 1. Duplicate the translation scene --> translation scene becomes 1 and 3. Import translation2 --> translation2 becomes scene 1. Repeat duplicate scene and import for the number of languages you have to import.
Thanks,
Kris
In Storyline 2 I leaned that we could delete lines in the word file (all 2 or 3 columns) which we would not need to translate. Storyline would only change the remaining lines. I guess it works because each line has a unique id.
I have not tested if this still works in A360/SL3.
This discussion is closed. You can start a new discussion or contact Articulate Support.