1. Technical Information

1. Font: Gulim, White
2. Minimum duration: 1 second
3. Maximum duration: 7 seconds
   • 29.97 frames/second (fps) - 210 frames
   • 23.98 frames/second (fps) - 168 frames
   • 25 frames/second (fps) - 175 frames
4. Reading speed (include spaces and punctuation):
   
   • Subtitles
     • Adult programs - 12 characters per second (cps)
     • Chidren's programs - 9 characters per second (cps)
   • SDH (Subtitles for the Deaf and Hard of Hearing)
     • Adult programs - 14 characters per second (cps)
     • Chidren's programs - 11 characters per second (cps)
5. Frame gap: 2 frames minimum 
        Note: Frame gap should be 2 frames or at least 5 frames 
        All frame gaps of 3-4 frames should be reduced to 2 frames
6. Character limit: 18 characters per line
7. Maximum number of lines: 2 lines

2. Line Treatment

1. If an event can fit on one line, please keep it to one line. Do not split for grammatical reasons.
2. For two line events, ensure that you maintain a logical and grammatically correct line break (e.g. after punctuation).

3. Positioning

1. Always position either top or bottom center. Never have subtitles in any other position.
2. An event should be moved to the top if there is text in the lower third of the screen (e.g. credits)
3. In cases where the entire screen is covered with text, choose the option that causes the least disruption to the viewer.

4. Timing

1. If there is a supplied English Template, the timing for that should be followed. Events may be merged or split if the in-cues and out-cues are maintained. This rule supersedes all the below rules.
2. Subtitles should be timed to audio (within 3 frames).
   • If extra time is needed for reading speeds, the out-time can be extended by 12 frames past end of audio.
3. If dialogue starts within 3 frames of a shot change, pull the in-time to the shot change.
4. There should always be a minimum of 2 frames between the out-time of an event and the shot change after it.
5. If dialogue ends within 3 frames or less of a shot change, pull the out-time to 2 frames before the shot change.
6. While the reading speed is 12 cps, this is not always possible, the following priority should be followed:
   1. Time to audio and extend by 12 frames past end of audio (if it doesn’t cause the event to cross a shot change and look awkward).
   2. Let the reading speed go up to 15 cps.
   3. Merge or split events to help with reading speeds.
   4. Truncate without losing the meaning of the audio.
   5. If, after you have tried all of the above, the reading speed is still exceeding 15 cps then the file can be submitted as is, but all the above must have been tried.

5. Truncation

1. Subtitles should convey the context of the audio as accurately as possible, but do not need to be a word for word translation.
2. Omit superfluous and unnecessary information such as hesitation markers, repetitions, and redundancies (e.g. "You know", "you see" etc).

6. Dual Speakers

Use a hyphen with a space to indicate two speakers in one subtitle, with a maximum of one speaker per line.

- 다들 어떻게 생각하는지 물어보자
- 또? 아까 물어본 것 같은데

7. Names

• Do not translate proper names (e.g. John, Mary) unless requested, otherwise transliterate.
• Only translate nicknames if they have a specific meaning or are well-known and have official Korean equivalents. (e.g. Stinky Pete)
• Use local language translations for historical/mythical characters (e.g. Genghis Khan, Santa Claus).
• Translate brand names to a generic term if the brand is unknown in Korean and is relevant to context. (e.g. "bleach" for "Clorox")
• Avoid placing a dot between first and last name unless it is part of the original format. (e.g. Homer J. Simpson=호머 심슨)

8. Formality

Terms of address: Use formal or informal terms of address based on the relationship between characters and keep them consistent throughout (unless there is a change in the relationship). When in doubt, use formal terms.

10. Italics

1. Do not use italics.

11. Titles

1. Follow instructions from Pixelogic regarding Main Titles. If instructions were not provided, double check.
   ALULA
   - If there is an English component ensure that it is ALL CAPS regardless of the casing in the LL.
   - Do not use double-quotation marks.
   Examples:

   One line MT
   
   
   
   NBCUNIVERSAL Must have client-provided Main Title. Check with Pixelogic for approved Main Title.
   NETFLIX Do not include Main Titles unless it is for Japanese content. If mentioned in dialogue, check with Pixelogic.

2. Episode Titles: Do not subtitle if they do not appear onscreen, if they do, check with Pixelogic.
   NETFLIX Do not include Episode Titles unless it is for Japanese content. If mentioned in dialogue, check with Pixelogic.
3. Titles of movies, TV shows or published works: Use official / accepted translations. If none are available, leave in the original language.

19. Songs

1. If the song is original to the show/movie, check with Pixelogic if translation is required. For all other instances do not translate.
   LIONSGATE This rule is for characters singing only. Do not translate background songs.
2. Songs in which the lyrics have been altered or parodied for comedic effect can generally be titled.
3. Start each line with an uppercase letter.
4. Use an ellipsis if the song continues in the background but is interrupted by dialogue.
5. Only question marks, exclamation marks and ellipses can be used at the end of a line. Commas can be used within the lyric line, if required.

21. Translator Credit

1. Include if present in provided English template, otherwise do NOT include a translator credit.
   Exceptions:
   NETFLIX Include a translator credit - "자막: "
   PARAMOUNT (Theatrical) Include a translator credit - "자막: "
   SONY Include a translator credit - "자막 번역: "
   ALULA Include a translator credit.
   NBCUNIVERSAL Include a translator credit.
2. If a client requests a translator credit and does not specify a format use one of the above prioritizing top to bottom.
3. Company names are not allowed as Translator Credit. Only the individual translator.
4. In the cases where the file is a reformat of an older subtitle file, there may be no translator credit required as it may not be present on the original file.

22. Language Tag

1. Do not translate the [LANGUAGE TAG - Do not Translate] event if present. This is an identifier in English for BD/DVD authors.

23. SDH Instructions

Speaker IDs/Sound Effects

1. Use parentheses （） for speaker IDs.
2. Use [ ] brackets for sound effects.
3. Use lowercase, except for proper nouns.
4. Only use speaker IDs or sound effects when they cannot be visually identified.
5. If a person who is on-screen continues talking off-screen, do not add another identifier for their off-screen dialogue. We assume it's the same person talking until another person is visible or until there is an identifier for a different speaker.
6. Do not identify a speaker until their character name has been introduced. Until they are introduced, use generic IDs (e.g. [man], [man 2], [cop], [doctor])
7. For documentaries, commentaries, bonus material (VAM) etc. do not identify interviewees by their first name. Only use their last name. You can use first names for the characters from the program, assuming they have been identified that way in the full program.
8. Use a generic ID to indicate and describe ambient music (e.g. [rock music playing on radio]).
9. Only include plot-pertinent sound effects.

Exclamations

1. Include single utterances and exclamations (e.g. Oh, Um..., Wow!)

Foreign Dialogue

1. If translated – Use [in language] (e.g. [EXAMPLE] )
2. If not meant to be understood – Use [speaking language] (e.g. [EXAMPLE] )
3. Always research the language. Do not use [speaking foreign language] or [in foreign language].

Songs (additional to Section 19)

1. Song lyrics should be enclosed with a music note (♪)
2. Songs heard within the scene should be identified if possible.

   [EXAMPLE]

Censored Words

1. If a word has been censored in the audio use four asterisks to indicate the censored word.

EXAMPLE ****!

26. Client Style Guides

•  - Latest version
•  - Latest version - December 7, 2017 

Back to top 

Change log:
Apple - August 3, 2017 - V1