May Meeting Recap: Translation Basics

by Opal Gamble, Program Manager

May's general meeting, Translation Basics, had a small turn out -- apparently the Leaf's playoff game was important (who knew?) -- but still featured an impressive string of questions from the small, but curious, audience.

Our panel of translation experts, Al Daigen (Daigen Communications), Margie Yundt (Virtek Vision International Inc.), Steve Desmeules and Rudi Vanvaerenbergh (DNS Translations Inc. / ACCU-Translation Services Ltd.) answered everything the audience could come up with -- then they stayed for nearly an hour answering even more questions!

To quote Rudi, translation is a "good business... it's a passion." It must be if they skipped the playoff game for our meeting!

How do you write for translation?

Be concise. Don't use slang and make sure you have clear descriptions.

Good writing always translates well.

How long should a project take?

This depends on the project, but generally 100 pages takes around six weeks. However, there are many variables for a time estimate, including the availability previous translations, the translator's familiarity with the product and/or authoring tool, and the technical complexity of the content.

How do I make a translation project go as smoothly as possible?

Give your translators as much information as possible for context. For example, send them:

• previous versions (translated or not, these documents provide translators with relevant background information and terminology references)
• glossary of terms
• style guide
• any relevant information about the document's structure and template, including any useful authoring tool tips
• flags indicating things that should not be translated

How do you deal with confidentiality issues?

Translators work under the Association of Translators and Interpreters of Ontario's Code of Ethics; for additional confidentiality, some companies ask translators to sign contracts or NDAs. However, you are protected by privacy regulations.

What are your ideal requirements for a project?

• finished! (Laugh, but we all know about project creep!)
• editable format (i.e., not PDF!)
• clear expectations
• translation time built into a project estimate
• heads-up that a project is coming
• access to SMEs
• documents with whitespace -- French and Spanish are 20% longer than English

How many drafts does a translator do?

Typically one, then there's an editorial review.

Does a good client get a better deal?

Absolutely! Relationship goes a long way.

Helpful clients with lots of work (volume) and friction-free interactions require less work and get the best deals possible. A client willing to spend time is a good customer.

Repeat work (for example, translation of an updated guide that had previous, translated versions) means translations take less time (and less translation) because you have the advantage of the translator's memory and glossaries.

How do I find a good translator?

Ask around for referrals and word of mouth recommendations.

Request that prospective translators send you references, suggestions for project optimization, and samples of their work.

Extra tips and tricks of the trade

• After finalizing page layouts for translated documents, send them back to the translators for a final check for appropriate hyphenation and page breaks in the target language. Most translators provide this service at no extra cost. Remember that hyphenation rules change for each language -- what looks right to you from an English perspective might not be correct for other languages.
• There is a deep pool of translation talent in Quebec and Canada -- don't think that you have to use foreign translators to get superior results.
• Trust between a client and a translator is important -- if you have feedback from sales people, resellers, or customers, send it to the translator!
  But, keep in mind that some feedback is a matter of style; sometimes translation disagreements are just personal preference.
• Agree on target audience and terminology before you begin a project.