User talk:Benwing2

Archive

• 2012-2019
• 2020-2021
• 2022
• 2023
• 2024
• 2025

Template:scn-noun

There were 251 Sicilian entries in Special:UncategorizedPages, which turned out to be WingerBot leaving out a "}" when it rewrote this template. No module errors, because the result was inexecutable, but a whole lot of entries with broken template syntax instead of a headword.

I did my best to purge everything using the API sandbox and I think everything is back to normal, but there are 1,574 transclusions- so it's hard to tell. Category:Sicilian nouns seems to have stabilized at 1,749. It wouldn't hurt to check.

This is a good illustration of why bot-rewriting of templates always makes me nervous... Chuck Entz (talk) 19:19, 2 January 2026 (UTC)

Thanks for fixing this up and my apologies for messing it up in the first place. This error was due to a typo I made when manually editing the templates offline. I had assumed that if I made any typos they would lead to module errors or an abuse filter getting triggered about unbalanced braces, but I forgot that this doesn't always happen with template syntax (unlike with Lua, where this usually does happen). What I should have done was push each change manually (although that would have taken a long time ...). Benwing2 (talk) 19:30, 2 January 2026 (UTC)

add French to Module:Quotations

Could you add French to the 'hasData' table at Module:Quotations please? Saumache (talk) 21:00, 2 January 2026 (UTC)

Done. Benwing2 (talk) 21:11, 2 January 2026 (UTC)

Thanks! Saumache (talk) 21:14, 2 January 2026 (UTC)

Language code errors

These typos were easily fixed, but I'm listing them so you know they happened:

1. Chichewa: Template:ny-head: hy/ny (in template code- 503 mainspace transclusions)
2. Crimean Tatar: {{h|crn|pron}}/{{h|crh|pron}} (in öz, özü, özüm and qaysı)
3. Mauritian Creole: {{letter|mfr}}/{{letter|mfe}}; {{Latn-def|mfr|letter|5}}/{{Latn-def|mfe|letter|5}} in e

These all showed up in Special:WhatLinksHere/Wiktionary:Tracking/headword/incorrect language header, which has a few extra hits almost every day (2 are basically unfixable at the moment)- 500+ was a real surprise. Chuck Entz (talk) 01:03, 4 January 2026 (UTC)

Fuck, I seem to be getting careless. Thanks for fixing them. The hy/ny error was because I copied the definition of {{ny-head}} from {{hy-head}}; the other two were simple typos, as n is next to h and r next to e. I think I know how to avoid the adjacent-letter typos, which is to do search-and-replace operations where I have the operation itself copy the language code instead of having me separately type the language code in both the search and replace portion. BTW as I get older I notice myself frequently writing of for on, to for the, in for is, and other random cases of replacing one word, usually a function word, with another. I used to do that even as a teenager but the frequency has gradually increased over time. Not sure if you see the same thing happening. Benwing2 (talk) 01:21, 4 January 2026 (UTC)

Seeking Input

Hey Benwing2, I would like to seek some constructive advice or criticism on any issues you have for me, generally. I know you have opinions about my edits, and I know that I do not really see Wiktionary from the broader angle that higher-level editors do; I am super narrow focus. So I want to use any various opinions you might give me from your big picture view to try to enhance the value of my edits. Thanks for any time you give me. --Geographyinitiative 🎵 (talk) 03:14, 4 January 2026 (UTC)

It would help if you gave me some specific topics you're looking for input on. In terms of overall advice, the only thing I would say is that you have a tendency to jump to conclusions and then start doubting yourself and try to retract everything you've said. It would be better to proceed more slowly when writing your opinions and think through what you've written before hitting "Publish"; then, if you still feel the need to correct something you said, just post an update/correction rather than trying to retract everything. Think of a newspaper article; if a newspaper makes a mistake of fact where they should have known better, they generally post a correction, while if they make a mistake where they couldn't have known better (e.g. due to incomplete information), they post an updated article and let the previous article stand. Only in extreme cases do they retract an entire article (and usually it's a big scandal if/when that happens because it means a journalist fabricated the whole story). Benwing2 (talk) 03:21, 4 January 2026 (UTC)

Thanks for your comments. It's so interesting that you bring up this topic, this was not what I expected! You know, one of my higher goals on Wiktionary is to help create a community that will explore the topics that I am interested in. But I am myself am in essence the greatest enemy of the creation of that community, because I am too crude and backward and not friendly enough. Hence, when I try to delete, strike through, or otherwise take back previous posts, I am trying to exercise whatever residual authority I have over my previous posts to liberate Wiktionary from my mistakes, and create a more friendly environment that other people want to contribute to. I want professors, I want grad students, I want the best people. But I can't get them here if I've got a million silly rants out there. I discredit Wiktionary, hence I try to clean up previous posts. Moreover, this is not reddit, this is Wiktionary. The posts are not the point, the dictionary is the point. This is not the NYT and we should not treat posts with such seriousness that a retraction should be made or something like that. How do you think about this viewpoint? I'd like to know. I want to know because I need to connect with the community better to be able to improve my overall performance building the dictionary, and that starts with making people more comfortable with me. --Geographyinitiative 🎵 (talk) 09:42, 4 January 2026 (UTC)

Template:nn-noun

After spot-checking Wiktionary:Todo/Lists/Entries with missing headword lines#Norwegian Nynorsk, I get the impression that, as of 3 days ago, its only function is to take half a dozen or so parameters that it doesn't use and place the entry in Category:Pages using invalid parameters when calling Template:nn-noun. That's a bit of an exaggeration, but it does look like too much for me to sort through right now. Chuck Entz (talk) 22:41, 4 January 2026 (UTC)

Ugh, the cause of this was an unclosed HTML comment. Benwing2 (talk) 22:49, 4 January 2026 (UTC)

And also, yes there seem to be a lot of params that are being used but not supported; I assume it used to take a different syntax and got changed at some point without cleaning up all the old uses. Benwing2 (talk) 22:52, 4 January 2026 (UTC)

Category:Irish verb inflection-table templates

Link: Irish verb inflection-table templates
Hi, I was wondering if you could please make WingerBot replace all instances of l|ga, <sup>†</sup>, and ‡ in the pages of this category with l-self|ga, {{sup|†}}, and {{sup|‡}} if possible.
I saw it carry out similar edits to some Assamese noun declension templates about a week ago. Though, it broke the category links as seen here which I think I had managed to completely fix. Sorry I didn’t bring them up here at the time (which would have been the right thing to have done in hindsight). Saighneánach (talk) 19:45, 6 January 2026 (UTC)

This is another similar unconstructive edit I found which seems to be the last. Saighneánach (talk) 20:05, 6 January 2026 (UTC)

Thanks for fixing the errors I accidentally introduced when doing search-and-replace. I'll make the above replacements ... and be more careful not to affect category links :) Benwing2 (talk) 06:18, 7 January 2026 (UTC)

Thank you very much for doing the replacements. In relation to {{ga-conj-abair}}, I'm ok with the conversion to {{inflection-table-top}} (ITT); there’s a discussion at WT:AGA about whether to convert all the conjugation table to ITT and which style to use (which is what inspired my Bot request). Saighneánach (talk) 19:50, 7 January 2026 (UTC)

Translation adder again

Here is a simple Python script I wrote to generate the nesting variable for the translation adder: https://gist.github.com/atlight/5c0f6fdc846cea5609064003a4ced569 If you don't have any problems with it, I will replace the current nesting variable with this script's output.

I'll now work on fixing the sort order. This, that and the other (talk) 09:57, 18 January 2026 (UTC)

Looks good to me, thanks! Benwing2 (talk) 18:53, 18 January 2026 (UTC)

@This, that and the other You might want to update the data in the script with the latest from the current version of my script as I added some more language groups (for obscure languages) late last night. I'm probably going to run with this version. Benwing2 (talk) 19:02, 18 January 2026 (UTC)

Updated the Gist with the commit you made today, and updated the adder data file with the new nesting table. This, that and the other (talk) 08:21, 19 January 2026 (UTC)

Thanks! I'm in the process of going through all the multiword languages and updating the script accordingly; almost all of them are very obscure. I should be done by tomorrow at the latest and if you can plug in that version, it should be the last one. Benwing2 (talk) 08:26, 19 January 2026 (UTC)

Yes, I figured you would have further updates. Let me know.

As for sorting (best to continue that discussion here, away from BP): I can confirm that my "English collation" approach and a JS rendition of your "NFD-strip" approach produce identical results except in three cases:

1. "Magɨ" is sorted after "Maguindanao" when using NFD-strip (in JS at least) but correctly before "Magoma" using English collation
2. Possibly different sorting behaviour regarding spaces and punctuation (e.g. whether "Mid Grand Valley Dani" comes before or after "Mid-Southern Banda" - this also affects the placement of N'Ko) - note that I did add stripping of spaces, hyphens and apostrophes to the NFD-strip approach but I only added apostrophe stripping to the English collation approach. Can you confirm your code's sorting behaviour here?
3. Lects whose names differ only by accentuation (e.g. Cat:Karipuna language and Cat:Karipúna language). It seems like your implementation treats these as equal, leading to the risk of unstable sorting. However, this is currently a therotical issue only, as none of the 4 pairs that differ only by accent have any lemmas or translations.

This, that and the other (talk) 12:02, 19 January 2026 (UTC)

As for #2, get_L2_sort_key() does remove spaces and hyphens from the sort key, so I added that to my sort key. Specifically, it removes the following spacing characters, which I have added to my sort key: [-\s'"ʻʼ]. The only difference now between my sort key and get_L2_sort_key() is the list of combining characters, which is more extensive in get_L2_sort_key().

As for #1, the thing is that ideally we want the translation adder and get_L2_sort_key() to match. I agree it's better to sort Magɨ as if written Magi, but I'm not sure the exact rules used by Javascript's "English collation", so I'd have difficulty duplicating it either in Lua or Python.

As for #3, such cases shouldn't exist. Can you list the four pairs that differ only in accent? We need to rename them to avoid this.

Also, I just pushed what should be close to the final update for my list of language groups; I finished going through all the multiword languages. Any further updates will be tweaks. Benwing2 (talk) 23:35, 19 January 2026 (UTC)

Okay. Perhaps the best thing to do is for you to supply the full list of LOL language names sorted into the order you think they should be sorted in. I'll make sure the adder matches it.

Here are the pairs of lects that differ only by accent:

guq	Aché	(cat, lemmas, translations)
yif	Ache	(cat, lemmas, translations)
aru	Arua	(cat, lemmas, translations)
arx	Aruá	(cat, lemmas, translations)
bfa	Bari	(cat, lemmas, translations)
mot	Barí	(cat, lemmas, translations)
cma	Mạ	(cat, lemmas, translations)
msj	Ma	(cat, lemmas, translations)
vor	Voro	(cat, lemmas, translations)
vro	Võro	(cat, lemmas, translations)
tci	Wára	(cat, lemmas, translations)
wbf	Wara	(cat, lemmas, translations)

This, that and the other (talk) 23:57, 19 January 2026 (UTC)

(Incidentally, I thought there were only four pairs because I was looking at a diff of the two sorting approaches. While "English collation" always sorts the non-accented letter before the accented one, "NFD-split" is inconsistent, so only some pairs were sorted differently.) This, that and the other (talk) 00:06, 20 January 2026 (UTC)

See User:Benwing2/sorted-list-of-languages. I fixed the sort key so the langname itself is used to break ties; you can see by looking at the history of this page that it changed the order of some languages (e.g. Apma vs. Ap Ma, Abu vs. Abu', Madi vs. Ma'di, etc.; IMO none of these pairs should exist as such, without a disambiguator). Benwing2 (talk) 00:20, 20 January 2026 (UTC)

Thanks, that was useful. I have been able to replicate this ordering precisely in JS. Implemented at Special:Diff/89256104/89263153. This, that and the other (talk) 02:26, 20 January 2026 (UTC)

And updated nesting: Special:Diff/89256385/89263285 This, that and the other (talk) 02:37, 20 January 2026 (UTC)

Thanks! Benwing2 (talk) 04:28, 20 January 2026 (UTC)

Hi. Adding translation or translation requests for Latin (la) is no longer working with recent changes. Anatoli T. ^{(обсудить}/^вклад) 02:47, 27 January 2026 (UTC)

@This, that and the other Can you look into this? Could it have something to do with handling Latin as a script name? Benwing2 (talk) 02:49, 27 January 2026 (UTC)

It must do. Whoops! Let me fix it. This, that and the other (talk) 03:47, 27 January 2026 (UTC)

@Atitarev I take it this is only happening on pages which also have a "Serbo-Croatian > Latin" translation? This, that and the other (talk) 03:50, 27 January 2026 (UTC)

Yes. A similar clash happens with other nested names, such as Arabic, Hebrew, etc.

The bug with nesting translations is never fixed either. E.g. adding "Serbo-Croatian/Cyrillic" adds into "Mongolian/Cyrllic" instead.

For example, if "Cyrillic" appears in multiple places. The preview is fine but it saves under "Mongolian" instead of "Serb-Croatian" or "Old Church Slavonic" (usually from the lower in the alphabet into the higher one). Anatoli T. ^{(обсудить}/^вклад) 04:23, 27 January 2026 (UTC)

@Atitarev okay, the situation is worse than I realised.

I have made a quick fix to allow addition of Latin translations in a box that has a pre-existing Serbo-Croatian > Latin translation. This is a very dirty fix, as the translation preview will appear in the wrong place - but it does get saved correctly.

But clearly some serious work is needed on this part of the translation adder. Unfortunately I don't have time to do it immediately, but I will make a note of it. This, that and the other (talk) 04:30, 27 January 2026 (UTC)

Need help with de-verb

Hi, I need help with de-verb/de-conj, maybe this is already possible, but I can't figure the syntax out. I'm trying to fix the conjugation over at radfahren. This is a weird case where the verb (noun-verb combination) is separable, but the separable noun part is still to be treated as a normal German noun when separated, thus capitalized. radfahren => "ich fahre Rad, du fährst Rad" etc. At the moment the module generates lowercase forms: fährt rad etc. These forms are not correct (and never have been). Thanks! Jberkel 13:50, 19 January 2026 (UTC)

I tried {{de-verb|Rad.fahren<fährt#fuhr,gefahren,führe.sein>}}, this works, but leaves the infinitive uppercase (Radfahren) in the headword line. Jberkel 13:52, 19 January 2026 (UTC)

This will require some updates to the code. Internally, the code distinguishes a "prefix" (when the separable part comes before the main verb) and a "postfix" (when the separable part comes after), but doesn't currently provide a way of specifying them separately. One way I can think of is to simply lowercase the separable part to form the prefix; that way, we'd get postfix " Rad" but prefix "rad". Does that always work or are there verbs written with a capitalized prefix? Benwing2 (talk) 23:41, 19 January 2026 (UTC)

No, verb infinitives (+ participles etc) are always lowercase so this would work. Jberkel 07:15, 20 January 2026 (UTC)

Consolidating duplicated Arabic letter forms

Hi,

On pages such as ج, the template {ArabForm} is used multiple times under different language entries, without any particular reason why some are included and others not. They all display the same thing. Wouldn't it be easier just to list the forms of the letter once, at the top of the page? I'm thinking of something like this. kwami (talk) 00:45, 20 January 2026 (UTC)

I agree. I'm not sure why it's being done the way it is. I could potentially imagine some display differences between e.g. Persian and Arabic but I think in those cases they are already using different codepoints. Benwing2 (talk) 01:21, 20 January 2026 (UTC)

Either that or they're different hands that wouldn't be captured by the user's default Arabic font. The template currently has no way of displaying such differences regardless. If the variation is sometimes notable and can be captured with Unicode (or with images), we could always add that capacity to the template and show it under the relevant languages after consolidating the basic template to the top of the page.

I'll go ahead and restore that edit then. I don´t have JSWB on Wk, so it will take a bit of time to extend it to other characters. kwami (talk) 01:53, 20 January 2026 (UTC)

Sounds good. Benwing2 (talk) 01:56, 20 January 2026 (UTC)

Here's an example of one that maybe shouldn't be changed: ؠ. But most are straightforward. kwami (talk) 02:24, 20 January 2026 (UTC)

Arabic alphabet's done. Not yet all of the basic Arabic block, though. kwami (talk) 07:57, 20 January 2026 (UTC)

ں is another I'm leaving alone. kwami (talk) 10:42, 21 January 2026 (UTC)

Casing in symbols

r̃ is a phonetic symbol but has casing. AFAICT it's not used in orthography except for disambiguation in dictionaries. It's labeled as a symbol because it's phonetic, but to show the casing I need to template it as a letter. Is that okay, or does it need to be fixed somehow? kwami (talk) 07:09, 23 January 2026 (UTC)

Hmm, is it normal for NAPA to have casing in their phonetic symbols? Benwing2 (talk) 07:12, 23 January 2026 (UTC)

There's no intrinsic case. It's not uncommon to have casing in an ad hoc NAPA-based orthography, or as in this case a modified actual orthography, but it's not usual. We can't really say it's Hausa othography, but it is comparable to older English dictionaries where English orthography is retained but with added diacritics to specify pronunciation. kwami (talk) 08:53, 23 January 2026 (UTC)

Maybe we could list it under Hausa as a letter and with a lexicography tag. This isn't specifically Hausa, though, that's just the example we have. kwami (talk) 09:20, 23 January 2026 (UTC)

I have thought about this and I think we should have both a Translingual NAPA entry (a symbol, no case) and a Hausa entry (a letter, with case). Benwing2 (talk) 01:15, 24 January 2026 (UTC)

Okay. I'll mark it as lexicographic. We could probably add other languages with the same, but the Hausa illustration should be enough to show people what's going on. kwami (talk) 01:25, 24 January 2026 (UTC)

Linking from header

At Gǃòʼé_ǃHú#Juǀ'hoan, the header is red because it's capitalized and the individual words have articles but in lowercase. Is there a way to specify casing so the template both displays and links correctly? (Alternatively, perhaps I could move the Juǀ'hoan entry to lowercase gǃòʼé ǃhú, but I imagine this isn't an uncommon problem.) kwami (talk) 06:54, 25 January 2026 (UTC)

Yes, use the |head= parameter, something like {{head|ktz|noun|head=[[gǃòʼé|Gǃòʼé]] [[ǃhú|ǃHú]]}}. This is the standard way of handling this. Benwing2 (talk) 06:59, 25 January 2026 (UTC)

Thanks. kwami (talk) 07:00, 25 January 2026 (UTC)

Before I fix them, should definitions for symbols avoid starting with "The symbol for"? E.g. at ♍︎. I'm thinking they should be e.g. "(astronomy) Virgo (constellation)" rather than "(astronomy) The symbol for the constellation Virgo." kwami (talk) 09:32, 25 January 2026 (UTC)

I'm not Benwing, and maybe he'll differ, but I'd favour the first option. If the POS is "Symbol", which it will be, then we are already declaring these as symbols elsewhere in the entry.

As an aside, I am perplexed at your use of {{ng}} in entries like ǃHãunu. The definitions written here are glosses, no? A non-gloss definition of ǃHãunu would be "Used to refer to the brother-in-law of ǂKá̦gára." or some such. This, that and the other (talk) 05:01, 27 January 2026 (UTC)

I thought I was told to use {ng} in such cases. I guess I misunderstood. It does read better without the italics. kwami (talk) 05:08, 27 January 2026 (UTC)

I've started converting the sign/constellation defs to glosses. kwami (talk) 06:15, 27 January 2026 (UTC)

What of ǂKá̦gára, should I also remove the ng template there? kwami (talk) 06:21, 27 January 2026 (UTC)

Yes, because the definition is a gloss (it defines what the word is) rather than a non-gloss (defining how the word is used, etc.). The info about the moon should be removed or at most placed in a usage note because it's not part of the definition. Benwing2 (talk) 06:24, 27 January 2026 (UTC)

ϟ#Zulu

Someone objected to the obsolete Zulu entry, which is based on being a graphic lookalike to the Greek. Since I created the entry, would it be a problem for me to delete it and recreate it on an unsupported-character page, without waiting for the deletion request to resolve? kwami (talk) 09:53, 3 February 2026 (UTC)

{{pagename}}

Is there any way to make it capitalize the first letter of an entry? Or perhaps an alternative template? For example, in dog, it would come in handy to have it displaying “Dog” instead of simply “dog”. ~2026-82697-7 (talk) 14:42, 6 February 2026 (UTC)

{{ucfirst:{{pagename}}}}. — Sgconlaw (talk) 15:14, 6 February 2026 (UTC)

Thanks! ~2026-82697-7 (talk) 15:20, 6 February 2026 (UTC)

old comma issue

This is from 2022 so I don't know if it's possible or worthwhile to look for other examples, but I notice that here WingerBot erroneously converted [[hätte der Hund nicht geschissen, hätte er den Hasen gefangen]] (link to "x, comma y") into [[hätte der Hund nicht geschissen|hätte er den Hasen gefangen]] (piped link displaying only "y" and pointing to only "x"). - -sche (discuss) 05:10, 7 February 2026 (UTC)

This was not a "manually assisted" edit (which would imply a one-off error), so there may be other such cases, and I should still have the old logs on my old laptop so it should be possible to dig them up and look for other cases. I've been meaning to copy over all the stuff from my old laptop so this may incentivize me to do so. Benwing2 (talk) 05:17, 7 February 2026 (UTC)

See also addition reversion

Hello,

You had reverted an addition of a "see also" template to a Spanish entry I had created as "not useful". I had made a typo (I had left off the acute accent in error); I have added the template back with its intended entry in place of the one that was there. A few Spanish verb forms differ from one another only in the presence or absence of that acute accent. StrangerCoug (talk) 08:42, 9 February 2026 (UTC)

@StrangerCoug Hi, because of the typo there was a module error, which is why I deleted the {{also}} template. Make sure to check for module errors after saving; they show up in red when you preview or after saving, and they're visible in Category:Pages with module errors (or CAT:E for short). Benwing2 (talk) 04:09, 10 February 2026 (UTC)

I will slow down a little more so I can play closer attention to the error next time—with the accelerated creation links, it's relatively easy for a human to make a lot of entries quickly, and the also templates I have to manually add. StrangerCoug (talk) 04:17, 10 February 2026 (UTC)

cln nl Low Saxon cardinal numbers

I noticed today this edit. I fixed it, and any other Dutch Low Saxon (or German Low German) entries which may have been edited in this way will also get fixed as they are merged, but I'm letting you know in case similar edits were made for other languages: there are other languages that that kind of search-and-replace would stumble on, e.g. "Hindi Dogri". You may already be aware of the issue; I recall a discussion about the fact that we have various language names that superficially contain other language names, and the ways in which this complicates search-and-replace of language names with language codes, happening somewhere recently. - -sche (discuss) 03:56, 10 February 2026 (UTC)

Hi, thanks for reminding me of this issue. I do remember someone mentioning this before but I'm not sure whether I ever fixed the script. I'll take a look; it shouldn't be too hard to fix, you just have to work from right to left looking for the longest matching name. I'll also look and see if I can find any other such cases. BTW if you need botting to convert e.g. German Low German nouns to Low German nouns, I should be able to do that fairly easily. Benwing2 (talk) 04:08, 10 February 2026 (UTC)

All right I see what the issue is; my script requires a language name or code and works one language at a time, but doesn't check to see if the language name is part of a longer language name. Benwing2 (talk) 04:11, 10 February 2026 (UTC)

It looks like all the Dutch Low Saxon errors in that 2024 run were cardinal numbers: drij, een, elf, negen, tien, twaalf, veer, vief, zes. No German Low German cases (at least in that run) were incorrectly converted to German. Benwing2 (talk) 04:22, 10 February 2026 (UTC)

Seems like you already converted all those numbers. Benwing2 (talk) 04:24, 10 February 2026 (UTC)

Capitalisation in {{cy-adj}}

Hi, I think you corrected {{cy-mut}} so it would show correctly capitalised mutated nouns. Would you be able to change {{cy-adj}} so it does the same? Currently Gwyndodig shown with a soft mutation of wyndodig in {{cy-adj}}! Arafsymudwr (talk) 19:11, 12 February 2026 (UTC)

Translation sorting

Your bot is renaming Adyghe -> West Circassian without sorting it to the right place in the list of translations. West Circassian is now first in the alphabetic list. Vox Sciurorum (talk) 01:54, 15 February 2026 (UTC)

@Vox Sciurorum That step comes next ... Benwing2 (talk) 02:18, 15 February 2026 (UTC)

I'm renaming Kabardian -> East Circassian then I'll sort all the results properly. Benwing2 (talk) 02:19, 15 February 2026 (UTC)

Bot request for Cornish

Hello, I have seen your bot WingerBot carry out similar tasks so I would like to request that it replace all instances with {{kw-mut-cons|foo|bar}} with simply {{kw-mut}}, in order to deprecate the former. All instances requiring additional input have (I believe) been replaced manually, just need a bot to carry out the arduous task of replacing the simpler instances. Thanks! Tesco250 (talk) 22:23, 15 February 2026 (UTC)

@Tesco250 Should be done. Benwing2 (talk) 02:28, 16 February 2026 (UTC)

Quotation template and other replacements (February–March 2026)

Hi, could you please carry out the following replacements when you have time?

• If |page= or |pages= used and |year=1959 not already added, {{RQ:Achebe Things Fall Apart}} → {{RQ:Achebe Things Fall Apart|year=1959}}.
• If |page= or |pages= used and |year=1919 not already added, {{RQ:Marshall Squire's Daughter}} → {{RQ:Marshall Squire's Daughter|year=1919}}.
• {{RQ:Morley Haunted}} → {{RQ:Morley Haunted Bookshop}}.
• {{RQ:Nesbit New Treasure Seekers}}: the template has been updated. If there is a number in the |1= position (formerly the chapter number), remove it.
• {{RQ:Trollope The Way}} → {{RQ:Trollope Way}}.
• {{RQ:Wallace Ben-Hur}} → {{RQ:L. Wallace Ben-Hur}}.
• {{RQ:Wilkins MM}} → {{RQ:J. Wilkins Mathematicall Magick}}.
• {{Navbox}} → {{navbox}} (they have been merged).
• Thesaurus:randy → Thesaurus:sexually aroused.
• |1=en in all quotation templates → |en.

Thank you. — Sgconlaw (talk) 14:06, 18 February 2026 (UTC)

FYI, as of the Feb 1 dump, there are 15,115 instances of |1=en in {{quote-*}} over 10,658 pages, and 23,330 instances of |1=* over 16,683 pages. I'm not sure where all of these are coming from; I wonder if Quiet Quentin or some other quote-generating gadget (@Ioaxxere?) is generating quotation templates this way. Benwing2 (talk) 03:20, 19 February 2026 (UTC)

Hmmm, no idea. Interesting. I keep coming across them. — Sgconlaw (talk) 05:27, 19 February 2026 (UTC)

I added another request relating to {{navbox}}. — Sgconlaw (talk) 17:55, 25 February 2026 (UTC)

Suggestion

In the entry 'effeminate' could you edit the first sense?

Of a boy or man, exhibiting behavior or mannerisms considered unmasculine or typically feminine

I think it's broader and more accurate, thank u! Logenman (talk) 00:47, 22 February 2026 (UTC)

Hi, you should bring this up in the tea room if you're unable to edit the page yourself. Benwing2 (talk) 00:49, 22 February 2026 (UTC)

bot request to move infinitives first on non-lemma entries like tremere

I think it's obvious that the Latin infinitive is more important than a secondary form of the 'second-person singular future passive indicative' and we're doing people a disservice by having the latter first (which was done by @Kennybot). So could you change the order here? Exarchus (talk) 19:44, 25 February 2026 (UTC)

mismatched headers

As a followup to #Casing in symbols above, we have medieval scribal abbreviations like ꝯ, which people are placing under the header 'symbol', but with a 'letter' template because they have casing. I wanted to check before changing the headers to 'letter'. They aren't letters of the alphabet, but behave as such. There are others such as ꝝ that are matched as 'symbol', but if the first is changed to 'letter', for consistency the second probably should be too.

I guess a follow-up question would be, what's the deciding difference between a 'symbol' in a phonetic alphabet and a 'letter' in a unicameral alphabet? kwami (talk) 19:57, 25 February 2026 (UTC)

talk page

Hello Benwing2,

May I request permission to archive/blank my talk page? box16 (talk) 20:53, 27 February 2026 (UTC)

@Box16 Please don't just "blank" your talk page. Instead, copy the contents to a sub-page named according to the dates of the contents, and then delete the corresponding contents on the main page. See my talk page for an example. Benwing2 (talk) 03:29, 28 February 2026 (UTC)

Thank you for the information. box16 (talk) 05:35, 28 February 2026 (UTC)

@Benwing2, in this post above, you politely request, "please", that an editor not do something that's actually not against the rules. So, in that same spirit, I want to do the same to you Benwing2: please stop requesting Wiktionary editors follow practices or rules which do not exist. I would say "please follow Wiktionary guidelines" and that's it, no need for extra taboos or moralizing etc. Please only advise people to follow the rules, not extra non-rules. And if you consider this annoying, because I'm pushing a non-rule request on you, imagine the people you're pushing non-rule requests on. Doesn't feel so good, does it? --Geographyinitiative 🎵 (talk) 10:56, 28 February 2026 (UTC)

Template:entryname

Why did you make this? —Justin (koavf)❤T☮C☺M☯ 19:45, 15 March 2026 (UTC)

@Fenakhay: for visibility. —Justin (koavf)❤T☮C☺M☯ 05:35, 20 March 2026 (UTC)

Language treatment

Hello, could you proceed with this request? I think there has been a consensus for some time regarding this as a minimum measure. I have been working on the language (family) and it should come in quite handy. Also pinging @-sche, who seems more active (hope everything is well with you). Jacaguoçãrana (talk) 00:03, 20 March 2026 (UTC)

Adding 100000 West & East Circassian entries using a bot

Hi,

We exchanged some messages in https://en.wiktionary.org/wiki/Wiktionary:Language_treatment_requests#Circassian one month ago. You said that you have a registered bot and scripts. I have almost 100000 entries in both West & East Circassian that I want to add to Wiktionary. I wanted to ask, if you can give me the dump of all West & East entries, I will modify them using a script of my own, and then I will re-send you all modified files + 950000 new entries. Adamʂa123 (talk) 18:03, 23 March 2026 (UTC)

Module:de-IPA

Hi, I was snooping this module cause I'm considering the possibility to implement it into other Wiktionary. But I found that you were working on a way more sophisticated version, but it didn't leave your user space, I want to ask you: is this project abandoned? Do you still consider it is a worth implementing module rather than do manual IPA transcriptions? Do you think in retaking the job someday in the future? What would be your advice for someone is looking for a automatic or semiautomatic transcription tool for this language? Tmagc (talk) 22:02, 2 April 2026 (UTC)

see discussion regarding the gerund in Portuguese

Hey, Ben! I've just noticed you were the one who added the entire "Participles" section to AP:Portuguese verbs 4 years ago. Special:Diff/70263704

Please see Appendix talk:Portuguese verbs#On the Portuguese gerund. o/ Emanuele6 (talk) 17:57, 3 April 2026 (UTC)

bot job

This poor guy is probably trying to manually add {{fr-IPA}} to every French verb form, which would take 24 years. Any chance you could speed up the process? —User:Vealhurl (talk 22:19, 21 April 2026 (UTC)

@Vealhurl: I don't know if you noticed, but Ben seems to have gotten really, really busy IRL and hasn't made an edit under any of his accounts in a month and a half. As for his bot, make that two months. Chuck Entz (talk) 03:51, 22 April 2026 (UTC)

OK, so Chuck, you make the bot!!! —User:Vealhurl (talk 07:08, 22 April 2026 (UTC)

You may be an eligible candidate for the U4C election

Greetings,

The Universal Code of Conduct Coordinating Committee (U4C) seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the Universal Code of Conduct. Elections are held annually, if elected a committee member serves for two years.

This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the call for candidates on Meta-wiki. Additionally, the committee's working language is English; some ability to communicate in English is required.

The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in SecurePoll, successful candidates must receive at least 60% support. More information is available on the 2026 Elections page, including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run.

In partnership with the U4C -- Keegan (WMF) (talk) 18:32, 28 April 2026 (UTC)

(This message was sent to User talk:Benwing and is being posted here due to a redirect.)

Words of positivity

I want to let you know that you are missed and I hope that you are faring well; Cheers! TranqyPoo [💬 | ✏️] 03:33, 5 May 2026 (UTC)