Template talk:Infobox Korean name

Adding Yale Romanization & New Romanization to Template
There seems to be issues with those favoring the additional romanizations for Korean and those that are citing it as vandalism or problems, e.g. WP:OR. These are recognized systems of romanization of Korean. The New Romanization page seems to be very new, and therefore doesn't have all the references yet. The Yale Romanization of Korean page is brief and also needs improvement. However, this does not mean that the template changes with the additional romanizations are unmerited. Those favoring the exclusion of the Yale Romanization & New Romanization seems to be very biased towards the romanization sponsored by the South Korean government. The Yale Romanization and New Romanization are not sponsored by any governments of both North and South Korea. They are used in academia, and thus provide a more rational organization and representation of Korean morphology.Jkrdsr (talk) 15:47, 14 May 2015 (UTC)


 * The first issue is about the ratio signal/noise. Inflating all these desinfo-boxes is only reducing the proportion of the page that provides some contents. The second issue is about who says who says the rule. As you should know, Korea is divided and there are two governments, leading to this shameful situation where two romanizations have to be used. Describing them as "McCune–Reischauer" and "Revised Romanization" is only misleading. The first one is the BukRom, the romanization decided by North Korea, and the second is the NamRom, the romanization decided by South Korea. Everything else is only an attempt to increase the mess and, who knows, an attempt to pretend that Korean matters are better decided outside of Korea. Pldx1 (talk) 10:26, 20 May 2015 (UTC)

North Korean version
Per the discussion referenced by Jiang above, an alternate template has been created for North Korean topics in which the order of RR and MR is reversed. It is located at Template:Koreanname north image. -- Visviva 02:01, 16 Jan 2005 (UTC)


 * This has since been superseded by this template, using "context=north". -- Visviva 13:04, 22 May 2007 (UTC)

List of Korean name table templates
moved to Naming conventions (Korean)

new templates needed
could someone make a template for koreanruler (with only one name, no birthname)? some ruler articles use the generic koreanname infobox, & hanja should be restored for those with a more specialized template. i feel strongly that hanja should only be included where relevant & helpful to the general english-speaking audience, & hangul should be enough as a local name reference in the vast majority of korea-related articles. it might be a good idea to make a hangul+hanja template to use when necessary, but hanja can always be discussed in the article body in those minority of cases.

i will replace the generic with the ruler template where necessary, though it is a lot of work. since i'm a relative newbie, i'd appreciate someone here quickly making the template, but i will do it myself otherwise. Appleby 05:43, 17 November 2005 (UTC)

please see Naming conventions (Korean) for a list of Korea-related templates, and use its talk pages for discussion. Appleby 18:32, 22 November 2005 (UTC)

Added explicit width to first column
By specifying a width for the first column as well, the second column is able to expand when there is a wider image, so that it's now a minimum of 135 pixels instead of exactly 135 pixels. Also, this modification allows longer captions to wrap at the width of the image. In the previous setup, the whole infobox expanded in width so the caption appeared on one line.

I'm fairly certain that this doesn't have any undesireable side effects. Feel free to revert if it causes problems and then I'll need to make some kind of modifications to Japanese General Government Building, Seoul. Canadiana 04:45, 27 August 2006 (UTC)


 * That worked for Netscape 7.2, but MSIE 6.0 can't handle a cell width and an align=right in the same cell, so I changed some more things, including getting rid of the explicit width in both places and now it works in both Netscape and IE. That's it. I'm not touching in anymore. Canadiana 02:14, 28 August 2006 (UTC)


 * Thanks for your hard work. -- Visviva 04:27, 28 August 2006 (UTC)

Context attribute
Having long been annoyed with the need to maintain two separate name tables, koreanname and koreanname north, I have added a "context" attribute to this template. If the context is set to "north" (or "n" or "nk" or "dprk"), this template will display in the manner of koreanname north. Otherwise, it will display in the usual way. That means that any implementations of Template:Koreanname north can now be replaced with.

This will also allow for flexible implementations in the event that Naming conventions (Korean) is ever changed to provide for additional contexts. It might in fact be wise to add "context=south" to name tables for South Korean topics, in the event that we ever depart from using SK as the default context. -- Visviva 08:58, 13 October 2006 (UTC)

New image syntax
Hi all,

The image/text field specified by can still be used, but should be considered deprecated in favor of a new syntax,  /  /. This will eliminate many of the idiosyncrasies in formatting that have occurred with the old syntax, while still allowing a reasonable degree of customization.

In detail:


 * img specifies the image name, i.e. the ABC in [[Image:ABC]]
 * caption (optional) specifies the caption and alt text.
 * width (optional) specifies the image width in pixels, i.e. the DEF in DEFpx. Default is 250.

Old syntax (most common approach): |image=

New syntax: |img=Foo.jpg |width=width |caption=caption

I think this is an improvement, although I'm not likely to rush out and change the hundreds of existing implementations to the new way. Comments welcome. -- Visviva 08:44, 19 October 2006 (UTC)

Autotagging
I've added some code so that now:
 * If the hangul, hanja and title fields are blank, the template does not display but just adds the article to Category:Lacking Korean text.
 * If the hanja field is set to "!", the template adds the article to Category:Wikipedia articles needing hanja.
 * If the rr or mr fields are left blank, the template adds the article to Category:Wikipedia articles needing romanized Korean.

This should streamline things a bit, since making a request just requires leaving a field blank, and the request is removed automatically as soon as it is filled. I am puzzled by one thing, though; I feel sure that there are some templates out there with blank "rr" and "mr" fields, but there's nothing in Category:Wikipedia articles needing romanized Korean. Are we really so fortunate, or did I mis-code something? -- Visviva 05:14, 11 November 2006 (UTC)


 * There's a couple there now; maybe the DB is just running a little slow today. -- Visviva 05:23, 11 November 2006 (UTC)

Name tag
I noticed how there is Template:Chinese name and Template:Japanese name, both used at the tops of articles where the last name comes first. Is there one for Korean names? Should there be one? SKS2K6 05:59, 3 December 2006 (UTC)


 * Probably. But if we want to use the same title, we need to fix all of these first.  -- Visviva 08:01, 3 December 2006 (UTC)
 * Well, that's done. Say hi to Template:Korean name.  -- Visviva 13:34, 8 December 2006 (UTC)

Italics & color
Couple of thoughts:


 * On Template talk:Koreanname north, which is now superseded by this template, it was suggested that a red title bar would be more suited to the North Korean context. Does this seem reasonable?  It might be nice to have a bit more of a distinction between the two contexts.
 * Should the romanizations be in italics by default? Most transliterations elsewhere on Wikipedia are, and after all they are non-English words.

Responses? -- Visviva 05:17, 12 December 2006 (UTC)


 * In the article text, using italics to display foreign words helps readers to identify them as such. In the box, they appear isolated and are (sort of) explicitly marked as transcriptions, so the typeface doesn't matter. If you prefer italics, go ahead. Wikipeditor 23:39, 19 December 2006 (UTC)
 * I remember having used italics for English words that appear in the box like so:
 * Hangul: 한글
 * Hanja: none (see article)
 * RR: Hangul or Han-geul
 * Wikipeditor 23:45, 19 December 2006 (UTC)

Standardizing name
Are there any objections to a gradual migration of calls to this template to use the alias Template:Infobox Korean name? -- Visviva 05:11, 20 May 2007 (UTC)

Fonts
The fonts in the hanja and hangul fields are showing up strangely when it says "none," such as at Buldak. Badagnani 06:51, 11 June 2007 (UTC)
 * This is due to the use of language-coding, which causes the Roman text to be displayed as if it were Hangul/Hanja. It would be possible to turn this off specifically for the word "none," but I don't think it can be fixed systematically (there's no way for the template to detect the kind of text that is being passed through it).  -- Visviva 08:45, 11 June 2007 (UTC)
 * Marking an English comment as Korean is obviously as wrong as it would be ugly (but correct) to mark romanisations as . Using   seems to work me. Perhaps it is somehow deprecated in terms of HTML/XML syntax as it does not open a new span, but if there is nothing wrong with using it, please tell me. Wikipeditor 11:03, 11 June 2007 (UTC)
 * That's quite an ingenious solution! At any rate, I have now fixed the code so that if "hanja=none" it will render correctly; however, any other English comments will still need a solution such as you suggest.  -- Visviva 12:10, 11 June 2007 (UTC)

New template
I have rewritten this template -. I've also documented what's been changed and included some examples. Please feel free to poke holes and tell me what you think. eDenE 02:33, 17 July 2007 (UTC)

I have replace the template with my version. If you find any problems, please revert back to the old one and let me know the problem. Thanks. eDenE 13:00, 18 July 2007 (UTC)
 * Context North isn't working as it should: it should re-order and rename the language fields (see Kim Jong-il for an example of this). Had to revert to double-check and show you what I mean. Unless, of course, that was an intentional change. PC78 22:51, 18 July 2007 (UTC)
 * Thanks, the context problem has been fixed. I seperated a portion to subpage and forgot to pass the  parameter. Regarding the order, is there any reason to put   first for North Korea?  eDenE  23:11, 18 July 2007 (UTC)
 * I believe that's what they use in NK, so yes. PC78 23:16, 18 July 2007 (UTC)
 * Yes, McCune-Reischauer is the official system in North Korea. I fixed this problem as well. Thank you as usual! eDenE  23:31, 18 July 2007 (UTC)


 * Comment - What was the reason for "rewriting" the template? Also, please restore CCF as the color for the top bar pending actual discussion of this sweeping change, thanks. Badagnani 06:30, 22 July 2007 (UTC)
 * I'd have to agree about the color; the rewrite in general is great, much more streamlined, but the the default color is rather critical to the visual impact of the table (and to distinguishing it clearly from the surrounding text). -- Visviva 09:37, 22 July 2007 (UTC)
 * I've reverted back to the new colours for now, Badagnani's edits meant the table was showing up with no colours at all, which is hardly an improvement. Perhaps a change back to the old purple is in order, but the new colours are absolutely fine by me. For what it's worth, there was some discussion about the rewrite of this template over at WT:KOREA. PC78 15:29, 22 July 2007 (UTC)


 * Comment - No good--restore the original color pending discussion. You may not change colors unilaterally, without discussion. The "new color" is too similar to that used for China-related articles and the old color has been used for quite some time, and is well associated with Korea-related articles. Badagnani 17:24, 22 July 2007 (UTC)
 * Reverted again; the title bar needs some colour, so can you please go back to the purple that was being used previously? PC78 17:47, 22 July 2007 (UTC)
 * Comment - The template is even more confusingly written than before, but, yes, of course, I did go in and replaced the sky blue with the three-letter code for the original color. Why don't you figure out why it didn't work rather than revert my change again and again? Let's please edit constructively, thanks. Badagnani 18:00, 22 July 2007 (UTC)
 * With respect, it's not my job to go around cleaning up after you - if you can't figure out how to revert properly, then perhaps you should leave it to others. Your objections have been noted and can be discussed, though I don't understand why you're being so hostile to the recent updates. I haven't seen any China-related articles that use similar colours to the new version of this template - can you please provide some examples? PC78 18:23, 22 July 2007 (UTC)

Okay! I rewrote the template to reduce its complexity. This was a good change, because I could merge Koreannames into here. I really don't think the new one is more confusing. You might want to compare it with the old Koreannames. Regarding the colour, I proposed this new template on 17th and there were no objections regarding changes. However, there haven't been any discussions or consensus over the new colours ( and  ). Therefore, I'm going to propose colours (including ) and have a poll to decide which colours to use. Thanks for your comments, Badagnani. For now, I changed the default colour back to #CCF. eDenE 18:39, 22 July 2007 (UTC)
 * The new colours are absolutely fine with me, unless it can be demonstrated that there is some kind of problem with using them (besides "I don't like it"). Using red for North Korea has been suggested before (see above), without opposition. Edene: your last edit to the template means that the colour can't be manually changed. Is there some way to fix it?PC78 18:45, 22 July 2007 (UTC)

Comments

 * Strong keep original color for South Korea-related articles. I also feel there's no need to have different colors for South and North Korean articles (as many articles are relevant to both), but if the decision to do so is made, I support keeping the original color for South Korea-related articles. I maintain that it was wrong, without discussion, to unilaterally impose the sky blue color instead of the color we formerly used with no problem. The sky blue is too similar to the light gray-blue color used for China-related articles and over a period of years this light purplish color has become widely associated with Korea-related articles. Badagnani 18:49, 22 July 2007 (UTC)
 * I still don't know what you mean about the colour being too similar to that used by China-related articles. So far as I can tell, they use the same (or similar) light purple that this one uses. Can you please provide some examples? PC78 18:56, 22 July 2007 (UTC)
 * Comment - No, we created the "Chinesename" template modeled exactly on the "Koreanname" template, with the difference that the bar on top went from light purple to light greyish-blue. See Zha cai. So even though those boxes are very similar, the purple - blue distinction has worked really well to distinguish between articles that are primarily Korea-oriented and ones that are primarily China-oriented. Badagnani 18:58, 22 July 2007 (UTC)
 * OK then, I was looking at the template used in Mao Zedong. PC78 19:05, 22 July 2007 (UTC)
 * Comment - I don't know what that template is, but I don't think it's widely used. Right now mostly "Chinese" and "Chinesename" are used, and they both have the greyish-blue color. That one might be a custom-made one just for that article. Badagnani 19:08, 22 July 2007 (UTC)

Let's stop here. I'm going to propose new sets of 3 colours soon and let people decide which colours to use. Because this template is mainly maintained by WikiProject Korea and new colours will be used for other Korea-related templates as well, the poll will be placed in WT:KOREA page. eDenE 19:07, 22 July 2007 (UTC)

Please visit Wikipedia_talk:WikiProject_Korea eDenE  21:18, 22 July 2007 (UTC)

Move to Template:Infobox Korean name?
I'm going to echo Visviva's suggestion above to rename this template. Korean name is a completely different template altogether, so it would make sense to give this template a more distinctive name to avoid confusion. If need be, I believe a bot could be used to update articles with the new template name. Any thoughts? PC78 12:50, 7 August 2007 (UTC)
 * Agree. May help to avoid confusion. Mumun 無文 13:27, 7 August 2007 (UTC)
 * Agree. Confusion avoid to help May. Wikimachine 02:19, 9 August 2007 (UTC)
 * Agree because of all the times I've put Korean name when I meant Koreanname. cab 02:21, 16 August 2007 (UTC)
 * One or two others have agreed with this proposal, and so far there have been no objections. I'll give it a few more days, then proceed with the move. PC78 00:38, 17 August 2007 (UTC)
 * ✅ Done. A bot has been busy updating articles, so everything should now be using the new template name. PC78 21:19, 22 August 2007 (UTC)

A few additions to the template
I've added fields for "othername1" and "othername2" to the infobox, which allow for up to two extra names that aren't covered by any of the other titles. See Hwang Jin-i and Gu, Prince Imperial Hoeun for a few examples of this new feature in action. I'll update the doc when I get around to it! :) PC78 00:38, 17 August 2007 (UTC)

Fonts still showing up strangely
The Latin-alphabet fonts for the "hanja" and "hangul" fields are still showing up in some kind of non-standard font (similar to the Latin fonts that come in CJK packages). Please fix this so they show up in the same (standard) font we have the rest of Wikipedia in. Badagnani 19:45, 1 November 2007 (UTC)

This non-standard font can be seen in the "hanja" field of Sujebi. Badagnani 19:48, 1 November 2007 (UTC)


 * I have no idea what you mean. It looks fine to me. PC78 03:39, 2 November 2007 (UTC)

Whatever you see, the fonts for the "hangul" and "hanja" fields are showing up as Asian-style Latin fonts (see the two screenshots). This should not happen at WP and this bug needs to be corrected promptly. Similar requests at other Asian templates have been ignored for months.



Badagnani 03:51, 2 November 2007 (UTC)


 * Hmmm, it doesn't show up like that on my screen. Are you sure this isn't a browser problem or something? I can post comparison screenshots if need be, but it's late and will have to wait until tommorrow. In any case, I can't see the problem being with this template, especially if other templates are similary affected. PC78 04:05, 2 November 2007 (UTC)

The other template in which this problem occurs is Template:Zh-s. Badagnani 04:14, 2 November 2007 (UTC)

Here's a couple of comparison screenshots from my computer:

Since I don't get the same problem as you, I strongly suspect that this is an external problem. AFAIK there's nothing in the template code that should affect the font style anyway. PC78 13:02, 2 November 2007 (UTC)

Great, it looks fine for you. But it needs to work for everyone without showing up as a strange, non-standard, "Asian-style" font. This needs to be addressed and fixed promptly, not waiting months with no response like the other template. Badagnani 18:21, 2 November 2007 (UTC)


 * This is hardly a matter of supreme importance that "needs to be addressed and fixed promptly". In any case, you're not likely to find a solution here. Perhaps you should try the village pump? PC78 00:18, 3 November 2007 (UTC)

Six months is way too long for something as simple as this to go unaddressed. If you don't have the programming skills to do so, then your negative comment isn't really helpful. Badagnani 03:50, 3 November 2007 (UTC)


 * I've already given you my advice, but if you don't want it then fine. Your trivial concerns are really no problem of mine. Sit here and wait another six months, and see where it gets you. With an attitude like yours it's a wonder anyone should want to help you. PC78 13:34, 3 November 2007 (UTC)

That is an un-Wikipedian comment and attitude. The weirdly showing up font is problematic not just to "me" but to our community and encyclopedia as a whole, as it looks unprofessional. Badagnani (talk) 17:11, 22 March 2008 (UTC)

Sorry for the super late interruption. However, what Badagnani is experiencing is totally normal. That happens because for that specific region of text, the language setting is set to Korean, and your browser tries to use Korean font. Sorry, but this is not a bug and won't be addressed. eDenE 16:25, 22 March 2008 (UTC)

Changes
Can these changes please be explained, preferably before they are made? Many thanks. Badagnani (talk) 08:59, 23 June 2008 (UTC)


 * I'd hoped the modified appearance plus the edit summaries would suffice. Essentially, it's to reduce the space used by the subheadings (lefthand column) so more space is available for the transliterated material (righthand column), the template's "raison d'être". Sardanaphalus (talk) 06:57, 25 June 2008 (UTC)

Seconded. Can we please stop making wholesale changes to the template without prior discussion? The changes made may suit some articles, but not others (eg. Bae) where the text is bunched up to the left leaving too much empty space in the rest of the box. PC78 (talk) 00:44, 27 June 2008 (UTC)

Could...
could someone make one of these for Japanese names and one for Chinese? It would be very useful. 70.20.76.119 (talk) 17:58, 29 June 2008 (UTC)


 * We already have them. Badagnani (talk) 17:59, 29 June 2008 (UTC)


 * Template:Chinese can be seen in use (with its multilingual function) at Tofu. Badagnani (talk) 18:01, 29 June 2008 (UTC)


 * On second thought, maybe there isn't one for Japanese. I can't find one in use anywhere. Sushi, for example, just gives the Japanese in the lead. Badagnani (talk) 18:03, 29 June 2008 (UTC)


 * IIRC, the Japan project prefer usage of the nihongo template over boxes such as this. But if you really wanted to, I think you can use the Chinese template just for Japanese names. PC78 (talk) 18:36, 29 June 2008 (UTC)


 * Good point. Then again, Japanese *people* have their own template; we're primarily using the Chinese one for things that are not people. Badagnani (talk) 23:28, 29 June 2008 (UTC)

Cleanup
The lines (borders) of the box is inconsistent. Some are heavier (the lines are wider) than other. Fix this.68.148.157.170 (talk) 03:34, 29 August 2008 (UTC)


 * Please? I'm not even sure what the problem is. Looks fine to me. PC78 (talk) 14:44, 29 August 2008 (UTC)


 * For a start, the sub-tables created by Infobox Korean name/Nametable all have double borders on the right. Chris Cunningham (not at work) - talk 13:34, 18 July 2009 (UTC)

Conversion to use infobox
I've updated the sandbox to use the infobox base class, inspired by 's work in the fork at template:Infobox Korean name/meta conversion. A comparison of old and new is available at the new test cases page.

I'd synced it, but PC78 has undone that, saying that they new code "looks like it's full of bugs". I'm eager to hear about these bugs. Chris Cunningham (not at work) - talk 13:47, 18 July 2009 (UTC)


 * A bit less wounded pride, perhaps? I'm not causing any drama here; your code contained a bug which was breaking pages, so I reverted - I find that perfectly reasonable and sensible. Whether or not a fix would have been trivial is besides the point; we should iron out any wrinkles in your code before they appear in mainspace, not after. A bit more caution in your editing can avoid unnecessary mistakes like this. PC78 (talk) 14:00, 18 July 2009 (UTC)


 * Correct. When one is urgently reverted and given the impression that one's work is "full of bugs" for a typo which took five seconds to fix when pointed out, it is natural to have "wounded pride". I'm eager for any further bug reports, but as far as I'm concerned this is good to go (again). Chris Cunningham (not at work) - talk 14:04, 18 July 2009 (UTC)


 * A poor choice of words on my part perhaps, but my point still stands. I'll have a good look at your code and see if I can find any further issues. Chances are excellent that this won't be in the next five or ten minutes (later this afternoon, hopefully), so I assume that there is no urgent need for us to move forward with this? PC78 (talk) 14:14, 18 July 2009 (UTC)


 * There's very rarely an urgent need to do things on Wikipedia. :) Take your time. Chris Cunningham (not at work) - talk 14:22, 18 July 2009 (UTC)

Width
While I'm waiting for PC78 to officially unveil his reworking of his template, I made the minor adjustment of changing this template to use to default infobox width of 22em and not 20em. Naturally, PC78 has decided to revert this. As this is a trivial, low-impact conformity change, it should be re-done. Chris Cunningham (not at work) - talk 08:15, 7 August 2009 (UTC)


 * I'd be fine with changing the width if 22em was a constant across all infoboxes, but it isn't; see User:PC78/Sandbox11, where, unless I'm very much mistaken, all templates bar this one have a width of 22em. I'm a little hazy on the reasons for this, but I presume the actual width of a template depends on other CSS stylings? In any case, increasing the width here makes this infobox noticably wider than others. Regarding the more general reworking of this templae, you rather gave me the impression that you were going to have another crack at this – certainly I have done nothing since our last exchange.
 * Another thing: if you wish to address me directly can you please do so on my talk page and not here, where you seem intent on discrediting me. If I revert you then it's for a reason, not because it's how I get my kicks, so if you find my edit summaries an inadequate explanation then please ask me for one and I will duly oblige. PC78 (talk) 12:12, 7 August 2009 (UTC)


 * 22em should work here; it works in the sandbox. For now, I'm going to see what can be done to deploy the sandbox in the immediate future. Once that's done, I'll start chipping away at its style overrides. Chris Cunningham (not at work) - talk 12:58, 7 August 2009 (UTC)


 * 22em works better in the sandbox, but not in the current template; it's a pointless change anyway if the entire code is to be changed. I'm more or less happy with what I wrote in the sandbox, but you described it as an "unparseable mess" and suggested you could do it better – is this no longer the case? PC78 (talk) 13:22, 7 August 2009 (UTC)


 * I don't feel that the perceived need for all of the conditional spaghetti (which is apparently to ensure that different romanization strategies are ordered first and second depending on whether one is talking about ROK or DPRK) is worth the hassle, but in the interests of expediency I'd rather ignore that for now if it works. Chris Cunningham (not at work) - talk 13:42, 7 August 2009 (UTC)

Sizing in fonts and cells
The new design is rather difficult to read; one needs to squint to read the hangul, while hanja is almost impossible to read at this font size; it is just too small to work. As an example, just try to read this: 我愛食龜肉龢倭麵 - as you can see, this line of characters is just a meaningless blabble of blobs at this font size. The interwiki links to Wiktionary make it even worse: 我愛食龜肉龢倭麵 - and more difficult to read. Since there is no simplified form of Hanja (only Traditional forms), this is certainly the case in many Korean personal names which use the traditional variants of characters, with many being very difficult to read on a screen at such a small font size. Just take a look at Seo Hui, Kim Il-sung, Shin Hye Sung and Choe Bu; you'll see how difficult it is to read the Hanja names. I would like to propose a revert to the old style; although one might argue that it tidies up articles by reducing the space taken up by the template, it aesthetically looks plain ugly to have almost-illegible characters, and perhaps does more ill than benefit on the respective articles. --  李博杰   | —Talk contribs email 13:31, 15 August 2009 (UTC)


 * I thought this may be an issue, though I was unaware that the template had been changed until your post. I have increased the font size for the hangul & hanja fields so that they match the older version of the template, so this should alleviate your concern. Please let me know if you have any further problems with the new design. Regards. PC78 (talk) 14:48, 15 August 2009 (UTC)
 * I was going to say the same thing with what Benlisquare said. PC78's change looks nice, so thank you everyone for caring the concern.--Caspian blue 14:54, 15 August 2009 (UTC)


 * It reads quite well on Mac. Perhaps it's time to make a switch from Windows? Colipon+ (Talk) 18:22, 18 August 2009 (UTC)

International Phonetic Alphabet
Would there be any objections to adding this alongside the existing parameters? Naturally it would be strictly optional, but it would be a worthwhile addition IMO. See example to the right. PC78 (talk) 00:03, 22 August 2009 (UTC)

I agree with this. Lpook at for example Jikji and its discussion page. J hastwo transcripton form to Hungarian and Persian also. It would make translations easier and more properly. --Ksanyi (talk) 09:24, 20 November 2009 (UTC)

Ho is not a pen name. Both ho and ja are courtesy names.
In traditional Northeast Asia, there was not the term for "pen name," but now translated as "필명/筆名".

Both ho and ja are courtesy names. Of course, they are slightly different. --Yes0song (talk) 05:43, 19 August 2011 (UTC)

Literal meaning
What do people link about adding a "Literal meaning" field to the infobox, similar to the Template:Infobox Chinese? Seems like it would be useful in many situations and would eliminate the need to write the hangul again in the body of the article to explain the literal meaning.

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, 12:30, 16 September 2015 (UTC)


 * There exists two authoritative bodies for the Romanization of textes written using the Korean alphabet. One is the government of North Korea. Another is the government of South Korea. Alternate wording: One is the government of South Korea. Another is the government of North Korea. No other authoritative bodies are existing. The practice here is to provide both Romanizations, putting forward the BukRom when dealing with topics that are "more North" while putting forward the NamRom when dealing with topics that are "more South". This is about how we [write today] Korean, not about how we write [today Korean(s)].
 * If something must be criticized, it's the programming of the desinfobox, that results in describing the Han River as

한강 Revised Romanization 	Han-gang McCune–Reischauer    	Han'gang
 * i.e. using less space for the content (Han-gang/Han'gang) and more for some pompous labels (Revised Romanization 	/ McCune–Reischauer). And, as a second bug, the size of the desinfobox has been enlarged to 22em instead of the more modest previous value (20em) in an attempt to avoid some disgracious line breaks. What would be the result of a third context ? Writing the BukRom and the NamRom at the same place (no one being upper than the other) ?  Or providing a 44em desinfobox, with a North above South column and a South above North column ?
 * Side remark: Using 'Dynasty' for describing the Joseon Period and/or the Joseon Kingdom shows some lack of neutrality: from ministers to slaves all the non-dynastic people were nevertheless human beings, rightful objects of study, and actual history makers.

Pldx1 (talk) 16:58, 16 September 2015 (UTC)

Hanja display incorrectly
In my browser, the Hanja display incorrectly in this template, as well as in Template:Korean and Template:Infobox settlement. When I insert Template:Lang-ko into the template, the Hanja display correctly. Is the problem only at my end, and if not, can it be fixed? Ardalazzagal (talk) 12:53, 18 August 2016 (UTC)

pen name
Hi there, there is an entry called art name that is for the Korean 호. I think the pen name section should be renamed or at least linked to this entry. So that the reader would not think it is just a normal pen name. I will wait for a few days before doings it. Please leave a comment if you have any suggestions. Hahahaha哈 (talk) 03:24, 29 August 2016 (UTC)

Meaning
Could somebody add a field for the meaning of the name to this template? Abductive (reasoning) 07:22, 10 August 2017 (UTC)
 * Template:Infobox name module has a translation box for that. CherryPie94 (talk) 14:31, 22 December 2017 (UTC)

Template-protected edit request on 23 December 2018
Please add to the top of this page (Infobox Korean name), as it is currently being discussed for a merger with Infobox Chinese. DanielleTH (Say hi!) 22:15, 23 December 2018 (UTC)
 * Done. &#123;&#123;3x&#124;p&#125;&#125;ery (talk) 22:24, 23 December 2018 (UTC)

Remove the "context" parameter?
Cross-link to a discussion I posted at Wikipedia talk:Naming conventions (Korean) Please discuss there. – Fut.Perf. ☼ 06:52, 1 May 2019 (UTC)

Title bolding
Title should be bolded just like every other infobox. Opencooper (talk) 14:49, 22 April 2021 (UTC)

Agreed that it should be bolded. In this documentation example, Korean name, Pen name, Birth name, etc is already bolded. Hddty (talk) 05:31, 8 November 2022 (UTC)
 * ✅.  P.I. Ellsworth &thinsp;, ed.  put'r there 06:03, 8 November 2022 (UTC)

Template-protected edit request on 5 July 2023
unnecessary keys 'neutral' and 'Neutral'

Desb42 (talk) 11:22, 5 July 2023 (UTC)


 * .  P.I. Ellsworth &thinsp;, ed.  put'er there 16:34, 5 July 2023 (UTC)

"Pen name" or "Art name"
The term for ho (호) in the infobox currently displays "Pen name" but links to art name. Why not just display "art name" too?

My opinion: I don't like the term "pen name" for ho, as "pen name" also corresponds to pilmyeong (필명), which does represent a significant chunk of what hos are, but not everything. They can be names for politicians, for students, for artists, for teachers, the names of buildings to represent people, etc. What's more, since there are separate articles for pen name and art name that have different scopes, using the term interchangably leads to confusion about what article to link for ho.

Admittedly I don't know what RS's commonly translate the term as, although I wouldn't be surprised if it was "pen name"... Although I don't like some common translations for things anyway. toobigtokale (talk) 18:18, 13 September 2023 (UTC)


 * I'm seeing this is unopposed; I may go ahead and make this change. If anyone disagrees, please feel free to revert and discuss here. Edit: wait I can't it's protected. toobigtokale (talk) 20:19, 21 September 2023 (UTC)

Edit request 21 September 2023
Description of suggested change: Change "pen name" to "art name" in display

Reason: see section Template talk:Infobox Korean name

Diff: toobigtokale (talk) 20:24, 21 September 2023 (UTC)
 * ✅ * Pppery * it has begun... 02:25, 22 September 2023 (UTC)
 * It looks to me like it's lower case; should be capitalized like the others toobigtokale (talk) 03:19, 22 September 2023 (UTC)
 * Fixed that. * Pppery * it has begun... 04:45, 22 September 2023 (UTC)
 * Thank you! 🙏🏻 toobigtokale (talk) 05:31, 22 September 2023 (UTC)

Edit request 28 September 2023
Description of suggested change:Investigate "image" vs "img" behavior

For some reason, when I use the "image=" param, the image doesn't show up. It only works when I use "img=". I don't think this is expected behavior, as the default param and documentation gives "image". Can someone investigate why this is happening? toobigtokale (talk) 11:25, 28 September 2023 (UTC)
 * Please see &mdash; Martin (MSGJ · talk) 12:07, 28 September 2023 (UTC)

Edit request 8 October 2023
Description of suggested change: Add ability to have either or both North Korean or South Korean name (maybe differentiated by "chosungul=", "nkhanja=", and "nkmr=" etc). I'm not sure if we even need Revised Romanization of Korean (RR) for North Korea, but maybe won't hurt to add it anyway? Make it so that at least one of the NK or SK name param is required. (i.e. just NK name is ok, and just SK name is ok). Also, I know it's less than ideal to give preference to the SK terms as default, but North Korean usage is much less common anyway, partially due to less info about it known by the outside and partially due to smaller population toobigtokale (talk) 16:22, 8 October 2023 (UTC)
 * Red information icon with gradient background.svg Not done for now: Please add your suggested code to Template:Infobox Korean name/sandbox and then reactivate the request. There should also be a consensus for the change you want to make, so it might be a good idea to drop a note at Wikipedia talk:WikiProject Korea to get their opinion. I think it would also be OK to treat the lack of response here as a consensus as well, so it's your call. — Mr. Stradivarius  ♪ talk ♪ 13:58, 28 October 2023 (UTC)

Edit request 8 October 2023_2
Description of suggested change: When infobox is made a child of another infobox, make the headers transparent by default. This is popularly done for many people, and is usually accomplished by setting "transparent" as the header color, but I'd prefer it if we standardized the practice by just making it default. Please discuss if disagree, I just want to get the ball rolling on a discussion toobigtokale (talk) 17:21, 8 October 2023 (UTC)
 * Red information icon with gradient background.svg Not done for now: Please add your suggested code at Template:Infobox Korean name/sandbox and reactivate the request. As above, it may also be a good idea to leave a note at Wikipedia talk:WikiProject Korea to get their opinion about your suggested change. Best — Mr. Stradivarius  ♪ talk ♪ 14:00, 28 October 2023 (UTC)

Edit request 8 October 2023_3
Description of suggested change: update template documentation description for all of the "ho" parameters "pen name" -> "art name", as per recent edit

Diff: toobigtokale (talk) 17:27, 8 October 2023 (UTC)


 * Full-protection-shackle-no-text.svg Not done: is usually not required for edits to the documentation or categories of templates using a documentation subpage. Use the 'edit' link at the top of the green "Template documentation" box to edit the documentation subpage.  P.I. Ellsworth &thinsp;,  ed.  put'er there 20:30, 8 October 2023 (UTC)
 * Whoops; thanks for the reply, I just made the change. toobigtokale (talk) 22:10, 9 October 2023 (UTC)
 * 'Sokay, pleasure to help, and thank you for your edits!  P.I. Ellsworth &thinsp;, ed.  put'er there 23:56, 9 October 2023 (UTC)