Nov 16, 2012

Trados 2007 goes to the guillotine - or not?

A recent Twitter exchange reinforced the impression of confusion I had regarding SDL's intentions with the older Trados technology. Many translators, corporate users and language service brokers continue to use the 1990s technology of Trados 2007 (which is the current translation technology of many EU institutions until it is finally phased out starting in the coming year), and recent troubles with the loss of "bilingual DOC" exports in memoQ 6.0.64 brought the matter of the old technology to a very uncomfortable head. (Earlier builds of memoQ must be used, or one must be patient until after the version 6.2 release, when this feature will be re-developed.)

The exchange with the colleague on Twitter as well as the frequent contradictions in ongoing discussions among my friends and clients in the translation world made it clear that definitive answers were needed to abate unnecessary fears and allow people to plan the future of their processes with proper information. So I talked to Paul Filkin, Client Communities Director at SDL,whose Multifarious blog is my favorite resource for reliable information about the technical arcana of Trados.

[KSL]: Judging from a recent Twitter traffic, there seems to be some confusion regarding SDL’s plans to discontinue support for SDL Trados 2007. So tell me – are Trados Workbench and TagEditor going away for good at last?

[PF] It’s worth clarifying that we are talking about SDL Trados 2007 and not SDL Trados 2007 Suite.  The difference is that the Suite contains the latest version of SDL Trados 2007 (as well as various other applications) which is  But to answer your question specifically… no, Trados Workbench and TagEditor are not going away for good just yet.  I imagine there will still be users working with the older version of these tools for some time yet, but over time they will of course become obsolete – we just need to allow for that time.  The driving forces for anyone hanging onto these old versions will be development of hardware and new operating systems as well as upgrades to authoring systems that the retired versions will no longer be able to support.

[KSL]: What exactly ARE the difference between those two versions?

[PF] The best place to look for all the technical differences is the SDL knowledgebase where you can find a nice article called “What is new in SDL Trados 2007 Suite”:

[KSL]: If I am using SDL Trados Studio 2011 and my client expects T2007-style “uncleaned” files, what can I do?

[PF] The safest approach, because of differences between the old Trados versions is to ask your client to provide you with a fully segmented bilingual file, whether they are after TTX or Bilingual Doc.  SDL Trados Studio 2011 supports TTX and Bilingual Doc as a file type without the need for SDL Trados 2007 at all.  Your client should be able to provide these files for you because they have the appropriate software already.

The other alternative, if you don't have a copy of SDL Trados 2007 Suite which you can still purchase with SDL Trados Studio 2011 today, is to use a free application from the SDL OpenExchange called the SDLXLIFF to Legacy Converter.  This application can convert your Studio bilingual file to a Bilingual Doc or a TTX.  This process caters for two parts in this workflow.  First your client can edit these files in SDL Trados 2007 Suite and clean them into their Translation Memory, and second you can use the application to import the changes back into your SDLXLIFF so that you have the updated and approved version in your own Translation Memory.  You can get this application here:

[KSL]: What are the “dangers” in this approach? Where might it go wrong for my client?

[PF] You still have to provide your client with the “cleaned” file from Studio however because the Bilingual Doc or TTX created will not “clean up” into the fully formatted document you started with.  This is because the Bilingual Doc or TTX is created from the SDLXLIFF and not from the original source file.  

This also means that the SDLXLIFF has been segmented using the new file types in Studio and not with the old file types in Trados 2007 Suite or earlier so even though your client will be able to clean the file into their Translation Memory they may lose some ability to fully pretranslate the same source file using Trados 2007 Suite or earlier.  This is actually the same problem that could occur when converting the file using memoQ or WordFast for example but as those clients only provide the translator with the source file and not a pretranslated bilingual file in the first place this doesn't seem to be an issue for them.

So all in all both approaches seem to work… the important thing is to understand what your client wants to do with the file when they get it.

[KSL]: Can these formats be edited and “cleaned” by the client to create a properly formatted target (translated) file?

[PF] Only if they were prepared using SDL Trados 2007 in the first place.  There is no substitute for SDL Trados 2007 if the client wants a properly formatted target file and future leverage from their Translation Memory.

[KSL]: At what point can we expect support for TWB and TagEditor formats to be discontinued?

[PF] I think it’s likely that when we release the next version of the software SDL Trados 2007 Suite and SDL Trados Studio 2009 will be retired.  However, the important thing to note is that we have the Trados 2007 infrastructure built into Studio and this allows users to upgrade Translation Memories, handle legacy bilingual files and more importantly use the SDL OpenExchange to develop applications that will support workflows using the older tools.  We are already seeing developers looking at ways of improving their older solutions with Studio since we were awarded the EU contract last month.

[KSL]: Does SDL Trados Studio 2011 still include a version of TWB and TagEditor?

[PF] It’s not included automatically but you can still purchase it when you buy SDL Trados 2011.  It’s not sold as a separate piece of software anymore.

[KSL]:  That's good to know. Will this continue to be the case with the next release (Studio 2013???)?

[PF] The honest answer is we haven’t made a decision on this yet.  SDL Trados 2007 Suite is really only needed by people who have create, rather than use, these legacy files.  So in reality these people probably already have it… all they have to do is make sure they always prepare files for those who are translating them.  This may be better for them and for the translator.


  1. Thanks for clarifying things, Paul. One thing I've been missing in this whole discussion however is the issue of previews. Unless I misunderstand, I won't have a document preview in any scenario in which I pre-segment files myself or have the client do it for me. Nor will I be able to export the document to proofread it in its fully formatted form; I would have to ask the client to do this for me as well (which I have had to do quite recently in fact). So if like me translators are working on material where having a document preview/formatted export option is indispensable, there really isn't an alternative when working with clients using Trados 2007 to either importing the Word document myself, assuming my tool can export a fully formatted bilingual doc, or just working in Trados 2007 (Suite?) in the first place. Or is there some workflow I'm overlooking?

    1. Hi Susan, this is a good point. If you don't have Trados 2007 then Studio 2011 is the only application that will allow you to create a formatted target file from the TTX. You can't preview it as you are working, but you can create the target whenever you like for checking, and this is irrespective of the underlying format that was used to create the TTX in the first place... obviously you'd need the source application to see it!
      If the bilingual file is a bilingual word file then Studio can handle it for translation but it can't clean it to give you a preview... however we do have a free app on the SDL OpenExchange called tw4winclean that will do this for you -
      Does this help?

    2. Yes, thanks Paul, that's very helpful. So what I'm getting from this is that if things stay pretty much as is in terms of interoperability between the tools, I won't have much of a viable alternative to purchasing Studio 2011. Getting clients to preformat files if necessary at the start of a project is no big deal, but in the end phase when things are typically down to the wire it is a pain to try to catch them when they're in the office and have time to create the output file for review.

  2. Thanks Kevin and Paul for clarifymg this issue. However, what happens with the communication interface from tools like Apsic Xbench (and others) that have been developed specially with Trados TagEditor 2007 in mind?

    1. Hi Pablo, I'm not sure I entirely understand your question. Anyone using this will still be able to do so... in fact in some ways they will be safer because we won't be changing this anymore..! Just because we stop supporting the application doesn't stop anyone who already has it from using it if they wish.
      If you mean what do these users do if everyone adopts the Studio Platform then in this case ApSIC have already provided some support for Studio and I expect they will continue to improve this as time goes by.


Notice to spammers: your locations are being traced and fed to the recreational target list for my new line of chemical weapon drones :-)