Template talk:ko-hanja/new

From Wiktionary, the free dictionary
Latest comment: 5 years ago by KevinUp
Jump to navigation Jump to search

@Suzukaze-c: Hi. How do you display multiple reading, like : 각 and 녹? --Anatoli T. (обсудить/вклад) 05:32, 24 June 2019 (UTC)Reply

I've been using different Etymology sections when the reading is totally different, and <br> + multiple copies of {{ko-hanja}} for multiple hun of the same reading. —Suzukaze-c 05:35, 24 June 2019 (UTC)Reply
@Suzukaze-c: Thanks. Like this?:
===Hanja===
{{ko-hanja/new|뿔|각}}<br>
{{ko-hanja/new|뿔|녹}}
--Anatoli T. (обсудить/вклад) 05:42, 24 June 2019 (UTC)Reply
@Suzukaze-c: User:B2V22BHARAT has added {{ko-hanja/new|사람 이름|녹(록)}} at , which is obviously problematic, it links to 녹(록). Can the template/module handle 두음 법칙 (dueum beopchik), displaying together >, like the old style did, something like > (rok>nok)? They belong to the same etymology. --Anatoli T. (обсудить/вклад) 06:18, 24 June 2019 (UTC)Reply
@Atitarev Your edit on was problematic, because you have put 뿔, 록(녹) which is not true. ///
Regarding 두음법칙, good idea. I think the format should represent North Korean style, too because words that don't come in the initial position are not affected by the 두음 법칙 (dueum beopchik). B2V22BHARAT (talk) 06:35, 24 June 2019 (UTC)Reply
Also, 록(녹) was not made by me. It is stated in here, look: https://hanja.dict.naver.com/hanja?q=%E8%A7%92&cp_code=0&sound_id=0 B2V22BHARAT (talk) 06:46, 24 June 2019 (UTC)Reply
@B2V22BHARAT: Yes, thanks for putting the right eumhun, my edit was problematic in that respect - I was just converting from the existing entry. I don't mean to offend you, I just mentioned the problem that in your edit the link is to 록(녹) (it's wrong but it's not your fault) but it should have separate links to both and . --Anatoli T. (обсудить/вклад) 06:48, 24 June 2019 (UTC)Reply
(edit conflict) @B2V22BHARAT: User:Suzukaze-c made the edit to use: {{ko-hanja|사람 이름|록||녹}}, which fixes the current issue. It links separately to and and even shows that (nok) is South Korean.
BTW, my preference is that etymologies, and everything else goes to lemmas, that is hangeul, not hanja. --Anatoli T. (обсудить/вклад) 06:59, 24 June 2019 (UTC)Reply
@Atitarev, B2V22BHARAT: Have a look at the entry now. —Suzukaze-c 06:58, 24 June 2019 (UTC)Reply
Thanks for that! --Anatoli T. (обсудить/вклад) 06:59, 24 June 2019 (UTC)Reply
@Atitarev @Suzukaze-c I'll take a look at it later. Thanks! B2V22BHARAT (talk) 07:02, 24 June 2019 (UTC)Reply
BTW I don't it's an (edit conflict), because I just corrected your error in good faith one time. And distinguishing 록(녹) is a new problem that you brought in in this talk. Anyway, thanks for contributing to wiktionary :)) B2V22BHARAT (talk) 07:05, 24 June 2019 (UTC)Reply
@B2V22BHARAT: I am afraid you misunderstood me again :). {{ec}} just shows my edit conflicted with the next edit by Suzukaze-c (not yours) but I posted it anyway, to show what I wanted to say before I saw the new message. If you stick around you'll learn how things work here. --Anatoli T. (обсудить/вклад) 07:11, 24 June 2019 (UTC)Reply
Hm, it looks like you and Suzukaze have been talking before I interuppted. I was just looking at your edit history and found an error, so I just fixed it according to my standard. Thanks. B2V22BHARAT (talk) 11:50, 24 June 2019 (UTC)Reply
@B2V22BHARAT: Thanks again. So that you understand, in case I wasn't clear, why the result was "problematic" (again, not necessarily your fault but the way the template was used), you don't link variant words like this: color (colour) but like this: color / colour. That's why I asked for a fix. --Anatoli T. (обсудить/вклад) 12:17, 24 June 2019 (UTC)Reply
I'm not sure what's going on here, but when a hanja has multiple readings, I would prefer to split it to multiple etymologies, such as that of 暴#Korean. By using an etymology header, we can add other valuable information such as Middle Korean hanja readings from dictionaries such as 훈몽자회/訓蒙字會 and 동국정운/東國正韻. This is work that can be done in future. KevinUp (talk) 13:34, 24 June 2019 (UTC)Reply