Talk:공룡

From Wiktionary, the free dictionary
Latest comment: 5 years ago by B2V22BHARAT in topic Phonetic change
Jump to navigation Jump to search

Phonetic change[edit]

@B2V22BHARAT Hi. Would you happen to know whether the phonetic change from 공룡 (gongryong) to 공뇽 (gongnyong) when pronouncing the word also occurs in North Korea?

Also, do South Koreans get confused when learning hanja? is spelled as (yong) but 恐龍 is spelled as 공룡 (gongnyong). This is of course, due to 두음 법칙 (頭音法則, dueum beopchik). Modern dictionaries don't usually list the original reading (, ryong) but fortunately Wiktionary has explanations of this at //.

On an unrelated note, please remember to use {{ko-l}} or {{l|ko}} for Korean hanja because Korean fonts are different from Chinese fonts (Korean preserves the original shape better). KevinUp (talk) 12:06, 15 May 2019 (UTC)Reply


@KevinUp I'm a South Korean, so I don't know about North Korean pronunciation. However, if you listen to how North Korean pronounce words via youtube or 북한 방송, you will notice that North Korean sometimes pronounce 로동당 as 노동당, because it's easier for them to pronounce it that way. So, what North Korea wants to do is they want to preserve the historical form of words. Pronunciation may be different from the actual spelling of words for the ease of pronunciation. On the other hand, South Korea wanted to change the historcal form of words to match the actual pronunciation. That's the difference. I don't care either way because my surname pronunciation is unaffected by 두음 법칙 (頭音法則, dueum beopchik).

Also, in South Korea, we pronounce 공룡 (gongnyong) as 공룡 (gongnyong). 두음 법칙 (頭音法則, dueum beopchik) was basically created in order to help Koreans pronounce better. It was created for the good purpose. So let's not see it badly. I think language can be changed that fits best for that society. In the past, I didn't see 두음 법칙 (頭音法則, dueum beopchik) in a good way because I felt cheated. However, now I understand and decided to accept it.

Sincerely, B2V22BHARAT (talk) 13:07, 15 May 2019 (UTC)Reply