XTM Connect: Sitecore 3.0 has arrived
Ensure content consistency while increasing efficiency with pre-processing
As our connectivity improvements are now part of a continuous deployment cycle, our connector releases are independent of the main XTM Cloud releases. This enables our users to take advantage of new connector features more quickly.
This release of XTM Connect for Sitecore introduces support for pre-processing. This enables Sitecore translation requesters to select any project template, even if a pre-processing step is included in the selected workflow.
The XTM Sitecore Connector lets you automate the creation of multilingual content, managing it directly from your Sitecore CMS. This enhances content creation by automating your localization process.
What is pre-processing?
Pre-processing is an additional step that can be added to any XTM Cloud workflow. This step happens prior to the main localization workflow starting. Simply put, it’s an additional ‘Translate’ step, except the source and target languages can be the same. Once that step is completed, the project will then automatically move on to the target languages, such as French and German for instance. All of this happens automatically and is completely seamless to Sitecore users.
This can be useful for a variety of use cases, such as checking for inconsistencies, or using pivot languages. Let’s first look at how pre-processing can help with source consistency as well as Translation Memory (TM) leveraging.
Using pre-processing to create consistent, on brand content
Brand and content managers know this issue all too well: when several team members are responsible for creating different kinds of content and are able to publish pages through Sitecore, it’s hard to ensure consistency. The tone of voice, or the wording used to refer to the same concepts could be slightly different. This is why harmonizing content before it gets sent for translation is key.
To do so, Project Managers (PM) can add a pre-processing step to their translation workflow. Until that first step is completed, linguists will not be able to access the source file. In this case, as we are checking for inconsistencies, the source and target languages will be the same, let’s say English (US) to English (US). At this stage, we’ll want to be looking closely at unpopulated segments with a high fuzzy match.
For instance, if the sentence ‘Clients should contact support for more information.’ appears in the source file, and ‘Customers should contact support for more information.’ already exists in the TM, we’ll get a 90% fuzzy match. Although the two sentences have a similar meaning, in this case ‘customers’ is the preferred term, and therefore should be used instead of ‘clients’ to ensure consistency.
If one person owns the content in English, they can ensure that the source files are consistent with previously translated pages, matching content that is already stored in the TM. Thanks to the TM leverage provided during pre-processing, the source file review can be further expedited, leading to additional efficiencies through automation. This brings us to our other benefits: time and cost savings.
Reduce costs and turnaround time with pre-processing
Pre-processing is used to create a new source file, which is the one that will then be analyzed for the location project. Using the same example: ‘Customers should contact support for more information’. As it has already been translated, the linguist would get an ICE match or 100% match from the TM, and would not charge for this segment.
However, without the pre-processing step, the linguist would have received ‘Clients should contact support for more information.’, which would return a 90% fuzzy match. The project manager would have to pay for that fuzzy match, while the linguist would have to spend time working on segments that shouldn’t even need to be translated.
A pre-processing step ensures that the source content is checked and aligned with the brand guideline, and therefore the TM, cutting costs and saving time. Plus, this new target file can be downloaded and passed on to the source authors, with an instruction to use this as their new source of truth moving forward.
Using pre-processing for pivot languages
Pre-processing can also be used when language pairs are difficult to find, such as German to Czech and Polish for instance. In these cases, it would be easier and faster to find a linguist to translate from German into English, and then from English into Czech and Polish. Plus, because everything is automated, as soon as the pre-processing step is completed, the workflow will automatically move on to the next step and notify linguists that they can start working on the project, using English as their source.
We are excited by this XTM Connect Sitecore 3.0 update and hope our users will enjoy the many benefits of implementing pre-processing.
You can see the full list of new features included in Sitecore 3.0 in our release notes.
Interested in XTM Connect? Find out more about our connector integrations.