Message-ID: <1340675409.3192.1485852343909.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3191_986875757.1485852343909" ------=_Part_3191_986875757.1485852343909 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Multilanguage

Multilanguage

eZ Platform offers the ability of creating different language ve= rsions of all content in the repository.

 

How to creat= e different language versions?

The multilanguage system operates based on a global translation list tha= t contains all languages available in the installation. Languages can be ad= ded to this list from the Admin Panel in the user interface. Once this is d= one, any user with proper permissions can create Content item versions in t= hese languages in the user interface.

See Using multiple= languages for an overview of how to operate language version from the = Admin Panel.

 

How to= make translations available to the visitor?

Once more than one language is defined in the global translation list an= d there is content in different languages, the question is how can this be = exposed to use by the visitor. There are two ways to do this:

  1. Implement a mechanism called Language Switcher. It lets you create links that allow switching b= etween different translations of a Content item.
  2. If you want to have completely separate versions of the website, each w= ith content in its own language, you can use siteaccesses. In this case, de= pending on the uri used to access the website, a different site will open, = with a language set in configuration settings. All Content items will then = be displayed in this primary language.

Fallback languages and missing translations

When setting up siteaccesses with different language versions, you can s= pecify a list of preset languages for each siteaccess. When this siteaccess= is used, the system will go through this list. If a Content item is unavai= lable in the first (prioritized) language, it will attempt to use the next = language in the list, and so on. Thanks to this you can have a fallback in = case of a lacking translation.

You can also assign a Default content availability flag to Content Types= (available in the Admin Panel). When this flag is assigned, Content items = of this type will be available even when they do not have a language versio= n in any of the languages configured for the current siteaccess.

 

Multilanguage and perm= issions

LanguageLimitation a= llows you to limit users' editing rights depending on the language of the C= ontent item. See Permissions a= nd Limitations reference= for more information.

------=_Part_3191_986875757.1485852343909--