In-game text and UI, store and marketing content, and manga, anime, and comic translation — localized with terminology, tone, and character voice kept consistent across languages and updates.
In-game strings, menus and UI, dialogue and subtitles, item and skill names, patch and update notes — with a glossary that keeps every update consistent.
Manga, webtoon, and comic translation and anime subtitles — adapted for tone, character voice, cultural references, and lettering constraints, so it reads naturally.
Store listings, app descriptions, trailers and campaign copy, and community content — so the marketing around the title matches the localized experience.
Character names, item and skill terms, and world vocabulary are locked in a maintained glossary — so a term is not translated one way in launch content and another in the next patch.
Dialogue, humor, and character voice are adapted by people who read for rhythm and register, not just correctness. That is what keeps players and readers immersed.
Chinese titles and manhua going global, and international games and manga entering Chinese-speaking markets, inside one workflow.
Live games and serialized manga fail on inconsistency more than on any single mistranslation. Keeping terminology and voice controlled across every update is the whole job.
A player does not experience your game as separate files. They read a skill name on the store page, see it in the UI, hear it in a voice line, and read it again in a patch note — and they notice when those four disagree, even if each one was translated well on its own.
That is why terminology in games fails more often than translation does. The asset set is unusually fragmented: each piece lives in a different tool, ships on a different cadence, and is usually owned by a different team.
| Asset | Usually owned by | Ships when |
|---|---|---|
| In-game UI and system strings | Engineering / build | Every release |
| Dialogue and voice scripts | Narrative, then a recording studio | Ahead of the build |
| Item, skill and character names | Design | Whenever content is added |
| Store listing and screenshots | Publishing / storefront console | Independently of the build |
| Marketing and campaign copy | Marketing, often an agency | To a campaign calendar |
| Patch notes and community posts | Community management | Per patch, at speed |
Six owners, six pipelines, one player. Consistency is a property of the whole set, not of any single file — so it cannot be achieved by translating each file well. It has to be enforced across them.
We run one termbase across all of it, and it is versioned per release rather than maintained as a living document nobody can pin down. When a build introduces a new skill name, that term enters the base once and every downstream asset inherits it — including the store page and the agency's campaign copy, which are the two that normally drift first because they never touch the build pipeline.
The same resource files you sent, with keys and placeholders untouched. Nothing that requires a developer to reassemble it by hand.
Not a document that silently changes. You can see which terms existed at the time of any given build, which is what makes a disagreement between the store page and the UI diagnosable rather than arguable.
Every release adds vocabulary. Surfacing it as its own list is what stops a term from entering the game in one patch and being translated differently in the next.
Strings checked where they actually appear — in the build or against context screenshots. A line can be correct in the file and wrong on screen: truncated in a button, breaking mid-word, or colliding with a character limit that only exists in one language.
Where text overran, what was shortened, and whether the short form is still correct — rather than a silent trim to the first N characters.
The verification layer above is the same discipline set out in the localization testing checklist, applied to a build instead of a website.
In-game text and UI, dialogue and subtitles, store and marketing content, patch notes, and cultural adaptation of names, references, and humor — keeping terminology and character voice consistent across every language and update.
One termbase covers every asset (UI strings, dialogue and voice scripts, item and skill names, store listing, marketing copy, patch notes and community posts) and it is versioned per release rather than kept as a living document. The assets that drift first are the store page and agency-written campaign copy, because they never pass through the build pipeline; enforcing the same base across them is the part that actually prevents a skill name reading three different ways in front of the same player.
New vocabulary from each build is captured and delivered as its own list rather than folded silently into the glossary. That is what stops a term entering the game in one patch and being translated differently in the next, which is the most common way live games lose consistency over time.
Both. Strings are checked in context (in the build, or against context screenshots) because a line can be correct in the file and wrong on screen: truncated in a button, breaking mid-word, or exceeding a character limit that only bites in one language. The pass returns a truncation and fit report rather than a silent trim.
Where text must be shortened, the short form is written deliberately and confirmed to still be correct and idiomatic, not cut to the first N characters. Cases that cannot be solved in text (where the constraint is the layout itself) are reported back so the decision sits with your UI team rather than being hidden in the translation.
Yes — manga, webtoons, comics, and anime subtitles, with attention to tone, character voice, cultural references, and lettering constraints. The goal is a version that reads naturally, not a literal transfer that loses the original's rhythm.
We maintain a project glossary and style guide covering character names, item and skill terms, and world vocabulary. Every update runs against those references — so a term introduced in one patch is not translated differently in the next.
In-game UI and text, dialogue and voice scripts, store listings and app descriptions, marketing and campaign material, patch notes, and community and support content — content that ships continuously and must stay consistent.
Tell us the title, languages, and update cadence — we'll keep tone and terminology consistent as it ships.
Talk to Us →