Wikipedia talk:WikiProject Korea

Proposed changes to disambiguation pages for Korean given names

I would like to remove these from disambiguation pages for Korean given names (Ha-yoon, Seo-jun, etc.):

1. Meaning, etymology, and gender
   1. Korean given names are usually made-up words. That is, a certain name written in hangul usually does not have a "fixed" meaning, etymology, gender, etc.
   2. For gender, I don't deny that there is some tendency, but there is no definite answer.
2. Mentions of List of Hanja for Use in Personal Names (인명용 한자표)
   1. This is a prescriptive list, not a descriptive list.
      1. The list shows what characters are currently allowed to be used in newly registered names (newly born babies and legal name changes). It does not show what are actually used in names. Some characters in the list may not actually be used in any name.
      2. The list was first introduced on April 1, 1991. Before that date, there was no restriction on registering hanja names. So hanja names that were registered before that date may contain characters not even in the list.
   2. The list sometimes grows (initially about 2800 characters, now more than 9300). The Supreme Court of South Korea sometimes adds characters to the list. It is not really possible to update each disambiguation page every time the list gets updated.
3. Mentions of specific hanja (single character or combination of two or more characters; see Jin-woo#Hanja and Yeo-jin#Hanja for examples; this also includes the hanja parameter of Template:Infobox Korean name)
   1. There are literally tens or hundreds of possible hanja forms for a single hangul name. Listing one or some hanja forms can give the false impression that those forms are somehow more "representative" than other hanja forms.

172.56.232.40 (talk) 06:53, 19 July 2025 (UTC)

No opinions on #2 and #3, but #1 is only a problem because people are getting away with adding unsourced content or badly sourced content such as from baby naming websites. The language of how meaning and etymology is described is often in need of change and sometimes removal; however there should be nothing stopping information on the subjects being added if it can be well-sourced. Same with gender prevalence. There is a difference between saying "____ is a male name" and "82.3% of people named ____ are male". Ike Lek (talk) 07:08, 19 July 2025 (UTC)

About meaning and etymology:

As I said, Korean given names are usually made-up words. That is, they are usually semantically opaque. Usually, the only person who knows the real meaning and real etymology of a certain name is the creator of that name (and additionally a very few people who heard (and still remember) the meaning and etymology from that creator).

Even a single hangul name can have multiple meanings and etymologies (and again, the creator of a name is the only person who truly knows which meaning and etymology are intended).

(Koreans do not have culturally common names like John or Muhammad.)

So the meaning and etymology of a name should not be included.

About gender:

Okay, then I guess that can be included as long as reliable statistics are cited. However, instead of directly defining the gender of a name (like "X is a male name"), it should be in the format like "among people named X, y% is male and z% is female" (while citing reliable statistics, of course).

172.56.232.40 (talk) 09:43, 20 July 2025 (UTC)

Maybe etymology should not be the norm for Korean given names unless there is a specific reason to include it. As far as hanja inclusion goes, I do think it is important for English-speaking audiences to be told that a name has tons of potential spellings in Korean, when it may only have a couple in English. Ike Lek (talk) 10:46, 20 July 2025 (UTC)

Regarding hanja, I think "different depending on hanja" is sufficient. This already exists on many pages. 172.56.232.66 (talk) 13:49, 23 July 2025 (UTC)

For #1, I don't think a blanket restriction is appropriate. Some names will have clearer meanings, etymologies, and genders than others. Like "Ha-neul" has a clear meaning and etymology; excluding it there would be strange. I don't even think we need to define a policy for this; the policy should be that whatever is appropriately sourceable and correct should go in. That's just the general policy for info on Wikipedia. If gender, etymology, or meaning are not clear then claims about it should be either excluded or made conservatively with sources.

For #2, (edit: deleted an idea I don't agree with anymore) how is this list typically used?

For #3, I agree with you on this. There are way too many possible combinations and they're not particularly encyclopedic or useful. This is a bit similar to like listing possible combinations of letters in English, e.g. "ae" or "al". grapesurgeon (seefooddiet) (talk) 17:07, 19 July 2025 (UTC)

For #1: Then do the names 미정, 수영, 시연, 여진, 연석, 지연, 현미, etc. mean "undecided", "swimming", "demonstration", "aftershock", "curb", "delay", "brown rice", etc. respectively? If one does not agree with these, then how can one be so sure that the name 하늘 always means "sky"?

For #2: As I wrote above. Basically, this is how that list is used: "if you want to register a hanja name right at this moment, you must pick from these". 172.56.232.40 (talk) 10:05, 20 July 2025 (UTC)

The answer for #1 is that unlike the other names mentioned, 하늘 is a pure Korean word & name, meaning it actually has an etymology as it isn't a bunch of probabilities of various different hanja characters. This textbook probably explains it better. [1] In other words, they're pretty semantically transparent. I don't see a reason to proscribe including etymologies, as most of the Hanja-character based name articles don't assign them an etymology as it would vary for every different combination. The example Seo-jun article that you gave states that the meaning of the name is "Different depending on Hanja". Pure Korean names such as Bit-na or Da-som actually do have etymology and meaning and those usually are included in the article. #1 seems to be a bad solution for a problem that doesn't seem to exist, and would create a new problem of not allowing to show the etymology and meaning of pure Korean names. ⁂CountHacker (talk) 07:07, 23 July 2025 (UTC)

In fact, it is possible to create a name 하늘 which does not mean "sky". For example,

• "always summer" (하 (hanja 夏; "summer") + 늘 (native Korean; "always"))
• "always the lowest" (하 (下; "lowest") + 늘 ("always")) – which is quite the opposite of "sky"

And it is possible to create a name 다솜 which means "all cotton" (다 all + 솜 cotton) or "lots of cotton" (다(多) lots of + 솜 cotton).

Creating names like the above is not prohibited. Any name can be individually crafted. So even native Korean names (or names that "look like" native Korean names) do not have a "fixed" meaning and etymology.

I don't see a reason to proscribe including etymologies, as most of the Hanja-character based name articles don't assign them an etymology & #1 seems to be a bad solution for a problem that doesn't seem to exist

Some pages do try to give possible meanings and etymologies, like Jin-woo#Hanja and Yeo-jin#Hanja. 172.56.232.66 (talk) 14:14, 23 July 2025 (UTC)

Is it possible to create a random, nonsensical Hanja-character based name that resembles a pure Korean name? Sure. But that wouldn't change the etymology of the original name. Just like how if one named a baby boy Derrick after a derrick, the lifting device, or named a Dick after a penis, it won't change the etymology of those names. Pure Korean names existed before Koreans even adopted hangul or hanja, meaning that their etymologies can't come from a hanja-character based name.

For the second part, I don't have a huge problem with showing examples of common hanja combinations for a name as long as its not defined as the sole fixed meaning for that name. Those articles show that those are only possible ways to write those names in hanja. ⁂CountHacker (talk) 17:22, 23 July 2025 (UTC)

Not necessarily "random, nonsensical" (for example, "always the lowest" can be "always be humble/modest"). And it does not really matter even if it is "random, nonsensical".

How do you know for sure that the intended meaning (or one of the intended meanings) of a name written as 하늘 in hangul is always "sky"? What if someone created a name 하늘 but never intended "sky"? Is there a requirement for a name written as 하늘 in hangul to always have the same meaning and etymology as the common noun spelled the same? No, there is no such requirement.

Given that any name can be individually crafted, we should avoid making assumptions (that is, providing (or trying to provide) a certain meaning or etymology for a certain name should be avoided).

For the second part, I am against mentioning any specific hanja form. As I wrote above (#3), listing one or some hanja forms can give the false impression that those forms are somehow more "representative" than other hanja forms. 172.56.232.95 (talk) 04:10, 24 July 2025 (UTC)

The original meaning behind the pure Korean names is not going to change, as they originated before the hanja-character names made to resemble the pure Korean names. It does not matter if someone later creates a name based on the original pure Korean name that has a different meaning. By that logic if a Korean creates a new name of 安儺, or Anna, made to resemble the Western name of the same name, would the original meaning for the Western name of Anna disappear? Should we get rid of all etymology sections for all personal names, since a Korean could create a hanja name based on that name that now has a different meaning from the original? ⁂CountHacker (talk) 06:26, 24 July 2025 (UTC)

So you are still assuming that a name must have the same meaning and etymology as a common noun if the name and the common noun are written the same (and you are selectively applying this when the common noun is a native Korean word). As I said, there is no such requirement. You need to stop making assumptions.

if a Korean creates a new name of 安儺, or Anna, made to resemble the Western name of the same name, would the original meaning for the Western name of Anna disappear?

Again, we don't know if the creator intended the Western name or not. You need to stop making assumptions.

Should we get rid of all etymology sections for all personal names

Not necessarily. But regarding Korean given names, we should avoid making assumptions. 172.56.232.166 (talk) 16:06, 24 July 2025 (UTC)

I agree and disagree with both of you.

1. I think IP is right that 하늘 and similar names can be given new meanings, even if the process of doing so is silly. But that doesn't stop people from doing silly stuff; see kira kira name.
2. However, I partly agree with CountHacker that the total exclusion of the original and most likely interpretation of a name seems odd. If 99% of like 1000 RS widely attribute some meaning to a name, what argument is there for not mentioning the meaning at all in the article? I don't think consistency with other articles where names have more fluid meanings is an adequate reason.

Tl;dr I stick with my original opinion for #1. grapesurgeon (seefooddiet) (talk) 16:55, 24 July 2025 (UTC)

I kept thinking about this, and would like to revise my removal proposal above:

1. Meaning, etymology, and gender
   1. Meaning and etymology: Remove for now. But if lots of reliable sources widely attribute some meaning to a name, then that can be (re-)added in the format such as "it is commonly believed/perceived that the name A means B" (while citing lots of reliable sources). Do not exclude the "it is commonly believed/perceived that" part.
   2. Gender: Remove for now. But if reliable statistics are cited, then percentages can be (re-)added in the format such as "among people named X, y% is male and z% is female" (while citing reliable statistics). In any case, the gender of a name should not be directly defined (i.e. should not say something like "X is a masculine name").
2. Mentions of List of Hanja for Use in Personal Names (인명용 한자표): Remove and cannot be (re-)added.
3. Mentions of specific hanja: Remove and cannot be (re-)added.

172.56.232.40 (talk) 15:49, 26 July 2025 (UTC)

Any comments on this? If not, I will carry this out someday. 172.56.232.66 (talk) 22:06, 5 August 2025 (UTC)

1.1 I think blanket removal first is strange; I think you should instead be allowed to boldly remove if unsourced or poorly supported by sources, but that's already standard Wikipedia policy. Removing in 100% of cases and slowly adding back is not really needed. Also I think the wording "commonly believed" is unnecessarily strict, can communicate similar idea in different ways.

1.2 Same as above on removal and wording. I think asking for statistics and prohibiting "x is a masculine name" is good though.

2 I think is fine

3 I think is fine grapesurgeon (seefooddiet) (talk) 22:11, 5 August 2025 (UTC)

About #3, are there any cases when a specific hanja choice is by far the most common (say, used more than 70% of the time) for a given name? Ike Lek (talk) 22:21, 5 August 2025 (UTC)

Hm actually you're right, could be same issue as name meaning interpretation.

I'm not sure if statistics are gathered for that. If they are or other methods can be used to determine widespread Hanja use, then would make sense to show Hanja. grapesurgeon (seefooddiet) (talk) 22:29, 5 August 2025 (UTC)

1.1. & 1.2. I don't think disambiguation pages for Korean given names are currently well cited anyway. And I want to make the wording descriptive, so I proposed the wording "commonly believed" (it does not have to be exactly this; it can be any wording that shows this is descriptive).

3. I don't think there are statistics or methods that can be used to determine widespread hanja use. Unless someone can actually provide such statistics or methods, I am not sure if there is a need to allow mentions of specific hanja. 172.56.55.222 (talk) 03:54, 17 August 2025 (UTC)

I will go with the following.

1. Meaning, etymology, and gender
   1. Meaning and etymology: Should show that lots of reliable sources widely attribute some meaning to a name. The wording for the meaning and etymology of a name should be descriptive (e.g. "it is commonly believed/perceived that the name A means B"; should not just say "the name A means B").
   2. Gender: Should cite reliable statistics. The wording for the gender of a name should be descriptive (e.g. "among people named X, y% is male and z% is female"; should not say something like "X is a masculine name").
2. Mentions of List of Hanja for Use in Personal Names (인명용 한자표): Remove and cannot be (re-)added.
3. Mentions of specific hanja: Remove and cannot be (re-)added.
   • Theoretically, there could be statistics or methods that can be used to determine widespread hanja use. However, unless someone can actually provide such statistics or methods, I don't think there is a need to allow mentions of specific hanja.

172.56.55.62 (talk) 22:21, 31 August 2025 (UTC)

Oh, it looks like I did not directly say something about categories. To be clear, The wording for the gender of a name should be descriptive ([...] should not say something like "X is a masculine name"). also applies to categories (i.e. no gendered categories for Korean given names).

Reasons:

1. This is very subjective. Even if there are reliable gender statistics for a certain name, what is the "threshold" of defining the gender (masculine/feminine/unisex)? And Wikipedia should not be the one setting such a threshold.
2. Even if a certain name is almost exclusively used by a single gender according to reliable statistics, that does not mean the other gender cannot use that name.

172.56.55.37 (talk) 18:41, 21 September 2025 (UTC)

Free books on Korea

WP:KO/RS#Books

I've listed out a bunch of places to find books on Korea, often for free. If you haven't already, I recommend you request access to WP:LIBRARY so you can access many of these books.

They're about pretty much everything you can imagine, including modern pop culture, film, theater, science, politics, and technology. Even saw one about soil quality. grapesurgeon (seefooddiet) (talk) 04:30, 10 September 2025 (UTC)

Discussion re: Copyright of S. Korean state media at Commons

Hi, just leaving this discussion from Commons in case it helps in the future. c:Commons:Village_pump/Copyright#South_Korean_state_media_may_be_free_content_now_but_login_required Reepy1 (talk) 13:10, 14 September 2025 (UTC)

Thank you for sharing! grapesurgeon (seefooddiet) (talk) 13:22, 14 September 2025 (UTC)

South Korea infobox

Hi folks, I've made some suggestions for slimming down the South Korea infobox at Talk:South Korea#Bloated infobox. I'd be okay with nuking all the stuff I've listed, but I don't know if you all watch that page, so I'd like to discuss first in case others have opinions. Toadspike [Talk] 23:42, 16 September 2025 (UTC)

Discord channel

Hello, thinking of creating a channel #wpkorea on the Wikimedia WP:DISCORD. To do that, we need consensus from the WikiProject that there would be interest in such a channel.

We currently have a thread Korea-related articles under #english-wikipedia, but threads are harder to find for people less familiar with the server and with Discord.

Please voice opinions here. grapesurgeon (seefooddiet) (talk) 02:52, 19 September 2025 (UTC)

• As a WikiProject Korea member who is active on the Wikimedia Discord, Absolutely Support. ~delta ^{(talk • cont)} 03:11, 19 September 2025 (UTC)
• I would also support, noting any WikiProject decisions still have to take place here. CMD (talk) 04:07, 19 September 2025 (UTC)
• Support. IMO thread feels mature enough - 00101984hjw (talk) 02:55, 20 September 2025 (UTC)
• More votes are needed before a channel is made. If you have opinions please voice them. grapesurgeon (seefooddiet) (talk) 16:16, 25 September 2025 (UTC)

Support - the thread is quite useful and active, and I think it makes sense to branch it into a channel. ArtemisiaGentileschiFan (talk) 16:44, 25 September 2025 (UTC)

I'm not that closely related to this wikiproject, but I'd also support such a channel. – Epicgenius (talk) 02:23, 29 September 2025 (UTC)

Support Very active thread. Ca ^{talk to me!} 08:56, 2 October 2025 (UTC)

Requested move at Talk:Hangul orthography#Requested move 23 September 2025

There is a requested move discussion at Talk:Hangul orthography#Requested move 23 September 2025 that may be of interest to members of this WikiProject. grapesurgeon (seefooddiet) (talk) 20:43, 25 September 2025 (UTC)

Park Gwang-hyun and Park Kwang-hyun (film director)

Looks like they are different people, but both pages use the same photo. 172.58.210.248 (talk) 00:53, 4 October 2025 (UTC)

film director one was wrong grapesurgeon (seefooddiet) (talk) 01:18, 4 October 2025 (UTC)

Title of Han conquest of Gojoseon

1. Per the title and most recent RM at Old Chosŏn, this title should also be changed to use "Old Chosŏn" instead of Gojoseon for consistency. May want to check other titles for the same issue.
2. I noticed in the infobox of Old Chosŏn that the Han conquest of Gojoseon is called Gojoseon–Han War. It seems the article has been moved several times but never had an RM. Someone might want to do a source analysis and figure out what the title should be.

Apologies for just dropping these here instead of doing them myself; I'm not sure I have the knowledge needed to deal with them. Hoping someone here takes interest. Toadspike [Talk] 10:03, 4 October 2025 (UTC)

Help requested with Draft:List of K-pop films

I created Draft:List of K-pop films during an RFD discussion at: Wikipedia:Redirects for discussion/Log/2025 September 9#Kpop film. This was briefly published and then draftified due to lack of citations and questions of notability. I would like to invite anyone interested to contribute to the draft if you feel it may be notable and worthy of publication here. This is not my usual area and I created this to be helpful and move the RfD discussion along. I thought there might be sources linking the rise of these films to Korean Wave phenomenon and K-pop's popularity but I was unable to find any without veering into OR/SYNTH territory. --MYCETEAE 🍄‍🟫—talk 20:48, 4 October 2025 (UTC)

@RachelTensions someone said "kpop", you're up. Toadspike [Talk] 23:43, 4 October 2025 (UTC)