Why many languages are harder than one
Adding a second language roughly doubles some work. Adding ten multiplies the number of files, people, questions and chances for a mistake. The writing itself may be fine; what goes wrong is usually organization. Files get mixed up, an old version ships, or a reviewer checks the wrong draft.
A little structure at the start prevents most of this.
Start from one master
Before any translation begins, settle a single source version: the final picture and one approved source-language subtitle file, often called the master. Every translation should come from that master, and everyone should know exactly which version it is.
If the source text changes after translators start, every language is affected. Fixing the master first, then passing the change to each language together, avoids languages drifting apart. Often a “source freeze” date is agreed, after which changes are logged rather than quietly made.
It also helps to clean up the master for translation. Mark where lines are split mid-sentence, flag unclear references, and note jokes, songs and cultural points that may need explaining. Good source preparation here benefits every language at once.
Name files in a predictable way
A consistent naming pattern makes files easy to sort and hard to confuse. A typical pattern includes:
- a short project or video identifier
- the language, preferably with a standard language code
- the version number or status, such as draft or approved
For example, a hypothetical file might be called intro_fr_v2_approved.srt. The exact pattern matters less than using it every time. Keep each language in its own folder, with a separate folder for the master and for delivered files.
Track everything in one sheet
A shared tracking sheet is usually enough. One row per language and video, with columns such as:
- translator and reviewer
- date sent and date due
- current status (not started, in translation, in review, approved, delivered)
- version of the master it was based on
- open questions
This shows at a glance what is late, what is waiting for approval and which languages are built on an outdated master.
Share one glossary and style sheet
Names, product terms and recurring phrases should be decided once and shared. A term glossary with agreed translations in each language keeps wording consistent between translators. Where a translation memory is available, it can reuse earlier approved wording across videos in the same language.
Also provide one set of style guidelines, with notes where a language needs different rules, such as the limits on characters per line. Some languages need more space for the same meaning, and text expansion can force careful trimming. Languages written right to left or without spaces between words may call for specific line-break rules and checks.
Assign reviewers per language
Each language should have a reviewer who actually reads it, preferably a different person from the translator. Without a fluent reviewer, nobody can judge whether a language is right, so check this before you promise a language. The reviewer’s tasks might include:
- checking meaning against the source
- checking names and terms against the glossary
- checking line breaks, reading speed and timing
- confirming the final file displays correctly
For medical, legal or safety content, make sure a qualified human reviewer signs off in each language.
Decide ahead of time who has the final say if the translator and reviewer disagree, and give reviewers a single route for questions, such as one contact person who keeps answers consistent and shares them with all languages.
Handle questions once
A question from one translator often applies to every language. If a translator asks what an ambiguous phrase means, record the answer and pass it on to all. A shared question log prevents the same ambiguity being resolved differently in each language.
Deal with changes carefully
Changes are the hardest part. When the video is edited, the master changes and each language has to follow. Make a list of changed cues once, then give that same list to every translator, rather than letting each one find changes alone. Re-edits are covered in more detail in the article on reusing subtitles for a re-edited video.
Whenever a language is changed, increase its version number and keep the previous file. Never overwrite an approved version without a record, a habit supported by sensible version control.
Test before you deliver
Check every language in the real player. Look for missing characters, boxes in place of letters, text running off screen and wrong language labels. Character encoding problems are especially common with non-Latin scripts. Make sure the right file is attached to each language track, since a perfectly good French file labeled Spanish is still a failure.
Deliver in batches if needed
If some languages are ready earlier, it is often fine to release them first, provided the schedule says so and later languages are tracked just as carefully. Record exactly what was delivered, when, and in which version, so later updates start from a known point.