Browse Articles

Browse Articles

Articulate 360 FAQs: Articulate Localization

Article Last Updated

This article applies to:

Rise 360, Storyline 360, Review 360

Articulate Localization isn't available yet for public purchase. Contact us if you'd like to learn more about this product.

 

Articulate Localization enables you to deliver multi-lingual training to your global workforce at record speed. See these FAQs for answers to common questions about Articulate Localization.

General

Support and Authoring

Security and Privacy

General

What is Articulate Localization?

Articulate Localization is a localization solution built specifically for L&D, with native integration to the #1 e-learning platform for creating workplace training. It allows course creators to deliver multi-language training to a global workforce, streamlined with integrated AI translation, in-context translation validation, and end-to-end workflow—all right from within Articulate 360.

What languages are supported?

Find a complete list of 70+ supported languages here.

Are there limits to how many languages we can translate a course into?

You can translate a course into as many languages as we have support for. However, there are quantity limits for the total number of translations you can initiate based on the terms of your subscription.

What counts as a translation?

We count a translation as a translation run of a course in one language (the source language) into one language or dialect (a target language). For example, translating two courses into five languages will count as 10 translations. For Rise 360, a course is a tile in your dashboard, either a course or microlearning. For Storyline 360, a course is a project (*.story) file. 

Once translated, Rise 360 presents multi-language courses as a single 'stack' tile in your dashboard. Storyline 360 stores all languages in the same project (*.story) file. Adding a new target language to a multi-language course also counts as a translation.

Retranslating or using AI translation for existing languages in a multi-language course or project within the same billing period does not affect your total purchased translation count.

Note:  For Rise 360, if you duplicate the multi-language course or send a copy to someone else, any new translations on the copy—including translating text updates—will be counted. For Storyline 360, however, copies of the project file—such as those created using File > Save As or shared with other authors—are treated as the same multi-language project. Note that the *.story file must be saved after the first translation run to link succeeding retranslations.

What gets translated?

Course texts and closed captions in Rise and Storyline are translated. See more details about what gets translated here. 

Text-to-speech, text within images or videos, embedded media originating from outside Articulate 360, or linked/attached resources (like PDFs) are not translated at this time.

Do you support a glossary of terms? Is there a size limit for the glossary?

Yes. Any account admin can upload the glossary of terms under the localization settings of the Manage Subscription tab in the account management console. Learn how to use the AI translation glossary.

The total glossary file can be up to 10MB and each individual glossary entry must be less than 200 bytes.

Do you have a translation memory? Can we use or integrate our translation memory?

Translation memory is on our roadmap. We don't have a timeline yet, but we're actively working on it. Although integrating external translation memory is not on our roadmap at this time, we're examining the possibility and may consider it in future developments.

What translation engines are you using? How will you decide which to use for a given project? 

We are using a combination of DeepL and Amazon Web Services (AWS), which we thoroughly vetted for translation quality, language coverage, and privacy and security standards. 

Our built-in translation will default to DeepL (the industry-leading provider) for most languages, and to AWS for languages that DeepL doesn’t cover.

How accurate are the AI translations? 

Accuracy can vary depending on the language pairs involved in the translations. We chose industry-leading translation engines based on quantitative evidence presented in academic research. Our early beta customers in several global markets have been generally impressed with the quality of our AI translation compared to other machine translations they’ve tried. However, translation quality is subjective and depends on factors such as language pairs used, subject matter, and each organization’s preferences. That’s why we also included a glossary and developed an in-context human validation workflow in Review 360, to make the content just right for your audience. 

Support and Authoring

Where can I find information on how to use the Localization features?

Check out our Articulate Localization user guide series to get started.

How can I share feedback or report issues?

We’d love to hear about your experience with Articulate Localization. Look for the Help & Feedback links in:

  • Rise 360: Launch a multi-language course from your dashboard. From the stack overview, click the Help & Feedback link at the bottom of the sidebar.
  • Storyline 360: Open a multi-language project file. Click the language menu on the top right and choose Help & Feedback… at the bottom of the menu.
  • Review 360: Launch a multi-language item from the dashboard and select any target language from the sidebar. Choose the Translate tab at the top and click the ? (question mark icon) at the bottom right.

From your chosen app, select the Share Feedback / Report an Issue button from the pop-up message to launch the feedback form on your browser. Fill in the details and submit.

Do language validators need an Articulate 360 seat? 

No, language validators don’t need an Articulate 360 seat. Similar to reviewers for Review 360 items, they only need an email address. 

If we embed a Storyline block into Rise 360, will that get translated?

Embedded Storyline blocks in Rise 360 courses are not translated. As a best practice, you could translate your slide or scene in Storyline first before embedding it as a Storyline block.

Will validators be able to edit the source files?

In our workflow, validators use Review 360 to review the translation. That means the edits they make are saved as suggestions, which the author can accept or reject from Rise 360 or Storyline 360. If you want a validator to edit the source file directly, they'll need an Articulate 360 seat to use the authoring apps and proper permissions to access the source files. 

Can Rise collaborators initiate a translation?

Only course owners and managers can initiate translations and import validation suggestions. The translation and import options will not be visible for course editors.

What happens to my content when Articulate Localization is switched off?

You retain access to all the content you created but you’ll lose language management features such as course stack views in Rise 360 and Review 360 or multi-language projects in Storyline 360. When you open a multi-language course or project, you’ll have the option to save the languages individually. You can also save copies before Articulate Localization is switched off. Here’s how to save translated courses for Rise 360 and save translated projects for Storyline 360.

Security and Privacy

How do you ensure data privacy security for Articulate Localization? 

Security and privacy have always been our top priorities. We will continue to ensure safety and confidentiality for Articulate Localization through: 

  • Data privacy and integrity
    • Other than the glossary, AI features do not retain or log customer data.
    • Customer data is not used for training AI translations.
    • Our AI translation partners (DeepL, AWS) have been thoroughly vetted for data privacy and security.
  • Data protection and encryption policies
    • We employ robust encryption protocols.
    • All data is encrypted in transit with a minimum of TLS 1.2 for all third-party localization services. 
    • We comply with data protection protocols including GDPR and CCPA.
  • Ethical AI implementation
    • Our features were designed to adhere to our stringent security and ethics guidelines.

What data can Articulate Localization access, and how does it use my data? 

Articulate Localization treats your data in the same way that Articulate 360 does. Here are some specifics:

  • If translation is done using DeepL, data is processed in their EU data center. No data is retained or stored for the translation process.
  • If translation is done with AWS, data is processed in the United States or European Union depending on your Articulate 360 data center. No data is retained or stored.
  • Glossary data will be stored in the DeepL EU data center and in the AWS data center matching your Articulate 360 data center. We retain glossary data for the duration of the subscription to provide the services under your agreement.

As with Articulate 360, you can be confident that your content/data will not be retained after the translation process, used to train translation engines, or shared with others.