As of December 2017, Articulate RISE does not offer a technical solution for content language translation. EzGlobe has developed a solution by which we can professionally translate the SCORM or web outputs generated by RISE.
Within the last 12 months, EzGlobe completed translations into 55 target languages. You may not even have heard of some of them. Here is the list:
Do you develop using Extensible Application Markup Language files (XAML)? Learn how to localize them.
Articulate Storyline offers two types of export/import formats: XLIFF (XML-based file) and MS Word. Which one is your best option?
Did you know that there are only three countries in the world that still use the (one would argue archaic) Imperial system of weights and measures?
When it comes to localization and translation reuse is one better than the other?
If there were only five pieces of advice to give you to make your user documentation more translation friendly, here they are:
We have evaluated the XLIFF Export/Import functionality in Articulate Storyline 2.0. We wanted to see if the localizaiton-friendly XLIFF export/import functionality works.
Translating strings out of context leads to GUI layout issues and mistranslations that can be corrected only after the localized GUI has been compiled. Multiplied by the number of target languages, these problems become expensive and carry a high risk of unpredictable release schedule delays.
We are not referring to the protruding part of one’s face below the mouth!
Parsing is the standard process of preparing files for translation – it separates the translatable content from the code.
Drupal PO files are fairly common and some standard filters exist. However, if your PO files contain HTML code and this HTML code further contains Java script functions then you need to be creative.
SDL Trados has a filter to support Author-IT XML. However, if the files are too large Trados will not swallow them.
L10N is the industry accepted abbreviation for localization. There are 10 letters between the letters L and N.
G11N is the industry accepted abbreviation for globalization. There are 11 letters between the letters G and N.
Certain mobile devices, such as the iPhone 4, have a screen resolution that is much smaller than that of an average smart phone or tablet. For the purposes of localization, we suggest developing a number of duplicate strings to have a short and long version of the strings to choose from depending on the target device.
I18N is the industry accepted abbreviation for internationalization. There are 18 letters between the I and the N.
The following is an example how the same English source can be translated by three different words in the target language based on the context.
Is the maximum length in characters as a string constraint useful?
Hindi is a complex script and while it can look fine to people who don’t read Hindi it can actually be wrong.
Why Choose Us?
- VOICE - You have a voice. We listen.
- CONTROL - We help you identify your requirements; we consider your constraints. We show you how, when and at what cost.
- SUPPORT - You have someone to rely on. We propose workable solutions.
- PEACE OF MIND - We tell you what we will do and we do it.
Your translation memory technology and its application saved us thousands of dollars and countless hours of work. Our content is highly technical and we appreciate the extra steps you take to produce high-quality translations. You are always very proactive in helping us improve the end quality of our materials – Thank you.
Director of Corporate Communications, Hardware and Software development company