What Happens When You Localize a Game Without a Glossary — How to Prevent 'Potion' from Being Called Six Different Things

Imagine localizing a single RPG into six languages. Three hundred characters, ten thousand lines of dialogue, and the word "potion" appears hundreds of times throughout the game. Then, after recording wraps, QA discovers a problem. In English it's "Potion," in German "Trank," in Japanese "ポーション"—all consistent. But in the Spanish version, the same item is called "Poción," "Elixir," and "Brebaje" interchangeably, and in French, different characters alternate between "Potion" and "Philtre." Now you have to re-record entire language tracks. This is what actually happens when you produce multilingual voice-over for a game without a localization glossary.

Game localization is not just translating text. The moment in-game voice enters the picture, a single inconsistent term disrupts player immersion and hits the studio with a double blow: rework costs and schedule delays. As the game dubbing market standardizes and major publishers launch with ten or more languages on day one, the localization glossary has shifted from optional to essential infrastructure. This article examines the concrete problems caused by missing glossaries and the practical strategies to prevent them.

Key Takeaways

Why 'Term Inconsistency' Is Fatal in Game Localization

Unlike films or series, games expose players to the same world setting repeatedly over dozens of hours. If "Mana Potion" is called "Mana Potion" in the first village but suddenly becomes "Magic Elixir" in a mid-game dungeon, players are confused: is this the same item or a new one? In a text-only game, you can patch it. The moment in-game voice is involved, the problem becomes complicated. Changing a line a voice actor has already recorded means re-booking the studio, re-hiring the actor, and re-editing—three steps all over again.

A mobile RPG publisher preparing a six-language simultaneous launch once assigned dialogue to different translators without a glossary. The result: the same boss monster was called "Shadow Lord" in English, but in Spanish it mixed "Señor de las Sombras" and "Lord Oscuro," and in Japanese it alternated between "影の王" and "シャドウロード" depending on the character. QA caught it, but by then over 300 characters' lines had been recorded. The team ended up re-recording roughly 40% of the affected language tracks, delaying launch by two months.

International standards (e.g., ISO 704, ISO 30042, ISO 17100) emphasize that multilingual terminology management requires a single concept to be translated and used consistently across languages. Without a glossary, the same concept risks being interpreted differently in each language, leading to lower localization quality and higher rework costs. [Enosema Foundation — Multilingual terminology](https://www.enosema.org/docs/documents/enosema-multilingual/document.html)

To prevent this, Polita builds glossaries with clients at project kickoff. Core terms—proper nouns, skill names, item names, place names—are defined per language and shared across translation, voice talent, and QA teams. In one mobile game project processing over 10,000 lines of in-game dialogue, terminology consistency was maintained so well that the client received zero term-related revision requests during QA. This demonstrates that Polita goes beyond generating voice with AI; it has the capability to design the entire localization workflow.

Concrete Scenarios That Unfold When You Record Multilingual Dialogue Without a Glossary

Scenario 1: Different Translators Choose Different Terms

Large game projects often split languages among multiple translators to compress schedules. The problem: Translator A renders "Health Potion" as "Heiltrank" in German, while Translator B uses "Gesundheitstrank" for the same term. Both are grammatically correct, but in-game they must be unified. Without a glossary, these inconsistencies are hard to catch during recording and emerge only during QA or in post-launch user feedback.

Scenario 2: Voice Actors Ad-Lib Term Changes

Actors receive a script and record, but sometimes they tweak words or substitute synonyms for more natural delivery. For example, the script says "Magic Staff," but the actor judges "Wizard's Staff" sounds better in context and reads that instead. Without a clearly shared glossary, the director may not flag it as a problem, resulting in the same item being called different things in different scenes.

Scenario 3: Cross-Language Cultural Context Confusion

When localizing "Dragon," the term is clear in Western fantasy contexts, but in East Asian languages the nuance differs between "용 (龍)" and "드래곤." Without a glossary, translators make individual judgment calls, and the same monster might be "드래곤" in Korean, "龙" in Chinese, and a mix of "ドラゴン" and "竜" in Japanese. This is not just a translation issue—it directly affects lore consistency and player experience.

To prevent these problems, global IT companies recommend treating glossaries not as simple word lists but as systematic management documents that include definitions, context, grammatical information, usage examples, and exclusions. This ensures translators, voice actors, and QA all work from the same standard. [Microsoft Learn — Manage terminology - Globalization](https://learn.microsoft.com/en-us/globalization/localization/managing-terminology)

Polita prevents these scenarios by managing glossaries as living documents that include not just words but context, tone, and pronunciation guides. For example, for the boss name "Shadow Lord," the guide might specify "dignified, low tone, never abbreviated," preventing actors from reading only "Lord" or ad-libbing "Shadowy Lord." Combined with Polita's infrastructure supporting over 70 languages, this enables culturally aware, consistent dubbing across languages.

Practical Guide to Building a Glossary: What, When, and How to Define

A game localization glossary should begin early in the project—ideally before dialogue writing is finalized. Below is the glossary-building process Polita uses in actual game dubbing projects.

Which Terms Belong in the Glossary?

Not every word needs to go in. Prioritize:

Game localization practitioners emphasize the "one concept, one term" principle and recommend systematic glossary operations: registering forbidden variants, requiring definitions, locking the glossary before translation begins. [hansem.com — Terminology Management for Equipment Manuals](https://hansem.com/resources/guides/manual-terminology-management/)

Polita has experience unifying over 300 courses for an online education platform under a single voice and terminology standard. This proves that Polita's glossary system works not only for games but also in education and e-learning, where term consistency directly affects learning outcomes. For game studios, this system enables maintaining the same terminology standard across the main game, future DLC, seasonal updates, and even sequels.

Standardization in the Large-Scale Multilingual Game Dubbing Market and the Importance of Terminology Management

The game industry has made supporting ten or more languages on launch day the new standard. Major publishers pursue "Global Day One" strategies, releasing all language versions simultaneously to prevent spoilers and revenue loss from regional launch gaps. This puts unprecedented pressure on localization teams. When you must record and QA 15 languages, 300 characters, and tens of thousands of lines in six months, rework caused by term inconsistencies can collapse the entire project.

The global game localization industry defines a glossary as "a curated list of established in-game terms and translations" and emphasizes it as an essential tool for all participants—translators, editors, PMs—to maintain consistency and accuracy. [Allcorrect — Localization Glossaries: Importance and Purpose](https://allcorrectgames.com/insights/localization-glossaries-what-they-are-and-why-they-matter/)

Polita handles these large-scale projects within standard turnaround, backed by infrastructure that processes over 45,000 videos annually and supports over 70 languages. One animation client dubbed a full 26-episode season in three languages simultaneously, and an OTT original drama delivered 12 episodes on broadcast schedule. This shows that Polita has not only AI dubbing technology but also the process and personnel to manage large-scale multilingual projects.

In game dubbing especially, terminology consistency is tied to brand trust. Player communities are sensitive to translation errors, and if word spreads on social media that "potion" is called different things in different languages, it raises doubts about the game's overall polish. Conversely, games with consistent terminology and solid world-building localization are celebrated in fan communities as "thoughtfully localized," driving long-term user loyalty.

Polita's Glossary-Driven Workflow: Combining AI Dubbing and Human Review

Polita's strength lies in its hybrid model combining AI dubbing technology with expert editing and review. This combination shines especially in projects like game dialogue, where terminology consistency is critical. AI recognizes terms registered in the glossary and generates voice according to per-language pronunciation and tone guides. Experts then review context, emotion, and timing, and verify that terms are implemented consistently.

For example, if the boss name "Shadow Lord" is registered in the glossary, AI generates it with identical pronunciation and tone throughout the script. If an actor ad-libs "Lord of Shadows," the expert review stage catches it and reverts to the original term. This process is faster than manual work from start to finish and more accurate than pure AI automation.

Polita's Pro plan ($20–25 per minute) offers voice conversion technology that reproduces the original actor's timing, breath, and emotion—especially useful in game dubbing. For instance, if a character in the Japanese original urgently shouts "potion" in a scene, the English, Spanish, and German versions can maintain the same timing and urgency. This goes beyond translating words; it carries the original's directorial intent across languages.

Polita includes voice cloning as standard, which is advantageous when a game studio wants to extend a specific voice actor's voice across multiple languages. For example, cloning a Korean original voice actor's voice into English, Japanese, and Chinese maintains the character's identity consistently across languages—a key factor in building a global fanbase.

Long-Term Impact of Glossaries Across a Game's Lifecycle

Once built, a glossary can be reused throughout a game's entire lifecycle. Applying the same terminology standard across the main game, DLC, season passes, spin-offs, and even sequels gives players a consistent world-building experience across the series. For studios, this also translates to cost savings. There's no need to redefine terms and re-explain them to translators and voice actors for every new project.

Polita provides an NDA-based secure workflow, enabling safe handling of unreleased content (pre-broadcast dramas, unreleased games). Game studios can build glossaries with Polita before launch, validate multilingual voice during beta testing, and release all languages simultaneously at official launch. This is an essential partnership for publishers executing Global Day One strategies.

Polita's Enterprise plan offers long-term partnerships and volume discounts, making it suitable for series or live-service games with continuous content additions. One mobile game signed a long-term contract with Polita and rapidly localizes new character dialogue added in monthly updates under the same glossary standard. This is a model that achieves both operational efficiency and quality consistency.

Preventing Term Inconsistency Is a Process Problem, Not a Technology Problem

Term inconsistency in game localization happens not from lack of technology but from process design failure. No matter how skilled your translators and voice actors, you cannot guarantee consistency without a glossary as a common standard. Especially in environments like multilingual voice recording, where multiple language teams work simultaneously, the glossary is the only mechanism that binds the project together.

Polita has AI dubbing technology, but it creates real value by integrating that technology into a process "finished by humans." From glossary building, to real-time collaboration among translators, voice actors, and QA teams, to feedback incorporation through up to two free revision rounds, Polita's workflow is designed with the understanding that game localization is not just translation—it's world-building.

As the game industry standardizes global simultaneous launches and players expect perfectly localized experiences in their native languages, term inconsistency is no longer tolerable. The way to prevent the disaster of "potion" being called six different things in six languages is clear: build a glossary at project kickoff, share it across all teams, and verify consistency throughout recording and QA. Polita is a partner that can execute this process at scale—over 70 languages, over 45,000 videos annually.

---

In game dubbing, terminology consistency is more than technical polish—it's essential for players to trust and immerse themselves in the world. The larger the multilingual project, the more the glossary becomes not just a reference document but infrastructure that determines project success. Polita's glossary-driven workflow and AI-human hybrid model are a practical solution for game studios to deliver a consistent brand experience in global markets and prevent rework costs and schedule delays. If the game you're preparing will launch in multiple languages, start with the glossary before dialogue writing is finished. That's the first step toward being remembered in the community as "thoughtfully localized" after launch.

Frequently Asked Questions

Q. When should I build a game localization glossary?

Immediately after dialogue writing is complete, at least two weeks before recording begins. At this point, select 100–300 core terms and lock per-language translations so translators, voice actors, and QA all work from the same standard, preventing term inconsistencies at the source.

Q. What must be included in a glossary?

Proper nouns (character names, place names, organization names), game system terms (skills, items, stats), world-specific terms, and culturally nuanced words that can be interpreted differently across languages. Polita adds pronunciation, tone, and stress guides to prevent actors from ad-libbing term changes.

Q. Can AI dubbing maintain terminology consistency?

Yes. Polita's AI dubbing accurately recognizes terms registered in the glossary and generates voice according to per-language pronunciation and tone guides. Expert review then checks context, emotion, and timing, ensuring terms are implemented consistently even in large-scale multilingual projects.

Q. How much does re-recording due to term inconsistency cost?

Depending on project scale, typically an additional 20–30% of total production costs. Re-hiring actors, re-booking studios, and re-editing are all required. Polita's glossary-driven workflow prevents this rework, helping clients complete projects within standard turnaround and budget.

Q. Can I use the same glossary for sequels or DLC?

Yes. Once built, a glossary can be reused throughout a game's entire lifecycle. Polita provides version control, enabling the same terminology standard across the main game, DLC, seasonal updates, and sequels, with the ability to add new terms as needed. This is key to long-term cost savings and brand consistency.

---

Free sample and quote: [polita.ai](https://polita.ai#contact) | sales@voithru.com

References

- International standards (e.g., ISO 704, ISO 30042, ISO 17100) emphasize that multilingual terminology management requires a single concept to be translated and used consistently across languages. — Explains that in multilingual environments, one concept must be managed consistently across languages according to international standards (ISO 704, ISO 30042, ISO 17100, etc.). - Global IT companies recommend treating glossaries not as simple word lists but as systematic management documents that include definitions, context, grammatical information, usage examples, and exclusions. — Explains that glossaries should include definitions, context, classification, grammatical information, usage examples, and exclusions to prevent translation confusion and inconsistency. - Game localization practitioners emphasize the "one concept, one term" principle and recommend systematic glossary operations: registering forbidden variants, requiring definitions, locking the glossary before translation begins. — Presents concrete operational procedures for glossaries: "one concept, one term" principle, registering forbidden variants, requiring definitions, locking before translation begins. - The global game localization industry defines a glossary as "a curated list of established in-game terms and translations" and emphasizes it as an essential tool for all participants—translators, editors, PMs—to maintain consistency and accuracy. — In the game localization context, defines glossary as "a curated list of established in-game terms and translations," emphasizing it as an essential tool for translators, editors, and PMs to maintain consistency and accuracy.