Forum Discussion
How are you designing courses for localization from the beginning?
This is becoming a topic of discussion here as more of our content developers are creating content that will be translated in Articulate. I created some training content for my team to help them understand how to best prepare content for translation - including making sure all the text content is there first - the alt-text, captions, etc., avoiding all caps and industry jargon as much as possible, using complete sentences so the context won't be lost, avoiding images with embedded text as much as possible - this one is hard for some to get used to.
In Storyline, the biggest issues that I have found that need to be considered ahead of time are text spacing and audio with corresponding moving graphics. If audio is being added to a moving graphic slide, for example an introduction to a dashboard with arrows and boxes highlighting different features on the slide may appear perfectly timed in the source language but after being translated, the graphics are all either ahead or behind the corresponding audio.
The text boxes are a concern when designing in Storyline - you want to make sure that you'll have enough room for the languages that use more letters so that it's not overcrowded or requires a much smaller font.
I've encountered a number of bugs in Storyline as well - in states where the text literally changed to a different language (not even to the source language) and with multiple fonts being applied in translated versions, the layout issue finder not displaying all the issues but instead showing me text boxes that do not have a scrollbar ... it's been frustrating but is still easier than doing it all manually.
Related Content
- 1 year ago