-
Improvement
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Kromeriz 35
-
3
We decided to implement only minimal changes: https://wiki.magnolia-cms.com/display/DEV/Minimal+required+changes
We currently generate these keys for templates:
templates.components.componentName.title
moduleName:templates.components.componentName.title
But that's not the case for dialogs:
moduleName:components.componentName.label
It should be consistent with templates (also to force more 'logical' keys)
Open Questions:
There is disagreement on what the consistant keys should be.
- Should the keys reflect the full "definition path", therefore being predictable - yet verbose?
- Should some keys support skipping parts of the definition - ie specify an app and a field, but not a subapp or view?
Next:
A list of all current keys will be created, which stakeholders from PD & PM can evaluate. Then another meeting to hopefully nail down the key generators we want to support, what patterns they should follow, and which ones we may want to deprecate.
https://jira.magnolia-cms.com/browse/DEV-137
- depends upon
-
MAGNOLIA-6535 I18n Key generators should be consistent
- Closed
- is depended upon by
-
MGNLRES-259 Use i18n best practices
- Closed
-
MTE-74 Use i18n "best practices" in MTK
- Closed
-
MTE-76 Make sure that i18n keys may be reused by other modules
- Closed