This page presents incremental enhancements and refinements to AEM translation management capbilities.
Options to improve productivity working with translation projects have been added, such as automatically promoting and deleting translation launches, and scheduling the recurring execution of a translation project.
It is possible to configure multiple target languages in a translation project, to reduce the total number of translation projects created.
Manual edits of translated content can be synchronized back to the Translation Management System (TMS) to train its Translation Memory.
A list view shows a side-by-side comparison of the source and the translation for every text component that was edited. Select which translation updates should be synchronized to Translation Memory, and select Update Memory.
AEM will send an XML representation of the selected strings back to the Translation Management System.
Language roots can now be grouped under nodes, for example by region, while still being recognized as roots of language copies.
Only one level is allowed. For example, the following will not allow the "es" page to resolve to a language copy:
This es language copy will not be detected as it is 2 levels (americas/central-america) away from the en node.
Language roots can have any page name, rather than just the ISO-code of the language. AEM will always check the path and name first, but if the page name does not identify a language, AEM will check cq:language property of the page for the language identification.
A property can now be selected in the Sites list view that shows if a page has been translated, is in translation, or has not yet been translated. To display it: