26 Manage Localization Policies
Localization policies are the translation rules applied to any assets in a repository. A localization policy defines if a translation will be required and if so, what the required languages are for assets and any optional languages that might be used. You must be a repository administrator to create localization policies.
Note:Localization policies aren't used in business asset repositories.
Assets can have multiple translated versions associated with the original item, which is considered the master copy. When an item is localized, a copy of the item is made for the language. For example, there may be a blog post about the newest Android tablet that is translated into French and Spanish with the master copy in English. Each version of the blog post exists as a separate entity. It can be edited as needed and can be at a different stage of asset lifecycle than the others. The French version can be in review, for example, while the Spanish version is published. There may be two or three content versions of the post, each of which can be translated and have a different status applied to it.
The simplest way to check the status of a particular translation version is to view the item in the asset repository. See Search, Filter, and Sort Assets for details.
By default the Localization Policies page shows all localization policies, sorted by name. Use the drop-down menu on the right to change the sort order. You can also use the search box to find a localization policy by name.
You can manage localization policies in the following ways:
Create a Localization Policy
A localization policy defines if a translation will be required and if so, what the required languages are for assets and any optional languages that might be used. You must be a repository administrator to create localization policies.
To create a localization policy:
- Sign in as a repository administrator in your browser and click Content under Administration in the left navigation menu.
- Choose Localization Policies from the drop-down list and then click Create.
- Enter a name for the policy. Don’t use special characters in the name.
- Enter an optional description for the policy.
- Choose the required languages for this policy from the drop-down list. To deselect a language, click the X. You can type part of the language name and results are shown, letting you quickly find the language you want to use. Assets created in a repository associated with this localization policy won't be able to be published unless they have translations for all required languages.
- If desired, select one of the required languages as a default language for sites and assets published with this localization policy. If a user tries to view a site or asset in a language for which there is no version, the site or asset will appear in the default language.
- Choose optional languages for the policy. Assets created in a repository associated with this localization policy don't need to have translations for these optional languages in order to be published.
- Click Save when done.
After a policy is created, it can be used in a publishing channel. See Manage Publishing Channels for details.
Delete a Localization Policy
You can’t delete a localization policy if it's associated with a publishing channel. You have to remove the association in order to delete the localization policy.
To delete a localization policy, select it and then click Delete.
Create Custom Locales for Translation
When submitting an item for translation the target language (locale) is identified by a code so the language service provider knows what language to translate the item into and return. For example, fr represents French and de represents German. If you are a developer for your organization, you can create custom locales for translation based on your organization's needs. Custom locale codes include the base language, any regional dialect code if applicable, an x to designate it is a custom locale, and whatever other identifying customization is required by your organization. For example, a custom local for English might look like en-JM-x-custom.
- Click Content in the Administration section of the side navigation menu.
- Select Localization Policies from the banner menu.
- Click Languages in the banner.
- Select the base language code with whatever regional dialect code you want to use for your custom locale.
- Enter the custom locale tokens in the field next to the base code. Custom local tokens cannot be more than 8 characters, but any number of tokens can be entered when separated by a dash. Only alphanumeric characters (A-Z and 0-9) are valid.
- Enter an optional description. If no description is entered, the default is to display the base language code description.
For example, if you select Portuguese (Brazil) (pt-BR) as your base code and dialect, you can enter custom-south-america as your tokens. The resulting custom locale displayed in the Language Code list would be pt-BR-x-custom-south-america. If no description was entered, then the description for the custom locale would be Portuguese (Brazil). If a description of Portuguese South America was entered, then that would be displayed as the description.
- Click Add. The custom locale is now available when creating localization policies.
To delete a custom locale, click next to the custom local type in the Language Code list.