User talk:Grapesurgeon: Difference between revisions

Line 65: Line 65:

::::Or, we could consider speeding up the process of adding it to the guidelines, as you considered previously [https://en.wikipedia.org/wiki/User_talk:Grapesurgeon/Archive_2#Question here], so we can regulate what people choose to add based on those guidelines. [[Special:Contributions/~2025-32317-07|~2025-32317-07]] ([[User talk:~2025-32317-07|talk]]) 05:47, 10 November 2025 (UTC)

:::::I’m still not sure how best to regulate this, if at all. In scenarios where I’m not sure I try to avoid adding regulation; adds more reading for others [[User:Grapesurgeon|grapesurgeon]] ([[User talk:Grapesurgeon|talk]]) 13:32, 10 November 2025 (UTC)

== Requesting to remove ==

Hi there, I would like to request to you to use AWB to remove the with <code>|image_upright = 1.15</code> parameter on all Korean drama related articles. [[User:D.18th|𝙳.𝟷𝟾𝚝𝚑]] [[User talk:D.18th|(𝚃𝚊𝚕𝚔)]] 11:07, 15 November 2025 (UTC)

Archives

1, 2

This page has archives. Sections older than 30 days may be auto-archived by Lowercase sigmabot III if there are more than 6.

@Grapesurgeon, I read this the other day and have found your work filling in much of the articles we need here. Great work, let me know where I can be a help down the line. ~~ CherryPie94 🍒🥧 (talk) 08:49, 6 November 2025 (UTC)[reply]

Thanks for the kind words 🙂 will do! grapesurgeon (talk) 16:07, 6 November 2025 (UTC)[reply]

You may want to create the following pages as redirects to the Obsolete Hangul jamo page:

ퟍ, ퟏ, ퟐ, ퟒ, ퟕ, ퟝ, ퟣ, ퟦ, ퟧ, ퟨ, ퟩ, ퟪ, ퟯ, ퟰ, ퟱ, ퟲ, ퟹ

~2025-31802-04 (talk) 04:34, 7 November 2025 (UTC)[reply]

Done, thank you grapesurgeon (talk) 19:36, 7 November 2025 (UTC)[reply]

You may want to request temporary account IP viewer. I’d just give it to you, but I’m not allowed to; this specific userright requires that the user make a request.

Also, were you planning to file an SPI for the weird activity on that article? If not, I’ll write one up. I suspect…something. Toadspike [Talk] 21:20, 7 November 2025 (UTC)[reply]

Requested, thanks for tip. I was considering writing SPI case but wasn’t sure how to frame it. Could you write up? grapesurgeon (talk) 21:28, 7 November 2025 (UTC)[reply]

I’ll file the report grapesurgeon (talk) 18:46, 8 November 2025 (UTC)[reply]

Wikipedia:Sockpuppet investigations/Parkeunseo grapesurgeon (talk) 19:29, 8 November 2025 (UTC)[reply]

Thanks. Haven’t had much time to edit from desktop over the last few days. Toadspike [Talk] 12:10, 9 November 2025 (UTC)[reply]

Hello, Grapesurgeon. Per your request, your account has been granted temporary-account-viewer rights. You are now able to reveal the IP addresses of individuals using temporary accounts that are not visible to the general public. This is very sensitive information that is only to be used to aid in anti-abuse workflows. Please take a moment to review Wikipedia:Temporary account IP viewer for more information on this user right. It is important to remember:

You must not share IP address data with someone who does not have the same access permissions unless disclosure is permissible as per guidelines listed at Foundation:Policy:Wikimedia Access to Temporary Account IP Addresses Policy.
Access must not be used for political control, to apply pressure on editors, or as a threat against another editor in a content dispute. There must be a valid reason to investigate a temporary user. Note that using multiple temporary accounts is not forbidden, so long as they are not used in violation of policies (for example, block or ban evasion).

It is also important to note that the following actions are logged for others to see:

When a user accepts the preference that enables or disables IP reveal for their account.
Revealing an IP address of a temporary account.
Listing the temporary accounts that are associated with one or more IP addresses (using the CIDR notation format).

Remember, even if a user is violating policy, avoid revealing personal information if possible. Use temporary account usernames rather than disclosing IP addresses directly, or give information such as same network/not same network or similar. If you do not want the user right anymore then please ask me or another administrator and it will be removed for you. You may also voluntarily give up access at any time by visiting Special:Preferences. Happy editing! — rsjaffe 🗣️ 21:50, 7 November 2025 (UTC)[reply]

A linguistics-interested friend of mine (not a Wikipedia editor) asked me to pass along that Origin of Hangul § Seal script hypotheses might be good to replicate in some way in the ʼPhags-pa inspiration for Hangul hypothesis article! Best, KevinL (aka L235 · t · c) 23:30, 8 November 2025 (UTC)[reply]

Oh! Good point, there’s some stuff I need to clean up between the two as well. Thanks! grapesurgeon (talk) 04:15, 9 November 2025 (UTC)[reply]

From my previous talk here

I fully agree with the concern of speculative translation. However, for cases where the suffix (산 / san) is consistently and conventionally translated as Mount in English, it would improve clarity to display this. To achieve consistency, I think infobox Korean auto (which you’re the co-author) should be automatically configured to display translation if the Hangul value is equal to the value from a list or something similar. The set of major Korean mountains is likely within a maintainable range to be easily created or maintained by experienced editors. ~2025-32317-07 (talk) 14:43, 9 November 2025 (UTC)[reply]

I’m skeptical. I don’t know if it’d be all that helpful, cause it’d just be like “Mount Paektu”, which is fairly obvious after reading a few words of the lead anyway. Also most people on Korean mountain pages likely know “san” means “mountain”. Also technical implementation detail; which romanization do we choose to show in the literal translation, and how do we know for sure the article is about a mountain and not like something else that ends in “san”? Takes a bit of thought and imo it’s not worth it overall grapesurgeon (talk) 22:00, 9 November 2025 (UTC)[reply]

We could match it verbatim from a predefined Hangul list instead of displaying every “san” suffix to Mount. Also this translation can extend beyond mountain, I suggest we do it for palaces as well, sources sometimes make the name redundant as in the case of “Gyeongbokgung Palace”, and I would hope for the infobox to explain that its translation is “Gyeongbok Palace”. ~2025-32317-07 (talk) 01:54, 10 November 2025 (UTC)[reply]

Programming that in is unnecessarily inelegant; would be writing in a list of every thing we want to provide literal translation for. I’m still skeptical of this idea. grapesurgeon (talk) 03:16, 10 November 2025 (UTC)[reply]

Or, we could consider speeding up the process of adding it to the guidelines, as you considered previously here, so we can regulate what people choose to add based on those guidelines. ~2025-32317-07 (talk) 05:47, 10 November 2025 (UTC)[reply]

I’m still not sure how best to regulate this, if at all. In scenarios where I’m not sure I try to avoid adding regulation; adds more reading for others grapesurgeon (talk) 13:32, 10 November 2025 (UTC)[reply]

Hi there, I would like to request to you to use AWB to remove the with |image_upright = 1.15 parameter on all Korean drama related articles. 𝙳.𝟷𝟾𝚝𝚑 (𝚃𝚊𝚕𝚔) 11:07, 15 November 2025 (UTC)[reply]

Must Read

Leave a Comment Cancel Reply

Leave a Comment