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
   DVD (all): 32 (if all uppercase) characters per line
   DISNEY (DVD only): 40 characters per line
   HBO: 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.
   DISNEY - Never raise events for burned-in subtitles as the burned-in subtitles will be removed on final video delivery. Raise as normal for everything else.
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).
   1. 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. For two events on either side of shot change, have the first event in 2 frames from the shot change and the second event start on the shot change.
7. Do not be afraid to cross shot changes if required. Do not split a subtitle unnecessarily to maintain a shot change.
8. 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.

1. 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. This article shows examples of basic syntactical changes - Fotios Karamitroglou: A Proposed Set of Subtitling Standards in Europe.
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 with a space to indicate two speakers in one subtitle, with a maximum of one speaker per line.

- Boa sorte.
- Obrigado.

2. Use a hyphen with a space to indicate the second speaker only, if the dialogue of the first speaker continues from the previous event.

Event 1: 
Não sabia se chegarias a tempo,

Event 2: 
mas preparei-te o jantar.
- Obrigado.

7. Names

1. Do not translate proper names (e.g. John, Mary) unless requested.
2. Only translate nicknames if they have a specific meaning or are well-known and have official Portuguese equivalents. (e.g. Kiddo / Rapaz ou Rapariga )
3. Use local language translations for historical/mythical characters (e.g. Santa Claus / Pai Natal).
4. Translate brand names to a generic term if the brand is unknown in Portugal and is relevant to context. (e.g.  "Desinfetante" for "Clorox")
5. Do not italicize proper names or company names.

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

The most common punctuation rules for Portuguese should be followed.  

Please refer to the following articles for some information on the correct use of punctuation: 

https://www.flip.pt/flip-on-line/gramatica/sinais-de-pontuacao 

https://ciberduvidas.iscte-iul.pt/consultorio/perguntas/sobre-a-pontuacao/11504 

10. Italics

1. If there is a supplied English Template, the italics usage for that should be followed. This rule supersedes all the below rules. If you spot something you think is incorrect, please follow the template regardless but notify Pixelogic immediately so that we may confirm.
2. Italicize:
   1. Dialogue that is heard through electronic media, such as a phone, television, public announcement system or computer
   2. Unfamiliar foreign words and phrases (not commonly used)
   3. Song lyrics when sung, not quoted (provided rights have been granted)
   4. Voice-overs such as out-of-scene narrators or visible characters expressing unspoken thoughts
   5. Titles of books / periodicals / works of art / albums / movies / tv or radio shows / plays / ship names
   6. Genera and species' scientific names
3. Do not italicize:
   1. During B-roll footage in a documentary. Avoid going back and forth between italics when the speaker is on and off screen. If the speaker is on-camera for part of the scene do not italicize
   2. If the dialogue starts/ends out-of-scene, but the character is visible during the event (e.g. on a phone call between 2 people)
   3. For emphasis

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.

Event 1:
Três anos não foi tempo suficiente

Event 2:  
para aprender tudo.

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. 

Event 1:
Não sei…

Event 1: 
Não sei… tenho de pensar sobre isso.

3. In the case of a pause (2 seconds or more), if the sentence continues in the next event, use an ellipsis followed by a space at the beginning of the next event.

Event 1: 
Sinto-me doente…

Event 2: 
… mas prefiro não pensar no assunto.

4. Use an ellipsis with a space for an event starting mid-sentence.

… assinaram um acordo.

5. Use an ellipsis for abrupt interruptions.

Event 1: 
 - Eu ia te dizer que… 
- Não quero saber!

12. Titles 

1. Main Titles: Check for any special instructions with Pixelogic.
   ALULA Match Localization Library entry if provided, otherwise uppercase.
   DISNEY Must be included for Features even if redundant.
   NBCUNIVERSAL Must have client-provided Main Title. Check with Pixelogic for approved Main Title.
   NETFLIX Do not include 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.
   ALULA Match Localization Library entry if provided, otherwise Sentence case.
   NETFLIX Do not include Episode Titles. If mentioned in dialogue, check with Pixelogic.
3. Use uppercase letters for titles.
   DISNEY+ Match the case of the onscreen text.
4. Titles of movies, TV shows or published works: Use official / accepted translations. If none are available, leave in original language.

13. Forced Narratives / Narrative Subtitles

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. Forced Narratives should be ALL CAPS.

Exceptions:
Excerpts from books / magazines / newspapers
Handwritten notes
Social Media Messages
Text messages
All the above should match the text as it appears on screen.

Long passages of on screen text (e.g. prologues / epilogues) can use mixed case to improve readability.

PARAMOUNT: Forced Narratives should always match the case of the onscreen text.
DISNEY+ Forced Narratives should always match the case of the onscreen text.

4. 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.
5. Never combine a Forced Narrative with dialogue in the same event.
6. If a Forced Narrative interrupts dialogue, use an ellipsis at the end of the preceding event and an ellipsis with a space at the beginning of the following event.

Event 1:
Eu trabalhei neste filme...

Event 2(FN):
REALIZADOR

Event 3:
... durante seis meses.

7. Speaker’s title for documentaries: Only translate the title. Do not include speaker’s name, company name or character name.
8. Only translate a speaker’s 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.
2. Always verify spelling and grammar when using foreign words.
3. Foreign words should be italicized, unless they have become part of normal usage (e.g. In English, the following do not need italicization: bon voyage, bona fide, alfresco, kaput).
4. Do not italicize proper names or company names.

15. Numbers, Time & Currency

1. From 1 to 10, numbers should be written out: "um", "dois", três, etc.
2. Above 10, numbers should be written numerically: 11, 12, 13, etc.
3. Numbers from 1000 and above should be spelled out.(Correct: mil. Incorrect: 1000. Correct: 10 mil. Incorrect: 10 000, etc.) 
4. When a number begins a sentence, it should always be spelled out.
5. Note that the above rules may be broken due to space limitations or reading speed concerns, as well as for consistency when listing multiple quantities, for example.
6. Measurements should be converted to the International System of Units, unless the original unit of measurement is plot-pertinent. 
7. For numbers up to 4 digits, do not add a space to separate the thousands. (Correct: 1234. Incorrect: 1 234) 
8. For numbers 5 digits and up, add a space between thousands and hundreds. (Correct: 12 345. Incorrect: 12345) 
9. Use a space instead of a period for thousands. (Correct: 123 456. Incorrect: 123.456) 
10. Do not omit the 0 when noting fractions. (Correct: 0,123. Incorrect: ,123)
11. Use a comma (,) as a decimal separator. 
12. For time notation, use the formats below: 
    • Ele partirá às 4 horas.
    • A reunião irá das 7 às 9 horas.
    • O foguete foi lançado às 8h5min15s (Incorrect: O foguete foi lançado às 8h5'15'')
    • A reunião será às 5h50.
13. When indicating duration, the numbers should be spelled out:
    • A reunião durou oito horas.
    • A comitiva esperou três horas pelo presidente.
    • Faltam dois minutos.

16. Quotation Marks

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

   Event:
   Ele disse-me: "Volta amanhã."

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

   Event:
   "O Charlie disse: 'Está tudo bem.'"

3. The period at the end of a sentence always comes before the quotation mark.
   

   Event:
   Ele disse-me: "Volta amanhã."

4. Question/exclamation marks are placed outside the quotation marks unless they are part of the quoted material.
   

   Event:
   "Viva Portugal!" Já ouvimos isto antes.
   
   Event:
   Quem se lembra ainda do "nada a declarar"?
   
   Event:
   Todos garantiram: "Iremos até o fim."
   
   

5. Quotes should be used at the start and end of a quote, not at the start of every subtitle.
6. Closing quotes should always follow the period.
7. Put song titles in quotes.

17. Abbreviations

1. Following the International System of Units, do not use periods or plurals: 1 km, 6 km (never 6 kms.) 
2. Add a space between the number and the abbreviation or symbol (6 km, 5 °C, 14 %), except for noting hours - please see the number section for details.
3. Ordinal numbers may be abbreviated only when followed by a noun.(Correct: Ela foi a 1.ª pessoa a chegar. Incorrect: Ela foi a 1.ª a chegar.) 
4. Presidente>: Pres.
5. Professor/Professora: Prof./Prof.ª
6. Doutor/Doutora: Dr./Dra.
7. Século: séc. (Finais do séc. XX) 
8. Senhor/Senhora: Sr./Sra. 
9. Menina/: Mna./Mno. 
10. Universidade: Univ. (must be followed by the name of the university: da Califórnia. Never use alone). 

18. Acronyms

Write acronyms without periods between letters: "FBI", "BBC", "LA".

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. Censored words

1. Dialogue must never be censored. If a word has been censored in the audio, use four asterisks to indicate the censored word.

O filme de ontem foi uma m****.

21. 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. Italicize lyrics.
4. Start each line with an uppercase letter.
5. Use an ellipsis if the song continues in the background but is interrupted by dialogue.
6. 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.
7. Song titles are in quotation marks.
8. Album titles are in italics.
9. DISNEY: All lines should be Left Aligned and Left Justified.
   PARAMOUNT: All lines should be Left Aligned and Left Justified.

22. Translator Credit

1. Include if present in provided English template, otherwise do NOT include a translator credit.
   Exceptions:
   NETFLIX Include a translator credit - "Legendas:"
   PARAMOUNT (Theatrical) Include a translator credit - "Legendas:"
   SONY Include a translator credit - "Tradução das legendas: "
   ALULA Include a translator credit.
   NBCUNIVERSAL Include a translator credit.
   If a client requests a translator credit and does not specify a format use one of the above prioritizing top to bottom.

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

24. 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. [em russo] )
2. If not meant to be understood – Use [speaking language] (e.g. [falando inglês] )
3. Always research the language. Do not use [speaking foreign language] or [in foreign language].

Songs (additional to Section 21)

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. Dialogue must never be censored. If a word has been censored in the audio, use four asterisks to indicate the censored word.

Event 1:
O filme de ontem foi uma m****!

26. Special Instructions

1. Both educated norm and colloquial language styles are allowed, if they match the category of the program. For example, a show set in a high school would use the colloquial style and a historic documentary would use the educated norm.
2. Always follow the spelling rules and regulations outlined in the new Portuguese agreement, Acordo Ortográfico de 1990 (AO90)
3. Deliberate misspellings and mispronunciations should not be reproduced in the translation unless plot pertinent.

27. Reference

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

1. Infopedia Portuguese dictionary (both with and without AO90):http://www.infopedia.pt/
2. Dicionário Priberam da Língua Portuguesa: http://www.priberam.pt/DLPO/
3. Technical Terminology for Europe: http://iate.europa.eu
4. Portal da Língua Portuguesa – Acordo Ortográfico da Língua Portuguesa de 1990 http://www.portaldalinguaportuguesa.org/?action=acordo&version=1990
5. Código de Redação Interinstitucional http://publications.europa.eu/code/pt/pt-000100.htm
6. Ciberdúvidas da Língua Portuguesa http://www.ciberduvidas.com/

28. Client Style Guides

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

Back to top 

Change log:
Apple - August 4, 2017 - V1