New in Storyline 360: Enhanced Word Translation

Translating courses with Storyline 360 has always been easy. In just a few clicks you can export all the text in your project for translation. And now you’re able to take advantage of changes we’ve made to Storyline’s Microsoft Word translation export. These enhancements make translating your courses easier than ever. Here’s a quick look at the changes:

  • Easier access to key information: Now you’re able to view important details about your project—number of scenes, slides, slide layers, strings (text objects), words, and characters—in an easy-to-read table.
  • More context clues: You’re also able to choose to include a screenshot of each slide before the slide’s associated text to give translators more context about where the text will appear.
  • Improved formatting preservation: Text formatting is now preserved when you use the Word export feature for translation—even when you use things like lists and paragraph spacing. This saves you time and effort after the translated text is imported. 
  • Compatible with Word, Google Docs, and Open Office: In addition to using Microsoft Word to translate your courses, you can now use Google Docs and Open Office, giving you even more flexibility with your translation process.

With these helpful enhancements to the Word translation feature in Storyline 360, translating courses is faster and easier than ever. We hope you’re as excited about this new productivity boost as we are. If you don’t have an Articulate 360 subscription, sign up for a free 60-day trial to give it a whirl.

For more details about enhanced Word translation in Storyline 360, take a look at these helpful resources: 

And to keep tabs on Storyline 360 features in the works, check out our What’s New, What’s Next page.

14 Replies
Stefan Lampert

Mike, we use the "Export as Single Table" option. When the text contains formattings, the text is split into speparate cells, but only in the Translation column (see attachment). It should be in one cell like in the Source text column. Could you change this? Thank you!

Manoel Gouveia

I agree with Stefan above. We want to move to the modern format. It's much much faster, easier to use, more compatible, and has solved some issues we've had with complex SL files.

However, we provide content to be translated into dozens of languages and no agencies/language translators want to use the new format and have all requested we go back to legacy because sentences are split up into separate cells. This makes it impossible to translate as every language has to translate the section in different order/way. You can't just do a word-by-word translation... it won't make sense.

PLEASE PLEASE PLEASE... put the translation column in the same cell for each section as in the previous legacy version and as the source text. Until this is updated we'll have to keep using legacy and miss out on all the benefits above.

Thank you for your help!!!

Jeremy Dittmer

I have just tried submitting a document in the new format to our translation house and they have replied that it is totally unusable.  And for exactly the reasons given above - splitting formatted text into individual chunks makes no linguistic sense.  It's as if the Articulate developers have bizarrely assumed that all non-English languages are just simple word-for-word substitutions for English.  We too will be sticking with the legacy format until this is corrected.

Bret Jorgensen

Hi Everyone,

Here’s a bit of insight into why we did this. While developing this feature, we chose to break up the strings in response to customer issues importing text formats consistently. Part of our reasoning was that things formatted that same way were likely semantically ‘complete.’ 

However, we realize we’ve missed the mark here. We are investigating whether we can handle breaking up strings in a different way without compromising the formatting. To that end, we would like to gather information from the community to design a feature that will help solve some of the concerns you’ve raised.

Please be on the lookout for an email from us requesting sample .story files to use in this investigation. 

Adam Ackerman

Experiencing the same, but wanted to say that I really like the info. summary that appears at the top of the Output. It has made it much easier to get an idea of the scope of a .STORY Project, and would be useful as a standalone feature as well. I hope this part remains present in your solution to the segmentation issue.

Wendy Ruano

As a translation services provider who has worked with Storyline for years, this is a huge problem for us and our clients. It is going to lead to inconsistent translations and lower quality all around. One current project has sentences broken up into single word segments, which is unacceptable. Any updates on the fixes?