With the coming release of AEM 6.2, Adobe has released a number of very interesting updates to AEM’s translation feature. These features improve the user experience for AEM’s Translation functionality, making it easier to translate and manage localized content.
I recently attended a webinar on the new translation features coming as a part of the AEM 6.2 beta program and am very excited for the following four features:
Search for Translation Content
In the initial version of the Translation API, available in AEM 6.1, adding translated content was a very broad activity. Essentially, the process was adding an entire content tree to be translated then if you wanted to limit the content being translated removing it item by item.
Now in AEM 6.2, you can leverage the powerful search features available in AEM to find content to be translated by last modification, page metadata or analytics information. This allows you to quickly refine down to the most important or most recently edited content and send it to translation.
Do Not Translate Configurations
Inspired Digital Experiences for Manufacturing & Automotive
Whether you’re just beginning your digital transformation journey or are well on your way, we invite you to explore our partnership with Adobe and our diverse capabilities in manufacturing and automotive.
Sometimes you want to be able to exclude certain portions of a website from being translated. To handle this in AEM 6.2, Adobe added the ability to create Do Not Translate configurations. These can then be associated with content by overriding the Cloud Configurations for a portion of a website. When the translation feature encounters a Do Not Translate configuration it will exclude that page and subpages from the translation process.
This allows authors to easily exclude website content from translation without having to involve developers or modifying the translation rules.
Override Source Language Warning
When I implemented the AEM – Lingotek translation integration, one of the biggest complaints we had was that the warning for when you were going to override the source language copy was not obvious enough. This dialog would appear if you say attempted to translate the English copy of a website to French. In AEM 6.1 this opened a fairly bland dialog, where as in AEM 6.2 this opens a clear warning and now allows you to create a Language Copy directly from the warning dialog.
One of the big misses in the original translation feature in AEM 6.1 was translating i18n dictionaries. Now in AEM 6.2, the translation feature will automatically queue i18n dictionaries into the translation job when you translate a page.
Bonus (Existing) Feature: Translation Rules
If you were wondering how to manage component or attribute translation rules, AEM includes a Translation Rules configuration. This offers you very fine grained control over what is sent to translation, but unfortunately there is currently no UI for managing the rules. This is expected in either a 6.2 feature pack or 6.3.
To update the Translation Rules, edit the file stored in AEM at /etc/workflow/models/translation/translation_rules.xml
A couple of notes:
1)The override option creates language copy, not a live copy.
2) we also have added support for XLIFF/XML support
3) Approve/Reject lifestyle part of the translation jobs.
4) Translation of assets now automatically adds the translated assets to appropriate language folders.
@Sridhar, thanks for the additional notes and correction on language copy, I updated the post to reflect the correct functionality.
We are facing issues in XLF generation using Translation API. Do you have any insights into this?
Unfortunately, this is most likely a product bug. I would contact Adobe Support and open a DayCare ticket to get this resolved.
Thanks Dan for the immediate revert. Are there any other known issues in Translation API? We identified few issues in import process and preview zip creation also.
Also would you be able to provide details of Daycare ticket?