Use Pseudo Translation to configure the memoQ XML import filter

You can test the import filter for an XML file in memoQ with the Pseudo Translation feature. This is particularly beneficial for XML formats, which have been adapted to customer requirements. With Pseudo Translation you can determine which sections of the XML file in memoQ have been released for editing and which are protected from editing. This is important to attain a valid XML file after successful translation.

Software localization with XML-files

In software localization, language relevant contents of XML files often have to be translated. The technical translation should only be done for certain parts of the XML file, other parts have to remain unchanged and should therefore be protected by the CAT tool from editing.

This is done via the correct configuration of an import filter for the respective file format. The import filter can be tested effectively using Pseudo Translation.

Detailed information on this topic can be found on Wikipedia. You can see an XML file in the following example. If you move the cursor over the image, you see the part of the text, which has to be translated, highlighted in yellow.

  1. Before
  2. After

It is very easy to recognize what has to be translated:

  • the content of the text tag
  • some of the CDATA framed texts within the text tag, but not all of them

XML file “translated” with Pseudo Translation

We exclusively use the CAT tool memoQ from Kilgray to translate XML files. It offers a freely configurable import filter, as well as the option to test filter configurations with the use of Pseudo Translation.

A translation can be simulated using the Pseudo Translation feature of memoQ.

In the first step we have used the standard memoQ XML filter for import. The edited texts were then translated using Pseudo Translation and the file was exported again.

  1. Before
  2. After

The effect of the Pseudo Translation can be clearly seen in the comparative image above: Texts, which can be edited in memoQ, are labelled with # at the beginning and $ at the end.

There is illegible gibberish with a number of special characters between these. The text for editing can therefore be easily recognized and in the example we see that the node tags within the CDATA elements are translated with the text.

This is, however, not intentional in this case.

Adaptation of the import filter for optimal results

Process for filter adaptation

Now we have to consider how to adapt the memoQ import filter in such a way that the desired result is attained.

There are three parameters for doing this:

  • Filter options for the XML filter
  • Cascading Filters – several filters connected in series
  • Regex Tagger – protection of certain strings against editing

The effect of these three parameters is more closely examined in a special article on XML filter configuration.

Result of the correct filter configuration

In the example we used a cascading filter to protect the node tags against editing using a downstream HTML filter.

The result looks like this:

  1. Before
  2. After

Now all parts of the XML file, which must not be edited, are protected by the specially adapted XML import filter from memoQ.

More information on Pseudo Translation

Application examples for the localization of XML data can be found in the articles translate IODD files and translate PROFINET GSDML files on the PRODOC homepage.

The following video shows how to use the Pseudo Translation function for the configuration of the import filter in memoQ: