Skip to main content

​
Supported locales

​
How a locale is picked

1

An explicit tag, if given

data-lang on the script tag, or locale in the programmatic config. Matched exactly first, then by base language. es-MX resolves to es.
2

Otherwise the browser

The visitor’s preferred languages, in order.
3

Otherwise English

A tag with no catalogue falls back to English rather than rendering a page of blanks.

​
Practice text

The interface strings ship with the widget. The practice’s own title and subtitle are set per language in Settings → Scheduling Widget. Leaving one blank is deliberate and safe: the widget uses the generic heading in that language rather than showing English text inside an otherwise Spanish page.

​
Pinning a language

Set data-lang when the page itself is in a fixed language:
On a bilingual site, serve the tag with the language of the page it is on. Do not pin a language on a site whose visitors vary. The browser default is right more often than a guess.

​
What is not translated

Data from the practice’s PMS. Provider names, office names, and appointment reasons. Appears as it is stored. A practice serving a bilingual population should name those things in whatever form both audiences read.