In October 2012 the European Union (EU) agency ‘European Centre for Disease Prevention and Control’ (ECDC) released a translation memory into the public domain containing 25 languages… the 23 official European languages plus Icelandic and Norwegian. This comes in a similar format to the DGT Multilingual Translation Memory of the Acquis Communautaire that I described here in this article but this time it’s much smaller… so we can look at how to handle a single TMX file that contains all of these languages in one file using Studio.
Actually there are two ways to do this. You can upgrade the TMX, or you can import a specific language pair. I’ll look at the upgrade first…. but before I do you need to know where to find this TMX. So go to the ECDC website here and download their translation memory from this section:
Once you download this file and open the zip file you’ll find eight files in there, but for this exercise the only one you need is the ECDC.tmx as this is a multilingual TM. So if you open this in a text editor you’ll note a couple of things:
- It was created with “Trados Translator’s Workbench for Windows”… the latest… and last… build
- Each Translation Unit contains a translation for each of the 25 languages… for example:
So this is a little different to the TMs you might normally encounter that only contain the source and target languages but still a valid format for any tools that support a multilingual TMX.
Now that you have it, let’s consider the process of using this TMX in Studio.
Upgrading a Multilingual TMX
This is actually made really easy by Studio. All you have to do is use the Upgrade Translation Memories… route here:
Selecting this brings up a window where you can select the TMX file, then you click on Next. This brings up the screen where you can decide between three options… create a TM for each translation memory you are upgrading (you can do as many as you like in one go), group them together by language pair and create one TM for each language pair (you can have as many different types of supported TMs and different language pairs in each one) or a custom output. So if you were a Project Manager you might find it useful to select the first option and have TMs for all 25 language pairs created for you:
But if you only want one… say English to Greek… then it would be faster and more appropriate to select the Custom option and choose only this pair… in fact I added one for each direction as these might be useful reference TMs for anyone specialising in public health material:
I can then click on Next -> Finish and I see that both TMs have been created:
I can now the TMs in Studio and I see something like this which looks ok and is ready for use… actually takes me longer to explain it than it does to do it..!:
Now, upgrading always keeps English as one of the pairs as this was the original source… srclang=”EN”… but what happens if you decided that you actually wanted to extract a TM for a language pair that didn’t contain English?
Importing the TMX
This process is slightly different because you need to create the TM in Studio first… or use an existing one, and then import the TMX into it. Only the language pairs that are in your Studio TM will be extracted and imported from the TMX. However this does give you even more flexibility because working this way allows you to create language pair from this resource that does not contain English. So for example, if I work with Bulgarian to Norwegian I can create my Studio TM first (or use an existing one to skip this step):
Then I right-click on the TM in Translation Memories View and select Import:
That’s it… now I have a Bulgarian – Norwegian Studio TM from the ECDC:
So two ways to use the new Translation Memory provided into the public domain by the ECDC… both nice and simple.