Welcome to Translation England: your first stop for quality Spanish to English translation, subtitling and proofreading services
Translation England
  • Home

Comparing Trados and MemoQ in terms of…terms

29/7/2014

11 Comments

 
This post compares the terminology management functionalities of SDL Trados Studio 2011 (hereafter referred to as Trados) and MemoQ Translator Pro Edition (hereafter referred to as MemoQ). It might be useful for beginner-intermediate users of CAT tools.
N.B. SDL have released an updated version of Trados (SDL Trados Studio 2014), which I have not experimented with. I apologise if any of the comments I make for 2011 are no longer relevant to the new program.

Trados

Terminology functionality in Trados is achieved through the additional standalone program, MultiTerm Desktop. At first glance, this interface appears neat, well-organised and reasonably user-friendly. However, one soon realises that MultiTerm, like Trados, is a complex program. Once the user learns to manoeuvre such complexities, this may be considered as a virtue, but for the beginner or non-IT expert, it can be quite confusing.

An example of this is Step 5 of 5 of the Termbase Wizard, which asks the user to create an Entry Structure. Whilst this provides a rich amount of detail and personalisation to a TB, it is certainly not something the user can pick up and start using quickly. Indeed, if one makes a mistake in designing the TB Definition File, it is difficult to rectify later on, and components such as languages and descriptive fields cannot be deleted easily after creation.

In the main MultiTerm interface window, it is fairly easy to add, edit and save terms using the shortcut keys F3, F2 and F12 respectively. Adding information to other descriptive fields is carried out by clicking on the small arrows, although it could be argued that this system is not particularly intuitive, as highlighted in Fig. 1 below. A table structure might have been clearer, as is the case of MemoQ.
Picture
Fig. 1: Screenshot of a term being edited in MultiTerm
It is worth mentioning that, depending on the SDL package, there are a number of additional extras which may aid the process of entering terms. The MultiTerm Widget, for example, allows quick searching of terms by connecting with such websites as Google, Wikipedia and Linguee. However, it is debatable how much time this actually saves, as the widget is not linked directly to MultiTerm or Trados. Indeed, one might contend that the same result could be achieved by merely opening an internet browser.
Picture
Fig. 2: Screenshot of MultiTerm Widget linking to Wikipedia
Still, MultiTerm Desktop has a wide variety of functions at its disposal. It has three search types including a Fuzzy Search (a notable omission from MemoQ), three search Modes (Hierarchal, Parallel and Sequential) and five layout styles, among other options. However, for all these additional details, SDL might well have opted to focus more attention on the usability of the interface itself. For example, if one accidently closes the Hitlist, it is not immediately obvious how to retrieve it, despite it being arguably one of the most important aspects of the program from the translator’s point of view.

Away from MultiTerm and into the main translation editor, terms can be added to the TB by double clicking on them and pressing CTRL+F2. There is a second or two lag when saving terms but in general, this system of adding to the TB is fairly easy to use. However, there are a few areas in which one might expect more from one of the market leaders in CAT tools. Firstly, the system is not particularly intuitive with regards to case-sensitivity. For example, the Spanish word “despúes” (“after”) has been entered into the TB. However, as “Después” starts with a capital letter, typing an “A” does not lead to the quick auto-insert prompt. The same applies when a word is added into the dictionary with a capital letter. This is shown in Fig. 3 below with the entry “Perspectives”, as typing the letter “p” in lower case does not prompt the auto-insert suggestion.

Another example is the lack of recognition of lemmatised forms. For example, the Spanish verb “incluyeron” is a 3rd person plural conjugation of the verb “incluir” (“include” in English). Unfortunately, despite both base forms appearing as an entry in the TB, auto-insertion suggestion does not appear for “incluyeron” in the translation editor. Whilst these issues may only prove to be relatively minor complications, they are worth mentioning as they could potentially add up to significant amounts of time in the long run.
Picture
Fig. 3: Screenshot showing case-sensitivity and lemmatisation issues in Trados
It is also disappointing that, although multiple TBs can be selected for viewing in Trados, the system only suggests terms from the TB which is selected as default, as displayed in Fig. 4 below.
Picture
Fig. 4: Screenshot showing a TB, not selected as the default, failing to suggest terms for auto-insertion in Trados
It is sublanguages, however, that has been my biggest concern when using Trados. This issue becomes immediately apparent while creating a project. Whilst in MultiTerm, the user is able to select languages in their general form (for example, “Spanish” as opposed to “Spanish (Spain)” or “Spanish (Mexico)”), this option is not available when choosing project languages in Trados. Unfortunately, this means that TBs for general languages will not function for sublanguages even if the general language is the same.

At this stage, MultiTerm can, of course, be opened, and new sublanguages can be added to the TB. However, old terms must be copied from the general language to the sublanguage in order for them to be accessible in Trados; a time-consuming and tedious task. Also, new terms entered from within the Trados interface will only be available in the sublanguages of the project. Back in MultiTerm, they will not appear on the Hitlist, given that these sublanguages were not part of the initial languages stipulated in the Definition File. Understandably, this is extremely frustrating.

It should not be underestimated how important this limitation is, and it may well be considered as a key reason not to choose Trados. A translator working in Latin America, for example, might receive Spanish TBs in general Spanish, Argentinean, Chilean and Mexican, but unless the source file shares that specific sublanguage, he/she will not be able to use them easily.
Picture
Fig. 5: Screenshot showing there is no “general Spanish” option when starting a project in Trados
Picture
Fig. 6: Screenshot showing that terms from a “general Spanish” TB do not appear in Trados
On the positive side, Trados contains features such as checks to verify whether potential terms from TB have been inserted. Moreover, the Studio package has a greater deal of flexibility than MemoQ with regards to the variety of files that it can import and export. This is enhanced by its additional program MultiTerm Convert, which helps change a diverse number of file types into those readable by MultiTerm, although this can be frustratingly time-consuming. Indeed, another example of user-friendliness being compromised while importing and exporting is the compulsory creation of log and exclusion files, which can be complicated and confusing for the non-expert user.
Picture
Fig. 7: Screenshot showing TB verification settings in Trados


MemoQ


MemoQ immediately comes across as more simple and user-friendly in comparison to Trados, reflecting Kilgray’s desire to develop a tool to suit the needs of translators. Indeed, MemoQ’s terminology management system is integrated into its main application, which is extremely helpful for the user as it allows quick and easy switching between the translation editor and TBs (incidentally, MemoQ also works faster than Trados, requires less CPU usage, and takes up less hard disk space). Whilst at first glance it may appear quite simple, most of the same operations can still be carried out in MemoQ. An example of this is the interface for adding and editing TBs, a table structure which translators may find clearer to use than Trados.
Picture
Fig. 8: Screenshot showing pictures being added to a TB
Within its main translation editor, MemoQ is not radically different to Trados regarding the insertion of terms from a TB. However, it does manage slight improvements in a few important areas. For example, entering terms into a TB from within the translation window is simpler and faster than in Trados as there is a “Quick Add Term” function, which adds and saves two selected terms automatically by pressing CTRL+Q. This means that new terms can be added in about 5 seconds as opposed to approximately 15-20 seconds in Trados.

MemoQ also offers improvements to the previously mentioned case-sensitivity issues in Trados. Furthermore, and significantly, it allows users to insert lemmatised versions of words, and suggests them for auto-insertion, even though their forms might not be identical. Therefore, as in the previously mentioned example, “include” appears as a TB suggestion for the Spanish conjugated form “incluyeron”, which did not occur in Trados. This is certainly a bonus for the translator and may acquire especial importance for those translating highly inflected languages such as Spanish.
Picture
Picture
Figs. 9+10: Screenshots showing case-sensitivity and lemmatisation functions in MemoQ
As well as TBs, MemoQ has the potential to enable add-ins such as the EuroTermBank plugin, which offers suggestions for words that may not be in the TB. Whilst the EuroTermBank is fairly simple and the translator will probably know all of the words already, it does hint at a great deal of potential. Indeed, a possible next step for Kilgray could be to establish connections with popular online dictionaries such as Linguee and WordReference, directly linking such vast arrays of resources to the MemoQ translation editor.
Picture
Fig. 11: Screenshot showing relatively easy terms found in MemoQ’s EuroTermBank plugin
However, where MemoQ truly excels in comparison to Trados is the fact that its works across sublanguages. Regarding terminology management, terms in a “general Spanish” TB will therefore function in a “Spanish (Spain)” project and terms in a “Spanish (Mexico)” TB will function in a “Spanish (Spain)” project. Furthermore, as mentioned earlier as one of the limitations of Trados, multiple TBs can work simultaneously in MemoQ, meaning less inconvenience for the translator when selecting more than one TB.

Another aspect worth mentioning is terminology extraction. MemoQ benefits from a rather useful extraction tool, which enables the user to locate and add potential terms before translating a text. Admittedly, Trados does offer a separate program, MultiTerm Extract, which essentially performs the same function. However, this comes at a quite hefty price indeed: $500.
Picture
Fig. 12: Screenshot of MemoQ’s Terminology Extraction tool
Picture
Fig. 13: Screenshot of SDL’s MultiTerm Extract


Conclusion


Both SDL Trados Studio 2011 and MemoQ Translator Pro Edition are useful translation systems, and terminology management functionalities constitute fundamental aspects of such tools. However, MemoQ most definitely offers greater value for money than Trados. Indeed, although Trados may be regarded as the industry leader, it is difficult to find significant objective reasons to choose it over MemoQ, other than if it were to be required by a certain company or task. MemoQ is considerably easier to use, whilst at the same time managing to carry out the vast majority of the same tasks as Trados to the same or better degree. Most significantly, in the context of terminology management, MemoQ’s TBs do what Trados’s do not: they work across sublanguages, an aspect which SDL might want to think about addressing in future versions.
11 Comments
Paul Filkin link
25/7/2014 12:02:18 am

Interesting article, but in my opinion doesn't really address terminology management which MultiTerm addresses in ways memoQ cannot. I would make a few comments though.

First on this; "MemoQ’s TBs do what Trados’s do not: they work across sublanguages, an aspect which SDL might want to think about addressing in future versions." All you have to do is create the termbase for a general language and then they can be used for whichever sublanguage you like. This has always been the case in MultiTerm. You would only use a sublanguage when creating your termbase if it was important for you to maintain a termbase with this distinction.

The "Glossary Converter" and the "Glossary Converter Plugin" which are tools developed using the Studio platform have virtually removed the need to use MultiTerm Convert completely for the vast majority of users. They make the manipulation of data around termbases in any structure (not just a predefined fixed model) extremely simple for any user, and extremely functional.

The MultiTerm Widget is really designed to be a tool for anyone who does not have MultiTerm installed. They can use this to look up their companies terminology resources in MultiTerm termbases, or websites if they wish, in a simplified way.

When using multiple termbases it's incorrect that only the default termbase returns terms. There are various settings around this and if you are experiencing this, as you clearly are, then it would probably be worth seeking help to resolve your problem.

I also think you need to look at your autosuggest settings as one of the main usecases for translators is to use Multiterm as a productivity booster rather than a true terminology resource, and your screenshots show something that should work - maybe this is also a setting somewhere?

You are correct when you state that in Studio 2014 things may be different, particularly around the rapid introduction of the integration API. This allows external developers to plugin into the Studio application without needing SDL to do it it. So you can probably expect to see more plugins for different terminology providers in the future.

I completely agree with you on the integrated terminology extraction in memoQ. This is very handy as you need a separate tool in MultiTerm for this called MultiTerm Extract.

But in general, especially with the creation of the "Glossary Converter" I think working with Terminology in MultiTerm has never been easier... probably far easier than in any other tool... in my opinion!

Reply
Nicky Bremner
25/7/2014 01:21:12 am

Hi Paul,

Thank you for your comments. You are clearly very knowledgeable about your CAT tools and TBs!

I understand what you're saying about the sublanguages but it just doesn't seem to work for me. If the TB is general and the project languages are specific the TB doesn't work or at least I haven't been able to get them to work through my experiments. There may be a workaround but what I like about MemoQ is that these little things just work.

Regarding the issues that "should work", I can only speak from my experience translating real texts and coming across issues like multiple TBs not functioning correctly, lemmatisation etc. There may be a way of fixing these annoyances in Trados, but it is interesting that they work straight away in MemoQ.

I've just been repeatedly disappointed with Trados and pleasantly surprised with MemoQ so have kept using it. Sounds like you've had a more positive experience!

Anyway thanks again for your comments.

Reply
Paul Filkin link
25/7/2014 01:51:49 am

Hello Nicky,

If you have time, and the interest, I'd be happy to take some time to look at the problems you're having?

Regards

Paul

Reply
Paul Filkin link
25/7/2014 01:52:49 am

Hello Nicky,

If you have time, and the interest, I'd be happy to take some time to look at the problems you're having?

Regards

Paul

Reply
Remy link
29/7/2014 02:14:58 am

Being a Swiss LSP we constantly deal with sublanguages (Swiss German and the Swiss French are different from the "official" German and French). And we never had troubles with Multiterm in that respect.
The main issue with Multiterm is currently that it's built on Java and this seems to cause endless troubles. But this should be solved in the next version I heard.

Reply
Luis Lopes link
30/7/2014 03:22:40 am

Hi,

I'm the Product Manager at SDL for SDL MultiTerm. Thank you for the article, it's interesting and helpful.

However there are a few factual errors:

- Terminology functionality in Trados is achieved through the additional standalone program, MultiTerm Desktop.

This is possible both from within Studio as well as standalone. Many users are terminologist and don’t want to install a full translation suite just to manage terminology, as they don’t translate documents.

- The MultiTerm Widget, for example, allows quick searching of terms by connecting with such websites as Google, Wikipedia and Linguee. However, it is debatable how much time this actually saves, as the widget is not linked directly to MultiTerm or Trados.

MT Widget plugs into file-based as well as server-based MultiTerm Termbases. This is the main use case for the tool, the websites you can plug-in are just additional resources.

- Still, MultiTerm Desktop has a wide variety of functions at its disposal. It has three search types including a Fuzzy Search (a notable omission from MemoQ), three search Modes (Hierarchal, Parallel and Sequential) and five layout styles, among other options.

The 5 layouts are standard layouts we ship with the product, you can actually create as many custom layouts as you want.

- It is also disappointing that, although multiple TBs can be selected for viewing in Trados, the system only suggests terms from the TB which is selected as default, as displayed in Fig. 4 below.

This is incorrect. Studio give you three options to sort terms found, hierarchically until a match is found, all in parallel and results grouped by term or sequentially and results grouped by term.


- Whilst in MultiTerm, the user is able to select languages in their general form (for example, “Spanish” as opposed to “Spanish (Spain)” or “Spanish (Mexico)”), this option is notavailable when choosing project languages in Trados. Unfortunately, this means that TBs for general languages will not function for sublanguages even if the general language is the same.

This is again incorrect and possible. Studio allows you to map any language to any language manually if needed. The flexibility even allows you to map English to German if you wanted to for whatever reason.

It would be great if the article could be corrected or followed up by another article.

@Remy: Yes, we are working on the Java topic.

Thanks,
Luis Lopes
Product Manager SDL

Reply
Riccardo Schiaffino link
12/8/2014 10:06:55 am

Hi Nicky,

Thank you for the very useful post. One thing worth mentioning about Multiterm is that while it is indeed a very powerful program, and while there are those who claim it is "easy to use" (as Paul does here in the comments), anybody that should need to learn it from Multiterm documentation is just out of luck.

Powerful the program may be, and easy to use it also might be for those who already know how to use it.

Trying to learn how to perform even the most seemingly straightforward operation in Multiterm from its documentation is an exercise in frustration. Multiterm documentation is probably very complete. It is also a complete mess that is definitely not designed with the average user in mind.

Paul's take is that for many operations now there are external applications available that make things easier - and, as far as that goes, it is true: they do.

But the fact that some user got so frustrated with Multiterm that he decided to create program to make easier such a basic function as importing an Excel or txt glossary speaks volumes about how really user unfriendly Multiterm is.

Riccardo Schiaffino
www.aboutranslation.com

Reply
Salley link
22/10/2014 04:27:55 pm

Hi

Thank you for this useful information.

I am currently using Trados 2011. Last year, I tested several CAT tools including Dejavu and MemoQ for one of my clients who wanted to used a CAT tool for their in-house translation projects. The critical problem for MemoQ was that some characters were corrupt in Korean OS environment. I contacted the vendor, but they did not provide me a correct solution for the issue. Which do you think is better between MemoQ and Dejavu? (I actually recommended Dejavu to my client, but they chose Trados in the end.)

Salley
http://www.experiencingwmscog.com

Reply
Nicky link
23/10/2014 11:16:49 am

You're welcome Salley. I understand what you mean about the corrupt characters. In certain circumstances the Spanish characters can become corrupted. I've found certain workarounds (playing with the Unicode settings for example), but I'm certainly no expert. Perhaps there is a workaround for MemoQ to get Korean working. It would surprise me if there wasn't. As for DejaVu, we experimented with it briefly on the Master's, but not in as much detail as the Trados or MemoQ. It is highly recommended, but by that time I was starting to like MemoQ and I was so traumatised with how bad Trados was that I stayed with MemoQ. But the general opinion of our tutors who are professional translators was that DejaVu was probably the best. I'm happy with MemoQ as it fits all my needs, but I would have a play and see which one you like best. As you say the choice might be taken out of your hands.

Reply
Mariam link
24/11/2020 01:28:30 am

Good postt

Reply
Jonathan Hemming link
25/11/2020 02:04:42 pm

Hello Mariam.
Thanks! Which CAT tool do you use?
Jonathan

Reply



Leave a Reply.

    Translation England

    We translate between Spanish and English.

    We do subtitles and proofreading too.

    Translation Blog Home:
    Click here!


    Archives

    May 2017
    June 2015
    May 2015
    March 2015
    February 2015
    August 2014
    July 2014
    June 2014
    January 2014

    Categories

    All
    Applied Translation Studies
    Audiovisual Translation
    Audiovisual Translation Studies
    CAT Tools
    Certified Translation
    Colombia
    CPD
    Freelance
    Institute Of Translation & Interpreting
    ITI
    Leeds University
    Luis Suárez
    MemoQ
    Peru
    Subtitle Edit
    Subtitler
    Subtitles
    Subtitling
    Trados
    Translation
    Translation Problems

    RSS Feed

Picture
Translation England
jonathan@translationengland.com
Copyright © 2013-2023 Translation England