1. Technical Information

1. Font: Arial, 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 - 17 characters per second (cps)
     • Chidren's programs - 13 characters per second (cps)
   • SDH (Subtitles for the Deaf and Hard of Hearing)
     • Adult programs - 20 characters per second (cps)
     • Chidren's programs - 17 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: 42 characters per line
   HBO: 40 characters per line
   DISNEY DVD: 40 characters per line
7. Max. 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 17 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 21 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 21 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

1. Use a hyphen without a space on the second speaker only to indicate two speakers in one subtitle, with a maximum of one speaker per line.

מה קרה שם בדיוק?
-אין לי מושג

7. Names

1. Transliterate proper names (e.g. John, Mary), do not translate unless requested. 
2. Transliterate nicknames. Do not translate unless they have a specific meaning or are well-known and have official Hebrew equivalents. (e.g. EXAMPLE)
3. Transliteration should comply with the transliteration rules of Academy of the Hebrew Language. If pronunciation of the name is difficult, find out the origin of the name and research its pronunciation
4. Use local language translations for historical/mythical characters (e.g. EXAMPLE).
5. Translate brand names to a generic term if the brand is unknown in Israel and is relevant to context. (e.g.  "EXAMPLE" for "Clorox")

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.

9. Punctuation

1. Both Hebrew and Latin punctuation marks are accepted.

10. Italics

1. Do not use italics.

11. Continuity

For ellipses, use the single smart character (U+2026) instead of three dots/periods.

1. Do not use ellipses (3 dots) or dashes when an ongoing sentence is split between subtitle events.
2. Use an ellipsis to indicate a significant pause (2 seconds or more) or dialogue trailing off. For a pause (2 seconds or more), there should be a space after the ellipses.

היא היססה... בנוגע לקבלת העבודה.

3. In the case of a pause (2 seconds or more), if the sentence continues in the next event, do not use an ellipsis at the beginning of the next event.
4. Use an ellipsis without a space for an event starting mid-sentence.
5. Use an ellipsis for abrupt interruptions.
6. In the case of a sentence that is interrupted by a second speaker and then continues afterwards, you should have an ellipsis before and after the interruption. 

12. Titles

1. Follow instructions from Pixelogic regarding Main Titles. If instructions were not provided, double check.
   ALULA Match Localization Library entry if provided.
   NETFLIX Do not include a Main Titles. 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 a Episode Titles. 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.

13. Forced Narratives / On-screen Text

1. Only include plot-pertinent Forced Narratives.
2. Delete redundant Forced Narratives (e.g. identical to onscreen text/covered in dialogue/appears repeatedly in the video).
3. Ensure that Forced Narratives do not cover onscreen text. In the event, there is onscreen text at the top and bottom, place the Forced Narrative in the location easiest to read. If both locations are identically difficult, then place the event at the bottom.
4. Never combine a Forced Narrative with dialogue in the same event.
5. Forced Narratives should be enclosed in hyphens ( - ), unless they are for foreign dialogue. If the Forced Narrative is split between two or more subtitles, use hyphens at the beginning and end of each subtitle.
6. If a Forced Narrative interrupts dialogue, use an ellipsis at the end of the preceding event but not at the beginning of the following event.

 

Event 1:
 …עבדתי על הסרט  

Event 2(FN):
-  שם הבמאי - 

Event 3:
  .במשך שישה חודשים

6. Speaker’s title for documentaries: Only translate a speaker’s name and title once, the first time the speaker appears in the documentary. 

14. Foreign Dialogue

1. Foreign dialogue should only be subtitled if the viewer was meant to understand it per creative intent in the original version. Please check with Pixelogic to see if you are using a Subtitled or Subtitle-less version of the video.

15. Numbers, Time & Currency

1. From 1 to 10, spell the numbers.
2. Above 10, numbers can be written numerically: "11", "12", "13", etc.
3. If a number starts a sentence, it should be spelled out.
4. Currency - Do not use symbols, write out the type (e.g. ".זה עלה 30 דולר ")
5. Never convert currency.
6. Exceptions to the above can be made for space limitations or correct usage (e.g. EXAMPLE).
7. Convert to metric system: kilometers (km), Celsius (°C), Kilograms (kg) unless the original unit of measurement is plot-pertinent.

16. Quotation Marks

1. Use double quotation marks (" ") without spaces for regular quotations.
   

   Event 1:
   ".הוא אמר: "אל תלכי לשם 

2. Use single quotation marks (' ') without spaces for quotes within quotes.
   

   Event 1:
   אתמול בחמש אחר הצהריים"  
   ."'לחשתי לה, 'בואי

3. Quotes should be used at the start and end of a line of applicable dialogue and not at the start of every subtitle.
   

   Event 1:
   ,היא אמרה לי  
   ."עזוב, אתה לא רציני"

   Event 1:

   .לא ידענו מה לעשות"
   ".הלכנו הלוך חזור ולא היה מוצא

4. Quotes should be used at the start and end of a quote, not at the start of every subtitle.
5. Put song titles in quotes.

17. Abbreviations 

1. Translate abbreviations with hyphens:
• אף-בי-איי
• אן-אף-אל
• >די-אן-איי

18. Acronyms

1. Acronyms are usually transliterated: נאס”א, נאט”ו  

19. Repetitions

1. Do not translate words or phrases repeated more than once.
2. If the word or phrase is said twice in a row, time to audio but do not repeat the translation.
3. This rule can be ignored if the context uses repetition for emphasis or comedic effect.

20. 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. Use an ellipsis if the song continues in the background but is interrupted by dialogue.
4. 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.
5. Use opening double quotes at the start of the song and the end of the last lyric, not for each event.

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 - ": תרגום כתוביות-" (include the hyphen)
   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 

Speaker IDs/Sound Effects

1. Use [ ] brackets for speaker IDs or sound effects.
2. Use lowercase, except for proper nouns.
3. Only use speaker IDs or sound effects when they cannot be visually identified.
4. 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.
5. 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])
6. 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.
7. Use a generic ID to indicate and describe ambient music (e.g. [rock music playing on radio]).
8. Only include plot-pertinent sound effects.
9. Never italicize speaker IDs or sounds effects, even if the dialogue is italicized.

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 20)

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. Reference

Please reference the following for any language-related issues not covered in this document:

1. Academy of the Hebrew Language: https://hebrew-academy.org.il

27. Client Style Guides

•  - Latest version
•  - Latest version - December 5, 2017

Back to top 

Change log:
Apple - August 16, 2017 - V1