Typical project materials
Localise narrative, interfaces, store pages and operational content using screenshots, variables and text-space constraints.
- Game narrative, character names and dialogue
- Interfaces, help content and product strings
- Store descriptions, subtitles and release updates
From narrative context to on-screen text
Language in digital products lives in story branches, interfaces and moving images. Each text type needs its own context and constraints; a string table detached from use is not a complete project reference.
Character voices and quest branches
Use relationships, worldbuilding and adjacent lines to determine address, voice and when information is revealed. Align quest names, items and choices while preserving speakers and branch conditions. If one line serves different emotional contexts, ask whether resources can be split rather than force one wording everywhere.
Interfaces and dynamic variables
Check buttons, prompts, achievements and store items in their interaction contexts, distinguishing actions from states. Preserve resource variables, tags and line-break syntax while considering changing numbers, plurals and word order. Offer short alternatives and context queries where space is insufficient.
Subtitles and visual timing
Use the agreed video or build to check speakers, on-screen text and subtitle continuity. Review pauses and speakability separately for dubbing scripts. Explain adaptation choices for jokes, wordplay and cultural references without deleting plot information. Scope timing and text work independently.
Connecting language feedback to resources and builds
Linguistic testing needs identifiable resources and reproducible screens. Delivery should help development and live teams locate the build, path and language associated with each issue.
Reproducible language issues
Issue records can include build, key, language, reproduction steps, screenshot and suggested text. Distinguish truncation, inconsistent terms, context errors and display faults. Language staff describe wording issues; product teams handle layout or functional changes. Agree rechecks against the new build and accessible paths.
Live updates and resource differences
Compare event, season and item updates by stable keys, separating removed, changed and new entries. Check current rules and character context before reusing old translations. Track strings added after a freeze in a separate batch so release owners can reconcile completeness.
Style decisions and resource handoff
Record character voices, forms of address, disallowed terms and approved adaptations, preserving resource structure and encoding. Store copy, in-game text and support material share facts but have different limits. Review after import needs actual screens or a build; spreadsheet review alone cannot confirm runtime appearance.
Establish shared working references
Provide project background, intended readers, source versions, terminology or approved translations, and the process for consolidating the designated specialist reviewer’s comments. Align file identifiers, names, units and change markers across teams and batches.
The language team handles the agreed translation, review and format checks. Technical, medical, financial or legal judgments in the source require the relevant professionals. Questions are documented and resolved rather than silently supplementing source conclusions.
A clear process at every stage
- 01
Define the purpose
Specify files, languages, volume, receiving requirements and timing.
- 02
Agree the plan
Confirm scope, references, review responsibilities, supporting work and delivery.
- 03
Translate and review
Use subject references and check terms, numbers, tables and versions.
- 04
Deliver and coordinate
Deliver the agreed files, consolidate feedback and confirm later updates.
Delivery, price and timing
Price and timing are assessed against language direction, word or page volume, subject matter, source clarity, editability, layout, review and supporting requirements. Changes to the source, languages or supporting work require a revised scope and plan.
Agree Word, PDF, Excel, subtitle or other formats, including any editable files, paper copies, statements or signatures actually needed. Supporting arrangements are defined for the particular purpose and receiving requirements.
Explore related services
Confirm the project details
Can work start without a playable build?
Text work can begin with character references, quest flows, screenshots and string notes, with context gaps logged. Without a runtime environment, truncation, triggers and every branch cannot be confirmed. Arrange those checks when a build is available under an agreed scope.
What if one Chinese string is shared across several buttons?
Provide each location and action to assess whether one target form works. Where grammar, gender or meaning conflicts, suggest separate keys or wording suitable across contexts for developer confirmation. Do not damage variables or resource structure to force a solution.
Does linguistic testing include fixing every display issue?
Separate issue detection, wording advice, technical fixes and rechecks. Agreed reports can provide evidence and suggested text while developers handle fonts, layout and code. Define platforms, languages and paths from actual build access; sampled checks do not imply complete path coverage.