Welcome to the Netflix Partner Help Center. Have a question or need help with an issue? Send us a ticket and we'll help you to a resolution.

 

TABLE OF CONTENTS

     Overview

     Main Features

     The QC Process

     How to flag a mistake

     FAQ

     Reference Materials

     File Naming

 

OVERVIEW

A Dialogue List (DL), also known as “As Broadcast Script”, and a Pivot Language Dialogue List (PLDL) are accurate transcriptions (DL and PLDL) and unadapted translations (PLDL only) of the original content in a video. They are typically created using a preliminary or locked cut and updated to the final cut once that becomes available. Additional materials like shooting scripts and Show Guides are sometimes provided as reference documents during origination.


DLs and PLDLs are leveraged by everyone involved in a title’s localization, including the teams responsible for the origination and QC of the dubbed assets, subtitles, and trailers.


MAIN FEATURES

The Dialogue List and Pivot Language Dialogue List should consist of three parts on separate tabs of an Excel sheet:


Tab 1 → Dialogue List/Pivot Language Dialogue List

In this tab, each column will include specific details from the original audio. There are 8 columns (DL) or 9 columns (PLDL) that comprise the actual DL/PLDL:

  • Timecode In
  • Timecode Out
  • Source: Speaker names and the source of on-screen text.
  • Dialogue: Transcription of all dialogue as well as descriptions of mouth sounds in brackets (e.g.: [sighs], [laughs], [screaming], etc) and other descriptions in parentheses e.g.: (long pause), (fades out to shot change), etc.
  • Translation [PLDL only]: Unadapted translation into English of the dialogue transcribed in the previous (Dialogue) column.
  • Burned-in Subtitles: Transcription of burned-in subtitles for foreign or hard-to-hear dialogue present in the locked cut or any documents provided by production.
  • On-screen Text: All plot pertinent on-screen text.
  • Annotations: Relevant context for localization.
  • Tags: Column may or may not be present. It includes the tag added to the event in the Scripting tool.

In addition, there are three more columns for QC:

  • Error Code: Represents the error codes available for the QC. The error code must be selected from the drop down list. Do not add your own error codes.
  • Severity: Indicate the severity level of the problem. There are two options: FYI and Issue. Don’t add your own either.
  • QC Notes: Use this column to provide an explanation of what’s wrong with the event. These notes are intended to be read by the fulfilling partner. Don’t assume the flag might be enough to understand the problem. Provide an explanation.


Tab 2 → Change Log
This tab is similar to the previous tab. It must list all the changes made to the DL or PLDL when it is updated from the locked cut to the final cut. Changes should be presented in table format, with new columns listing the content of the new version inserted to the right of the corresponding column from the original Dialogue List.


Error Code, Severity Level, QC Note columns are present in the Change List tab. Errors which are already listed in the Dialogue List tab do not need to be flagged again in the Change List tab. Please only use the QC columns in the Change List to flag errors in the Change List itself, i.e., changes which have been overlooked and not logged or listed changes that are not actually present in the new media.

 

Tab 3 → Project Info:
Project Information should be clearly labeled and include all the details in the template.
Do not add columns, change the order of the columns or their formatting in any of the tabs. Also, do not add empty rows. Any problem detected should be flagged in one of the rows that already exists in the Dialogue List.
If the tabs are not filled out properly or have been tampered with, such as columns removed, order changed, special formatting added or any change that deviates from the template, please flag it in your completion email.

 

THE QC PROCESS

HOW TO FLAG A MISTAKE

  1. Select the Error Code from the drop-down menu in the Error Code column that best reflects the problem.
    • Translation - Consistency:
      • The translation of names, key phrases and locations, or the treatment of relationship references (older vs. younger sibling), formality or theme song is inconsistent within the episode or with previous episodes and/or seasons.
    • Translation - Objective:
      • The translation is objectively incorrect or unidiomatic (i.e. unnatural or ungrammatical).
    • Translation - Subjective:
      • Although the translation is not wrong, an improvement could be made to make the dialogue clearer or more natural. Always use FYI as the severity level.
    • Missing Content:
      • The translation is missing a line or section of dialogue or on-screen text.
      • One or both timecodes are missing.
      • There’s more audio than it has been transcribed and therefore translated.
      • Source column is not filled out.
      • Annotation is missing for a cultural reference, challenging idiomatic expression, or to provide clarity.
    • Mishearing:
      • The transcription doesn’t render the audio accurately.
      • There is more audio than it is transcribed.
      • There is an extraneous transcription in the dialogue cells that is not present in the audio.
  2. Select a Severity Level from the drop-down menu in the Severity Column:

    • FYI - Something we would like to draw attention to that is not necessarily an issue.

    • Issue - Objective linguistic issues that would negatively impact customer experience/or deviate from the creative intent of the original version.

  3. Explain the issue in the QC Notes column:

    • Specify the dialogue segment, on-screen text or any other column that needs correction.

    • Explain why the suggested change is necessary. Comments should be written in English.

    • Include a back translation, if possible.

    • Suggest an alternative translation when appropriate.

    • Be courteous. The notes are going to be read by the fulfillment partner.


FAQ

What if more than one error code applies?
The error code that most closely matches the root of the problem should be used.
For example, if a translation problem was created by a mishearing, select mishearing as the error code even though there is probably also a mistranslation.


What if I find a typo/misspelling/punctuation/grammar error?

The DL or PLDL is not a final deliverable. Its contents are not going to be seen by members. It is intended as a reference document for the creation of dubbing scripts. Thus, if you find a typo, missing punctuation, or grammar issue, just fix it. As long as the issue doesn’t lead to a misinterpretation of the sentence, there is no need to flag it as an error.

However, flag any typo, grammar or punctuation error which leads to another error. For example, a misplaced comma can change the meaning of a sentence, resulting in a mistranslation. In such a case, fix the comma and flag the mistranslation.

As a rule, if an issue has the potential to negatively impact the other translations, it should be flagged.


What if I find an error that doesn’t fit with available error codes?

Select one from the list that best matches the problem and explain the error in the QC Notes column.


What if I select the wrong severity?

Use your best judgment when selecting the appropriate severity level. A good way to do so is to imagine yourself as the recipient of the DL or PLDL. How problematic would this mistake be if you had to translate the line of dialogue that contains it into another language?

The only exception is the Translation - Subjective error code. It should always be an FYI.


What if there are too many missing annotations throughout the file?

If annotations are too sparse or altogether missing throughout the entire file, do not flag each and every instance. Instead, please indicate "Insufficient Annotations" as a comment in the first line of the Annotations column.


What if the overall quality of the file is poor?

If you encounter an unusually large number of errors throughout the entire file, please notify the Dubbing Title Manager via email.


REFERENCE MATERIALS

If reference materials are already available, such as Show Guide and KNP, they will be provided to be used as references to aid in the QC process.
Keep in mind that at the time the DL or PLDL was created, the fulfillment partner may not have had access to any reference material beyond shooting scripts. Therefore, they should not be penalized for not complying with any instructions in the Show Guide. Refer to the Project Info tab to know which reference material they were supplied.

Before submitting their QC task, linguists must check that all relevant source terms have been added to the KNP tool by the partner. If linguists wish to add source terms to the KNP, they must submit a Zendesk ticket and wait for their suggestions to be reviewed. Once suggestions are approved, linguists may update the KNP accordingly. As with all QC tasks, linguists must review all relevant Style Guides and Show Guides to ensure the Dialogue List is fully compliant with the guidelines provided by Netflix.


FILE NAMING

Upon completion of DL QC, you must add “QCed” to the end of the file name before delivery to Netflix.
To learn more about the Dialogue List scope of work and other critical information, please review the following articles:


Dialogue List Scope of Work
Pivot Language Dialogue List Scope of Work
Template: Dialogue List/As-Broadcast Script

Was this article helpful?
0 out of 0 found this helpful
Powered by Zendesk