{"id":6315,"date":"2013-03-25T00:00:00","date_gmt":"2013-03-25T00:00:00","guid":{"rendered":"https:\/\/www.globalizationpartners.com\/2013\/03\/25\/adobe-experience-manager-content-translation-and-management-part-2\/"},"modified":"2021-07-29T17:11:19","modified_gmt":"2021-07-29T17:11:19","slug":"adobe-experience-manager-content-translation-and-management-part-2","status":"publish","type":"post","link":"https:\/\/www.globalizationpartners.com\/2013\/03\/25\/adobe-experience-manager-content-translation-and-management-part-2\/","title":{"rendered":"Adobe Experience Manager Content Translation and Management Part 2"},"content":{"rendered":"<p>Once an Adobe Experience Manager website is set up for a multilingual website deployment (review: <a href=\"\/setting-up-adobe-experience-manager-for-multilanguage-websites-part-1\/\">Setting up Adobe Experience Manager for Multilanguage Websites Part 1<\/a>), website content can be localized into different target languages by exporting\/importing the content using the built-in Adobe Experience Manager CRX Package manager.<\/p>\n<p>CRX Package Manager is an Adobe Experience Manager tool for creating, editing packages, previewing package content, building, downloading and deleting packages. An Adobe Experience Manager package is a bundle in zip format that includes content along with other related data.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/adobe-manager_335x77.jpg\" alt=\"adobe-manager\" width=\"335\" height=\"77\" \/><\/p>\n<p>Package Manager can be accessed from Adobe Experience Manager welcome screen or directly using the following path: <em>https:\/\/&lt;server name&gt;:&lt;port number&gt;\/crx\/packmgr\/.<\/em><\/p>\n<h5>Exporting Content<\/h5>\n<p><strong>1- After login select Packages<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/1_468x350.jpg\" alt=\"1\" width=\"468\" height=\"350\" \/><\/p>\n<p><strong>2- Select Create Package<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/2.png\" alt=\"2\" width=\"544\" height=\"381\" \/><\/p>\n<p><strong>3- Add package name and version and press OK.<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/3.png\" alt=\"3\" width=\"540\" height=\"273\" \/><\/p>\n<p><strong>4- Select Edit &gt; &#8220;Filter&#8221; TAB &gt; Add Filter button<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/4.png\" alt=\"4\" width=\"624\" height=\"91\" \/><\/p>\n<p><strong>5- Add Root Path:<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/5.png\" alt=\"5\" width=\"496\" height=\"108\" \/><\/p>\n<p><strong>6- Expand the content node and select the website node (this is for the content).<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/6.png\" alt=\"6\" width=\"352\" height=\"329\" \/><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/7_312x326.jpg\" alt=\"7\" width=\"312\" height=\"326\" \/><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/8_516x370.jpg\" alt=\"8\" width=\"516\" height=\"370\" \/><\/p>\n<p>The above package includes the content and a rule to include the path of images. By Default all the website images are under ContentDAM {site name}<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/9.png\" alt=\"9\" width=\"536\" height=\"147\" \/><\/p>\n<p><strong>7- Press Done, then Save<\/strong><\/p>\n<p><strong>8- Press Build<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/10.png\" alt=\"10\" width=\"546\" height=\"366\" \/><\/p>\n<p><strong>9- Final step is downloading the compressed zip folder.<\/strong><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/11.png\" alt=\"11\" width=\"540\" height=\"307\" \/><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/12-adobe-manager.png\" alt=\"12-Adobe-Manager\" width=\"635\" height=\"79\" \/><\/p>\n<h5>Package&#8217;s folder structure<\/h5>\n<h5>Translation specification<\/h5>\n<ul>\n<li>Format: XML<\/li>\n<li>Translation units: jcr:title, name, subtitle\u00a0 and text<\/li>\n<\/ul>\n<h5>Import back the translation<\/h5>\n<p>1- Zip the package in the exact same structure as the source package<\/p>\n<p>2- From CRX Packager select Upload Package<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/13_661x369.jpg\" alt=\"13\" width=\"661\" height=\"369\" \/><\/p>\n<p>3- Browse to the package and check &#8220;Force Upload&#8221;, then click OK<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.globalizationpartners.com\/wp-content\/uploads\/2018\/07\/14.png\" alt=\"14\" width=\"538\" height=\"244\" \/><\/p>\n<p>Once the translation package is imported successfully, a new localized version in the target language will be available with identical structure as the original website.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Once an Adobe Experience Manager website is set up for a multilingual website deployment (review: Setting up Adobe Experience Manager for Multilanguage Websites Part 1), website content can be localized into different target languages by exporting\/importing the content using the built-in Adobe Experience Manager CRX Package manager. CRX Package Manager is an Adobe Experience Manager [&hellip;]<\/p>\n","protected":false},"author":13,"featured_media":6316,"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\/6315"}],"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=6315"}],"version-history":[{"count":6,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6315\/revisions"}],"predecessor-version":[{"id":32603,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6315\/revisions\/32603"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media\/6316"}],"wp:attachment":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media?parent=6315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/categories?post=6315"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/tags?post=6315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}