"Please translate this short paragraph and return by email"

These “quick” jobs are never that quick if you want to make sure you add the translation to your Translation Memory, or leverage the work you’ve done before.  You need to copy the text into a word document, or similar, then open the document in your favourite translation environment, translate the document, save the target translation, open the document and copy the text, finally paste it back into your email to return to your client.
Continue reading “"Please translate this short paragraph and return by email"”

The ATA53 Studio presentation in San Diego…

As a follow on to the presentation I gave at the ATA this year, which was very well attended (photo courtesy of Wesley Budd) I thought it might be useful if I highlighted some of the things covered on the day.
The session itself was a little ad-hoc, deliberately so, because I wanted to make sure the content was relevant to the attendees, and because it wasn’t a getting started session.  So I covered quite a lot of material, that judging by the number of people furiously scribbling down in their notebooks could use a little follow up!
Continue reading “The ATA53 Studio presentation in San Diego…”

More useful resources… and multilingual TMs

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.
Continue reading “More useful resources… and multilingual TMs”

Working with Variable Lists

Updated January 2015 : Also possible, and easier, to use the Variable Manager from the SDL OpenExchange (now RWS AppStore) 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.
Continue reading “Working with Variable Lists”

Making the most of your resources… and some free extras

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.
Continue reading “Making the most of your resources… and some free extras”

Upgrading your legacy resources – filetypes

When you upgrade from Trados to SDL Trados Studio there are a number of things you can take with you.  Translation Memories, Termbases, AutoText lists, custom variable lists, customised segmentation rules for example.  These are all discussed quite a lot in the public forums and in blog articles, but what we don’t see a lot of information on is how to update your file types.  As a result I think many users convert files to TTX unnecessarily just so they can use the old *.INI files they’ve had for years.
Continue reading “Upgrading your legacy resources – filetypes”

Making use of the Studio Track Changes features

SDL Trados Studio 2011 SP2 was released last week and SDL are in the process of giving introductory webinars and sending mailers with lots of nice details about the new features provided. One of these features is being able to open word documents (DOCX only) that contain tracked changes.  This is interesting of course, but what makes this so useful?
Continue reading “Making use of the Studio Track Changes features”

What's all the fuss about "edit source"?

Update: 15 January 2015
This is now possible for all file formats except for ITD, updated in Studio 2014.
SDL Trados Studio 2011 SP2 has introduced “edit source”… but only for Microsoft Word and Microsoft PowerPoint file formats at the moment.  For Freelance Translators this is a welcome addition because it has been one of the most heavily voted for ideas on the SDL Ideas site.  However, is this enough and why haven’t SDL introduced this before?  This is fast becoming a topic for much debate on the public forums and Facebook pages so I thought it warranted a little insight into the problems of introducing “edit source”.
Continue reading “What's all the fuss about "edit source"?”