All posts by Harpreet Neelu

What’s New : Multilingual Support features in Experience Manager 6.4

Over the years, AEM Multilingual features have extended translation capabilities to facilitate content translation for AEM Sites, Experience fragments and AEM forms, machine translation for Communities, content and metadata translation for DAM. With every release, we strive to make global content translation and management easier for customers

The latest release of Experience Manager brings a bunch of new out-of-the-box Multilingual Support features. These features bring automation to the translation workflows, support flexibility with site structures and provide out-of-the-box translation memory updates.

New features include :

  • Identification of language branch by page property
    • In the previous versions of Experience Manager, language copies were supported for a Site structure. It was required that the url path has an iso-language code, for it to be recognized as a language root. In Experience Manager 6.4, it is no longer a requirement. With new advanced property ‘Language root’ in a Site page, it is possible to assign any page as a language root, without altering Site structure.
  • Support creation of language root at two levels
    • With introduction of this functionality, a Site structure where language roots residing at two levels in a hierarchy, is supported. For example, all language roots, irrespective whether they are residing under APAC or EMEA or are sibling of en, are recognized.

This eliminates the need to having duplicate copies and additional roll-out,  once content has been translated.

  • Auto-promote launches
    • Setting ‘Auto-promote launch’ property on a translation project ensures that the launches are promoted automatically when translation content is received from the vendor.
  • Auto-creation of recurrent translation jobs
    • Additional settings have been added to Translation Project properties to support future automation. If same content is translated at a periodic interval, these properties can be modified to create a new translation job automatically. The recurrence of job creation can be defined at a day/week/month/year interval. Since Translation workflows are smart enough to recognize if a page has been modified or created, only modified/new pages (from original job) are added in the automatically created translation job.
      Enabling auto-promote launch functionality along with auto-creation of translation job feature ensures that the translated content in repository is always updated.
  • Translation project with multiple destination language
    • To reduce the number of translation projects created, support for creation of translation projects with multiple destination languages is present in Experience Manager 6.4. While creating a Translation Project from AEM Projects , multiple target languages can be added. With this change, the target/destination language property is now present at a translation job level. All jobs in the Translation Project are independent of each other and can have different content. This ensures flexibility to add or remove content for a particular destination language, hence retaining the customer’s control on what he want to get translated and in which locale.
    • Creation of multiple destination language Translation Projects is also supported from Site Reference panel and Language Copy wizard.
  • Out-of-the-box TM update
    • To improve quality and efficiency of translated content, out-of-the-box translation memory update feature has been implemented. Once the translated content is received from the vendor, the customer can view the page and if required , update a segment with appropriate text. This updated segment can be send back to the vendor via translation workflows so that the vendor can update their Translation Memory and ensure correct translation for future re-use.

These out-of-the-box features ensure that customers can get started with translation workflows early, with minimal customization and improved time efficiency .

Multilingual support for Adobe Experience Manager

With increasing access to the web,  online content has become the ‘first’ customer interaction point for most brands. As businesses go global, the end user expects the brands to host their content specific to their region/preferred language.   To facilitate and support the requirement for global presence for businesses, Experience Manager has built tools for content translation. Using out-of-the-box multilingual features, customers can translate

  • Site pages
  • Assets
  • Forms

to any locale.

In-built functionality for Multilingual support in Experience Manager includes:

  • Translation projects

To get started with translations, a Translation project should be set up. It requires specifying source and target language, translation method(machine/human translation), translation provider and the content to be translated. Any type on content – page, assets, tags, i18n dictionary etc can be added to a project
More information: https://helpx.adobe.com/experience-manager/6-3/sites/administering/using/tc-manage.html

  • Sites/ Assets UI support

A content author or review can remain in the Site/Assets UI in Experience Manager and set up their translation projects . This can be done by

  • Using Reference Panel to detect language copies, in which the content can be translated.
  • Language copy wizard takes care of creating the language copy as well the translation project. Multiple projects , have same source but different target languages, can be created at the same time.
  • Translation Integration Configuration

Translation Integration Configuration gives choice as to how to translate reference content inside a site page. If user wants to translate the site page but not the images inside it, it can be achieved using this configuration . More information :  https://helpx.adobe.com/experience-manager/6-3/sites/administering/using/tc-tic.html

  • Content Update scenarios

The user would want to update the translated content if the source content has changed. Smart translation feature detects which source pages/assets have been updated, deleted or created. Only these pages/assets are send for translation, thereby reducing the cost of re-translating entire site.

  • Component property based translation

Using Translation Rules UI , component property/s to be translated can be selected. This ensures that non-relevant content is not translated.  More information : https://helpx.adobe.com/experience-manager/kt/sites/using/translation-rules-editor-technical-video-setup.html

  • Content type supported

Multilingual workflows are supported for

  • Site pages
  • Assets
  • AEM forms
  • Content Fragments
  • Experience Fragments
  • I18n Dictionaries
  • Tags

These content types can be extracted from a page where they are referenced. Hence, user doesn’t need to know the location of the referenced content.

Beyond Experience Manager features, an ecosystem is built around multilingual support.

  • Translation Partner connectors
    To support content translation there needs to be a translation connector. Adobe Exchange (https://experiencecloud.adobeexchange.com/ ) host 19 translation connectors to choose from, depending on partner vendors or translation method. By default, Experience Manager ships with Microsoft Connector which supported Machine Translation.
  • Sample translation connector
    Sample connector, called Bootstrap connector, is provided for customers or service providers who want to create their own custom connector. The connector is build using the latest Translation APIs. GIT : https://github.com/Adobe-Marketing-Cloud/aem-translation-framework-bootstrap-connector
  • Best practices and documentation

For optimum utilization of out-of-the-box multilingual functionality, documentation around best practices is available.

About the Author: Harpreet Neelu is an engineering program manager at Adobe based out of Noida, India.