Coreon
Multilingual terminology tool that organizes terms as a concept map instead of a flat list.
- Developer API
- Glossary or termbase support
Terminology management is the work of deciding how key words are written and translated, and then making sure everyone follows those decisions. A termbase holds each concept with its approved term in every language, plus notes such as definitions, forbidden alternatives, part of speech and where the term is used. When translators, writers and machine translation all draw on the same termbase, a product feature has one name in each language instead of four.
The tools here cover different points in that process. Trados MultiTerm is a dedicated terminology system that builds termbases for Trados projects, and a good termbase system adds approval workflows so new terms are requested, reviewed and released. Coreon organizes terms as a map of related concepts, which helps in technical fields with deep vocabularies. Acrolinx and Congree check source writing against terminology and style rules before it reaches translation, which stops inconsistent terms at the start. Sketch Engine is a corpus tool that helps terminologists find candidate terms in large collections of real text.
Start small. A list of a few hundred terms that matter most, such as product names, feature names, terms that must stay in English and words customers often see, does more good than an attempt to capture every word. Decide who can add and approve terms in each language, usually a mix of a central owner and reviewers in each market.
Then connect the termbase to the tools that produce text. Most translation management systems read termbases in TBX format and highlight terms for translators. Some machine translation engines accept glossaries so the approved term is used automatically. Writing assistants can flag the wrong term while a source author is still drafting. A termbase that lives only in a spreadsheet tends to drift out of use.
What a featured listing costs ยท from $99 a month
Multilingual terminology tool that organizes terms as a concept map instead of a flat list.
Terminology management from RWS for building termbases that plug into Trados projects.
Content governance software that checks writing against company terminology and style rules before it goes to translation.
Authoring assistant that checks source text for terminology, style and grammar inside the editors writers already use.
Corpus tool used by linguists and terminologists to extract candidate terms and see how words are used in real text.
Plan for change as well. Products are renamed, features are retired and markets prefer different words over time. Each entry should show its status, such as proposed, approved or deprecated, and the date it changed, so translators know which term to use today and can still recognize the old one in legacy content.
Watch for the terms that cause trouble. Short words with several meanings, terms that differ between regions of the same language, such as Brazilian and European Portuguese, and brand names that sound like ordinary words all need extra notes. A short usage example in each entry often prevents more errors than a definition does.
Finally, measure use. Several tools can report how often approved terms appear in translations and where forbidden variants still slip through. Those reports show which teams or vendors need help and which entries are unclear.
A glossary is often a simple list of terms and translations. A termbase is a structured database where each entry is a concept with terms in several languages, definitions, usage notes and status. Small teams can start with a glossary and move to a termbase as the list grows.
TBX is a standard XML format for exchanging terminology between tools. If your termbase can export and import TBX, you can move it between translation management systems and terminology tools without retyping entries.
Several engines and platforms accept glossaries and apply the approved term during translation. Results are usually good for nouns and names and less reliable for words that change form with grammar, so QA checks are still worth running.
Usually one central owner, often in localization or documentation, with reviewers in each language market who approve terms. Product and marketing teams should be able to request new terms early, before content is written and sent for translation.