Connecting to a Translation Service Provider

Create a cloud configuration that connects AEM to your translation service provider. AEM includes the capability to connect to Microsoft Translator by default. For other translation providers, download the connector package from Package Share.
The following translation vendors provide an implementation of the new API for the Translation Projects. Links to learn more about the integration and how to download from Package Share:

After you install a connector package, you can create a cloud configuration for the connector. Typically, you need to provide your credentials for authenticating with the translation service. For information about adding a cloud configuration for the Microsoft Translator connector, see Integrating with Microsoft Translator.

You can create multiple cloud configurations for the same connector if required. For example, create one configuration for each of the accounts or projects that you have with the same vendor.

After you configure a connection, you can create the translation integration framework configuration that uses it.

Creating a Translation Integration Configuration

Create a translation integration framework configuration to specify how to translate your content. The configuration includes the following information:

Which translation service provider to use.

Whether human or machine translation is to be performed.

Whether to translate other content that is associated with a page or asset, such as tags.

After you create a framework configuration, you associate the cloud configuration with the pages that you want to translate according to the configuration. When the translation process is started, the translation workflow proceeds according to the associated framework configuration.

When different sections of your website have different translation requirements, create multiple framework configurations accordingly. For example, a multilingual website includes English, Spanish, and Japanese language copies. The site owner uses two different translation service providers for Spanish and Japanese translations. Therefore, two configurations of the framework are configured. Each configuration uses a different translation service provider.

Human Translation: Content is sent to the translation provider to be translated by translators.

Do Not Translate: Content is not sent for translation. This is to skip certain content branches which would not be translated but could be updated with latest content.

Translation Provider

Select the translation provider to perform the translation. A provider appears in the list when their corresponding connector is installed.

Content Category

(Machine Translation Only) A category that describes the content that you are translating. The category can affect the choice of terminology and phrasing when translating content.

Translate Tags

Select to translate tags that are associated with the page.

Translate Page Assets

Select how to translate assets that are added to components from the file system or referenced from Assets:

Do not translate: Page assets are not translated.

Using Sites translation workflow: Assets are handled according to the configuration properties on the Sites tab.

Using Assets translation workflow: Assets are handled according to the configuration of the properties on the Assets tab.

Auto-Execute Translation

Select to execute translation jobs automatically after translation projects are created. You do not have an opportunity to review and scope the translation job when you select this option.

Communities Configuration Properties

Communities properties control how the translation of user-generated content is performed. The translation of user-generated content always uses machine translation. For more information, see Translating User Generated Content.

Property

Description

Translation Provider

Select the translation provider to perform the translation. The provider for which cloud configurations are created appear in the list.

Content Category

A category that describes the content that you are translating. The category can affect the choice of terminology and phrasing when translating content.

Choose A Locale To Use As The Global Share Store

(Optional) By selecting a locale for storing UGC, posts from all language copies will appear in one global conversation. By convention, choose the locale for the base language for the website. Choosing No Common Store will disable global translation. By default, global translation is disabled.

In the Translation Integration area, whether any configurations have been created determines which link appears:

If no configurations have been created, click or tap Configure Now.

If configurations already exist, click or tap Show Configurations, and then click or tap the + link that appears next to Available Configurations.

Type a name for the configuration and then click or tap Create.

Configure the properties on the Sites, Communities, and Assets tab, and then click or tap OK.

Configuring Pages for Translation

To configure the translation of your source pages into other languages, associate the pages with the following cloud configurations:

The cloud configuration that connects AEM to your translation provider.

The translation integration framework that configures the details of the translation.

Note that the translation integration framework cloud configuration identifies the cloud configuration to use for connecting to the service provider. When you associate a source page with a framework cloud configuration, the page must be associated with the service provider cloud configuration that the framework cloud configuration uses.

When you associate a page with a cloud configuration, the descendants of the page inherit the association. For example, if you associate the /content/geometrixx/en/products page with a Translation Integration Framework, the Products page and all pages below it are translated according to the framework.

When required, you can override the association on a descendent page. For example, the content of a web site is mostly about clothing. However, one branch of pages describes the company. The root page of the site is associated with a Translation Integration Framework that specifies machine translation using the Clothing category. The branch that describes the company uses a framework that performs machine translation using the General category.