3

I understand relative clauses in Korean in general, but I struggle when there are multiple descriptors for one noun. I don't know if the descriptors should be joined with a conjunction to make one big relative clause or listed serially as two relative clauses. For example, I wrote the following sentence:

이 책은 유니라고 하는 한국 어린이가 탄자니아에 살 미리암이라고 하는 언니랑 편지를 쓰는 이야기예요.

Where I was trying to say:

This book is a story about a Korean kid named Yuni writing letters with her friend [lit: older sister] who lives in Tanzania and is named Miriam.

I was told it should be correctly written as:

이 책은 유니라고 하는 한국 어린이가 탄자니아에 사 미리암이라고 하는 언니랑 편지를 쓰는 이야기예요.

Note the 살고 was changed to 사는 creating serial relative clauses. This would change the transition to:

This book is a story about a Korean kid named Yuni writing letters with her friend [lit: older sister] who lives in Tanzania named Miriam.

Removing the "and is" does arguably improve the sentence even in English, so I have somewhat answered my own question, but I'm wondering if there are rules or patterns to follow for this in Korean. Specific questions:

  • In the corrected sentence does 탄자니아에 사는 modify 미리암 or 언니? I'm assuming 언니, which is why I said they were serial, but I guess it could also be interpreted as modifying 미리암 creating nested relative clauses.
  • Are there rules when to join with a conjunction vs serial clauses? I'm assuming conjunctions would be used when the descriptions are one related unit, but want to confirm.
  • Does the order of multiple relative clauses matter?

1 Answer 1

1

"사는" is much more natural in the sentence. I can think of two reasons:

  1. When two clauses modify the same noun, I think it is quite common to have "A하는 B하는 C", especially if the middle part (B) is short. On the other hand, "A하고 B하는 C" is preferred if A and B are comparable(?) properties that belong to the same category.

    For example, I would say "어제 꽃집에서 본 예쁜 꽃", because "꽃을 꽃집에서 보았다" and "꽃이 예쁘다" are very different properties. You wouldn't normally say "그 꽃은 어제 꽃집에서 보았고 예쁘다." ("The flower was seen yesterday and is pretty." - it's even awkward in English.)

    On the other hand, I would say "빨갛고 파란 꽃" instead of "빨간 파란 꽃", just like an English speaker would more likely say "a red and blue flower" instead of "a red blue flower". Here they are equal properties, so it's more natural to use connect them using -고.

    Similarly, "탄자니아에 살다" and "(이름이) 미리암이라고 한다" sound like "different categories" to me. Especially since "X라고 하는 Y" is more or less a fixed phrase, so adding "-하고" in front of it doesn't sound natural.

    On the other hand, you could say, e.g., "탄자니아에 살았고 지금은 한국에 사는 언니".

    In general, I'm not sure if there's a fixed rule on which form is better. (If anyone has a better idea, please chime in.) I think you just have to keep practicing and get the feeling of it.

  2. Another problem is parsing: if you use "살고", the sentence could be equally parsed as:

    이 책은 [유니라고 하는 한국 어린이가 [탄자니아에 살고] [미리암이라고 하는 언니랑 편지를 쓰는]] 이야기예요.

    = This book is a story about a Korean kid, Yuni, who lives in Tanzania and writes letters with a girl named Miriam.

    (Although I would rather use "살면서" instead for this meaning.)

    So, using "사는" gets rid of this ambiguity.

Finally, regarding your specific question #1, "탄자니아에 사는" can only modify 언니, because if it modifies 미리암 that would sound pretty weird: it then means A girl who is named 'Miriam who lives in Tanzania'!

3
  • Awesome answer, thank you! I was thinking along the lines you mentioned, but your examples confirm and highlight proper usage. As far as my (embarrassing) inflection mistake, would you mind of if I edited both my question and the first paragraph of your answer? I think it'll help future readers. Commented Jun 17, 2017 at 9:27
  • Yeah, sure, please do. Glad it helped. :)
    – jick
    Commented Jun 17, 2017 at 17:34
  • Updated both the question and answer! Commented Jun 18, 2017 at 0:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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