How to Keep Technical Terminology Consistent Across Translators, Suppliers and Markets
Technical terminology stays consistent across translators and suppliers when one approved translation glossary is applied to every job: the same component keeps the same name in manuals, interfaces and spare parts lists, whoever translates them. DEMA Solutions builds client-owned glossaries, approved by your experts and used on every project.
Why the same component ends up with three names
It rarely starts as a decision. A manual is translated by one translator, the interface texts by another, the spare parts catalogue by a third supplier a year later. Each of them makes a reasonable choice for the same term, and each choice is different. Add a distributor who adapts the wording for its market and a source text written by several authors over the years, and the same control panel can appear under three names in one language.
Nobody notices on a single document. Your technicians, distributors and customers notice when they read them side by side.
What inconsistent terminology costs
- Review rounds. Every inconsistency becomes a question from an engineer or a distributor, and another correction cycle before release.
- Confused users and technicians. If the manual and the machine interface use different words for the same function, the instruction is harder to follow, and in safety information that is a real risk.
- Rework on every update. Terms are decided again on each job instead of once.
- Machine translation that guesses. Without your approved terms, a machine picks a generic translation, and it may pick a different one next time. See when machine translation post-editing is good enough.
- Higher cost per release. Inconsistent source and target terms lower what your translation memory can reuse. See where the cost of technical manual translation really comes from.
What most companies have today
In practice we see three situations. Some companies have no glossary at all and rely on the memory of a long-standing translator. Some have an Excel file that was sent to a supplier once and never updated. Others have a term base, but it sits inside their previous supplier’s tools, and they have never seen it.
None of these is a glossary that works. A glossary only protects consistency if it is approved, kept up to date and applied on every job.
What a translation glossary that works looks like
- Approved by your experts. Engineers, product managers or in-country distributors confirm the translations of the terms that matter. The glossary reflects how your company and your markets speak, not one translator’s preference.
- Applied inside the translation workflow, on every job. A spreadsheet sent once is forgotten. The glossary has to be part of the tools the translators work in, so approved terms are shown, or enforced, every time the term appears.
- Covering every content type. Manuals, interface texts, spare parts lists, marketing and service documents use the same approved terms.
- Owned by you. The glossary, often called a term base or terminology database, is your asset, exportable in a standard format such as TBX or a structured spreadsheet, so it works with any supplier.
- Updated when your products change. New components, renamed functions and market feedback go back into the glossary, so it stays the single reference.
How a glossary is built
- Share your documentation. Existing manuals, previous translations and any term lists you already have.
- Extract the key terms. Component names, functions, safety terms, units and product names that must never vary.
- Translate and research. Linguists propose translations based on your previous documents, standards and the usage of your markets.
- Approve with your experts. Engineers or product managers confirm the technical terms; distributors or subsidiaries confirm local usage in their market. Each proposed term comes with its context and the source documents it appears in, so approval is a review, not a research project.
- Apply and maintain. The approved glossary is connected to every translation job and updated as your products evolve.
Our terminology management service describes this process in detail.
Consistency starts in the source text
A glossary fixes the translation of a term. It cannot fix a source text that uses three words for the same thing. When manuals are written by different authors over the years, “control panel”, “operator panel” and “HMI” may all describe the same part, and every translator will faithfully reproduce the difference.
Three habits help your technical writers:
- One concept, one term. Decide the preferred source term and list the ones to avoid. The same glossary can hold both.
- Short, consistent sentences. Instructions written the same way each time are easier to translate and easier for your translation memory to reuse.
- Update the glossary when the product changes. A renamed component should change in the glossary first, then in the documents.
One glossary, local variants where markets need them
Sometimes a market genuinely needs a different term: a distributor’s customers use a regional word, or a standard in one country prescribes its own wording. That is not inconsistency, as long as it is decided once and recorded. A good glossary holds the approved term per language and, where needed, per market, with a note on why. Your distributors and subsidiaries then stop adapting the wording on their own, and every document in that market uses the same choice.
Several suppliers, one glossary
If you work with more than one translator or supplier, a glossary you own is the simplest way to keep them consistent. Give every supplier the same approved glossary and the same translation memory, and consistency stops depending on who does the work. It also means a new supplier, or a new translator at your current one, starts from your terminology instead of their own. See who owns your translation memory.
When you evaluate a new supplier, ask how they apply your glossary on every job and whether their checks flag terms that do not match it. See how to check a supplier’s quality before you hire them. And if coordinating several suppliers is itself the problem, see how to stop managing translations by email and spreadsheets.
Example: aligned terms across manuals, interfaces and spare parts
One of our manufacturing clients, an Italian producer of industrial equipment, ships every machine with manuals, safety information and interface texts in the language of the destination market. Component and process names must be identical in all of them, and across years of documentation. An approved client glossary keeps those names aligned between manuals, interface texts and spare parts documentation, and the same specialist linguists work on the same product families, so technical choices stay consistent from one project to the next. Read the industrial manufacturer case study.
“Our native-speaking dealers have also praised the quality and accuracy of the translations.”
Michela R. ยท FMB S.r.l. ยท Italy
Where TUBE fits
In TUBE, your glossary controls every machine translation. Your approved terms apply from the first draft, together with your translation memory, so the machine follows your terminology instead of guessing. The glossary is set up by our language technology team and stays yours.
Frequently asked questions
A translation glossary is a list of approved terms with their required translation in each language, often with definitions, context and terms to avoid. Translators and translation tools use it so the same concept is always translated the same way.
A glossary stores individual terms. A translation memory stores whole approved sentences. You need both: the glossary keeps terms consistent, the memory reuses approved sentences and saves cost.
The people who know the product and the market: engineers, product managers and, for local usage, in-country distributors or subsidiaries. Linguists propose and research; your experts confirm.
Own one approved glossary, give it to every supplier, and require that it is applied inside their translation tools on every job, not only sent as a reference file.
Only if the machine translation is set up to use it. Generic machine translation tools choose their own terms. When machine translation is controlled by your glossary and translation memory, your approved terms apply from the first draft.
One component, one name, in every language
If the same part has different names in your manuals, interface and spare parts lists, that is the first thing to fix. Send us a few of your documents and we will show you where your terminology drifts and how a glossary would align it.
How can we help?
Tell us what you need and we’ll get back to you with the solutions.