Definition
A termbase, sometimes written term base or called a terminology database, is a structured list of the terms a business uses for what it sells and does, each with its approved equivalent in every target language. The entries are the words that must be consistent for customers to follow the business across pages and channels: product and product line names, feature names, components, materials, service names, category words, and fixed interface phrases such as button and checkout labels.
Its reason for existing is simple. Terms drift because nobody decided them: each translator meets a term, picks a reasonable equivalent and moves on, and the next translator picks a different one. The tutorial on building a termbase and translation memory builds the file from the source content and puts it in the business's hands; this entry defines what it is and how it is used.
What each entry holds
A complete entry records more than the translation:
- The source term, with a one-line definition and an example sentence from real copy, because context decides the translation.
- The approved term per language, agreed with the reviewer for that market, with the reviewer's name and the date of approval.
- Do-not-translate status for the brand name, product line names and any feature names kept in the source language, with a note on how each behaves in a sentence.
- The searched-for word, where local keyword research found that the market searches with a different term from the approved one, and a note on which leads where.
- Rejected alternatives, each with the reason it was turned down, so a new translator does not bring it back.
What the termbase is not matters too. It is an internal resource for the people producing copy, not a glossary for customers, and it does not cover register, address, voice or formats, which belong to the localisation style guide.
In practice: ownership, corrections and new names
Ownership. The termbase is the business's record of decisions it has paid for and its reviewers have approved. The guide to choosing and managing translation suppliers puts it plainly: a supplier uses and adds to the termbase, the business keeps it, and a missing termbase is usually the cause when a supplier is blamed for inconsistent product terms.
Corrections. When a reviewer finds a wrong term, the fix goes into the termbase as well as the asset, or the old word returns with the next job. The guide to keeping localised content in step with the source logs a change to the termbase as a change to a reference file and shows every edition that uses it.
Checking. A central marketer who cannot read the language can still search a localised asset for the approved terms. The tutorial on reviewing localised copy in a language you do not speak does exactly that, which is one of the few language checks a non-speaker can make with confidence.
New names. A product name joins the termbase when it is chosen, not when it is first translated. The tutorial on naming a product or brand adds the chosen name to the termbase with its rules, usually as a term that is never translated.
A pet food maker settles one word for its puppy range
Pleffott Dog Food sold in its home market and two others. A customer email asked whether two product pages described the same range, and a search of the site in one market found the puppy range called three different things across 46 pages, depending on which of its 3 translators had written the page. The marketing manager created a termbase entry for the range with a definition and an example sentence, and asked the in-country reviewer to choose one approved term. The reviewer chose the word local shoppers used in search, and the 2 other versions were recorded as rejected, with reasons. The file went to every translator, and the 46 pages were corrected in the next update cycle.
Related terms
A termbase works beside a Translation MemoryA record, kept by the business, of each source sentence or segment and the translation a reviewer approved for it, so repeated wording comes back the same way., which stores approved sentences or segments rather than single terms, so repeated wording comes back the same way whoever translates it. Its entries are agreed and corrected through In-Country ReviewThe check of translated or adapted content by a native speaker who knows the market and category, who signs off the language before publication., the check by someone who knows the language and the market. And a term marked for TranscreationRewriting marketing copy for another language or market from the original brief, so the intended effect survives even when the words change., such as a piece of wordplay or a campaign coinage, is flagged in the termbase rather than given a single fixed equivalent, because it is rewritten for each market.
Common confusions
- A termbase and a translation memory are the same file. A termbase works at the level of single terms; a translation memory stores whole approved sentences.
- The supplier's termbase is the business's termbase. If the file lives only with a supplier, the decisions leave when the supplier does.
- Fixing the asset fixes the term. Unless the correction goes into the termbase, the old word returns on the next job.
- A termbase is a public glossary. It is an internal working file for the people producing copy; most of its entries never appear on the site.
- Every term should be translated. Brand and product line names are often kept in the source language, and the termbase records them as do-not-translate.
