Template:Korean is permanently
protected from editing because it is a
heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by
consensus, editors may use {{
edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's
documentation to add usage notes or
categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
Korea Template‑class | |||||||
|
Writing systems Template‑class | |||||||
|
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)
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)
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'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)
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)
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)
Wow, that was fast. Thanks. Looks to be working. – Illegitimate Barrister, 14:30, 16 September 2015 (UTC)
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)
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)
There is still nesting required to properly render the Hanja. Can a template-editor or administrator remedy this? Compare:
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)
<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)
<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>
<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)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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)
|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){{
edit template-protected}}
template.
Primefac (
talk) 20:09, 28 December 2018 (UTC)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)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace [[Hangul]] with [[Korean language|Korean]]. – Illegitimate Barrister ( talk • contribs), 22:51, 12 June 2019 (UTC)
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)
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)
Why is RR before MR, even though MR came before RR? ValenciaThunderbolt ( talk) 18:26, 4 December 2022 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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)
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)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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{{!}}{{#switch:{{{context|}}}|north=Hancha|#default=Hanja}}]] |
Northern Moonlight 00:34, 13 April 2024 (UTC)
Template:Korean is permanently
protected from editing because it is a
heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by
consensus, editors may use {{
edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's
documentation to add usage notes or
categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
Korea Template‑class | |||||||
|
Writing systems Template‑class | |||||||
|
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)
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)
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'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)
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)
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)
Wow, that was fast. Thanks. Looks to be working. – Illegitimate Barrister, 14:30, 16 September 2015 (UTC)
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)
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)
There is still nesting required to properly render the Hanja. Can a template-editor or administrator remedy this? Compare:
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)
<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)
<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>
<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)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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)
|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){{
edit template-protected}}
template.
Primefac (
talk) 20:09, 28 December 2018 (UTC)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)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace [[Hangul]] with [[Korean language|Korean]]. – Illegitimate Barrister ( talk • contribs), 22:51, 12 June 2019 (UTC)
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)
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)
Why is RR before MR, even though MR came before RR? ValenciaThunderbolt ( talk) 18:26, 4 December 2022 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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)
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)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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{{!}}{{#switch:{{{context|}}}|north=Hancha|#default=Hanja}}]] |
Northern Moonlight 00:34, 13 April 2024 (UTC)