{"id":42055,"date":"2016-11-09T12:46:08","date_gmt":"2016-11-09T07:16:08","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=42055"},"modified":"2016-11-09T13:17:06","modified_gmt":"2016-11-09T07:47:06","slug":"how-to-implement-a-translation-connector-in-aem","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/how-to-implement-a-translation-connector-in-aem\/","title":{"rendered":"How To Implement a Translation Connector in AEM?"},"content":{"rendered":"

The purpose of a Translation Connector in any Content Management System (CMS) is to automate content transmission between CMS and Translation Service Providers making it quicker and cost-effective. Such integration is required when there is a need to maintain multiple languages in CMS. Similarly, for projects in Adobe Experience Manager (AEM)<\/a> that involves website localization and multilingual SEO management, translation connectors implementation<\/a> becomes a mandate.<\/p>\n

Translation Connectors are simply used to provide an interface between AEM and Translation Management System (TMS), where TMS is nothing but programs which support complex translation tasks.<\/span><\/p>\n

\"Translation<\/p>\n

Once the content is selected in AEM which needs to be translated, it can be pushed further to TMS.<\/p>\n

After this, TMS does the actual translations by either using machine translation using APIs or by sending it across to different Language Service Providers (LSP).<\/span><\/p>\n

After the required translation is performed the content is then returned to AEM where it can be approved or rejected. Since the states of the translation projects are easily visible on AEM project console, the authors can also monitor the progress of source files which were sent for translation.<\/span><\/p>\n

Follow these basic steps to implement a connector with AEM<\/span><\/p>\n

\"Translation<\/p>\n

To explain these steps in details, I would be referring to <\/span>AEM 6.2\u2019s Translation Bootstrap Framework<\/span><\/a>.<\/span><\/p>\n

Step 1: Create Cloud Configuration<\/h3>\n

The first and the foremost step is to establish a connection between AEM and TMS. This can be done in AEM through multiple ways but the best way is to make use of <\/span>Cloud Configurations<\/span><\/a>. This provides content managers’ the flexibility to add configuration details or any other related information themselves to connect to TMS.<\/span><\/p>\n

Once Bootstrap framework build is deployed, under Cloud Services Configurations you can create a\u00a0configuration using the following template. <\/span><\/p>\n

\"Cloud<\/p>\n

The dialog needs to be created which should contain properties required to connect to TMS. This can be designed as per the requirement. <\/span><\/p>\n

\"Cloud<\/h3>\n

Step 2: Create Translation Project<\/h3>\n

Project Creation Wizard provides basic properties which are required to create a Translation Project. The project contains options to add details about source and target languages, human\/machine translations and configurations to translate the project.<\/span><\/p>\n

The source files can be added to the project by either using the \u2018Add translation\u2019 widget or by using \u2018References\u2019 feature under \u2018Sites\u2019. This is further explained in detail <\/span>here<\/span><\/a>. <\/span><\/p>\n

Using project creation wizard, one can go to \u201cCreate Projects\u201d and \u201cSelect Translation Project\u201d.<\/span><\/p>\n

\"Translation<\/p>\n

Advanced Properties should contain custom \u201cTranslation Provider\u201d and respective \u201cCloud Configuration\u201d.<\/span><\/p>\n

\"Translation<\/p>\n

Step 3: Send Project Containing Source Files to TMS<\/h3>\n

The content in AEM which requires translation can be added in the project. AEM 6.2 provides options to add pages, assets, assets metadata, tags, tags metadata and i18n dictionaries.<\/span><\/p>\n

Using custom solution or AEM translation APIs, AEM pages are required to be converted to TMS acceptable format, which is generally XLIFF.<\/span><\/p>\n

\"Translation<\/p>\n

\"TranslationOnce the files are added, the project can be started and sent for translation.<\/p>\n

\"Translation<\/h3>\n

<\/h3>\n

Step 4: Translation Process at TMS<\/h3>\n

Every TMS follow workflows to manage translations. Based on the required translation such as human or machine translations, the source files are either sent to different LSP or are translated using APIs. The source files may require conversion into a specific format which is acceptable by TMS. \u00a0Once the files are successfully translated and reviewed, they are imported back into AEM.<\/span><\/p>\n

Step 5: Import Translated Files from TMS<\/h3>\n

The translated files are then imported from TMS into AEM. AEM\u2019s polling functionality can be used or even a custom scheduler can be implemented to identify whether the project status has been changed at TMS and the translation files are ready to be imported.<\/span><\/p>\n

The translated XLIFF file from TMS either needs to be converted to AEM recognizable format like XML or can be imported into jcr:content node structure.<\/span><\/p>\n

With AEM 6.2, the translations can be accepted or rejected once the import to AEM is successful.\u00a0<\/span><\/p>\n

\"Translation<\/p>\n

The translated page looks like this after successful import and can be published.<\/span><\/p>\n

\"AEM<\/p>\n","protected":false},"excerpt":{"rendered":"

The purpose of a Translation Connector in any Content Management System (CMS) is to automate content transmission between CMS and Translation Service Providers making it quicker and cost-effective. Such integration is required when there is a need to maintain multiple languages in CMS. Similarly, for projects in Adobe Experience Manager (AEM) that involves website localization […]<\/p>\n","protected":false},"author":993,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":240},"categories":[1],"tags":[4847,4052],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/42055"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/993"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=42055"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/42055\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=42055"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=42055"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=42055"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}