A localisation (*) or translation project is the sum of many well-coordinated components that work together seamlessly, like an orchestra.
In a localisation project, compiling a glossary is like overseeing another small project.
According to Pavel Soukenik from the University of Washington, glossaries are to replace traditional dictionaries.
The benefits of a glossary
- A good glossary needs to help improve the quality of translated files.
- A good glossary is used to achieve consistency throughout the various parts of a project, such as the user interface, marketing materials, manuals, videos, product packaging, and so on. This means we can ensure that words and concepts are used in the same way across the whole project.
It’s possible that several people write content for an individual product or that different translators translate parts of the same documentation into another language. In these cases, a glossary helps to keep everything consistent for the same language and product.
- A good glossary can save lots of mistakes from being made. Paula Barreto de Mattos, who worked as a linguistic and terminology specialist at Microsoft for eleven years, states, “In technical documentation, terminology accounts for 20% to 70% of errors”.
When and how to prepare a glossary
For the best outcome, a glossary should be ready to use before starting the translation.
The terms to be included in a glossary are those used for a particular market or industry, or those that can create confusion among translators.
For example, if a term has two meanings, both meanings need to be included with a comprehensive description, so that the translator can decide which one is being referred to, based on the context.
This is the case of the world “folder”. It can refer to a folder in which digital files are stored, or it can refer to an accessory that some large-format printers have that literally folds paper.
How to decide if a term should be part of a glossary
The criteria are highly subjective:
The following are some helpful pointers:
- Choose terms that often come up in the documentation: frequency.
- There’s no need to add common verbs that are used a lot.
- Add those frequently used words used in the project that are given a different meaning from usual.
In some languages a literal translation might not make any sense.
It’s important for the customer to help with the process of creating a glossary.
Who can help create a glossary?
- People who create content: engineers who add texts to user interfaces, technical writers who write manuals, etcetera.
- People from the marketing department: who work with lists of product features.
- Translators: when they come across terms they don’t understand or that could have more than one meaning, which they query.
- Project managers (translation project coordinators): when they analyse the project, they can read the source documentation and make a list of the terms that may lead to confusion, or that are particular to the topic or industry.
What should a glossary include?
Besides the term itself, a description is crucial, as well as an image if possible (they say a picture is worth a thousand words). Anything that can help contextualise and understand a term is welcome.
Glossaries that show terms which shouldn’t be used are also very helpful. For example, often companies give names to projects that have little to do with the commercial name, or engineers name pieces differently from the terminology decided by the marketing department. In these cases, it’s essential that content creators, who produce the literature that customers will see, avoid using internal terms and instead use those terms that have been specifically designed for the market.
Once the glossary is ready, and before starting the translation, the customer needs to review it.
If the customer is prepared to review the translated glossary terms as well, so much the better. But this rarely happens.
If the glossary is used properly, it can help create documentation and translations more quickly, that are of a higher standard and that are consistent.
If you need help creating a glossary, at LocalizationLab we’d be delighted to help.