Whatever your opinion of Trados Studio–read about my own change of heart about it here–I think we can all agree that it takes a while to learn to use. In the words of an SDL staffer, just as professionals in other industries don’t expect to learn Photoshop, Quark Xpress or InDesign in an hour, translators need to invest some time in learning to use Trados Studio.
Enter one issue: Studio comes with extensive help files and even its own YouTube channel (111 videos and counting!), but it doesn’t come with a manual. Enter one solution: Swedish translator Mats Linder has written a comprehensive manual for Studio (2009 and 2011 versions) which you can purchase for US $45 from Mats’ own website or from the SDL OpenExchange App website. If you own Trados Studio, you need this manual…yesterday! Even if you’re fairly tech-savvy and have used TM tools before–and I’d include myself in both of those categories–you probably felt as if your head were going to explode when you looked at the Studio interface for the first time. Then, you probably either battled with learning the program on your own, or, as I did, hired a trainer to help you learn to use it. Regardless of your Studio learning level, let me give you an overview of this manual and why you need it.
At 324 pages, it’s hard to imagine an important Studio feature that this book doesn’t cover. Downside: if you prefer reading on paper, the manual is available as a PDF only and it would be cumbersome (although possible) to print. But it is exhaustively comprehensive, covering even the most recent Service Pack–SP2, released in September, 2012. Mats has included numerous screen shots that are marked up to show exactly the menu item that you’re looking for; this also minimizes or eliminates the need to have the program open while you’re reading the manual. And before you start, be aware that the manual does not cover installation or licensing issues, and that you need at least a basic knowledge of CAT tools (i.e. what is segmentation, what is a TM) before you get going.
Longtime Trados users will appreciate Mats’ thorough coverage of the differences between “old” Trados (2007 and before) and Trados Studio. He also details the changes from Studio 2009 to Studio 2011, including SP2. There’s also a very helpful chapter on where to get help with Studio–blogs, websites, etc.
Mats kicks things off with the basics of Studio: how to get going without learning sophisticated functions that you may not need right away. Even more helpfully, he defines the key concepts associated with Studio, which may trip up a lot of beginning users; i.e what is a project? what is a package? He is also very honest about Studio’s drawbacks and limitations, for example by telling you that there are a number of problems with the Preview function and it may be better to find a way to work around it, or that there is only one stage in the project prep process where you can merge files. One advantage of the PDF format is the numerous active links to external references such as SDL Client Communities manager Paul Filkin’s blog. Another helpful addition is some information about workarounds: for example how to open a Studio package without using Studio (change the file extension to .zip).
Once you’ve mastered the basics, Mats moves on to Studio’s more advanced features such as AutoSuggest, a new capability whereby Studio automatically suggests a word completion once you type the first few letters. And here’s something that only an independent author can slip in: a list of features that Studio is lacking, such as auto-insertion of target text terms and expressions. Mats also helpfully suggests Open Exchange applications (many of them free) that can fill these gaps. Additional “power user” content includes a thorough rundown of the file formats that Studio can handle, and a comprehensive table of how to migrate non-Studio translation memories into Studio.
In sum, I loved this book, and I fervently hope that Mats considers writing a manual for SDL MultiTerm in the near future. Not only is the manual incredibly comprehensive, but Mats writes in a very clear, easy-to-understand style that should help almost every user learn or master Studio. My only suggestion for improvement is that I think SDL should either include this manual with the software, or at least provide a more visible way to purchase it–for example by offering it as an add-on when one purchases the software–instead of burying it in their app store. Congratulations and thanks to Mats Linder for such a valuable resource!
Volkmar says
Wholeheartedly agree with you, Corinne, as far as the manual is concerned. Just bought it the other day, after many trials, tribulations and useless searches in the Help section. And what a blessing it really is.
I also agree with you that SDL ought to offer this manual to every buyer of Trados Studio. Personally, I think it is rather ungracious of SDL–if not to say rude–to sell you such a product without giving you the option to learn how to use it. As far as I am concerned, especially the legacy Trados and less so the Studio series are anything but user-friendly. And they are hopelessly overloaded with functions that the average freelance translator will never use. As Kevin Lossner put it, if you want to get started fast you buy MemoQ, if you are masochistically inclined, go for Trados Studio. I tried a demo of MemoQ and got it fairly quickly; with Studio, on the other hand, it took me ages to really come to grips with it; and I’m not sure I’m really there yet. That is why I bought the manual.
Now I hear everybody shout–yes, but SDL have videos on YouTube to get you started; why not look there?
Indeed they do! But SDL forgot something–many of us aren’t native English speakers, and many of us run Studio with a user interface in another language than English.
Firstly, SDL should use presenters that don’t speak with some quaint English countryside accent but pronounce clearly, so at least we can understand them.
Secondly, they should show the screen shots long enough and BIG enough so we can recognize what they are showing and chase that on our own screens in a different language.
Thirdly–and I think there are few tool vendors that pay attention to this–many users have little or no command of English. Why should they? Maybe they translate from French to Tagalog. But who helps *them*? Who cares about them at all? Translating the interface alone isn’t doing them justice. After all, they paid as much for their Trados copy as you and I did.
And Trados Studio (at least 2009) is not fully compatible with Dragon Naturally Speaking. Why not? Speech recognition is ubiquitous.
Now you will be asking me why, after so much griping, I’m using Trados Studio at all?
Very simple.
Two of my biggest clients insist on it. It is true that MemoQ claims 100 percent compatibility with Trados, but who is to guarantee that claim?
If I didn’t have those two clients, you know what I would do.
Thank you, Corinne, for bearing with me, and keep up the good work! I enjoy your postings very much!
paulfilkin says
@Volkmar
To be fair there is a pretty comprehensive online help with Studio (EN, DE, FR, ZH), three simple quickstart guides in pdf (EN, DE, JP) for installed with the product (covering “Translation and Review”, “Translation Memory Management”, “Project Management”) and a migration guide that explains quite well where the differences are and how to migrate your resources (from Trados or SDLX)… this one’s only in EN though. Most presentations are on YouTube too, or they are made available for review with the webex player after the event so you can always refer back to them and freeze the fame when needed. We see youtube channels in other languages too (a DE channel and often subtitles for other languages).
In addition to Mats manual we also have PL manuals on the OpenExchange and I noted Loctimize were sharing a DE manual through their website last week.
But you’re right in that I’m sure we don’t have solutions for everyone like this but we are open to discussion and improving this if the demand is there. For the cases where the demand is low we can always arrange special training in local language if users get in touch, or even do an online training to help users get started in local language.
But to get back to the article written by Corinne… I think it’s a fair assessment of the manual and it is good because it’s been written independently by someone who uses the software in anger and pulls no punches. A good article.
Corinne McKay says
Thanks Paul! And thanks also for being so accessible to people who need help with Trados; seriously (seriously!) I don’t know what we would do without you and all of your awesome tips. And thanks for responding to the article, I really appreciate your feedback!
Riccardo Schiaffino (@RSchiaffino) says
Hi Paul,
It’s true that Studio comes with a comprehensive help… but the writing of that help could be much improved: I think it works OK for experienced users who only need a reminder of how something works, or even how to use a feature they have never used before. For new users it may look like a daunting maze (the quickstart guides are much better in that regard).
But what we would really need from SDL is a complete rewrite (starting from scratch, and using completely different writers) of the MultiTerm documentation: the current help system is probably very comprehensive. It is also very badly organized and essentially no help at all.
Try to have a new user, give him (or her) a simple task to accomplish in MultiTerm (e.g., convert an Excel glossary into a MultiTerm termbase), and tell them to follow the instructions in the help system, and you’ll see what I mean.
matsdlinder says
I saw Corinne’s suggestion that I also write a MultiTerm manual (she’s not the only one who has suggested this). But I think the market for such a book would be too small to make it profitable. My impression is that most Studio users are satisfied with the basic uses that are covered by the manual and other documentation on that level. (If anyone can prove me wrong, I might reconsider.)
atuckeronline says
This article couldn’t have come at a better time for me, so thank you and those who have commented for sharing your opinions. I am currently migrating from Wordfast to Trados because a couple of my higher-paying clients demand it and because I am interested in its project management features, and though I’ve used the video tutorials and set up a couple of projects, I’ve been quite frustrated by having to look for all of the information I need since it doesn’t seem to be in one place—at least I’ve had trouble finding it quickly and easily. I believe I will purchase this manual and give it a go.
Thanks again!
matsdlinder says
Actually, I don’t think that Studio is as user-unfriendly as some people say. I also think it’t a big step forward from Trados 2007. And I find the help facilities plentiful (and the OpenExchange concept is invaluable, as is Paul’s multifarious blog). But in my opinion, no amount of help texts, however well written, can replace a good manual, and that’s why I decided to try and write one (also because it’s a kind of job I like to do).
But Paul, I never used Studio in anger. Sure there are problems now and then (otherwise TW_Users would not be as much used as it is), but that happens with all software, and sometimes the fault lies with the user. And I have also the distinct expression that the Studio developers honestly listen to the users’ comments and do try to improve the program as best they can. (I’m looking forward to that big step — already taken by Déjà Vu and memoQ — when Studio is able to suggest suitable TM segment pieces in the target segment as it opens.)
BTW: Where can I find the Loctimize DE manual? I’ve looked everywhere on their website but can’t see it.
matsdlinder says
@Paul
I found the DE manual. I also found another interesting document called “Sub-segment matching demystified” which discusses exactly what I was talking about.
paulfilkin says
@Mats Many apologies… the phrase “used in anger” is a metaphor for making full use of something… my bad for not writing clearly. But I’m certainly glad to know you weren’t!
The DE manual can be found here : http://goo.gl/FDpIq for anyone else interested.
Volkmar says
@paulfilkin
Thank you, Paul, and I am also very grateful for your valiant work in different fora, trying to steer us disoriented Studio users through the troubled waters between Scylla and Charybdis…or whatever they were called.
*About Help: Help is great, if you now exactly what you are looking for.Trouble is that in many cases you don’t know how to phrase your question or what search term to use. Plus, Help will help you with a specific problem; it won’t give you the overall picture.
*The videos: I wish–and I hope you pass this message on to the people concerned–SDL would use narrators who speak clear and plain English. I don’t want to sound conceited but I think my command of spoken English as a listener isn’t all that bad; I do however have a problem understanding certain British accents, especially when the speech is somewhat slurred, as is the case in a number of Studio videos.
* Function overload: I think that Trados Studio is vastly overloaded with functions, and the only reason I never upgraded to Studio 2011 was that according to the SDL marketing copy, 2011 sports an additional 113 functions (give or take a few, I don’t remember the exact number). 113 additional functions!!! How am I ever going to cope?
So why isn’t SDL offering a “thinned-out” version for us mere mortals (i.e. ordinary freelancers), with the option of adding more bricks later?
*The critical point: As a freelance translator, I always strive to improve my translation skill because translation, after all, is my profession. So I would prefer to spend what little spare time I have to become a better and more proficient translator (= communicator). I agree that managing a CAT tool is part of that process but it should take second place to honing my language skills. If, however, these priorities are reversed, then something is wrong. Studio is not making me a better translator, just (hopefully) a faster translator.
I think that most CAT tool vendors forget that we are first and foremost translators, and that operation of a CAT tool should take the back seat to that.
Again, I appreciate your work and have profited from it myself. Thank you for that!
matsdlinder says
@Paul
Interesting — I had never encountered the phrase “used in anger” before (or at least not noticed it). I found this additional explanation: “it is generally used in British English to mean used for its intended purpose, or used for real rather than in tests”.
Live and learn… (But a phrase made for misunderstanding!)
Riccardo Schiaffino (@RSchiaffino) says
Mats,
I think it’s a probably a chicken-and-egg kind of problem: most users don’t use MultiTerm more (or don’t use it at all beyod the level of a normal bilingual glossary) because it is not well documented, and they are not aware of how it could better help their work if used in a less superficial way. If it was better documented (and sported a more user-friendly UI) people would use it more.
But yes, I agree that the market for a MultiTerm manual would probably be much smaller than for the Studio manual.