Template talk:Korean

Name

I think this is better using a "name infobox." --68.74.66.158 21:32, 17 December 2005 (UTC)

If you wish to use a template without hanja, then use template:ko-hrm. --68.74.66.158 04:21, 18 December 2005 (UTC)

Similar templates

• {{Ko-hrm}}
• {{Ko-chmr}}

Limitations of this template

This template is perfectly acceptable for Korean names that need to be cited in other articles.

However, for article subjects, please use Template:Koreanname or one of the many other templates available. This is in conformity with Wikipedia:Naming conventions (Korean), and helps to ensure that we have a consistent approach. -- Visviva 00:13, 16 January 2006 (UTC)

I wish that there was a template that was more or less equivalent to the Zh template for Chinese. An infobox can be a bit awkward. I'm thinking of inanimate things in particular: something along the lines of

korean | hg=한글 | hj=none | rr=Han-geul | mr=Han'gŭl | y=Hankul | context=s

Naturally, all bar hg or simply h would be optional. It would made things a lot easier. So many articles are formatted this way, it should be supported. Cashie (talk) 11:58, 4 November 2010 (UTC)

Problem with spaces

Please delete all superfluous spaces from this template; that is, spaces in the template that may result in plenks in articles. For example, there should be no space or line break between ‹사› and ‹;› in Chungcheong#Notable personalities. Wikipeditor 22:57, 29 May 2007 (UTC)

Oh, and if some of the spaces that cause trouble cannot simply be deleted, how about replacing them with some special character such as zero-width joiner, or simply <nowiki></nowiki>? Wikipeditor 23:14, 29 May 2007 (UTC)

I think this is fixed now; if not, please advise. If I recall correctly, in earlier versions of MediaWiki spaces were automatically stripped from template variables; apparently that is no longer the case, hence the emergence of this problem. (or maybe this problem was here all along...) Happiness, -- Visviva 05:32, 30 May 2007 (UTC)

Context parameter

I've added a context parameter to this template, so there is no longer any need to maintain a seperate variant for North Korean usage ({{Ko-chmr}} was only being used in one article anyway). Just add context=north and let the template do the rest! PC78 11:50, 31 August 2007 (UTC)

Problem when using in headers

There was a bug when using the template on ";" header lines, for example like this:

Korean: 한국어; Hanja: 韓國語; RR: Hangugeo; MR: Hangugŏ

Korean: 한국어; Hancha: 韓國語; RR: Hangugeo; MR: Hangugŏ

If you use ";" headers and include a ":" anywhere on the line, MediaWiki apparently thinks that you meant to include a line break. I altered the template to use "&58;" instead of ":" in the code, so now it works properly in ";" headers. I hope that this won't cause any problems elsewhere. --Stefan2 (talk) 19:50, 22 May 2012 (UTC)

Third context syntax/parameter

May somebody please add a third context parameter? At the moment, we currently have two: "North" (Chosongul) and "South" (Hangul). However, both of those terms appear to be have been coined within the past hundred years, so a third parameter "Neutral" (Korean) would be useful, to maintain neutrality in articles regarding ancient Korean history, up to and including the Joseon Dynasty. Illegitimate Barrister (talk) 08:12, 1 May 2013 (UTC)

@Illegitimate Barrister: 2 years 3 months later... better late than never? I agree with what you wrote above, so I added the optional parameter "context=old" which displays Hunminjeongeum instead of Hangul or Chosungul. According to the Hangul article, Jeongeum can be used as shorthand, but a cursory search suggested it was not very common so I went with the full name. I'm also not married to the "old" value so if you or anyone else has a better idea, feel free to change it. Ry's the Guy ^{(talk|contribs)} 14:02, 27 August 2015 (UTC)

Thanks. Much appreciated! – Illegitimate Barrister, 14:04, 27 August 2015 (UTC)

Could you possibly add it to "Template:Infobox Korean name" as well? – Illegitimate Barrister, 12:29, 16 September 2015 (UTC)

Done. I've tested it and it seems to be working fine. Please let me know if you come across any problems. Ry's the Guy ^{(talk|contribs)} 13:53, 16 September 2015 (UTC)

Wow, that was fast. Thanks. Looks to be working. – Illegitimate Barrister, 14:30, 16 September 2015 (UTC)

Template Hangugeo

There's a discussion going on at Template talk:Hangugeo about whether that template is different enough from Template:Korean to be useful. Any input would be appreciated. Thanks! Ry's the Guy ^{(talk|contribs)} 10:22, 3 September 2015 (UTC)

Redundant nesting of the lang template

The use of the {{lang}} template within {{Korean}} seems to be redundant and results in what I think is suboptimal html. If this is the case then there are about 60 instances in articles that need to be replaced. Any volunteers? Uanfala (talk) 20:46, 30 September 2016 (UTC)

I agree, Uanfala. With only 64 instances it shouldn't be too difficult to remove them. Have fun! Primefac (talk) 15:20, 4 November 2016 (UTC)

Good then! But I think I'll leave that to the AWB folk who'll be able to manage it much more efficiently than I could ever dream of. – Uanfala (talk) 20:17, 4 November 2016 (UTC)

Still an issue

There is still nesting required to properly render the Hanja. Can a template-editor or administrator remedy this? Compare:

1. Korean: 대청황제공덕비; Hanja: 大清皇帝功德碑 ({{Korean|hangul=대청황제공덕비|hanja=大清皇帝功德碑}})
2. Korean: 대청황제공덕비; Hanja: 大清皇帝功德碑 ({{Korean|hangul=대청황제공덕비|hanja={{lang|ko|大清皇帝功德碑}}}})

Apart from having a pop-up of "Korean language text" appear when scrolling over it, the Hanja in No. 1 is rendered indistinguishable from unformatted raw Chinese text. CaradhrasAiguo (talk) 21:20, 9 July 2018 (UTC)

CaradhrasAiguo, I'm not entirely sure where the issue is. Other than the extra <span> added by the extra {{lang}} template, there's no difference between the output that I can see. Primefac (talk) 11:55, 10 July 2018 (UTC)

@Uanfala:@Primefac: Using another example, the Hanja in Korean: 대한민국; Hanja: 大韓民國 is identical in font to the bare format "Hanja/Chinese: 大韓民國"; sorry in advance if this is still unclear to both of you. Also, yesterday, I completed my drive to remove the redundant nesting in the "hangul" parameter. CaradhrasAiguo (talk) 21:03, 10 July 2018 (UTC)

Um... shouldn't it be? I realize that I don't have any extra fonts enabled on any of my browsers, but I see (on the page, in the edit mode, and in the page source itself) the same text regardless of whether it's in {{Korean}} or not. I think I'm being thick, though, and I apologize for the idiocy but could you explain in captain-dummy-talk what the issue seems to be? Primefac (talk) 12:00, 11 July 2018 (UTC)

The two examples look the same to me as well. Perhaps CaradhrasAiguo could post a screen shot showing the difference. Updated to add: I see a very slight difference in Safari for Mac but no difference in Firefox for Mac.

The rendered HTML for the relevant portion of the two examples looks like this:

<span lang="ko-Hani" title="Korean language text">大清皇帝功德碑</span>

<span lang="ko-Hani" title="Korean language text"><span lang="ko" title="Korean language text">大清皇帝功德碑</span></span>

There is a nested set of span tags. If lang="ko-Hani" does not render in the way that you want, then maybe the {{Korean}} template needs to apply different formatting. Take a look at Template:Korean/testcases, at the bottom, which compares the live template with a sandbox version that might be better. Is it better? I don't really see a difference, but you might. – Jonesey95 (talk) 16:44, 23 July 2018 (UTC)

I have neglected to mention I have been using Chrome on a Windows 10 machine, but yes, the current sandbox version (all lines using {{ko-hhrm/sandbox}}) at Template:Korean/testcases renders properly for me now. CaradhrasAiguo (talk) 17:26, 23 July 2018 (UTC)

I have updated the template from the sandbox. I trust that editors will report problems here if there are unintended consequences. – Jonesey95 (talk) 19:33, 23 July 2018 (UTC)

misnested tag causing lint error

<span class="error"><code style="color:inherit; border:inherit; padding:inherit;">[[Template:Korean]] requires{{para|hangul}} parameter.</span></code>

should be

<span class="error"><code style="color:inherit; border:inherit; padding:inherit;">[[Template:Korean]] requires{{para|hangul}} parameter.</code></span>

I don't have rights to fix it. Could someone who does... do so? pauli133 (talk) 03:05, 15 May 2018 (UTC)

 Fixed. Primefac (talk) 11:28, 15 May 2018 (UTC)

Template-protected edit request on 26 December 2018

I'd like to add a "context=neutral" option for articles, such as Korean Demilitarized Zone, where the term is the same in both North and South Korea but the choice Chosŏn'gŭl/Hangul is in dispute. It would render as "Chosŏn'gŭl/Hangul:&nbsp;" and provide equivalent functionality. This would be just for convenience. Daviddwd (talk) 03:48, 26 December 2018 (UTC)

Hi David. I'm wondering if you were aware of the already available |context=old which displays the more neutral Hunminjeongeum instead of "Hangul" or "Chosŏn'gŭl", though I'm not sure that this is what you've meant since that concerns language differences pre-1945. Right now the DMZ article lists all three manually, Chosŏn'gŭl/Hangul/Hanja. Pinging @Rystheguy: to get their input on this. Might it be possible to incorporate all three automatically in the template?  Spintendo  23:22, 27 December 2018 (UTC)

 Not done: please establish a consensus for this alteration before using the {{edit template-protected}} template. Primefac (talk) 20:09, 28 December 2018 (UTC)

Remove the "context" parameter?

Cross-link to a discussion I posted at Wikipedia talk:Naming conventions (Korean)#Why are we calling Hangul "Chosŏn'gŭl" in North-Korea-related articles? Please discuss there. – Fut.Perf. ☼ 06:51, 1 May 2019 (UTC)

I've made the change as proposed in the thread linked above, as there was no opposition to it during one week and I think it's clearly more in line with standard policy. On second thought, it occurs to me that for this template we could also simply go for "Korean" instead of "Hangul". That seems even more in line with how we do it for other languages. Whenever a language is clearly and unambiguously associated with one writing system, we just name the language and then give the native form in the typical native script, without bothering to name the script as such. Just throwing this idea out here for the moment, in case anybody has comments on it. Fut.Perf. ☼ 10:20, 4 May 2019 (UTC)

I have to say, for the record, that I am absolutely opposed to this recent unilateral change. It should either be changed to the neutral all-encompassing term "Korean", or the parameter for "Chosongul" should be added back. The way it is at the moment appears to violate WP:NPOV as we've got "Hangul" being used for many North Korean articles which is weird; for instance the way it is after this recent change would be like if the article on the England national football team were located at "England national soccer team". On another note, we might just well be better served merging (i.e. deleting/replacing) this template with Template:Lang-ko. – Illegitimate Barrister (talk • contribs), 07:30, 12 June 2019 (UTC)

Let's please keep the discussion in one place, at Wikipedia talk:Naming conventions (Korean). Fut.Perf. ☼ 06:14, 13 June 2019 (UTC)

Template-protected edit request of 12 June 2019

Please replace [[Hangul]] with [[Korean language|Korean]]. – Illegitimate Barrister (talk • contribs), 22:51, 12 June 2019 (UTC)

I've done this for the time being, as it seemed to be the option that all who commented in the discussion could live with. Fut.Perf. ☼ 07:55, 13 June 2019 (UTC)

Very well. – Illegitimate Barrister (talk • contribs), 02:45, 14 June 2019 (UTC)

Literal translation

Literal translation should probably insert ' on either side per MOS:SINGLE. Template:Literal translation does that as well. Pinging @Rystheguy who added the parameter. – Finnusertop (talk ⋅ contribs) 22:23, 6 April 2021 (UTC)

Why is the hangul parameter required?

If I only want to give a romanization, or hanja, I need to do something clumsy like [[McCune–Reischauer|MR]]: {{transl|ko|Chosŏn}} instead of just {{korean|mr=Chosŏn}}. – Finnusertop (talk ⋅ contribs) 15:12, 19 December 2021 (UTC)

MR and RR Switch

Why is RR before MR, even though MR came before RR? ValenciaThunderbolt (talk) 18:26, 4 December 2022 (UTC)

Very late reply, I'm also fairly neutral on this topic. I very slightly prefer RR to be before MR. Most people don't really know how to read MR unless they're particularly interested in academic-level work on Korean history or North Korea; the average person with interest in Korea (i.e. largely pop culture) will have much higher interaction with RR. I understand your point about chronology of development though. toobigtokale (talk) 14:20, 20 November 2023 (UTC)

Template-protected edit request on 1 June 2023

Please add the |hangul= parameter to the template example at the top of the page, to prevent an error message and render the example correctly. Thanks! Exobiotic 💬 ✒️ 14:47, 1 June 2023 (UTC)

 Not done: hi Matt, the error message is actually left on purpose so editors will readily see what happens when the "hangul" parameter is not included. P.I. Ellsworth , ed. ^{put'er there} 17:18, 1 June 2023 (UTC)

Edit request 8 October 2023

Description of suggested change: Make it so that, in visual editor, when you enable on the "labels" parameter it automatically populates the field with "no". I've seen automatic population in some templates so I think it should be possible? Reasoning I want this: by default, if the labels param isn't specified it's assumed yes anyway; only reason you'd enable the labels param is if you want to say "no" toobigtokale (talk) 17:09, 8 October 2023 (UTC)

 Not done: The documentation, which is where the code that controls the Visual Editor's use of the template lives, is not protected. It is confusing, I know. – Jonesey95 (talk) 22:23, 8 October 2023 (UTC)

Oh, just saw this. That is weird yeah, thanks for the reply. I'll try to figure out how to set it up. Edit: got it! toobigtokale (talk) 05:05, 19 October 2023 (UTC)

IPA suggestion

Hi. Would it be possible to include IPA I'm the Korean template? As it stands, if we want to include Hangul, a literal translation, and IPA transcription, the order will be Hangul, then literal translation (both with this template), then IPA (with the IPA template). Instead, Hangul-IPA-Literal may be a more intuitive ordering, yet this doesn't appear possible with the current setup. I don't know whether this is feasible, but thought it worth mentioning just in case. Thanks. :) JPBarrass (talk) 18:04, 1 February 2024 (UTC)

I think it should be possible; this is a good idea. seefooddiet (talk) 04:13, 1 September 2024 (UTC)

Edit request 13 April 2024

Description of suggested change:

Reinstate the context parameter for hanja vs hancha deprecated by this diff. The cited supporting corresponding discussion is only concerned with deprecating Chosŏn'gŭl and does not actually mention the removal of hancha.

Diff:

−

[[Hanja]]

+

[[Hanja{{!}}{{#switch:{{{context|}}}|north=Hancha|#default=Hanja}}]]

Northern Moonlight 00:34, 13 April 2024 (UTC)

 Done * Pppery * _{it has begun...} 03:13, 15 April 2024 (UTC)