Details
-
Improvement
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
Description
By now, translation module searches for the mgnl:template attribute to check the dialog associated for digging in and search for the properties which should be translated. Anyhow and tho is not aa good practice, its posible to associate a dialog to an area and create i18n attributes to it.
Under this scenario, when the translation modules checks for the template attribute of the area and determines it doesn't have, it jumps to the next dialog so the properties are not translated.
Attached a light-module with an example and some screenshots.
Checklists
Acceptance criteria