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: Translating Your Storyline 360 Courses Just Got Easier Storyline 360: Enhanced Word Translation And to keep tabs on Storyline 360 features in the works, check out our What’s New, What’s Next page.

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!

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!!!

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.

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.

Articulate team,I agree with the Stefan, Manny, and Eva above. Making use of the single box features of the legacy translation with the modern format would be the ideal outcome of this.I would love to see this in the next update of Storyline.

MikeOlivieri-6f

Former Staff

4 years ago

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.

storyline 360

RenGomez
Staff
4 years ago
Hi Bill,

I'm sorry to hear you're having issues purchasing our software! I've started a case on your behalf to connect you with our team to get this sorted out.

Be on the lookout for a reply soon!
billhardy
Community Member
4 years ago
Thank God my card is working again.
MariaCS
Staff
4 years ago
Hi, Bill.

I'm happy to hear everything is working now! Please reach out through the case if you have additional questions!
MarianoAran-477
Community Member
2 years ago
Have there been any updates on this?

Is this still being reviewed with 'some kind of priority' or has it been abandoned for now? (I'm asking because the last message was one year ago)

Thanks
KellyAuner
Staff
2 years ago
Hi Aukalen,

Thanks for checking in! I don't have an update since the latest release, but I'll share your comments with the team and post our progress here. If you need any assistance in the meantime, please let me know or submit a case for our Support Engineers.
Dominik1
Community Member
2 years ago
I would like to add my voice here to. I totally agree with Aukalen and the others as well. The "new" Word format looks great and it much faster to export, but also our translation agency is not able to translate it without us having to pay extra for the additional effort. We also went back to the legacy format until this has been addressed and fixed.

Many here would appreciate, if this is made a higher priority.
EricSantos
Staff
2 years ago
Hi Aukalen and Dominik,

So sorry for the trouble with Word translation! The issue with Word translation export segmentation should have been fixed in Storyline 360, Update 53. Would you be willing to share a copy of your Storyline file privately through a support case so we can find out what's happening and provide additional fixes as needed? We'll delete it when we're done testing!

In the meantime, can you try using XLIFF for translation instead of Word? Our old version of XLIFF was outdated, but we've already updated our XLIFF support. Let us know if this works for you!
Dominik1
Community Member
2 years ago
Hi Eric,

Thank you for your reply and also thank you to Aukalen for the very detailed and well explained response. That is exactly what your translation agency is struggling with as well, hence we are still using the legacy translation option. In our case XLIFF files are not an option, we tried it, but it leads to higher translation costs as well.

Thank you.

Best,
Dominik
StefanLampert-7
Community Member
2 years ago
Dear Articulate team.

I have been following this discussion after my initial post in March 2021, which is almost two years ago.

Special thanks to Aukalen M for the excellent explanation (posted on 12/27/22). And thanks to all who keep this disussion alive.

As a company specializing in e-learning translation we are confronted with translation issues in our daily business.

It is real pitty that Articulate published an advanced export feature two years ago, but is obviously not listening to its users saying that it is UNUSABLE in its current state.

The result is that everyone who needs to translate Arculate Storyline courses in a professional way still has to rely on the LEGACY translation option. What's the use of a "new" export feature that nobody can use? From my perspective it is not enough to publish new features that look nice but are not usable.

In the case of the Export feature, I assume that 90% of the work is already done with the current version, so there is no need to re-develop the feature from scratch.

Articulate Storyline is a great tool - no doubt. But not listening to user feedback for almost two years as shows this discussion is not state-of-art.

As far as Articulate Storyline is concerned, my wish for 2023 that you Articulate will publish an amended Export format by end of March 2023. If you decide to look into this, we will be happy to assist with advice and feedback.

Regards,
Stefan