-
Story
-
Resolution: Fixed
-
Critical
-
None
-
-
Empty show more show less
-
5.1 Beta1- Frontend, 5.1 - Final
-
2
Up until Magnolia 5.0, we were relying on code calling info.magnolia.cms.i18n.MessagesManager in each and every place that needed translation.
The process was tedious and error prone. If a developer forgot to do this from the start, or to write his code in such a way that labels could be internationalized, finding usages of code and replacing it can be a long and error prone process.
With this proposal, we introduce an annotation-based framework, where any object can be decorated such that its method annotated with @I18nText will return a translated text.
- is depended upon by
-
MAGNOLIA-5309 I18nizer: pluggable/configurable way to handle unknown keys
- Open
-
MGNLUI-1826 i18n keys: As a developer I don’t have to define i18n keys for every translatable item, if they follow the convention, so that the process is less redundant and error prone
- Closed
-
MAGNOLIA-5315 I18nizer: allow default values, optional, or default-to-blank texts
- Closed
- is related to
-
MAGNOLIA-5317 i18nizer: Default values set in a constructor override a previously configured value
- Closed
-
MAGNOLIA-5876 Freemarker templates and jsp are not aware of new i18n mechanism
- Closed
-
MAGNOLIA-5296 I18nizer: Pattern or API for unmodeled/unconfigured texts
- Open
- supersedes
-
MAGNOLIA-5283 New module in magnolia_main
- Closed
-
MAGNOLIA-1519 i18n should be definable at module level
- Closed
- mentioned in
-
Wiki Page Loading...