Resource Library

Jargon Support, Concepts, Documentation, and More

Need Additional Support?

We're here for you and happy to answer questions. Don't hesitate to reach out!

Contact Support

Planning for Voice App Localization

If expansion to new markets is in the plans, localization should be a consideration from the beginning and factored into the structure of the content. If left as a secondary concern, it becomes very challenging to update and maintain content across multiple languages while sharing the same app logic. Language complexities such as plurality, gender, and cultural/local references become complicated content puzzles. Jargon's multilingual capabilities allow for structuring and maintaining content across multiple locales. To handle plurality, gender, formality, etc. within responses, Jargon supports the ICU format.


How to Internationalize Voice App Content

There are three components of a voice app that need to be translated - the user utterances, the voice app responses, and any store metadata that describe the application. With Jargon, content is managed separately from the business logic of the application, making it easy to hand off content to a translator while maintaining the structure of the content. During this handoff, context for each piece of content is provided in order to assist with localization decisions.


Maintaining Voice App Structure

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 maintained when switching between locales.


How to use the ICU Format in Voice App Content

The ICU 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}}"


Fallback 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.


Need additional support?

support@jargon.com