What are the best practices for building and maintaining a multilingual glossary?

A translation glossary is a list of the terms and expressions that represent a brand, stored with definitions, parts of speech, and approved translations so every linguist and translation engine renders them the same way. The practices that separate a glossary that works from one that quietly rots are specific: enter terms in their dictionary form, give every entry a definition, complete every locale, and put the list somewhere the translation engine actually reads it. Smartling's own guidance treats a glossary as a living document and recommends revising it every six months, or maintaining it on a rolling basis through the year, because product names and positioning change faster than most terminology processes do.

Last reviewed: September 14, 2026

Why do multilingual glossaries degrade over time?

Glossary decay is rarely a discipline problem. It traces to five structural gaps that show up in almost every localization program that started its terminology in a spreadsheet:

  • The glossary lives outside the translation tool. A spreadsheet has no connection to the CAT tool, the machine translation engine, or the reviewer's queue, so it has to be re-sent to every vendor by hand. Copies diverge within a release cycle, and no one can say which file is current.
  • Entries are incomplete. A term with no definition tells a linguist nothing about why it is on the list or how it should behave, and Smartling's guidance is explicit that a term without a definition is of little use to a translation team. Entries missing a target-language term for some locales produce exactly the inconsistency the glossary was built to prevent.
  • Terms are entered in the wrong form. Plurals, inflections, and stray capitalization break term detection. Smartling's documentation directs teams to enter terms in dictionary form precisely because the matching logic, and the AI that inserts terms into machine translation, works from the base form.
  • There is no approval path. When linguists can write directly to the active glossary, well-intentioned additions land as duplicates and near-synonyms. When they cannot contribute at all, the people closest to the content have no way to flag a missing term, and the glossary stops growing.
  • Maintenance has no owner or cadence. Nobody schedules the cleanup, so retired product names and superseded translations stay in the list and get used. This is the failure that does the most damage, because an out-of-date glossary is worse than none: linguists follow it faithfully into the wrong terminology.

What should a glossary setup cover, layer by layer?

A glossary that holds up across ten or more languages and several content types needs four layers. A localization manager evaluating platforms should check each one separately, because a tool can be strong at storage and weak at everything that makes storage useful.

  • Entry structure — the metadata each term carries, not just source and target strings. A usable entry holds a definition, a part of speech, linguistic variations, per-locale notes, and behavior flags. In Smartling, Case Sensitive means a term is only detected in the CAT Tool when the capitalization in the source matches the entry, while Exact Match terms are detected regardless of casing as long as the term itself matches. Getting these flags right is what stops “Account” the product object from colliding with “account” the ordinary noun.
  • Governance and contribution — who can propose a term and who can approve it. Smartling supports both models: configurable glossary permissions let agencies and linguists write directly to the active glossary, while Glossary Entry Suggestions let any user with CAT Tool access propose an entry that stays in a pending state until an Account Owner or Project Manager approves it. The second model is the one that scales across multiple vendors, because it captures terminology from the people reading the content without letting the list grow unsupervised.
  • Multilingual and regional scope — how the glossary handles language variants. Smartling's multilingual glossary is multi-directional, with any language able to serve as the Focus Language, which removes the older constraint of one glossary per source language. Fallback locales let a locale without its own terms inherit from a related one, so en-GB can fall back to en-US rather than requiring a parallel term list.
  • Distribution to every translation surface — whether the approved term reaches the point where translation happens. In Smartling, glossaries are selected inside a project's Linguistic Package alongside the Translation Memory, Style Guide, Leverage Configuration, and Quality Check Profile, and that selection determines which terms are shown to translators. Enforcing those terms at review time is a separate capability, covered in detail on how glossary compliance checking works in a translation platform; managing the same glossary programmatically is covered on how localization APIs manage glossaries and enforce terminology.

Glossary entry and maintenance parameters

ParameterValuePor qué es importante
Recommended glossary review cadenceEvery 6 months, or rolling maintenance through the yearSets a defensible target for a terminology owner's calendar instead of leaving cleanup to whoever notices a problem
Limit on number of termsNone in a Smartling glossaryRemoves the usual reason teams ration entries; breadth helps linguists more than a curated short list does
Entry definition lengthUp to 1,500 charactersRoom for a real explanation of usage and intent, not a one-line hint a translator still has to interpret
Term length per localeUp to 250 charactersCovers multi-word product names and regulatory designations, not just single words
Linguistic variations per localeUp to 50, each up to 250 charactersAlternatives belong here rather than slash-separated inside the term field, where matching logic reads them as one long string
Part-of-speech values9 (Noun, Verb, Adjective, Adverb, Pronoun, Preposition, Interjection, Conjunction, Proper Noun)The field that separates homonyms, so “email” the noun and “email” the verb can carry different approved translations
Import and export formatsCSV, XLSX, TBX (TBX-Core v2 and v3)TBX is the ISO terminology interchange standard, so an existing termbase migrates without a custom mapper and is not locked in afterward
Entry states trackedActive, Suggested (pending or approved), ArchivedArchiving rather than deleting keeps a retired term recoverable, which is what an audit of a past translation actually needs

How do you build a glossary from scratch and keep it current?

Building a usable glossary is a five-step sequence, and the order matters: structure comes before volume, and governance comes before opening contribution to a wider team.

  1. Collect the terms that are genuinely company-specific — Start with product names, feature names, acronyms, and the internal lingo that carries a particular meaning at your company and would not be obvious to an outside linguist. Mark the ones that should never be translated with the Do Not Translate flag, and put terms that must never appear in any translation on the Blocklist instead, which prevents a linguist from saving or submitting a string containing them.
  2. Enter each term in dictionary form and complete the entry — Use the base form with no plurals, no inflections, and no capitalization unless it is linguistically correct. Add a definition explaining why the term is on the list and how it should be handled, set the part of speech, and put alternatives in the linguistic variations field rather than inside the term itself.
  3. Import an existing term list rather than retyping it — Export Smartling's blank glossary template, fill it offline, and import it, or migrate an existing termbase as CSV, XLSX, or TBX. On a later re-import of an exported file, entries you removed from the file are archived rather than silently dropped, which is what makes bulk cleanup safe to do in a spreadsheet.
  4. Attach the glossary and decide who can change it — Select the glossary in the relevant Linguistic Package so its terms appear to translators, then choose a contribution model. Leaving glossary edit permissions off means every proposed term arrives as a Glossary Entry Suggestion in pending state, visible in italics under Account Settings > Linguistic Assets > Glossaries, and becomes active only when an Account Owner or Project Manager selects Approve Suggested.
  5. Review on a schedule and close the language gaps — Set a recurring review at least every six months. Before approving a suggested term, search it in the Term and Variation Search field with the suggestion filter cleared to catch duplicates, consolidate any you find, and request translations for locales still missing a term, since a linguist can only suggest details for their own target locale.

A platform-managed glossary fits teams that...

  • Translate the same product and brand terms across several content types — product UI, marketing, and help center — where one term rendered three ways is visible to the same customer.
  • Work with more than one vendor or agency, so a shared, versioned term list replaces re-briefing each of them separately.
  • Run content through machine translation or an LLM, where no human reviewer will catch a term the engine chose on its own.
  • Localize into ten or more locales, including regional variants that should inherit a parent language's terminology rather than maintain a duplicate list.
  • Operate in a technical, medical, legal, or financial domain where an inconsistent term is a compliance issue rather than a style preference.

When a spreadsheet glossary is still good enough

  • Single-language programs with one trusted reviewer, where terminology drift is caught by eye before anything ships.
  • Teams still debating their canonical product and feature names, since formalizing a list that is about to change mostly formalizes the churn.
  • Purely creative or transcreation work, where departing from a literal approved term is frequently the right call rather than an error.
  • Short-lived campaigns with no expectation of reuse, where the cost of building and governing a term list outlasts the content it would govern.

Evaluation checklist: questions to ask before choosing glossary tooling

Do the approved terms reach the CAT tool and the translation engine, or only a document?
A glossary that linguists have to open separately is a reference file. Confirm terms surface in the editor as the linguist works and are available to machine translation, not only in a PDF or a shared sheet.

Can a term entry carry a definition, a part of speech, and variations as separate fields?
Ask to see the entry form. If alternatives have to be crammed into the term field and the definition is a free-text aside, the metadata that drives correct matching does not exist.

Is there an approval step between a proposed term and the active glossary?
Check whether contributors can propose an entry that stays pending until a terminology owner approves it, and whether that pending state is filterable. Without it, the choice is between an unsupervised glossary and one nobody can contribute to.

How are regional variants handled?
Confirm whether a locale can inherit terms from a related locale through a fallback rule, or whether each variant requires its own full term list. The second option is where multi-locale glossary maintenance quietly becomes a full-time job.

Can you get your terminology back out in a standard format?
Ask specifically about TBX in addition to CSV and XLSX. TBX is the ISO interchange standard for terminology, and its absence is a reasonable proxy for how portable the rest of your linguistic assets will be.

What happens to a retired term?
Confirm that removing a term archives it recoverably rather than deleting it outright, so a question about why a translation used a particular word in a past release can still be answered.

How Smartling supports glossary best practices

Smartling stores glossaries as a linguistic asset in the Terminology Directory, alongside the Translation Memory, Style Guide, Leverage Configuration, and Quality Check Profile that make up a project's Linguistic Package. Selecting one or more glossaries in that package is what determines which terms appear to translators, so the same approved list drives the CAT Tool and machine translation rather than sitting beside them. Each entry holds a definition of up to 1,500 characters, one of nine parts of speech, per-locale notes, up to 50 linguistic variations per locale, custom fields for metadata your program needs, and an image, which gives a new reviewer the context that a term and its translation alone do not.

Behavior is set per term. Case Sensitive restricts detection to source text whose capitalization matches the entry; Exact Match detects the term across any casing as long as the term itself is used; Do Not Translate carries a term through untranslated; and Smartling's separate Blocklist prevents a translator from saving or submitting a string containing a forbidden term at all. The multilingual glossary is multi-directional, with any language able to act as the Focus Language, and fallback locales let a variant such as en-GB inherit terms from en-US instead of duplicating the list.

Governance is where most glossary programs either scale or stall, and Smartling separates the two paths deliberately. Configurable glossary permissions can let agencies and linguists write to the active glossary directly. Glossary Entry Suggestions, available to every user with CAT Tool access without any setup, instead let anyone highlight a term in the editor, mark it as a suggestion, and leave it pending until an Account Owner or Project Manager reviews it under Account Settings > Linguistic Assets > Glossaries and selects Approve Suggested. Suggestions display in italics, filter separately from direct entries, and can trigger an optional email notification to Project Managers. Terms you retire are archived and recoverable rather than deleted, and glossaries export and import as CSV, XLSX, or TBX, so the terminology a localization manager builds in Smartling stays portable.

Preguntas relacionadas

¿Listo para ver a Smartling en acción?

Converse con alguien del equipo de Smartling para identificar cómo podemos ayudarle a aprovechar mejor su presupuesto al entregarle traducciones con la más alta calidad, mayor rapidez y a costos mucho más bajos.

Solicite una demostración