Subtitles, dubbing & localization / FIELD NOTES
Localization quality checklist: meaning, language and playback
Review accuracy, natural expression, terminology and final presentation separately, with a contextual translation example and actionable issue log.
Why review the source picture when a translation already reads fluently?
Fluency is only one quality dimension. Meaning, context, language conventions and actual playback need separate checks. Apply the receiver’s language guide to the relevant delivery type; accessibility captions may also need meaningful non-speech audio information.
Check whether the information changed
Compare source and picture for names, numbers, negation, time, relationships and cause. Log uncertain passages for someone with context. Better phrasing is not a reason to add a promise, remove a condition or turn a possibility into a fact.
- Check numbers, units and negative statements
- Use the project terminology list
- Reference ambiguities by source and time
Review expression in its scene
Identify the speaker, listener, emotion and level of formality. Titles, descriptions, subtitles and dialogue may require different lengths, but identity and facts must stay consistent. Separate language preferences from meaning errors in review notes.
- Match tone to the relationship
- Look for misleading literal translations
- Check consistency across titles and body copy
Worked contextual example
At a café checkout, “It’s on me” could mean “这次我请” in Chinese. In a responsibility discussion, it may instead need “这事由我负责.” An issue log might say: “cue 18, payment scene, current translation implies responsibility; revise against the picture.” These are illustrative choices, not universal replacements.
- Explain the scene before proposing a fix
- Check surrounding dialogue after revision
- Judge repeated phrases in their own context
Close issues in the delivery file
Review timing, wrapping, on-screen text and audiovisual alignment in the final output. Classify issues as obstructing meaning, affecting consistency or improving expression, and specify release blockers. Record the revised version and verification result instead of closing a problem through an informal message alone.
- Give each issue an ID, evidence and state
- Review the actual delivery file
- Approve only the version with blockers resolved
Before you hand over the work
- Fluency, accuracy and playback are separate checks.
- Context is essential to translation review.
- Connect issue closure to a specific delivered version.
Demonstration projects and examples illustrate working methods. Follow the receiving party’s specifications and the scope agreed for your project.