I am having to translate some training into 7 languages but I am seeing a problem when using the translation export and import in storyline 2 (using the word file)
Some of the text is German and some is translated correctly into portuguese.
I have attached the translation file and the corresponding page from the training course.
Hi, Sean -- Thanks so much for reaching out and I wanted to share this page with a variety of Translation-related articles that may be helpful for the issue you are experiencing. Please let us know if issues persist and we'll see what more we may be able to do to assist!
I'm speculating here, but my guess is somehow, somewhere, the Translation Matrix/Table in your Word document MIGHT have gotten corrupted and/or confused.
There is significant potential for this to happen if you have multiple copies of the SAME English or other source content housed within the SAME project.
If I damage or mix-up even the SLIGHTEST element in this translation document, it can lead to some serious FIND/REPLACE confusion when I import into Articulate Storyline.
I have several badly-formed translated content Import passes to support this concept.
My suggestion:
This is likely not what you want, but TRY limiting your translation documents to just ONE other language before importing. I'm betting if you break it up into distinct language chunks, the Translation features will likely work much better for you.
Now, getting past that, if you can come up with a way to somehow bring in multiple languages of text content into a single Storyline Project at the SAME time, more power to you, but I have yet to see it be done, never mind done accurately and well.
Hi All, I will check the link to articles, just to clarify I was importing one language in the word document and saving it as PT (for example) then reopening the English document and translating that one to German and then saving it as DE.
I was then going to repeat for the other languages
Hi, Sean -- Thanks for the update, and if you discover a method to address the issue you are facing, please feel free to share it here so that others who come across this discussion looking for help may benefit, as well. :)
I am reasonably sure it was a problem of my own making, I must have changed something after exporting the file to be translated. This caused the software to look like part of the page was German and the other Portugees when the file was imported back into storyline.
7 Replies
Hi, Sean -- Thanks so much for reaching out and I wanted to share this page with a variety of Translation-related articles that may be helpful for the issue you are experiencing. Please let us know if issues persist and we'll see what more we may be able to do to assist!
Interesting translation issue, Sean!
I'm speculating here, but my guess is somehow, somewhere, the Translation Matrix/Table in your Word document MIGHT have gotten corrupted and/or confused.
There is significant potential for this to happen if you have multiple copies of the SAME English or other source content housed within the SAME project.
If I damage or mix-up even the SLIGHTEST element in this translation document, it can lead to some serious FIND/REPLACE confusion when I import into Articulate Storyline.
I have several badly-formed translated content Import passes to support this concept.
My suggestion:
This is likely not what you want, but TRY limiting your translation documents to just ONE other language before importing. I'm betting if you break it up into distinct language chunks, the Translation features will likely work much better for you.
Now, getting past that, if you can come up with a way to somehow bring in multiple languages of text content into a single Storyline Project at the SAME time, more power to you, but I have yet to see it be done, never mind done accurately and well.
Hope this helps!
-Mark
Good suggestions here, Mark! Please let us know if that helps, Sean, or if difficulties persist!
Hi All, I will check the link to articles, just to clarify I was importing one language in the word document and saving it as PT (for example) then reopening the English document and translating that one to German and then saving it as DE.
I was then going to repeat for the other languages
Hi All,
Don't worry about this issue I think it's an problem with the translation file that I can fix.
Thanks for the support
Hi, Sean -- Thanks for the update, and if you discover a method to address the issue you are facing, please feel free to share it here so that others who come across this discussion looking for help may benefit, as well. :)
I am reasonably sure it was a problem of my own making, I must have changed something after exporting the file to be translated. This caused the software to look like part of the page was German and the other Portugees when the file was imported back into storyline.
This discussion is closed. You can start a new discussion or contact Articulate Support.