When I generate and import my storyline course into my translation management system, it contains formatting in the string and is difficult for my translators to distinguish the actual text to be translated. It also causes the system to count all of this formatting in the wordcount to be translated. Is there a way to fix this? See attached photo example (text to be translated is highlighted in yellow), as well as email from the Translation Management System support team.
Thanks so much for reaching out! I'm sorry to hear you're having difficulty with your translation course. Happy to help!
I'd recommend exporting your Storyline project to Word, so you are able to gather the correct word count and the correct language you need to be translated without the additional characters.
Here is a screenshot of how you can navigate to this feature:
I have tried this as well, however all of the Project Information imports
to the TMS as strings to be translated also. For example Source FileName,
Author, etc.
[image: image.png]
I suppose it would be possible more me to go through and individually mark
each unnecessary string as "Do Not Translate". This just makes things a bit
more tedious.
There isn't a way to modify the XLIFF translation file that is generated by Storyline 360. You can try uploading your translation file into a different translation tool such as Smartcat to compare how each tool recognizes the words that are for translation.
If tools such as Smartcat or Trados don't recognize the entire contents of the translation file as words that need to be translated, try reaching out to the support team of your translation management system to check why it is reading the XLIFF file from Storyline 360 differently.
3 Replies
Hi Amanda,
Thanks so much for reaching out! I'm sorry to hear you're having difficulty with your translation course. Happy to help!
I'd recommend exporting your Storyline project to Word, so you are able to gather the correct word count and the correct language you need to be translated without the additional characters.
Here is a screenshot of how you can navigate to this feature:
I hope this helps!
Hi Luciana,
Thank you so much for getting back to me.
I have tried this as well, however all of the Project Information imports
to the TMS as strings to be translated also. For example Source FileName,
Author, etc.
[image: image.png]
I suppose it would be possible more me to go through and individually mark
each unnecessary string as "Do Not Translate". This just makes things a bit
more tedious.
Any suggestions here?
Thanks, Luciana.
Hi Amanda,
There isn't a way to modify the XLIFF translation file that is generated by Storyline 360. You can try uploading your translation file into a different translation tool such as Smartcat to compare how each tool recognizes the words that are for translation.
If tools such as Smartcat or Trados don't recognize the entire contents of the translation file as words that need to be translated, try reaching out to the support team of your translation management system to check why it is reading the XLIFF file from Storyline 360 differently.