Skip to main content

Terminology Management as Part of the Translation Workflow




When we think of terminology management in the translation and localization lifecycle, we often think of adding a new or unknown concept into an Excel spreadsheet and maybe translating it into another language.

That's actually a very simplified way of looking at terminology management and the real work is much more complex than this.

The image shows a simple example of a workflow of a translation project which includes terminology management. The translation and revision steps were simplified merely to emphasize what it takes for a terminologist to finish a lifecycle of adding one single term into the termbase.



Terminology as a discipline stretches back to the 18th century and identifies Carl von Linné as the founder of terminology organization, standardization, and planning. According to ISO, terminology is associated with particular areas of specialist knowledge. In terminology, we are not dealing with everyday worlds, with general language. But what we do we do with terms then that belong to special or technical language? According to Barbara Inge Karsch, a terminologist and a professor of terminology management "we collect or extract terms. We research their underlying concepts. We document terms and approve or fail them. We might research their target language equivalents. We distribute them and their terminological entries. We use them. Whatever you do with terms, don’t translate them." And she explains: "While both translators and terminologists research terms, the product of their work is different. The translator is responsible for the delivery of a correct target language text with correct technical terms (parole or language in use). The terminologist is responsible for the creation of a correct and complete terminological entry in a database."

In terms of a translation workflow, a terminologist needs to be fast enough to provide a solution to an issue triggered by the translators otherwise translators will find an ad-hoc solution to the problem which might be not as good or accurate. At the same time, terminology entries need to be precise, correct, long-living, and in line with the other entries. And that takes time. Generally, one single entry takes about 20 minutes from researching and validating to term entry and release. If there are 10 terms to be researched and entered, that takes about 200 minutes, and so on.

While ad-hoc terminology management has the advantages of being quicker and, it's inevitable to see that systematic terminology management solves more problems in the longer run. Consistency and domain-oriented approaches are just a few of them.

More and more companies and businesses realize the importance of including terminology management in their workflows. If the content creators and/or translators don't know something, they ask questions, those questions need to be answered by someone and if they don't get an answer, assumptions happen, which will lead to errors and mistakes, which will create confusion, and that costs more money and takes more time for the company to fix the issues than to implement an extra but essential step into their workflows. Instead of asking, what does it cost to include terminology management, the question is, what they can lose if they don't include it?

While in the beginning, just like with any other investments, terminology management might seem a bit luxurious, in the longer run, the cost will come down dramatically, as terminologists and other terminology stakeholders become more efficient in the process, standards, and tools. Investing in terminology management will create a clear and exact message about the company's brand, products, and/or services.





Resources:



Comments

Popular posts from this blog

Why I switched to Google Sites?

In the last few months, I have successfully rebuilt and relocated all my small business websites to Google Sites. You may wonder why, and what services I used it before. Here is my story. I am a graduate student in the Middlebury Institute of International Studies at Monterey in the Translation and Localization Management program, and this spring semester I took Website Localization classes. Just to give you an idea of what my studies are about, localization refers to the process of adapting content related to an idea, service, or product to the language and culture of a specific market or region. During the course, we were exposed to a wide variety of technologies and tools, such as the fundamental web technologies of HTML, CSS, and JavaScript, as well as dynamic WordPress websites localized with Polylang and WPML, Drupal websites, translating with SEO in mind, and advanced topics such as Node.js and PHP. We have touched upon the fundamental tools of dynamic website creation, websit

Fearless Workplace and Psychological Safety

  We live in a world where success is a matter of solving problems and coming up with the next big idea. It’s not enough anymore to be smart and hardworking. Organizations need their employees to collaborate, experiment and respond to their business needs that are constantly changing. But in many workplaces, people lack the confidence to do this silenced by fear and failure, judgmental colleagues, or unapproachable bosses. When leaders use fear to motivate, people can turn to extremes and dangerous methods to get the job done. And when fear gets in the way of people speaking up at work, it’s not only the individuals who miss out. No one wakes up in the morning saying and thinking that as soon as they arrive at the office, they want to look ignorant, incompetent, intrusive or negative. Well, it’s easy to manage that: if you don’t want to look ignorant, don’t ask questions. If you don’t want to look incompetent, don’t admit your mistakes and failures. If you don’t want to appear incompet

Discussion: Managing Stakeholders

A point of view of a freelance localizer and translator Who was the stakeholder and what was their role? For this discussion, I am going to use my freelancing experiences and use my clients as stakeholders. These clients are mainly LSPs and within that, primarily need to deal with translation project managers or project coordinators. In some cases they are more on the junior side, meaning they are not involved that much in the entire project but only in the coordination between linguists, and in some cases, they are senior project managers who have more interests in the project outcome because they need to manage them from beginning to end and they also need to deal with their clients. In some cases, depending also on the client and the size of the company, the project manager can be the owner or the president of the organization at the same time. As I mainly had pleasant experiences with these stakeholders, I am going to explain how I learned to deal with them in general going into de