Template talk:ko-conj-adj

From Wiktionary, the free dictionary
Jump to navigation Jump to search

Stems whose final ㅂ changes to 오[edit]

Let's be certain to include in the test forms an adjective whose stem ends in a ㅂ that changes to 오, e.g. 가깝다 (gakkapda, “gakkapda”), where important forms to verify include the formal plain future/assertive indicative (가깝겠다), formal plain present interrogative (가까으냐), and the formal plain past (가까왔다). Rod (A. Smith) 23:15, 25 June 2007 (UTC)[reply]

You raise an important point, but just for the record the connective/haeche form of 가깝다 is actually 가까워.  ;-) I've added 곱다 to the house of pain above; it does show the 오 mutation... Because this change is reflected in stem2, which is used for all forms dependent on the second principal part, there shouldn't be any specific weirdness involved... but yes, let's keep an eye on it.
I'm still somewhat out to sea on the proper rules for the formal plain present interrogative for adjectives; it's not a form I encounter very often. Judging from Google, Koreans are as confused as I am; the number of people forming it as stem1+냐 (가깝냐) seems roughly equal to the number forming it as stem3+냐 (가까우냐). But stem3 seems right. -- Visviva 04:07, 26 June 2007 (UTC)[reply]
Lee & Lee support this with examples like 작으냐 (작다) and 기냐 (길다), although they formulate the rule in such a way that the reader is left assuming that the correct form would be *가깝으냐! But at least from their examples it seems clear that 가깝냐 cannot be correct, so it must be 가까우냐. -- Visviva 12:54, 26 June 2007 (UTC)[reply]
Yes, you're right about 가까우냐 instead of *가까으냐. My "201 Korean verbs" book and http://user.chollian.net/~lyh220/urimal/verbs.htm both corroborate that. Strangely, those two sources disagree regarding 가까워... vs. 가까와.... They are both commonly used (193,000 Google hits for 가까웠다 vs. 204,000 Google hits for 가까왔다).
I tried adding 굽다 (gupda, “gupda”) to the house of pain because it follows the 눕다 (nupda, “nupda”) model, which is significantly different from that of 곱다 (gopda, “gopda”). Following is my attempt:
Unfortunately, I cannot make it display correctly. For example, it should show 굽는다, 굽느냐, etc. Is there another parameter I should use for such words? Rod (A. Smith) 17:52, 26 June 2007 (UTC)[reply]
For 굽다 as an adjective, my dictionaries disagree on 굽은 vs. 굽는; but since the latter would be insanely irregular, I'll assume it is 굽은 (Google seems to agree):
My source for 가까워 was Naver's mirror of the Pyojun, here: [1]. Perhaps there is more going on than meets the eye, though. Interestingly, the Pyojun's entry for 굽다 as "bent/to bend" ([2]) is ambiguous, as it does not provide separate information for the verb and adjective senses. -- Visviva 00:06, 27 June 2007 (UTC)[reply]
w:Korean language North-South differences#ㅂ-irregular inflections attributes the difference in 가깝다 conjugation to regional variation (with North Korea following historical vowel harmony as 가까+와). We should probably separate North and South Korean conjugation tables when the inflections differ by region. Rod (A. Smith) 02:04, 28 June 2007 (UTC)[reply]
Oho! Very cool, thanks for catching that. This difference can be captured by the template as written (changing stem2, stem2_r, and haet) but there may be other differences that are not so easy to take care of. I trust we will cap this at North/South differences though, and leave Hamgyong, Jeju, Gyeongsang, et al. out of the picture for now? -- Visviva 08:52, 28 June 2007 (UTC)[reply]
Interestingly, a site search of KCNA suggests that 가까운 (rather than *가까온) is still correct for the North. Odd. -- Visviva 13:24, 28 June 2007 (UTC)[reply]

Transliteration and transcription[edit]

I think {{ko-conj-adj}} (and probably {{ko-conj-verb}}) has some transcription errors, e.g. with 좋다 above, it transcribes 좋다 as *joda instead of jota, 좋지만 as *jojiman instead of jochiman, 좋겠다 as *jogetda instead of joketda, 좋더니 as *jodeoni instead of joteoni, 좋고 as *jogo instead of joko. As we've discussed, the solution depends on whether we choose to transcribe or transliterate. Rod (A. Smith) 22:20, 2 July 2007 (UTC)[reply]

Woops! Thanks for noticing. I could have sworn I fixed that -- in fact it was noticing that joko was specifically mentioned in the RR specification that made me do my last round of fixes -- but obviously I failed to do so. Should be OK now (per standard RR), unless I missed one. -- Visviva 04:09, 3 July 2007 (UTC)[reply]

Conj?[edit]

Do adjectives have conjugations in Korean, or do they have declensions like they do in other languages? Mglovesfun (talk) 12:23, 20 July 2010 (UTC)[reply]

Just another example of Latin-based grammatical terminology trying (and failing) to describe the world's languages. —Μετάknowledgediscuss/deeds 21:06, 12 January 2013 (UTC)[reply]

New template[edit]

I have created {{ko-conj-adj/auto}}, which is essentially based on this template but generates all forms automatically (i.e. no |stem1= ..., |stem2= ..., |stem1_r= ...). Only the |irreg=... (if p-, h- or s-irregular) parameter is needed. It can also detect whether conjugation in the North Korean standard differs from South Korean standard, and can generate two templates simultaneously. Wyang (talk) 23:27, 10 April 2014 (UTC)[reply]