Subtitles, dubbing & localization / FIELD NOTES
Multilingual version matrix: keep every asset aligned
Track picture, captions, audio, metadata and artwork with stable identifiers, dependencies and separate approval states.
How do you avoid publishing the wrong language or platform version?
“The Japanese version is finished” hides several assets: picture, audio, subtitles, title, description and artwork. A version matrix records those dependencies and links to the actual files; it complements rather than replaces your asset folders.
Define one row precisely
Use one row per content ID, target locale, delivery use and picture version. Give subtitles, audio, metadata and artwork separate version columns, followed by owner, status and approval date. One combined “done” field is too coarse.
- Use a stable content ID
- Distinguish regional language variants
- Identify delivery use and current owner
Connect dependent assets
A picture recut can affect timed text and dubbed audio; a product-name change can affect captions, metadata and artwork. Record which columns each change requires you to review. Some platforms accept translated titles and descriptions separately, including YouTube, so keep metadata outside the subtitle file too.
- Link assets to their picture master
- Reset affected approvals after a change
- Keep replacement history
Worked six-row matrix
A demo video with Chinese, English and Japanese outputs in landscape and portrait needs six rows. A Japanese landscape row might read “DEMO01 / ja-JP / 16:9 / picture V04 / subtitles V03 / audio V02 / metadata V02 / final preview pending.” A portrait-only crop need not change landscape versions; revised dialogue needs a wider review.
- Link each row to files
- Distinguish not required from not produced
- Release approved assets only
Record the actual release
Before release, ask another reviewer to open files from the matrix and check language, aspect ratio, beginning and ending. After publication, add the live URL, time and playback-check result. Log withdrawals and replacements so old assets do not reenter the next release.
- Match live language to the matrix
- Match artwork and title to the video
- Record the URL and reviewer
Before you hand over the work
- Give each asset its own approval state.
- Use dependencies to decide what needs another review.
- Connect the matrix to files and live releases.
Demonstration projects and examples illustrate working methods. Follow the receiving party’s specifications and the scope agreed for your project.