Creation

• Import/Copy the subtitles from the DFXP/RTF source into Composition Editor. Territory Manager’s who have an EZT license can import the DFXP.
• Fill in the Localization Library.
• Type [MISSING] for events that are not included in the source file, but are present in the English Template.
• Submit file

Linguistic QC

Stylistic/formatting changes:

The following related to style and formatting can be changed without flagging to the client:

• Italics
• Capitalization
• Ellipses/Hyphens
• Dual speaker events
• Objective spelling errors
• Punctuation/Quotations

MISSING Events

For [MISSING] events, please ensure the the text from the English template is translated. If the dialogue is redundant in your language, please omit the event.

Do not submit the file with any events still marked [MISSING].

Content changes (New Release Titles):

• The QC Linguist should QC the entire file and flag egregious errors and/or events with mis-translation that change the meaning or context of the dialogue.
• The Territory Manager will need to provide a full QC report of every event that we want to correct/update in terms of translation.
  Examples:
  • Subjective: Source file translates “Correct” as “Exactly." Do not flag/change.
  • Objective: Source file translates “Right” as “Left.”.  Flag for client approval before the change is implemented.
• Please ensure to provide English back translations in the notes. It should be in this format: 

• The QC Linguist should hold on submitting the file until they receive client approval as we will need clearance from the studio for any changes to the file.
• If there are no notes related to the content – the linguist can finish their QC and submit the file.

Content changes (Catalog Titles):

• The QC Linguist should QC the entire file and flag egregious errors and/or events with mis-translation that change the meaning or context of the dialogue. The Territory Manager will need to provide a full QC report of every event that we want to correct/update in terms of translation (same as the above).
• In the event that there are too many issues and the entire file is very poor and requires a full re-translation, the Territory Manager should email the Paramount localization Project Managers a couple of examples to send to Paramount (use the above format).
• If Paramount confirms the file can be used as is, QC Linguists can carry on without flagging these issues.
• If Paramount approves a re-translation of the file, we will change the job type and budget to be an Origination using the client-supplied file as reference, with an updated due date.