Hi grapesurgeon, I noticed you made some helpful edits on some earlier articles I wrote about South Korean professional golfers and I was wondering if you could lend a hand?
I've made a few more for the Women in Red project, and as you were so great correcting the Korean text, I was wondering if you could check these new ones for any mistakes with the translations? I'd really appreciate it.
The articles are Lee So-mi, Kim Su-ji (golfer), Hwang You-min, and Yoo Hyun-jo.
Nice work! Only notable thing I saw is use of Maeil Business Newspaper's English articles; those articles were translated using unvetted machine translation, and are thus unreliable. See WP:KO/RS for more. grapesurgeon (seefooddiet) (talk) 22:13, 15 June 2025 (UTC)[reply]
Edits that you made to infoboxes on many Korea-related pages caused Linter errors. They needed to be reverted. You are welcome to try again; check Page information after a single edit to see if you introduced Linter errors. I am available to help if you get stuck. – Jonesey95 (talk) 13:27, 16 June 2025 (UTC)[reply]
I reverted about 20 articles. The problem comes from putting Infobox Korean name/auto inside |footnotes=. That parameter opens a div tag in one table cell and closes it in a different table cell. You can see the results if you put the whole Infobox country section in Special:ExpandTemplates. (P.S. You can ignore the night mode and duplicate ID Linter errors.)– Jonesey95 (talk) 13:58, 16 June 2025 (UTC)[reply]
Ah yeah you're right. I was just about to post comment with same conclusion. For others reading, I had made these edits 100% manually; no AWB. This was just a misunderstanding on my part about how {{Infobox country}} works.
To address this, I may request that an additional parameter |module= get added to Infobox country. Then I'll reattempt these edits.
Ah yeah nice. Should I go ahead and request the edit to the template? It seems like you're a template editor; are you willing to edit it while we're at it? grapesurgeon (seefooddiet) (talk) 14:10, 16 June 2025 (UTC)[reply]
I recommend that you request that edit and explain why it is needed. You might check the template talk page to see if there has been a previous discussion. If there are no objections, I will implement the change. – Jonesey95 (talk) 14:15, 16 June 2025 (UTC)[reply]
Sorry for bothering you, but can you please take care of this first? I need to update the documentation and go to other wikis that copied the module. 172.56.232.142 (talk) 20:51, 20 June 2025 (UTC)[reply]
No worries; I put the template there originally and knew about the unreliable sources. They're almost entirely gone now (there's one disney-related source that's classified unreliable left).
I will do that now! I'm always down for reliable tools! I was just reading your user page. We both use AWB! I've been a Wikipedia user for, gosh, I think 15 years, haha It's always nice to meet an older user, such as me. Dillard421♂♂(talk to me)16:44, 24 June 2025 (UTC)[reply]
Possibly. I've said this before, but I'd rather Wikipedians not spend much time on him past the bare minimum. Neurotic attention seekers like him are everywhere nowadays. They relish even negative attention; by giving him all this exposure, even on Wikipedia, we're giving him what he wants. Better to just spend bare minimum on upkeep for the article, then otherwise ignore and move on. More societally beneficial things that need attention. Despite my edit count on that article, I've not spent much time on him; I plan on keeping it that way. grapesurgeon (seefooddiet) (talk) 22:26, 27 June 2025 (UTC)[reply]
Ok fixed, thankfully was simple. Solution was to search for every use of either of those templates in a page and replace "script-title" back to "title". Shouldn't occur anymore. grapesurgeon (seefooddiet) (talk) 22:16, 6 July 2025 (UTC)[reply]
Hey! Just a note that it's currently basically only useful for Korea-related articles; when I run it on non-korea articles it often gets 0 matches or minor cosmetic things. In order to make it functional for other topics would need a significant rewrite; almost equivalent to rewriting from scratch. If still interested lmk. Otherwise I could share the broad skeleton of the script (i.e. script has a list of publication names to link, script has a section for unreliable sources to tag, script has a section for general find+replaces in a list format. That structure is generally applicable. grapesurgeon (seefooddiet) (talk) 13:52, 28 June 2025 (UTC)[reply]
Ok; I'll send you an email via your profile. If you reply to it I can reply back with the xml profile file as an email. grapesurgeon (seefooddiet) (talk) 19:17, 28 June 2025 (UTC)[reply]
Hm I'm not sure but leaning towards saying "no". We currently don't have guidelines on whether to add those kinds of translations. What we don't want is people to translate the abstract part of place names, like "jiri" in your example. "San" is probably more ok to translate, but I feel like opening door to translating that may tempt a lot of people into translating entire mountain name
Hello, I'm aware they aren't the same person. That list is for people with net worth over a billion. I'm not sure what Chung Yong-ji's current net worth is but if it's still over a billion maybe he should be on that list grapesurgeon (seefooddiet) (talk) 12:31, 2 July 2025 (UTC)[reply]
In Special:Diff/1296287045 for the film A Tale of Two Sisters, you changed {{korean|hangul=장화, 홍련|rr=Janghwa, Hongryeon|lit=Rose Flower, Red Lotus}} to {{Korean/auto|hangul=^장화, 홍련|rr=yes|lit=Rose Flower, Red Lotus}} in the LEDE. But the obtained RR is now Janghwa, hongnyeon: in the second word, the "r" has been changed to "n". If I understand correctly, according to Revised Romanization of Korean, this is incorrect (an initial ㄹ corresponds to "r"). The version with an "r" is also what is (almost?) always used on the web. This could be a bug in Module:Ko-translit.
Moreover, what about the capitalization of the word (it seems that a capital H is expected here)?
Hello, thanks for the message. "Hongnyeon" is actually correct per Revised Romanization. This is due to linguistic assimilation, which is reflected in this case in RR.
See the official explanation of RR, the section where it says The case of assimilation of adjacent consonants. The "Jongno" example is similar principle. You'd expect it to be spelled "Jongro", to match the Hangul spelling. However, due to assimilation and reflecting how Koreans pronounce the word in practice, it'd be "Jongno".
On how other romanizations online use that spelling, they're simply just wrong. See WP:ROMANKO#Background; other than linguists, basically nobody really understands romanization of Korean. I notice incorrect romanizations constantly in Korean studies academic books and peer-reviewed papers. grapesurgeon (seefooddiet) (talk) 00:27, 6 July 2025 (UTC)[reply]
Oh forgot to address the capitalization question. We're less sure on what to do there. To my knowledge, RR has no official recommendations on whether/how to capitalize titles of works. In East Asian studies, it's widespread practice to use sentence case.
Similarly, and adding to the capitalization hairiness, it's relatively ambiguous how RR should be spaced. Should words "created" by additional spaces added be capitalized as well? Not straightforward answer I think.
We're currently pondering if/how we could systematize capitalization and spacing, but not straightforward. So for now, we're defaulting to mostly sticking with original spacing of Hangul and using sentence case. This is relatively close to practice in academia. grapesurgeon (seefooddiet) (talk) 00:33, 6 July 2025 (UTC)[reply]
Hi there, I'm pleased to inform you that I've begun reviewing the article Kwŏnŏphoe you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Grnrchst (talk) 18:37, 8 July 2025 (UTC)[reply]
Hi there, I saw you put in a "criticism" tag for the selfsame section in the McCune–Reischauer article. Thank you very much for this. I don't know your position on MR, but I am currently learning Korean and personally I find MR to be far superior to RR in terms of accurately and intuitively capturing Korean pronunciation.
Of course, with any transliteration system for any language, MR does have its drawbacks, but these are minor compared to the mess that is RR, and they're not hard to understand and adapt to. I understand you might delete the section soon if no credible citations are forthcoming - I might help you to delete it myself! If I have time I will expand the "limitations" section of the article to illustrate MR's advantages as well as disadvantages, for a balanced POV.
Hello, thanks for the message! To be clear, my tag has little to do with the ideas of the section. It's purely mechanical concerns. 1. Per WP:CRITICISMSECTION, we should try to distribute criticisms of the system throughout the article, not try to concentrate them all in one place. 2. It's unsourced, and likely the personal opinions of the editor who added them.
If that info had been sourced and wasn't concentrated in a criticism section, I wouldn't have gotten involved at all. grapesurgeon (seefooddiet) (talk) 03:19, 9 July 2025 (UTC)[reply]
Oops, I just fixed it. Thank you for letting me know. It was missing a set of close brackets; I also forgot to specify that it was the television version of the infobox grapesurgeon (seefooddiet) (talk) 22:13, 9 July 2025 (UTC)[reply]
.jpg)
I was thinking of making my own list of genfixes at some point so maybe it is useful inspiration. Thanks, Polygnotus (talk) 15:51, 28 June 2025 (UTC)
gmail.com thanks Polygnotus (talk) 00:04, 29 June 2025 (UTC)
This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Grnrchst (talk) 18:37, 8 July 2025 (UTC)