This project page does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:
Korea This page is within the scope of WikiProject Korea, a collaborative effort to build and improve articles related to Korea. All interested editors are invited to join the project and contribute to the discussion. For instructions on how use this banner, please refer to the documentation.KoreaWikipedia:WikiProject KoreaTemplate:WikiProject KoreaKorea-related

Looking for Wikipedia talk: WikiProject Korea in Korean, see 위키프로젝트토론:한국.

Archives

Archive 1 Archive 2 Archive 3 Archive 4 Archive 5 Archive 6 Archive 7 Archive 8 Archive 9 Archive 10 Archive 11 Archive 12 Archive 13 Archive 14 Archive 15 Archive 16 Archive 17 Archive 18 Archive 19 Archive 20 Archive 21 Archive 22 Archive 23 Archive 24 Archive 25 Archive 26

Notice board Archive 1 Notice board Archive 2 Notice board Archive 3 Architecture Archive 1 Arts Archive 1 Biography Archive 1 Cuisine Archive 1 History Archive 1 South Korea Archive 1 South Korean geography Archive 1

This page has archives. Sections older than 15 days may be automatically archived by Lowercase sigmabot III.

(I was wondering if anyone could help find sources for the film The Man with Two Faces (1975 film) 공포의 이중인간 ). The article is up for deletion and it would be great if someone could check for sources in Korean. I am using Google Translate so I'm limited to just what can get translated easily - since the film is older, I have a feeling that if sourcing does exist, it's potentially going to in places I can't use Google Translate. ReaderofthePack(formerly Tokyogirl79) (｡◕‿◕｡) 14:03, 21 November 2024 (UTC)[reply]

Here's some coverage in sources considered reliable by WP:KO/RS

• https://www.kmdb.or.kr/story/74/1663 - review/retrospective on the film
• https://www.kmdb.or.kr/story/10/5427 - discusses the Frankenstein narrative of the film
• https://www.hankookilbo.com/News/Read/201909201405360300 - Article discussing 100 years of Korean cinema, director Lee Yong-min's love of horror films and how this film is the Korean adaptation of Frankenstein
• https://www.newsis.com/view/NISX20140227_0012753607 - Film included in an exhibition by the Korean Film Archive highlighting the best villains in Korean films
• https://www.kmdb.or.kr/story/154/4714 - Same as above, an exhibition on "Korea's greatest villains"
• https://www.yna.co.kr/view/AKR20140227189300005 - Similar coverage as above
• https://www.chosun.com/site/data/html_dir/2014/02/27/2014022704170.html - Similar coverage as above
• https://www.yna.co.kr/view/AKR20061228186000041 - Restoration of the film by Korean Film Archive (among other films) over a three year period, then exhibited by the Archive
• https://www.yna.co.kr/view/AKR20180517077700005 - In this article an author (Kwak Jae-sik) is discussing how he watches old/"failed" films and uses this film for writing inspiration
• https://www.hani.co.kr/arti/culture/movie/181500.html - Another article on the film's restoration by Korean Film Archive
• https://www.seoul.co.kr/news/society/science-news/2018/05/16/20180516023004 - This is one of those "sci-fi is becoming reality" pieces about "memories by injection" - snails are taught sensory responses, then their RNA is extracted, and implanted into other snails, and they find the sensory responses transfer. The article references that it is similar to a plot point in the film where the memories of a corpse are transplanted into the main character.

"공포의 이중인간" translates literally as "The Double Man of Terror" so if you're reading it with machine translation that's probably what the title will show.

Easily enough coverage there, and its inclusion in the Korean Film Archive means it meets criteria #4 in WP:NFO at the very least, and likely #2 as well for being selected as a film that portrays the greatest Korean villains. RachelTensions (talk) 16:26, 21 November 2024 (UTC)[reply]

I'm trying to complete the incomplete list on Korean clans with population data. However, the source for it (source n.2, [1]) is now a permanent deadlink with no archive. I can't find whether there is (or has been) another survey online with an intact url. There's a naver blog post which still has the data([2]), but I assume it still wouldn't be considered a reliable source. -- 00101984hjw (talk) 22:28, 25 November 2024 (UTC)[reply]

Is this it? [3] Idk why documents would be in .exe format but links work and download (I have no idea what they do, I have a Mac)

Link retrieved from Statistics Korea here: [4] RachelTensions (talk) 22:44, 25 November 2024 (UTC)[reply]

The link you found only elaborates on the outlines on the methodology of the census, and not actual census data. Although, it does say here that family clans were surveyed during the census, so I'm hopeful the actual census results would have something useful. Thanks anyways. -- 00101984hjw (talk) 22:54, 25 November 2024 (UTC)[reply]

Here is a direct download link for the bon-gwan report from the 2015 census: 2015년 인구주택총조사보고서 전수조사결과(성씨본관편).pdf. Not sure if anything similar is available for the 2020 census. -- Visviva (talk) 23:00, 25 November 2024 (UTC)[reply]

Thank you -- 00101984hjw (talk) 23:28, 25 November 2024 (UTC)[reply]

One more thing - does anyone here know whether Korean family clan seals are in public domain? It appears that many of them were created during the Japanese colonial era, and I believe some may be designs copyrighted by clan associations. Samhanin created a bunch of those a few years ago and released them as public domain.([5], [6], etc.) - 00101984hjw (talk) 04:32, 27 November 2024 (UTC)[reply]

Think it'll be case-by-case basis. If a seal is provably old enough it's probably in public domain.

Side note, I'm not sure what the copyright situation is for both of those seals. The license given for both of those pictures is that This image of simple geometry is ineligible for copyright and therefore in the public domain, because it consists entirely of information that is common property and contains no original authorship. but especially if the shape involves things like dragons I think they may be pretty distinct designs.

In other words, if the Gimhae Kim clan seal was originally created in a time that still has copyright protection (e.g. if the seal was created in 1970), the Wikimedia Commons license could be wrong and it could actually be a copyright violation.

On the other hand, some other seals could genuinely be pretty simple geometric shapes and be ineligible for copyright. The Gyeongju Kim one may lean closer to that, but I'm not sure. seefooddiet (talk) 04:47, 27 November 2024 (UTC)[reply]

While I'd hate to lose them from Commons, I'm afraid most of them may not be old enough to be in the public domain area ([7]). While I can't find any information on the specific dates of creation, many seals were allegedly created post-2016. Almost all of them seem too contemporary for a design created prior to the 1920s. 00101984hjw (talk) 05:04, 27 November 2024 (UTC)[reply]

Asked someone on discord and they said the Gimhae Kim clan logo is not simple enough. If it was created post-2016 it's a copyvio.

On the other hand, the Gwangsan Kim clan logo is pretty clearly simple enough to be copyright free I think. Same with the Danyang U clan logo. Anything that's just basic shapes or letters in a reasonably standard font is copyright free. seefooddiet (talk) 05:09, 27 November 2024 (UTC)[reply]

Has there been past discussion about why we have a bunch of disambiguation pages in Hangul? Category:Disambiguation pages with Hangul titles Surely they should all be redirected to a romanized version (WP:UE).

Looks like a lot of them are just disambiguating two pages so could probably go anyway if one is a primary topic (WP:ONEOTHER).

Just wanted to see if anyone knows backstory before I start cleaning it up. RachelTensions (talk) 04:12, 28 November 2024 (UTC)[reply]

I don't know of any backstory and would approve of the cleanup. seefooddiet (talk) 05:13, 28 November 2024 (UTC)[reply]

Do these always have a primary topic? Both entries for 둔전역 get a combined 17 views total for the past 30 days, so it's hard to argue that. On the other hand, there is only one valid blue link at 이영애 (disambiguation), so we can probably get rid of that one. I don't know if there's a backstory, but Category:Disambiguation pages with Chinese character titles has existed for 17 years and some of those pages have survived AFD and RFD. ✗plicit 06:53, 28 November 2024 (UTC)[reply]

Even if there isn't a primary topic to allow getting rid of the disambiguation page (as is the case for 둔전역) I'd assume the disambiguation page title should be romanized wherever possible instead of left in hangul... WP:UE "Names not originally in a Latin alphabet, such as Greek, Chinese, or Russian names, must be romanized."
RachelTensions (talk) 07:00, 28 November 2024 (UTC)[reply]

FWIW, I don't think UE strictly applies to these pages, because a disambiguation page is not an article, but rather a navigational aid more closely akin to a soft redirect (this is discussed somewhat in the lede to MOS:DAB, although our nomenclature on this subject is not entirely consistent). But even if it doesn't strictly apply, it's probably still the best way to go (absent strong countervailing considerations, which I don't think exist for most of these).

There have been some fitful past discussions on this point, which seem to have come to more or less random outcomes depending on who showed up. You can find some relevant (but not particularly edifying) background at Wikipedia:WikiProject Disambiguation/CJKV task force (of which I apparently was/am a member, although that was long enough ago that I have no actual memory of it), and at various discussions linked from there and the associated talk page. IMO the particular reasons for maintaining dabs at (some) Han-character titles, which do not generally have a language-neutral transcription, are considerably less compelling for Hangul, and I think moving these Hangul dabs to romanized titles is probably a good idea. (But the messiness of Korean romanization could still create some difficulties.) -- Visviva (talk) 23:27, 28 November 2024 (UTC)[reply]

I agree with all these opinions. seefooddiet (talk) 00:15, 29 November 2024 (UTC)[reply]

I’d agree that the ”must” part of UE probably doesn’t apply but we should romanize whenever possible, though I’m sure there’s one or two that won’t be possible. RachelTensions (talk) 00:22, 29 November 2024 (UTC)[reply]

Yeah some of the ones in that cat require some thought. But I think most will be easy to resolve. seefooddiet (talk) 01:30, 29 November 2024 (UTC)[reply]

Just putting this out there—we should make a Korean calendar converter module. It's clearly possible, per [8]. {{JULIANDAY}} is similar, see also Category:Date-computing templates and Category:Chinese traditional date and time templates. I probably won't get around to programming it in near future but having this module would be a huge help to our community. seefooddiet (talk) 04:25, 3 December 2024 (UTC)[reply]

There is a requested move discussion at Talk:Lee Young-ja (comedian)#Requested move 6 December 2024 that may be of interest to members of this WikiProject. RachelTensions (talk) 14:28, 8 December 2024 (UTC)[reply]

I've had some confusions/doubts about our disambiguation pages for people names.

• Many of our disambigs have non-standard romanizations as their titles, e.g. "Lee Young-ja" should be "Lee Yeong-ja" per WP:KOREANNAME. Are these better served by being more standard romanizations? Seems unintuitive to have ad-hoc romanizations for these.
• Noticed (but can't recall cases rn) where the disambig has a non-standard romanization but people with the same Hangul names don't appear on the disambig page because they use some alternate romanization.
  • Think the lack of enforcement of WP:NCKO#Create alternate title redirects is contributing to this problem.

I think it'd be helpful if we had a drive to really enforce creating redirects for people name pages. Redirects should handle all reasonably conceivable cases (surname order, standard MR, standard RR, WP:KOREANNAME spelling). By doing this, we'd be able to weed out a lot of edge cases (people with same hangul names but no disambiguation pages, people missing from disambig pages, etc). seefooddiet (talk) 16:28, 8 December 2024 (UTC)[reply]

Many of our disambigs have non-standard romanizations as their titles, e.g. "Lee Young-ja" should be "Lee Yeong-ja" per WP:KOREANNAME. Are these better served by being more standard romanizations? Seems unintuitive to have ad-hoc romanizations for these.

The romanization of the disambiguation page title should match whatever the majority of article titles listed on it use. For example, all three articles listed at Lee Young-ja use "Young-ja", not "Yeong-ja", so having the disambiguation page be titled "Lee Yeong-ja" wouldn't make any sense.

Similar situation at Kim Bong-soo, none of the articles listed use the RR form of Bong-soo ("Bong-su"), so listing the disambiguation page at "Kim Bong-su" would be unintuitive.

If there is no majority (ie 2 articles romanize one way, 2 articles romanize another way), only then should we defer to the strict RR form. RachelTensions (talk) 16:43, 8 December 2024 (UTC)[reply]

I agree with this btw; is this based on Wikipedia policy somewhere or is it novel reasoning? Should we put it in WP:NCKO/MOS:KO? seefooddiet (talk) 21:29, 9 December 2024 (UTC)[reply]

Not based on any policy that I'm aware of, just common sense. Idk if it needs to be added to the MOS given that I'm not sure it's ever come up as a problem before. RachelTensions (talk) 21:44, 9 December 2024 (UTC)[reply]

I don't think it's so straightforward; I think there are reasonable arguments to default to systematic spellings given the chronic uncertainties we have around ko people names. Many titles have no real proof of common name or personal preference, and are not systematic. Disambigs that align with these faulty titles reinforce these non-rigorous spellings. That said I think your proposal is fine for dealing with it, I just didn't think it's clear cut. seefooddiet (talk) 22:03, 9 December 2024 (UTC)[reply]

If the article titles themselves are faulty then that's a problem to deal with at the article level. The purpose of the disambiguation page is nothing more than to serve as a landing point for articles with ambiguous names... determining or validating the WP:COMMONNAME romanization of each individual article included within it to determine what the actual name of the disambiguation page should be titled is out of scope. RachelTensions (talk) 22:08, 9 December 2024 (UTC)[reply]

My point about article titles wasn't that disambiguations should resolve them in some way, it was that we have so much uncertainty, frequently changing article titles for people, and plausible variations of name spellings, that defaulting to something systemic in general may be less confusing. Tl;dr felt like my uncertainty was being snubbed when I still think there's reasonable confusion there seefooddiet (talk) 22:17, 9 December 2024 (UTC)[reply]

Funny story about this. Back in 2006 I created a template to assist in creating these redirects, using the then-new Magic Words functionality. It was modernized by @PC78 but subsequently deleted following a TFD in 2022 for having "no clear purpose" (sigh), despite that purpose being clearly documented on the template page. (I was out of the game due to medical issues at the time.) I don't really know if that kind of template-based approach is the way to go, or if it would make more sense to recode it from scratch, or if perhaps a botted or otherwise external-code-assisted approach might make more sense, but I will explore whether I can userfy that ex-template for the community's review.

Regardless of the technical means used, if we're going to return to large-scale creation of alternative-romanization redirects for Korean names, we may want to consider exactly how such redirects should be categorized. IMO the issues around creating and maintaining these redirects are sufficiently Korea-specific that it would be helpful to have one or more specific rcats for them. -- Visviva (talk) 18:12, 8 December 2024 (UTC)[reply]

Update: I have been kindly assisted in restoring the former {{Koralt}} to User:Visviva/Korean alternate name redirects. It is ... definitely a bit of an "echo from another time", which probably helps explain why it was deleted. But I would be interested in getting thoughts on the general concept, and how we might update it (or if it's worthwhile to do so). My initial thoughts are (1) this should probably take as its basic input not precomposed romanizations of each syllable, but the actual jamo or naive RR representations thereof, with standard/predictable romanizations generated by template logic (with an option for the user to add ad-hoc romanizations as well); (2) the output format should be changed to be more suitable for use on some kind of coordination page in project or user space, as the old idea of placing this template on article talk pages is surely a non-starter today; (3) some of the auto-generated forms like "Xxx Yyy zzz" may not be plausible enough to merit redirects; (4) this is missing some obvious value-added features, and should e.g. provide an indication of the current target for bluelinked redirects (thus helping to identify cases where dabs are needed) and preload the suggested redirect page content and edit summary for redlinked redirects. I will work on putting a somewhat more modernized version of this together with those thoughts in mind, happy for any suggestions. -- Visviva (talk) 04:40, 9 December 2024 (UTC)[reply]

This is great, thanks! Some thoughts:

• Bit of a hassle to manually create all these pages; ideally we'd like to create these kinds of redirects for every person with a Korean-language name. Do you think something like WP:BOTARTICLE would work for us? The bot should only create R's when no page exists, otherwise leave alone.
• I think we should keep this manual Latin script input version and make a new Hangul input version; an IP user I know has been working on an automatic romanization module that's nearing ready for use. Would need to be modified to fit this purpose, but it's doable. Not sure when we'll deploy though.
  • E.g. for Syngman Rhee, by using Hangul only, "Syngman" wouldn't be captured as it's ad-hoc.
  • We could also automatically populate common ad-hoc romanizations, e.g. "young" for 영 or "moon' for 문.

I think maybe one possibility is a bot page or something that creates a bunch of redirects given a Hangul and/or Latin script input. Users would probably need some kind of permission to get access to it. If I got access to this once and ran it on every Korean person's page that may be sufficient for a couple of years even; can run it every time there's a backlog.

Anyone else have thoughts on this? seefooddiet (talk) 18:54, 9 December 2024 (UTC)[reply]

Oh actually someone just told me AWB can create redirects.

I may be able to do this without a bot in near future. Regardless a bot would be an easier solution for most people who don't program or use AWB seefooddiet (talk) 19:44, 9 December 2024 (UTC)[reply]

I think a bot would make sense once the redirects are lined up (it's amazing what you can do with SnapLinks or equivalent and a table of links with preloaded content, without any automation tools at all -- but it gets old after the first thousand clicks or so). But IMO probably we would want to have a human in the loop, at least initially, to check (a) that the redirects are actually plausible, and (b) that there aren't any collisions that need to be sorted out. (Regarding automated romanizations: I wish Wiktionary hadn't deleted the old ko-pron template, which had logic I would really rather not have to recreate, but wikt:Module:ko-pron is pretty impressive (but does way more than we need here).) -- Visviva (talk) 02:23, 10 December 2024 (UTC)[reply]

There is a requested move discussion at Talk:The New Six#Requested move 8 December 2024 that may be of interest to members of this WikiProject. 𝙹𝚒𝚢𝚊𝚗 忌炎 (𝚃𝚊𝚕𝚔) 21:52, 8 December 2024 (UTC)[reply]