Skip to content

Languages

Two things have languages, and they don’t always match: the site, and each trip.

The storefront lists the languages the site is in (locales) and its default_locale. Your site’s own words (menus, buttons, messages) are yours to translate into each. Pages and menus from the API come in the language you ask for with locale, else in the site’s default.

Every trip is written in English first. A seller then publishes it in other languages one by one, writing the translation or starting from a machine draft they review in the portal. Nothing is translated automatically, and a trip is never shown in a language its seller hasn’t published.

Ask for a trip with locale, e.g. ?locale=fr:

  • if the seller published it in French, the text is French and content_locale is fr;
  • if not, the text is English and content_locale is en.

locales lists the languages the trip is published in, English first. A few newer fields, such as place_label, are in English for now; the reference says which.

A French page can hold an English trip. When content_locale isn’t the page’s language:

  • mark the trip’s text with lang="en", so screen readers and browsers read it as English;
  • ask search engines not to list that trip page in that language (noindex), and leave it out of the sitemap and hreflang for it.

The SEO guide has the rest.

Arabic reads right to left. Set dir="rtl" on an Arabic page and use CSS logical properties (margin-inline-start, not margin-left), so one layout serves both directions.

Sites and trips can be in English, French, German, Italian, Spanish, Japanese and Arabic.