Supported Content Languages

AppNavi supports multiple languages for content such as routes, posts, and announcements. This helps users view guidance in a language they understand.

You can translate content manually or use automatic translation powered by DeepL for supported languages. Each piece of content has a primary language, which is the language in which it was originally created. You can change the primary language for individual content items in the AppNavi Portal.

For details about translating content, see Content Language Translation.

Supported languages

The portal offers 32 more languages but they are not supported by automatic translation

Afrikaans, Amharic, Bengali, Bosnian, Catalan, Cebuano, Gujarati, Hebrew, Hindi, Kannada, Kazakh, Korean, Kurdish, Malay, Malayalam, Marathi, Nepali, Norwegian, Pashto, Persian, Punjabi, Sinhala, Somali, Swahili, Tamil, Telugu, Ukrainian, Urdu, Uzbek, Vietnamese, Zulu.

Note: Languages marked No are not available for automatic translation. You can translate content manually where needed.

How AppNavi selects the content language

AppNavi determines which language to display by checking the available translations and applying the following priority order:

1. Language set through the API: Uses the language specified through the API, if configured.
2. Browser language with region: Uses the detected browser language and regional preference, if available.
3. Browser language: Uses the detected browser language if a regional preference is unavailable.
4. Application primary language: Uses the primary language configured in the application settings.
5. Content primary language: Uses the primary language of the individual content item.
6. First available language: Uses the first available language if none of the previous options matches.

The selected language must be available for the content. If a preferred translation is unavailable, AppNavi continues through the priority order to find an available language.

Configure application primary language

In the settings of an application, you can define the primary language with which content is recorded by default. If necessary, the primary language can be adjusted per content via the portal.

To configure it:

1. Open the relevant application in the AppNavi Portal.
2. Navigate to the application settings.
3. Set the desired primary language.
4. Save your changes.

You can also change the primary language for an individual content item in the portal when it differs from the application default.

Identify and change browser language

In order for AppNavi to display content in the desired language, it is important that the browser transmits the correct language request. To do this, you must first set the desired content language. These settings differ from browser to browser. You can find out how to change the settings for the Chrome browser here.

To find out if your browser is sending the correct request language, you can use this web page:
Detect browser language

The tabular list shows you which languages your browser requests. The language at the top has the highest relevance. The language codes themselves are displayed above the table. In this case the language code de has the highest relevance. If an AppNavi content is available in this language, it will be displayed in this language accordingly.

Setting the language preference using API

You can set a preferred content language through the AppNavi API when the browser's language is not appropriate for your application or when you need to control the language displayed to users.

For example, the following code sets German (de) as the preferred content language:

window.appnaviApi.application.setPreferredLanguage('de')

AppNavi displays the German version when it is available for the requested content. If it is unavailable, AppNavi follows the language-selection priority described above.

Troubleshooting