Magnolia 5.4 reached end of life on November 15, 2018. This branch is no longer supported, see End-of-life policy.
...
System languages are configured in Configuration > /server/i18n/system
. Each locale has a language
and country
properties that define the locale when combined. This allows you to define regional variations such as zh_TW
for traditional Chinese or pt_BR
for Brazilian Portuguese.
Note |
---|
Please take note of the supported locales for your version of Java (JDK 8 and JRE 8 Supported Locales). |
Advanced Tables - Table Plus | |||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||
|
...
enabled | required , default is Enables multilanguage content entry. | ||||||||||
class | required A class that implements
|
...
| required | ||||||||||
| required Locale name constructed from the language and country such as | ||||||||||
| optional , default is Enables the locale. | ||||||||||
| required Language code such as | ||||||||||
| optional Country code such as | ||||||||||
| required Class that implements
| ||||||||||
| optional , default is Enables support for localized content. Used to rewrite URIs and getting nodes based on the current language. | ||||||||||
| optional , default is Content is served for the fallback locale if content is not available for the current locale. |
...
When you select a language from the dropdown, dialogs show a language identifier such as fr
next to field labels. This makes it clear what language editors should be entering. The
Info |
---|
The language identifier is not displayed for the fallback locale, unless the i18n property is set to true in the definition of the given dialog. For example, if your fallback locale is English you won't see (en) next to the field label. |
Info |
---|
Displaying the locale dropdown and a locale identifier in the dialog is Magnolia's default way to let editors choose a language. You can implement your own alternative such as separate tabs for each language. If the number of supported languages is not very large (3-4) tabs work well. The default approach works with any number of languages while keeping UI changes minimal. |
...
enabled | required , default is Enables multilanguage content storage and delivery. | ||||||||||
class | required A class that implements
|
...