Creating a glossary for each translation project has been a part of my daily work as a translator for so many years that I no longer understand how anyone can work without one. In this post, I want to explain why I believe consistent translation is impossible without a project glossary.
Why It Pays to Create a Glossary
The two primary functions of a glossary are making it easy to insert translations of terms into a current segment and making it possible to check the entire translation for consistency after it’s completed. Of course, a translator can use a TM to find terms as well. But searching a TM is not as efficient as using a glossary and requires a lot of discipline. With a glossary, inserting translations of terms is so much easier. For instance, the translation program OmegaT highlights every term that’s in a glossary and enables you to insert it using a context menu. And a TM is useless when it comes to checking for consistency. You still need some sort of a list of terms to feed to your QA program.
I started selling the idea of creating a project glossary to our team years ago. It was difficult back then because we didn’t have the great tools we have now. Due to this technical challenge and the fact that creating a glossary takes time and discipline, getting everyone’s buy-in wasn’t easy. At first, we even had to formally require everyone to add at least one term per 100 words because they wouldn’t do this otherwise. Today, after years of practice and with better tools available to us now, a glossary is a part of our culture.
Some Freelance Translators Don’t Use Glossaries
Now, what strikes me in dealings with freelance translators is that many folks don’t create the type of a glossary I’m talking about. I’d really like them to do so, but no matter how strongly we believe in glossaries internally, I can’t force freelance translators to do this. Even if we formally agree that they will create a glossary, translators normally grudgingly obey, but they don’t commit to following through, which is a prerequisite for getting the most out of a glossary.
I’m especially bewildered when it comes to testing new candidates. The very people who should use a glossary to make sure they deliver a perfect translation and make a good first impression often DON’T care much about it. Okay, I’m realistic and know that quite a few translators just don’t have the necessary level of commitment. But if you think about it, not creating a glossary doesn’t make sense at all for them. They take the time to market their services to us for an opportunity to get our business. And then they blow it so easily because of a failure to take a few additional minutes to ensure consistency.
The Main Point
While editing a pretty big sample translation last week, I once again realized that even if a translator recognized the importance of consistency, but didn’t create a glossary, his/her consistency would be at 80 or 90% level at best. Those missing 10 or 20% are usually enough to ruin impression. And this is the main message for this post. If you want to provide a consistent translation especially when you’re pursuing a freelance opportunity, creating a project glossary is a must.
Readers: What else would you say to a translator to make him/her change his/her mind about glossaries?
For more information on this topic, read my post about tackling three common challenges around glossaries.