{"id":29980,"date":"2021-02-17T13:24:38","date_gmt":"2021-02-17T13:24:38","guid":{"rendered":"https:\/\/www.globalizationpartners.com\/?p=29980"},"modified":"2021-02-17T17:09:02","modified_gmt":"2021-02-17T17:09:02","slug":"best-practices-for-building-multilingual-websites-using-kentico-xperience-part-2","status":"publish","type":"post","link":"https:\/\/www.globalizationpartners.com\/2021\/02\/17\/best-practices-for-building-multilingual-websites-using-kentico-xperience-part-2\/","title":{"rendered":"Best Practices for Building Multilingual Websites Using the New Kentico-Xperience Platform \u2013 Part 2"},"content":{"rendered":"

This is the second part of a series of 2 blog posts about localization in the Xperience platform.\u00a0<\/span>In this blog post, I\u2019ll cover some of the aspects you need to consider when exporting content for translation and importing translations back.<\/span><\/p>\n

 <\/p>\n

Machine Translation and Xperience<\/span><\/h2>\n

Xperience allows using resource strings to localize names and descriptions of objects, as well as other text in the user interface. There is a specific section in\u00a0Configuration > Localization<\/strong>\u00a0that allows you to enter the translation for these elements.<\/p>\n

\"Machine<\/p>\n

Machine translation can be used to translate these resource strings. You need to set up a translation service in Configuration > Translation services<\/strong>\u00a0section. This service needs to have the\u00a0Is machine translation service<\/strong>\u00a0checkbox checked:<\/p>\n

\"Machine<\/p>\n

By default,\u00a0Microsoft<\/strong>\u00a0and\u00a0Google translators<\/strong>\u00a0are present in Xperience as Machine Translation services.<\/p>\n

 <\/p>\n

Human Translation and Xperience<\/h2>\n

Xperience provides a nice set of features to export content from pages for translation in\u00a0XLIFF<\/a>\u00a0format. Also, it provides a feature to import the translated XLIFF files back in an Xperience-based website.<\/p>\n

To do this, you can either use the\u00a0Manual translation<\/strong>\u00a0option or automate the process by using a Translation Service to send the files to an external translation provider. There are different Translation Services, like GPI Translation Services Connector for Xperience 13.<\/p>\n

Alternatively, you can\u00a0develop a custom translation service<\/a> if you want to send the files to a specific endpoint.<\/p>\n

 <\/p>\n

Export Content for Translation<\/h3>\n

If you need to export content for translation, you have to navigate to\u00a0Content Management<\/strong>\u00a0>\u00a0Translations<\/strong>. This will show you a dashboard with all the submissions you created and their status.<\/p>\n

\"Export<\/p>\n

The next step will be to click on the\u00a0Create new submission<\/strong>\u00a0button. This will show a popup that will allow you to pick:<\/p>\n