Details
-
Improvement
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Kromeriz 30, Kromeriz 36
-
5
Description
Do not set i18n-basename, label, description on dialogs and templates - instead make use of autogenerated keys and use bundles within i18n folder.
Move keys from "old" bundles into i18n folder wherever possible.
Checklists
Attachments
Issue Links
- depends upon
-
MAGNOLIA-6559 Support i18n directory in light module
-
- Closed
-
-
MGNLUI-3764 I18n: I can reuse the keys between modules
-
- Closed
-
- is causing
-
MGNLEESOLR-96 Change i18n keys used from MTE and fix class used for mteSolrSearchResult page template
-
- Closed
-
-
MTE-81 Translate label for component 'image'
-
- Closed
-
- is depended upon by
-
MTE-49 More sophisticated main page template
-
- Closed
-
-
MTE-76 Make sure that i18n keys may be reused by other modules
-
- Closed
-
- is related to
-
MGNLDEMO-114 Use i18n "best practices" on the travel-demo
-
- Closed
-
- supersedes
-
MTE-82 Image component translations are broken
-
- Closed
-