{"id":6193,"date":"2013-06-20T00:00:00","date_gmt":"2013-06-20T00:00:00","guid":{"rendered":"https:\/\/www.globalizationpartners.com\/2013\/06\/20\/website-translation-in-adobe-experience-manager-adobe-cq5\/"},"modified":"2021-01-05T09:59:49","modified_gmt":"2021-01-05T09:59:49","slug":"website-translation-in-adobe-experience-manager-adobe-cq5","status":"publish","type":"post","link":"https:\/\/www.globalizationpartners.com\/2013\/06\/20\/website-translation-in-adobe-experience-manager-adobe-cq5\/","title":{"rendered":"Website Translation in Adobe Experience Manager – Adobe CQ5"},"content":{"rendered":"

After Setting up Adobe Experience Manager for Multilanguage Websites<\/em><\/a> Part 1 and Adobe Experience Manager Content Translation<\/a>Part 2, web content management teams can focus on maintaining the current multilingual content as it is important to preserve the integrity and consistency of the website between all the available languages.<\/p>\n

Two very common cases after initial site localization are a) the need to translate website<\/a> new content that has been added or b) updating existing content.<\/p>\n

Adobe Experience Manager CQ5 Translation workflow<\/h5>\n

Adobe Experience Manager provides a built-in workflow (Adobe Experience Manager Translation workflow) that provides solutions for these basic cases related to multilanguage website updates and maintenance.<\/p>\n

The following steps explain how to add new content in source language and use Adobe Experience Manager Translation Workflow to localize it:<\/p>\n

From Adobe Experience Manager CMS, select the source language<\/strong> (i.e. English), select New Page<\/strong> and then Create New Page<\/strong><\/p>\n

\"Adobe-CMS01\"<\/p>\n

From the sidekick, open the workflow tab<\/strong>, expand the Translation group<\/strong> then select target language(s)<\/strong><\/p>\n

\"Adobe<\/p>\n

From the dropdown list select Translation workflow<\/strong> and click translate<\/strong>.<\/p>\n

\"Adobe-CMS03\"<\/p>\n

Now, a reference for the new page has been added to the website(s) in the target language(s). By activating the reference<\/strong> a new page is created. A User with editor rights can then access the content in target language and translate it.<\/p>\n

In order to maintain the integrity of the content between source and target language(s), other features are provided by the built-in Translation workflow such as providing a solution to monitor changes done in source language(reference page) and comparing these changes with the content in the target languages.<\/p>\n

The following steps demonstrate the feature allowing a user to compare between source and target language(s):<\/p>\n

    \n
  1. Implement any changes to the reference page (the one with the source language)
    \n\"Multilanguage<\/li>\n
  2. Open the same page in target language(s), from translation tab<\/strong> in the sidekick<\/strong> select “Show side-by-side<\/strong>” and select a version of the reference page to compare with:
    \n\"Website<\/li>\n
  3. The website will be displayed side by side in 2 parts with the source (reference page) and the target language page in order to compare, check difference, edit and translate as appropriate.
    \n\"Adobe<\/li>\n<\/ol>\n

    As per as the above demonstration, adding new content in source language can be easily controlled and translated by using Adobe Experience Manager built-in translation workflow that facilitate the process of controlling, reviewing and comparing the content between the source and the target languages.<\/p>\n

    Please make sure to read the next blog in the Adobe Experience Manager Website Translation series entitled:<\/p>\n

    Part Four: The Adobe Experience Manager<\/em><\/strong>
    \ni18n Translator for Website Translation.<\/em><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

    After Setting up Adobe Experience Manager for Multilanguage Websites Part 1 and Adobe Experience Manager Content TranslationPart 2, web content management teams can focus on maintaining the current multilingual content as it is important to preserve the integrity and consistency of the website between all the available languages. Two very common cases after initial site […]<\/p>\n","protected":false},"author":13,"featured_media":6194,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[1421,530,64],"_links":{"self":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6193"}],"collection":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/comments?post=6193"}],"version-history":[{"count":5,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6193\/revisions"}],"predecessor-version":[{"id":22486,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6193\/revisions\/22486"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media\/6194"}],"wp:attachment":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media?parent=6193"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/categories?post=6193"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/tags?post=6193"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}