Localizing EPiServer XML data in memoQ

There are several aspects at the different stages of a localization project that may have an influence on the level of its complexity, e.g. the structure of the source data during the pre-processing stage. The aim of the paper is to demonstrate how memoQ enables its users to create very fluent workflows for complex projects if one manages to make optimal use of the different functionalities offered by the tool.

In the case of XML exports from EPiServer, the pre-processing script that needs to be executed in order to filter the translatable content is fully automated via the project template. The powerful concept of cascading file filters finishes the script’s work by importing the filtered content only. Vendor management (both job assignment and deadline calculation) is also beautifully organized for all the target languages in the project template. The post-processing steps that are required to prepare the translated documents for delivery are integrated in the template as well. Thanks to the custom export path rule, target documents automatically end up in the folder that will be used for delivery to the customer.

The actions described in this presentation lead to a workflow in which only one thing is still done manually: selecting the source documents to import for translation. All other manual interventions are excluded or significantly reduced. This allows saving precious time, and therefore also precious money, which is advantageous for all parties involved.



Jourik Ciesielski

Jourik Ciesielski
Jourik Ciesielski holds a Master in Translation as well as a European Master in Specialised Translation from the Thomas More University (University of Leuven) in Antwerp. In 2013 he started as an intern at Yamagata Europe as part of his studies and then stayed in the company as a full-time language engineer. Today Jourik’s strong interest in language technology supports him in his localization engineering and quality assurance tasks.