{"id":40924,"date":"2017-01-16T17:06:31","date_gmt":"2017-01-16T11:36:31","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=40924"},"modified":"2017-11-22T16:02:14","modified_gmt":"2017-11-22T10:32:14","slug":"top-6-translation-features-in-aem-6-2","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/top-6-translation-features-in-aem-6-2\/","title":{"rendered":"Top 6 Translation Features in AEM 6.2"},"content":{"rendered":"

There are few out-of-the-box Translation features in AEM<\/a>\u00a0which are used for overall translation management and specifically for\u00a0translation connector implementation<\/a>. The base foundation of these features were already laid down with the release of AEM 6.1 however the enhancements in AEM 6.2 have made the implementation and the entire translation process management easier.<\/p>\n

Outlined below are few most relevant features<\/p>\n

1.\u00a0Language Copy Management<\/strong><\/p>\n

In AEM 6.1 one had to manually create the language copy and then proceed with end-to-end execution of translation process, thus resulting in an additional execution step. But with AEM 6.2, in the \u2018Warning dialog box’ there is an option to \u2018Create Language Copy\u2019 \u00a0by simply clicking on a button. This dialog box doesn\u2019t open if the Language Copy\u00a0of the content already exists.<\/p>\n

\"warning<\/p>\n

2. Accept or Reject Workflow<\/b><\/p>\n

The feature to accept or reject the content has been introduced to manage the translated content on AEM. This option is available only when the content required to be translated\u00a0is in \u2018Ready for Review\u2019 status. On rejection, addition of comment is also available which can be used to state the reason of rejection. But the project cannot be restarted or the content cannot be sent for translation again, if all the content is \u2018Rejected\u2019. Generally the review part is handled by translation services providers, but in case an additional review is required, then this feature would be of a great use.<\/p>\n

\"translation<\/p>\n

3. i18n Translations<\/b><\/p>\n

i18n dictionaries<\/a>, a translation feature has been introduced in AEM 6.2, \u00a0where the\u00a0dictionary automatically queues up into the translation\u00a0job and which can be sent for translation. Any explicit dictionaries can be added by clicking on \u2018Add i18N-Dictionary\u2019 option under the \u2018Translation Job\u2019. This would help in translating all the content present under dictionaries which is referenced all over the site,\u00a0in one go.<\/p>\n

\"i18n<\/p>\n

\"i18n<\/p>\n

4. Traslation Rule Editor File<\/b><\/p>\n

The most critical requirement for any translation connector to work is to configure correct translation rules file<\/a>. This file predominantly controls what all properties in a component should be sent for translation and hence this should be set up correctly.\u00a0Currently this file needs to be populated by either developer or administrator who has good knowledge of components, their properties and business requirements in terms of what needs to be translated and what needs to be ignored. Because of the complexity of generating rules\u00a0file, an enhanced management console to populate this file\u00a0is going to be released with AEM 6.3.<\/p>\n

\"component_selection\"<\/p>\n

 <\/p>\n

5. Multiple Language Management<\/strong><\/p>\n

The \u00a0project creation process doesn\u2019t provide an option to translate or manage multiple language directly using the project console but different languages\u00a0can be managed using References<\/a>\u00a0tab under Sites section. Internally translation API is capable of handling a single language only. Hence, for multiple languages, multiple projects are created under\u00a0Project folders, with project names corresponding to target language codes.<\/p>\n

\"2_Reference_Languages\" \"7_MultiFolder\"<\/p>\n

6. Translation API<\/strong><\/p>\n

There have been enhancements in translation API for providing the support for XLIFF\/XML conversions which helps developer in exporting\u00a0the correct source file to translator and importing the translated file from the translator. Package com.adobe.granite.translation\u00a0<\/em>contains all the relevant classes being used for translation process implementation.<\/p>\n

The XLIFF API<\/a> provides support for converting translation-object-XML to XLIFF, and vice-versa.<\/p>\n

The\u00a0TranslationObject<\/a> has also been enhanced to support retrieving Translation Object XML\/XLIFF input stream. Plus you can get the page preview of Translation Object by creating Zip file containing HTML and its references.<\/p>\n

Following methods support these enhancements:<\/p>\n

InputStream\u00a0getTranslationObjectXLIFFInputStream(String\u00a0xliffVersion)\r\n<\/a><\/pre>\n
InputStream\u00a0getTranslationObjectXMLInputStream()<\/a><\/pre>\n
ZipInputStream\u00a0getTranslationObjectPreview()<\/a><\/pre>\n
A high level idea on the usage of these functions is provided in the Bootstrap Framework<\/a>. The exact flow of translation API and product issues present in XML to XLIFF conversion will be further explained in upcoming blogs.<\/p>\n
References:<\/p>\n