Adding Multi Language to Desktop

Updated on June 2, 2019 Download PDFDownload as PDF
Download PDF

Brief Overview

Multi-Language allows you to add translations to WalkMe Items you’ve created so you can support a global audience. Users either select the language from a toggle in the Desktop Player Menu, or you can configure WalkMe to change the language automatically. Translations are accessed from Insights. Translate your Smart Walk-Thrus, Shuttles, ShoutOuts, etc., into alternative language(s) and help non-English speaking users complete processes without changing the native language of your application.

How it works

Multi-Language in WalkMe Desktop is used in the same way as in WalkMe Web.

Additionally, should you desire to only translate a portion of a WalkMe item’s text, you now have the option to export and import specific items’ text, as opposed to all text at once.

Currently, only left-to-right (LTR) languages are supported in WalkMe Desktop

WalkMe does not translate the text you create, though we do allow you to export either an .XLIFF file, which is used by popular localization services, or an .XLSX Excel file, which is better suited to human translation. For more information see exporting and importing translations

Auto language detection feature is available: WalkMe Desktop can identify the OS language of the end-user and play the content accordingly.

Using Multi-Language for Desktop

Enabling Multi-Language in Analytics

Make sure you select the platform “Desktop Windows” in WalkMe Analytics:


Create translations for the desired language (see here)

Automatic language detection

The language will be detected from the operating system.

To enable multi-language, contact your WalkMe representative to add a configuration to your JSON settings that map the operating system language to a back office name.

Example:

LanguageAutoDetection”: {
“DefaultLanguage”: “ENG”,
“LanguageConverter”: {
“RUS”: [“ru-RU”],
“HEB”: [“es-es”],
“ENG”: [“en-us”,”en-uk”]
}
}

Language Converter

If you choose to use it, specify a list of language short names that are mapped to a certain language.

For example: if in the back office English is ‘ENG’, you can map OS languages ‘en-us’ and ‘en-uk’ by adding:

“ENG”: [“en-us”,”en-uk”]

Where:

DefaultLanguage is an optional field, you can add it if you want to set a fallback language that the content will be played in if the detected language doesn’t have a matching translation in Multi-Language interface in Analytics.

It’s also a way to bypass the default language set in Multi Langauge interface (regardless of the auto-detection feature); if the customer already wrote the content in a certain default language in Multi-Language interface and then wanted to change the default language of the played content without changing anything in Multi-Language interface, you can simply add this field and the content will be played in this language if no translation was found for the end-user.

LanguageToSimulate

For testing purposes, you can set the widget to run with a specific language (it will override auto detection)

Add “LanguageToSimulate”: “<Back-office-name-of-language>”

Example:

LanguageAutoDetection”: {
“LanguageToSimulate”: “ENG”
}

Note:

Make sure to write all the languages in the squared brackets and separate them by commas (if there are more than one). Make sure all the fields are in quotation marks as they appear in the example above.

Read more about WalkMe Multi Language here

Was this article helpful?

Related Articles