-
Story
-
Resolution: Fixed
-
Critical
-
5.0.1
-
None
-
-
Empty show more show less
-
Yes
-
5.1 Beta1- Frontend, 5.1 - Final
-
8
In Magnolia 5.0, many Strings used in UI are either hardcoded, or used from configuration without i18n. To allow full i18n in M5.1, such Strings have to be replaced by message keys, and the proper i18n code has to be used.
See http://wiki.magnolia-cms.com/display/DEV/i18n+in+Magnolia+5
And See Progress:
http://wiki.magnolia-cms.com/pages/viewpage.action?pageId=72974954
Meeting notes:
https://www.evernote.com/shard/s249/sh/659d7e8a-3e37-4026-aaac-61b016b3c94a/a18676c38f7ed947d87b408523f90ec4
- depends upon
-
MGNLUI-2087 Untranslated old keys due to not passed i18n bundle basename
- Closed
-
MGNLUI-2045 create new message-bundles each for every app / module (with texts) and define naming-convention for theses files
- Closed
-
MGNLUI-2085 FIeldDefinitionKeyGenerator creates keys with colon ":"
- Closed
-
MGNLUI-2088 key-generator creates keys with ".." (2 dots in a row)
- Closed
-
MAGNOLIA-5268 As a developer I can annotate objects to be internationalized and let a framework do the rest
- Closed
-
MGNLUI-2086 STK-keys cannot / is not using fallback to the old API ...
- Closed
-
MGNLUI-2039 split and move bundle-files
- Closed
-
MAGNOLIA-2530 Cleanup/consolidate MessagesManager vs MgnlContext
- Closed
- is related to
-
MGNLUI-1825 Use the languages from /server/i18n/system/languages in the Edit User dialog
- Closed
- relates to
-
MGNLUI-2131 i18n: use new i18n for all text in Magnolia - Master Ticket
- Closed
- supersedes
-
MGNLUI-252 Handle user language
- Closed