Localizely logo
  • Home
  • Getting started
  • How it works
  • Pricing
  • FAQ
Sign up

Translate Articulate Rise 360 courses

Export the XLIFF file from Rise 360, translate it in Localizely, and import it back.

Documentation

Articulate Rise 360 exports the text of a course as an XLIFF file and imports the translated file back, one file per language. Localizely translates these files with AI translation, machine translation, translation memory, a glossary, and the review of your team or a translation agency. The translated file you download keeps the ids of the exported file, so it imports into Rise 360 as a translation of the course.

How it works

  1. Export the course from Rise 360. In the course settings, choose Translations and export the XLIFF file of the source language. If the export offers a version, choose XLIFF 1.2.
  2. Upload the file to Localizely. Create a project with the language of the course as the main language, open Upload, drop the file and upload it for the main language. Every text of the course becomes a string key; the notes of the file are kept with it.
  3. Translate. Add the target languages and translate them the way you prefer: in bulk with AI or machine translation, from the translation memory, with your team, or by ordering a professional translation. HTML formatting of the course text shows up as tags in the editor; keep them in the translation, the QA checks flag a missing or broken tag.
  4. Download the translated files. Open Download, choose the XLIFF format and select the languages. Each file holds the source text and the translation of every text of the course, under the same ids as the exported file; several languages come as a zip with one file per language.
  5. Import into Rise 360. In the course translations, import the downloaded file for each language.

Note: Set Empty translations to Main language when downloading, so that a text that is not translated yet keeps the source text in the course instead of an empty block.

Updating a translated course

When the course changes, export the XLIFF file again and upload it for the main language. Texts that are already in the project keep their translations, changed texts are updated (with Overwrite enabled), and new texts are added. Translate what is new or changed, then download the files again. Texts that were removed from the course stay in the project until you delete them, or tag the keys in the file on upload and download only those tags.

CLI and API

The same flow works with the CLI, with the file type xliff:

config_version: 1.0
project_id: <your-project-id>
file_type: xliff
upload:
  files:
    - file: course/course-en.xlf
      locale_code: en
download:
  files:
    - file: course/course-de.xlf
      locale_code: de
    - file: course/course-fr.xlf
      locale_code: fr
  params:
    export_empty_as: main

Through the REST API, upload the file like any other localization file and download the translated files with type=xliff. See the API documentation.

Other tools

The flow is the same for any tool that exchanges XLIFF 1.2 files, such as Articulate Storyline 360 or a translation tool of an agency: upload the exported file as XLIFF, translate, and download the translated files.

Previous: XLIFF file

Read next: AI translation

Tired of manually editing translation files?

Our platform streamlines software localization for you.

Try now for Free
Localizely logo
About
Free tools
Boring stuff
  • Privacy Policy
  • Terms of Service
  • Cookie Policy
Newsletter
Copyrights 2026 © Localizely