Goal

In Magnolia 5.0 went slightly backwards - we lost some translations. The mechanisms are still in place, 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. This applies especially for the new code, i.e. magnolia_ui, and contacts and dam modules.but we "forgot" to implement them; many dialogs are configured with "hardcoded" labels. Some code, too.

More important, the way we apply i18n through the UI is currently inconsistent or inexistent.

To explore

• Generate key from app-dialog-field(.desc)
• Generate i18nbasename?
• (Updtask remove if match)
• (Check contents)
• Migrate existing translations
• Chain bundles for simple defaults (chain with generated bundle names, sort of package fallback)

Existing uses

info.magnolia.ui.form.AbstractFormItem#getMessages - should not be public

...