AI translation & post-editing

How do you keep game terminology consistent in AI translation?

Use approved terms, context notes, and expert review to keep character, skill, and item names consistent across languages and updates.

Keep concepts and usage rules consistent

Players should recognize the same skill in its description, combat messages and quest text. Consistency does not require mechanically repeating an identical string everywhere. A language may require inflections, and forms of address may change with relationships. Explain the concept and its usage conditions so linguists and reviewers can distinguish real inconsistency from valid variation.

At a glance
FieldWhat to recordWhat it resolves
Concept and definitionSkill function or character identityAmbiguous or similar names
Approved term and rulesTranslation, inflections and forms of addressValid variation versus inconsistency
Status and scopePending or approved; applicable releaseReuse of outdated translations

Give the glossary enough context for decisions

Alongside the source and approved translation, record the concept type, a short definition, usage context, forbidden alternatives and approval status. Explain differences between similar names. If no approved name exists, collect candidates for the language lead to review; a pending candidate is not a final rule. Tools can assist with extraction and detection, while naming and ambiguity need human judgment.

From term approval to verification

InputSource and setting
Step 01Collect
OutputTerm candidates

Identify terms and concepts

Use project materials to collect names for people, items and systems.

InputCandidates and context
Step 02Approve
OutputApproved glossary

Confirm names and usage

The language lead checks definitions and approves applicable forms.

InputGlossary and source
Step 03Apply
OutputTranslation and open questions

Work from shared rules

Use confirmed terms in translation and editing; record conflicts.

InputTranslation and findings
Step 04Verify
OutputReviewed, consistent translations

Review differences before making changes

Tools flag variation; people assess inflections and context.

Carry changes through every affected location

When a term changes, confirm the language, release and scope before finding affected translations. Check the current deliverables and the language assets still being reused. Record the approval and reason for change so an outdated term does not return in the next release. Review AIQA findings in context instead of automatically replacing every similar word.

Keep exploring

Find the right AI-assisted workflow for your game.

Share your target languages, content, volume, and schedule. We’ll review the materials with you and recommend a production approach, quality checks, and delivery plan.

Plan your localization