Game Localization · All Services
Game Localization Glossary — Building Consistent Terminology
Native translators. Translation Memory. In-build LocQA. Get a free quote →
A localization glossary is a managed list of game-specific terms and their approved translations in each target language. The glossary ensures that ‘Fire Sword’ is always ‘Épée de Feu’ in French, never ‘Épée de Flamme’ — regardless of which translator works on which section of the game, and regardless of how many updates and patches follow the initial release. Terminology inconsistency is one of the most common localization quality problems in games, and a well-maintained glossary is the primary tool for preventing it. This guide explains how to build and use a game localization glossary effectively.
What Goes in a Localization Glossary
A game localization glossary should include: character names (with decisions on transliteration, translation, or retention in each language); place names and faction names; game system names (the Crafting System, the Reputation System, the Prestige Track); ability and skill names (particularly for games with many abilities); item names that appear frequently; mechanic names (the Push mechanic, the Combo system, the Parry window); user interface labels that appear in many contexts (Inventory, Equipment, Bestiary); and any term that has a specific in-game meaning that differs from its everyday meaning. Do not attempt to pre-translate every string — glossaries are for recurring, high-value terms that require consistency, not for unique or contextual text.
How Glossaries and Translation Memory Work Together
Translation Memory (TM) and glossaries serve different functions that complement each other. Translation Memory stores complete segment pairs (source string and its translation), allowing automatic suggestion of identical or similar previous translations. A glossary stores individual terms and their approved translations, enforcing term consistency within new translations. In practice: TM handles macro-level consistency (previously translated full strings are reused automatically), while the glossary handles micro-level consistency (individual terms within newly translated strings are verified against approved terminology). Professional CAT tools enforce both — glossary terms are flagged or automatically highlighted when they appear in source text, prompting the translator to use the approved translation.
When to Build the Glossary
The glossary should be built before translation begins, not during or after. Building a glossary after translation begins means early-translated content may use different terms than later content, requiring a retroactive consistency pass. The process: (1) Extract all candidate glossary terms from your string export. (2) Identify terms that appear multiple times and/or terms where consistency matters (abilities, items, UI labels). (3) Review with your localization provider to confirm the glossary scope. (4) Have the glossary translated into each target language by a native speaker of each language who reviews the terms in the context of the game. (5) Lock the glossary before bulk translation begins. (6) Allow glossary updates only through a formal change process — undocumented glossary changes defeat the purpose.
Maintaining the Glossary Across Updates
A game’s glossary grows with the game. Each update adds new abilities, new characters, new items — each new term that appears more than once should be added to the glossary. When new glossary terms are added, they must be translated in each target language and added to the CAT tool’s glossary enforcement. At each update project start, review the glossary for terms that have been renamed or removed in the new version, and update the glossary accordingly. Your localization provider should maintain the glossary as a project asset and deliver the updated glossary alongside the Translation Memory at each project completion.
Frequently Asked Questions
How many terms should a typical game glossary have?
Glossary size depends on game content. A small indie game with simple mechanics and minimal dialogue might have 20–50 glossary terms. A mid-size RPG with named abilities, items, and characters might have 100–300 terms. A large MMORPG or RPG with thousands of items and abilities might have 500–2,000 terms. The goal is to capture the terms that matter most for consistency, not to pre-translate every string in the game. When in doubt, include terms that appear more than 3 times in the source text.
Does SandVox build and maintain the glossary as part of the project?
Yes. We build the localization glossary as part of every project. At project start, we extract candidate terms from your string export, propose the glossary scope, and have the terms reviewed by native-speaker translators in each target language. The glossary is maintained in our CAT tool (memoQ), enforced throughout translation, and delivered to you at project completion in a standard format. Subsequent projects build on and extend the existing glossary.
What happens if a term in the glossary needs to change after translation is done?
Glossary term changes after translation are a legitimate part of game development — character renames, ability renames, and UI changes happen. When a term changes, we assess the impact: how many strings used the old term, what needs to be re-translated, and whether TM entries for the old term should be updated or archived. We provide a change impact assessment and re-translate affected strings. This is significantly less expensive than if the change happens before the glossary was established — which is why building the glossary early reduces total project cost.
Start Your Game Localization Glossary Project
Tell us your word count, target languages, and platform. We return translated files ready for import — with Translation Memory and terminology glossary included. Free quote in one business day.