If you are a translation buyer, you are probably concerned that a translation should be consistent across the different documents it involves: marketing brochures, PowerPoint slides, technical descriptions, even sales items and press releases. It makes sense to keep a unified message out there.
If you are a translator like me, you’ve heard it too: keep the terms consistent; maintain consistency across all files.
I think translation buyers, translators and project managers are meaning different things when they request consistency and I’ll attempt to clarify it here.
First, let’s get the obvious meaning out of the way: when people talk about consistent things, they mean use the same terms: a bolt is a bolt, not a carriage bolt. A partition is not necessarily a wall anymore than a white blood cell is a blood element. The more technical a document, the more consistent it should be, because using ambiguous terms might mean using the wrong kind of steel or injecting the wrong dosage of a certain drug.
But I think consistency refers to a more important fact: comprehension. And for a statement to be easily understood, the same exact words do not always need to be used. An example:
A) Provide stainless steel self-tapping metal fasteners to attach the metal panel system to the bathroom partition.
B) Affix the metal panel to the bathroom partition using stainless steel self-tapping screws.
Both sentences above, A and B, are giving exactly the same instructions. Notice, however, that B is shorter, crisper and clearer. Imagine that the user’s manual has sentence A while a maintenance manual has sentence B: the sentences differ, but they are consistent in meaning and purpose. And that’s worth remembering.
A translator doesn’t just substitute words like code characters.
The other side of the consistency coin is terminology. Many people, including translators, use the word a bit carelessly without fully understanding what it means. In civil engineering, an overhead panel ceiling is the same as a panel ceiling system, or a panel ceiling. Some people like to show off a bit and call a heater a heating unit or a heating system, but they are all one and the same in the real world.
Translators should concern themselves more with doing proper word and concept research to support their translation choices rather than promise a fuzzy idea of consistency. They should know better about using glossaries, dictionaries and other sources rather than floating the word terminology so casually. Why? Because terminology is more than just building a glossary of specialized words; proper terminology also involves developing the right criteria to use those words. Terminology is not about foreign word substitution because languages are not software codes, not easily amenable to a simple search and replace action or a copy and paste method. And a seasoned translator who changes a word doesn’t necessarily do it out of preference but out of precision and, ironically enough, to preserve the much-valued consistency.
Then, what to do with consistency? Call it something else, for starters. As a project manager, I learned that the best time to ask questions about expectations is in the beginning, before mistaken assumptions cause costly mistakes and delays. The first expectations to be clarified are those of the translation buyer, i.e. the client. What are her priorities? Once priorities are stated and fleshed out, begin from there:
Is there a company glossary to use as reference? A responsible and expert translator does not promise blind conformity with a glossary without taking a good look at it first. Also, it’s also a translator’s best practice to tell the customer that the most updated, industry-specific and appropriate terms shall be used, and that those terms may or may not come from the company glossary. If this potentially sticky point is handled at the beginning, then expectations shall be clearer for all concerned and any questions of consistency will be resolved.
If the translator earns the customer’s trust about his performance in writing excellent technical translations, then nitpicking about this or that word usage will be very rare. When this trust is not established from the beginning among the translator, his customer, the customer’s reviewers and even the project manager and fellow translators working on the same project, then the entire team will spend time arguing over terminological issues, preferences and so-called consistency. Chances are that, in this chaotic environment, an otherwise well-written translation will be questioned for the terms it uses.
As an aside note on consistency, I think universities and colleges engaged in teaching translation and interpretation should teach lexicography basics rather than terminology. If we want to prepare a new generation of competent translators, we need to show them the basics of dictionary making, the process of word formation and the principles of empirical research aimed at finding the right terms and expressions in a given industry or specialization. Otherwise, we are selling them just an empty shell of knowledge —after all, terminology is widely (and mistakenly) understood as the process of building glossaries for a given industry. But, as I hoped to show above, that’s only part of the story.
Wordsmeet: translation for businesspeople 
You must be logged in to post a comment.