It’s 2012 and you are still using Trados 2007?

The translation process dates back to ancient times but technology has changed our jobs and working methods quite a bit. CAT (Computer-assisted translation) tools make our jobs easier, more accurate and more efficient. Nowadays, in order to provide the client with a quote, the files first need to be analyzed, and based on word repetitions and matches against a TM (Translation Memory) or a previously translated document, the rates can be more competitive. For the sake of exemplifying how a CAT tool can save you a lot of grief, we’ll refer to one of our most recent upgrades: SDL Trados Studio 2011.

Since the launch of its previous version in 2009, we’ve been aware of the mixed reactions in regards to this software. We’d grown attached to Trados 2007 and also, we’d grown attached to our translators, who handled the same software as we did. Studio 2009 had come and gone, and only a few had dared to venture into its somewhat unknown territory. Also, translators can be tough cookies. The idea amongst a considerable amount of people was, and still is: If a tool works, why replace it? Why spend money on an upgrade you’re not sure you need?

I’m a baby compared to other people and their experience in this industry. When I started working full-time in translation, I was introduced to both Trados 2007 and Studio 2009. As I got to know both versions in an unbiased manner, I soon became baffled on how people continued working on a version that is now 5 years old. At this point in the history of technology, 5 years is a huge amount of time!

So, for all of you out there, still dancing around with the idea of upgrading from a 2007 version, (or older…or none of all!) here is a list of what are my whole-hearted honest opinions, experiences and discoveries about Studio 2009 and 2011, in contrast with Trados 2007. I am in no way the expert and truly welcome all the more knowledgeable people on the subject to speak out!

• Fully Integrated Interface: nothing made more sense to me but to have everything on one same platform. With Studio you can roam around like the master of the castle: all your projects, files, reports, TMs in one same place and easy to handle.
• In Trados 2007 I soon discovered that a false move can be devastating. Big accidents can happen. (And I mean big!) Studio is far from being accident-free but at least it blocks your path every time something wrongs pops up. However, discovering the error can be a hassle. I remember going ballistic on a project that I had gone back to edit after 6 months of having it marked as completed. I attempted to create new target translations but the options where grayed out. It had been a long day, the deadline was imminent and the minutes that I struggled not knowing what to do, were horrible. What was the problem? I had forgotten to “Reactivate” the project. Just a click.
• Tags could be a great problem when cleaning files in Trados 2007. In Studio, there is no way you can mess with them. You can even take them out from your sight if you don’t want to see them (Format>Tag Display Mode.) And if you want to input them into the target text, you can either copy the source to target or use the “QuickPlace” function, which applies formatting just by highlighting what you want where you want it.
• Much less DTP work with Studio! No more nightmares about tables, text boxes or bullet points.
• Need to make sure that you use a consistent translation? In Studio, you can filter segments out in either the source or the target text, in order to see every instance where a word or words are used.
• Use several TMs at the same time.
• Get leverage not only with the TM, but at the paragraph and document level.
• You can easily upgrade your old TMS to Studio based TMS (.sdltm)
• Pretranslate segments and lock them so that nothing that was reviewed and approved once is reviewed again.
• The concept of packages allows you to send out and return translation or review projects. It creates a folder structure, a package per target language, lets the user define tasks for individual packages and it allows to recompute word count or analysis for cross-file repetitions.
• Once your heart is set on something, override translations easily and maintain a clean TM.
• Multilingual projects.
• Track changes. This feature is only available in Studio 2011. It allows reviewers to mark their changes that can later be accepted or rejected.

I realize I may have spoken more about the positive attributes than the negative aspects. Not everything is sugar and cotton candy with Studio; there is still a lot of room for improvement. For example, I cannot speak for the increased functionality between Studio 2009 and 2011, as nothing has impressed me just yet. For some reason, my 2011 version is much slower than its predecessor. The project set up process seems a little more convoluted than it needs to be, especially for translators. And obtaining an analysis should be simpler.

Upgrading can be tricky if not everyone is on the same page. We are not going to dismiss all the translators whom we like and who deliver quality work, just because they haven’t upgraded. Sometimes, everyone on the translation team will have Studio, but not on the editing team. For these cases for example, there is such a thing called the SDL XLIFF Converter for Microsoft Office. The “user is then able to use MS Word application to review/edit the exported document and use the tool to import these changes back to the original SDL XLIFF file.” Pretty cool!

Like for a lot of translators out there, our company’s transition into Studio has been difficult. It has been slow, challenging, surprising, happy, frustrating and a million other things. It’s been complicated, but we have learnt to love the tool and we now wonder how we ever lived without it. A piece of advice, don’t be afraid to give it a try…


Tania Varela and the BeatBabel Team

It’s 2012 and you are still using Trados 2007?