Languages, Locations & Timezones

In this article, you will learn how languages, locations, and time zones work on the platform.

The Platform can be viewed in a variety of different languages. The different languages are machine-translated as opposed to human translated.

If you are interested in having the Platform professionally translated, then please contact success@learnamp.com and they will be happy to assist.

  • A Language is known as a Locale on the platform.

  • A Locale is a two-letter acronym that is used to signify the Language.

  • The locale located in a URL link will decide which language the page is displayed in:

  • Learn Amp currently supports the following locales:

Locale

Language

Locale

Language

en

English (UK)

en-US

English (United States)

de

German

fr

French

it

Italian

nl

Dutch

pt-BR

Portuguese (Brazilian Portuguese)

es-CO

Spanish (Spanish Colombia)

pl

Polish

ru

Russian

no

Norwegian

sv

Swedish

da

Danish

zh-CN

Chinese (Traditional)

zh-TW

Chinese (Taiwan)

ja

Japanese

ar

Arabic

 

How are Locales set?

The server automatically determines the locale for every page request by considering:

  1. If the URL contains a locale

  2. If the user logged in has a primary language (see how to set a primary language later on in this article)

  3. If the company has a default language

  4. If none of the above are applicable, then the system default (en) is used

If you try to switch to a locale that’s not enabled for your account, then the page will revert back to the system default.

 

When is Locale remembered?

You can change your locale, using the Language switcher. This only sets the locale for the current URL session. This means that if you log out and then back in, the Locale will be reverted to your primary locale or the company default.

You can switch to any Locale supported by Learn Amp for every page, even if Translations are disabled for your company by editing the URL of a page. This will force the locale to change, even when the language switcher is not visible.

Emails and Locale-

When the system sends an email notification, Locale is never determined by the URL segment. It is automatically determined for the recipient by considering:

  • If the recipient has a Primary Language.

  • If the company has a default language.

  • If none of the above are applicable, then the system default (en) is used.

 

How do new users get their Locale?

If Translations are enabled for your company, then Locale can be set during the invite flow (including Bulk Invite CSV):

Setting language via Manual invite:

  • In the top navigation bar, select the '+' icon

  • Click on People

  • Select Single User

  • Go through the invite flow

  • Input your chosen language for the user on step 6

  • Click on Send Invitation

 

Setting language via Bulk Importer:

  • In the top navigation bar, select the '+' icon

  • Click on People

  • Select Many Users

  • Upload your CSV (you can use our template)

Make sure there is a coloumn named ‘language’
Input your chosen languages for the new users

 

Okta and AzureAD also support setting a Primary Language in their default mappings that can be enabled when setting up the integrations.

Check out how to set up languages for users via Okta here and AzureAD here.

If a locale is not enabled for a new user during the invite flow or via default mappings in Okta and AzureAD, then the new user’s Primary Language is set as the Company’s Default Language.

 

Configuring Language & Location

The Language & Location feature can be used to create a list of options that will be available on the user’s profile and set default settings for language and time zones. These options include the ability to:

  • Set a default language and timezone

  • Add languages and locations to the list of available languages for users

You can access the Language & Location feature by:

  • clicking on your profile icon

  • selecting Company Settings

  • clicking on Languages & Locations

 

Changing the default language:

  • Make sure you are logged in

  • Click on your profile image

  • Click on Profile & Preferences

  • Select Languages & Locations

  • Select your Primary language

Note: You can also add any other languages you know here

 

Change your user account language:

  • In the upper right-hand corner there is a globe (language switcher), click this

  • Select your language

 

What does the language switcher affect?

  • UI - All of the titles, buttons, etc. that Learn Amp owns.

  • Items / Events etc. - Your company can choose to translate the titles and descriptions of various Items and Events as well as the actual Item itself.

 

Changing the default location:

In the Company Settings>Languages & Locations>Locations you will have the option to ‘Add a Location’ to the list of Available Locations, that your users can pick while editing their profile.

Admin/Owner users can set up company locations (such as cities or specific offices):

  • In the top navigation bar, Click on your profile image

  • In the dropdown, select Company settings

  • Click Add location

  • The box is then free-text so that you can be as specific or vague as you like, e.g. by country, city, building name, etc

  • Edit the settings for the location

  • Click Save

 

Changing the default timezone:

  • In the top navigation bar, click on your profile icon

  • Select Company settings

  • Click on Languages & Locations

  • Select Time zone

  • Select the time zone you want as the default (note that this can be overridden by individual timezone)

To change your individual time zone:

  1. In the top navigation bar, click on your profile icon

  2. Go to Profile & Preferences

  3. Click on Languages & Locations

  4. Select the time zone you want (this overrides your location or company default).

 

New content must be added in the Company’s Default Language - The system will redirect you to the company’s default language if you try to create a new item whilst tuned into a different language. Once the main translation has been added, the content can then be edited in other languages.

How Translations are stored and updated-

Translations are managed via an external web interface
New phrases in English are automatically translated into Dutch and Spanish – by Google

System-wide

Translations are stored in configuration files, hard-coded, and kept in source control.

Content

The following can be translated:

Content Type

What can be translated

Content Type

What can be translated

Item

Name, Description (html content), Elearning Package (one per locale), Document/File (one per locale)

Channel

Name

Learnlist

Name, Description, Section Title

Quiz

Name, Description

Quiz Questions/Answers

Sentence and Feedback (for correct/incorrect)

Dashboard & Widgets

Dashboard Name, Widget Name (Widget titles are translatable but may need to be edited)

Exercise

Name, Description

Event

Name, Description

Skill/Topic

Name

Skill/Topic Category

Name

Invitation Email

Subject/Body

 

What about missing Translations?

Missing translations always fall back to English, UK. Although, English translations will not fall back to other languages if translated when the company’s default is not English.

User Interface – If no translation exists for your selected locale or for English UK, the system will show a copy containing the error message “translation missing”.

Content – If no translation exists for your selected locale or for English UK, the system will show a blank space.

User Interface – If no translation exists for your selected locale or for English UK, the system will show a copy containing the error message “translation missing”.

Content – If no translation exists for your selected locale or for English UK, the system will show a blank space.

You can help keep our translations up-to-date by providing us with the correct translations via CSV. Here are some top tips:

  • Only edit the phrases: To make sure that there are no errors with the import make sure that you only edit the column for the relevant language.

    • Don't edit the 'Key' column - this helps us to identify the right phrase to translate.

    • Don't add any additional columns, rows, etc. - if you want to share any comments with us you can do so over email, or even send us a separate document if you wish!

  • Only edit the phrases: To make sure that there are no errors with the import make sure that you only edit the column for the relevant language.

    • Don't edit the 'Key' column - this helps us to identify the right phrase to translate.

    • Don't add any additional columns, rows, etc. - if you want to share any comments with us you can do so over email, or even send us a separate document if you wish!

  • Don't worry about skipping: Any phrases you skip, will remain as they are.

  • Don't worry about skipping: Any phrases you skip, will remain as they are.

  • Code phrases: Some phrases include code, be extra careful to preserve these:

    • Anything in curly brackets, keep as it is (keep in English and with the correct bracket structure). E.g. 'Click to view the report %{report}'.

    • For pluralisations keep the 'One:'and 'Other:', only translate the phrases themselves. E.g. 'One: Learnlist, Other: Learnlists'

  • Code phrases: Some phrases include code, be extra careful to preserve these:

    • Anything in curly brackets, keep as it is (keep in English and with the correct bracket structure). E.g. 'Click to view the report %{report}'.

    • For pluralisations keep the 'One:'and 'Other:', only translate the phrases themselves. E.g. 'One: Learnlist, Other: Learnlists'

  • Empty + odd phrases: There may be some empty translations and/or some phrases that seem highly technical:

    • Any blanks may just be where we've not yet updated the field. If you want to provide us with a translation this will work otherwise we can update this ourselves.

    • Some phrases may seem very technical or slightly unusual. If you wish to 'skip' these, then that's fine - we can always do another import or update that specific field later.

  • Empty + odd phrases: There may be some empty translations and/or some phrases that seem highly technical:

    • Any blanks may just be where we've not yet updated the field. If you want to provide us with a translation this will work otherwise we can update this ourselves.

    • Some phrases may seem very technical or slightly unusual. If you wish to 'skip' these, then that's fine - we can always do another import or update that specific field later.

  • Saving in CSV: The file is provided in a CSV format, please save it as a CSV before sending it over to support@learnamp.com.

  • Saving in CSV: The file is provided in a CSV format, please save it as a CSV before sending it over to support@learnamp.com.