This page presents incremental enhancements and refinements to AEM translation management capabilities.
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.
In your translation project, click or tap the ellipsis at the bottom of the Translation Summary tile.
Switch to the Advanced tab. At the bottom, you can select Automatically Promote Translation Launches.
Optionally, you can select if after receiving translated content, translation launches should be automatically promoted and deleted.
To select the recurring execution of a translation project, select the frequency with the dropdown under Repeat Translation. Recurring project execution will automatically create and execute translation jobs in the specified intervals.
It is possible to configure multiple target languages in a translation project, to reduce the total number of translation projects created.
In your translation project, click or tap the dots at the bottom of the Translation Summary tile.
Switch to the Advanced tab. You can add multiple languages under Target Language.
Alternatively, if you are initiating translation via the references rail in Sites, add you languages and select Create Multiple-language Translation Project.
Translation jobs will be created in the project for every target language. They can be started either one by one within the project, or all at once by executing the project globally in Projects Admin.
Manual edits of translated content can be synchronized back to the Translation Management System (TMS) to train its Translation Memory.
From the Sites console, after updating text content in a translated page, select Update 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 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:
es language copy will not be detected as it is 2 levels (americas/central-america) away from the
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:
In Sites, switch to List View.
Click or tap View Settings.
Check Translated checkbox under Translation and tap/click Update.
You can now see a Translated column which shows the translation status of the pages.