I believe this interesting quote can be found in “Prometheus Bound”, a play by a Greek dramatist called Aeschylus. I haven’t read the play, but I like the quote, and it certainly lends itself to the importance of memory… even when we refer to a Translation Memory rather than your own built in capability. It’s because your Translation Memory is such an important asset to you that you need to regularly maintain it, and also reuse it wherever possible to expand the benefits you get from it.
People often tell me that using Studio is complicated. Other people, who have been working with Studio tell me it’s actually quite logical once you get your mind around it. I clearly lean towards the latter and whilst I always try hard to see the difficulties the conclusion I always come back to, rightly or wrongly, is that many users who used Trados in the past expect Studio to be similar and then struggle when they discover it’s not.
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.
Updated January 2015 : Also possible, and easier, to use the Variable Manager from the SDL OpenExchange for this.
I mentioned in a previous post that it wasn’t possible to import long variable lists into a Studio Translation Memory using the desktop version of Studio. You can do this with GroupShare, but the ability to do this in the desktop version is a work in progress.
Well that wasn’t quite true and as I’ve been preparing for some roadshows and events that are coming up this month I figured out a simple workaround using SDL Trados 2007 Suite.
One of the more common questions I see on the forums today is “I’ve finished my translation and now my client is asking for a TMX. How do I get this from Studio?”.
Updated 15 January 2015 : Only 10,000 TUs are required for the generation of an AutoSuggest dictionary with Studio 2014.
I’ve been talking to a Freelance Translator in Canada over the last few weeks who purchased Studio 2011. She has a great set of resources from many years of translating, all split up in different sublanguages to cater for en(US), en(GB) and fr(FR), fr(CA) variations. What she didn’t have was consolidated Translation Memories so she could maximise her leverage from all of these variations, or Autosuggest dictionaries, or termbases and didn’t use the AutoText lists.
The new Studio product and the old Trados products are compatible aren’t they? Would it be true to say that Studio can handle the old Trados formats, but Trados can’t handle the new Studio formats out of the box? I think it’s true… but it still requires a little knowledge about how best to handle the compatibility issues that might arise.