CPD: The Linguist Magazine

I wrote a blog post last year about CPD, or Continuing Professional Development. As I mentioned before, CPD is a systematic way of keeping your professional knowledge and skills up to date, increasing your expertise, planning your career development and putting learning into practice throughout your working life.

As a Member of the Chartered Institute of Linguists, I am expected to set my own professional objectives at the start of each year and evaluate these at the end of the year. To help me do so, I keep a regular record of any CPD activities I carry out using the form provided by the IoL.

CPD can be any number of things. One activity that constitutes CPD is reading publications related to you specialism. This is something I am able to do regularly with the Linguist Magazine. For those of you that don't know, The Linguist is the official bimonthly magazine from the Chartered Institute of Linguists. It includes news about the Institute and is filled with articles, reviews and opinions on translation, interpreting and languages. It also features job ads for linguists, information on CIOL events and websites that may be of interest to professional linguists.

The April/May 2012 issue (which I'm currently reading!) includes all sorts of interesting articles covering subjects such as the year abroad, the Speak to the Future campaign to encourage students to study languages, the language challenges faced by the UK as it gears up to host the London 2012 Games, the results of the ITI/CIOL rates survey for translators and interpreters, careers in international sales, marketing and PR for linguists, translating the Taming of the Shrew into Urdu, going multilingual in business, using social media to boost your career (a great article by Marta Stelmaszak - I recommend following her on Twitter if you don't already @mstelmaszak), public service interpreting in Poland, and many more!

The Linguist is free to all CIOL members but it is also available to non-members on subscription.

Want to add to your CPD record? I highly recommend The Linguist!

Yours truly,
Lingo Woman

Lingo Woman's Q&As for Translators: How do I generate a bilingual Word file when working with Trados Studio?

TRANSLATOR: A lot of my clients still use Trados 2007. I, on the other hand, use Trados Studio 2009. I usually don't have any issues with this as SDL Trados Studio 2009 has maintained compatibility with TagEditor files (.ttx) and most clients are happy for me to deliver in this format. 

But when it comes to a client requesting a bilingual Word file (.doc) I really have no idea what do do! It's just not possible to do this in Trados Studio. What should I do?! Or more to the point...

LINGO WOMAN: Howdy fellow translator! I too have faced this situation many a time before while translating. Fear not, there is a solution!

First off, however, there are some alternative options available to you:

  • Obviously the best option is to get the client to use Studio! Failing this, at least see if they will agree to being sent a .tmx export of your translated file that they can import into their TM and reuse.
  • A second option, as you already mentioned, is to deliver a TagEditor file (.ttx). First, of course, you need to persuade your customer that a .ttx file is OK.
For those that don't know how to do this in Studio, here's a quick run-through:

  1. Open the Word file in TagEditor
  2. Save as a .ttx file
  3. Open the .ttx file in Studio
  4. Translate as normal
  5. Save as .ttx

  • You could also try the recently released SDLXLIFF to Legacy converter but the downside to this is that you will lose all the source file formatting.

So if, as in your case, a particular client specifically requests a bilingual Word file, what do you do?

Here's the Lingo Woman workaround...

  1. Save your .sdlxliff file.
  2. Create a new TM in Studio.
  3. Import the .sdlxliff file you have just saved.
  4. Export it in .tmx format.
  5. Create an empty TM in Workbench (part of the Trados 2007 suite) (File -> New).
  6. Import the .tmx file you have just created (File -> import).
  7. Pretranslate the file.

Et voila!

A WORD OF WARNING HOWEVER! This workaround does, of course, have its limitations. It's not perfect. You will need to check every segment carefully. They should all appear as 100% matches, but be aware that Trados Workbench and Trados Studio deal with segmentation slightly differently so this may not always be the case. You may have to spend time fixing some of the segments manually. For this reason, this solution works best for smaller files.

Yours truly,

Lingo Woman