Managing multiple locales

In Jargon, content can maintain the same response structure across multiple locales, eliminating the need to maintain a separate application for each locale. Response names are also maintained when switching between locales.

You can configure the locales of your app under Settings > Platforms and Locales. Within the studio, you can switch between your available locales in the dropdown menu in the upper left, below Jargon. If you click on an unvisited resource that was created in a different locale, Jargon will prompt you to initiate that resource in that locale, whereby you can author the resource in that locale’s language. If not every resource needs to be initiated for the current locale, you can configure fall-back locales in settings.


Fall-back Locales

Fallback locales are used to provide an alternative response when one is not available for a specified locale. This is particularly useful when working with different locales of the same language (e.g. English US and English UK). By selecting a fallback locale, you can focus on creating locale-specific variations where it matters, while sharing the bulk of the content that is in the same language and that doesn’t have locale-specific nuances.


Multilingual variable logic (Gender, plurality, formality, etc)

The ICU message format should be used to handle pluralization, gender, and formality in variables. This allows logic to be determined within a variable in order to simplify the localization of the content. For example, a message using the ICU format might read:

"You have {itemCount, plural,
=0 {no coins}
=1 {# coin}
=other {# coins}}"