The Black Box…

An interesting thing about Trados Studio is how easy it makes it for new users to save all their projects in one place, all their translation memories and all their termbases.  In fact it’s so easy that I’m absolutely certain many users never give these things a second thought as they start to get to grips with using the software itself.  But then, one day, these users upgrade… in some cases even the upgrade seems to happen automagically… and then the problems start.  After becoming a competent Trados Studio user, excited to try the latest version, all of a sudden the translation memories, termbases and projects are all gone!  Lost inside the black box otherwise known as Trados Studio!

Regular readers of this blog over the years may recognise this theme as I have addressed this idea of Trados Studio losing files in the past.  But it was nearly 7-years ago (hopefully you’ve found your files by now) and for sure we are seeing a lot of new users in the RWS Community who are upgrading for the first time, so I thought it would be a good idea to breathe some life into my previous article (it’s still relevant) and also specifically address the questions I’m seeing recently around upgrading.

Translation Memories

Where are they?

So, first of all… Trados Studio is not a black box.

There’s a simple accessible pattern implemented with each installation.  Every time you install a version of Trados Studio various default locations are created for you.

I’m not going to look back any further than 2015, but by default the location for your translation memories would be here:

c:\Users\[USERNAME]\Documents\Studio 2015\Translation Memories\
c:\Users\[USERNAME]\Documents\Studio 2017\Translation Memories\
c:\Users\[USERNAME]\Documents\Studio 2019\Translation Memories\
c:\Users\[USERNAME]\Documents\Studio 2021\Translation Memories\

The bad news, and this is one I think should be addressed by the software, is that when you upgrade from one version to another the “upgrade wizard”, and I use this term loosely, does not check to see if you have any translation memories in these “known” locations and offer to move them for you.  So when you upgrade you won’t find the memories you were working with previously readily available for you.

The good news is that Trados Studio is not a black box so if you’re smart you simply won’t use these default locations.  Instead you would, in my opinion, be better off putting your translation memories into a folder somewhere of your choosing.  It really doesn’t matter where, so you could do this for example:

c:\Users\[USERNAME]\Documents\Trados\Translation Memories\

Here I have a folder called “Trados” that is not version related, and it’s not created by the software.  If I put my translation memories in here then I always know where they will be because I have taken control of them myself.  Now when I upgrade I simply point to this known location that won’t change whenever I need a translation memory.  Simple.

Another important thing to note when upgrading to Trados Studio 2021 is that some really useful features that were in all previous versions of the software have been removed and placed into the AppStore instead.  I covered this in an article called “Some you win… some you lose” when the 2021 version was released, but I’ll just mention the parts related to translation memories again here.

Missing features in Trados Studio 2021

But first… a quick note on making sure you get the right version from the AppStore.  There has already been several versions for Trados Studio 2021 released, and because of changes to the product in each release you must pay attention to always download and install the correct version of the app for the version of Trados Studio 2021 you have.  I’d also recommend you do this via the AppStore and not using the integrated AppStore in Trados Studio because it’s not an sdlplugin and controlling the versions is harder.  When you download the app these are your choices:

  • (2021)
  • (2021 SR1 CU5+)
  • (2021 SR1 CU7+)
  • (2021 SR2 CU8+)

The version numbers for the app are same as for Trados Studio, so just look under Help -> About in Trados Studio to see which version you need.  At the time of writing,  the version which I have installed is as we’re up to SR2 CU9.  So I’ve installed the last one in this list since it’s greater than 2021 SR2 CU8.  The installation itself should only take around 30 seconds at most… so no real hardship, just a little annoying.

So, what do we get once we’ve installed this app.?

Upgrading TMs

The app will bring back the Upgrade Translation Memories feature which you can use for several really useful purposes. First you can convert translation memories in the TMX/TXT/TMW/MDB formats into an SDLTM; and secondly you can merge translation memories in the SDLTM/TMX/TXT/TMW/MDB formats into one or more translation memories, even grouping them by languages.  This latter feature is brilliant and was one of the well hidden gems within Trados Studio which is now even more hidden as it’s an app.  You might enjoy this video explaining how it works if you’ve never seen this before…. it’s 8-years old, and I think I had a cold when I recorded it so the sound is very poor but it’s still one of the most popular videos I ever made.  Installing the app will bring this feature back in Trados Studio 2021.

I’d also note that this “Upgrade Translation Memories” is not to be confused with the brilliantly named “Upgrade Translation Memory” when you right-click on a TM in the Translation Memories View:

This one will be there out of the box and will be greyed out unless you see the small orange triangle on the TM icon to the left of the TM name.  I’d also note that just because you see this it doesn’t mean you have to “upgrade”, it just means you can if you choose to.  You can use a TM from Trados Studio 2009 without “upgrading” in Trados Studio 2021 if you really want to!  This “upgrade” will re-index your translation memory, build a translation model and align the translation units (units created from fragments extracted from the model).  To get better performance with your TM you might be advised to try it as it effectively ensures that changes to Trados Studio in this new version that could affect translation memory leverage, and the ability to use fragment matching, will be implemented.  You could also re-index the TM without the “upgrade” by opening the TM settings and selecting “Performance and Tuning“.  If your TM already contains several hundred thousand translation units you might prefer to do this anyway since adding additional aligned fragments for fragment matching will bloat your TM significantly, and if your TM is really large the process can take hours to never completing at all!  But the re-indexing part is always important to maximise leverage benefits from your existing translation units.

So definitely not the same “upgrade” as the one the app from the AppStore puts back!

Quick Upgrade

The other very neat feature that used to be available was the “Quick Upgrade”.  This allowed you to select a TMX/TXT/TMW/MDB translation memory when you created a project and convert it to an SDLTM on the fly:

This feature is no more I’m afraid.  Not even the app will put this back.  I can’t help feeling this was an oversight to remove these features, especially if they never put them back.  Whilst I’m sure TXT/TMW/MDB are probably not used very much anymore, TMX is certainly used and retaining the feature just for this format alone would have been desirable… in my opinion.


Where are they?

So, once again… Trados Studio is not a black box.

This time, when you install Multiterm, irrespective of the version of MultiTerm you install you should find a folder has been created in this location:

C:\Users\[USERNAME]\Documents\SDL\SDL MultiTerm\Termbases

Whenever you upgrade, if you use the Open Termbase command in Multiterm and choose “Browse” you should find that any termbases you created without paying attention to where they went will be in here.  So this is somewhat more logical than Trados Studio in this regard, but you can still create and save your termbases anywhere you like.  For example, you could do this if you wanted to:


Now I have a folder called “Trados” that always contains my termbases and my translation memories.  Makes my life a lot easier!

On upgrading specifically… not really much to say here.  Quite often I read users saying they need to upgrade their termbase from one version to the next.  In reality this should not be needed.  If you were upgrading from the old 2007 and earlier versions then yes, this would be needed and the process is well covered in the migration guide in Trados Studio..  But since 2009 upgrading termbases has never been required.  So if you can’t use the same termbase you used in 2017 or 2019 when you upgrade to 2021 then something is wrong and the best place to go is here and ask for help… the RWS Community is free!

If you’re looking for the migration guide I just mentioned, you’ll find it here:

c:\Program Files (x86)\SDL\SDL Trados Studio\Studio16\Documentation\en\Trados_Studio_Migration_Guide_en.pdf

Only available in English.


Where are they?

And again… Trados Studio is not a black box.

I’m still not going to look back any further than 2015, but by default the location for your Trados Studio Projects would be here:

c:\Users\[USERNAME]\Documents\Studio 2015\Projects\
c:\Users\[USERNAME]\Documents\Studio 2017\Projects\
c:\Users\[USERNAME]\Documents\Studio 2019\Projects\
c:\Users\[USERNAME]\Documents\Studio 2021\Projects\

However… I’m going to start by recommending you DO NOT migrate unfinished projects if you can avoid it.  The reason for this is that there may be changes made to filetypes, TM leverage, various settings with the application that just might be the source of a problem for you. Most of the time you won’t have any problems at all, but I’d still recommend you complete existing projects before upgrading if at all possible.

If you need to access old projects in the new version you upgraded to it’s simple… just use the Open Project button, or the keyboard shortcut Ctrl+O, in the Projects View to select the project file, *.sdlproj:

For the avoidance of any doubt, and if you still didn’t read this article, your project consists of various different types of files.  The only files that contain the translations are the SDLXLIFF files.  The SDLPROJ file is a sort of table of contents and it just tells Trados Studio where to find the SDLXLIFF files, translation memories, termbases and other resources that were used in your project.  So to open your old projects in a new version of Trados Studio you just open the SDLPROJ as explained above and Trados Studio will do the rest.

Keep in mind that when you do open old projects your Project Settings for these old projects will be settings based on the older version of Trados.  So don’t use these to create new project templates, and don’t use these as the basis for creating new projects!

So yes… in my opinion that also means you can avoid potential problems after upgrading if you recreate your project templates and don’t use the ones you’ve been using for years in older versions.  Might be painful I know, especially if you have a lot, but until the “upgrade wizard” in Trados Studio handles these things in a nice elegant fashion your best bet is to play safe and also start afresh.

I’d also add that this is most important when moving from major version to major version… so the 2017 version to the 2019, and the 2019 to the 2021 for example.  Things should be less likely to break when updating within the same major version, so from CU1 (Cumulative Update) to CU3 for example, or from SR1 to SR2.

Moving Projects

I’ll just touch on this topic briefly.  Trados Studio Projects are not always stored in the default locations I mentioned above.  This is for possibly three reasons at least:

  1. when you created the project you specifically chose a location somewhere else in the wizard:
  2. you use project templates with different locations for projects defined in the template:
  3. you work with the single document translation workflow and save your projects in the same folders as your customers files.  There are no settings for this, it just happens when you create single file projects, for example:

If you work like this then moving projects means you will have to find all the locations on your hard drive and move them manually by copying all the project files (SDLPROJ, SDLXLIFF etc.).  This might be a fairly difficult thing to do if they are all over the place.  So it’s worth giving this a little thought when you consider how you wish to work, and that you may at some point in the future wish to back up all your projects, or move onto another computer.  You also need to think about making sure that a new computer follows exactly the same folder structure to make it easy to switch between them… but that’s probably better discussed in the RWS Community as there are many users who are really well organised and expert in this sort of task… and they are always happy to share their knowledge if you ask!

RWS AppStore and Plugins

To finish off… and I didn’t mention this at the start… what do you do about apps?  There are basically two types of apps that work with Trados, identified by their installer:

  2. MSI or EXE (inside a ZIP)

Both types probably always need to be installed again if you upgrade from one major version to another (Trados Studio 2019 to 2021 for example).  In theory upgrading within a major version between CU’s or SR’s should not require reinstallation.  But there are two reasons why this may not be the case:

  1. the APIs were updated with what’s known as “breaking changes”.  This basically means the changes are non-backwards compatible so the apps will need to be rebuilt to work in the new version of Trados Studio for example.
  2. the apps were built using non-public APIs.  Developers “should” always use the public APIs as these should be supported without a breaking change most of the time.  Developers can find all the API’s available for RWS products on the developers website.  But sometimes, it’s impossible to create the amazing stuff we see available in all the apps without breaking this rule and this can mean any update is a risk as the non-public APIs used are not guaranteed to work in the same way.

So how do you handle this as a user?  There are many nuances to this, but the best advice I’m going to give is always uninstall your apps before upgrading using the plugin manager if they are SDLPLUGIN apps:

If they were MSI/EXE installers then you will need to use the Windows Control panel and remove the apps there as they are essentially applications in their own right that just happen to add stuff to Trados Studio:

Then, upgrade Trados Studio.  Once the upgrade is complete download each app from the AppStore again, making sure that the apps supports the version of Trados Studio you have upgraded to.

If the apps you use are all SDLPLUGIN files then you can use the integrated AppStore in Trados Studio to reinstall.  This is not only faster, but it will also ensure that you always install the correct SDLPLUGIN for the version of Trados Studio you are using:


I guess the main message here is know your software, understand your folder system and definitely become comfortable with file management.  Once you’ve done this life is simple… especially since Trados Studio is not a black box!

Social sharing, kindle or email....

Introducing the multilingual XML… super filetype!

I was compelled to make a return to a previous theme around Marvel Comics because it’s the only way I can do justice to the amazing work the RWS AppStore team carry out on a daily basis.  There are some things you just can’t wait to get up in the morning for, and for me, one of these things is being able to work with this team on a daily basis.  The first meeting of every day for me is with this team and what a fantastic way to start the day it is!  I started this article by mentioning Marvel, but as you’ll see, the hero of this story is probably a Honey Badger!

Continue reading

Social sharing, kindle or email....

Let’s learn about XML…

This year at the Spring Trados Roadshows the emphasis was firmly placed upon education.  Almost all the presentations were based on providing translators, project managers, localization engineers etc. with great material to help them as they work with the Trados toolsets.

I had a few presentations at this event and decided it might be useful to post a few of them here, especially the ones that might help with some of the common filetype questions we see in the communities from time to time.

Continue reading

Social sharing, kindle or email....

What’s in a name?

“What’s in a name? That which we call a rose
By any other name would smell as sweet.”

In Shakespeare’s soliloquy, Romeo and Juliet, Juliet isn’t allowed to be with Romeo because his family name is Montague… sworn enemies of the Capulet family.  Of course she doesn’t care about his name, he’d still be everything she wanted irrespective of what he was called.  The rose would still smell as sweet irrespective of what it was called.  “Trados”, “SDL” and “RWS” have endured, or enjoyed, a feuding history as competitors in the same industry.  Our names are our brand and now that they’re changing do we still smell as sweet?  Sadly things don’t end well for poor Romeo and Juliet… but in our story we fare a little better!

Continue reading

Social sharing, kindle or email....

A file with a view…

I started thinking about “A room with a view” by E. M Forster when I contemplated how to start this article.  But as you can see from the images on the left my mind wandered from this idea and was focused more on the “view”.  This is quite possibly because our R&D team started a “Working from home” distance challenge to cover as much distance as you can every day for a month by physically getting out of your office/home and taking some fresh air.  A great initiative in these days of working from home where it’s all too easy to never leave your desk!  Walking, running, cycling and even swimming were acceptable activities and you get the distance converted into points based on the type of exercise you are doing.  You do have to track the activity and you have to take a few pictures as evidence of your efforts… but that brings me back around to my topic for the article… the pictures, or more specifically the views.  Yes, this is a very tenuous link indeed with the actual topic which is studioViews!

Continue reading

Social sharing, kindle or email....

Short term memories…

“Not only is my short-term memory horrible, but so is my short-term memory.”  I have no idea who this quote can be attributed to, and its certainly not original, but it is quite appropriate when I start to think about the evolution of Trados.  Ever since Trados Studio was launched you can be sure to find many “experts” in places like ProZ and even the SDL Community recommending you don’t upgrade because there is no difference compared to the last version.  To be fair, if you only use a fraction of the features despite having used the software for a decade, then it probably is like this.  The alternative being these “experts” have very short-term memories.

Continue reading

Social sharing, kindle or email....

Psst… wanna know a few more things about file types?

I wrote under this title back in 2013 and provided a bit of information about the Word filetypes in Studio.  It was a pretty popular article and I always meant to circle back and do some more.  Seven is a lucky number so now we’re in 2020, seven years later, I thought I’d do it again… and it’s also just as long, so grab a coffee first!

Continue reading

Social sharing, kindle or email....

A Private AppStore…

All the apps come in these places
And the apps are not the same
You don’t look at their faces
And you don’t ask their names
You don’t think of them as human
You don’t think of them at all
You keep your mind on the money
Keeping your eyes on the wall
I’m your private AppStore, I don’t cost no money
I’ll do what you want me to do…

Every time I think the words “Private AppStore” that song comes into my head and leaves me with an earworm for a while.  Funny, but true!

Continue reading

Social sharing, kindle or email....

Some you win… some you lose

When we released the new Trados 2021 last week I fully intended to make my first article, after the summary of the release notes, to be something based around the new appstore integration.  The number of issues we are seeing with this release are very low which is a good thing, but nonetheless I feel compelled to tackle one thing first that has come up a little in the forums.  It relates to some changes made to improve the product for the many.

Continue reading

Social sharing, kindle or email....

Not your usual stuff!

Time seems to be going faster as I’m getting older as it doesn’t seem that long ago since we saw the release of the 2019 version of SDL Trados Studio.  But here we are, it is that time again and many users will already have noticed they have a shiny new version in their account… SDL Trados Studio 2021.  Fast as it is, we don’t want to do these product launches too often because I can tell you it’s a major undertaking requiring no small amount of coordination between the product management teams, core development teams, AppStore team, support teams, customer success teams, marketing teams, sales teams, back office teams, IT teams, 3rd party developers who provide plugins and more.  In addition to this we often have other projects on the go and many of the teams worked on the new website which also went live this week, AND everyone did all of this while having to work isolated from their colleagues while working from home.  Quite an achievement and I certainly feel proud to be part of this SDL team, and not just because of how well they all work together.

Continue reading

Social sharing, kindle or email....