Skip to main content

Supported TripBuilder Languages

Product Management avatar
Written by Product Management
Updated this week

Overview

This article presents TripBuilder's supported languages.

Supported UI Languages

On Discovery, Planner and Checkout, the following languages are supported:

  • English

  • German

  • Spanish

  • Portuguese

  • French

  • Italian

  • Dutch

  • Finnish

Important: This feature needs to be configured by Nezasa. Please contact our support team or your customer success manager to configure the following fields in Distribution Channel > General tab > Localization:

  • Languages: selection of the content languages currently supported, either the eight available or a subset.

  • Default Language: the default language used for content display. Requires to be one of the languages selected in the field Languages.

  • Fallback Language: the language to be used for content display fallback if no translation is available for a user-selected content language.

UI language configuration is performed per Distribution Channel.

In Cockpit, the following languages are supported:

  • English

  • German

  • Spanish

  • Portuguese

Destination Content

Nezasa maintains a global inventory of locations, including descriptions and pictures, so the content is constantly improved and extended. The supported languages are:

  • English

  • German

  • Spanish

  • Portuguese

If you decide to create your own destination content, then other languages can be enabled or disabled as well.

Note: In the case where a selected UI language has no available translation for a specific area/destination, the following rules apply:

  • In Discovery: The text area will appear blank. No substitution with content in another language will occur.

  • In Planner: Regardless of the selected UI language, the text will default to English content (considering this is available).

Third-Party Supplier Content

Each supplier has its own list of supported languages. Nezasa's integration with all suppliers shares (as an API parameter) the actual user language with the supplier. The range of supported languages is relatively broad: some only support English, some a specific set of languages, and some use machine-based translations for languages they don't directly support.

Note: If a supplied product has no available translation for the set language, then an automated fallback to English is applied.

Did this answer your question?