I think I’ve discussed Project Templates in the past, although perhaps only in passing. So let’s start off by painting a picture of the situation you find yourself in where templates come in handy. You maintain your own Translation Memories, in fact you have five you regularly use for every project but keep them separate because they are based on different sublanguages and you have some clients who adhere strictly to the minor linguistic differences. You have a couple of termbases that you also like to add to every project and you find it easier to manage the terminology for your clients in separate termbases rather than use custom fields that complicate the ability to import/export with your colleagues. You also have very specific quality assurance rules that you’ve honed over many years of translating and you know these are reliable and help you when you work.
So that’s a nice straighforward scenario that is probably followed by many of your colleagues… but then a new Project Manager with an agency you regularly work with starts to send you Project Packages for the first time, and another direct Corporate client of yours purchased GroupShare and you started to receive links to online projects. The Project Managers in question are not as experienced as you and they create their projects with default settings and their own less relevant resources, and they send them out to you. No problem you say, and you just add your own Translation Memories one at a time, your termbases one at a time, and you import your own quality assurance rules. This is all fine as Studio lets you take advantage of your own resources and your client is quite happy because you’re still turning in quality translations as you always have. But then you have to do this again… and again… and again… and it all starts to get a little tiresome. Surely there’s a way to add more resources at a time and apply them to an existing project? Continue reading “Keep Calm and use your Project Templates…”
I had the pleasure of meeting Michael Farrell, the developer of 
On two previous occasions I’ve been lucky enough to attend the 
It’s funny how questions seem to appear like London buses… you don’t get any and then they all come at once! More often than not it’s very specific questions that behave this way too. So you don’t see them for ages and then you get the same question in a number of places for a day or two and then it goes quiet again! One of the topics that falls into this category is changing the view in the Editor. By this I mean the colour of the text, the font types or the background you’re working on. All these things can be changed in Studio to make it easier if you’re dealing with documents that don’t display well and you want to work in wysiwyg mode.
This article is all about out with the old and in with the new in more ways than one! In the last week I have been asked three times about converting Wordfast translation memories and Wordfast glossaries into resources that could be used in Studio and MultiTerm. Normally, for the TXT translation memories I get I would go the traditional route and use a copy of Wordfast to export as TMX. Then it’s simple, but what if you don’t have Wordfast or don’t want to have to try and use it? Wordfast glossaries are new territory for me as I’d never looked at these before. But on a quick check it looked as though they are also TXT files so I decided to take a better look.
When we want to purchase software what’s the first thing we do? I know what I do… I look around on the internet for websites where I can learn more about the tools I’m interested in and only purchase if I can try them myself, and I imagine you’re no different. If I want to compare TEnTs (Translation Environment Tools) it’s a small and very competitive field and you don’t see the sort of widely published comparisons you might for Office products, or desktop publishing tools for example. So one place to start might be reviews from real users… but can you trust them? They are often written by fans of a particular product who like to rate the comparisons based on their own personal choice, and often the comments they make about other tools are based on not knowing other tools well enough. Certainly when you read the comments from users of the tools that came off worse you can see it’s also quite an emotive area… although it’s good to see users so passionate about their translation tools. Even articles that are written in a well meaning and honest way, such as the one that Emma Goldsmith co-authored with David Turner 
The AutoSuggest feature in Studio has been around since the launch of Studio 2009 and based on the questions I see from time to time I think it’s a feature that could use a little explanation on what it’s all about. In simple terms it’s a mechanism for prompting you as you type with suggested target text that is based on the source text of the document you are translating. So sometimes it might be a translation of some or all of the text in the source segment, and sometimes it might be providing an easy way to replicate the source text into the target. This is done by you entering a character via the keyboard and then Studio suggests suitable text that can be applied with a single keystroke. In terms of productivity this is a great feature and given how many other translation tools have copied this in one form or another I think it’s clear it really works too!
Happy New Year to everyone reading my blog. It’s been fun writing it, and I hope it’s been just as enjoyable and useful for you all as well.