Template talk:Korean

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

message: 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)
thread_title:  Limitations of this template 

message: 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)
replies: text: 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)
thread_title:  Problem with spaces 

message: 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 ( 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)
thread_title:  Context parameter 

message: There was a bug when using the template on ";" header lines, for example like this:
;
;
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)
thread_title:  Problem when using in headers 

message: 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)
replies: text: 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)
replies: text: Thanks. Much appreciated! – Illegitimate Barrister, 14:04, 27 August 2015 (UTC)
replies: text: Could you possibly add it to "Template:Infobox Korean name" as well? – Illegitimate Barrister, 12:29, 16 September 2015 (UTC)
replies: text: 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)
thread_title:  Third context syntax/parameter 

message: 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)
thread_title:  Template Hangugeo 

message: Template:Korean requires parameter.
should be
Template:Korean requires parameter.
I don't have rights to fix it. Could someone who does... do so? pauli133 (talk) 03:05, 15 May 2018 (UTC)
replies: text: . Primefac (talk) 11:28, 15 May 2018 (UTC)
thread_title:  misnested tag causing lint error 

message: 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: " and provide equivalent functionality. This would be just for convenience. Daviddwd (talk) 03:48, 26 December 2018 (UTC)
replies: text: Hi David. I'm wondering if you were aware of the already available  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  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)

text: Not done: please establish a consensus for this alteration before using the  template. Primefac (talk) 20:09, 28 December 2018 (UTC)
thread_title:  Template-protected edit request on 26 December 2018 

message: 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)
replies: text: 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)
replies: text: 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)
replies: text:  Let's please keep the discussion in one place, at Wikipedia talk:Naming conventions (Korean). Fut.Perf. ☼ 06:14, 13 June 2019 (UTC)
thread_title:  Remove the "context" parameter? 

message: Please replace Hangul with Korean. – Illegitimate Barrister (talk • contribs), 22:51, 12 June 2019 (UTC)
replies: text: 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)
replies: text: Very well. – Illegitimate Barrister (talk • contribs), 02:45, 14 June 2019 (UTC)
thread_title:  Template-protected edit request of 12 June 2019 

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

message: If I only want to give a romanization, or hanja, I need to do something clumsy like MR:  instead of just . – Finnusertop (talk ⋅ contribs) 15:12, 19 December 2021 (UTC)
thread_title:  Why is the hangul parameter required? 

message: Why is RR before MR, even though MR came before RR? ValenciaThunderbolt (talk) 18:26, 4 December 2022 (UTC)
replies: text: 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)
thread_title:  MR and RR Switch 

message: Please add the  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)
replies: text: 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)
thread_title:  Template-protected edit request on 1 June 2023 

message: 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)
replies: text: 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)
replies: text: 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)
thread_title:  Edit request 8 October 2023 

message: 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)
thread_title:  IPA suggestion 

message: Description of suggested change:
Reinstate the context parameter for  vs  deprecated by this diff. The cited supporting corresponding discussion is only concerned with deprecating  and does not actually mention the removal of .
Diff:
]]
}}
Northern Moonlight 00:34, 13 April 2024 (UTC)
replies: text: * Pppery * it has begun... 03:13, 15 April 2024 (UTC)
thread_title:  Edit request 13 April 2024