Where is the "no breaks for same speaker" guideline from last March?

Exactly. You know, I make websites sometimes (for friends, for my boss etc…). Once upon a time, before the “responsive” era, when we were all doing tables inside other tables including more nested tables and so on, I was appalled when I saw how the web page which looked so perfect on my PC screen looked when seen from a small (12’’) netbook. Everything looked terrible and the proportions were screwed up. And, later on, tablets and phones.
I mean, nowadays we have to take into account all the different platforms. And it is true that many short lines may take up lots of screen space on a small device.

3 Likes

Maybe I wasn’t clear.
Because of the extra breaks sometimes subtitles look like this on various screens and apps:

Because of the
extra breaks sometimes subtitles look like this
on various
(the line below is off screen)
screens and apps.

I don’t think it’s a matter of taste.

3 Likes

70 characters with a break, its mean 2 line in a line of sub with 35 characters each (lets say so)…
(in most players) up to 40 characters, the thing you talk about would never happen

to be sure, just ask viki about the limit for each lines in a line for every platforms… or check it yourself… you know if ask viki it will take so so much time

the other case…
that’s what i dont like about viki’s autobreak, they just put it on the off screen part (so most of time the second line just have one or two word)… others, mostly, make the autobreak show up at the middle of the sentences(?)

1 Like

I just found it, in the Team Notes of a series I work on.
It’s hidden in a Google document.

Of course, who could see it there?

Viki Subbing Guidelines
To Subbers:
Please believe that we appreciate all the time you contribute to making it possible for people around the world to understand K-drama.
Before you sub on this or any other channel for any recent uploaded video, please check the Team Discussion to see who is subbing and where! Post where you will sub and post when you leave. This way, we can avoid accidental overwriting of your and other subber’s work.
These are general guidelines, based on the most common spelling and grammar errors in subtitling from Korean to English.

  1. Please do your best to translate EVERYTHING in a segment. If there are two sentences in a segment, please translate both! Nearly all of the segmenters are non-native speakers of Korean, so there will be segments with partial sentences or more than one sentence in them. If you can’t translate everything in the segment, SKIP the segment so other subbers can spot the yellow blank quicker in the Subtitle Editor.

  2. Please leave editing of spelling, punctuation, and grammar to the editors! Please don’t change subtitles because of personal preferences – for example - changing “okay” to “all right” or vice versa, changing a single ! to !! and similar changes.

  3. Non Korean to English subtitlers – please leave the English subtitles alone – don’t touch them no matter how bad an error in translation, grammar, spelling or punctuation is – you can always pm one of the editors!!

  4. The beginning of every sentence should be capitalized. A subtitle which begins in the middle of a sentence should not have its first word capitalized unless it is a proper noun.

  5. Every sentence should be ended with a period, a question mark, or an exclamation mark.

  6. Ellipsis: Either … or . . . ( three (3) periods without or with spaces between the dots) are all right for dramatic pauses or when the speaker in interrupted mid sentence by somebody else. Don’t use – or ~ for pauses in the middle of sentences. Please don’t automatically put the … at the beginning or end of every subtitle when the rest of the sentence is in the next segment. At the end of a segment which is mid-sentence where you would ordinarily use a comma, use a comma, not … Remember that the segments have been cut by non-native speakers of Korean so there might be some strange breaks!

  7. “alright” and “all right” are equally acceptable. “OK” and “okay” are equally acceptable. “until”, “till” or " 'til" are equally acceptable.

  8. An apostrophe should be used when it represents the contraction of a verb such as is, am, are, has, have, would, should, etc. “I’m sorry.” “He’s come.” “I should’ve done that.” You’re, not your or the omission of the “o” in not – don’t; doesn’t. This is wrong: “You’re father is a nice person.” This is right: “Your father is a nice person.” This is wrong: “Your late.” This is right: “You’re late.”

  9. There is no apostrophe for a pronoun possessive – That which belongs to her is hers, not her’s. That which belongs to it is its NOT it’s. That which belongs to you is yours, not your’s. Your face is pale. Are you feeling sick? Your stomach is upset? You’re sick?

  10. Let’s delete all ssi, shi, ah, yah and i unless there is some dramatic effect to saying Yeon Jae Ssi or Miss Yeon Jae. Otherwise, do NOT bother with subbing the 씨. If a son is talking to his mother and uses “씨", then do use Miss! Or a mother is taking to her son and uses 씨 --then use Mr. or Master as appropriate.

  11. Romanization – We generally follow the South Korean Revised Romanization Rules except for: Kim, Park, Kang, We usually don’t put hyphens in given names per a survey of subbers’ preferences taken several years ago – they didn’t want to type the “-”. We follow the romanization rules for place names.
    Instead of translating, you may use: Ahjumma (Ajumma) , Ahjussi (Ajusshi), Agasshi (Agassi) , Noona, Oppa, Hyung, Sunbae, Hoobae, Unni (Eonni) may be used instead of lady (aunt), mister (uncle), young lady, sister, brother, brother, senior, junior, sister You may also write Aigoo or Omo as appropriate or Jeez, Gosh, Oh my, etc. [Jeez is short for Jesus so should be capitalized]

  12. Relatives should be capitalized when the relative is being spoken to but if the person is the subject of discussion and the title is modified, then do not capitalize. : I am thankful to my mother. Hello, Mother. His father is the president of a corporation. Hi, Dad! This is my brother. Hyung!

  13. Titles should proceed the proper name. Not Cha Bong Man Chairman but Chairman Cha Bong Man. Not Lee Eun Jae Attorney but Attorney Lee Eun Jae, Oppa Do Yoon, not Do Yoon Oppa.

  14. Although Korean does not have articles such as “a”, “an” and “the”, please insert them where necessary. In general “A/an ” are indefinite and “The” is specific or definite. I am going to a school vs. I am going to the school – a school is any school, the school is a specific school.

  15. For the benefit of subbers from English to other languages, please try to avoid using abbreviations such as “prbly” (probably), “tty” (I’ll talk to you later) or “ltr” (letter or later?).

  16. We use Italics [the < and the > with an i in the middle (sorry, if I did the real thing, you wouldn’t see the marking) for any printed material, text messages, and flashbacks of what was said, unspoken thinking, unspoken reminiscing and unspoken dreaming, song lyrics when the singer is not visible live; and speech where the voice is being transmitted over the telephone, radio, or television. Eg. Person A speaks (live, no italics) and Person B’s voice is heard over the phone (put B in italics). Then screen shows B saying next part of conversation (no italics) and we hear A’s response to B over the telephone (Put A’s response in italics).

Please don’t automatically italicize dialogue just because the speaker is momentarily off screen – italicize only if the words fall in one of the categories described in the prior paragraph.

  1. For money, you can use either won or dollars. Don’t get hung up on checking the daily currency rate. Rounding won to dollars by knocking off the last three zeroes is okay.

  2. Although a date in Korean is year, month, day, we usually sub the American way: Month Day, Year. If you are translating a written date on the screen. If the screen says 2015 년 – just sub it 2015, not 2015 year.

  3. “Gonna” and “wanna” are usually not standard English – may be used if a child said it, but otherwise, avoid them both!

20) Breaks. Put a break in a subtitle only if more than one person is speaking in the dialogue or the subtitle segment contains both transcription of text on the screen and dialogue. Don’t put breaks into the subtitle for appearance’s sake only.

  1. If a segment is unnecessary—DON’T WRITE ANYTHING – not even the < br >! Leave the unnecessary segment blank please. If no words can be heard or be translated do not write your description such as “sobbing” “moaning” “singing”. If you cannot read the text on the screen, do not write a break or “undecipherable” – Just leave the blank blank! If you wish, you may post in Team Discussion the time of segments which can be deleted.

  2. Use of English words – if you hear an English word in the Korean dialogue, use the word in the subtitle except that be mindful of the different usage of certain words such as “schedule” which is very often used when in English we would use “appointment;” – Instead of “ I have schedule tomorrow,” sub “I have something scheduled tomorrow” or “I have an appointment tomorrow.”
    “Grand open” when we would use “Grand opening”, etc.

  3. If more segments are needed, please post in Team Discussion. If the video suddenly goes out of sync, post the information and stop subbing – It’s temporary and usually is fixed within a short time. Do come back later!

5 Likes

I think this happens a lot though…

1 Like

When using
for breaks in subtitling, do we also use the dash (-) for the sentence by the next speaker? For example, I have seen all three, not sure which to use.

Are you happy?
-Yes!

OR

-Are you happy?
-Yes!

OR

Are you happy?
Yes!

Which is correct?

Thank you!

with two or more speakers I use the 2nd version, meaning each speaker has a - (dash and one space before the dialog):

      - Are you happy? (the break coding "< br >")
      - Yes!
3 Likes

When there are two or more people, I think it’s much neater to put a dash for both. And, unlike your example, always with a space between the dash and the sentence:

  • Are you happy?
  • Yes!

I always use the first one, because I think putting two dashes is not necesarry. The dash is there only to make it clear that there are two people talking in one segment and putting a dash for the sentence means that now person B is talking in stead of person A.
Maybe guidelines for other countries are different, but I’ve seen for Dutch that you should only use the first construction as in your example. Also I’ve never seen two dashes in official subs in Dutch.

@emmelie96
At school I was taught that we put one dash for each speaker, on separate lines.

  • Hi!
  • Hi!
  • How’s things?
  • Fine.

If we don’t do that, it’s considered reported speech and needs “…” (<<…>>) and verbs like “they said”. Maybe it’s different in other languages.

1 Like

Yes, I’ve read about Dutch subbing on a forum and there someone said the rules can be different from English or other languages. There was also a link to guidelines set up by a professional subbing company. If you like here is the link see it.
I don’t agree with everything, for example they say you should never ever use an exclamation mark, but I think it’s ok to use it when someone is screaming.

[quote=“christina_, post:31, topic:10456”]
At school I was taught that we put one dash for each speaker, on separate lines. If we don’t do that, it’s considered reported speech and needs “…” and verbs like “they said”. [/quote]

Well you’re right, of course, but what they taught us in school was for writing of essays, articles, novels and such, not for subtitles. In subtitles you know that it’s direct speech anyway.

I like to put a dash for each speaker because it looks much neater and more balanced, and it immediately says “this is dialogue”. I don’t remember what happens in films you see in cinemas, it’s been such a long time since I’ve been to an actual cinema!

2 Likes

I have no idea. Personally, until I see a dash, I consider it’s the same person speaking.

1 Like

We have a Dutch subbing team at Ninja Academy that is up and running. They have a subbing guide in Dutch as well. You might wish to check this out.
https://docs.google.com/document/d/1wRQApR1q_fMIw7ZZI7C1xizhN4_e7gbRhkdp9clJ0zI/edit

https://docs.google.com/document/d/1wRQApR1q_fMIw7ZZI7C1xizhN4_e7gbRhkdp9clJ0zI/edit

there is just empty space, what were you trying to post?

@robertases
It’s a google doc link, which for whatever reason, the discussion tries to preview it instead of just showing the link. Fixed (just added a space in front) in first post.

2 Likes

I know there was going to be a Dutch subbing team at Ninja Academy. I once got a email that it would be launched soon and I signed up to join, but I never heard anything of it afterwards. So I didn’t know it was already out.

Ooh! Although I can’t understand Dutch, just by looking at the headings and the tables, I could see it’s an awsome reference document. Now I’m envious, mine seems paltry in comparison. I wish I could read what they say…
(On the other hand, if it’s too long they don’t read it, so that’s a small consolation)

I looked at people interested in Italian subtitling lessons at the Ninja page, but I saw there was only one person, so didn’t even attempt to write to anybody to volunteer for a teaching post. Same for Greek, only one person. Oh well, I suppose I’m just going to continue with my one-on-one Skype sessions.

I’ve read a part of the document and it’s really well explained.They give a lots of examples of sentences that could be translated wrong and how to translate them correctly. And in the doc is also a link to translations of medical, juridical and political terms with the proper Dutch translation.

1 Like