XTM Connect for Sitecore
Requesting a translation from Sitecore is easy and intuitive. The process involves a few simple steps to complete.
Start by logging in to Sitecore. This will take you to the Sitecore launchpad, which is divided into four groups of applications. Content localization is managed from Sitecore’s Content Editor. Here we see the Content Tree, showing the website structure. Depending on the location of the element in the website structure, large sections of the website can be taken for translation as a single XTM project. We want to translate the Home element, so we select it. The tab containing the XTM translation controls is on the right of the top toolbar. Before content is sent to XTM for translation, it is placed in a queue.
Items for translation are kept in the queue until project creation is triggered either by a manual action or automatically according to a schedule. The “Translate Now” button, sends the translation to XTM immediately. Sitecore users can check the progress of the translation project directly from the Sitecore interface, with the XTM “View Translation Progress” button. The “Get XTM Template” button, allows you to download new project templates and update the existing list when any changes have been introduced in XTM.
Let’s return to the Content Editor. A new window opens after clicking “Add to queue”. In this pop up window you need to specify the source language, enter a name for the project that will be displayed in XTM, and select the target languages. Then, you can choose one of the XTM templates for the project creation and management. You can also select the checkbox below to include all sub-items to the selected element. In this instance, below the Home element in the Content Tree, you can find a list of subordinate items in the website tree structure. These can be included in the translation as the selected Home item is the parent to all the listed items, covering the entire website. This is a convenient way to manage the translation of large websites in XTM.
In this case, the structure of items taken for translation exactly reflects Sitecore’s website structure. The project queue confirmation displays immediately after clicking the Add button. We want to send the content for translation now. The prompt informs us that the project creation has begun. Translators in XTM can instantly find the project which they need to work on. The project has been created automatically for the selected target languages. The workflow and linguists specified in the template have been auto-assigned and the project has been started too. All that happened without any human intervention at all. XTM comes with two advanced editing environments: the traditional CAT workbench and a unique Visual Editor.
The standard translation editor is the perfect choice for most translation work. Opening the file, shows that the whole project has been machine translated – which was also specified in the template. We can now post edit the machine translation, changing one of the segments to make it easily recognizable in the visual environment. Now we are opening the WYSIWYG XTM Visual Editor. The original content exported from Sitecore is visible to the left, and the translation is on the right. The “French translation” phrase we entered in the standard editor is present here too. The source text can be hidden to allow us to review the localized content in more detail. This view is far more advanced than a simple preview. Translators or reviewers can easily update the text taking into account the visual and textual context. The changes are then immediately visible in the view. Texts can be selected for editing even from the source text view for direct editing in the target. Once the translation is complete, the target files are automatically returned to Sitecore for publishing.
Congratulations! You have localized your Sitecore website effortlessly in XTM. No content copying & pasting or file management involved! Not a single email sent or human mistake made!
Can managing a multilingual website be any simpler than that?