Translation methods and TSP integration in AEM 6.4

Types of translation:

To automate translation workflows, one must integrate translation service providers with AEM and create projects for translating content into multiple languages. AEM supports –

• Human translation
• Machine translation

Human translation:
Human translation is best-suited for content where messaging and quality expectations are high, and the content will live for some time on the site (for example, marketing pages). During human translation, the content is sent to the translation provider and is translated by professional translators. When complete, the translated content is returned and imported into AEM.

Machine translation:
The machine translation service immediately translates the content once one integrates any of the TSPs which are available. It is best suited when the number of pages to be translated are very high and the quality expectations are low. When complete, the translated content can be reviewed before launching the translated pages (Let’s discuss more about these translation methods in the upcoming blog).

NOTE:
You can download TSPs from either of the options below:
Adobe Exchange – https://www.adobeexchange.com/experiencecloud.html and search for “translation” and download it.
CRX Package Share – Tools > Deployment > Package Share and search for “translation” and download it.

The following image shows some of the TSPs which can be integrated with AEM for content translation.



However, adobe is partnering with Microsoft Translator to take the content management experience one step further by enabling machine translation features and functionality powered by the Microsoft Translator API seamlessly within AEM. Users will be able to leverage the state-of-the-art machine translation from any of Translator’s supported languages expanding the reach of your content to deliver greater experiences to customers regardless of the language they speak.

Now let’s see how to connect to the default Translation Service Provider (Microsoft) which comes with AEM.
Steps for integrating AEM with default TSP (Microsoft):
Go to http://localhost:4502/aem/start.html
Click on Tools icon in the left side rail.
Select Cloud Services.
Then select Translation Cloud Services.
Go to libs > Translation Integration > Default Configuration and click on Edit.

Here, select the Translation Method (for example, Machine Translation) and select Translation provider (for example, Microsoft). Once these selections are done, click on Save & Close.
Go to libs > Microsoft Translator > Microsoft Translator Trail License and click on Edit.

Here, enter the Subscription Key * (It comes when one signs up for a free trial subscription) and click on Save & Close.
Now go to conf > <your-project> (for example, conf > we-retail) and click on create. It opens a Create configuration pop-up. Select configuration type as “Microsoft Translator” and enter a title for your project configuration (for example, MyTranslator). Now go-ahead and click on Create button.
Once you click on Create button, Edit Configuration window will be opened. Go ahead and enter the Subscription Key *. Click on Save & Close.

NOTE:
In prior versions, this configuration has to be done at:

Tools > Operations > Configuration > Cloud Service Configurations > Translation Integration > Default Integration > Edit

Once all the above configurations are done, one is good to proceed with the actual translation process.