Define the languages that editors should be able to choose as locales in the site definition under <site>/i18n/locales. Each locale has language and country properties. They allow regional variations such as zh-TW for traditional Chinese or pt-BR for Brazilian Portuguese.
Example: Locales en and de in the default site definition
Properties:
locales
| required |
<locale>
| required Locale ID that consists of language and country such as zh-TW for traditional Chinese or pt-BR for Brazilian Portuguese. |
enabled
| optional, default is false Enables the locale. |
language
| required Language code such as pt for Portuguese. See Java 8 locale IDs. |
country
| optional Country code such as BR for Brazil. See Java 8 locale IDs. |
class
| required Class that implements I18nContentSupport such as: info.magnolia.cms.i18n.DefaultI18nContentSupport which supports a language prefix such as /en/* in the URL and stores localized content in a node using the naming pattern <name>_<locale>, for example subtitle_en.
Use this implementation if your site is organized into a single tree, in which the locale prefix usually points to the root of a site.
info.magnolia.cms.i18n.HierarchyBasedI18nContentSupport which stores and serves localized content in a hierarchical structure.
Use this implementation if your site is organized into multiple trees, in which site roots are usually named after the locales.
info.magnolia.cms.i18n.RequestLocaleAwareI18nContentSupport which reads the locale from the request. This implementation does not render language specific URLs.
|
enabled
| optional, default is false Enables support for localized content. Used to rewrite URIs and getting nodes based on the current language. |
fallbackLocale
| optional, default is en Content is served for the fallback locale if content is not available for the current locale. |
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))