|
All content with label i18n.
Related Labels:
development, v2_1, needsreview, improvable, templating, outdated, v3_5, howto, introduction
Single hierarchy multiple languages
(Community Wiki)
Magnolia 3.5 provides a lot of new functionality to make singlestructuremultilanguage sites work. The ideas below have been written for older versions of Magnolia. If you want Magnolia output in more than one language, you have follow two ...
Other labels:
v2_1, development, improvable, templating
|
Encoding property files
(Community Wiki)
Java properyfiles are encoded in iso88591. this standard does not support special characters. but there is an escaping mechanism to use unicode characters (utf8) in this propertyfiles. An excample of a french propertyfile: menu.roles=R\u00f4le To make a proper file you can save ...
Other labels:
development
|
Introduction to I18nContentSupport
(Community Wiki)
Table of contents: Magnolia Content Internationalization And Localization Support Magnolia 3.5 offers content internationalization (i18n) and localization (l10n) support in a pluggable manner which allows you to customize the applied i18n or l10n strategy (note that i18n and l10n use ...
Other labels:
v3_5, howto, development, introduction
|
I18n translator informations
(Community Wiki)
General Information It is very easy to translate the messages: # update the entries below with your name, language and email (so we can contact you) or provide your own page on the wiki. # get the latest English files "messagesen.properties" and "messagestemplatingen.properties" from ...
Other labels:
v2_1, outdated, needsreview
|
I18n Developer Information
(Community Wiki)
latest information. there are some jira tasks which can have an impact on the current i18n solution (more in the context of configuration than to the api). configuration the configuration is done in Config repository: /server/i18n: define the application language (change the language node ...
Other labels:
v2_1, development, needsreview
|
|
|
