How to handle languages in Rise 360?

Due to a bug in Rise 360 the browser might incorrectly interpret a course’s language as English, no matter the actual language. If the user has enabled automatic translations in their browser, this may cause the browser to translate words that exist in both languages (English and source language) into the user’s local language.

Note: This may also affect the accessibility of the course as well as screen reader compatibility.

Some examples for courses in Swedish:

• "Finns risk för..." translates to "Finländarna risk för..."
• "fast" translates to "snabb"
• "leg." translates to "ben"
• "rum" translates to "rom"
• "former" translates to "före detta"

The issue has been reported to Articulate who are looking into it, but, in the meantime, you can do the following workaround:

In Edit mode, Preview mode or in a Share link:

Disable the automatic translation in your browser or use a different browser.

Export for LMS:

1. Export your course.
2. Un-zip the package that was downloaded.
3. Open the files index.html and indexAPI.html in a text editor.
4. In the code: lang="en"
   Change “en” to the language code corresponding with the language of your course. For example, it is “sv” if the language is Swedish.
   Here is a list of the language codes: https://www.w3schools.com/tags/ref_language_codes.asp
5. Save the changes in the files and close them.
6. Re-package a new scorm package by selecting the folders and files as shown in the image below and create a zip file.

7. The new zip file is the new scorm package, which is uploaded in the LMS.

Export for web:

1. Export your course.
2. Un-zip the package that was downloaded.
3. Open the files index.html in a text editor.
4. In the code: lang="en"
   Change “en” to the language code corresponding with the language of your course. For example, it is “sv” if the language is Swedish.
   Here is a list of the language codes: https://www.w3schools.com/tags/ref_language_codes.asp
5. Save the changes in the files and close them.
6. Upload the files to the server.

Please contact us if you are having trouble with the workaround or have additional questions.