5

The rules for when whitespace is required/permitted in Korean are not obvious, but are not explicitly discussed in any grammars or textbooks I have access to.

I can infer this much:

  • Between classifier words and their complements (e.g. 한 달)
  • After pre-verbal adverbs, sentential adverbs and conjunctions (e.g. 잘 지내세요)
  • To separate complete phrases (e.g. 도서관에서 책을 읽어)

while whitespace is not allowed:

  • before phrase-final particles (e.g. 저도; 민식만; 시드니까지)

There are clearly some additional rules, as it seems that whitespace after the classifier word and before 만 is optional as well: 한 달 만 or 한 달만, but I doubt particles 은/을 can ever be preceded by whitespace.

Similarly, 뭐 is always followed by whitespace in my textbook, but just Googling I see matches for both 뭐 했어 as well as 뭐했어.

Question 1

Are there any other environments in which whitespace is required or optional? Can the above rules be generalised into a simpler rule?

Question 2

In Korean, phonemic words which begin with 'weakly aspirated' affricate or stop consonants (i.e. ㄱ, ㄷ, ㅂ, ㅈ) are pronounced lenis with weak aspiration.

Do the word boundaries as indicated by whitespace always correspond to phonemic words?

1 Answer 1

4

Since no one else has submitted an answer I guess I will. Be warned though that my answer will be based more on anecdotal evidence from living and working in Seoul for 2 years.

Word Boundaries in Written Korean
Koreans have a joke about word boundaries:

아버지가 방에 있어.
dad-SUB room-LOC exist
Dad is in [his] room.

아버지 가방에 있어.
dad handbag-LOC exist
i) [It is] in Dad's handbag.
ii) Dad is in [his] handbag.

(The subject particle 이/가 is often dropped in casual speech, making the ii variant grammatical. My original understanding was that ii was the preferred interpretation but talking with friends seems to suggest that i might be the preferred interpretation. I would need more data before I can say for certain.)

However, the question remains "are word boundaries observed in usage?". The answer to that, again taken from my personal experience, is "it depends on the context".

Short form writings (SMSes, Twitter, chatting, notes-to-self, etc.) allow for the omission of white spaces. I have actually received SMSes from my faculty which had all spaces removed (which caused me great confusion as a non-native speaker).

Longer and more formal forms do enforce word boundaries (thus the joke above). From what I've seen, the spaces are heavily enforced after case markers (은/는 topic markers, 이/가 subject markers, 을/를 object marker, 에(게) dative marker, etc.) and after any structural markers (은/는/을 adjective marker, adverb marker, 와/과 lexical and, sentence and, various other conjunctions).

The example you cited, 한 달 versus 한달 (both "one month"), varies because they are both nouns and both "pure" Korean (i.e. not taken from another language). meaning "one/first" and meaning month. They retain their meaning in isolation and the sense of their meaning does not change when viewed as a compound word. Therefore, without any grammatical markers, spacing is not strictly enforced.

Interestingly, I've found that Chinese-based vocabulary (i.e. 한자, or"hanja", words) tend to avoid intra-word boundaries. For example: 일월 (一月, also literally one/first month, but with a different usage context than 한달) means "January" while 일 월 (一 月) is ungrammatical.

I hypothesize that although these characters have a meaning in isolation the white space is enforced because, unlike "pure" Korean words, the way Chinese-based vocabulary combines changes the meaning of the characters based on context. For example, 친구 (親舊, "friend") broken into it's base characters is literally "old closeness" ( meaning "close", in the sense of relationships, or "related" and meaning "old" or "ancient"). In this particular case one can guess how the modern meaning "friend" is derived (probably "someone that you have been close to for a long time"), but the literal meaning is essentially non-sense. Therefore, they cannot be analyzed separately.

Word Boundaries in Spoken Korean
This is a much more interesting problem. As I am sure you know, spoken language isn't a series of discrete words like written language but a continuous stream of input.

Consider the following:

잘 못했다.
well not-do-PAST
[I] did not do [it] well.

잘못 했다.
incorrect do-PAST
[I] did [it] incorrectly.

These two examples have different pronunciations. I am not a phoneticist so I cannot comment on exactly how they are different, but the effect is noticeable. It may have something to do with how humans comprehend word boundaries or it may be due to Korean's semi-tonal nature.

Again, due to my lack of expertise in phonetics I do not feel comfortable attempting to answer your second question.

3
  • Thanks for your answer. My question 2 actually relates to your joke: if whitespace corresponds to phonemic words, then ignoring intonation, 가 would have the voiced pronunciation in 'Dad is in [his] room', while exhibiting the voiceless weakly aspirated pronunciation in 'Dad is in [his] handbag'. If you have access to native speakers it would be very informative to know whether the two instances of /g/ are produced differently (modulo intonation).
    – jogloran
    Nov 2, 2012 at 4:54
  • @jogloran Oh, I didn't realize that is what you were asking. My understanding is the same as yours. That's how I was taught voicing in Korean. I asked a few [non-linguist] native speakers and they seem to think there is no difference at all.
    – acattle
    Nov 2, 2012 at 5:08
  • I thought it would be useful for non-Korean speakers to know that Korean does not have any voiced/non-voiced distinction (however it does distinguish by aspiration, which English does not) making it difficult for non-linguistics to notice voiced features. That could explain the difference between what my Korean Language Teacher told me and my friend's intuitions.
    – acattle
    Nov 6, 2012 at 12:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.