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 repositories.
Localization policies are the translation rules applied to any text assets in a repository. These policies don’t apply to digital assets such as images. That content is classified as non-translatable when it’s uploaded. But content items 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.
Select a topic to get started: