1. Non-English > English Templates

Context

The English template is the first step of subtitle translation. The file that is created from this step is considered the Source of Truth (SOT) for all other languages a trailer will be translated into.

 

Considering this, it’s of the utmost importance that an English template is complete, accurate, and includes all plot-pertinent dialogue and on-screen text.

General Specifications

English template specs are here. If you are assigned a trailer where you’ll be creating an English template from a language that is not English, please ensure that ALL plot-pertinent dialogue and on-screen text is included (whether it be non-English dialogue or text or  English dialogue or text).

Trailer-Specific Notes

The major differences between English templates for long-form content and trailers are the following:

  1. Timing

    1. Due to the quick pace of trailers, sometimes timing to shot changes cannot be met. Please try to maintain this spec, but if needed, you can go over shot changes (especially if the duration of a subtitle is less than 20 frames).

  2. Content

    1. DO NOT include a subtitle for a translator credit

    2. DO NOT introduce English translations that include profanity, so soften as necessary. See below for more information:

      1. A harsh profanity word should NOT be included in the audio of the service/product trailer. If it is, please flag to us via Zendesk.

      2. Words that would not be considered “living-room safe,” like “shit,” “fuck,” racial or regional identity-based slurs, and overtly sexualized language like “cum,” “dick,” etc. should NOT be included in the English template, as this could result in the same level of profane language in the subsequent language files that use the template as their source of truth

      3. If the direct translation of a word in the source language cannot be softened in English, please let your Netflix rep know so they can reach out to the video editors to have the source audio censored

  3. Forced Narratives (FNs)

    1. Main title: For Product/Service trailers, MAIN TITLES are included, so please make sure to include and tag as a forced narrative (keyboard shortcut: Ctrl-T).

    2. Note that aside from on-screen text, FNs could also include foreign dialogue (dialogue that is different from the source language in the trailer) and hard-to-hear or hard-to-understand dialogue

      1. Example: A linguist is creating an English template for a trailer where the source language is Danish. In the trailer, English is also spoken. When this happens, transcribe the English and tag these instances as FNs.

    3. How-To:

      1. Template creator tags any event that should be in the Forced Narrative file by using Ctrl+T/Alt+T keyboard shortcut while working on the subtitle template.

      2. Pay close attention to FNs that are overlapped by dialogue-- if they are plot-pertinent, they should be included and tagged so that you can deliver the file successfully, without overlapping subtitles blocker errors.

 

2. Non-English SDH/Closed Captions Files (CC)

Context

The SDH/CC file is created specifically for the deaf and hard-of-hearing audience. This process entails transcribing the audio in the video, adding sound effects that are not visually indicated on the screen (a door knock not shown on screen, for example), and including speaker identifiers if the person is not on the screen when speaking or if would be difficult to note who is speaking in a scene with a lot of overlapping dialogue. 

General Specifications

Once a Template is completed for a project, the SDH/CC file moves to a “Ready to Author” state in Originator. SDH specs are located in each language’s Timed Text Style Guide, here.

  • Note that using general identifiers like [man] [man #2], etc. are fine to use in these SDH files, especially if you don’t know the names of who is speaking on the screen

    • It’s important to note that the trailer is usually a viewer’s first foray into content, so unless you are absolutely sure of a character’s name, it is fine to use general identifiers to ensure that you are not misrepresenting the content or providing spoilers

  • The profanity guidelines noted in the English Template section should be adhered to in SDH files

    • Sound effects like “[bleep]” (if there is a bleep in the audio) is allowed