Set up Locales

Setting up Translation Profiles & Options in Translations

Use the Locales screen to create a New Locale or to edit the settings for an existing Locale. The Locale record stores the locale relationships between the source language (shown as a parent locale in the screenshot) and translation language (shown as a child locale in the screenshot) settings used when you create a translation job. It also stores the translated variable values used during publishing for that locale.

You'll create the language pairs based on your translation needs, and then use the locale pairs when you are creating a Service Provider record. (When you create your service provider records, you'll assign one or more language pairs to the service provider's record. This will determine which service providers can be assigned to a translation job.)

Requirements for use:

  • The Library's license has capacity for adding at least one more Locale (required when creating New Locales).
  • A default (or base) locale has been created for the Library (this does not count towards the number of Locales set in the license).
  • The language setting for a Locale record cannot be edited if any variant objects are already using that locale.
  • A Locale record cannot be deleted if any variant objects are already using that locale.

Locale relationships

The language pairs are used in the service provider records to show the languages that provider translates from and the languages they translate to.

Fall-back Locale in Locale Records

The records in the locale list are organized into parent and child locales. The parent is the source language for the translation job and the child is the language your service provider will use for the translation (in this example the parent is English and the child is French). Your can create a language pair using the library's base language as the parent, or you can translate from one locale into another locale (for example, from Chinese [Simplified] to Korean).