Define the scope first
Coordinate language, cultural context and delivery formats for narrative, interfaces, audiovisual and live-operation content.
Tell us the target language, purpose, receiving audience and desired timing. Related files for the same matter can share a contact, spellings, terminology and delivery plan; main text, attachments and supplementary records are checked separately.
Handling narrative and sound by medium
Game text, screen subtitles and dubbing scripts share characters and stories, but audiences receive information at different speeds and in different ways. Each medium needs its own treatment rather than one literal script for every use.
Character dialogue and episodic continuity
Use adjacent scenes, relationships and addressees to determine address and subtext, preserving the timing of misunderstandings and reveals. Recaps and later clips may reuse material, so check the actual edit. Query ambiguous isolated lines instead of imposing one unsupported plot interpretation.
Subtitle text and timing
Check cue times, segmentation and cuts against the video version, linking speakers and on-screen text. Condense while retaining action, causality and story information rather than delete mechanically to meet a character count. Flag unclear or overlapping speech and request scripts or confirmation.
Dubbing scripts and speakability
Retain recording cues by character, shot or segment and check pronunciations, pauses and speakability. Scope lip synchronization, duration and performance guidance separately while preserving story meaning. Subtitle delivery does not itself complete recording, mixing or voice performance.
Aligning assets, language and revisions
Editing and build updates can misalign multimedia content. Record asset versions, text resources and approved adaptations so production and product teams can continue reliably.
Reference packs and language decisions
A reference pack can include character profiles, names, pronunciation, audience and approved lines, distinguishing character traits from general style. Explain alternatives for wordplay or cultural references and record approved use. Keep forms of address consistent across episodes and updates.
Format delivery and picture review
Agree SRT, VTT, script tables or resource sheets and retain required timecodes, speakers and style data. Check overlaps, omissions and picture mismatches within scope. Burned-in subtitles, player rendering or game import need actual playback or builds; a text editor cannot confirm every display.
Revised assets and language rechecks
After recuts, compare timeline and dialogue changes to distinguish retiming from text revision. Track game updates by build and key and add reproduction paths to issues. Identify checked assets and unavailable versions so old video or build reviews are not carried over to a new release.
Materials and content
Narrative
Confirm markets, platforms, content types and audiences before preparing the language approach.
Subtitles
Keep character names, terminology, tone and text constraints consistent with the surrounding scene.
Voice scripts
Define the scope of subtitle timing, voice scripts, language testing and subsequent updates separately.
Translation and review priorities
- Confirm markets, platforms, content types and audiences before preparing the language approach.
- Keep character names, terminology, tone and text constraints consistent with the surrounding scene.
- Define the scope of subtitle timing, voice scripts, language testing and subsequent updates separately.
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.
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.
What should I prepare?
Provide a clear, complete source and relevant references. Include approved translations, required terms or name spellings where available. Share special receiving formats, statement or signature requirements and other supporting needs for individual confirmation.
Explore related services
Confirm the project details
Can a video be translated without a dialogue script?
Assess sound quality, languages, overlapping speakers and on-screen text, then scope listening, transcription and translation. Timestamp unclear speech for confirmation rather than guess from the plot. Include timing and playback checks explicitly against the supplied video revision.
Can existing subtitles be used directly for dubbing?
Subtitles are a reference, but dubbing requires speakability, turn-taking and any agreed duration or lip-sync checks. Prepare a recordable script and confirm pronunciations; removing timecodes alone is not adaptation. Scope recording, performance and post-production separately.
If a recut shifts timing by seconds, must all subtitles be redone?
Compare whether the change is a uniform offset or includes added, removed or moved dialogue. Retime and replay affected ranges for offsets, and revise text where content changes. Check the new asset rather than apply one duration difference blindly to every cue.