Setting Up Locales
A locale corresponds to a language, such as English, or a language specific to a place, such as English spoken in the United States. You must create at least one locale for the original language in which your content is written. Create additional locales for each language into which you plan to translate your content.
Locale example
Assume you are either creating content in US English or you are working with existing content written in US English. Create a US English locale for your content. (For translation purposes, this is called the source locale.)
You need to create an additional target locale for each language you plan to translate into. For example, say you plan to translate into French (for customers in France and in Quebec), into Spanish (for customers in Spain, Mexico and Peru), into Japanese, and you might also want to ship your product to England. You would need seven additional locales: French spoken in France, French spoken in Quebec, Spanish spoken in Spain, Spanish spoken in Mexico, Spanish spoken in Peru, Japanese, and English spoken in the UK. These locales accommodate differences in spelling, word use, and dialect.
In WorldServer, a locale is a combination of a language and a specific encoding for the content in that language. For example, you could have one locale for English content stored in UTF-8 and another locale for English content stored in ISO encoding.
A WorldServer locale also has a list of users who work with content in the associated language. During workflow execution, this can be used to filter the users eligible to perform a particular task, so only users who can read French would be chosen to review a translation into French, for instance.
This chapter describes how to manage locales in WorldServer.