Localization, Localisation

Practical and concise answers to common questions in G11N, I18N and L10N

SDL Trados 2007: Translation Memory Strategies

Posted by Nick Peris on March 27, 2009

What is the best way to organise and maintain Translation Memories?

I currently maintain TMs using 2 features of Trados (the Attributes and Master/Project TM dichotomy) and Alchemy’s Trados component.

Master TMs

  • single and exhaustive repository for each field and language pair (e.g. EN-FR Medical).
  • used to analyse all new projects and generate Project TMs.
  • content of Project TMs are only added to it when full project cycle has ended (including review, QA etc.).
  • because of their exhaustive nature, Master TMs tend to grow rapidely and would not be practical for inclusion into a translation kits.
  • even when outsourcing all or most of the localisation process, these should always be held by the client as they are a valuable asset which they own, regardless of whether they are outsourcing TM Management.

Project TMs

  • specific to a project or project stage (i.e. successive handoffs of a same project often have their own Project TMs).
  • used to pre-translate the handoff (i.e. generate the TTX files to send to the vendor).
  • passed on to translation vendors for analysis and use during interactive translation.
  • used during post-translation engineering (bugs are fixed in Workbench + TagEditor + MultiTerm interactive translation environment by the localisation engineer).

Software TMs

  • single and exhaustive repository for each field and language pair, generated bi-yearly from Catalyst TTKs.
  • added to Master TM of their field and/or used as Concordance reference during translation of help, documentation, knowledge base articles etc.
  • also used as leverage source for software through Catalyst.

Use of attributes

  • every time a new project is analysed, custom attributes are added and set (e.g. Vendor=AAA, Project=XXX, Field=FFF).
  • can be used to filter searches and analyses.
  • also useful to track back on errors or arbitrate between duplications.
Advertisements

2 Responses to “SDL Trados 2007: Translation Memory Strategies”

  1. […] same and latest version of Translation Memories. Different Localisation Managers have different TM Strategies which are often dependent on the CAT tools or even the version of the CAT Tools in use by […]

  2. […] main grief is around TM Maintenance or the lack of it. Because TMS automatically updates the Translation Memories at whatever stage of […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: