Language services built around your work
Story, dialogue and quests
World-building notes, character profiles and quest flow provide the context for dialogue, item names and ability descriptions. Where humour or cultural references need adaptation, we explain the options for the development and publishing teams.
UI, store pages and live content
UI strings retain their IDs, variables, tags and placeholders and are checked against length limits. Store descriptions, release notes, event copy and support FAQs are adapted for the intended players.
In-context language checks
With a test build or screenshots, we can check truncation, line breaks, context, terminology and character voice. Issues are logged with their location, evidence, suggested wording and priority. Functional testing, age ratings and platform compliance are separate scopes.
Deliverables and version control
Agreed deliverables may include localized strings, character style notes, a glossary and a linguistic issue log. For continuing releases, an approved baseline separates new and changed content from text already signed off.
From the brief to usable deliverables
Define the brief
Agree the languages, readers, file formats, confidentiality terms and final approver.
Prepare the references
Review reference translations and terminology; identify missing context and open queries.
Translate, review and check
Complete the agreed linguistic work and check figures, names, completeness and context.
Deliver and maintain
Deliver the files, revision details and feedback records, with subsequent changes scoped clearly.
What to include in your brief
- Complete originals and editable files; scans should be clear and complete.
- Target languages, countries or regions, audience and final use.
- Terminology, approved translations, style guidance and required formats.
- Deadline, reviewers, confidentiality requirements and feedback process.
Project questions
Can we start with strings rather than a playable build?
Yes, provided there is enough information about characters, context, variables and length limits. Unclear strings become queries. Checking the actual display requires screenshots or a test build as a separate agreed step.
