How does translation work in Portal 2.0?

Flatfile Portal 2.0 sets its language depending on the primary locale set in your browser. If Flatfile sees a locale that it has a translation for, it loads that translation. 

If Flatfile does not have the primary locale set in your browser, it looks at the secondary, tertiary, and so on locales that are enabled. Flatfile will load the translation for the first matched locale that it finds. 

If, in the rare instance that Flatfile does not have any matching translations for your set locale, it will attempt to load the base version of the language you have set. For example, if your primary language is Mexican Spanish (es-MX), and that locale is not available, Flatfile will load the Spanish (es) translation.

If Flatfile does not have any matching languages at all available, it will default to English.

You can also provide some custom translations and localizations using i18n overrides.

To choose a language within the Flatfile importer, use the importer.setLanguage('xx')method. You can use this method right after importer.setCustomer(). The code snippet below shows an example of how to choose a language in the Flatfile importer., 

const importer = new FlatfileImporter(
  licenseKey,
  settings
)

importer.setCustomer(customer);
importer.setLanguage("xx");

const importOnClick = () => {
  importer.requestDataFromUser().then(
    // do something
  )
}

Supported languages:

• German - de & "de-DE"
• English - en , "en-CA" , "en-GB" & "en-US"
• Spanish - es & "es-ES"
• French - fr , "fr-FR" & "fr-CA"
• Italian - it
• Japanese - ja
• Korean - ko
• Dutch - nl
• Polish - pl
• Portuguese - pt & "pt-BR"
• Swedish - sv
• Thai - th
• Turkish - tr
• Chinese - zh , "zh-Hans" , "zh-Hant" & "zh-Hant-TW"
• Indonesian - id