Japanese, Korean and Chinese subtitles are some of the hardest to bring into English well. The languages pack a lot of meaning into very few characters, leave subjects and pronouns implied, and encode politeness in ways English does not. A line that fits comfortably on screen in the source can turn into a sentence that is too long to read in time once it is in English. This guide walks through a workflow that starts from the subtitle file you already have and ends with an English file you have checked line by line.
Start from the subtitle file, not the video
If you already have a Japanese, Korean or Chinese subtitle file, translate that file instead of transcribing the video again. The file already carries the cue timing, so a translation that keeps each cue in place will stay in sync with the picture. Keep an untouched copy of the original so you can compare the two later.
Check three things before you translate:
- Format. SRT and WebVTT are the most common, but you may also have ASS/SSA files with styling. Aivently accepts SRT, WebVTT, ASS/SSA, SBV, TTML/DFXP and several other formats, and exports SRT, VTT, ASS, TXT or JSON.
- Encoding. Older Chinese and Japanese files are sometimes saved in legacy encodings. If characters look garbled in a text editor, re-save the file as UTF-8 first.
- Completeness. Make sure the file covers the whole video. Missing cues are easier to spot now than after translation.
Why these languages need a careful review
Machine translation gets the general meaning of most lines right. The problems are concentrated in a few predictable places, so that is where your review time should go.
- Implied subjects. Japanese and Korean often drop "I", "you" or "they". The translation has to choose one, and the right choice usually depends on the previous line or on who is on screen.
- Honorifics and forms of address. Suffixes such as -san, -nim or 先生 carry relationship information. Decide once whether to keep them, translate them ("Mr. Tanaka", "Teacher") or drop them, and apply that choice consistently.
- Names. Romanize each person's name one way and keep it. A name that changes spelling halfway through an episode is one of the most visible errors.
- Length. English usually needs more characters than the source to say the same thing. A translated line that is accurate but too long for its time slot fails viewers just as much as a wrong one.
- Wordplay and cultural references. Puns, idioms and references rarely translate literally. Rewrite them so an English viewer gets the intended effect.
A practical workflow
- Upload the original subtitle file and choose English as the target language.
- Translate the whole file so every cue gets a first-pass English line in the same position and timing as the original.
- Review side by side. Read each English line next to its source line. In Aivently the source and the translation appear together in one editor, so you can check meaning, names and honorifics cue by cue.
- Fix reading speed. Watch for lines that are too long for their duration. Shorten wording rather than shifting timing where you can; condensing is a normal part of subtitle translation.
- Keep a short glossary. Note how you rendered recurring names, titles and terms, and search the file for each one before export.
- Export and test. Export the English file in the format your player or platform expects and watch a few minutes of the video with it before publishing.
Common problems and how to fix them
- A line reads correctly but makes no sense on screen. The subject was probably guessed wrong. Check the surrounding cues and rewrite.
- Two speakers merged into one line. Source subtitles sometimes combine dialogue from two people. Keep the dash convention from the original so viewers can tell who says what.
- Inconsistent tone. A character who speaks casually in the source should not sound formal in English. Read the full scene, not only individual lines.
- On-screen text. Signs and captions burned into the video are not part of the subtitle file. If they matter to the story, add a short translated cue for them.
Check before you publish
Before you publish the English track, play it with the video at normal speed. Fix any line you cannot finish reading before it disappears, and confirm that names, honorifics and key terms match your glossary. A short final pass at playback speed catches problems that are easy to miss in an editor.
Translate your subtitle file with Aivently
If you have a Japanese, Korean or Chinese subtitle file, you can translate it into English, review every line next to the original, and export it in the format you need.