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.

Leave a Reply

Your email address will not be published. Required fields are marked *