Wiktionary:Requests for deletion/Others

Wiktionary > Requests > Requests for deletion/Others

Wiktionary Request pages (edit) see also: discussions
Requests for cleanup
add new | history | archives

Cleanup requests, questions and discussions.

Requests for verification/English
add new English request | history | archives

Requests for verification in the form of durably-archived attestations conveying the meaning of the term in question.

Requests for verification/CJK
add new CJK request | history

Requests for verification of entries in Chinese, Japanese, Korean or any other language using an East Asian script.

Requests for verification/Italic
add new Italic request | history

Requests for verification of Italic-language entries.

Requests for verification/Non-English
add new non-English request | history | archives

Requests for verification of any other non-English entries.

Requests for deletion/Others
add new | history

Requests for deletion and undeletion of pages in other (not the main) namespaces, such as categories, appendices and templates.

Requests for moves, mergers and splits
add new | history | archives

Moves, mergers and splits; requests listings, questions and discussions.

Requests for deletion/English
add new English request | history | archives

Requests for deletion of pages in the main namespace due to policy violations; also for undeletion requests.

Requests for deletion/CJK
add new CJK request | history

Requests for deletion and undeletion of entries in Chinese, Japanese, Korean or any other language using an East Asian script.

Requests for deletion/Italic
add new Italic request | history

Requests for deletion and undeletion of Italic-language entries.

Requests for deletion/Non-English
add new non-English request | history | archives

Requests for deletion and undeletion of any other non-English entries.

Requests for deletion/​Reconstruction
add new reconstruction request | history

Requests for deletion and undeletion of reconstructed entries.

{{attention}} • {{rfap}} • {{rfdate}} • {{rfquote}} • {{rfdef}} • {{rfeq}} • {{rfe}} • {{rfex}} • {{rfi}} • {{rfp}}

All Wiktionary: namespace discussions 1 2 3 4 5 - All discussion pages 1 2 3 4 5
This page is for the nomination (for deletion) of non-main namespace entries. General questions about categories, templates and the like should be posted at Wiktionary:Grease pit. Remember to start each section with only the wikified title of the page being nominated for deletion.
Oldest 200 tagged RFDOs

2016 edit

Category:Kangxi radicals edit

Redundant to Category:Kangxi Radicals block. Has a table that might be worth keeping. —suzukaze (tc) 07:39, 25 September 2016 (UTC)Reply

Category:CJKV radicals edit

Redundant to Category:Han character radicals. —suzukaze (tc) 07:39, 25 September 2016 (UTC)Reply

Category:Han rad sup edit

Redundant to Category:CJK Radicals Supplement block. Also it has a terrible name. Has a table that might be worth keeping. —suzukaze (tc) 07:39, 25 September 2016 (UTC)Reply

Keep - not in itself a rational for deletion. also yourself: is the category useful? does it fit into a schema of categorisation? is it likely that we are goingto have things to vategorise into it, inm the future? if the answer to anty ofthese is "yes", then we should keep it, rather than have to repeat the work later. respectfully, Lx 121 (talk) 10:55, 29 April 2019 (UTC)Reply

Delete all - the first one is more dubious than the rest though, as Kangxi Radicals block is just a Unicode block category. If the contents are the same though, there's little point in keeping them separate. — surjection??18:46, 19 October 2021 (UTC)Reply

Okay:

This, that and the other (talk) 11:44, 26 September 2022 (UTC)Reply

@Justinrleung since you are commenting elsewhere on this page, I wonder if you can advise how to proceed with the remaining component of this ancient RFDO request? This, that and the other (talk) 09:11, 27 December 2022 (UTC)Reply
@This, that and the other: Entries seem to be automatically categorized into CAT:Han character radicals by {{Han char}}. I'm not exactly sure what the exact mechanism is. @Fish bowl, I'm wondering if you know. Some of the so-called radicals in CAT:CJKV radicals seem to not be Kangxi radicals but Shuowen radicals, like 共, so these would not be automatically categorized by CAT:Han character radicals. I do think that there should probably only one category for radicals, and I think CAT:Han character radicals is probably better as a name since Han characters are not exclusive to the four languages of CJKV. But we'll have to see if these radicals in CAT:CJKV radicals only should just be moved to CAT:Han character radicals manually or with changes to {{Han char}}. — justin(r)leung (t...) | c=› } 16:23, 27 December 2022 (UTC)Reply
@Fish bowl we are waiting for your input here. Could you please state whether you agree with Justin's proposal to merge all of the radical entries in both categories to Cat:Han character radicals and delete Cat:CJKV radicals? This, that and the other (talk) 23:23, 22 November 2023 (UTC)Reply
The mechanism is categorization if there are 0 residual strokes (Module:zh-han#L-125).
Whatever the difference between Category:Han character radicals and Category:CJKV radicals is, it's a poor one as the names are essentially equivalent. —Fish bowl (talk) 06:16, 24 November 2023 (UTC)Reply
I agree - let's merge them into Han character radicals. Theknightwho (talk) 09:51, 7 January 2024 (UTC)Reply
So the entries requiring manual review are those only in CJKV radicals. It appears to me, as a CJK outsider, that many of these are essentially alternative forms of radicals. Many of these have corresponding radical appendices, and many of them have the residual strokes parameter set to "00", which I assume is meant to do something magical.
This, that and the other (talk) 22:38, 7 January 2024 (UTC)Reply

Category:Japanese-only CJKV Characters edit

Category:Japanese-coined CJKV characters used outside Japanese edit

Category:Korean-only CJKV Characters edit

Was this created to distinguish "exclusively" Japanese and Korean inventions from Chinese characters? The Chinese will use it anyway. —suzukaze (tc) 04:10, 9 October 2016 (UTC)Reply

Delete. --Daniel Carrero (talk) 04:19, 9 October 2016 (UTC)Reply


I note that Japanese has Category:Japanese-coined CJKV characters is fine, but there is no Category:Korean-coined CJKV characters. As such, I propose moving Category:Korean-only CJKV Characters to Category:Korean-coined CJKV characters if this RFD fails. —suzukaze (tc)

Delete - none of these have etymological value. Theknightwho (talk) 11:31, 27 May 2022 (UTC)Reply

I’m a language learner, not a linguist. Whether it’s Category:Korean-only CJKV Characters or Category:Korean-coined CJKV characters, I find this list interesting, and would like to be able to refer to it. W3steve (talk) 01:26, 8 May 2023 (UTC)Reply

Keep them, it is of practical value. Maybe Chinese will use it, or not, will understand it, or not, doesn't matter. What is important in it the Koreans / Japanese respectively and the lerners of Korean / Japanese respectively will find the respective category valuable. NoychoH (talk) 07:04, 13 August 2023 (UTC)Reply
I agree to keep per NoychoH, I found this Japanese-coined CJKV characters used outside Japanese and was surprised to see anyone wants it deleted. It's just curious, for which reason it's valuable. I just see no reason to delete it. Kiril kovachev (talkcontribs) 19:57, 30 August 2023 (UTC)Reply
Keep for the same reasons as Kiril kovachev.Auvon (talk) 03:04, 3 December 2023 (UTC)Reply
@NoychoH @Kiril kovachev @Auvon If its starts being used in Chinese, then it stops being a Japanese-only character. The big problem with the category is that it relies on other languages not using it, which is essentially impossible to keep track of. Theknightwho (talk) 09:54, 7 January 2024 (UTC)Reply
@Theknightwho Okay, good point. I could suggest removing a character from the category once we have a Chinese entry for it, but this would require more work on the part of Chinese editors. I don't necessarily oppose deleting the Japanese-only and Korean-only categories, but I don't know why Category:Japanese-coined CJKV characters used outside Japanese is being included in this RfD. That doesn't have the same problem in that it doesn't run the risk of misinformation, and is rather much more interesting for language learners. I say we should keep that one, delete the rest if that's what we want. Kiril kovachev (talkcontribs) 22:14, 7 January 2024 (UTC)Reply

2017 edit

Category:Reference templates edit

These should be placed in the appropriate language-specific categories. —CodeCat 15:24, 23 February 2017 (UTC)Reply

Yes, but the category shouldn't be deleted, as the lang-specific catgs should be kept here. Perhaps rename Cat:Reference templates by language if necessary. —Aɴɢʀ (talk) 15:54, 23 February 2017 (UTC)Reply
Never mind, I didn't realize that's already a separate catg. —Aɴɢʀ (talk) 15:55, 23 February 2017 (UTC)Reply
I presume that such templates are categorized by the target language, not the language in which they are written. Do we not care about the language in which the reference is written? What about a multilingual dictionary? (There are at least two such templates.) DCDuring TALK 16:15, 23 February 2017 (UTC)Reply
They're placed in whichever language they're relevant to as a reference. So the language it's written in is not taken into account, but they can be placed into more than one language category. —CodeCat 16:21, 23 February 2017 (UTC)Reply
Shouldn't this category be kept as a parent category for "Category:Reference templates by language"? Also, there may be translingual templates such as {{R:Reference-meta}} which I have been working on. — SMUconlaw (talk) 18:44, 23 February 2017 (UTC)Reply
Why should Category:Reference templates by language be placed in this category? It already has its own parent category. And translingual reference templates naturally go in Category:Translingual reference templates. —CodeCat 18:51, 23 February 2017 (UTC)Reply
Thanks, I didn't know "Category:Translingual reference templates" existed. However, isn't it usually the case that when there is a category in the form "X by Y", "X" exists as a parent category as well? At least that's what happens at the Wikimedia Commons. — SMUconlaw (talk) 18:59, 23 February 2017 (UTC)Reply
Not on Wiktionary. I can't imagine Category:Nouns being very useful as a parent of Category:Nouns by language. —CodeCat 19:01, 23 February 2017 (UTC)Reply

──────────────────────────────────────────────────────────────────────────────────────────────────── In that case, delete according to the reason provided by the nominator. — SMUconlaw (talk) 19:12, 23 February 2017 (UTC)Reply

Could some people help with clearing it out? —CodeCat 14:05, 26 March 2017 (UTC)Reply

@CodeCat: I'll do some work on it. — Eru·tuon 21:46, 26 March 2017 (UTC)Reply
When it's deleted, where shall we put Category:Quotation reference templates? —Aɴɢʀ (talk) 15:50, 27 March 2017 (UTC)Reply
What about the templates not in another category, like Template:R:Wordorigins.org! Will they become orphant-templates upon deletion of Category:Reference templates? Thx, B Lemeukx (talk) 11:56, 21 October 2017 (UTC)Reply

Keep - obviously useful as a meta-category. Lx 121 (talk) 14:19, 29 April 2019 (UTC)Reply

You haven't read the discussion. There are currently two such categories. —Rua (mew) 14:20, 29 April 2019 (UTC)Reply
I've seen both categories, & they seem to serve different purposes. this one is general-purpose (any template related to references), & the other one Wiktionary: Reference templates seems to be narrowly-defined (a list of dictionary-reference templates). So either merge or differentiate them better? & 'Reference Templates' is still the obvious meta-category for ALL reference templates. Lx 121 (talk) 15:28, 29 April 2019 (UTC)Reply
After some more cleanup, the category now has only six members. —Rua (mew) 16:25, 30 April 2019 (UTC)Reply

Appendix:X is a beautiful language edit

They are present at the translation section of English is a beautiful language.--2001:DA8:201:3512:BCE6:D095:55F1:36DE 12:18, 6 June 2017 (UTC)Reply

Your logic would be flawed if English is a beautiful language is deleted. --WikiTiki89 21:46, 6 June 2017 (UTC)Reply
So maybe on hold until the discussion of the latter is closed.--115.27.203.95 10:55, 7 June 2017 (UTC)Reply
Delete. That RFD failed. I would have preferred to keep the entry, but I'm not comfortable with keeping the appendix either if the entry is unwanted. It makes it seem like the appendix namespace is a space for random trash. Either the phrase is good enough for the dictionary or it's not. --Daniel Carrero (talk) 03:51, 22 July 2017 (UTC)Reply
Here is the RFD for anyone who wants to read it. - excarnateSojourner (talk | contrib) 23:05, 11 April 2022 (UTC)Reply
Delete. --Barytonesis (talk) 14:33, 1 December 2017 (UTC)Reply
Please delete per above. --Soumyabrata (talksubpages) 07:49, 8 March 2020 (UTC)Reply
Keep per Mahāgaja. - excarnateSojourner (talk | contrib) 21:51, 11 April 2022 (UTC)Reply
@PUC Chuck Entz (talk) 03:09, 12 April 2022 (UTC)Reply
Delete. This was a silly entry outside the appendix since this hasn't ever come up in any casual conversation I've ever had. What makes this appendix-worthy either? What value does it add? This question doesn't seem to have been answered in any above keep votes. PseudoSkull (talk) 21:08, 12 April 2022 (UTC)Reply
@PseudoSkull: With due respect, that’s your problem. What if I showed you a YouTube video of a song (in a particular language) and say it is a beautiful language? ·~ dictátor·mundꟾ 14:38, 14 April 2022 (UTC)Reply
@Inqilābī For the phrasebook more than just one song would be needed. I never said the phrase never appeared anywhere, but that it's not nearly commonplace enough for me to consider it worthy of inclusion in a phrasebook, per evidence given in the last RFD. And my point here was, what makes the appendix then a proper place for this? What role does it fulfill for our readers? Who would look this up and why? PseudoSkull (talk) 16:09, 14 April 2022 (UTC)Reply
Delete, this is a totally random phrase, not idiomatic in any language as far as I can see. It was deleted from the phrasebook, so why should we keep it in the Appendix? There's enough useless junk there, we don't need a proliferation of translations of random phrases. If you want to know how to say that a particular language is beautiful, Google Translate will likely do just fine. This, that and the other (talk) 12:11, 30 September 2022 (UTC)Reply
I'm leaning towards delete, per Pseudoskull and This, that and the other. Doesn't seem to have a lot of value tbh. Acolyte of Ice (talk) 12:17, 30 September 2022 (UTC)Reply
Delete per This, that and the other. Graham11 (talk) 07:30, 24 November 2022 (UTC)Reply
Aside from whether this is worthy of inclusion, some of these may be word-for-word, grammatically clueless constructions. For example, Lithuanian "lietuviškas kalba yra graža" should be "lietuvių (or much less naturally, lietuviška) kalba yra graži". "graža" isn't even a word or inflection in Lithuanian at all. The Latvian translation means "Latvian-man language is beautiful". Rubbish. 98.170.164.88 07:40, 24 November 2022 (UTC)Reply
Weak keep as I find it interesting, but it needs checking and cleanup as 98.170 says. - -sche (discuss) 22:02, 30 July 2023 (UTC)Reply

Category:English four-letter abbreviations edit

There are only two pages that are in this category right now and all of the edits of this page were by the same person, so it should probably either start being used or be deleted. 24.13.226.156 18:56, 14 October 2017 (UTC)

The page isn't showing up for some reason it's https://en.wiktionary.org/wiki/Category:English_four-letter_abbreviations never mind I figured it out 24.13.226.156 19:06, 14 October 2017 (UTC)Reply

  Input needed
This discussion needs further input in order to be successfully closed. Please take a look!
Delete - this category is not useful. - TheDaveRoss 13:15, 9 April 2020 (UTC)Reply
TIFLL (anyone guess the meaning of this?) --Java Beauty (talk) 01:00, 31 August 2020 (UTC)Reply
I am going to take a guess. "This is five letters long.". John Cross (talk) 19:02, 17 December 2022 (UTC)Reply
Mild keep - can we just auto put in all four letter words that are all in uppercase letters? Facts707 (talk) 04:48, 12 March 2021 (UTC)Reply
Delete, not useful. Ultimateria (talk) 18:38, 28 November 2021 (UTC)Reply
Delete. — Fytcha T | L | C 21:57, 15 January 2022 (UTC)Reply
We also have two-letter abbreviations with 12 entries and five-letter abbreviations with 5 entries. (Three has over 300, but it looks like they have still been added manually.) - excarnateSojourner (talk | contrib) 17:01, 12 October 2022 (UTC)Reply

Template:el-future-form edit

This template is used for definitions that should not exist, as they are simply showing how the particle θα (tha) can be used with verb forms to create other forms. It would be like having a template for showing a definition at come for will come. —Μετάknowledgediscuss/deeds 04:27, 4 December 2017 (UTC)Reply

  • Well, it is a definition, because that's just how Wiktionary works. But it obviously doesn't deserve to be one. And I don't think it's that useful, because learners will have to apply a little grammar in order to conjugate, that's just how it is. Our job is just to provide and document the words, which these are not. —Μετάknowledgediscuss/deeds 07:03, 5 December 2017 (UTC)Reply
Now modified to give usage example - rfd removed. — Saltmarsh. 18:49, 6 December 2017 (UTC)Reply
That's a lot better, but I still think we'd be best off removing it altogether. I'm willing to accept this, but I'm reinstating the RFD because I'd prefer to let it run its course. —Μετάknowledgediscuss/deeds 20:02, 6 December 2017 (UTC)Reply
@Saltmarsh: I don't mean to hassle you, but why do you feel this is different from {{el-dep}}, which you agreed to see removed (as per the template talkpage linked above)? --Barytonesis (talk) 20:32, 6 December 2017 (UTC)Reply
@Barytonesis:My purpose was to illustrate a usage and its a shorter way of achieving this with resorting to {{ux}} which requires a translation. — Saltmarsh. 06:09, 7 December 2017 (UTC)Reply
Not necessarily, you can use {{ux|el|xxx|t=-}} --Barytonesis (talk) 15:04, 8 December 2017 (UTC)Reply

Category:en:Directives edit

Discussion moved from Wiktionary:Requests for moves, mergers and splits#Category:en:Directives.

This is a newly created (September 2017) topical category. It should be renamed to something that does not imply that it contains expressions that are directive. It contains terms that relate to direction or, more frequently, terms that can be confused with direction. I recognize that Direction would not be a suitable category name. I don't have any suggestion. It may be that the category is ill-conceived. DCDuring (talk)

I see nothing wrong with it. If it contained directive expressions, it would be called Category:English directives or similar. We have voted in the past to keep topical category naming distinct from other categories, so the naming scheme is considered indicative of its use/meaning/function. —Rua (mew) 20:37, 22 December 2017 (UTC)Reply
I'm not surprised that you see nothing wrong, what with the cat scheme being otherwise so perfect.
I favor keeping topical categories as far way as possible from our other entry categories.
But, unlike other categories that have names that are plural in form, Category:en:Directives contains neither examples nor names of the referents of its category name, ie of directives. It contains a dog's breakfast of terms that the categorizer, User:51.9.55.214, thought to be connected to some sense of the noun(?) directive. One mistake was to pick as name for a concept/category a de-adjectival noun. Probably the name was made plural to avoid confusion with the adjective.
If you can make sense of the rationale for the membership in the category of ban, bare minimum, beckoning, behest, besaiel, beseeching, bidding, bill, blacklist, blackmail, bloodlust, blueprint, booty call, boundary, boycott, breve, bribe, and bytecode, you, Gunga Din, are a better man than I. I am at a loss to understand the common element among these terms. Is each suppopsed to be a type of directive? If no one can come up with a better name for the category, or prune membership rationally, or split it into multiple comprehensible cateogries, or RfDO it, I will RfDO it. DCDuring (talk) 02:43, 23 December 2017 (UTC)Reply
Bytecode in the sense of compiler directive! Really pushing it a bit. Equinox 02:49, 23 December 2017 (UTC)Reply
Delete. This category seems ill-conceived to me. — SURJECTION / T / C / L / 19:05, 21 September 2023 (UTC)Reply
I agree with the nominator. (I cannot always make that claim after a multi-year gap.) DCDuring (talk) 00:14, 22 September 2023 (UTC)Reply
I think the category should either be renamed to CAT:Commands or at the very least, entires should be moved up to CAT:Communication. -- Sokkjō 06:38, 22 September 2023 (UTC)Reply
Delete: it seems unclear what the category should contain. — Sgconlaw (talk) 19:08, 22 September 2023 (UTC)Reply
Delete. Ill-conceived. Benwing2 (talk) 23:44, 12 October 2023 (UTC)Reply

2018 edit

Category:Languages of the Caucasus edit

Another one of these regional, rather than national, holding categories. See Category talk:Languages of the Middle East. —Μετάknowledgediscuss/deeds 05:29, 21 February 2018 (UTC)Reply

Delete --Per utramque cavernam (talk) 08:38, 27 February 2018 (UTC)Reply
@Metaknowledge: Couldn't you just speedy delete them at this point? --Per utramque cavernam (talk) 14:34, 5 March 2018 (UTC)Reply
Perhaps. I think they deserve due process. —Μετάknowledgediscuss/deeds 18:38, 5 March 2018 (UTC)Reply
Unlike the Middle East, the Caucasus is close-knit linguistic area with many shared traits. This is why one hardly ever hears about the “Middle Eastern languages”, but the Caucasian languages are very often referred to as such in linguistic literature. Guldrelokk (talk) 09:39, 6 April 2018 (UTC)Reply
While regional groupings of languages are of course useless in general, I think they have their merits in the case of Sprachbünde. The current name is poorly chosen and this category should be deleted but a category like Category:Languages belonging to the Caucasus Sprachbund is something I'd support. — Fytcha T | L | C 10:37, 13 March 2022 (UTC)Reply
Keep a shorter name like CAT:Caucasian languages. ·~ dictátor·mundꟾ 14:05, 14 March 2022 (UTC)Reply

February 2019 edit

Russian non-rhymes edit

(Notifying Atitarev, Benwing2, Cinemantique, Useigor, Wikitiki89, Stephen G. Brown, Guldrelokk, Fay Freak, Per utramque cavernam, Wittiami): Masculine rhymes in Russian require at least one consonant, either before or after the stressed vowel. In other words, вода́ (vodá) rhymes with когда́ (kogdá) (the rhyme is -dá) but not коса́ (kosá) (where the rhyme -sá; it would rhyme with небеса́ (nebesá)).

If the syllable ends in a consonant, the preceding consonant is not necessarily required: стол (stol) does rhyme with уко́л (ukól) (the rhyme is -ól; it's officially considered a "poor rhyme" (бедная рифма), but is nevertheless very widely used in poetry).

The following recently created non-rhymes need to be deleted and entries linking to them need to be cleaned up by a bot:

Rhymes:Russian/a, Rhymes:Russian/ɛ, Rhymes:Russian/i, Rhymes:Russian/o, Rhymes:Russian/u, Rhymes:Russian/e, Rhymes:Russian/ɨ, Rhymes:Russian/ɵ.

Tetromino (talk) 03:52, 27 February 2019 (UTC)Reply

@Tetromino OK. This isn't how things work in English but I'm completely ready to believe that Russian works differently. If others can confirm this, I'll do a bot run to fix things up. (The bot could handle the whole process of adding rhymes, potentially, if people think this is useful.) Benwing2 (talk) 04:04, 27 February 2019 (UTC)Reply
It's actually a little bit more complicated: the consonant doesn't need to match exactly: ловлю́ (lovljú) famously rhymes with на Ю (na Ju) because in this case a palatalized approximant [lʲ] in [lɐˈvlʲu] is "close enough" to the glide [j] in [nɐ‿ˈju]. But you need something consonant-ish there; -u by itself does not make a rhyme. Tetromino (talk) 04:26, 27 February 2019 (UTC)Reply
@Wittiami: Please note that your creations can be deleted. You should discuss these edits first. --Anatoli T. (обсудить/вклад) 19:28, 2 March 2019 (UTC)Reply
@Tetromino, @Atitarev: OK. I can reorganize all rhymes into subcategories in order to arrange every ultimate syllable accordingly to their preceding consonant. Also I think it is a nice idea to combine rhymes like люблю and на Ю with similar preceding consonants in one entry. Additionally I have already combined entries for /æ/ and /a/ sounds in one, analogously /ɵ/ and /o/. If my work here still make sense, I'll continue adding more rhymes and entries. Wittiami (talk) 19:59, 2 March 2019 (UTC)Reply
@Wittiami Even after you said you'd stop creating entries with rhymes like /a/, you are still doing it with туда́ (tudá) and сюда́ (sjudá). Note that in any case, adding rhymes is better suited to a bot than a human. Benwing2 (talk) 08:53, 3 March 2019 (UTC)Reply

March 2019 edit

Template:liv-compound edit

@Neitrāls vārds Similar logic appears here as for Template:sv-compound above. The usage is a bit less random as it's mostly used specifically for some suffix-like words used as the second component of a compound, but it's still used only on about 80 pages for about 7 components. The documentation gives the example of mīez, which is supposed to be equivalent to compounds with English -man, except that the latter *is* analyzed as a suffix, and I don't see why the same can't be done for these Livonian components. Benwing2 (talk) 19:16, 20 March 2019 (UTC)Reply

Judging by talk:-man there isn't exactly a consensus... And they have a point. By that logic who is to hold someone back from creating Bundes- and -republik and hundreds of other "prefixes", "suffixes".
Latviešu valodas gramatika says that "a sign of a tendency towards grammaticalization is weakening of the initial meaning and strengthening of generalized character(?)" (I guess what is meant is that the affixoid yields uniform results?) and apparently grammaticalization is a sign of an affixoid...
Or we can go by Nordisk leksikografisk ordbok referenced in affixoid and consider this case solved with -mō and -mīez being postfixoids.
I only want to know how I can get the derived terms at mō#Derived terms and mīez#Derived terms (this is assuming you would replace the template to be deleted with {{af}})? It's possible to tell {{suffixsee}} to show -mō and not take the page name which would be mō, right? (I have no interest in making entries for the "postfixoids" I think they're completely redundant on an entry level.) Neitrāls vārds (talk) 06:56, 22 April 2019 (UTC)Reply

Template:case-gov edit

Redundant to the much more widely used {{+obj}}. —Rua (mew) 17:06, 24 March 2019 (UTC)Reply

@Rua I am inclined to agree with you as it appears {{case-gov}} is used on < 10 pages and {{+obj}} is used on 300+ pages, but it's hard to tell for sure because {{+obj}} isn't properly documented. Can you fix this? Benwing2 (talk) 09:23, 25 March 2019 (UTC)Reply
@Rua It should be noted that we also have {{construed with}} (barely used) and {{indtr}} (used on over 500 pages, mostly Spanish and Portuguese) for the same purpose. Ideally we should have only one. Benwing2 (talk) 15:50, 31 March 2019 (UTC)Reply
@Rua, Benwing2 I hope I am right in assuming that {{case-gov}} will not be deleted before {{+obj}} is properly documented and ready for use. I feel that it might also be good if whatever we use linked to the case in the glossary (but that is a different discussion). PJTraill (talk) 00:23, 17 November 2022 (UTC)Reply
@PJTraill I have a total rewrite of {{+obj}} that I did a year or so ago. I need to find time to polish it a bit and push it to production. Benwing2 (talk) 06:02, 17 November 2022 (UTC)Reply
What about the categorisation? I see that {{+obj}} just adds to Language prepositions, while {{case-gov}} also adds to Language case prepositions, which seems useful to me. I imagine that is a small change, but I have not worked with Lua, and am a bit wary of modifying a moderately heavily used (~1,498 times) template+module. PJTraill (talk) 11:04, 17 November 2022 (UTC)Reply
This wouldn't just be used for prepositions though, would it? Sometimes you need to indicate the case governed by a verb (for instance, Latin incidō) or even another part of speech on occasion. This, that and the other (talk) 00:18, 18 November 2022 (UTC)Reply
I am not familiar with how these templates are used, but I see there are also {{+preo}} {{+posto}}, which I suppose are meant for pre- and postpositions. If {{+obj}} does all the work, it could be passed an argument indicating or implying which categories are wanted, or the caller could do it itself; I prefer the former as keeping in one place all the responsibility for categorisation. PJTraill (talk) 11:03, 18 November 2022 (UTC)Reply
Orphaned and deleted. Benwing2 (talk) 12:15, 2 March 2024 (UTC)Reply

April 2019 edit

Template:abstract noun of edit

This is used only in Thai, and seems to be used in addition to, but also instead of real definitions. Note diff: an editor has entirely removed the English definitions, replacing them with an incomprehensible "abstract noun" definition. The full definition is definitely preferable to this, so I think we should undo this and restore the original full definitions. —Rua (mew) 21:19, 1 April 2019 (UTC)Reply

Pinging @Miwako Sato, who seems to be the editor who removed all the definitions. —Rua (mew) 17:27, 14 April 2019 (UTC)Reply

  1. There had long been people who manually defined abstract nouns as "abstract noun of xxx", and then I imported this template from the Thai Wiktionary because it would more helpful than inserting such kind of definition manually.
  2. In my opinion, using this template is more useful than putting actual definitions. For example, the verb ตะแบง (dtà-bɛɛng) is defined as "(1) to cross; to twist; to intertwine; to plait. (2) to make or express (a remark, argument, etc) obliquely, evasively, or distortedly.", and its abstract noun, การตะแบง (gaan-dtà-bɛɛng), would be defined as "(1) an act or instance of crossing; an act or instance of twisting; an act or instance of intertwining; an act or instance of plaiting. (2) an act or instance of making or expressing (a remark, argument, etc) obliquely, evasively, or distortedly." So, just defining it as "abstract noun of ตะแบง (dtà-bɛɛng)" would be more appropriate. Moreover, there are terms that have no directly corresponding terms in English and there abstract noun definitions would need long and redundant descriptions. For example, the verb เสียอาการ (sǐia-aa-gaan) is defined as "to lose control of oneself, lose one's mind, or go crazy because of shyness, excitement, surprise, etc.", and its abstract noun forms are ความเสียอาการ and การเสียอาการ, which would be defined as "the condition of losing control of oneself, lose one's mind, or go crazy because of shyness, excitement, surprise, etc." and "an act or instance of losing control of oneself, lose one's mind, or go crazy because of shyness, excitement, surprise, etc.", respectively. Wouldn't a mere definition like "Abstract noun of เสียอาการ (sǐia-aa-gaan)" be more suitable?
  3. Anyway, those who regularly participate in Thai entries might be able to give more beneficial opinions on this: @Alifshinobi, GinGlaep, Octahedron80, Wyang
--Miwako Sato (talk) 16:39, 17 April 2019 (UTC)Reply

In Thai, an abstract noun is merely formed by placing "การ" (for action) or "ความ" (for condition) before any verb, adverb, or adjective and just covers all the senses that the verb, adverb, or adjective has. There's no need to add something which the OP described as "real definitions". This is the same thing as defining "flied" as "a simple past tense of fly" instead of defining "fly" as "to move in the air" and defining "flied" as "moved in the air". The template is applicable to any languages of similar structures, including Asian languages like Khmer, Lao, etc. The fact that it is now used in Thai and has not yet been used in other languages doesn't constitute a reason for its deletion. So, keep it. --YURi (talk) 19:36, 17 April 2019 (UTC)Reply

RE: Definitions/translations vs "abstract noun of". Which one?
I probably need to think more about this, but my current view is that a simpler approach should be used primarily. I am not a fan of unnecessarily complex approaches. So, "abstract noun of" should be used mainly, and a definition/translation should be provided only if it is needed. Defining/translating words that are equivalent to -ing words (e.g., การพูด (gaan-pûut) and การเดิน (gaan-dəən) = speaking and walking respectively) does not add much. So, definitions/translations should be provided only for (a smaller set of) words that really do need them (e.g., ความรู้ (kwaam-rúu) is defined in the Thai Wiktionary. Other words that should be defined/translated are ความถ่วง (kwaam-tùuang) and ความเร่ง (kwaam-rêng) etc.). These words, for those who do not speak Thai, have to be defined because they do not simply mean "the state of -ing (something)", or they may have specialized meanings. For example, ความรู้ (kwaam-rúu) does not simply mean "knowing," or "the state of being aware or informed." It means "knowledge," or "facts, information, and skills acquired by a person." It also has other meanings. Anyway, I am open to other views. If you have a strong argument for eliminating "abstract noun of," please share it.
--A.S. (talk) 20:06, 17 April 2019 (UTC)Reply

Other than Thai, this template was generally tended to serve many languages such as Northern Thai, Isan, Lao, Lü, etc, as it was used in Thai Wiktionary. (Indeed, they have all same abstract noun concept.) At the present, we made more specific templates for each language like "th-abstract noun of", "lo-abstract noun of", etc. For English Wiktionary, I suggest that the template could be renamed in same way (because it is just currently used with Thai entries).

It is not limited to have the "abstract noun of" only one line. More senses can be added. For example, th:ความเร็ว can have "abstract noun of" in meaning 1 and then scientific sense in meaning 2.

Additionally, use of template is beneficial for scripts and bots making more entries, as I do in Thai Wiktionary everyday. --Octahedron80 (talk) 01:53, 18 April 2019 (UTC)Reply

@Octahedron80, YURi, Miwako Sato The problem I have with these is that they are defined as lemmas. That means that they have the full status of independent word, and are not part of the inflection paradigm of another word. One expects lemmas to have proper definitions, and one would also expect to find lemmas in a typical dictionary with definitions given. If they were defined as non-lemmas, then it is understood that their meaning is tied to the meaning of the verb to which they belong, and that they generally are not given entries in the average dictionary but instead are grouped with the verb. A key in this question is also whether every verb has its own abstract noun. If there are many verbs that do not have abstract nouns, then they are better considered as lemmas as their existence is not predictable. They should have proper definitions then, rather than being labelled as "abstract noun". To say it another way, the treatment we give to them depends on whether we consider them a case of inflection or of derivation. Inflection is non-lemmas, derivation is lemmas. Inflection usually implies every verb has a fixed set of forms, while derivation is unpredictable and happens on a case-by-case basis.

If abstract nouns are inflectional, and thus non-lemmas and do not need a full definition, then it is still possible for them to have special senses. The same situation exists in English with participles and gerunds. On one side, they are verb forms, inflectional and thus non-lemmas, and their meaning is tied to that of the verb. But they can also sometimes "detach" from the verb and develop senses that are not shared with the verb. In these cases, the standard practice (that I have seen) has been to have Verb headings for the sense tied to the verb, and Noun or Adjective headings alongside it for senses that are separate from the verb. This practice could be applied to Thai too, then these abstract nouns could be defined simply as verb forms (non-lemma), with an additional Noun header (lemma) for cases where they have independent senses. Again, though, if abstract nouns are derivational, then they must have full definitions and should not use a template, as this is the standard for Wiktionary entries.

Separately from this, there is the question of whether abstract nouns need their own special template. We already have the {{inflection of}} template, which can easily handle any kind of inflection, making a separate template unnecessary. I also wonder if an abstract noun is not really just a verbal noun, for which a separate discussion exists below. It would be cleaner if we could make Thai use the verbal noun template instead of having its own separate one. But using {{inflection of}} would be even more preferable. —Rua (mew) 21:46, 24 April 2019 (UTC)Reply

Abstract noun (อาการนาม) is a type of noun and is used in sentences as noun, equivalent to English -ing or -ness. It is the umbrella term for verbal noun, adjectival noun, and adverbial noun (other languages may have more kinds). Almost verbs/adjectives/adverbs could be fix with การ/ความ to make the abstract nouns, with some exceptions: (1) The rule can only be found in nowaday/modern use. Dated or obsolete words do not have it. (2) It seldom applies on peotic/galant terms or long idioms/proverbs. (3) Some terms actually never form the abstract noun. They might be considered as (sort of unpredictable) non-lemmas because they are likety not given in published dictionaries, but they should not also have misrepresenting header tag, they must have noun instead of verb/adjective/adverb that would become incorrect part of speech. (I also speak upto other languages in the region that have same concept.)
I see {{gerund of|walk|lang=en}} in walking as lemma under noun tag, that is really equivalent to the abstract noun of in การเดิน. Why the gerund of can exist while the abstract noun of cannot?
FYI: There are five types of Thai noun: common noun (สามานยนาม), proper noun (วิสามานยนาม), collective noun (สมุหนาม; BTW we do not separate this), classifier (ลักษณนาม; someone calls counter, it is same), and abstract noun (อาการนาม). --Octahedron80 (talk) 03:42, 25 April 2019 (UTC)Reply

Seems worth keeping, but I agree that definitions/glosses should be provided. Not sure it would qualify as an "inflection of" anything. Ultimateria (talk) 18:51, 28 November 2021 (UTC)Reply

@Ultimateria, Octahedron80, Alifshinobi: To a first approximation, just saying 'abstract noun of' plus the entry for the verb is the definition. How this is to be interpreted is the task of a grammar. However, perhaps we do need to expand on this for individual languages. If there are language specifics, perhaps 'abstract noun of' should link to an appropriate section in the about page for a language. I'm not sure how we do this. A per language table of targets would be rather unwieldy, though I suppose we could include this in the language data; this would be a question for the greasepit. We could also link it through the glossary.
It's an inflection like the English gerund or -able form. It resembles the latter in that I'm not sure the split into actions and conditions is purely semantic - I suspect it's partly lexical, despite the words like รัก (rák) that have both forms. --RichardW57m (talk) 12:19, 1 September 2022 (UTC)Reply
From the above explanations, I get the impression that Thai การ (gaan) is equivalent to Vietnamese sự. If that’s the case, aren’t การ (gaan) + verb combinations completely SoP? (They may have idiomatic translations in English, of course, but that doesn’t make them idiomatic in Thai.) For Vietnamese sự there was a discussion long ago that ended with the deletion of all transparent sự + verb/adjective entries for being SoP. MuDavid 栘𩿠 (talk) 09:22, 13 July 2023 (UTC)Reply

Template:lv-inflection of edit

This is a duplicate of {{inflection of}} in terms of function and logic, except less capable. —Rua (mew) 17:12, 14 April 2019 (UTC)Reply

@Rua Don't worry, this is on my list. As it has > 106,000 uses, though, it's not high on the priority list, and some thought needs to go into whether we really want to deprecate such high-use templates. For references, here's a list of all the lang-specific form-of templates with >= 10,000 uses:
Aliased template Canonical template #Uses Comments (as of June 2023)
Template:es-verb form of Template:es-verb form of 441646 Converted to auto-determining template; < 100 old uses left.
Template:es-verb form of/subtense-pronoun Template:es-verb form of/subtense-pronoun 337361 < 10 uses left.
Template:es-verb form of/subtense-name Template:es-verb form of/subtense-name 337360 < 10 uses left.
Template:es-verb form of/indicative Template:es-verb form of/indicative 185279 < 10 uses left.
Template:es-verb form of/subjunctive Template:es-verb form of/subjunctive 144578 < 10 uses left.
Template:es-compound of Template:es-compound of 114260
Template:lv-inflection of Template:lv-inflection of 106703 Deprecated.
Template:eo-form of Template:eo-form of 99100
Template:pt-verb-form-of Template:pt-verb-form-of 94585 Obsoleted and deleted.
Template:ca-verb form of Template:ca-verb form of 78144
Template:es-verb form of/adverbial Template:es-verb form of/adverbial 63386 < 10 uses left.
Template:de-verb form of Template:de-verb form of 54762 Deprecated.
Template:fi-form of Template:fi-form of 54262 Deprecated.
Template:es-verb form of/imperative Template:es-verb form of/imperative 52546 < 50 uses left.
Template:ru-participle of Template:ru-participle of 47321 Deprecated.
Template:de-inflected form of Template:de-inflected form of 46670 Deprecated.
Template:pinyin reading of Template:pinyin reading of 40032 Obsoleted and deleted.
Template:el-form-of-nounadj Template:el-form-of-nounadj 31509
Template:nl-verb form of Template:nl-verb form of 30619 Deprecated.
Template:bg-verb form of Template:bg-verb form of 30114 Deprecated.
Template:en-past of Template:en-past of 28731
Template:pt-verb form of Template:pt-verb form of 28730 Entirely converted to auto-determining template.
Template:nl-noun form of Template:nl-noun form of 27827 Deprecated.
Template:en-third-person singular of Template:en-third-person singular of 26977
Template:es-verb form of/participle Template:es-verb form of/participle 24257 Obsoleted and deleted.
Template:ja-romanization of Template:ja-romanization of 16472
Template:pt-adj form of Template:pt-adj form of 15455 Deprecated.
Template:io-form of Template:io-form of 10429
Template:sv-noun-form-def Template:sv-noun-form-def 10063 Deprecated.
Benwing2 (talk) 22:48, 14 April 2019 (UTC)Reply
Ok, I'll leave them to you then. Thank you for the work! —Rua (mew) 22:50, 14 April 2019 (UTC)Reply
Delete - yes, agreed. Get rid. Theknightwho (talk) 11:05, 27 May 2022 (UTC)Reply
Deprecated. I also marked the status of the other templates in the above table. Benwing2 (talk) 07:04, 25 June 2023 (UTC)Reply

Category:Mongolian pronunciation spellings edit

Phonetic respellings should be handled differently. We normally don't have entries for words, which are phonetic representations of another word, unless they are attestable common respellings. It is useful to show them (unlinked), though, as in баярлалаа (bajarlalaa) (this revision). If pronunciation module for Mongolian is eventually developed, these spellings can be used as parameters. Someone suggested displaying respellings in the headword, as in Nelai फूल (phūl), which says "pronounced फुल (phul)" --Anatoli T. (обсудить/вклад) 01:27, 29 April 2019 (UTC)Reply

I'd RFV these individually; it's possible that the pronunciation spellings are actually used in writing as misspellings (though then they should be changed to {{misspelling of}} or {{alternative spelling of}} depending on how standardized Mongolian spelling is). —Mahāgaja · talk 05:35, 29 April 2019 (UTC)Reply
Oh, and I don't like the solution at Nepali फूल (phūl). That info belongs in the Pronunciation section, not the headword line. For Irish I do sometimes write "as if spelled XYZ" after the IPA in the pronunciation section. —Mahāgaja · talk 05:42, 29 April 2019 (UTC)Reply

May 2019 edit

Template:feminine equivalent of edit

Redundant to {{female equivalent of}}. It is not at all clear what a "feminine equivalent" is. If it refers to grammatical gender, then what distinguishes a "feminine equivalent" from a general alternative form whose grammatical gender is feminine? —Rua (mew) 19:00, 30 May 2019 (UTC)Reply

Also @Fay Freak who was previously engaged with this user. —Rua (mew) 19:01, 30 May 2019 (UTC)Reply

Judging from the two uses of this template, the intent is not grammatical gender. What would be a suitable alternative name for referring what is often referred to as natural gender? DCDuring (talk) 20:43, 31 May 2019 (UTC)Reply
It's not redundant at all as there is a huge difference between gender (of words) and sex (of things and living beings).
English actress (no gender; refering to someone with female sex) is the female equivalent of actor (no gender),
while German terms in (...-er)-in (feminine gender; female or no sex at all) are the feminine equivalent of terms in -er (masculine gender; male, female, unknown or no gender). Real-life examples:
  • "Lenin sah in der Partei die Führerin und Lehrerin der Massen" - Führerin and Lehrerin are feminine but here refer to a sexless thing.
  • "ein weiblicher Lehrer" (sg.), "weibliche Lehrer" (pl.) - Lehrer is masculine but here refers to female beings.
  • "männliche und weibliche Lehrer", "Lehrer beiderlei Geschlechts" - Lehrer is masculine but here refers to male and female beings.
  • "der Glaub ist der Führer der Hofnung" - Führer is masculine but here refers to a sexless abstract thing.
--B-Fahrer (talk) 19:00, 6 April 2020 (UTC)Reply
@B-Fahrer, Fay Freak, DCDuring, Rua I don't really see the point of having separate templates {{feminine equivalent of}}/{{female equivalent of}} and {{feminine noun of}}. All the templates are in practice used equivalently. The three examples above of Lehrer/Führer are irrelevant as they refer to the masculine form, which in many languages can also be used of female beings. The feminine form Lehrerin, as far as I can tell, does normally refer to female beings. All examples on Glosbe of Führerin [4], for example, refer to women. It seems clear to me that the above example where Lehrerin and Führerin are used to refer to a political party is a marginal case as well as a clear example of personification. It is comparable to the use of she in English to refer to boats, airplanes, countries, etc. and he to occasionally refer to various programming language constructs; this does not change the fact that he and she are natural-gender pronouns. As a result I am planning on merging these templates. Benwing2 (talk) 03:25, 1 October 2020 (UTC)Reply
BTW I thought about this a bit more. There are cases in German like Herstellerin (manufacturer) that are often used of non-human entities (in this case, companies) and cannot be called personifications. (Sammlerin (collector) is claimed to be another instance, although the examples in Glosbe [5] all appear to refer to women.) This situation appears to be specific to German, and exceptional even in that language, where most words in -erin do appear to refer primarily to women. In my opinion, words like Herstellerin should not use {{female equivalent of}} or any other similar variant, but should simply be defined as "manufacturer", possibly with a usage note indicating that they are normally used only to refer to feminine nouns (if that is indeed the case). If Sammlerin can equally refer to a woman who is a collector or to a non-human feminine-gender collecting object, it should have two definitions, one with {{female equivalent of}} and the other defined as [[collector]] {{gloss|object that collects}} or similar, with a usage note. Benwing2 (talk) 04:48, 3 October 2020 (UTC)Reply
glosbe doesn't matter in any way; and as for Sammlerin it has examples not refering to women but to forager bees:
  • Wenn eine Sammlerin eine neue Nektarquelle findet, kehrt sie zum Bienenstock zurück, um die gute Nachricht zu übermitteln.
    Mockingly ]The duck may swim on the lake, but my daddy owns the lake [this english text is no translation]
  • Andere Arbeiterinnen, gleich welchen Alters, unternahmen vergleichsweise wenige Sammelflüge, solange eine aktive Sammlerin vorhanden war.
    It was great [this english text is no translation]
BTW some entries with good examples that show that it is about gender (masculine/feminine) and not sex (male/female):
Also related: Blaue
--B-Fahrer (talk) 07:32, 3 October 2020 (UTC)Reply
@B-Fahrer You are 100% not listening to what I'm saying. Since the predominant usage of {{feminine noun of}}, {{female equivalent of}} and {{feminine equivalent of}} is to refer to female beings (which BTW includes bees), they should be used for this purpose and not distorted due to vagaries of German. Wiktionary needs to cater to all languages, not just to German. Please reread what I said about (a) masculine nouns referring to female humans (irrelevant for this discussion as they don't use {{female equivalent of}}), (b) feminine and neuter nouns referring to male humans (similarly irrelevant), (c) personification, (d) nouns in -in that refer to things other than female beings (which should do something else than use {{female equivalent of}}). BTW feel free to use {{feminine of}} if the primary meaning of a given word does *not* refer to female beings. Benwing2 (talk) 16:42, 3 October 2020 (UTC)Reply
Also, normal practice when giving quotes or usage examples is to include a translation into English; please do so in the future, thanks! Benwing2 (talk) 17:02, 3 October 2020 (UTC)Reply
Well, for different languages there can be different templates or approaches if the languages are different.
(a) & (b) It's relevant for the related issue with {{de-noun}} and its incorrect text for the parameters m= and f=.
(c) "and cannot be called personifications" - indeed.
(d) "which should do something else than use {{female equivalent of}}" - indeed, as that's incorrect as shown by the examples.
(Quotes) It's also normal practice to not provide translations (whatever the reasons may be, like lazyness or lack of time, lack of translation skills or vocabulary), although it's indeed nice to have them. --B-Fahrer (talk) 09:41, 5 October 2020 (UTC)Reply

February 2020 edit

Template:zh-obsolete edit

Like anything using title text, this is really awful from a usability perspective. It also stands out from normal Wiktionary practice, which is to use context labels. A context label would make it immediately clear what it means. —Rua (mew) 10:01, 29 February 2020 (UTC)Reply

I support making it more "standard" and less awful UX-wise, but how? It is a long tooltip.Suzukaze-c 19:50, 9 March 2020 (UTC)Reply
Labels commonly link to a glossary. Couldn't that be done here too? It doesn't have to be Appendix:Glossary, language-specific pages can be a thing too. —Rua (mew) 19:52, 9 March 2020 (UTC)Reply
I guess we can also do {{lb|zh|literary|or|Cantonese|...}}. —Suzukaze-c 19:51, 9 March 2020 (UTC)Reply
If that conveys the same thing, then I think it's fine. —Rua (mew) 19:53, 9 March 2020 (UTC)Reply
Could something be added to the section that the references template or something else that us used on most or all pages that identifies what the template means? I saw both this template and the "††" symbol for the "zh-hg" template on the page 我#Chinese, and had no idea what they meant. Jimw338 (talk) 23:06, 7 September 2021 (UTC)Reply
What is the difference between Template:zh-obsolete and Template:zh-no-solo? It seems that only one needs to stay. Or maybe make it redirect. Some characters (eg. 子#Chinese) have both templates and it's very confusing. Betty (talk) 13:28, 10 October 2021 (UTC)Reply
Delete. The title text does not even appear for me when I mouse over any more, and an anon has reported that they don't know what the symbol could possibly mean. We need to bring Chinese entries more in line with the dictionary as a whole, which seeks to communicate plainly and clearly rather than obfuscate with cute symbols. —Μετάknowledgediscuss/deeds 20:53, 4 November 2021 (UTC)Reply
Delete. I support using clearer labels, such as those that @Suzukaze-c has suggested above. — justin(r)leung (t...) | c=› } 23:24, 4 November 2021 (UTC)Reply
Delete per Metaknowledge, though it do appear for me. It is space-efficient but we have the space to spell it, and if we don’t then due to the other uses of that dagger I still prefer Todesrune in a print-out version of this dictionary, but here it is still safest to just spell it out (although this creates the problem to distinguish obsolete, archaic and dated, then probably use other words such as “outmoded” if you are too judgementless to distinguish thus far …). Fay Freak (talk) 10:11, 6 November 2021 (UTC)Reply
I support changing the template to be equivalent to {{lb|zh|obsolete}}, but deleting a widely used template breaks old versions of pages. Vox Sciurorum (talk) 17:12, 8 November 2021 (UTC)Reply
Delete. Very confusing label. Hope that I'm not too late to discussion. The obvious way would be to spell them in {{lb}}, but I think when there are multiple senses repeating the same {{lb|zh|obsolete}}, it is better to list them as a subsense under a sense that just says {{lb|zh|obsolete}}, as demonstrated here Special:Diff/68565444. (Obviously it should be templatized if done in this way)
I should also note that these labels are sometimes used outside of definitions and not in templates, such as in the {{zh-forms}} at . How should we deal with them? -- Wpi31 (talk) 08:29, 12 August 2022 (UTC)Reply
Delete. The dagger character can have other uses, such as an asterisk-like function, so it's better to write obsolete in a label. Soap 09:56, 19 December 2022 (UTC)Reply
Delete this template along with the similar ones listed below. Fancy symbols like these just make the dictionary harder to understand and edit. Glades12 (talk) 22:06, 26 December 2022 (UTC)Reply

Template:zh-o, Template:† edit

and redirects. —Suzukaze-c (talk) 23:28, 4 November 2021 (UTC)Reply

Delete. — justin(r)leung (t...) | c=› } 16:28, 8 November 2021 (UTC)Reply

Template:zh-historical-dict, Template:zh-hd/s, Template:zh-no-solo edit

ilk —Suzukaze-c (talk) 23:28, 4 November 2021 (UTC)Reply

These are even obscurer and should the more be deleted. The verbal equivalent of Template:zh-historical-dict “is per the record found in one or more historical dictionaries. It does not necessarily have citations” is elsewhere “Lex.”, for Template:zh-no-solo and Template:zh-obsolete it is “obsolete except in compounds”. Fay Freak (talk) 10:11, 6 November 2021 (UTC)Reply
Delete. — justin(r)leung (t...) | c=› } 16:28, 8 November 2021 (UTC)Reply
Delete for the reasons above. Frankly, we should be incorporating the functionality of all of the zh templates into the generic templates wherever there's an equivalent. Theknightwho (talk) 11:09, 27 May 2022 (UTC)Reply

April 2020 edit

Category:Languages of California edit

I don't think we need to be any level lower than countries... Ultimateria (talk) 02:37, 13 April 2020 (UTC)Reply

California at one time probably had about a hundred indigenous languages and represented the intersection of the Algic languages (which extend to the east coast), the Athabascan languages (which extend from Alaska to northern Mexico), the Uto-Aztecan languages, (which extend to Central America), a few still-to-be-proven language families like Hokan and Penutian, and a few probable isolates like the Chimariko language and the Karuk language, with a very high percentage endemic to the state. Right now the category contains only one language which was added by a clueless editor based on a bogus etymology, but we already have hundreds of entries in upwards of 5 dozen indigenous languages- about a fifth of Category:Languages of the United States. I should also mention that we have Category:Languages of Hawaii, among others. Chuck Entz (talk) 04:04, 13 April 2020 (UTC)Reply
Make that over a thousand lemmas. Chuck Entz (talk) 04:26, 13 April 2020 (UTC)Reply
I've now added 58 indigenous languages to the category, which I will, of course, remove if we decide to delete. Chuck Entz (talk) 05:20, 13 April 2020 (UTC)Reply
What about nonindigenous languages? Besides English and Spanish, Chinese, Korean, Vietnamese, and Tagalog are all widely spoken in California. —Mahāgaja · talk 08:16, 13 April 2020 (UTC)Reply
Yes, and I've been to stores with signs in Arabic, Armenian, Hebrew, Hindi, Indonesian, Japanese, Persian, Russian and Thai, and I've met people from Greek, Malagasy, Samoan and Tongan communities as well. The Los Angeles County election websites can be viewed in Spanish, Chinese, Tagalog, Hindi, Khmer, Korean, Vietnamese and Thai, and American Sign Language interpreters are in considerable demand. I understand that we have lots of people speaking American Indian languages from the rest of the US and from other parts of the Americas. I've even heard of a radio station somewhere in the Central Valley broadcasting in Assyrian Aramaic. I should add that I know there are lots of people speaking other South Asian languages than Hindi and other Chinese languages than Mandarin, but I don't know which ones. Chuck Entz (talk) 10:16, 13 April 2020 (UTC)Reply
So how do we decide what to include and what not to? And really, that question applies not only to this category but also to country-level categories like CAT:Languages of the United States. —Mahāgaja · talk 10:51, 13 April 2020 (UTC)Reply
I don't know, but I disagree with categorizing Category:American Sign Language into Languages of California. ASL is used in all 50 states. I don't think it needs to be in potentially 51 location categories when 1 covers that same information. Leave the demographic specifics to Wikipedia. Ultimateria (talk) 01:41, 16 April 2020 (UTC)Reply
English and Spanish are spoken in all 50 states too. And they're spoken in other countries as well; does that mean they shouldn't be in CAT:Languages of the United States? —Mahāgaja · talk 05:47, 16 April 2020 (UTC)Reply
That's what I'm arguing for, rather than put e.g. Spanish in 300 categories for all the states of the US and South American countries. Ultimateria (talk) 16:21, 17 April 2020 (UTC)Reply
Delete because it is ambiguous. If we talk about native languages we go also beyond the current state borders and might think about the California of the now United Mexican States. Fay Freak (talk) 15:14, 13 April 2020 (UTC)Reply
Deletion for the reason given immediately above is completely inappropriate. The rationale would suggest renaming. "Early languages...", "Pre-Columbian languages..." might work for the instant case.
We use current governmental borders for categories such as this because of the administrative processes that govern almost all the research on such matters and because that is how most of our users would approach the subject matter. California may secede after the coming election so it would seem prudent to wait before any rash deletion or renaming. DCDuring (talk) 17:13, 13 April 2020 (UTC)Reply
California might secede? Even then there is still a different California. I am not sure that we use governmental borders. Many who use these categories think that. Fay Freak (talk) 20:58, 13 April 2020 (UTC)Reply
That's Baja California, not California. Don't conflate etymology with meaning. Theknightwho (talk) 09:27, 30 August 2022 (UTC)Reply
Keep per Chuck Entz as it's important to have the indigenous languages there. AG202 (talk) 01:36, 14 March 2022 (UTC)Reply
  • Keep: It is so well populated now that it is not overly precise. — excarnateSojourner (talk · contrib) 06:03, 16 February 2023 (UTC)Reply
  • Keep because it seems useful to have a category of indigenous languages. That said, I'm not sure about cases like Mandarin, Tagalog, Korean, and Vietnamese, all currently in the category. Worth noting that neither English or Spanish currently are in the category, and they undoubtedly have the most speakers. I can see a case for including these non-indigenous languages, but if we were to admit any language that has a community of speakers in California then the category would probably stop being useful, even though I suspect there may be more speakers of Icelandic in California than of Valley Yokuts. Not sure where the line should be. There might be a case for only including languages that are (semi-)unique to California, which would probably limit the category to indigenous languages. There might also be a case for having separate categories for indigenous and non-indigenous. Or we could just hope that having all indigenous languages + maybe the top ten non-indigenous is a sane heuristic and hope nobody decides to add Icelandic. (This issue is not by any means unique to California, and I'm not sure whether there's a general rule that's been agreed upon.) 70.172.194.25 06:57, 16 February 2023 (UTC)Reply
    Maybe the rule should be indigenous to California OR speakers per capita in California >> speakers per capita in US, which would exclude English but plausibly include those Asian languages. There may still be some disagreement about what ">>" means, however, as I assume Spanish is spoken at a greater rate per capita in California than in the US as a whole, but it seems weird to include Spanish but not English. I don't have a fully satisfactory answer. 70.172.194.25 07:10, 16 February 2023 (UTC)Reply
Rename to Cat:Indigenous languages of California etc and remove the non-indigenous (post-European colonisation) languages. That would make for a more meaningful category per the IP above. I see no value in categorising colonial and migrant languages by state, province, etc. This, that and the other (talk) 10:12, 23 November 2023 (UTC)Reply
Actually, this is a much better idea. Support the above. AG202 (talk) 13:28, 23 November 2023 (UTC)Reply
I also Support, I think this is a useful category, whereas including non-indigenous languages is unworkable.--Urszag (talk) 11:36, 6 January 2024 (UTC)Reply
Keep: states have a variety of languages and this saves space in the main category. The Australia category is big too, so I'm creating some for Australian states and territories (the NT will probably have the biggest category because of all the living Indigenous languages there). 2001:8004:2778:4E8D:40F:54A0:A43F:F695 08:16, 6 January 2024 (UTC)Reply
However, except for subregional dialects, I think we should just stick to putting languages spoken mostly or exclusively in that state or territory (so in the instance for Hawaii, Category:Hawaiian English would absolutely fit in Category:Languages of Hawaii, but Category:English language or Category:American English would not. 2001:8004:2778:4E8D:40F:54A0:A43F:F695 08:20, 6 January 2024 (UTC)Reply

August 2020 edit

Template:sla-pro-root-h₁rewdʰ edit

@Useigor, this looks like an aborted experiment? PUC11:02, 19 August 2020 (UTC)Reply

Boo. You can use {{root}}. --{{victar|talk}} 03:32, 20 August 2020 (UTC)Reply
The deletion notice shows up in the pages transcluding the template. This is very confusing. I think that the deletion template should be wrapped in a noinclude tag. 217.197.198.196 08:08, 8 April 2021 (UTC)Reply
As it now is. DCDuring (talk) 15:05, 8 April 2021 (UTC)Reply

October 2020 edit

All templates in Category:Chinese headword-line templates except Template:zh-noun edit

@Atitarev, Rua, Suzukaze-c With the exception of {{zh-noun}} and {{zh-punctuation mark}}, every one of these is a trivial wrapper around {{head}}. {{zh-verb}}, for example, is defined simply as follows:

{{head|zh|verb}}<noinclude>{{documentation}}</noinclude>

This proliferation of trivial templates doesn't accomplish anything, so I think they should all be orphaned and deleted/deprecated. From the history, they were all created by User:Atitarev, and at the time they seem to have done something useful using {{zh-pos}}. However, this is no longer the case, and {{zh-pos}} itself no longer exists. Note that {{zh-punctuation mark}} is defined in terms of {{meta-punctuation mark}}, but doesn't appear to do anything that couldn't be accomplished just as easily using {{head|zh|punctuation mark}}.

Specifically, using the "rule of 1000" that I normally follow, I propose to orphan and delete the templates with fewer than 1000 uses, and orphan and deprecate (using {{deprecated code}}) the ones with 1000 or more uses. Benwing2 (talk) 06:21, 2 October 2020 (UTC)Reply

@Benwing2: I have no objection to orphaning and deleting. @Justinrleung, Suzukaze-c. -- User:Atitarev 06:49, 2 October 2020 (UTC)Reply
I'm down with deleting them. I personally don't like these functionally 'neutered' headword templates either. —Suzukaze-c (talk) 07:09, 2 October 2020 (UTC)Reply
In addition, the parameters of {{zh-noun}} are actually deprecated, and the content should be moved to {{zh-mw}}, which is more flexible. —Suzukaze-c (talk) 07:40, 2 October 2020 (UTC)Reply
Making sure other Chinese editors are aware of this potential change (because I somehow didn't get @Atitarev's ping above until @Tooironic told me about it): @Mar vin kaiser, Geographyinitiative, RcAlex36, The dog2, Frigoris, Apisite. — justin(r)leung (t...) | c=› } 04:47, 4 October 2020 (UTC)Reply
I support deleting all templates in Category:Chinese headword-line templates except Template:zh-verb (see Wiktionary:Beer parlour/2020/July#Inner structure of a Chinese verb - not supported now, but may be supported in the future). -- 10:17, 4 October 2020 (UTC)Reply
@沈澄心: Apologies for forgetting you above. You do bring up a good point. I do wonder if it may be better for us to do it on a definition-by-definition basis, like we do with {{zh-mw}}, though. Is it possible for a verb to be more than one type? This reminds me that I forgot about @恨国党非蠢即坏, Thedarkknightli, Michael Ly. — justin(r)leung (t...) | c=› } 12:17, 4 October 2020 (UTC)Reply
@Justinrleung: 出櫃 seems to be both. —Suzukaze-c (talk) 12:27, 4 October 2020 (UTC)Reply
@Suzukaze-c: Exactly what I'm looking for. The first sense is separable (verb-object specifically), but the second sense is not. I think this is a good case for having it in {{lb}} rather than {{zh-verb}}. — justin(r)leung (t...) | c=› } 12:31, 4 October 2020 (UTC)Reply
@Justinrleung: No. This is another Chinese grammar phenomenon. When a "verb-object" verb is followed by another object, it becomes unseparable. This rule applies to all transitive senses of all "verb-object" verbs, including 加速 mentioned below. There is no point to repeat stating a general rule in every definition. Also, this does not change the "verb-object" nature of the verb and it becomes separable again if the the object is omitted, regardless of the sense used. Thus I oppose the definition-by-definition format. 恨国党非蠢即坏 (talk) 13:42, 4 October 2020 (UTC)Reply
... although there is also the issue of using a dot or slashes to demarcate where we can separate the verb. — justin(r)leung (t...) | c=› } 12:34, 4 October 2020 (UTC)Reply
@Justinrleung: Another example is 加速 (per Xiandai Hanyu Cidian). Also, 糊口 is separable in Classical Chinese (Zuozhuan: “寡人有弟,不能和協,而使於四方。”, Shiji: “伍子胥橐載而出昭關,夜行晝伏,至於陵水,無以……”), but in Modern Standard Chinese, it's not. -- 13:13, 4 October 2020 (UTC)Reply
@沈澄心: 糊口 is in fact separable. The reason why we rarely see expressions like 糊了口 is a semantical one, not a grammatical one. 糊口 describes a habitual and ongoing action, thus there is usually no need to attach tense/aspect particle to it, which is the most frequent case of a modern Chinese verb to separate. 恨国党非蠢即坏 (talk) 13:42, 4 October 2020 (UTC)Reply
@恨国党非蠢即坏: Yeah, there seem to be some ghits for 糊著口, so it is separable. I guess there are grammatical restrictions that make verb-object constructions inseparable if it takes an object, but when that happens, I don't know if we should still treat it a verb-object construction. It's not like 出 is ditransitive in transitive 出櫃, nor is transitive 出櫃 functioning as verb + object anymore from how I see it. I'm not familiar with how people have dealt with these, but I think we probably need some scholarly sources to back up our decisions. I still think definition-by-definition is a safer way to go in case there are cases where a compound could be both separable and inseparable. — justin(r)leung (t...) | c=› } 16:52, 4 October 2020 (UTC)Reply
@Justinrleung: It is very evident in the 把 structure and the passive voice that they are still verb-objects and separable.
我曝光了他们干的事。
我把他们干的事曝了光
他们干的事被我曝了光
The only key point is whether they are directly followed by another object. Of course they are not ditransitives. They simply don't work that way. 恨国党非蠢即坏 (talk) 17:53, 4 October 2020 (UTC)Reply
@恨国党非蠢即坏: Okay, that makes sense. I can also find some ghits for google:"把*加了速". Then we should keep {{zh-verb}} and implement the verb compound categorization soon. — justin(r)leung (t...) | c=› } 03:17, 5 October 2020 (UTC)Reply
@Justinrleung, 恨国党非蠢即坏 We also have {{tlb}} for adding a label after a headword to indicate that it applies to all definitions. That could potentially be used here, and has the advantage that {{lb}} could be used if there are cases where the compound verb has different structures per-definition. OTOH this doesn't allow for adding a dot or slash to indicate where the separation point is. Benwing2 (talk) 04:40, 5 October 2020 (UTC)Reply
@Benwing2: Yes, thanks for bringing that up. I thought of it but forgot to mention it. We could use the |head= to show where the separation point is, but it'd be nice to have a template so that the formatting could be more easily standardized. — justin(r)leung (t...) | c=› } 04:49, 5 October 2020 (UTC)Reply
@Justinrleung: This is fine with me. Benwing2 (talk) 04:51, 5 October 2020 (UTC)Reply
I am not familiar with the coding so I don't have any particular opinions now. 恨国党非蠢即坏 (talk) 07:35, 5 October 2020 (UTC)Reply

──────────────────────────────────────────────────────────────────────────────────────────────────── I obsoleted/orphaned all except {{zh-noun}}, {{zh-verb}} and {{zh-hanzi}}. Maybe {{zh-hanzi}} should go as well; I figured it might be marginally easier to remember {{zh-hanzi}} than {{head|zh|Han character}}. I deleted all the ones with < 1000 uses, and deprecated the remainder (which includes only {{zh-adj}}, {{zh-adv}}, {{zh-idiom}} and {{zh-proper noun}}). Benwing2 (talk) 21:29, 10 October 2020 (UTC)Reply

Might be worth updating {{head}} to include the alias Hanzi for Han character? Theknightwho (talk) 11:14, 27 May 2022 (UTC)Reply

December 2020 edit

Just stumbled upon their WP articles which has been removed from mainspace as spurious (and the original retained for historical reference), so it's time to delete their language family category, including the Category:Proto-Sunda-Sulawesi language, and rearrange the Malayo-Polynesian family tree.-TagaSanPedroAko (talk) 07:27, 1 December 2020 (UTC)Reply

@Metaknowledge, Fay Freak, SemperBlotto, DTLHS: Can you take a look on this? -TagaSanPedroAko (talk) 04:13, 2 December 2020 (UTC)Reply
My understanding is that the Malayo-Polynesian family tree is more like a lawn. Aside from Oceanic, there are lots of smaller local groups and there's Malayo-Polynesian, but no real structure in between. Chuck Entz (talk) 04:35, 2 December 2020 (UTC)Reply
@Chuck Entz: There 's a Western Malayo-Polynesian family (and a Proto-Western-Malayo-Polynesian protolanguage) proposed by Blust that lumps all those currently grouped under Borneo-Philippines and Sunda-Sulawesi here into a single family, but it's mostly geographical and discredited. I agree with your point. --TagaSanPedroAko (talk) 05:30, 2 December 2020 (UTC)Reply
  • If the scholarly consensus is that these nodes are invalid, then I agree we should delete them and associate their daughters directly with Malayo-Polynesian, but there will be widespread consequences, including deleting all of the Proto-Sunda-Sulawesi lemmas. —Mahāgaja · talk 09:12, 2 December 2020 (UTC)Reply
    • Most of those are only present due to their easy availability via Blust's Austronesian Comparative Dictionary. I use that a lot for data on languages, but I don't trust its reconstructions unless I can find confirmation elsewhere. Blust is notorious for using software designed for cladistics in biology on lexicostatic data.
    • As you know, it's possible to reconstruct a protolanguage for any assortment of languages that are related at all, and coincidental patterns of presence or absence of reflexes as well as borrowing can make these reconstructions different for different arbitrary groupings even though they share the same latest common ancestor. I'm sure Proto-English-Italian-Romanian and Proto-Engliah-French-Spanish would look different, even though the only common ancestor for both is Proto-Indo-European. Chuck Entz (talk) 05:39, 3 December 2020 (UTC)Reply
Looking over our PSuSw lemmas, most of them are just trivial rewritings of PMP lemmas anyway, and the sole exception is actually continued solely in Malayo-Chamic *bagus. I don't know what has motivated creating Sunda-Sulawesi and also intermediate Malayo-Sumbawan entries for this, did someone perhaps originally miss Blust's note that the reflex in Rembong (spoken on Flores) should be considered a loan from Malayic rather than inherited? --Tropylium (talk) 18:29, 3 December 2020 (UTC)Reply
@Chuck Entz, Mahagaja, Tropylium I've been fixing Austronesian reconstructions to get rid of Borneo-Philippines and PSuSw, and some IP working on the same area reverted my change for *buʀuk. I think there should be already be a resolution here.
In addition to Borneo-Philippines and Sunda-Sulawesi, should we also delete these families as well?
  • Malayo-Sumbawan (proposed by K. Adelaar. Includes Malayic and Chamic, Bali-Sasak-Sumbawa, Sundanese and Madurese)
    • Malayo-Chamic (rather two separate families directly grouped with MP)
--TagaSanPedroAko (talk) 01:49, 19 December 2020 (UTC)Reply
Related discussion: Wiktionary:Requests_for_deletion/Non-English#Proto-Sunda-Sulawesi. –Austronesier (talk) 12:04, 1 January 2022 (UTC)Reply
The recent RFV of the term Proto-Sunda-Sulawesi has reminded me of this. It looks like we only have a few lemmas left to remove? (And then perhaps etymologies to update... and so many categories to delete...) - -sche (discuss) 06:32, 28 December 2022 (UTC)Reply

April 2021 edit

Module:template utilities edit

Unused. Created by @Kephir in 2014 and enlarged this year by @Huhu9001 with some potentially useful stuff, but is it actually useful enough that anyone is going to bother using it? —Μετάknowledgediscuss/deeds 00:06, 27 April 2021 (UTC)Reply

Abstain. -- Huhu9001 (talk) 10:20, 27 April 2021 (UTC)Reply
Keep. It is used now. -- Huhu9001 (talk) 09:03, 21 March 2023 (UTC)Reply
The template parsing code there seems to be supplanted by Module:templateparser. — SURJECTION / T / C / L / 11:32, 19 June 2022 (UTC)Reply
Delete and merge with Module:templateparser. We should not have multiple modules doing the same thing. IMO User:Huhu9001 should not have expanded this module and started using it but instead should have added any missing functionality to Module:templateparser. Benwing2 (talk) 07:06, 20 July 2023 (UTC)Reply
Delete - I am working to deprecate this now. Theknightwho (talk) 09:57, 23 February 2024 (UTC)Reply

September 2021 edit

Template:he-wv edit

This template pushes headword-line information off the headword, which makes entries unnecessarily messy, and is a practice seen nowhere else in the dictionary (and certainly not in other Semitic languages, like Arabic). As an example, take a look at how the entry מודה changed from a messy version using {{he-wv}} to its current, neater state with the structure standardly found on Wiktionary. —Μετάknowledgediscuss/deeds 03:22, 6 September 2021 (UTC)Reply

In your example the template was in the definition line, however it is used in pronunciation sections: isn’t the usage in pronunciation sections as on מלך about the thing we need for Arabic entries presenting multiple vocalizations from the same root, to avoid structuring around pronunciation headers? Fay Freak (talk) 03:38, 6 September 2021 (UTC)Reply
@Fay Freak: I'm actually fine with its use in pronunciation headers; it's the use everywhere else that I find to be a problem. Perhaps instead of deleting it, the solution is to change its usage? —Μετάknowledgediscuss/deeds 04:01, 6 September 2021 (UTC)Reply
Yea. Though it may be deleted if a template working for more languages is created. Fay Freak (talk) 04:08, 6 September 2021 (UTC)Reply

October 2021 edit

Reference templates categories by family edit

Note to archiver: please archive this discussion to Wiktionary talk:Reference templates

Undeletion of Category:Indo-Aryan reference templates edit

(discussion started at User talk:TongcyDai § CAT:Indo-Aryan reference templates)

Why did you have it deleted? This and CAT:Proto-Indo-Aryan reference templates are supposed to be different categories. ·~ dictátor·mundꟾ 22:20, 27 October 2021 (UTC)Reply

@Inqilābī I'm not quite sure about it, but it seems like these sorts of templates are categorized by languages, not language families. I've seen some templates that were belonged to a category named after a language family but later moved to a new category named after related proto language's name, so I did the same thing. --TongcyDai (talk) 22:32, 27 October 2021 (UTC)Reply
Indo-Aryan reference templates do not necessarily deal with Proto-Indo-Aryan. Indo-Aryan reference templates just pertain to the family as a whole while Proto-Indo-Aryan reference templates are specifically meant for the language. So I do not agree with the deed, but I will at first inform other editors about it. (@Bhagadatta, Kutchkutch, AryamanA) ·~ dictátor·mundꟾ 22:52, 27 October 2021 (UTC)Reply
@Inqilābī: Since there are templates that would be in both categories and many Indo-Aryan templates are named as Template:R:inc:Name, that must have created the impression that they should be merged into a single category. However, there really should be a distinction so that templates that involve more than one Indo-Aryan language but not Proto-Indo-Aryan can be in Category:Indo-Aryan reference templates. For comparison,
Category:Sino-Tibetan reference templates
Category:Proto-Sino-Tibetan reference templates
are currently two separate categories. Kutchkutch (talk) 12:21, 28 October 2021 (UTC)Reply
@Kutchkutch Category:Sino-Tibetan reference templates is currently a category of categories. Do we need this kind of category? In addition, I think it will be fine to add all main languages mentioned in a reference one by one, just like many templates do. --TongcyDai (talk) 12:34, 28 October 2021 (UTC)Reply
@Kutchkutch: You can now recreate the deleted cat. I have fixed those reference templates that deal with the family. ·~ dictátor·mundꟾ 12:43, 28 October 2021 (UTC)Reply
Discussion moved from User_talk:TongcyDai#CAT:Indo-Aryan_reference_templates.

Category:Sino-Tibetan reference templates edit

(Notifying Atitarev, Tooironic, Suzukaze-c, Justinrleung, Mar vin kaiser, Geographyinitiative, RcAlex36, The dog2, Frigoris, 沈澄心, 恨国党非蠢即坏, Michael Ly): Kutchkutch (talk) 11:37, 29 October 2021 (UTC)Reply

January 2022 edit

Category:Korean syllables edit

Category:Korean syllables without final edit

Category:Basic Korean syllabaries edit

Nearly empty, they don't appear to be useful anymore. "Letter" would probably be more appropriate than "syllable" for the two entries in the first category. Ultimateria (talk) 18:25, 1 January 2022 (UTC)Reply

Delete. (Notifying TAKASUGI Shinji, Atitarev, HappyMidnight, Tibidibi, Quadmix77, Kaepoong): AG202 (talk) 15:13, 15 June 2022 (UTC)Reply
The subcategories can essentially be speedied, which I have done, however, it's not clear what should be done with the two entries in Cat:Korean syllables. The entry bears some similarities to, say, , but none of the latter's categories are appropriate for 튽. And ꥸᅦퟗ is a bit of an oddball entry. Ultimateria's suggestion of merging this category into Category:Korean letters seems inappropriate, as that cat contains Hangul "radicals" (sorry, don't know the proper term). This, that and the other (talk) 12:46, 26 September 2022 (UTC)Reply

Template:rfv-term edit

And its CSS subpage. This template, only used by its creator on 4 pages, attempts to indicate that a translation is questioned by blurring it out and thus making it impossible to read for someone like me with poor eyesight. It does not, however, give any explicit indication why the term is being blurred, and simply looks like a bizarre browser error. There may be a way to go about RFVing translations, but this template is not the right way to do it. —Μετάknowledgediscuss/deeds 18:14, 6 January 2022 (UTC)Reply

@Useigor Thadh (talk) 18:17, 6 January 2022 (UTC)Reply
The amount of fuzzing is ridiculous. The idea of making something even a little bit harder to read when we are supposed to be giving it attention to try to verify is contrary to logic. DCDuring (talk) 18:19, 6 January 2022 (UTC)Reply
@Metaknowledge, DCDuring: Apparently, when you hover over the term, it explains the issue and unblurs it. Thadh (talk) 18:25, 6 January 2022 (UTC)Reply
What about mobile? (Or me, who didn't think to hover over something I couldn't read?) —Μετάknowledgediscuss/deeds 18:27, 6 January 2022 (UTC)Reply
Since it is a departure from any standard way of indicating that something is being challenged, how would any user or contributor know what was going on? Hovering is not always the response one would make. We have often been encouraged to be sensitive to accessibility concerns. This seems like an occasion to apply that sensitivity. DCDuring (talk) 18:52, 6 January 2022 (UTC)Reply
I did not mean that I think this template should be kept in its current state, I was simply pointing out that blurring isn't the only thing the template does. By the way, what about just putting a dotted line under the term, or something similar? Thadh (talk) 19:00, 6 January 2022 (UTC)Reply
I would change the background colour to orange or the like (one sufficiently distinct from that of {{quoted term}} in any case). I found the blurring bizarre from the beginning (but ignored the template thinking that Useigor was still coding) and the reason boils down to that, as DCDuring said, the idea of making something even a little bit harder to read when we are supposed to be giving it attention to try to verify is contrary to logic. Fay Freak (talk) 19:23, 6 January 2022 (UTC)Reply
Why not just use the same format as Template:t-check? - -sche (discuss) 22:38, 6 January 2022 (UTC)Reply
Cause it was not “for translations” in translation sections, I don’t know whence this equation by Metaknowledge comes from but now have to dispel this conception, but apparently for strange derived terms and descendants in Proto-Slavic entries. The design of {{t-check}} is of course for the background of translation tables while descendants and derived terms sections look different and hence seek different tinge. Fay Freak (talk) 00:10, 7 January 2022 (UTC)Reply
We could use the same format of adding superscript "(please verify)". Although really, if the term is so likely to be fabricated and the likelihood of someone coming back to provide references is low, maybe just remove it or move it to the talk page or HTML-comment it out... - -sche (discuss) 18:48, 7 January 2022 (UTC)Reply
It is not supposed to be readable because term is likely fabricated (i do some search before adding the template) and it is unknown when its editor will provide reference for it. Marked term could be removed instead but there is slight possibility that it can be verified. If you want to read, you can hover (swipe) or click and then create page with reference. For me, colored background or excessive text are ugly and distracting when i'm reader and not editor. Any editor can make custom CSS in User:USER/common.css (e.g. #mw-content-text .temp-rfv-term+[lang] {filter: blur(0px); text-decoration: underline dotted; background: orange;}). —Игорь Тълкачь (talk) 07:42, 7 January 2022 (UTC)Reply
I have a computer that has no mouse input at the moment. It is very cumbersome to interact with words that have this text decoration. —Justin (koavf)TCM 07:50, 7 January 2022 (UTC)Reply
Now blur is changed to strike. I wanted to use 50%-opaque 2px-thick line (text-decoration: line-through 2px rgba(0,0,0,0.50);) but for some reason wiki editor does not let use thickness so i had to use 80%-opaque 1px-thick line (text-decoration: line-through rgba(0,0,0,0.80);) —Игорь Тълкачь (talk) 06:58, 8 January 2022 (UTC)Reply
I stand by my earlier comment that using the same format as Template:t-check, a superscript note explicitly saying "(please verify)", or even a non-superscript note like Template:rfv-sense, would probably be the clearest thing, although if a term is really most likely fabricated and the likelihood of someone coming back to provide references is low, maybe just remove it or move it to the talk page or HTML-comment it out. IMO we should allow people to occasionally RFV terms that don't have entries yet: then we could just submit the terms this is for to RFV and remove them after a month... - -sche (discuss) 03:48, 13 March 2022 (UTC)Reply
Delete, if this is not rendered more useful/user-friendly. Strikethrough is not a help. Text display of what action is to be taken and where seems essential, but has not been provided in the more than five months this RfD has been active. And deprecate now. DCDuring (talk) 17:56, 25 June 2022 (UTC)Reply
We need to decide what this template is for if we're going to keep using it, and make sure the template code matches that as well as making sure the documentation is clear and matches that, too. Then we need to update the relevant modules so the categories are integrated into our category structure.
The cosmetic problems that led to the RFD have been fixed, but the combination of unclear documentation, clash between category naming and actual use, and inability to create the categories without fatal errors is an absolutely bizarre train wreck that traces back to the original creation of the template. That needs to change or this needs to be deleted. Chuck Entz (talk) 04:36, 11 September 2023 (UTC)Reply
At least there are no passengers on the train any more. DCDuring (talk) 13:48, 11 September 2023 (UTC)Reply
@Chuck Entz: The mismatch could be handled by a list at WT:Todo/Lists. --RichardW57m (talk) 12:24, 18 January 2024 (UTC)Reply

Appendix:Terms derived from toponyms edit

There's already Category:English terms derived from toponyms. We should make sure the entries listed have that category, then delete the appendix. – Jberkel 20:08, 13 January 2022 (UTC)Reply

I've added as many as I could extract from that page. – Jberkel 23:04, 13 January 2022 (UTC)Reply
Delete. Ultimateria (talk) 19:40, 19 May 2022 (UTC)Reply
Delete for the sake of deduplication. — excarnateSojourner (talk · contrib) 19:47, 16 November 2022 (UTC)Reply

Category:English appendix-only phrases edit

Tagged by User:Zcreator alt (diff) but not listed. — Fytcha T | L | C 00:37, 16 January 2022 (UTC)Reply

No reason to divide by part of speech, I think, but having all Appendix entries that look like English mainspace articles in a Category:English Appendix lemmas would be good. Currently, Appendix:Star_Wars/protocol_droid is in the mainspace's Category:English lemmas. — Fytcha T | L | C 00:44, 16 January 2022 (UTC)Reply
Discussion moved to Wiktionary:Requests for verification/Non-English#Appendix:Toki Pona/teje.

February 2022 edit

Category:en:Multiracial edit

I don’t think it is a proper category. ·~ dictátor·mundꟾ 20:32, 26 February 2022 (UTC)Reply

@Inqilābī: I think you'll need to explain why it's not "proper". — SGconlaw (talk) 20:56, 26 February 2022 (UTC)Reply
  1. It is not in proper category format; we do not have Category:Multiracial. (It was created unilaterally without consensus.)
  2. This category is a hotchpotch of random entries. All ethnonyms, including mixed races (such as mestizo, mulatto, Eurasian), belong in CAT:Ethnonyms; ethnic slurs have their own separate category; CAT:Scientific racism and CAT:Eugenics could be separate categories, if useful.
  3. Even the category name is not grammatically correct, it should be either multiracial people or multiracials.
  4. A lot of mixed-race group names are not dictionary material, being SoPs. Therefore, I do not think we need any category dedicated to multiracial people (the name as used in that category, which itself links to Wikipedia). ·~ dictátor·mundꟾ 21:36, 26 February 2022 (UTC)Reply
    I think a lot of third culture kids would disagree with that last point... Theknightwho (talk) 21:51, 26 February 2022 (UTC)Reply
    William Jones (philologist) was an Anglo-Welsh person. This racial term should remain as a redlink; tho’ it could have a different idiomatic sense. ·~ dictátor·mundꟾ 14:34, 27 February 2022 (UTC)Reply
    Issue #1 could be addressed very easily by adding it to the category tree. Issue #3 could be addressed by renaming the category. I don't find #4 a very convincing argument. We could just keep the ones that aren't SOP and delete the ones that are, which is the same rule we apply to any other kind of term. There are evidently plenty of such terms in English that are single words or idiomatic. Also, the RfD of Irish American closed as keep, and although that isn't a term related to mixed ancestry, it shows that hyphenated or spaced combinations of nationalities aren't necessarily regarded as SOP by the community.
    Point #2 seems to be the most substantial, but as I wrote in my comment below I think there might be value in separating out these terms from other ethnonyms. And not all of these fall under Scientific racism or Eugenics. I don't think Blasian or Finndian are necessarily associated with racism or eugenics. Such terms seem to be used as identities by members of the groups themselves. That said, I don't particularly object to deletion either. 70.172.194.25 02:17, 23 February 2023 (UTC)Reply
Delete per nom. —Svārtava (t/u) • 09:46, 27 February 2022 (UTC)Reply
  • Delete per nom. — excarnateSojourner (talk · contrib) 06:20, 16 February 2023 (UTC)Reply
  • I can see some potential value in keeping a separate category for things like mulatto, Blasian, Chindian, the last of which isn't even in the category currently. I think there is something different about those terms as compared to most ethnonyms, and Wikipedia seems to agree given that it has a "Multiracial affairs" category with similar terms as members.

    While an argument could be made that almost all human populations have admixture from multiple groups and so almost everyone is in some sense multi-ethnic, I don't think most would e.g. include Desi in this category even if one could theoretically make an argument that the Indian subcontinent has a mix of Indo-Aryan and Dravidian genetics. It has to be a term for someone whose recent ancestors came from different groups, not way back in (pre)history. One doesn't have to be a racial essentialist to realize that people who fall under this umbrella are viewed differently in society (hence the existence of such terms).

    That said, I don't particularly object to deletion, as the issue may be more trouble than it's worth, most commenters support deletion, and the category mixes relatively PC and highly offensive terms as though there is no distinction.

    The inclusion of BIPOC in this category perplexes me. I thought "multiracial" in this context describes a person with mixed ancestry, not a coalition of different ethnic groups. 70.172.194.25 01:55, 23 February 2023 (UTC)Reply

March 2022 edit

Category:Two-letter words by language edit

Category:Three-letter words by language edit

Category:One-letter words by language edit

All entries are manually categorized. If we must have these categories, can’t the categorization be automated? ·~ dictátor·mundꟾ 16:35, 10 March 2022 (UTC)Reply

Sure, but why are you proposing them for deletion? This sounds like a bot request. —Justin (koavf)TCM 19:57, 10 March 2022 (UTC)Reply
Actually I wanted to know whether the community wishes to keep these categories… ·~ dictátor·mundꟾ 11:05, 11 March 2022 (UTC)Reply
I'm good with keeping them, but it should be automated. Theknightwho (talk) 00:45, 12 March 2022 (UTC)Reply
It would be impossible to add these automatically without rendering the categories essentially meaningless. For example, d has several POSs which consist only of abbreviation senses (which evidently don't count as "words" in the eyes of this categorisation system), but the headword line template has no way of knowing that. This, that and the other (talk) 04:27, 12 March 2022 (UTC)Reply
Not to mention the fact that we don't want to increase Lua memory burden on Latin script letter pages, so a lot of headword templates on a few such entries (currently a, A, b, o, u) are using {{head-lite}} anyway. 70.172.194.25 05:22, 12 March 2022 (UTC)Reply
Keep - useful for word games and other things. John Cross (talk) 22:06, 23 March 2022 (UTC)Reply
@Inqilābī Keep three-letter words. I asked (under my old account) about using a bot to populate (specifically the English subcategories of) these categories last June and @Suzukaze-c said that they could be trivially populated using {{head}} or its subtemplates. Several months later I sought consensus to populate them (and someone with template editing privileges) and received no responses. But I do not have a solution to the problem pointed out by @This, that and the other above, so for now I will abstain on one-letter words. - excarnateSojourner (talk | contrib) 23:06, 8 April 2022 (UTC)Reply
Keep I agree the one and two letter categories are useful. As pointed out, a bot can't make proper categorization since it can't separate words from other character groups like abbreviations. Bots could assist maintenance, if all n-letter entries were flagged with either "include" or "exclude" templates or some such; the bots could report entries missing either flag into a maintenance category for manual attention. --R. S. Shaw (talk) 18:11, 21 May 2022 (UTC)Reply
It can do it via parts of speech and checking for templates like {{initialism of}}. It's certainly doable, I think. Theknightwho (talk) 21:53, 9 August 2022 (UTC)Reply

Templates and reference templates by language family rather than by language edit

For some reason, we have Category:Indo-Aryan reference templates and Category:Sino-Tibetan templates but not other families and subfamilies. See Category:Templates by language, where we don't have Category:Niger-Kongo reference templates or Category:Semitic reference templates or Category:Balto-Slavic reference templates. I propose that we delete these two one-offs or at the very least, change the hierarchy explicitly to include larger language families. There's no reason for these two outliers. —Justin (koavf)TCM 02:50, 13 March 2022 (UTC)Reply

Cf. https://en.wiktionary.org/w/index.php?oldid=64486872#Undeletion_of_CAT:Indo-Aryan_reference_templatesJustin (koavf)TCM 02:51, 13 March 2022 (UTC)Reply
@Koavf: Please see the bottom of that category that contains reference templates pertaining to the Indo-Aryan language family as a whole, rather than specific languages or even chronolects. Since Wiktionary does not treat Indo-Aryan as a united macrolanguage like Sinitic/Chinese, it makes more sense to dedicate a separate category for the current reference templates that deal with Indo-Aryan linguistics. That said, we may remove the 56 individual language categories from the list. (Pinging @Kutchkutch, Bhagadatta, Svartava, AryamanA for more input.)
I’m not sure what to be done with other families, or if consistency is needful across all languages: in that case you could raise the matter in the BP. ·~ dictátor·mundꟾ 11:32, 13 March 2022 (UTC)Reply
@Inqilābī: You are correct that some of these are about Indo-Aryan at large, but 1.) they can just be put into specific language categories as they are used on entries for those languages, 2.) what I'm suggesting is already done in practice for several of these categories (and was before I started editing them), and 3.) there are definitely other references that apply to more than one (e.g.) Romance language or Semitic language as well, so we're back to either sorting one reference template into several individual language categories (my preference) or building out the module and hierarchy to include language families. —Justin (koavf)TCM 15:45, 13 March 2022 (UTC)Reply
@Koavf I find the existence of these categories very convenient and do not support their deletion. There is a long history of comparative literature on these families and in that respect being able to easily find reference templates for related language varieties is useful. If these categories are outliers, then I would suggest that the creation of more like them would actually be a better idea. I could see such categories being particularly useful for Iranian languages, Dravidian languages, Austro-Asiatic, for example. عُثمان (talk) 16:27, 21 July 2023 (UTC)Reply
Thanks. You've been able to use this category scheme before? —Justin (koavf)TCM 02:37, 22 July 2023 (UTC)Reply
Yes—for example on an entry like urial, it was helpful for locating the relevant reference templates for reconstructing the etymology عُثمان (talk) 02:44, 22 July 2023 (UTC)Reply
Were they recategorized the way I suggested, would you not have been able to use it as effectively? —Justin (koavf)TCM 03:01, 22 July 2023 (UTC)Reply
No—the larger a category is, the more challenging I find it to navigate it. (Even the difference in the amount of time it takes to load the pages is non-trivial since I don't have a great internet connection.) عُثمان (talk) 17:29, 22 July 2023 (UTC)Reply
And my proposal is to make smaller categories, so you made my argument for me. —Justin (koavf)TCM 02:51, 23 July 2023 (UTC)Reply
If you make smaller subcategories, the containing category becomes larger. There also aren't any established genetic subgroupings of Indo-Aryan to make smaller categories with. (Most schemes which do so out of convenience on solely geographic criteria end up splitting mutually intelligible dialects between subgroups.) So it is not clear what sort of categories you are suggesting be made عُثمان (talk) 03:11, 23 July 2023 (UTC)Reply

Template:ethnologue edit

Ethnologue stuff (like here for English) is behind a paywall. At the link it reads: "This profile is available with an Essentials plan." And following that link, it's stated that it costs $199/month or $480/year. That's not useful, quite expensive, advertising/spam. --學者三 (talk) 16:11, 14 March 2022 (UTC)Reply

Quite a lot of money, yes! We could tag the template with Template:crippling paywall (or whatever...), I suppose. If not, delete Notusbutthem (talk) 09:39, 20 March 2022 (UTC)Reply
Replace with {{ISO 639}} This, that and the other (talk) 13:02, 2 June 2022 (UTC)Reply
I'm doing a general rework of how we treat ISO 639 codes at the moment - part of which involves splitting out the ethnologue parameter from {{ISO 639}} because it's a bit of a mish-mash at the moment, which makes it trickier to deprecate things in situations like this. I agree that it's less-than-ideal to link to sites which are hidden behind paywalls, though. Theknightwho (talk) 22:39, 15 June 2022 (UTC)Reply
Delete. This is literal advertising. — Fytcha T | L | C 23:09, 18 June 2022 (UTC)Reply
We should replace it with a Glottolog link, as that's free. Theknightwho (talk) 21:55, 9 August 2022 (UTC)Reply
Why not add a link to https://glottolog.org/glottolog?iso=aaa into {{ISO 639}}? This, that and the other (talk) 05:24, 11 August 2022 (UTC)Reply
@Theknightwho ^^ if we do this we can surely delete the ethnologue template, unless there is some issue with divergent codes. This, that and the other (talk) 07:18, 17 September 2022 (UTC)Reply
@This, that and the other They do have divergent codes (Glottolog use a different system that is also much more comprehensive on the dialectal level), but that’s bottable. Theknightwho (talk) 12:22, 17 September 2022 (UTC)Reply

Template:es-adj form of edit

Was unduly tagged as deleted by Wonderfool, despite it not being deleted, and them being unable to delete it. Notusbutthem (talk) 09:42, 20 March 2022 (UTC)Reply

I think we archive deprecated templets instead of deleting them. ·~ dictátor·mundꟾ 11:01, 20 March 2022 (UTC)Reply

April 2022 edit

Wiktionary:Entry templates edit

Wiktionary:English entry templates edit

Wiktionary:French entry templates edit

Wiktionary:Hebrew entry templates edit

Wiktionary:Swedish entry templates edit

·~ dictátor·mundꟾ 21:11, 4 April 2022 (UTC)Reply

Delete. Ultimateria (talk) 16:54, 27 April 2022 (UTC)Reply
Keep I cannot see any reason given to delete, and there is a link from the listing of entry templates, and this entry shows documentation for what they are about. Graeme Bartlett (talk) 05:21, 30 May 2022 (UTC)Reply
@ExcarnateSojourner Have you clicked on these? The redlinks and general stubbiness indicate that no one is using these pages. The templates (which I also doubt are being used) should be housed in categories if we want them at all. Ultimateria (talk) 01:15, 17 April 2023 (UTC)Reply

June 2022 edit

South Levantine Arabic edit

Hey, I'm the guy who works on South Levantine Arabic. Occasionally someone contributes an entry or two in good faith, but sometimes entries that don't meet CFI are introduced, and because I'm not an editor or whatever I'm not allowed to delete it. Can someone delete: على سيرة, قطع الإشارة & قليل ما for me? They are not idiomatic. Additionally, I would argue that بالطبع is not attested in the dialect; the right form is طبعا. Finally, this one is my bad: I instructed someone to create the entry بلف — I'm not sure where I got this from, but after further investigation I couldn't find any attestation of it, so I may have confused it for the Present Tense of لف — so if someone could please delete بلف I would appreciate it. Thanks. AdrianAbdulBaha (talk) 08:39, 4 June 2022 (UTC)Reply

@AdrianAbdulBaha Hi. You should use Wiktionary:Requests for deletion/Non-English for terms you want deleted because they are non-idiomatic (we call this "sum of parts"), and Wiktionary:Requests for verification/Non-English for terms you want deleted because you believe they aren't attested. Can you resubmit your requests to these pages? That way, other editors who are familiar with Levantine Arabic can respond appropriately. Benwing2 (talk) 03:56, 14 June 2022 (UTC)Reply

Template:kk-regional edit

Rather than being presented as a floating box, this information should be incorporated into the headword line, like we do for other dual-script languages (Serbo-Croatian, Malay, etc). This, that and the other (talk) 13:12, 15 June 2022 (UTC)Reply

It's also out of date, as Kazakhstan has been transitioning to the Latin alphabet since 2017 as well. Theknightwho (talk) 14:16, 15 June 2022 (UTC)Reply
Keep, and update to having three scripts. Thadh (talk) 15:01, 15 June 2022 (UTC)Reply
Why not put it in the headword line still? Having it all the way over on the right is nonstandard (except for Persian I guess) and easy to miss. This, that and the other (talk) 01:41, 16 June 2022 (UTC)Reply
I agree - merge into the headword template. Theknightwho (talk) 02:22, 16 June 2022 (UTC) I've changed my mind, as I actually really prefer this formatting. Keep. Theknightwho (talk) 23:55, 22 July 2022 (UTC)Reply
Not every contributor prefers to use multiple scripts in the headwords, apparently. E.g. Mongolian entries are gradually converted from that into a similar Mongolian template {{mn-variant}}, e.g. суулгах (suulgax) by @MonoParallax, LibCae, Crom daba.
We should also ask the opinion of primary Kazakh editor who heavily uses the template: @Vtgnoq7238rmqco. Note that the modern Roman spelling for Kazakh <> the Kazakh transliteration at Wiktionary and the conversion is not that straightforward. --Anatoli T. (обсудить/вклад) 02:50, 16 June 2022 (UTC)Reply
In fairness, that layout does make more sense for Mongolian given it's written vertically. Theknightwho (talk) 03:37, 16 June 2022 (UTC)Reply
I stuffed up my edits (put the answer into a wrong section), so repeating the ping to @MonoParallax, LibCae, Crom daba, Vtgnoq7238rmqco. --Anatoli T. (обсудить/вклад) 04:21, 16 June 2022 (UTC)Reply
@Atitarev, Theknightwho, This, that and the other I think I agree that it would be better in the headword line. If there were inflected forms in the headword line, having multiple scripts as well would get crowded, but it appears this isn't the case. We do have {{ku-regional}} for Kurdish but this isn't really parallel because these represent different languages rather than different script variants of the same language. Arguably the same thing is going on with {{fa-regional}}. Benwing2 (talk) 06:30, 16 June 2022 (UTC)Reply
I assume that the current layout of Azerbaijani lemmas could be a perfect example, as all three scripts (Arabic, Latin and Cyrillic) are represented independently on most occasions. However, it could be a huge work to give all Kazakh entries a similar overhaul. Vtgnoq7238rmqco (talk) 11:50, 16 June 2022 (UTC)Reply
@Vtgnoq7238rmqco This should be easy by bot, no? Benwing2 (talk) 23:58, 18 June 2022 (UTC)Reply
@Vtgnoq7238rmqco, Benwing2, This, that and the other, Theknightwho: Just wish to mention that a missing Latin parameter makes the current Kazakh entries with the template look ugly, e.g. жандармерия (jandarmeriä). Can they be safely made optional (or just the new one) or can we use named optional parameters instead? Re: bot. @Benwing2, @Vtgnoq7238rmqco: I don't think we have data to populate the new Roman spelling on all Kazakh terms and the conversion from Cyrillic is not 1:1 and can't be error-free, AFAIK. --Anatoli T. (обсудить/вклад) 04:23, 6 July 2022 (UTC)Reply
@Atitarev I can fix {{kk-regional}}. As for bot conversion: (1) can we simply convert whatever we have without needing out the Cyrillic -> Latin conversion? (2) what are the issues with Cyrillic -> Latin? Is it possible to automate it for some pages, while leaving others to be done manually? Benwing2 (talk) 05:48, 6 July 2022 (UTC)Reply
@Benwing2: The Cyrillic -> Latin correspondence issue was mentioned by User:Vtgnoq7238rmqco in the past when we talked about what should be the romanisation standard but I don't remember the discussion. The issue may not be current, though. Back then we had digraphs in the proposed romanisation. They have been abandoned since. If we are targeting just one romanisation version, the future one, then it's possibly one-to-one but it's not the one we use at Module:kk-translit
Copying the table from Wikipedia. This must be the latest proposed romanisation to be implemented:
A a
(А а)
Ä ä
(Ә ә)
B b
(Б б)
D d
(Д д)
E e
(Е е)
F f
(Ф ф)
G g
(Г г)
Ğ ğ
(Ғ ғ)
H h
(Х х,
Һ һ)
I ı
(І і)
İ i
(Й й,
И и)
J j
(Ж ж)
K k
(К к)
L l
(Л л)
M m
(М м)
N n
(Н н)
Ñ ñ
(Ң ң)
O o
(О о)
Ö ö
(Ө ө)
P p
(П п)
Q q
(Қ қ)
R r
(Р р)
S s
(С с)
Ş ş
(Ш ш)
T t
(Т т)
U u
(У у)
Ū ū
(Ұ ұ)
Ü ü
(Ү ү)
V v
(В в)
Y y
(Ы ы)
Z z
(З з)
The proposed romanisation may be updated yet again, LOL. --Anatoli T. (обсудить/вклад) 06:26, 6 July 2022 (UTC)Reply
@Atitarev Thanks. No digraphs any more in the proposed romanization and our own romanization only has digraphs for я ё ю which aren't anywhere in the table above (presumably they are used only for Russian loanwords?). I am all in favor of using a standard romanization instead of an ad-hoc one but I gather that the proposed romanization is a moving target. Benwing2 (talk) 02:38, 7 July 2022 (UTC)Reply
@Benwing2, Vtgnoq7238rmqco: Yes, in the latest development, the digraphs (apart from Russian loanwords) are eliminated. Transliterations of я, ё, ю, ъ, ь, э, ц need clarifications. I support switching Module:kk-translit and WT:KK TR to the latest proposed transliterations and the Roman forms could simply be the automated transliteration of the Cyrillic spelling. I first proposed the switch in Module talk:kk-translit but it wasn't support. I'd like to ask @Vtgnoq7238rmqco to revisit. There may be a few corner cases but we can look up any of those.
BTW, https://sozdik.kz/ also has a romanised Kazakh. It looks up-to-date but I am not 100% sure. I have an account there. The site will require it when you have too many searches. Anatoli T. (обсудить/вклад) 02:52, 7 July 2022 (UTC)Reply
@Atitarev: I tried to compare the transliteration of several Kazakh loanwords from Russian on the website you mentioned, and the results are as followed. I feel doubtful about these transliterations because I have not found any official documents to regulate them. Besides, я and ю are rather common in Kazakh text apart from Russian loanwords (e.g саясат is borrowed from Persian, and ю usually appears in some infinitives).
Я is transliterated into Ä (same as Ә. e.g ядро/ädro).
Both Ё and Э are transliterated into E (same as Е. e.g щётка/şetka).
Both Щ and Ч are transliterated into Ş (same as Ш. e.g чемпионат/şempionat).
Ю is transliterated into Ü (same as Ү. e.g юрисдикция/ürisdiksia).
Ц is transliterated into S (same as С. e.g циклон/siklon).
НГ is transliterated into Ñ (same as Ң. e.g акваланг/akvalañ).
ъ and ь are omitted as default (e.g гуашь/guaş), but there are irregularities. For instance, король is transliterated into ‘koröl’, but ‘korolı’ and ‘korol’ also appear in the sample sentences.
Perhaps further regulations would clarify those changes I mentioned. Personally, I doubt if Kazakhstan government will update the current transliteration once more.
Vtgnoq7238rmqco (talk) 12:58, 7 July 2022 (UTC)Reply
@Vtgnoq7238rmqco, Benwing2: Sorry, I missed the response without the ping. It's interesting. I think we can start the bot could add the Latin spelling for words where these letters are not used and leave the rest to be filled manually or wait when the conversion is clarified. We can perhaps agree on what to use.
Some or most of Vtgnoq7238rmqco's findings make sense. Apparently "щётка" is not pronounced as in Russian, "ё" is ignored and read as a dotless "е" and it makes sense "щ" has become a "ш". Ц has become a single "s", rather than "ts" in the romanised Uzbek, Turkmen and Azerbaijani, although there are inconsistencies and variants with "ts". Tajik (even if it's still Cyrillic and not a Turkic language) has abandoned letter "ц" entirely in favour of "тс", which is also often just a "с".
I have asked a question on w:Talk:Kazakh alphabets regarding the policies on these selected letters - я, ё, ю, ъ, ь, э, ц, ч and щ.
Should part of the discussion be moved to Module talk:kk-translit or Wiktionary talk:Kazakh transliteration instead? This is not all about the template. --Anatoli T. (обсудить/вклад) 04:58, 9 July 2022 (UTC)Reply

Combine and Deprecate Template:kk-regional and Template:kk-scripts into Template:kk-alt edit

(Moved from Template talk:kk-alt)
There was already a discussion at Wiktionary:Requests for deletion/Others#Template:kk-regional but that was about moving Arabic spellings to the header, so this discussion is a bit different.
kk-alt can now preform all the functions of both kk-scripts and kk-regional (those were previously separate templates because kk-regional did not have a field for the pre-reform Arabic spelling); and kk-alt can auto-fill the various spellings (with the Cyrillic spelling provided, if the entry is Cyrillic it can use the page name). I think kk-scripts and kk-regional should be deprecated in favor of template:kk-alt, since kk-alt combines and improves on both of them (also kk-regional implies regional differences, so it's a bit of a misnomer). I had initially updated kk-regional and kk-scripts to simply forward everything to kk-alt... but i'm not sure if that's actually a good idea, I think it might be better to replace all instances of kk-scripts and kk-regional with kk-alt. سَمِیر | Sameer (مشارکت‌هاکتی من گپ بزن) 04:42, 27 September 2023 (UTC)Reply

notifying @Atitarev, @Theknightwho, @Benwing2, @Thadh, @Vtgnoq7238rmqco, who were involved in the discussion in RFD. I would've started this conversation in requests for deletion but there was already a conversation started there (for a different reason), unless one of you thinks this should be added to that conversation??? سَمِیر | Sameer (مشارکت‌هاکتی من گپ بزن) 04:44, 27 September 2023 (UTC)Reply
@Sameerhameedy I think this should go into that same conversation in WT:RFDO; you can make a new L3 header for it in the same conversation. Benwing2 (talk) 04:51, 27 September 2023 (UTC)Reply
Moved, re-notifying @Atitarev, @Theknightwho, @Benwing2, @Thadh, @Vtgnoq7238rmqco. (as the old pings are no longer valid). سَمِیر | Sameer (مشارکت‌هاکتی من گپ بزن) 05:01, 27 September 2023 (UTC)Reply
@Sameerhameedy This is fine with me but we should decide whether this info is better placed in the headword. (If so, it should be easy to adapt the code in {{kk-alt}} into Module:kk-headword.) Benwing2 (talk) 05:18, 27 September 2023 (UTC)Reply
I'm fine with the new template, but I would prefer it as a box rather than in the headword for aesthetic reasons. Thadh (talk) 08:43, 27 September 2023 (UTC)Reply
I'm not sure how I feel about this. The Cyrillic and Latin spellings are already in the headword line; it seems weird to repeat them in this box. The only unique info here is the Arabic spelling. If it is possible to find a nice way to fit it into the headword line, wouldn't that be better? Alternatively (heh), they could go under an "Alternative forms" or "Alternative spellings" header. This, that and the other (talk) 09:56, 27 September 2023 (UTC)Reply
I definitely think we should remove them from the headword line, if they are given there as well. But if you're referring to the transliteration, is not the same as the Latin script: cf. анархия. Thadh (talk) 11:04, 27 September 2023 (UTC)Reply
@Thadh I think that is a mistake (re the difference between Latin script and translit). The problem is that the current approved Latin script version is very much a moving target and we haven't yet worked out to what extent we will try to track this. BTW I agree with User:This, that and the other that we should put these in the headword line. This is consistent with the handling of other multi-script languages such as Serbo-Croatian, Malay, Hindi/Urdu, etc. Mongolian is an exception but things are weird there due to the vertical script. Benwing2 (talk) 11:41, 27 September 2023 (UTC)Reply
@Benwing2: What about Azerbaijani, Uzbek, Uyghur, Tatar...? You can't just name a couple of languages that do this option and say it's now some kind of status quo. Thadh (talk) 11:46, 27 September 2023 (UTC)Reply
OK fine (for the record I named 4 languages not 2) but I still think it belongs in the headword. It will get generated automatically if placed in the headword (to the extent this is possible), but it needs a separate template call if placed in a float-right box, which is extra editor work (for this reason many of the Uzbek entries I checked were missing the box). Benwing2 (talk) 12:02, 27 September 2023 (UTC)Reply
No the current transliteration Module for Kazakh doesn't match the current Kazakh Latin alphabet, so the kk-alt uses its own conversion. سَمِیر | Sameer (مشارکت‌هاکتی من گپ بزن) 17:58, 27 September 2023 (UTC)Reply
@Sameerhameedy Just FYI there are errors caused by kk-alt on Ь and ь; it seems the Yañalif code can't handle them. Benwing2 (talk) 20:14, 27 September 2023 (UTC)Reply
@This, that and the other, @Benwing2 it only automatically generates the modern Arabic, Cyrillic, and Latin spellings (sometimes it generates the yañalif spelling) but there's also the pre-reform Arabic spelling used by Kazakh prior to 1924 and the Latin script (Yañalif) used by Kazakh for some 7 ~10yrs before switching to Cyrillic (see құдай, which includes all of them). I suppose we could remove all Kazakh alphabets that are no longer used... But I think the information is helpful, even if it can only be included occasionally. I kinda agree with @Thadh that the Latin script should be moved from the headword to the box (assuming we don't move the Arabic spelling), It would be similar to what Pali does.
But if we end up deciding that the old Arabic and Latin spellings are not worth including.. or you guys have some other plan for showing them.. then whatever. I suppose it wouldn't matter where the Latin and Arabic spellings go. سَمِیر | Sameer (مشارکت‌هاکتی من گپ بزن) 17:56, 27 September 2023 (UTC)Reply
I definitely think we should aim to include these in the long run, so might as well start now. Unlike with scripts like IPA or shorthands, there is a good chance of people finding these in running text and wanting to look up what these words mean. Thadh (talk) 20:06, 27 September 2023 (UTC)Reply
yes I think so too, the only issue I can think of is that since the yañalif alphabet was abandoned decades before the internet, it'll probably be difficult to attest. Nearly all Yañalif spellings will be red links unless someone sorts through newspapers from the 1920s and 1930s سَمِیر | Sameer (مشارکت‌هاکتی من گپ بزن) 22:28, 27 September 2023 (UTC)Reply
@Sameerhameedy I suppose if we are showing that many different scripts it makes some sense to put them in a box, but I'm not sure we need the older spellings esp. Yañalif, since it was used only for a few years. The alternative is to put some of them (the less common ones) in an ==Alternative forms== section. Benwing2 (talk) 20:09, 27 September 2023 (UTC)Reply
@Sameerhameedy Also if we do include the obsolete script forms we should have some clear indication that they are obsolete, like including the years used. Benwing2 (talk) 20:16, 27 September 2023 (UTC)Reply
I'd much prefer to put these spellings in "Alternative forms". We currently have a divergence of practice where Indic languages (e.g. आसन (āsana)) are using "Alternative forms" while Central Asian languages use this floating box. Floating boxes force the reader away from the top-to-bottom "flow" of the entry and should only be used for things that are truly peripheral to the lexical content, like sister project links. This, that and the other (talk) 23:23, 27 September 2023 (UTC)Reply
@This, that and the other, @Benwing2, @Thadh I could update the floating box to look more like the "alternative scripts" header used by Sanskrit and Pali if that's the main issue. (something like this?) Though this conversation has shifted away from whether to delete Template:kk-regional and Template:kk-scripts in place of Template:kk-alt; to the general layout of Kazakh entries. Since Kazakh Layout is more of a policy issue shouldn't that discussion be in beer parlor? سَمِیر | Sameer (مشارکت‌هاکتی من گپ بزن) 03:32, 28 September 2023 (UTC)Reply
@Sameerhameedy Yes, that looks fine to me and seems a reasonable compromise, and yeah it might be reasonable to bring this up in the Beer Parlour. Benwing2 (talk) 23:20, 28 September 2023 (UTC)Reply

July 2022 edit

Template:R:OxfordJapanese edit

See Special:Diff/67879927/67923936. Pinging @Eirikr, Fish bowl. I've done a first AWB sweep where I've removed all references to this work in untemplated form and now there's approximately 50 entries left that use the same reference but in templated form. — Fytcha T | L | C 12:35, 20 July 2022 (UTC)Reply

DeleteFish bowl (talk) 06:05, 29 July 2022 (UTC)Reply
Delete, a poor and unnecessary reference. This, that and the other (talk) 22:56, 26 September 2022 (UTC)Reply
Delete per the above. Theknightwho (talk) 09:16, 8 August 2023 (UTC)Reply

Category:en:Phobias edit

Most of these entries are already part of Category:English words suffixed with -phobia, and the only advantage that I can see to this category is that the critera for inclusion are (at least hypothetically) a bit looser. But aside from maybe a handful of premodern coinings (e.g. hydrophobia) and Anglish neologisms (snake-fright), nothing that belongs to this category could be excluded from Category:English words suffixed with -phobia. Redundant. —(((Romanophile))) (contributions) 07:40, 31 July 2022 (UTC)Reply

Either delete or rename to Category:en:Fears. You might also want to take a look at Category:en:Philias, which is essentially a duplicate of Category:English words suffixed with -philia. Binarystep (talk) 01:27, 2 August 2022 (UTC)Reply

August 2022 edit

Template:table:colors/zh edit

Extremely POVed and limited to modern Mandarin usage. Ignores usages in other Chinese subgroups. 青色 can mean a lot of colours between blue and green. On the other hand, it overly represents Mandarin words for some colours, e.g. 緋紅色, 艷紅色, and 大紅 are all just variations of . (Also why only these ones but not 鮮紅 or 嫣紅?) Other table templates also have this problem, such as template:table:playing cards/zh, but this is the most offending one. Either delete, or move to Template:table:colors/cmn and allow creating templates under other language codes. -- Wpi31 (talk) 11:20, 11 August 2022 (UTC)Reply

Support move to colors/cmn, and the creation of colors/yue, playing cards/nan , &c. Remsense (talk) 17:56, 19 February 2023 (UTC)Reply

Template:table:playing cards/zh edit

Template:table:chess pieces/zh edit

Template:table:seasons/zh edit

Template:table:continents/zh edit

Template:table:suits/zh edit

Template:Table:Chinese Zodiac/zh edit

Template:table:German suits/zh edit

Template:table:Chinese tones/zh edit

Nominating some of the others as well since they more or less have similar issues. --Wpi31 (talk) 11:25, 24 August 2022 (UTC)Reply

Why not move these to [foo]/cmn? —Justin (koavf)TCM 17:32, 24 August 2022 (UTC)Reply
also nominating Chinese tones, which imo only the first table is relevant material. –Wpi31 (talk) 09:05, 30 August 2022 (UTC)Reply
also the various templates in Category:Chinese list templatesWpi31 (talk) 07:42, 23 October 2022 (UTC)Reply

Resolved. Seems like the only responses are in favour of moving these from /zh to /cmn. I will be doing the moves gradually over the next few weeks. This will need some manual intervention to determine which terms are Mandarin and which are not Mandarin but incorrectly added to these templates. – Wpi31 (talk) 08:31, 2 April 2023 (UTC)Reply

@Wpi31 Did you ever get around to doing this? If not, do you need some help? Also, maybe some of these should be just moved into set categories rather than separate lists. Benwing2 (talk) 20:25, 27 September 2023 (UTC)Reply
@Benwing2: Sorry I've just sort of forgot about them. I'll do them soon. There are sometimes non-Mandarin terms in the mix so it needs to be checked one by one. – wpi (talk) 13:56, 28 September 2023 (UTC)Reply
I've moved most of the table ones to /cmn, as well as splitting Template:table:poker hands/zh and Template:table:suits/zh into /cmn and /yue; except for Template:Table:Chinese Zodiac/zh where the template naming/formatting itself is problematic and Template:table:colors/zh where I'm not terribly familiar with the color names.
It would be helpful if there was a bot that (re)populates these templates and delete the unused /zh templates. And yes, some of the list templates would probably be better suited for categories. – wpi (talk) 14:42, 28 September 2023 (UTC)Reply
@Wpi Thanks! Can you clarify what the issue is with Template:Table:Chinese Zodiac/zh and what you mean by a bot that "(re)populates these templates"? I can delete the now unused /zh templates. Benwing2 (talk) 19:57, 28 September 2023 (UTC)Reply
@Benwing2: Template:Table:Chinese Zodiac does not conform to the naming scheme, and should be Template:table:Chinese zodiac or Template:table:Chinese zodiacs instead, and it wraps <span lang="und"></span> around the term which breaks some of the css formatting; there's also |language= which doesn't make much sense when we have {{langname}} - it seems the person who made the template hasn't put much thought into it.
By repopulating I mean replacing the existing uses of /zh with the /cmn equivalents, or perhaps even adding the template to pages which lack them. – wpi (talk) 00:50, 29 September 2023 (UTC)Reply

Some categories for historical countries edit

CAT:Czechoslovakia, CAT:West Germany, CAT:Yugoslavia. All of these mostly contain either of the following three types of entries:

1. Terms denoting the country (Кралство Југославија, Republika Federalna Niemiec) or its inhabitants (Westdeutsche)
2. Terms denoting a currency or something similar that is in no way specific to this period in time (halerz, korona)
3. Terms denoting a place name of a town or city that still exists (Prague, ベオグラード)

The category for Yugoslavia does include a handful of entries that do not fall into these types, but are still pretty basic and do not imho need a category (these are terms like Yugoslav People's Army).

I feel like these categories denote historical periods of countries that are not culturally significant enough to warrant a separate category, but rather should be distributed among the country's descendant's/s' categories. I don't see - judging by the entries now present in the category - how Yugoslavia is more culturally and/or historically significant than, say, the Batavian Republic, the Kingdom of Italy or the French Third Republic. I do not think these three categories are at all comparable with CAT:Soviet Union or even CAT:East Germany (again, judging by the current entries that are added to the respective categories). Thadh (talk) 18:15, 21 August 2022 (UTC)Reply

It seems that at least for Category:West Germany, the category just isn't populated in the same way that Category:East Germany is, at least for English. I've created the category Category:en:West Germany, and populated with a few entries. I also added terms like Wessi and Besserwessi to the respective category for German. With that, I think that the categories just need to have entries actually marked with them before really talking about deletion. AG202 (talk) 18:57, 21 August 2022 (UTC)Reply
I still think marking terms like fall of the wall with "historical"+"Germany" would suffice, without creating these niche categories. Thadh (talk) 19:37, 21 August 2022 (UTC)Reply
My point was more that if Category:en:East Germany exists then Category:en:West Germany should as well, looking at the entries in both. I'm aware that Category:DDR_German exists as well for East German German, but that can exist easily without Category:de:East Germany. Either they should both go or they should both stay. Same with the Yugoslavia category. The only one I'd maybe support deleting is the Czechslovakia category, but I have a strong feeling that it just hasn't been populated and there may be Czech or Slovak terms that would have a special place in it. AG202 (talk) 22:54, 21 August 2022 (UTC)Reply

October 2022 edit

Template:object-shaped edit

Shouldn't this be handled by the derived terms section at shaped? If kept, it definitely needs a more systematic name. This, that and the other (talk) 09:32, 3 October 2022 (UTC)Reply

Delete. There's no reason to present this list via template. Ultimateria (talk) 03:42, 5 October 2022 (UTC)Reply
I see some logic in using a template if the intention is to transclude it in multiple entries in the “Related terms” (or, preferably, “Coordinate terms”) section. It’s easier to update a template than multiple individual entries. — Sgconlaw (talk) 04:26, 5 October 2022 (UTC)Reply
Delete The list on the template is an open set, subject to indefinite expansion, not even limited by attestation. The derived term section of shaped could be periodically repopulated from Wiktionary entries from the XML dumps, taking care to preserve any meaningful redlinked items. DCDuring (talk) 13:08, 5 October 2022 (UTC)Reply
Move to Template:list:en:shaped, maybe, like other list templates? Or just delete. I do agree with Sgconlaw that it's sometimes better to centralize certain things in a template that can be pasted into all the "related terms" sections, rather than duplicate it across them all, but this seems so open-ended (as DCDuring notes) that it doesn't seem helpful... - -sche (discuss) 09:21, 31 October 2022 (UTC)Reply
The Derived terms at shaped is the logical and consistent place for this list. If you're listing e.g. months of the year, which in English are etymologically unrelated, then it makes sense to have the individual pages link to each other through a See also list. I don't see it in this case though. Ultimateria (talk) 23:43, 5 November 2022 (UTC)Reply

not Old Prussian but (re-)constructed Old Prussian AKA Neo-Prussian, and the page doesn't even clarify that it's a (re-)construction and by whom it was made. --11:26, 12 October 2022 (UTC) — This unsigned comment was added by 93.221.61.136 (talk).

Template:R:Etymological Dictionary of Arabic Comment Suggestion edit

This template is transcluded into two entries, but does not accomplish what it purports to do, eg, link to entry in the reference. It categorizes in English reference templates, not Arabic ones, though the reference work is written in Arabic about Arabic terms. It uses the deprecated template {{R:Reference-meta}}. Revision might eliminate any reason for deletion. The documentation says that it was derived from an English reference template. DCDuring (talk) 17:14, 16 October 2022 (UTC)Reply

BTW, there are 101 other templates that use deprecated {{R:Reference-meta}}, though I don't think they all are as error-laden as this one. DCDuring (talk) 17:21, 16 October 2022 (UTC)Reply
Well, the categorisation was trivial to fix. --RichardW57 (talk) 21:12, 19 October 2022 (UTC)Reply
  • Have migrated it to {{cite-web}} and fixed the URLs at the two entries, so keep. —Al-Muqanna المقنع (talk) 20:02, 16 November 2022 (UTC)Reply
    • @Al-Muqanna: The links on tuna and Algeria don't seem to work for me. Do they work for you? Btw, do you think it would be better to make the ID a parameter instead of the full URL? Maybe it wouldn't be a good idea if the IDs aren't stable or if the URL has to be very complicated, but if those issues don't apply then it seems preferable. Anyway, I certainly support keeping this in theory, but it would be good to make the links work if at all possible. 70.172.194.25 01:26, 23 February 2023 (UTC)Reply
      They certainly worked a few months ago when I wrote it, but the links seem to have changed (which beats the whole idea of a permalink), along with the IDs. If they're not going to preserve stable URLs then it might be problematic to maintain the template. I've updated Algeria and will look for the other one in a bit. —Al-Muqanna المقنع (talk) 08:06, 23 February 2023 (UTC)Reply

Template:zh-noun edit

This template can be replaced by {{head|zh|noun}} (parameters of {{zh-noun}} are deprecated). -- 02:49, 23 October 2022 (UTC)Reply

Delete - agree with proposer. Theknightwho (talk) 19:56, 3 November 2022 (UTC)Reply
What will happen to all the entries that still use it? ---> Tooironic (talk) 23:16, 3 November 2022 (UTC)Reply
They'll need to be bot-converted to {{head|zh|noun}} first. Theknightwho (talk) 23:31, 3 November 2022 (UTC)Reply
It won't take too long for a bot to convert them. Glades12 (talk) 10:07, 27 July 2023 (UTC)Reply
Deprecate per above. – Wpi (talk) 14:03, 19 June 2023 (UTC)Reply

November 2022 edit

Undeleting {{false friend}} edit

I would argue this is a useful template for etymology sections, especially for unrelated related languages. The code would have to be changed, of course. Thadh (talk) 11:30, 5 November 2022 (UTC)Reply

Would be handy to have SOME form of marking false friends. Vininn126 (talk) 11:32, 5 November 2022 (UTC)Reply
We do have the template {{U:false_friend}}, though it seems little used, almost entirely for Spanish, and may have been largely the work of one person. Soap 12:28, 5 November 2022 (UTC)Reply
As the person who created that specific page, I just want to say I was just generalizing and making into a reusable template what had been Template:U:es:false friend and manual wording in some entries. - -sche (discuss) 22:18, 14 December 2022 (UTC)Reply
False friendship is somewhat of a spectrum: words rarely exactly match up. This means that the template would go only on terms where the difference is very obvious. Even in these cases, it just seems redundant to the definition section. Catonif (talk) 15:21, 5 November 2022 (UTC)Reply
Undelete. I agree that this would be very useful, especially for folks learning a language. AG202 (talk) 20:39, 9 November 2022 (UTC)Reply
Undelete per nom. Theknightwho (talk) 12:48, 10 November 2022 (UTC)Reply
Undelete. Binarystep (talk) 22:44, 10 November 2022 (UTC)Reply
UndeleteSaltmarsh🢃 07:20, 11 November 2022 (UTC)Reply
In my opinion, we should think about the rules surrounding the use of this template (and pointing out false friends in general) to avoid overuse. — SURJECTION / T / C / L / 21:00, 14 December 2022 (UTC)Reply
Yeah, and we — let me ping the undelete voters @AG202, Theknightwho, Binarystep, Saltmarsh — should decide whether we want an etymology section template (which seems to be the proposed use for T:false friend), or the usage note template T:U:false friend (T:U:es:false friend, etc), because I don't see a reason to have both. (Do any of you?) - -sche (discuss) 22:18, 14 December 2022 (UTC)Reply
Sorry - no very strong opinion - but wherever it's used it should be done sparingly and with a minimum of blah ! — Saltmarsh🢃 06:34, 15 December 2022 (UTC)Reply
Delete the oones with a langcode in the name; that could be set up as a parameter. As too the section - I can see the upsides to both but I think Usage Notes would ultimately make the most sense. Vininn126 (talk) 10:32, 15 December 2022 (UTC)Reply
I agree with Surjection and -sche, and I am therefore reticent to see it undeleted just yet. An appendix would be the best place for gathering false friends, though maybe a template could be used in the main space to tag false friends and prepare the ground for creating such an appendix. PUC10:54, 24 December 2022 (UTC)Reply
Undelete --Daniel Carrero (talk) 22:25, 24 December 2022 (UTC)Reply

These are the only two categories of this type for ancient greek, and they each have one entry. I dont even think that there are any other entries fitting this description that have been missed. I propose just removing the category template from these pages, and they would be removed from the category page automatically right? Anatol Rath (talk) 15:29, 17 November 2022 (UTC)Reply

It's certainly productive in Byzantine Greek where there's theological stuff like θεοποιῶ (theopoiô), ἁγιοποιῶ (hagiopoiô) (though we don't have entries for them). But it would probably make sense to just analyse this as a suffix instead? There's already an entry for modern Greek -ποιώ (-poió) which cites ancient -ποιῶ (-poiô) as etymon. —Al-Muqanna المقنع (talk) 15:50, 17 November 2022 (UTC)Reply

December 2022 edit

remove lesser-used column templates edit

I propose to remove the following column templates, after orphaning them by bot:

@Saltmarsh, Useigor, Surjection, Donnanz, Theknightwho We have far too many column templates with overlapping functionality, each with their own bugs and limitations. People keep "helpfully" creating more of them, for unclear reasons but seemingly to try to "fix" the "bugs" in the existing templates. IMO we only really need two sets: (1) {{col}} and related templates, which take the items inside the template, (2) templates where the items go outside, such as in {{top2}}, {{rel-top}}, {{der-top}}, etc. etc. I have pinged some of the creators of the existing templates that I propose to delete. Several other creators are no longer active. Benwing2 (talk) 06:34, 23 December 2022 (UTC)Reply

@Benwing2 Mea culpa — looking back I see that I was guilty of "helpfulness". Why did I create the first-named above, I don't remember (it was 2008). It must have seemed like a good idea at the time — was it ever used? Trim away! — Saltmarsh🢃 06:50, 23 December 2022 (UTC)Reply
Fully supportive of this endeavour! It will be very exciting to get rid of unnecessary templates and minimise the terrible confusion that currently exists in this space. I would suggest to leave {{nav-bottom}} out of this list though, as it is currently being used as a collapsible box template, rather than a column template. (Why don't we have something like Category:Collapsible box templates, incidentally?) This, that and the other (talk) 09:16, 23 December 2022 (UTC)Reply
For some context, I created {{nav-top}} and {{nav-bottom}} less as a column template and more as a collapse box template that also has column functionality (although I don't think any transclusion currently uses that feature). If it is removed, there should be some kind of alternative that it is replaced with. — SURJECTION / T / C / L / 09:18, 23 December 2022 (UTC)Reply
If I remember correctly, Template:User:Donnanz/der3-u was created to deal with false automatic alphabetical sorting of Scandinavian characters, the sorting was manual. I haven't used it for some years. DonnanZ (talk) 11:13, 23 December 2022 (UTC)Reply
@Surjection, This, that and the other I see, it looks like there are actually four potential sets of templates: items inside vs. items outside and collapsing vs. non-collapsing, and {{nav-top}} and {{nav-bottom}} are actually generalizations of the items-outside collapsing variants. I would maybe suggest giving them different or shorter names, maybe {{col-top}} or {{ctop}} where 'col' or 'c' = collapsing; at least for me, the nav- prefix isn't self-explanatory of what it does. (Update: there already is a {{col-top}}. Blah.) BTW for reference I've attached a table of all the templates currently in CAT:Column templates, along with their aliases and their usage count. Note that the canonical names are boldfaced, and their usage count includes the usage count of their aliases.
Aliased template Canonical template #Uses Disposition
Template:bl Template:bl 344 Replace with a blank line; I don't see the point of a template. [some discussion of this below]
Template:topspan Template:bl 25   Done Deleted. Replace with a blank line; I don't see the point of a template. [some discussion of this below]
Template:bottom Template:bottom 19656 Keep.
Template:Bottom Template:bottom 1   Done Replace with {{bottom}} and delete.
Template:bottom2 Template:bottom 700   Done Replace with {{bottom}} and delete.
Template:bottom3 Template:bottom 210   Done Replace with {{bottom}} and delete.
Template:bottom4 Template:bottom 38   Done Replace with {{bottom}} and delete.
Template:bottom5 Template:bottom 1   Done Replace with {{bottom}} and delete.
Template:co-top Template:co-top 357 Replace with {{ctop2|Collocations}} and delete.
Template:co-bottom Template:co-bottom 356 Replace with {{cbottom}} and delete.
Template:col Template:col 177 Move |1= to |n= so it can be omitted in the future to get auto-width behavior.
Template:col-auto Template:col-auto 1714 This template is questionable, see discussion in Wiktionary:Grease pit/2022/December#col-auto.
Template:collapse Template:collapse 487 Replace with {{ctop}}, add {{cbottom}} and delete.
Template:collapse-bottom Template:collapse-bottom 30 Delete in favor of {{nav-bottom}}/{{box-bottom}}/{{cbottom}} (whatever name is chosen).
Template:collapse-mid Template:collapse-mid 1   Done Orphan and delete.
Template:collapse-quote Template:collapse-quote 7   Done Delete. Move to Victar's userspace This, that and the other (talk) 07:18, 25 December 2022 (UTC)Reply
Template:collapse-top Template:collapse-top 30 Delete in favor of {{nav-top}}/{{box-top}}/{{ctop}} (whatever name is chosen).
Template:der-auto Template:col-auto 2   Done Replace with {{col-auto}} and delete.
Template:rel-auto Template:col-auto 0   Done Delete.
Template:col-bottom Template:col-bottom 1807 Keep for now?
Template:col-top Template:col-top 1848 Keep for now?
Template:col-u Template:col-u 34 Replace with {{col|sort=0}} and delete.
Template:col1 Template:col1 259 Keep.
Template:col1-u Template:col1-u 25 Replace with {{col1|sort=0}} and delete.
Template:col2 Template:col2 16251 Keep.
Template:rel2 Template:col2 3244 Keep.
Template:der2 Template:col2 9124 Keep.
Template:col2-u Template:col2-u 279 Replace with {{col2|sort=0}} and delete.
Template:col3 Template:col3 64916 Keep.
Template:rel3 Template:col3 6669 Keep.
Template:der3 Template:col3 21969 Keep.
Template:col3-u Template:col3-u 458 Replace with {{col3|sort=0}} and delete.
Template:col4 Template:col4 27323 Keep.
Template:rel4 Template:col4 4491 Keep.
Template:der4 Template:col4 10766 Keep.
Template:col4-u Template:col4-u 258 Replace with {{col4|sort=0}} and delete.
Template:col5 Template:col5 452 Keep.
Template:col5-u Template:col5-u 44 Replace with {{col5|sort=0}} and delete.
Template:columns Template:columns 8   Done Delete.
Template:der-bottom Template:der-bottom 7247 Keep.
Template:der bottom Template:der-bottom 5   Done Replace with {{der-bottom}} and delete.
Template:der-mid Template:der-mid 3430   Done Orphan and delete.
Template:der-mid3 Template:der-mid3 342   Done Orphan and delete.
Template:der-mid4 Template:der-mid4 129   Done Orphan and delete.
Template:der-mid5 Template:der-mid5 6   Done Orphan and delete.
Template:der-top Template:der-top 5960 Rename to {{der-top2}} for consistency with {{top2}}, unless the header is overridden, in which case replace with {{ctop2}}.
Template:der top Template:der-top 5   Done Replace with {{der-top2}} for consistency with {{top2}}, unless the header is overridden, in which case replace with {{ctop2}}; then delete.
Template:der-top3 Template:der-top3 1457 Keep unless the header is overridden, in which case replace with {{ctop3}}.
Template:der-top4 Template:der-top4 277 Keep unless the header is overridden, in which case replace with {{ctop4}}.
Template:der-top5 Template:der-top5 25 Keep unless the header is overridden, in which case replace with {{ctop5}}.
Template:derived terms Template:derived terms 169 Replace with {{col-auto|title=Derived terms}} or with {{col|n=N|title=Derived terms}} where N is the value that the algorithm for this template auto-selects; then delete.
Template:des-bottom Template:des-bottom 293 Replace with {{cbottom}} and delete.
Template:des-mid Template:des-mid 80   Done Orphan and delete.
Template:des-top Template:des-top 295 Replace with {{ctop2|Descendants}} and delete.
Template:desc-bottom Template:desc-bottom 400 Replace with {{cbottom}} and delete.
Template:desc-mid Template:desc-mid 73   Done Orphan and delete.
Template:desc-top Template:desc-top 400 Replace with {{ctop2|Descendants}} and delete.
Template:exp-topx Template:exp-topx 11 Replace with something and delete.
Template:exp-topx+ Template:exp-topx+ 1   Done Delete.
Appendix:French names of colours/ListeCoul E Appendix:French names of colours/ListeCoul E 0 Delete.
Appendix:French names of colours/ListeCoul L Appendix:French names of colours/ListeCoul L 0 Delete.
Template:hcol Template:hcol 239 Replace with {{top2}}, add {{bottom}} at the bottom and delete.
Template:acol Template:hcol 6   Done Replace with {{top2}}, add {{bottom}} at the bottom and delete.
Template:hcol2 Template:hcol2 10 Replace with {{top2}}, add {{bottom}} at the bottom and delete.
Template:acol2 Template:hcol2 5   Done Replace with {{top2}}, add {{bottom}} at the bottom and delete.
Template:hcol3 Template:hcol3 13 Replace with {{top3}}, add {{bottom}} at the bottom and delete.
Template:acol3 Template:hcol3 9   Done Replace with {{top3}}, add {{bottom}} at the bottom and delete.
Template:hcol4 Template:hcol4 8 Replace with {{top4}}, add {{bottom}} at the bottom and delete.
Template:acol4 Template:hcol4 5   Done Replace with {{top4}}, add {{bottom}} at the bottom and delete.
Template:hrow Template:hrow 2961 This is almost exclusively used for Proto-Slavic descendants. We could make a special-purpose template for this use, replace and delete.
Template:hrow+ Template:hrow+ 7   Done Delete.
Template:hyp-bottom Template:hyp-bottom 44 Replace with {{cbottom}} and delete.
Template:hyp-mid Template:hyp-mid 16   Done Orphan and delete.
Template:hyp-mid3 Template:hyp-mid3 16   Done Orphan and delete.
Template:hyp-top Template:hyp-top 25 Replace with {{ctop2|Hypernyms and hyponyms}} and delete.
Template:hyp-top3 Template:hyp-top3 24 Replace with {{ctop3|Hypernyms and hyponyms}} and delete.
User:Benwing2/old-mid2 User:Benwing2/old-mid2 0   Done Delete.
Template:mid2 Template:mid2 5849   Done Orphan and delete.
User:Benwing2/old-mid3 User:Benwing2/old-mid3 0   Done Orphan and delete.
Template:mid3 Template:mid3 2613   Done Orphan and delete.
Template:mid4 Template:mid4 2242   Done Orphan and delete.
Template:mid5 Template:mid5 186   Done Orphan and delete.
Template:mid6 Template:mid6 1   Done Orphan and delete.
Template:nav-bottom Template:nav-bottom 6 Rename to {{cbottom}}.
Template:nav-top Template:nav-top 6 Rename to {{ctop}} and rename |columns= to |n=.
Template:rel-bottom Template:rel-bottom 4654 Keep.
Template:rel-mid Template:rel-mid 1550   Done Orphan and delete.
Template:rel-mid3 Template:rel-mid3 801   Done Orphan and delete.
Template:rel-mid4 Template:rel-mid4 345   Done Orphan and delete.
Template:rel-mid5 Template:rel-mid5 20   Done Orphan and delete.
Template:rel-top Template:rel-top 3463 Rename to {{rel-top2}} for consistency with {{top2}}, unless the header is overridden, in which case replace with {{ctop2}}.
Template:rel-top1 Template:rel-top1 5 Keep unless the header is overridden, in which case replace with {{ctop}}.
Template:rel-top3 Template:rel-top3 937 Keep unless the header is overridden, in which case replace with {{ctop3}}.
Template:rel-top4 Template:rel-top4 394 Keep unless the header is overridden, in which case replace with {{ctop4}}.
Template:rel-top5 Template:rel-top5 29 Keep unless the header is overridden, in which case replace with {{ctop5}}.
Template:related terms Template:related terms 33   Done Replace with {{col-auto|title=Related terms}} or with {{col|n=N|title=Related terms}} where N is the value that the algorithm for this template auto-selects; then delete.
Template:rhyme list begin Template:rhyme list begin 6641 Keep.
Template:rhyme list end Template:rhyme list end 6639 Keep.
Template:Show-head Template:Show-head 16 Replace with {{ctop}} and delete.
Template:show head Template:Show-head 0   Done Delete.
Template:Show-tail Template:Show-tail 15 Replace with {{cbottom}} and delete.
Template:show tail Template:Show-tail 0   Done Delete.
Template:templatetable Template:templatetable 12 Inline code and delete.
Template:th-also Template:th-also 180   Done Replace with {{col3}} and delete.
Template:th-alt Template:th-alt 696 Replace with {{col3}} and delete.
Template:th-ant-list Template:th-ant-list 117   Done Replace with {{col3}} and delete.
Template:th-der Template:th-der 1860 Replace with {{col3}} and deprecate.
Template:th-rel Template:th-rel 486 Replace with {{col3}} and delete.
Template:th-syn-list Template:th-syn-list 858 Replace with {{col3}} and delete.
Template:top2 Template:top2 10596 Keep.
User:Benwing2/old-top3 User:Benwing2/old-top3 0   Done Delete.
Template:top3 Template:top3 6277 Keep.
Template:top4 Template:top4 3265 Keep.
Template:top5 Template:top5 279 Keep.
Template:topx Template:topx 31 Replace with something and delete.
Template:trans-bottom Template:trans-bottom 123345 Keep.
Template:ttbc-bottom Template:trans-bottom 14   Done Replace with {{trans-bottom}} and delete.
Template:ttbc-bot Template:trans-bottom 0   Done Delete.
Template:reqtrans-bottom Template:trans-bottom 0   Done Delete.
Template:trans-bottom/new Template:trans-bottom/new 2   Done Delete as obsolete. Push to production in place of existing {{trans-bottom}}.
Template:trans-mid Template:trans-mid 121580 Orphan and delete after pushing new version to production.
Template:ttbc-mid Template:trans-mid 10   Done Replace with {{trans-mid}}, then orphan and delete after new version of {{trans-mid}} is pushed to production.
Template:reqtrans-mid Template:trans-mid 0   Done Delete.
Template:trans-mid/new Template:trans-mid/new 1   Done Delete as obsolete. Push to production in place of existing {{trans-mid}}.
Template:trans-top Template:trans-top 122641 Keep.
Template:trans-top-also Template:trans-top-also 1770 Keep.
Template:trans-top-see Template:trans-top-also 380 Replace with {{trans-top-also}} and delete.
Template:User:Donnanz/der3-u Template:User:Donnanz/der3-u 399 Replace with {{der3}} and delete.
Template:User:Donnanz/der4-u Template:User:Donnanz/der4-u 0   Done Delete.
Template:txg-der Template:txg-der 732   Done Replace with {{col-auto|txg}} and delete.
Template:vi-der Template:vi-der 2230 Why do we need this? Figure out how to obsolete it.
Template:zcol Template:zcol 23   Done Replace with something and delete.
Template:zcol+ Template:zcol+ 5   Done Delete.
Template:zh-der Template:zh-der 38175 Keep. Replace with {{col3}} and deprecate.
Template:zh-der/fast Template:zh-der/fast 34 A failed experiment; replace with {{zh-der}}{{col3}} and delete.
Template:zh-list Template:zh-der 14656   Done Replace with {{zh-der}}{{col3}} and delete.
Template:zh-syn-list Template:zh-der 1938   Done Replace with {{zh-der}}{{col3}} and deprecate.
Template:zh-ant-list Template:zh-der 48   Done Replace with {{zh-der}}{{col3}} and delete.

Benwing2 (talk) 03:35, 24 December 2022 (UTC)Reply

Update: I added a column labeled "Disposition" containing what I think should be done with the template. I think there should only be three sets of templates: (1) auto-collapsing with items inside the template: {{col}}, {{col2}}, etc.; (2) auto-collapsing with items outside the template: {{ctop}}, {{ctop2}}, etc.; (3) non-collapsing with items outside the template: {{top2}}, etc.. Thoughts? Benwing2 (talk) 06:09, 24 December 2022 (UTC)Reply
Very comprehensive, and very sensible. I endorse the entire list.
To me {{col-top}} says "column", not "collapsible". Perhaps {{box-top}}? This, that and the other (talk) 11:05, 24 December 2022 (UTC)Reply
Seems sensible. Thanks! — Sgconlaw (talk) 11:29, 24 December 2022 (UTC)Reply
@This, that and the other {{box-top}} makes sense to me. Benwing2 (talk) 19:11, 24 December 2022 (UTC)Reply
I support consolidating a lot of these. I do want to note that I have long seen {{rel-top}} used (and have subsequently myself used it, e.g. in blunket and Iroquois) purely to collapse prose, e.g. details and less-important info in a long etymology, without necessarily needing the contents to be divided into columns, though it seems like at some points in its history the template has divided info into columns (I can recall when the ety info in Iroquois used to show up in two columns, although it did not originally, and presently does not again). That is a situation we still need a template for, to collapse info into an expandable box without dividing it into columns, but I'm by no means wedded to {{rel-top}} being that template: it's just what I saw people use for that purpose, but it's not an intuitive name for that use-case. The superficially more intuitively named col-top (collapsible-box-top? no) is apparently short for column- instead. We have T:collapse-top, which should work, although it's currently presented as if it's intended to be used to list translations (which are displayed in columns). (Update, I changed that.) Anyway, as long as there is still a template for "collapsing, with items outside the template, not divided into columns", I support consolidating the proliferation of column templates. I wonder if there's a way to find cases where people have used "column templates" purely for their collapsing functionality, to convert to T:collapse-top: perhaps we look for cases where they're used in the ===Etymology===, ===References=== or ===Further reading=== section, and/or where the contents includes a line of characters longer than some number N, to catch things like
This is a long string of prose someone felt should be collapsed, able to be expanded by interested parties but otherwise out of the way.
as opposed to
  • item in a list
  • another list-item
- -sche (discuss) 01:38, 25 December 2022 (UTC)Reply
@-sche Thanks for your comments. Yes, I am also suggesting using 'col' or 'c' to stand for 'collapse' but it seems confusable with 'column' as you note. I didn't know about {{collapse-top}}; it seems there are ever more column templates I'm finding. The current {{nav-top}}, which I'm proposing to rename to {{ctop}} or {{box-top}}, should work as well as {{collapse-top}}, and the two should be merged. As for uses of {{rel-top}} for collapsing functionality, this appears to work because the items are raw paragraphs rather than list items, and we should be able to check for this by looking for * or # at the beginning of the lines. Benwing2 (talk) 03:52, 25 December 2022 (UTC)Reply
Box-top sounds fine, or frankly we could just keep the very plainly named T:collapse-top (at least as a redirect). Maybe we should avoid using col- or c- for either columns or collapsing, given the ambiguity. - -sche (discuss) 20:19, 26 December 2022 (UTC)Reply
Having thought about this some more, I am not sure if it is a good idea to delete {{bl}}. In certain cases, chiefly complex nested lists of descendants, it can be valuable to have the ability to break the CSS columns manually. It feels neater to me to do that with a template than with a pure blank line in the wikitext, which is more fragile. This, that and the other (talk) 10:28, 26 December 2022 (UTC)Reply
Yeah, a blank line seems liable to be removed as an error / stray whitespace, whereas {{bl}} is at least clearly intentional. If there are cases where we need to insert blank lines, I suppose it's reasonable to have a template for it. - -sche (discuss) 20:19, 26 December 2022 (UTC)Reply
(No objection to deleting the redirect from T:topspan, though, which seems little-used and unintuitively-named.) - -sche (discuss) 04:40, 27 December 2022 (UTC)Reply
Regarding hrow, it also seems to be used in Irish pronunciation sections, and could of course be deployed to other proto-languages besides Slavic, but ... is it better than just using the templates like desc-top and top2 that we use to list descendants (etc) in other entries? Is there some advantage hrow has over those other templates, that we'd need to keep it? The proposal above to make a special-purpose template to replace hrow with just seems like pointless busywork to me; if hrow's functionality is needed, just keep or rename hrow. Or if hrow's functionality is not needed, why not just deprecate it altogether in favour of desc-top, top2, etc? - -sche (discuss) 20:33, 26 December 2022 (UTC)Reply
@-sche Thanks again for your comments. As for {{hrow}}, it seems to force items to get laid out horizontally, which {{top3}} doesn't do, so it may be necessary to keep. Your other comments make a lot of sense and I will update the disposition column accordingly. I have a question about {{trans-top-see}} vs. {{trans-top-also}}. The latter is older and you created the former as a redirect; I would like to eliminate one, do you think {{trans-top-see}} is a better name? It has "see also" functionality so it's not obvious which name is better. Benwing2 (talk) 05:03, 27 December 2022 (UTC)Reply
I will let -sche respond for himself, but I note that we have {{trans-see}}, {{prefixsee}}, {{seeCites}} (the name of which I can never remember), etc, so "see" would seem best. As a tangent, I have a fuzzy memory that {{also}} used to be called {{see}} too, but then it was noticed that the code see was assigned to the language Seneca, so the template had to be moved (this was in the pre-Lua days where each language code got its own template). Now {{see}} is something else. This, that and the other (talk) 06:50, 27 December 2022 (UTC)Reply
I probably created the redirect because redirects are cheap and I could never remember what the canonical template was called. Neither name seems immediately better or worse than the other, although TTO makes a good point that -see would be consistent with other sees. (Is there a need to delete the redirect from whichever name we don't lemmatize, though? If it's just a redirect and not a separate redundant template, then it's not dulicating any template code and won't fall out of sync. OTOH I admit this one is of lower importance to keep, since typing Template:trans-top- into the search bar will bring up the right template.) - -sche (discuss) 17:05, 27 December 2022 (UTC)Reply
(Notifying Atitarev, Tooironic, Fish bowl, Justinrleung, Mar vin kaiser, RcAlex36, The dog2, Frigoris, 沈澄心, 恨国党非蠢即坏, Michael Ly, Wpi31, ND381): Apologies for the wide ping. I'd like to get rid of the aliases for {{zh-der}} (namely {{zh-list}}, {{zh-syn-list}} and {{zh-ant-list}}). Is this OK for the Chinese editors, and if so is {{zh-der}} the correct name or should it be {{zh-list}}? Benwing2 (talk) 05:05, 27 December 2022 (UTC)Reply
@Benwing2: I'm not sure about {{zh-list}}, but {{zh-syn-list}} and {{zh-ant-list}} need to stay because the templates {{zh-syn-saurus}} and {{zh-ant-saurus}} depend on these two, respectively. — justin(r)leung (t...) | c=› } 06:37, 27 December 2022 (UTC)Reply
@Justinrleung Not sure I understand. {{zh-syn-saurus}} and {{zh-ant-saurus}} do not actually depend on either {{zh-syn-list}} and {{zh-ant-list}}, but instead refer to {{zh-list}} in the module (Module:zh/templates), and since {{zh-list}} is just an alias for {{zh-der}}, it's trivial to change the module code to refer to {{zh-der}} instead. Benwing2 (talk) 06:53, 27 December 2022 (UTC)Reply
@Benwing2: Line 179 in the the current version of the module is where the dependence on those two templates is. It's not very ideal that it's trying to extract things from the wikitext, but that's how it's currently set up. — justin(r)leung (t...) | c=› } 07:04, 27 December 2022 (UTC)Reply
@Justinrleung I see, why can't we just change the code to look for {{zh-der}} (or even more safely, look for {{zh-der}} inside of a =Synonyms= or =Antonyms= section, as appropriate)? Benwing2 (talk) 07:24, 27 December 2022 (UTC)Reply
@Benwing2: If that's doable, then sure, I don't have any objections. It would seem to be inappropriate to have the one template be called "der", though, if it's used more widely than for derived terms/compounds. — justin(r)leung (t...) | c=› } 07:37, 27 December 2022 (UTC)Reply
@Justinrleung It seems to be called {{zh-der}} because it defaults to displaying "Derived terms from PAGENAME" -- but only when there are more than 72 entries and not on Thesaurus pages. All this Chinese-specific code is really terrible IMO. Maybe {{zh-list}} or {{zh-col}} is a better name (note that {{zh-der}} claims to work like {{der3}}, which is a redirect to {{col3}}). Benwing2 (talk) 08:07, 27 December 2022 (UTC)Reply
@Benwing2: I agree that the Chinese-specific code is quite unsatisfactory. {{zh-col}} sounds good as a replacement, but it would probably be best to make it mirror {{col3}} behaviour, at least in the title. (Other than the 72-entry threshold, there is also a |fold= parameter that collapses the list.) — justin(r)leung (t...) | c=› } 16:50, 27 December 2022 (UTC)jReply
Could we please also add Template:User:Donnanz/der4-u? Theknightwho (talk) 19:09, 30 March 2023 (UTC)Reply
Also {{txg-der}}, which (as the largest contributor to Tangut) I think can be fully replaced by {{col-auto}}. Theknightwho (talk) 23:35, 30 March 2023 (UTC)Reply
  Support deletion of redundant templates and redirects, and keeping the number of column temlates to a sane minimum. Taylor 49 (talk) 14:34, 4 April 2023 (UTC)Reply
@DCDuring That's not really possible with nested templates because the outer template sees the expansion of the inner template rather than the template itself. The best solution I think is a specialized column template that supports the equivalent of {{vern}} and {{taxlink}} using inline modifiers. Benwing2 (talk) 14:39, 17 April 2023 (UTC)Reply
Or just something that, 1., doesn't alphabetize at all, 2., doesn't have a required lang parameter, 3., allows specification of the number of columns, and, 4., allows a title. Collapsability and auto-balancing would also be very helpful. DCDuring (talk) 15:31, 17 April 2023 (UTC)Reply
I've responded to the thread about this on the BP, but just putting it here that this isn't necessary, as column templates already take the formatting used by {{vern}} and {{taxlink}} into account when sorting (among others). There's a function in Module:utilities called get_plaintext which is called by Module:collation that finds the text which is actually visible on the page, and it's that which is used for sorting purposes. Previously, sorting was done in a much cruder way, which is why we had problems with this. Theknightwho (talk) 19:10, 5 May 2023 (UTC)Reply

In the interests of making progress, here is an inventory of the remaining templates. I have removed the translation templates (not really in scope for this discussion) and grouped into the three classes identified by Benwing on 24 December 2022:

Aliased template Canonical template #Uses Disposition
1. auto-collapsing (first 3 rows always visible) with items inside the template
Template:col Template:col 177 Move |1= to |n= so it can be omitted in the future to get auto-width behavior.
Template:col-auto Template:col-auto 1714 This template is questionable, see discussion in Wiktionary:Grease pit/2022/December#col-auto.
Template:col-u Template:col-u 34 Replace with {{col|sort=0}} and delete.
Template:col1 Template:col1 259 Keep.
Template:col1-u Template:col1-u 25 Replace with {{col1|sort=0}} and delete.
Template:col2 Template:col2 16251 Keep.
Template:rel2 Template:col2 3244 Keep.
Template:der2 Template:col2 9124 Keep.
Template:col2-u Template:col2-u 279 Replace with {{col2|sort=0}} and delete.
Template:col3 Template:col3 64916 Keep.
Template:rel3 Template:col3 6669 Keep.
Template:der3 Template:col3 21969 Keep.
Template:User:Donnanz/der3-u Template:User:Donnanz/der3-u 399 Replace with {{der3}} and delete.
Template:col3-u Template:col3-u 458 Replace with {{col3|sort=0}} and delete.
Template:col4 Template:col4 27323 Keep.
Template:rel4 Template:col4 4491 Keep.
Template:der4 Template:col4 10766 Keep.
Template:col4-u Template:col4-u 258 Replace with {{col4|sort=0}} and delete.
Template:col5 Template:col5 452 Keep.
Template:col5-u Template:col5-u 44 Replace with {{col5|sort=0}} and delete.
Template:th-alt Template:th-alt 696 Replace with {{col3}}{{alt}} and delete.
Template:th-der Template:th-der 1860 Replace with {{col3}} and deprecate.
Template:th-rel Template:th-rel 486 Replace with {{col3}} and delete.
Template:th-syn-list Template:th-syn-list 858 Replace with {{col3}} and delete.
2. auto-collapsing (into a NavFrame) with items outside the template
Template:box-top Template:box-top 16 Replace with {{ctop}} and delete. However, many of the uses require auditing.
Template:box-bottom Template:box-bottom 15 Replace with {{cbottom}} and delete.
Template:Show-head Template:box-top 16 Replace and delete.
Template:Show-tail Template:box-bottom 15 Replace and delete.
Template:co-top Template:co-top 357 Replace with {{ctop2|Collocations}} and delete.
Template:co-bottom Template:co-bottom 356 Replace with {{cbottom}} and delete.
Template:collapse Template:collapse 487 Replace with {{ctop}}, add {{cbottom}} and delete.
Template:collapse-top Template:collapse-top 30 Delete in favor of {{nav-top}}/{{box-top}}/{{ctop}} (whatever name is chosen).
Template:collapse-bottom Template:collapse-bottom 30 Delete in favor of {{nav-bottom}}/{{box-bottom}}/{{cbottom}} (whatever name is chosen).
Template:der-top Template:der-top 5960 Rename to {{der-top2}} for consistency with {{top2}}, unless the header is overridden, in which case replace with {{ctop2}}.

This, that and the other (talk) adds: If the template contains a simple list of {{l}} templates or bare wikilinks, and the header is not overridden, it should be auto-converted to {{der2}}. Same goes for {{der-top3}}, {{rel-top}} etc.

Template:der-top3 Template:der-top3 1457 Keep unless the header is overridden, in which case replace with {{ctop3}}.
Template:der-top4 Template:der-top4 277 Keep unless the header is overridden, in which case replace with {{ctop4}}.
Template:der-top5 Template:der-top5 25 Keep unless the header is overridden, in which case replace with {{ctop5}}.
Template:der-bottom Template:der-bottom 7247 Keep.
Template:des-top Template:des-top 295 Replace with {{ctop2|Descendants}} and delete.
Template:des-bottom Template:des-bottom 293 Replace with {{cbottom}} and delete.
Template:desc-top Template:desc-top 400 Replace with {{ctop2|Descendants}} and delete.
Template:desc-bottom Template:desc-bottom 400 Replace with {{cbottom}} and delete.
Template:hyp-top Template:hyp-top 25 Replace with {{ctop2|Hypernyms and hyponyms}} and delete.
Template:hyp-top3 Template:hyp-top3 24 Replace with {{ctop3|Hypernyms and hyponyms}} and delete.
Template:hyp-bottom Template:hyp-bottom 44 Replace with {{cbottom}} and delete.
Template:nav-top Template:nav-top 6 Rename to {{ctop}} and rename |columns= to |n=.
Template:nav-bottom Template:nav-bottom 6 Rename to {{cbottom}}.
Template:rel-top Template:rel-top 3463 Rename to {{rel-top2}} for consistency with {{top2}}, unless the header is overridden, in which case replace with {{ctop2}}.

This, that and the other (talk) adds: If the template contains a simple list of {{l}} templates or bare wikilinks, and the header is not overridden, it should be auto-converted to {{rel2}}. Same goes for {{rel-top3}}, {{der-top}} etc.

Template:rel-top1 Template:rel-top1 5 Keep unless the header is overridden, in which case replace with {{ctop}}.
Template:rel-top3 Template:rel-top3 937 Keep unless the header is overridden, in which case replace with {{ctop3}}.
Template:rel-top4 Template:rel-top4 394 Keep unless the header is overridden, in which case replace with {{ctop4}}.
Template:rel-top5 Template:rel-top5 29 Keep unless the header is overridden, in which case replace with {{ctop5}}.
Template:rel-bottom Template:rel-bottom 4654 Keep.
3. non-collapsing (purely creates a columnar arrangement) with items outside the template
Template:top2 Template:top2 10596 Keep.
Template:top3 Template:top3 6277 Keep.
Template:top4 Template:top4 3265 Keep.
Template:top5 Template:top5 279 Keep.
Template:bottom Template:bottom 19656 Keep.
Template:hcol Template:hcol 239 Replace with {{top2}}, add {{bottom}} at the bottom and delete.
Template:hcol2 Template:hcol2 10 Replace with {{top2}}, add {{bottom}} at the bottom and delete.
Template:hcol3 Template:hcol3 13 Replace with {{top3}}, add {{bottom}} at the bottom and delete.
Template:hcol4 Template:hcol4 8 Replace with {{top4}}, add {{bottom}} at the bottom and delete.
Template:col-top Template:col-top 1848 {{col-top|N}} is equivalent to {{topN}}. Keep for now?
Template:col-bottom Template:col-bottom 1807 Keep for now?
Template:rhyme list begin Template:rhyme list begin 6641 Keep.

This, that and the other (talk) adds: This is identical to {{top3}} (or the "topX" template corresponding to the chosen number of columns) except it that has a different CSS class. Not sure if it is really necessary to keep this separate.

Template:rhyme list end Template:rhyme list end 6639 Keep.
Other templates needing special attention
Template:derived terms Template:derived terms 169 See separate discussion below: #Template:derived terms
Template:templatetable Template:templatetable 12 Inline code and delete.

This, that and the other (talk) says: Rename and keep. It is used on relatively few pages, but on those pages it is used heavily.

Template:hrow Template:hrow 2961 This is almost exclusively used for Proto-Slavic descendants. We could make a special-purpose template for this use, replace and delete.

This, that and the other (talk) adds: This template has a lot of potential for complex descendants lists. I say keep, perhaps rename.

Template:topx Template:topx 31 Replace with {{hrow}} and delete.
Template:exp-topx Template:exp-topx 11 Replace with {{hrow}} and delete.
Template:vi-der Template:vi-der 2230 Why do we need this? Figure out how to obsolete it.
Template:zh-der Template:zh-der 38175 Replace with {{col3}} and deprecate.
Template:zh-der/fast Template:zh-der/fast 34 A failed experiment; replace with {{col3}} and delete.

Eventually I would love to see further tidying as per my comments at User:This, that and the other/column templates, but the actions set out in the table above are conservative and will result in little change to the actual display of entries. This, that and the other (talk) 01:43, 19 August 2023 (UTC)Reply

@This, that and the other Regarding your comment on keeping {{hrow}}, I would much prefer if we actually created a dedicated template for descendant lists. This would solve many of the issues we're currently having with formatting by ensuring that descendant sections are consistent. Theknightwho (talk) 02:07, 19 August 2023 (UTC)Reply
Thanks! I'll review this at some point soon and see if there's further progress I can make. Benwing2 (talk) 03:00, 19 August 2023 (UTC)Reply
@This, that and the other I don't really have a horse in this race other than this, which I would like to add as feedback: I really like how {{col-auto}} removes the need to think about the number of columns and would like for it to be preserved, or at the very least for it to be replaced with another list template with similar automatic column-balancing features. Anyway, I welcome any effort to cut out dead wood and reduce bloat. — Mnemosientje (t · c) 16:00, 22 August 2023 (UTC)Reply

I am going to replace "th-alt" with "alt" instead, better option than "col3". --Octahedron80 (talk) 13:32, 29 November 2023 (UTC)Reply

Template:R:Shuri-Naha Dialect Dictionary edit

The site shutdown more than 2 years ago and it's no longer accessible. So should we delete this? This includes removing all references to this template and putting a new one (if there isn't any). Chuterix (talk) 20:16, 24 December 2022 (UTC)Reply

@Chuterix: was the site archived at the Internet Archive? — Sgconlaw (talk) 20:39, 24 December 2022 (UTC)Reply
Yes but I don't know if the full database is archived. Chuterix (talk) 20:46, 24 December 2022 (UTC)Reply
@Chuterix: when Lexico was shut down we redirected {{R:Lexico}} to the Internet Archive. Not all entries were archived there, unfortunately, so I have been removing the template manually in those cases when I come across them. We could do the same for the Shuri-Naha Dialect Dictionary. — Sgconlaw (talk) 08:37, 25 December 2022 (UTC)Reply
@Chuterix: Many of the entries seem to be taken from the Okinawa-go jiten (沖繩語辞典) which is freely accessible on CORE. — Ceso femmuin mbolgaig mbung, mellohi! (投稿) 06:50, 26 December 2022 (UTC)Reply
@Kwékwlos, 荒巻モロゾフ, Eirikr, TAKASUGI Shinji, Atitarev, Fish bowl, Poketalker, Cnilep, Marlin Setia1, Huhu9001, 片割れ靴下, Onionbar, Shen233, Alves9, Cpt.Guapo, Sartma, Lugria, Mellohi!, anyone else interested in Japonic/Ryukyuan linguistics: The problem is it's only the Okinawan Dictionary that's available for free. The Ryukyu-go onsei database also hosted the Kunigami (Nakijin dialect), Northern Amami Oshima (Yamatohama dialect), and Miyako dialects, that which I can't find anywhere else online.
I am now undergoing the process of deleting this template from all Okinawan entries. Some time I will delete all remaining template usage involving RGODB (Ryukyu-go onsei database) in other dialects. Chuterix (talk) 16:07, 9 February 2023 (UTC)Reply
Any news? Chuterix (talk) 01:55, 29 March 2023 (UTC)Reply
If Sgconlaw's suggestion, to point Internet Archive in the manner used for Lexico, is possible, I like the idea. If there are technical difficulties, or more false-positives than actually archived entries, though, it may not be worthwhile. Cnilep (talk) 05:08, 10 February 2023 (UTC)Reply

January 2023 edit

Category:Breakable Han characters edit

The category seems to be a very small set of characters that may or may not actually be derived from a process of "breaking". I also don't know if the title of the category is appropriate. — justin(r)leung (t...) | c=› } 02:37, 19 January 2023 (UTC)Reply

What do you mean? I'm not sure how much you know about Chinese glyph origins, but is it not obvious that 彳亍 is a broken up version of 行? It's pretty much accepted that 行 came first and then the other characters were derived from breaking it into two halves. And thus with all other characters in the category. WiktionariThrowaway (talk) 00:46, 20 January 2023 (UTC)Reply
Any objections? It's been over 2 months. WiktionariThrowaway (talk) 17:09, 26 March 2023 (UTC)Reply
@Justinrleung any response here? Even as a non-CJK speaker I kind of understand what this category is doing, even though the name feels wrong (it seems like it should be "Han characters derived by breaking" or something). This, that and the other (talk) 07:04, 31 March 2023 (UTC)Reply
Is there a formal name for this phenomenon? If so we should use it. — Sgconlaw (talk) 12:02, 31 March 2023 (UTC)Reply
@WiktionariThrowaway, This, that and the other, Sgconlaw: Sorry for not checking again. I kind of understand what the category is for now, but I do agree that the name of the category looks wrong since the characters in the category are not breakable AFAICT. While 彳亍 is from "breaking up" 行, other uses of 彳 (mostly as a radical) are simplifications of 行 rather than "breaking up" the character. I'm not sure if there's an established name for this phenomenon. @RcAlex36, Wpi31, do you know of any names for this? — justin(r)leung (t...) | c=› } 15:32, 1 April 2023 (UTC)Reply
@Justinrleung: ah. Well, it's clear that the category name is wrong, because the category contains characters that are the result of "breaking" other characters, so the first-mentioned characters are not themselves "breakable". My question is whether there is any particular value in having a category of characters that are derived from other characters in this way. For example, if such "breaking" (for want of a better term) is not a common way of forming new characters, then it doesn't sound very useful. The fact that such characters are formed from other characters is already explained in the relevant etymology sections. — Sgconlaw (talk) 15:43, 1 April 2023 (UTC)Reply
「兵」字省掉末筆。乒、乓二字皆為後出新字,當為「兵」字之省形。或以為兵械相碰常缺,故从「兵」省。寫法參「兵」字。: 省形 may be a Chinese name for this, but that usually refers to omission of the entire component rather than what is done here.
I doubt there is a proper academic name for this, not even in Chinese. It seems that all these characters come in (vaguely) mirrored pairs, each constituting half of a common character, so maybe "Han characters with etymologically-related mirror characters" or "Han characters derived from halving a character"? – Wpi31 (talk) 16:07, 1 April 2023 (UTC)Reply
@Wpi31: yes, but is there even any point in categorizing characters in this way? The category currently has just 14 entries. Are there likely to be more? — Sgconlaw (talk) 18:00, 1 April 2023 (UTC)Reply
There are several examples that aren't even in Unicode, and which may be added in future extensions. I've listed some of them here. WiktionariThrowaway (talk) 18:58, 1 April 2023 (UTC)Reply

February 2023 edit

Category:Uncategorized templates edit

Redundant, and in fact inferior, to Special:UncategorizedTemplates. As cat:Uncategorized templates explains, the category is added automatically when a template page uses {{documentation}} but its documentation page does not exist, and it is included in the preload "template" for creating documentation pages. But this approach has made the category inconsistent in two ways:

  1. Some templates ({{hyw-conj}}, {{tli-inalienable-noun-inflection}}) are correctly categorized in template categories, but the categories are listed on the main template page rather than the documentation page, meaning they are still members of cat:Uncategorized templates.
  2. Many templates ({{'}}, {{BSD}}, {{FWOTD}}, and all others at Special:UncategorizedTemplates) are actually uncategorized, but because they do not use {{documentation}} (and do not have cat:Uncategorized templates explicitly on their documentation pages, if they even exist) they are not members of cat:Uncategorized templates.

If we delete and depopulate the category, the special page will become more useful than either is currently.

One counterargument I can see is that templates in, for example, cat:Templates and modules needing documentation and no other categories are insufficiently categorized, but will not appear at Special:UncategorizedTemplates. However, the only such categories I'm aware of are meant to actively draw editors' attention to some lack or problem with the templates, and should therefore be at least removed, if not replaced, when said lack or problem is fixed. — excarnateSojourner (talk · contrib) 21:14, 11 February 2023 (UTC)Reply

Delete - I completely agree. Theknightwho (talk) 18:49, 12 February 2023 (UTC)Reply
Del per nom. - -sche (discuss) 21:20, 2 March 2023 (UTC)Reply
Delete per nom. Taylor 49 (talk) 17:18, 16 May 2023 (UTC)Reply

Template:list:Vaṅga Bengali calendar months/bn edit

According to the Wikipedia article of Eastern Bengali, "Eastern Bengali or Vaṅga is a nonstandard dialect cluster of Bengali spoken in most of Bangladesh and Tripura". The list of Bengali calendar months in Vanga is produced possibly with an assumption that Vanga is a standardised written variant of Bengali. However, it is not the case and (as far as I know) Vanga speakers use Standard Bengali (based in Nadia, WB, India) in writing. Sbb1413 (he) (talkcontribs) 18:37, 19 February 2023 (UTC)Reply

Is this variety never written, or just uncommonly? If these terms are attested then the template should be kept. Worth noting that we even have Vaṅga entries for many of these months, like জেঠ (jeṭh), আঢ় (aṛh), হাওন (haōn), etc., and Category:Vanga Bengali has 250 entries total covering a much broader range of topics, so it seems like specifically targeting the calendar template is the wrong way to go about this if you're challenging whether this dialect cluster is written at all. (Compare Westrobothnian above.) The user who created this template and most if not all of these entries, User:Sylotoid, may be able to comment.
I should state that I know next to nothing about Eastern Bengali, except for what can be gathered by reading the first two sections of the Wikipedia article. 70.172.194.25 03:28, 21 February 2023 (UTC)Reply

Template:blockquote-top edit

An untranscluded, undocumented alternative to {{blockquote}}, created by Ruakh in 2010. It looks like this:

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

From reading the template code, it seems to open two <div> tags with the expectation that the template user would invoke the template, follow it with the quote, and then manually close the <div>s (e.g. {{blockquote-top}}Lorem ipsum</div></div>). Its only parameter sets the colour of the border. The default colour is generated using the current hour, minute, and second, effectively meaning it changes each time the page is reloaded. IMO it provides no advantages over just using {{blockquote}}.

— excarnateSojourner (talk · contrib) 20:11, 21 February 2023 (UTC)Reply

The reason it's untranscluded is that it's intended for use via subst:-ing. (So it's not true that the color "changes each time the page is reloaded"; rather, the color is fixed at time of use.) But I haven't used it in quite a while, and I don't think I've seen anyone else use it in quite a while, either. So if no one jumps in to say that they still use it, please feel free to delete it. (In that case I may end up re-creating it in my userspace.) —RuakhTALK 06:20, 23 February 2023 (UTC)Reply
You can see some places where it's been subst:-ed here. 70.172.194.25 07:47, 23 February 2023 (UTC)Reply
It hasn't been used for a long time, or much at all, based on those results. —Al-Muqanna المقنع (talk) 10:13, 23 February 2023 (UTC)Reply
Even after substitution, the code in brackets remains, so the colors still continue to change. I cant tell what the change depends on, though ... from the code, it looks like it should be changing every second, so effectively it would be every time the page is reloaded ... but it seems not to be. But it definitely still changes .... and it also appears differently for me on different devices, possibly because their clocks are slightly out-of-sync. I really like this template, and in particular how it is possible to center it whereas with {{blockquote}} it is either not possible or I couldnt figure out how ... but the color-changing behavior stands out a lot and might be seen as a distraction from an otherwise down-to-earth conversation, so perhaps it would be best if it were kept in userspace where people could use it but not as an official replacement for the main template. Soap 10:07, 24 February 2023 (UTC)Reply
The color depends on when the page was last rendered, which can occur when a page is edited, when its cache is purged, when changes need to be propagated due to edits in templates, etc. I do not understand the point of having the colors change at all honestly, but I do not especially mind it either. It might appear differently on mobile and desktop devices (or rather skins?) because I think the WMF maintains separate caches for them. 70.172.194.25 05:15, 25 February 2023 (UTC)Reply

March 2023 edit

Appendix:Glossary of Welsh words of English origin edit

This page originated on Wikipedia and still exists on Wikipedia. (I misread. The Wikipedia page is Welsh>English, not English>Welsh. Nonetheless ....) Moreover, we have a much better way of listing Welsh words of English origin through our category system, where the main category is Category:Welsh terms derived from English. The appendix list is much shorter, and updating it would be quite a lot of work. Moreover it would be in constant need of updates, unlike our category system, which refreshes automatically. I porpose we save ourselves some time by deleting this appendix page. Soap 16:17, 9 March 2023 (UTC)Reply

Delete, the category is much better. Ultimateria (talk) 02:11, 24 March 2023 (UTC)Reply

Category:Untranscluded templates edit

Redundant and inferior to Special:UnusedTemplates. The category describes itself as containing templates that are not transcluded anywhere (exactly what the special page is for), but contains only twelve of the thousands of such templates listed at the special page. IMO the automatic nature of the special page makes it clearly superior to manual categorization.

Category:Untranscluded templates is not to be confused with Category:Unused templates, which is supposed to contain templates that are not transcluded anywhere in mainspace.

— excarnateSojourner (talk · contrib) 22:16, 14 March 2023 (UTC)Reply

Do we have a category for templates that are designed to be substituted? Admittedly, the use of substitution (subst:) is much rarer on Wiktionary compared to Wikipedia, but still, it would be nice to categorise these templates so we know when a template should not be deleted for lack of use. This, that and the other (talk) 00:25, 30 October 2023 (UTC)Reply

Category:Chinese terms by their individual characters and its subcategories edit

I don't see how these categories will be realistically usable/maintainable, unless this could be added automatically with a template, given that the total amount of entries in Category:Chinese terms written in foreign scripts and Category:Chinese terms written in multiple scripts exceed 1000. – Wpi31 (talk) 09:43, 23 March 2023 (UTC)Reply

@Wpi31 There is already a mechanism for adding these categories automatically, called standardChars. I don't know why it isn't enabled here. Benwing2 (talk) 23:55, 30 March 2023 (UTC)Reply

April 2023 edit

Category:Noun plural forms by language edit

The last two discussions about this category (BP, RFC) led to the deletion of a few subcategories and little else. Its purpose is unclear and it is not consistently being populated. Is it actually needed for any language? Ultimateria (talk) 01:05, 17 April 2023 (UTC)Reply

I think the major issue is that people are hesitant to re-categorise languages they're not familiar with. I can't think of any language that would have a need for this category, even though I have added it in the past. Thadh (talk) 15:58, 17 April 2023 (UTC)Reply
@Ultimateria, Thadh: FWIW, it appears that Classical Nahuatl and Swahili add entries to their respective noun plural forms categories through accelerated entry generation for non-lemma forms (see Module:accel/nci and Module:accel/sw). There may well be others. 0DF (talk) 01:22, 8 December 2023 (UTC)Reply

May 2023 edit

Template:el-link-ttip edit

Template:el-link-ttip-sm edit

These are link templates for Greek that show transliterations as a tooltip instead of displaying them on the page. e.g. αυτοκίνητο  instead of αυτοκίνητο (aftokínito). Several disadvantages here:

  • They are extremely basic (i.e. other than the transliteration, they don't call into Lua at all). That means they lack many of the features most users expect from link templates.
  • They are nonstandard by comparison to every other link template, and provide no indication that the transliteration is in a tooltip. That means many (most?) users won't realise it's there.
  • They can't remove diacritics for Greek, so any links that contain them will break (unlike the standard link template).
  • They are useless for mobile, where tooltips usually don't work.
  • It's not clear whether these are supposed to be used in place of {{l}} or {{m}}.
  • They're part of a language-specific ecosystem that's an extra maintenance headache for no real benefit.

We should replace all instances of these with normal link templates. If transliterations need to be suppressed, then that's fine, but we should not be using these kinds of weird bespoke templates. Pinging @Saltmarsh, who made these. Theknightwho (talk) 01:26, 22 May 2023 (UTC)Reply

I'm sorry that you don't like these templates @Theknightwho.
Examples of their use
  1. {{el-link-ttip}}: καΐκι 
  2. {{el-link-ttip-sm}} is similar but produces smaller characters: καΐκι 
  • Where possible transliteration is introduced to help users unfamiliar with a foreign script. In many places where space in a table is limited these templates enable transliterations to be available, admittedly hidden but there for the curious. Our headword template uses similar bullets to indicate the transliteration there: viz. καΐκι (kaḯkim.
  • The templates were written for Standard Modern Greek (SMG) entries and only intended for use there, and then ONLY within templates and specialist tables, note that such pages would only be edited by someone with experience.
  • There are many situations where transliterations of long words create a space problem, it was felt that any transliteration was better than none. (The standard headword template used just such a character to help users.
You list several "disadvantages" of these templates:
  • They are extremely basic — I could say "so what!" — their use is limited as stated above, most editors will not need to use them.
  • (most?) users won't realise it's there — I have covered this above.
  • They can't remove diacritics for Greek — this is wrong, see examples above, SMG is limited to a single stress or diaresis. They are not intended for Ancient Greek or Katharevousa.
  • They are useless for mobile — OK a shortcoming.
  • It's not clear… to be used in place of {{l}} or {{m}} — I hope that I have clarified this above..
  • They're part of a language-specific ecosystem that's an extra maintenance headache for no real benefit. — Well I believe there is a benefit and I question your use of "weird", their structure is easily understood. If maintenance ever became an issue a solution could be sought then.
  — Saltmarsh🢃 11:10, 22 May 2023 (UTC)Reply
@Saltmarsh
  1. The mobile issue alone is significant enough that we shouldn’t be using these templates.
  2. The nonstandard layout is confusing for readers, not just editors.
  3. Saying they’re only used in specific situations actually makes things worse, because that creates a mish-mash of layouts.
  4. The major problem with being simple is that users will not be expecting that, so will assume diacritics are removed (and modern Greek does occasionally use them). I see these are used in declension templates, which means they’re functionally useless if the headword has an extra diacritic, because links to inflectional forms won’t work.
  5. You mention katharevousa, but it actually comes under the Greek language code, yet these templates cannot be used with it for the above reason. That is a serious problem.
  6. You created these templates quite recently, and long after the normal link templates were well-established, which means they can't be grandfathered in as pre-dating the usual templates.
  7. It is absolutely possible to handle transliterations comfortably in tables - see how a language like Russian handles them.
  8. It is really misleading to compare this approach to the headword template, which uses the bullet as a link to the transliteration scheme. That’s very different.
Please reconsider this approach, as having tons of minor, bespoke templates used in piecemeal ways is a barrier of entry to editors. I notice the exact same issue came up with Greek headword templates in the past, and it was only solved there due to a bot doing a mass replacement. We should do something similar with these. Theknightwho (talk) 11:35, 22 May 2023 (UTC)Reply

Template:el-UK-US edit

The provides links to both spellings of English words that end in -ize-ise. e.g. {{el-UK-US|national|ise}} gives nationalise (UK), nationalize (US).

  • This is not a helpful feature, as it clutters entries.
  • It isn't specific to Greek, so why does this need to be a Greek template?

Theknightwho (talk) 01:36, 22 May 2023 (UTC)Reply

  • Good bilingual dictionaries will give US and UK spellings of translations.
The χρώμα entry gives:   colour (UK), color (US)
  • This is precisely what templates are intended for, ease of entry for the editor and a standard output layout. Meaning that a global change to the layout can be easily achieved. I think it's useful. It doesn't need to be specific for Greek. Make it universal!
  — Saltmarsh🢃 11:54, 23 May 2023 (UTC)Reply
@Saltmarsh It has literally nothing to do with Greek, and it's an extremely clunky way of conveying information. colorcolour is much more elegant, and can be done with the normal link templates just fine: {{l|en|color//colour}}. Theknightwho (talk) 04:08, 24 May 2023 (UTC)Reply
Delete. Vininn126 (talk) 10:00, 22 May 2023 (UTC)Reply
I'm not particularly opposed to this template; our traditional reluctance to present both of the major spelling variants as glosses for foreign terms is one of many things that makes Wiktionary less friendly for those not already familiar with a language (English in this case). However, it obviously needs renaming if kept. Why it was ever created with an el- prefix baffles me. {{l-UK-US}} perhaps? This, that and the other (talk) 03:35, 24 May 2023 (UTC)Reply
I'd oppose this as well, because doing it that way becomes really awkward when someone wants to use it outside of {{l}}: we'd end up with even more horrible wikitext like {{cog|en|-}} {{l-uk-us|color|colour}} in entries. Much better to have something like {{cog|en|color//colour}}, which has the added flexibility of allowing other spelling variations, too, as spelling variations are sometimes more complex than that. These kinds of limitations are why templates like {{zh-l}} are being phased out. Theknightwho (talk) 04:23, 24 May 2023 (UTC)Reply
Such formatting would also be useful for dual-script languages such as Mongolian and Serbo-Croatian, solving two issues with one format. Vininn126 (talk) 10:28, 24 May 2023 (UTC)Reply
Precisely why I chose it, yes! It may be possible to automate it for English, though that’s likely to run into attestation issues with very rare terms.Theknightwho (talk) 16:21, 24 May 2023 (UTC)Reply
Usages such as {{cog|en|color//colour}} should be expunged as depending on undocumented behaviour - or the behaviour should be documented. --RichardW57m (talk) 09:48, 26 May 2023 (UTC)Reply
We’re not going to remove features, Richard. Theknightwho (talk) 12:45, 26 May 2023 (UTC)Reply
  • Delete, we shouldn't be giving both spellings in glosses in the first place (it's ridiculous and redundant) and even if we do, we shouldn't be doing it like this. —Mahāgaja · talk 16:09, 24 May 2023 (UTC)Reply
  • Those unfamiliar with a term (familiarise/ize) need both spellings, good bilingual dictionaries will give both, and this is the best way of doing it. If the el- prefix is a problem — make it universal.   — Saltmarsh🢃 04:28, 26 May 2023 (UTC)Reply
  • Agreed. It is standard for bilingual dictionaries to offer both spellings, with some sort of label indicating where the spelling is used (just like this template does). Note that with a modification of the template, we could still have both spellings link to whichever entry host the definitions. I would support making this template more general and using it more widely. Andrew Sheedy (talk) 00:13, 4 June 2023 (UTC)Reply
    @Andrew Sheedy As noted elsewhere on the thread, there are much better ways of handling this issue than a dedicated template. Theknightwho (talk) 12:09, 4 June 2023 (UTC)Reply
The prefix in the name probably comes from it being part of the Greek subsystem of Wiktionary! The template is only used in the translation of Greek words. Note that that is an explanation of the name, not a justification of the name. --RichardW57m (talk) 09:43, 26 May 2023 (UTC)Reply
FWIW I think it's a good idea to include both UK and US variants in definitions; when I encounter UK-only usages it sometimes trips me up (esp. when it's a word like swot that I've never heard of, but even the -ize/-ise and -o(u)r differences stand out to me and slow down my reading). As a result I tend to fix such usages to include both variants. IMO it potentially looks nice to have the {{a|UK}} and {{a|US}} tags explicit, but I only think this is really needed when the terms are totally different rather than just spelling variations; e.g. for wrench vs. spanner or (railroad) switch vs. points it's good to have the variant tags, but for color/colour or nationalize/nationalise it's enough to just list both spellings, and the reader can use the one that is familiar and ignore the other. In practice that means we can use User:Theknightwho's suggestion of {{l|en|color//colour}} in most cases, and manually add the tags for the more complex cases. Benwing2 (talk) 20:26, 13 June 2023 (UTC)Reply
Delete. No reason this should be language-specific. Ultimateria (talk) 18:36, 2 July 2023 (UTC)Reply
Delete per Ultimateria. I also tend to agree with Mahagaja that it's not useful to give both spellings (OTOH I think giving both a UK word and a US one is fine). But even if we do, I don't think the definition of a foreign term is the place to talk about Pondian differences; at first I found it highly confusing, as I thought the UK / US labels somehow pertained to the word being defined (the definiendum) rather than the words used in the definition (the definiens). If one wants more information about the latter, one just has to click on the links. PUC15:47, 16 December 2023 (UTC)Reply

Template:center top and Template:center bottom edit

Deprecate. These templates center arbitrary content, which {{center}} already does without requiring separate top and bottom templates. — excarnateSojourner (talk · contrib) 02:58, 30 May 2023 (UTC)Reply

June 2023 edit

some more form-of templates replaceable by Template:infl of or Template:participle of: part 1, participles edit

We have the following:
  1. {{active participle of}}, {{passive participle of}}
  2. {{present participle of}}, {{past participle of}}, {{future participle of}}, {{perfect participle of}}
  3. {{present active participle of}}, {{past active participle of}}, {{past passive participle of}}, {{future passive participle of}} (NOTE: No {{present passive participle of}}, {{future active participle of}})
  4. {{feminine singular past participle of}}, {{neuter singular past participle of}}, {{masculine plural past participle of}}, {{feminine plural past participle of}} (NOTE: No {{neuter plural past participle of}})

The following table shows the current uses and my suggestions for what to do with the template:

Aliased template Canonical template #Uses Suggested disposition
Template:active participle of Template:active participle of 297 Replace with {{participle of|...|act}}
Template:passive participle of Template:passive participle of 157 Replace with {{participle of|...|pass}}
Template:present participle of Template:present participle of 61028 Keep
Template:past participle of Template:past participle of 38903 Keep
Template:future participle of Template:future participle of 16 Replace with {{participle of|...|fut}}
Template:perfect participle of Template:perfect participle of 12 Replace with {{participle of|...|perf}}
Template:present active participle of Template:present active participle of 16 Replace with {{participle of|...|pres|act}}
Template:past active participle of Template:past active participle of 67 Replace with {{participle of|...|past|act}}
Template:past passive participle of Template:past passive participle of 41 Replace with {{participle of|...|past|pass}}
Template:future passive participle of Template:future passive participle of 15 Replace with {{participle of|...|fut|pass}}
Template:feminine singular past participle of Template:feminine singular past participle of 5672 Replace with {{feminine singular of|...|PAST_PARTICIPLE}}
Template:feminine plural past participle of Template:feminine plural past participle of 5815 Replace with {{feminine plural of|...|PAST_PARTICIPLE}}
Template:masculine plural past participle of Template:masculine plural past participle of 5861 Replace with {{masculine plural of|...|PAST_PARTICIPLE}}
Template:neuter singular past participle of Template:neuter singular past participle of 359 Replace with {{neuter singular of|...|PAST_PARTICIPLE}}

Note that things like {{feminine singular past participle of}} really mean "feminine singular of the past participle of LEMMA". IMO non-lemma forms of participles should refer to the base form of the participle rather than to the underlying verb lemma, which is what I'm proposing here. Benwing2 (talk) 06:24, 18 June 2023 (UTC)Reply

Support. Ultimateria (talk) 22:02, 6 July 2023 (UTC)Reply

some more form-of templates replaceable by Template:infl of: part 2, misc edit

Aliased template Canonical template #Uses Suggested disposition
Template:attributive form of Template:attributive form of 291 {{infl of|...|attr|form}} or just {{infl of|...|attr}}
Template:construed with Template:construed with 77 This is a weird template that should be replaced with other methods. Need to investigate more. Seems used mostly for Hungarian.
Template:definite singular of Template:definite singular of 9094 {{infl of|...|def|s}}
Template:definite plural of Template:definite plural of 4242 {{infl of|...|def|p}}
Template:dual of Template:dual of 76 {{infl of|...|d}}
Template:elative of Template:elative of 219 {{infl of|...|elad}}
Template:equative of Template:equative of 5 {{infl of|...|equd}}
Template:imperative of Template:imperative of 1468 {{infl of|...|imp}}
Template:indefinite plural of Template:indefinite plural of 3912 {{infl of|...|ind|p}}
Template:passive of Template:passive of 3020 {{infl of|...|pass}}
Template:passive past tense of Template:passive past tense of 96 {{infl of|...|pass|past}}
Template:past tense of Template:past tense of 920 {{infl of|...|past|tense}} or just {{infl of|...|past}}
Template:present tense of Template:present tense of 2352 {{infl of|...|pres}}
Template:singulative of Template:singulative of 539 {{infl of|...|sgl}}
Template:superlative attributive of Template:superlative attributive of 110 {{infl of|...|attr|supd}}
Template:superlative predicative of Template:superlative predicative of 111 {{infl of|...|pred|supd}}
Template:supine of Template:supine of 90 {{infl of|...|sup}}

NOTE: A few of the above categorize; this could be handled automatically in Module:form of/cats. Benwing2 (talk) 07:41, 18 June 2023 (UTC)Reply

Support. Ultimateria (talk) 22:02, 6 July 2023 (UTC)Reply
I have deleted or deprecated all of the above except for {{attributive form of}} (because I'm not yet sure whether to replace with {{infl of|...|attr|form}} or {{infl of|...|attr}}) and {{construed with}} (need to look into this more). Benwing2 (talk) 01:55, 12 July 2023 (UTC)Reply
@Benwing2: As far as I can tell as a native Hungarian-speaker "construed with" is strictly equivalent to the label "(with X)" and doesn't mean anything special beyond that. —Al-Muqanna المقنع (talk) 11:02, 14 August 2023 (UTC)Reply
@Al-Muqanna Thanks. For non-Hungarian terms it seems replaceable with {{+preo}} or {{+obj}}. In the Hungarian terms it seems to be a catch-all for words often found along with the lemma in question. Maybe these are better handled by a usage note? Just saying "construed with" in such a general sense seems unhelpful. Benwing2 (talk) 01:04, 15 August 2023 (UTC)Reply
@Benwing2 Perhaps @Adam78 can explain further? I agree that it seems unhelpful as a label, as the way it’s been used doesn’t really convey any information properly. Theknightwho (talk) 01:18, 15 August 2023 (UTC)Reply
@Theknightwho, Benwing2 If you want, it might be converted into a label like "(used) with" to indicate that it strictly co-occurs with the given term in the given sense. Just like "few" has a different meaning when used as "a few". Or does it warrant a separate entry? Let me know if you have a better idea to convey this. Honestly, I think it's good to be able to look up terms used as part of a phrase or collocation in a given sense (I could even imagine a category for them, cf. Hungarian verbs normally used with a prefix), and without a dedicated template this option would be lost. Adam78 (talk) 07:43, 15 August 2023 (UTC)Reply
@Adam78 I think this relates to @Vininn126’s ideas about government (i.e. how words must be used). I can’t remember the specifics, but I know a template exists. Theknightwho (talk) 11:24, 15 August 2023 (UTC)Reply
@Adam78 Can you give some examples of Hungarian terms that strictly co-occur with other terms? In English and other language entries this is normally conveyed by {{only used in}}, where the larger collocation has an entry and contains the majority of the info. As for Category:Hungarian verbs normally used with a prefix, there are two situations: (1) the base verb exists but is archaic or obsolete, (2) the base verb doesn't exist on its own. In Russian we handle the analogous cases as follows: For (1) we list the verb as normal but mark it as archaic or obsolete as appropriate, while for (2) we consider the verb a combining form and precede it with a hyphen (see Category:Russian verbal combining forms for examples). In both cases there's a table of prefixed variants of the verbs; see -речь (-rečʹ) for a typical example. Benwing2 (talk) 19:54, 15 August 2023 (UTC)Reply
@Benwing2: Examples where "only used in" could be applied: utol is obsolete on its own and (el)képed is unattested without the prefix. However, the above cases where "construed with" is applied doesn't mean that the given term is only used in a particular phrase but that it only has the given sense if/when it is used in the given way (with the given suffix, article, compound element, etc., whether in the same word form, same expression, or the same sentence but in a different clause). So it is like a restricting condition for the applicability of the given sense (even though the term may well have any number of other senses where this morphological or syntactic condition doesn't apply). Sometimes this template has a qualifier or clarification, as in kicsit or ledönt, and sometimes it has more than one value, as in készen, megenged, or jöhető.
I even created templates for verb senses used with a particular case-suffixed form of the reflexive pronoun: {{hu-maga1}} (where this argument precedes the verb in neutral word order), {{hu-maga2}} (where this argument follows the verb, since the verb works as a focus), and {{hu-refl}}, where the reflexive pronoun takes the role of the object. In these cases, the overall meaning of the phrase can only occur if the given argument is present. (Using reflexive as a label, as opposed to transitive/intransitive, would have been misleading as the verb itself doesn't have a reflexive sense on its own.)
For the category of Hungarian verbs normally used with a prefix, I think most if not all might have an obscure and/or obsolete sense without the given prefix, or maybe in some very special (unlikely, uncommon) syntactic situation it might be possible to use them without the prefix, so I think your option (1) applies. Adam78 (talk) 20:32, 15 August 2023 (UTC)Reply
@Adam78 I thought about this and if a term is "only used in" a particular phrase in a particular sense, but has a meaning of its own, you should define that phrase as its own lemma entry. Compare put up vs. put up with. What we don't do is define put up with under put up and say "construed with with", which is the analogy of what you're doing. Instead we define put up with as its own lemma, and put it as a derived term from put up. I would recommend doing the same for every case where you're currently using {{construed with}} for this purpose. In general all languages in Wiktionary should follow the same practices as much as possible and it seems that Hungarian is doing things differently for no clearly good reason. I would caution against creating Hungarian-specific templates like {{hu-maga1}} and {{hu-maga2}}; if you continue in this vein it will amount to a mess that others will eventually have to clean up (compare the similar situation with Chinese and Japanese, for example). Benwing2 (talk) 21:26, 16 August 2023 (UTC)Reply
I followed the practice used in {{R:Nagyszotar}}, see e.g. érez ("to feel"), which also defines érzi magát. However, I find the way you suggest equally good, and I understand that it's more in line with the current practice in Wiktionary ("mess" might not be the best word for another editorial decision), so all right, I will convert the entries in the way you suggested. (@Panda10, just to inform you.) Adam78 (talk) 23:07, 16 August 2023 (UTC)Reply
@Adam78 Apologies, "mess" is a loaded term and I understand you have been trying to follow a definite practice, if not the practice of most languages. (I'm biased by the end state I see in the Chinese and Japanese entries, where I've done quite a lot of cleaning up to bring them more in line with normal Wiktionary practice and there is still a lot more to be done.) Benwing2 (talk) 01:01, 17 August 2023 (UTC)Reply

Commentary above French verb conjugation templates edit

French and its ancestor languages are the only languages (of which I am aware) where descriptive commentary is included above verb conjugation boxes ({{fr-conj-auto}}). All verbs, except the regular -er verbs, carry commentary of this type. Here are some examples:

finir
This is a regular verb of the second conjugation, like nourrir, choisir, and most other verbs with infinitives ending in -ir. One salient feature of this conjugation is the repeated appearance of the infix -iss-.
lever
This verb is conjugated like parler, except the -e- /ə/ of the second-to-last syllable becomes -è- /ɛ/ when the next vowel is a silent or schwa -e-, as in the third-person singular present indicative il lève and the third-person singular future indicative il lèvera.
battre
This verb is conjugated like vendre, perdre, etc. (sometimes called the regular -re verbs), except that instead of *batt and *batts, it has the forms bat and bats. This is strictly a spelling change; pronunciation-wise, the verb is conjugated exactly like vendre.


Pointing out "salient features" of a verb paradigm, giving *hypothetical forms, and listing other, similarly-conjugated verbs is the domain of grammar textbooks and/or Appendix:French verbs. These notes clutter the entries, and I don't believe there is anything special about French verbs (as opposed to verbs in all other languages) that means their entries should exceptionally carry such notes above the conjugation template. Let's remove them. This, that and the other (talk) 06:57, 21 June 2023 (UTC)Reply

I can definitely see this argument for removing these notes. On the other hand, one could argue that the notes, although redundant, are really a more condensed way of presenting the non-trivial aspects of these verbs' conjugation; the conjugation table lists every form even though French conjugational endings are highly predictable and fairly repetitive, so even though it includes the same information it's kind of "buried" among other stuff in that context. While these kinds of tables are obviously valuable for someone with zero knowledge of French, the notes could be considered a more efficient presentation of the information for intermediate learners. A third option aside from leaving or removing them could be to shorten them.--Urszag (talk) 08:01, 21 June 2023 (UTC)Reply
I wouldn't be opposed to shortening them; it would certainly be better than leaving them as is with their generous helping of "Interesting Facts". The reason I didn't suggest this to begin with was because the notes would still have to express the differences relative to other verbs ("conjugated like vendre except for the present forms je bats, tu bats, il/elle/on bat"), which is only helpful if you have a certain level of knowledge of French conjugations.
You mention that "French conjugational endings are highly predictable and fairly repetitive" - is the same not true in Italian, Spanish etc? Why do their tables not have notes like this? The inconsistency bothers me as much as anything else. This, that and the other (talk) 23:35, 21 June 2023 (UTC)Reply
The need for a consistent policy across languages is not obvious to me, and consistency could be achieved equally well by adding notes about conjugation to Spanish and Italian entries (which I would not oppose). It looks like in the case of Spanish stem-changing verbs such as morir, there is a brief note in the title of the conjugation box itself before the link to the appendix (e.g. "Conjugation of morir (irregular; o-ue-u alternation) (See Appendix:Spanish verbs)"; that seems like another possible way to draw attention to this information in French (e.g. "Conjugation of lever (regular with e-è alternation) (See Appendix:French verbs)").--Urszag (talk) 06:52, 22 June 2023 (UTC)Reply
Keep. For a fluent speaker of French, these notes are probably more helpful than the conjugation tables themselves. However, I wouldn't be opposed to moving this information to within the conjugation table somehow, so that there's less clutter in the entry when the tables are collapsed. Andrew Sheedy (talk) 18:05, 21 June 2023 (UTC)Reply
Keep. I agree with Andrew Sheedy. Most French resources teach and most French learners are familiar these groups of verbs, so having notes as to what makes each verb different would be helpful. Also, I don't like the Appendix in situations like this, if I'm being quite honest, as most people do not know that it exists (I didn't even know that that page existed), and upon looking at it, it's way too cluttered to be of direct use when looking at a single verb. AG202 (talk) 20:04, 21 June 2023 (UTC)Reply
It's linked right there in the header of the conjugation box. The link could even be adapted to point directly to the relevant section of the page – and if the notes are shortened as Urszag suggested, the direct link could be brought out to sit next to the shortened note. This, that and the other (talk) 23:35, 21 June 2023 (UTC)Reply
Oops, missed that, but my other points still stand. I still think that it's way too cluttered and that just having the note upfront is much better. I'm not opposed to the suggestions of shortening it or moving it into the conjugation table, though. AG202 (talk) 12:47, 22 June 2023 (UTC)Reply
Move into the conjugation table, maybe before the footnotes (unless that's a formatting taboo?). Ultimateria (talk) 18:32, 2 July 2023 (UTC)Reply

all lang-specific phrase templates powered by Template:meta-phrase edit

This includes the following:

All of these are just trivial wrappers around {{head|LANG|phrase}}. They could and should be replaced accordingly. The only one that passes the 1000-uses mark for deprecation is {{en-phrase}}; the others can just be deleted after orphaning. Benwing2 (talk) 03:54, 26 June 2023 (UTC)Reply

Delete. Ultimateria (talk) 18:33, 2 July 2023 (UTC)Reply
Update. The last two ({{he-phrase}} and {{vi-phrase}}) have some lang-specific logic in them so they might need to be kept, although not using {{meta-phrase}}, which is really junky. Benwing2 (talk) 07:36, 3 July 2023 (UTC)Reply
I have Deleted all except {{he-phrase}}, {{vi-phrase}} and {{en-phrase}}, and deprecated {{en-phrase}}. Benwing2 (talk) 07:44, 16 July 2023 (UTC)Reply
Why wouldn't we just make {{en-phrase}} use {{head|en|phrase}} for the five keystrokes per use saved? DCDuring (talk) 17:22, 16 July 2023 (UTC)Reply
@DCDuring Because wrapping {{head}} in another template disables all of its parameters unless the template actively enables each one specifically again, which most of the time they don't - that's one reason why a lot of these little language-specific templates are a problem, and there's no straightfoward solution because it's an intentional design-limitation of the software. It's also an extra template to maintain for no real benefit, as it creates an unexpected inconsistency. It's good to standardise inputs wherever possible, unless something language-specific is genuinely needed. Theknightwho (talk) 17:40, 16 July 2023 (UTC)Reply
In fairness to User:DCDuring, I did implement Module:call awhile ago (unfortunately not yet documented) which attempts to allow for "call forwarding". In particular it allows for forwarding of given specified parameters as well as well forwarding all remaining parameters unchanged. It doesn't yet allow for forwarding list parameters while changing the parameter name but this should be implementable. However, (a) this is pretty obscure, (b) User:Theknightwho's point remains that most of these trivial wrappers are unpowered and are a big maintenance headache in the aggregate. It's the same reason why I don't like people creating random redirects, which is also a maintenance headache (as well as in many cases making the Wikicode even harder to understand). I feel like we could potentially make exceptions with good enough reasons, but it's important to spell out those reasons so we don't end up with a free-for-all. Benwing2 (talk) 18:10, 16 July 2023 (UTC)Reply
Wouldn't it be reasonable for a contributor to expect that there would be template of the form Template:en-[PoS] for each and every PoS that occurred in English? DCDuring (talk) 18:17, 16 July 2023 (UTC)Reply
@Benwing2 This is something that the wikitext parser would excel at, as it allows us to bypass all of these design limitations - we just need to be careful about it, because most of them were put in to stop templates from becoming exponentially complex. Theknightwho (talk) 18:20, 16 July 2023 (UTC)Reply
@DCDuring I'd say no because there are lots and lots of obscure parts of speech, e.g. do we really need a specialized template for the 7 English postpositions? Also, using this logic, where does it stop? You could say it's "reasonable" to have a specialized template for every common or semi-common language times all parts of speech, which gives you thousands and thousands of such templates, each with their own unique behavior, which adds up to a big mess. That's why I generally disfavor such templates. Benwing2 (talk) 18:37, 16 July 2023 (UTC)Reply
One possibility is to alias {{head}} to {{h}}, which saves 3 chars. Not sure what others think of this but it might reduce the demand to create lang-specific POS templates. Benwing2 (talk) 18:44, 16 July 2023 (UTC)Reply
@Theknightwho That is interesting, do you have any concrete suggestions as to how to use it? Benwing2 (talk) 18:45, 16 July 2023 (UTC)Reply
@Benwing2 Currently, the parser uses only two frame objects (one set as the parent of the other), and the parent/child arguments are simply swapped in as necessary right before loading a module. It wouldn't be difficult to modify this so that there's a chain of frames for each layer of the stack, meaning that the grandparent frame's arguments could be accessed in the module with frame:getParent():getParent() and so on.
The risk of this approach is that it makes modules that use it inherently reliant on the parser, since it won't work if loaded conventionally. Theknightwho (talk) 19:02, 16 July 2023 (UTC)Reply
How many PoS headers are used in English entries? DCDuring (talk) 18:52, 16 July 2023 (UTC)Reply
There are more than I thought, but fewer than 25. Excluding those with fewer than, say, 100 members of the associated category would be fine with me. We need to address the really high-volume cases and not let relatively rare phenomena, mostly of interest only to linguists, get in the way. DCDuring (talk) 19:01, 16 July 2023 (UTC)Reply
@DCDuring If we follow Ben's suggestion of using {{h}}, then I really don't see a need for this at all. Theknightwho (talk) 19:03, 16 July 2023 (UTC)Reply
Why not. DCDuring (talk) 19:06, 16 July 2023 (UTC)Reply
@DCDuring There are genuine maintenance issues (as explained above) for no benefit that I can see. Theknightwho (talk) 19:08, 16 July 2023 (UTC)Reply
I have no objection to the {{h}} proposal, as apparently wasn't clear from my previous reply. It should be a modest time-saver for contributors in all languages. DCDuring (talk) 20:35, 16 July 2023 (UTC)Reply
We could potentially also create aliases for the long POS's like interjection (e.g. aliased to int or intj); the advantage of this approach is it's cross-language and standardized. We already allow POS aliases in the |pos= param specified to {{m}}, {{l}} and all other link templates. Benwing2 (talk) 19:12, 16 July 2023 (UTC)Reply
@DCDuring I implemented POS aliases. The full list of aliases is in Module:headword/data starting around line 641; I will expose them in the documentation of {{head}} as soon as I have a chance. I took the list from Module:form of/pos and added phr = phrase. So now you can write {{h|en|phr}} in place of {{head|en|phrase}} and it will work the same. This is even shorter than {{en-phrase}} and should obviate the need to create lots of lang-specific POS headword templates. Benwing2 (talk) 06:56, 20 July 2023 (UTC)Reply
So, keystroke savings for more experienced users and cognitive savings for less experienced users. Great! DCDuring (talk) 13:00, 20 July 2023 (UTC)Reply
Don’t forget easier to maintain, too, plus it also means we can standardise these kinds of abbreviations between languages. Win-win-win. Theknightwho (talk) 13:07, 20 July 2023 (UTC)Reply

July 2023 edit

English form-of verb templates edit

I have added support for language-specific tags, including those that expand to more than one tag set ("conjoined shortcuts"), and implemented a number of them for English. I propose replacing the existing English verb form-of templates with direct calls to {{infl of}} with these new tags. The archaic tags automatically generate an appropriate label (which currently displays "archaic" and links to w:English verbs#Archaic forms, for all three of the archaic forms listed below, but this can be customized), and automatically add to the appropriate category (e.g. Category:English second-person singular past tense forms for forms like openedst). In most cases the resulting Wikitext is actually shorter than the original Wikitext it replaces, and IMO is clearer, because the tag corresponds to the ending of the form rather than the grammatical function of the form, which is in my experience the way English speakers tend to think about these forms. The actual tag names themselves can be changed if people think others are clearer, as they're not yet in use other than in the definitions of the existing templates. Benwing2 (talk) 08:37, 6 July 2023 (UTC)Reply

Canonical template #Uses Suggested disposition
Template:en-archaic second-person singular of 1967 {{infl of|...|st-form}}
Template:en-archaic second-person singular past of 482 {{infl of|...|st-past-form}}
Template:en-archaic third-person singular of 1727 {{infl of|...|th-form}}
Template:en-third-person singular of 36021 {{infl of|...|s-verb-form}}
Template:en-simple past of 1933 {{infl of|...|spast}}
Template:en-past of 37687 {{infl of|...|ed-form}}
Template:en-ing form of 92 {{infl of|...|ing-form}}

Benwing2 (talk) 08:37, 6 July 2023 (UTC)Reply

@ExcarnateSojourner, Theknightwho, Vininn126, Ultimateria who have commented on previous similar deprecation proposals. Benwing2 (talk) 08:38, 6 July 2023 (UTC)Reply
Support using this new way of marking these and also delete these templates. Things shouldn't be spread out if possible. Vininn126 (talk) 10:32, 6 July 2023 (UTC)Reply
Support the changes; delete/deprecate the templates. Ultimateria (talk) 22:00, 6 July 2023 (UTC)Reply
Deprecated or deleted. Benwing2 (talk) 22:58, 1 August 2023 (UTC)Reply
@Benwing2: Template:en-simple past of, Template:en-past of, and Template:en-third-person singular of don't appear to have been deprecated and are still being used in entries. Ioaxxere (talk) 00:05, 7 March 2024 (UTC)Reply
@Ioaxxere Oops, looks like I forgot to do the deprecation step. Will fix. Benwing2 (talk) 00:07, 7 March 2024 (UTC)Reply
"spast" ? This better not be for use by humans. DCDuring (talk) 17:12, 7 March 2024 (UTC)Reply

August 2023 edit

Template:l-nb edit

Template:l-nn edit

These are just wrappers for {{l}} which include the qualifiers (Bokmål) or (Nynorsk) after the term, seemingly for linking to the equivalent term between the two Norwegian L2s. They can easily be replaced by simply using {{l}} and {{q}}, which has two further advantages: it's more intuitive, and (more importantly) it means that most of the auxliary parameters aren't disabled, which is a common problem with wrappers like these. Theknightwho (talk) 22:22, 13 August 2023 (UTC)Reply

  • Delete both as redundant. — excarnateSojourner (talk · contrib) 03:42, 8 September 2023 (UTC)Reply
    Delete. Benwing2 (talk) 20:35, 27 September 2023 (UTC)Reply
    @Theknightwho I am thinking of creating a template {{lq}} or {{l+q}} (or similar) that is just a link template but auto-adds the language name after the link as a qualifier. This is conceptually similar to what {{m+}} does for mentions, but with a different display format (i.e. the language name is added afterwards instead of before, in qualifier format), and would avoid the redundancy and typing hassle of having to write out the name manually. Provided we allow the language name displayed to be customized on a per-language basis, this could also replace {{l/sl-tonal}}, and probably has uses in Chinese entries as well. The corresponding version of {{desc}} could replace {{desc/sl-tonal}}. The new template(s) would be implemented in Lua, similarly to how {{m+}} is implemented, and would support all the parameters that {{l}} and {{desc}} support. What do you think? Benwing2 (talk) 06:54, 2 March 2024 (UTC)Reply

Template:derived terms edit

Template with little usage (127 transclusions). Poorly maintained and the template output is simply a plain list. {{col3}} etc. should be used instead. (NB: the associated module pages should also be deleted accordingly) – Wpi (talk) 09:33, 17 August 2023 (UTC)Reply

Delete per nom and replace with the col* series. I've been confused about the purpose of this template for a while. —Al-Muqanna المقنع (talk) 10:01, 17 August 2023 (UTC)Reply
@Wpi @Al-Muqanna This is already listed for deletion in #remove lesser-used column templates above. Theknightwho (talk) 14:07, 17 August 2023 (UTC)Reply
The idea behind this template is not without merit. When there are less than 8 derived terms, it presents them as a regular list (well, currently it uses a non-standard horizontal "flat list" - but this can easily be fixed). If there are more than 8 derived terms, it presents them as a multi-column list. Perhaps the threshold should be lower, like 5. However, the template should be more like {{col}} and less like {{der-top}}, I'd say.
Here's a bold idea: We should just get rid of the fixed-number-of-columns templates. Instead, the number of columns would be automatically determined according to (a) the number of items in the list - by using a non-columnar list for a small number of items, like this template does - and (b) the defined width of each column, using CSS to adapt to the user's screen - like our translation tables do. This template would then be used for all kinds of term lists, and could be renamed to just that: {{term list}}. This, that and the other (talk) 02:55, 18 August 2023 (UTC)Reply
An outline of my ideas: User:This, that and the other/column templates. This, that and the other (talk) 03:59, 18 August 2023 (UTC)Reply
@This, that and the other It would be good to have something like that, yes. Ideally, we would have one (1) template that handles any and all list sections, which we use irrespective of whether there's 1 term or 500. The formatting should match what is most appropriate, but it should all be handled automatically.
I think we should just call it {{list}}. Keeps it nice and straightforward. Theknightwho (talk) 02:12, 19 August 2023 (UTC)Reply
@This, that and the other, Theknightwho: This was already partially implemented at Template:col-auto. I (and some others) opposed a full rollout last year because of its over-simplistic algorithm to select column number, which only accounts for number of entries; that hasn't changed yet, see the code at Module:columns/auto. I think there was consensus that if it accounts primarily for column width it would be suitable. —Al-Muqanna المقنع (talk) 08:38, 19 August 2023 (UTC)Reply
@Al-Muqanna I was working on that, but iirc it needs to be done with CSS and JS, which means that it would need to be done by an interface administrator. I’ll have a look into it again.
I’d be really keen to get rid of as many unnecessary list templates as possible, because they clog up entries with suboptimal hard-coded formatting that only looks good for users on certain devices. Theknightwho (talk) 14:02, 22 August 2023 (UTC)Reply
I request, actually beg, that either
1. we retain one column template that does NOT make the assumption that all components of the list are of the same language specified as a parameter
OR
2. column templates allow Translingual (taxonomic) terms to appear without triggering the orange link coloring.
In places other than derived- and related-terms lists I use the orange-link gadget to identify entries that need a taxonomic name entry and would like to retain that capability. DCDuring (talk) 14:50, 22 August 2023 (UTC)Reply
@DCDuring You can already vary the language for specific terms. There’s no reason that would change. Theknightwho (talk) 15:54, 22 August 2023 (UTC)Reply
I mean without using {{l}} to override the specified language. DCDuring (talk) 16:02, 22 August 2023 (UTC)Reply
@DCDuring Yep - you just use the language code as a prefix: {{col3|en|term 1|mul:term 2|term 3}}. The only thing to be mindful of is that the terms will be sorted using the main language code, but I think that’s the correct approach when linking to Translingual terms from a specific language entry. Theknightwho (talk) 16:07, 22 August 2023 (UTC)Reply
Oh, wow, only 4 extra keystrokes, compared to 9. What is most annoying is mass change from the column templates that do not specify a language to those that do. In any of those cases that have Translingual items in the list the orange links appear as a result of the change, all solely in an overweening pursuit of uniformity. DCDuring (talk) 16:14, 22 August 2023 (UTC)Reply
@DCDuring It’s fewer keystrokes than manually typing the list with separate templates, which is the only way to not specify the language at the moment. It’s not possible to automatically detect if something is a taxonomic term, either. Could you give me an example of where you think it would be a problem? Theknightwho (talk) 16:20, 22 August 2023 (UTC)Reply
I know it's not possible to detect in general, but it is possible to note that there are some instances of {{taxlink}} or {{vern}} or {{l|mul}} (especially in italics) in a table and NOT convert it from a simple column template to a langcode-using column template. All the tables that have been so converted are a PITA for me. DCDuring (talk) 17:00, 23 August 2023 (UTC)Reply
@DCDuring All of those templates and italics can be used in column templates without problems. There’s no difference in the number of keystrokes, either - you just use | instead of * on a new line. Theknightwho (talk) 17:17, 23 August 2023 (UTC)Reply
What I'm trying to communicate is that:
  1. I have to do work to find and emend the problem items in the lists and restore the value to me of the orange links whenever one of the langcode using templates replaces one of the old ones, now endangered by the uniformitarianism.
  2. It would be easy enough to selectively avoid almost all the tables that would require the corrective work by avoiding those that have the templates or formatting mentioned above.
DCDuring (talk) 21:15, 23 August 2023 (UTC)Reply
@DCDuring
  1. There is nothing stopping you from ensuring each link has the correct langauge code, as I've already shown. That prevents any issues with orange links, so I don't undertand why you keep bringing them up.
  2. I see no reason why language codes for specific terms would be changed by converting them: if a list contains 10 items and 3 of them are Translingual, then those 3 terms would still be Translingual links after the conversion, because they'd use the prefix as I showed above. As such, I don't see how a conversion would present any extra work for you.
  3. It's actually fewer keystrokes to do it in column templates, because you don't need to give each link its own template.
  4. None of the functionality of templates like {{vern}} or {{taxlink}} is hindered by using them in column templates.
What exactly is the problem here? I and Ben Wing have, in the past, implemented improvements like these as a direct response to your concerns, and I've told you as much, so I genuinely don't understand what the issue is at this point. Theknightwho (talk) 01:27, 24 August 2023 (UTC)Reply
You ignore the fact that converting to the new system makes work for me, whenever there is a conversion from old to new, as I have repeatedly expressed. DCDuring (talk) 12:52, 24 August 2023 (UTC)Reply
@DCDuring How is it extra work if everything is the same apart from some minor syntax differences? Theknightwho (talk) 17:14, 24 August 2023 (UTC)Reply
@User:Theknightwho If a list is converted from the langcode-free templates to the new langcode-needing templates and Translingual items are included in the list (usually in parentheses and following a vernacular name in the language of the L2), then the Translingual items will appear orange if one has the orange-link gadget on. The orange-link gadget, otherwise quite useful to find missing Translingual L2s where a blue link is to a Latin or German entry, displays false indications. What I am asking for are two things:
  1. Do not delete the column templates that are langcode-free
  2. Do not convert tables with parenthesis-containing items from the langcode-free column templates to the langcode-needing templates.
This doesn't seem hard. I do not like to ask for special exceptions and treatment for taxonomic names, partially because taxonomic names do not have a langcode different from that used by entries for CJKV characters etc. This is a case where a means of accommodating taxonomic names requires only inaction, not template complication. DCDuring (talk) 13:30, 30 August 2023 (UTC)Reply
@DCDuring then the Translingual items will appear orange if one has the orange-link gadget on
No they won't, because they would be converted with the mul: prefix, which would prevent that issue. I have explained this several times now. That feature was actually implemented after you raised this issue a few months ago. It does not make sense to carve out these lists just for you, because it would leave a bunch of extra templates to maintain for no reason. Theknightwho (talk) 13:43, 30 August 2023 (UTC)Reply
Are mul: prefixes added automagically? How are appropriate cases detected? If not automagically, then I need to do it myself, which is exactly what I seek to avoid. DCDuring (talk) 13:50, 30 August 2023 (UTC)Reply
@DCDuring I am assuming that the conversions would be done by the bot of an experienced user like Ben Wing, who would take this into account. It would be easy to do that automatically, because it would simply check for {{l|mul|...}} or {{vern|...}} and know that that link has to be Translingual. It would be helpful to get a full list of taxonomic templates, so that all of them can be taken into account.
The only times when it wouldn't be possible are with bare links (i.e. [[...]]), but those already need to be corrected anyway. In those cases, showing an orange link is actually an improvement, because a blue link is misleading. Theknightwho (talk) 14:03, 30 August 2023 (UTC)Reply
The ONLY cases that have concerned me are the ones which appear correctly in langcode-free column templates but not in langcode-using templates, the ones with - horror of horrors - bare links. There are many of these because there is no need to specify the langcodes in langcode-free tables. DCDuring (talk) 14:13, 30 August 2023 (UTC)Reply
@DCDuring In those cases, the orange links are actually helpful, because they show there's a problem. There's no point having blue links if they're misleading. Theknightwho (talk) 16:24, 30 August 2023 (UTC)Reply
The problem indicated is relevant only in tech world, not in content world, as are so many things. DCDuring (talk) 16:30, 30 August 2023 (UTC)Reply
@DCDuring Great - but that doesn't mean it's not important. If your problem is the fact it shows an orange link, then the work you're complaining about has to be done anyway. We shouldn't be using bare links outside of definitions, and that's a well-established practice by now. Theknightwho (talk) 16:45, 30 August 2023 (UTC)Reply
My current thinking is as follows:
  • 1 to 6 items: use a regular, bulleted list - no columns, no collapsing
  • 7 to 9 items: use a columnar list with no more than 3 columns, and potentially fewer, depending on screen size (using CSS column-width) and the presence of any long items (determined by Lua)
  • 10 to 12 items: ditto, but no more than 4 columns
  • 13+ items: ditto, but no more than 5 columns
The reason for the multiples of 3 is that the {{col}} series of templates always displays the first 3 rows of items without collapsing, so it makes sense to use that space in an orderly, efficient way. Compare the following:
9 items, no more than 3 columns (as proposed)
9 items, 5 columns (lots of tiny columns)
Thoughts? In my mind, the main open question is whether to artificially limit the possible number of columns to 5, or whether to impose no upper bound (I guess some people might have really really wide screens?) This, that and the other (talk) 02:53, 23 August 2023 (UTC)Reply
@This, that and the other I think it’s good to have the number of columns scale up, but they should be proportionate to the number of items in each column, and there should be no upper limit on the number of columns.
I would say that the maximum number of columns should be equal to the number of items that would leave in each column. So 4 items would be 2 columns of length 2, 9 items would be 3 columns of length 3, and so on, but once the columns have comfortably filled the width then the number of columns should stay fixed. The columns should also grow from the left, instead of filling the width, because 2 or 3 columns can be too spread out on some screens.
Doing it this way means we avoid having silly situations where 5 items are spread across 5 “columns” of length 1, and equally, if someone has a massive screen, then the terms can fill all that up without being ridiculously spread out. Theknightwho (talk) 16:09, 23 August 2023 (UTC)Reply
@Theknightwho, This, that and the other: To be honest I don't see the reason to restrict the number of columns for lower numbers of entries, I would prefer it to be based on column width alone. If you happen to have 10 short items then (for a normal screen size) 5 columns of 2 each is probably fine. Seven also seems too high for a lower bound to me—for example three entries displayed on one line is fine IMO, people often do that manually with col3 at the moment anyway, so I would just put the lower bound at three. —Al-Muqanna المقنع (talk) 16:13, 23 August 2023 (UTC)Reply
@Al-Muqanna I find it looks a bit silly, and I know others have expressed objections in the past. I’m just trying to find a way to get something that is standardised in the wikicode, but which addresses various aesthetic concerns that have been raised before. Theknightwho (talk) 16:27, 23 August 2023 (UTC)Reply
Yeah, it is the kind of thing that can be debated till the cows come home, granted. To me an unformatted list of anything above 4 starts looking like bad use of space, for 3 or 4 entries I don't mind either way. I broadly agree with your suggestion in your second paragraph. —Al-Muqanna المقنع (talk) 16:31, 23 August 2023 (UTC)Reply
How is it that this template is able to remove duplicates in the list, but our other templates can't? Can the code be ported over, or is it too computationally expensive? I apologize if this has been addressed above and I didnt see it. Thanks, Soap 20:59, 24 August 2023 (UTC)Reply
It actually wasn't removing duplicates, heh - but it does now. I can't imagine this functionality would be too hard to add to {{col3}} and friends, but I haven't checked the code to verify this. This, that and the other (talk) 23:57, 24 August 2023 (UTC)Reply
@This, that and the other @Soap Certainly possible, but it would need to make sure all the auxiliary stuff is the same (qualifiers, alt display etc). Theknightwho (talk) 11:44, 25 August 2023 (UTC)Reply

Delete. Ioaxxere (talk) 07:13, 27 December 2023 (UTC)Reply

Roman Empire toponym categories edit

Further to Wiktionary:Grease pit/2023/August#Auto cat and the Roman Empire.

Specifically:

None of these are widely used: Cities in the Roman Empire has 3 entries, all English; most subcats for Places have 1 entry, with the most populated being (not Latin, but) Portuguese with 23. Compare Category:la:Places in Italy with 258 entries at the top level.

Per Module:place/shared-data, "former states such as Persia, East Germany, the Soviet Union and the Roman Empire should have their cities, towns, rivers and such listed under the current entities occupying the same area". Creating categories for former countries creates obvious consistency and maintainability issues, as well as not being particularly helpful for readers (saying that, say, the Daradax is an otherwise unknown river in modern Syria is far more useful than it just being a river in the Roman Empire). —Al-Muqanna المقنع (talk) 11:34, 17 August 2023 (UTC)Reply

I think different categorisations would be useful for different people. If you're reading a Latin text on provincial government in Pannonia, it would be more useful to you to have a category like Category:la:Cities in Pannonia, Roman Empire to get the lay of the land than it would to have the same contents dispersed over Category:la:Cities in Austria, Category:la:Cities in Bosnia and Herzegovina, Category:la:Cities in Croatia, Category:la:Cities in Hungary, Category:la:Cities in Serbia, Category:la:Cities in Slovakia, and Category:la:Cities in Slovenia and mixed with irrelevant-for-your-purposes place names therein. 0DF (talk) 12:25, 18 August 2023 (UTC)Reply
@0DF I think this is an extreme example; most of the Roman provinces were more similar to Syria in corresponding to one or two modern entities. However, even in this case, the problem is that the set of provinces in the Roman Empire (and Roman Republic, etc.) changed over time, and they changed their shape. In order for this categorization to work, Module:place/shared-data needs effectively to have a list of all provinces that existed at any point in the Roman Empire, and presumably another one for the Roman Republic (and similarly for all other historical entities we want to categorize: practically speaking, an impossible task). And then you have the issue of what happens when a province changes its area over time? Does the city have to be categorized in all provinces that it existed in at any point in time? Who is going to do the research to make this happen? Benwing2 (talk) 04:13, 19 August 2023 (UTC)Reply
@Benwing2: According to w:Roman province#Primary sources for lists of provinces, we can derive an exhaustive list of provinces from Tacitus De origine et situ Germanorum, Ptolemaei Geographia, Laterculus Veronensis, Notitia Dignitatum, Laterculus Polemii Silvii, and Hieroclis Synecdemus. 0DF (talk) 20:35, 10 December 2023 (UTC)Reply

Pages under Wiktionary:Requested entries (Japanese)/Phrasebook/ edit

Not quite sure what these pages are. They were transwiki'd from Wikibooks in 2009; the pages' original creator, Swift, is still occasionally active on other wikis. Most of the pages have broken templates. I found one of them in the Thesaurus: namespace where it had incorrectly been stored for the past 9 years.

Can any Japanese editors shed light here? Ping @Eirikr, Atitarev This, that and the other (talk) 12:21, 23 August 2023 (UTC)Reply

If I recall correctly we moved this here during some cleanup of Japanese language learning related Wikibooks. They had accumulated a lot of bits and pieces over the years and many didn't really add to a coherent structure. I suspect that moving these phrases to Wiktionary came after some discussion that this was a more appropriate project for that type of content. If the Wiktionary admins decide that's not the case, I won't oppse deleting this content. --2A00:C88:4000:A003:EC1A:2EE7:DB94:F62F 14:14, 14 December 2023 (UTC)Reply

(Notifying Ungoliant MMDCCLXIV, Metaknowledge, Ultimateria, Koavf, PUC, Jberkel, Nicodene): Are these really needed? The letters are a part of the alphabet, even if they're primarily used in foreign loanwords. It's not that rare or notable of an occurrence if they have 1000+ entries (or 4000+ in the first one). I might suggest added Category:Spanish terms spelled with Ü as well, but that one has less than 1000 entries. AG202 (talk) 13:12, 27 August 2023 (UTC)Reply

(Notifying Ungoliant MMDCCLXIV, Daniel Carrero, Jberkel, Svjatysberega, Cpt.Guapo, Munmula, Koavf, Sarilho1, Benwing2): : (Apologies for any double pings) I'll add Category:Portuguese terms spelled with K & Category:Portuguese terms spelled with À as well. These categories "are intended for characters not part of the standard repertoire of a language (e.g. Cyrillic characters in English or Latin characters in Russian)". These categories don't fall under that. AG202 (talk) 13:15, 27 August 2023 (UTC)Reply
@AG202 This should be folded into Wiktionary:Beer parlour/2023/August#standardChars_field_in_Module:languages/data/2_et_al. which addresses this exact issue. Let's not vote on this until that's been sorted. I should also note that these don't exclude non-lemmas, which obviously bulks up the figures by a lot. Theknightwho (talk) 15:58, 27 August 2023 (UTC)Reply

September 2023 edit

Template:R:jpx:Tekin1993 edit

A fringe source promoting Altaic and only used to source fringe cross-family comparisons. We're not a catalog of every single crackpot's favorite theory. — SURJECTION / T / C / L / 15:17, 2 September 2023 (UTC)Reply

Probably worth examining all of the sources for the supposed "Altaic" family. It's about time we purge any promotion of it from here. — SURJECTION / T / C / L / 15:18, 2 September 2023 (UTC)Reply

Template:ur-x edit

I don't even know why we have this in the first place. It's not like Urdu has a need for one. — Fenakhay (حيطي · مساهماتي) 07:14, 7 September 2023 (UTC)Reply

Delete. Theknightwho (talk) 11:43, 7 September 2023 (UTC)Reply
Delete. Benwing2 (talk) 11:49, 27 September 2023 (UTC)Reply
@Hammad You created this. Before I delete this entirely, can you respond why you felt the need to create it? It's used on ~ 170 pages so it would be easy to remove, and looking at the code the only thing I see that isn't immediately replaceable with {{ux}}/{{uxi}} is that it tries to autoselect whether to display inline or not depending on the length of the example. IMO this is done badly in this code and needs more thought before we implement this, but it should definitely be done in the generic code if done at all. Benwing2 (talk) 05:58, 28 September 2023 (UTC)Reply

Template:hi-usex edit

Same as above. — Fenakhay (حيطي · مساهماتي) 07:25, 7 September 2023 (UTC)Reply

Delete. Theknightwho (talk) 11:44, 7 September 2023 (UTC)Reply
Delete. Benwing2 (talk) 11:50, 27 September 2023 (UTC)Reply
@AryamanA Before I delete this entirely, can you respond and specify why you created this? It's now used on about 2,400 pages but looking at the code I don't see why the generic {{ux}} can't be used. It looks like you modeled this after Wyang's Nepalese version but Wyang in general was not good at integrating his code with existing code, so you shouldn't use his code as a model. Also pinging User:Kutchkutch and User:Pulimaiyi, who may know why this was created. Benwing2 (talk) 05:54, 28 September 2023 (UTC)Reply
Well, it has the same code as {{ur-x}} that attempts to autodetermine whether to display inline or not, and the same caveats apply about this. Benwing2 (talk) 05:59, 28 September 2023 (UTC)Reply
Delete. @Benwing2: It was created only for the automatic inline determination. —AryamanA (मुझसे बात करेंयोगदान) 22:00, 1 October 2023 (UTC)Reply
Delete for the reasons mentioned by @Benwing2: Since AryamanA is inclined to delete this template, perhaps this RfD can be closed now. In 2017, I asked AryamanA the reason for this template at User_talk:Kutchkutch#Babel:
Kutchkutch: I was also wondering why {{hi-usex}} is is used for Hindi instead of the default {{ux}} or {{uxi}}. Is {{hi-usex}} customised in some way or is it simply a shortcut for {{ux|hi|यह एक उदाहरण है।}}?
AryamanA: Right now, it automatically makes it inline ({{uxi}}) for short examples, and it highlights the word to make it more visible. Otherwise, it is pretty much the same as {{ux}}/{{uxi}}.
Kutchkutch (talk) 00:48, 20 October 2023 (UTC)Reply

Template:rfcoll and Category:Requests for collocations by language edit

There are so many request categories that it becomes difficult for potential request-fulfillers to identify all the requests in their language. Those that are barely used should be removed. Currently there is only one entry tagged with {{rfcoll}}, sinine, which has been spammed with every request tag imaginable. It seems unlikely to me that this term even has collocations. Having said that, the existence of a range of (now-empty) language categories under Category:Requests for collocations by language suggests that this template has seen some use previously.

I would further argue that this type of request is too specific to warrant its own request template and category tree structure. At minimum, {{rfcoll}} could be changed so it categorises into the Category:Requests for example sentences by language hierarchy (perhaps that hierarchy would need renaming), but I'm not convinced the template is needed at all. This, that and the other (talk) 01:52, 26 September 2023 (UTC)Reply

@This, that and the other Agreed and I'm partly at fault because the request category-handling code presumes a specific template call for each request category. You might want to do an audit of request categories and request templates and see which ones should be deleted. Benwing2 (talk) 12:07, 27 September 2023 (UTC)Reply

Category:Rest and all lang-specific versions; Category:Sitting and all lang-specific versions edit

@Victar I don't see the point of Category:Rest. It groups Category:Sitting and Category:Sleep, which don't form a natural category. I also think we don't need a Category:Sitting. This category exists in only one language (Proto-West-Germanic), in which it has only two morphologically-related terms, a verb for "sit" and a verb for "sit on, occupy, etc.". It is better to use affix or root categories to group morphologically-related terms, and it is enough to create Category:Body positions (a set category) to enumerate verbs related to body positions, like sit, stand, lie, crouch, loom, etc. Benwing2 (talk) 07:16, 28 September 2023 (UTC)Reply

Wiktionary lacks a lot basic categories, and as I've been better categorizing West Germanic terms, I've been also porting some categories from Wikipedia for my needs, like Category:Sitting. Category:Body positions or Category:Human positions could also work, but things sit other than humans, which is why I went with Category:Sitting. As for Category:Rest, what would be better recommend for terms of rest that aren't sleep? -- Sokkjō 21:12, 28 September 2023 (UTC)Reply
"Sitting" is not necessarily rest, and it seems too specific to be a category of its own. We don't need categories for every single semantic concept; that would be far too ramified. IMO we need to be parsimonious (which Chrome underlines in red, for no obvious reason) with our categories so we don't end up overwhelming the end user or creating categories that are largely unfilled. I really think you should think about creating larger-scale categories and only create the finer-scale ones when there's a genuine need. (BTW non-humans have bodies too, so Category:Body positions should be fine for animals, and "sitting" in reference to inanimate objects is not the same concept.) Benwing2 (talk) 22:39, 28 September 2023 (UTC)Reply
I hate to vote to delete something that another contributor to this project clearly thought/thinks was a good idea, but I have to agree with Benwing that nothing about grouping "sleep" and "sitting" together as "rest" seems logical or necessary to me; I would delete the "Rest" category, at least as it is presently constituted. "Sitting" is a more plausible category, I would like to see how many terms it could contain: sit (and trivial variations like sit up and sit down), terms like Indian style and criss-cross applesauce, and what else? If it's only a handful of terms, I'm not sure it's useful, but if it's a lot of terms, then sure... - -sche (discuss) 00:33, 29 September 2023 (UTC)Reply
@-sche: The idea behind Category:Rest was for terms like rest, relaxation, chill out, etc. Perhaps there's a better name for this category? -- Sokkjō 21:05, 29 September 2023 (UTC)Reply
Hmm, if we can flesh it out (categorize more entries into it, or list entries that would go in it), I could get a better sense of how useful a Category:Rest would be; maybe it's useful after all. I see Category:Sitting has been populated with a variety of entries. When I add a new category, I try to populate it with entries right away to demonstrate that it could contain a significant number of entries, to head off RFDs (or at least let them proceed based on evaluation of what a decently fleshed out category looks like). - -sche (discuss) 14:05, 30 September 2023 (UTC)Reply
Well, for me, as I don't work in English, filling English categories isn't something I'm inclined to do, but Category:gmw-pro:Rest I can fill up no problem. -- Sokkjō 00:47, 1 October 2023 (UTC)Reply
Took the time to populate Category:en:Rest FWTW. -- Sokkjō 04:07, 1 October 2023 (UTC)Reply

Category:Work edit

User:Victar has been hard at work creating IMO useless categories. I don't see the point of Category:Work, which contains Category:Employment under it. "work" has two definitions in English: "employment" and "effort". If Category:Work is intended to encompass both, it should be split into already-existing Category:Employment and Category:Effort (but I don't see why the latter category is useful). Otherwise it's redundant to Category:Employment. Either way it should be removed. Benwing2 (talk) 07:22, 28 September 2023 (UTC)Reply

I also have a request for you: please let's have a moratorium on further Victar-created categories until we've made sure the dozens you've recently created are needed. Many of them appear to be unneeded or ill-thought-out, and I need to have time to review them individually while you're not adding even more. Benwing2 (talk) 07:27, 28 September 2023 (UTC)Reply
Again, Category:Work is a port of Wikipedia Category:Work. There is work that isn't employment, which is why Category:Employment is a separate category on Wikipedia. I can tell you, none of the categories I've created are "ill-thought-out", and I've put a lot of consideration into them. But please feel free to audit me on any of my addtions. -- Sokkjō 21:20, 28 September 2023 (UTC)Reply
@Sokkjo We don't necessarily have to follow Wikipedia. I took a look at Category:Work and it has things like make-work job in it that would be better put under Category:Employment IMO (note that busy work, essentially a synonym of make-work job, is under Category:Employment not Category:Work; in general there's no rhyme or reason for the separate categorization as far as I can see). Benwing2 (talk) 22:34, 28 September 2023 (UTC)Reply
Absolutely, we have no imperative to follow Wikipedia, but seeing as their categories are far more extensive and already vetted, it's not a bad starting point. Category:Work contains both Category:Employment and Category:Slavery, which are both clearly distinct, yet still fall under "work". I think there's plenty of "rhyme or reason". -- Sokkjō 08:20, 29 September 2023 (UTC)Reply
@Sokkjo From looking at Wikipedia's categories, they are a sorry mess, much like a lot of the Wikipedia modules that people wrongly think are a good idea to "port over". They are too ramified and highly duplicative. I would not use Wikipedia as a starting point. You have a point that slavery is a type of forced labor, which is a type of labor, and employment is also a type of labor; so maybe we should rename Work -> Labor, which makes it clearer. (Wikipedia again, in their messiness, distinguishes Work from Labor, but I disagree.) I also see you created 'Slaves' as a topic cat separate from Slavery; this makes no sense at all, so i'm RFD'ing Category:Slaves. Once again I ask you to stop creating new categories until we have a chance to work through the dozens you've already created. Benwing2 (talk) 08:49, 29 September 2023 (UTC)Reply
Category:Labor could work too, but unlike Category:Work, labor/labour can be spelled multiple ways and could also refer to the act of childbirth. -- Sokkjō 20:41, 29 September 2023 (UTC)Reply
@Sokkjo This is true but "work" also has multiple interpretations, and we say "slave labor", "forced labor" and the like and not normally "slave work" or "forced work". The spelling issue is not a biggie; we certainly have other category names with one spelling or the other (cf. CAT:Organizations, CAT:Visualization, CAT:Vocalizations). Benwing2 (talk) 00:59, 30 September 2023 (UTC)Reply
Maybe some other people can chime in. -- Sokkjō 03:42, 30 September 2023 (UTC)Reply
I agree that we're going to have a hard time making users keep "Work" and "Employment" distinct (and if we rename "Work" to "Labor", then we also have a hard time distinguishing it from Pregnancy / labor). I also appreciate the point that not all work is employment. What if we solve this in the other direction: keep CAT:Work and delete CAT:Employment, which currently contains no entries in any language and no subcategories besides CAT:Occupations? CAT:Employment seems like it does nothing but make users put in an extra click when navigating between CAT:Occupations and CAT:Business (or whatever higher-level category we might decide to put Occupations in). If we make Occupations a subcategory of Work instead, then any work-that's-not-employment could go in Work, as can any employment-that's-not-an-occupation (while still putting anything that does belong in a more specific category like Occupations, or e.g. CAT:Hobbies, in those categories). - -sche (discuss) 14:45, 30 September 2023 (UTC)Reply
I'd support this change. AG202 (talk) 01:00, 1 October 2023 (UTC)Reply

Category:Slaves edit

Created by @Sokkjo AKA @Victar (BTW can you pick one account and use it? I don't understand why you are now using two.) Duplicates Category:Slavery. If Category:Slaves were a set category, that would be a different story, but its intent appears to be a topic category, and it contains only Proto-West-Germanic entries that belong under Category:Slavery. Benwing2 (talk) 08:51, 29 September 2023 (UTC)Reply

(This is starting to sound like a personal attack.) Category:Slavery is the societal concept and includes terms like plantation, whilst Category:Slaves refers specifically to enslaved peoples. Having Category:Slaves places them under Category:People, and also saves me not to have to write {{topics|Slavery|People}}. -- Sokkjō 20:33, 29 September 2023 (UTC)Reply
@Sokkjo Not a personal attack; my apologies if it appears that way. Is Category:Slaves meant to be a topic or set category? That isn't clear to me. If a topic category, it's definitely redundant to Category:Slavery; otherwise you need to clarify what goes in it. Note also that a clear decision was made a few months ago that we don't create intersection categories; at that point I deleted various Category:Male OCCUPATIONS and Category:Female OCCUPATIONS categories and recategorized them using Category:OCCUPATIONS + Category:Male people or Category:Female people. Benwing2 (talk) 22:00, 29 September 2023 (UTC)Reply
Yes, Category:Slaves is a set list, unlike Category:Slavery -- like Category:Art is to Category:Artists -- for terms like field slave, house slave, wage slave, etc. -- Sokkjō 03:41, 30 September 2023 (UTC)Reply
@Sokkjo OK. I see you only just now made it a set category, and you still haven't updated the description, which still indicates that it's a topic category. In general you need to be less sloppy about this, esp. as it's fairly likely the set and topic categories will be split into different namespaces (per a recent Beer Parlour discussion). Benwing2 (talk) 05:11, 30 September 2023 (UTC)Reply

Keep as a set category. Ioaxxere (talk) 07:13, 27 December 2023 (UTC)Reply

October 2023 edit

Appendix:Glossary of contract bridge edit

Discussion moved from WT:RFC.

English. Anyone know anything about bridge? This page uses a range of nonexistent templates to try to show various aspects of the game, including suits (the templates probably exist on Wikipedia - for instance w:Template:BridgeSuit and w:Template:Ds). Also the initial case of each defined term (or in some cases, each individual word in a multi-word term) needs to be checked; all our other glossaries use lowercase initial letters. This, that and the other (talk) 12:32, 23 August 2023 (UTC)Reply

This seems to just be a poorly-maintained/less complete duplicate of Glossary of contract bridge terms? —Al-Muqanna المقنع (talk) 13:16, 23 August 2023 (UTC)Reply
It is. Back in 2007, Connel MacKenzie's bot transwikied it from Wikipedia here, on the presumption that a glossary of terms was more appropriate for a dictionary than an encyclopedia. Since then, it's barely been touched here. —Mahāgaja · talk 14:26, 23 August 2023 (UTC)Reply
Arguably they were right, but in practice Wiktionary appendices are basically invisible to readers and potential editors whereas Wikipedia articles of general interest within a particular niche like this one tend to be well-maintained. I think there's a good case to RFD this one. —Al-Muqanna المقنع (talk) 15:00, 23 August 2023 (UTC)Reply
On my to-do list/bucket list is to try and bring some order to the chaos that is the Appendix namespace, perhaps through a "breadcrumb trail" like what {{auto cat}} generates at the top of category pages, and in the long term, possibly even proposing to rearrange the appendix by language: Appendix:French/Verbs, Appendix:English/Star Wars vocabulary, etc. Then we can feel proud of the appendix and add a link to it (as well as the thesaurus, rhymes section, ...) from the sidebar, making it much more visible! This, that and the other (talk) 23:40, 24 August 2023 (UTC)Reply
I used to play bridge so I am familiar with many of these terms but I'd argue that information presented in this form (glossaries of specific subjects) is more encyclopedic than dictionary-like, so I have no problem with deleting it. Benwing2 (talk) 05:56, 21 September 2023 (UTC)Reply
Delete. Ioaxxere (talk) 07:13, 27 December 2023 (UTC)Reply
Move to mainspace, with checking to see if the terms are used. CitationsFreak (talk) 18:16, 15 January 2024 (UTC)Reply
@CitationsFreak I used to play a lot of bridge, and there are quite a lot of technical bridge terms that could/should be defined if they're not already, e.g. void, singleton, doubleton, ruff, slough (maybe spelled sluff?), squeeze, double, redouble, trump, notrump, dummy, declarer, Blackwood, Stayman, negative double (found a red link!), etc. But some of these terms I've absolutely never heard of, and for some of them the definition doesn't even make sense e.g. rainbow "A movement used in individual events" (?). I see for example that Stayman (a type of bridge bid/convention, which includes many variants such as puppet Stayman; see the Wikipedia article on Stayman convention) is not defined, but the less common derived convention Namyats (which is "Stayman" spelled backwards) does have a definition. Something for a rainy day I suppose. Benwing2 (talk) 22:40, 15 January 2024 (UTC)Reply

Category:Arabic definite proper nouns edit

Arabic. All proper nouns are definite. --2A02:9B0:4057:C5AE:796D:4966:EE3A:3763 04:27, 10 October 2023 (UTC)Reply

They all behave as though they are definite, sure, but morphologically, some are indefinite: Template:ar-decl-noun#Definite_proper_nouns. However, I'm not sure that this category serves any useful purpose. It's instructive to observe that Category:Arabic indefinite proper nouns doesn't exist. This, that and the other (talk) 09:35, 19 January 2024 (UTC)Reply

Category:Ports and harbours edit

Another User:Sokkjo/User:Victar-created category. Contains only four terms from Proto-West-Germanic, two verbs meaning "to harbor" and the words "port" and "harbor". This is therefore not a set category, not a natural grouping, and too small. These terms can go into Category:Nautical. Benwing2 (talk) 23:42, 12 October 2023 (UTC)Reply

Again with the hostility. Port over of Category:Ports and harbours. Not a hard category to fill. -- Sokkjō 23:53, 12 October 2023 (UTC)Reply
@Sokkjo You are reading hostility where there is none. I simply stated my reasons why I think this category should be deleted. BTW I don't think "could be filled" is a valid reason for keeping a category, nor is "exists in Wikipedia". Benwing2 (talk) 23:55, 12 October 2023 (UTC)Reply
Is this about Category:Ports and harbours or Category:gmw-pro:Ports and harbours? DCDuring (talk) 00:23, 13 October 2023 (UTC)Reply
@DCDuring When I posted this, there was no Category:en:Ports and harbours. If this is made into a set category, I think it's OK but that would entail removing things like "to harbor", coaling, harbormaster and other terms that are not instances of ports or harbors. Benwing2 (talk) 00:49, 13 October 2023 (UTC)Reply
This should be a topics category to various set categories, see Category:Ports and harbours. -- Sokkjō 01:03, 13 October 2023 (UTC)Reply
@Sokkjo I don't understand what you mean. Why do we need a separate "related-to" category for this? Why can't Category:Nautical suffice, and Category:Ports and harbours be used for types of ports/harbors? And why do you keep referring to Wikipedia? Wiktionary and Wikipedia are very different entities. Benwing2 (talk) 01:49, 13 October 2023 (UTC)Reply
No, CAT:Nautical does not suffice. Have you seen Category:en:Ports and harbours? It took me ten minutes to fill it with terms and there are many more to add that do not belong in a set category, such as CAT:Ports and harbours by country, as you yourself pointed out.
You keep asserting that I shouldn't refer to Wikipedia, but as I said before, the categories on Wikipedia are far more built out then those on this project, and to say they have nothing worth taking as guidance is absolute hubris. So yes, I will be continuing to make comparisons and citing their project. -- Sokkjō 06:07, 13 October 2023 (UTC)Reply
@Sokkjo Why does CAT:Nautical not suffice? Once you remove the set entries from consideration, the non-set entries are small and can go into CAT:Nautical or nowhere. You seem not to understand that synonyms do not really belong in topic categories; they go in the Thesaurus. If we are to have a related-to "Ports and harbors" category, we need a DIFFERENT set category for ports and harbors. They should not be mixed. BTW under what circumstances will you be willing to admit that one of your created categories doesn't belong? It seems like never. Benwing2 (talk) 06:14, 13 October 2023 (UTC)Reply

Keep as a set category (types of ports). Ioaxxere (talk) 07:13, 27 December 2023 (UTC)Reply

Category:Ambiguity edit

Created by User:Solomonfromfinland. Ill-conceived and vague and contains essentially terms meaning "ambiguity", "polysemy" and "double-entendre". Technical terms should go into Category:Semantics and the rest removed. Benwing2 (talk) 23:59, 12 October 2023 (UTC)Reply

This seems like content for normal entries, eg, ambiguity and/or ambiguous. DCDuring (talk) 00:36, 13 October 2023 (UTC)Reply
@DCDuring Can you clarify what you mean? Do you mean the terms should be moved to "related terms" under ambiguity? Benwing2 (talk) 00:50, 13 October 2023 (UTC)Reply
Yes. Some would be derived and some would be merely related. In addition to the semantic relations headers, "See also" is useful for items that have less easily classified semantic connection. DCDuring (talk) 00:57, 13 October 2023 (UTC)Reply

Delete. Ioaxxere (talk) 07:13, 27 December 2023 (UTC)Reply

Delete Jberkel 21:38, 26 February 2024 (UTC)Reply

Category:Bricks edit

Created by User:Koavf, who then added a bunch of tangentially-related terms to this category, whose only connection is containing the word "brick" in them:

etc.

IMO this is a poster child for what categories should *NOT* be. Benwing2 (talk) 00:26, 13 October 2023 (UTC)Reply

Delete: Category:en:Bricks, those should all be in derived terms at brick, not to mention that one would expect examples of bricks to be in a category with a plural name. DCDuring (talk) 00:30, 13 October 2023 (UTC)Reply
Even sandstock is a hyponym of brick. DCDuring (talk) 00:45, 13 October 2023 (UTC)Reply

Weak delete. Seems reasonable. —Justin (koavf)TCM 00:36, 13 October 2023 (UTC)Reply

Category:Cheating edit

Created by User:Sokkjo/User:Victar. We already have Category:Deception. Contains only Proto-West-Germanic terms: four verbs meaning "to cheat" or "to deceive", and two tangentially related terms meaning "unloyal" and "adultery". There is no reasonable way to make this into a set category, and the items here should either be listed as synonyms of a basic verb "to deceive", moved to Category:Deception or removed. Benwing2 (talk) 00:57, 13 October 2023 (UTC)Reply

  • Delete Make sure context is appropriately placed in entries. Some of this would belong in a well-designed Thesaurus, if we had one. All of this seems to be the result of our having this ponderous, readily abusable topic category structure without explicit, comprehensive, understandable criteria for their formation and population. Seems to fall under it seemed like a good idea at the time and grow like Topsy. DCDuring (talk) 01:03, 13 October 2023 (UTC)Reply
    @DCDuring I agree. I have done some work recently to clarify the types of topic categories ("related-to", "set", "type" or "name") and include verbiage stating what belongs in the categories, but I completely agree we need some clear criteria for what topics are appropriate. Benwing2 (talk) 01:08, 13 October 2023 (UTC)Reply
    The combination of the {{topics}} and {{autocat}} templates seems highly prone to abuse. At least one or the other needs oversight. I haven't paid much attention because I have no use for such categories. I wonder who does. This will be a matter for BP. DCDuring (talk) 01:15, 13 October 2023 (UTC)Reply

Delete. Ioaxxere (talk) 07:13, 27 December 2023 (UTC)Reply

Category:Conflict edit

Created by User:Sokkjo/User:Victar. This is populated only with a single subcategory Category:War, except for Proto-West-Germanic, where it has a smattering of terms meaning "to quarrel", "quarrel" or "conflict", and a couple other vaguely related terms. These belong as synonyms of a basic term "to quarrel"; terms related to war can be moved to Category:War. This should be deleted and Category:War moved up one level. Benwing2 (talk) 01:05, 13 October 2023 (UTC)Reply

Conflict ≠ war and I needed a category for such words. See Category:Conflict (process). -- Sokkjō 01:38, 13 October 2023 (UTC)Reply
@Sokkjo Why did you need a category for such words? I really think you misunderstand what the topic category system is for. Topics should not be used for vague collections of synonyms; that's what the Thesaurus and Synonyms sections and inline synonyms are for. Benwing2 (talk) 01:47, 13 October 2023 (UTC)Reply
I think this line you're drawing of what's too "vague" is arbitrary and gatekeeping. Higher categories by their very concept are more generalized. Again, war and conflicts are not synonyms. The terms brawl, spat, feud, dispute, rivalry, etc. simply do not belong under CAT:War. -- Sokkjō 06:20, 13 October 2023 (UTC)Reply
Yes, and these are Thesaurus-type items, not topic items. Benwing2 (talk) 06:22, 13 October 2023 (UTC)Reply
Also you keep eliding or confusing the difference between set-type and related-to categories. Benwing2 (talk) 06:23, 13 October 2023 (UTC)Reply

Delete. Ioaxxere (talk) 07:13, 27 December 2023 (UTC)Reply

Template:cite-thesis edit

This is a complete duplication of {{cite-book}}, which can be used in its place. — Sgconlaw (talk) 05:00, 17 October 2023 (UTC)Reply

Obvious delete. -- Sokkjō 02:15, 19 October 2023 (UTC)Reply
Strong Keep. It's not an exact duplication, including parameters like "type" that aren't included in {{cite-book}} ("genre" is not the same). Additionally, theses aren't books nor journals, and I've felt very weird using those templates for works that don't fall under them. AG202 (talk) 04:39, 29 January 2024 (UTC)Reply

Category:Adjective plural forms by language edit

And all subcategories. These categories are inconsistently (manually) added and serve no immediate purpose. There was a BP discussion (the first one on this page) that led nowhere.

Also note that I nominated Category:Noun plural forms by language 6 months ago and haven't gotten any votes. Ultimateria (talk) 18:58, 20 October 2023 (UTC)Reply

I added {{rfd}} to all the "LANG adjective plural forms" cats (and "LANG noun plural forms"). Let's wait a few months to see if anyone complains, and if not, delete. This, that and the other (talk) 01:38, 25 October 2023 (UTC)Reply
  Oppose If it bothers you, don't look at it. Simple. — Fenakhay (حيطي · مساهماتي) 10:03, 26 October 2023 (UTC)Reply
I've seen several complaints about "category bloat" in recent years. The first step to addressing this problem is to eliminate unwanted and unmaintained categories. Why do you think we should keep these categories? Ultimateria (talk) 23:45, 30 October 2023 (UTC)Reply
  Support strongly. Benwing2 (talk) 06:29, 1 November 2023 (UTC)Reply

Delete. Ioaxxere (talk) 07:13, 27 December 2023 (UTC)Reply

Template:R:non:Koebler, and all other similar templates edit

Posting it here with a {{rfd}} tag since it already had the {{d}} tag added. However I oppose deletion. There was some contention about whether umlauts should be allowed in template names, which would apply to all templates ending in Köbler. I would personally prefer keeping the umlaut variant as the main page and using redirects from Koebler for those who cannot input ö. In either case, the form with oe should be kept. Helrasincke (talk) 10:01, 21 October 2023 (UTC)Reply

November 2023 edit

Template:poj of edit

This template goes against the current practice for how POJ entries are treated, which is either to have a full Min Nan entry or to have {{zh-see}}. — justin(r)leung (t...) | c=› } 00:01, 5 November 2023 (UTC)Reply

The usage of Template:poj form of only appears in three POJ entries. But that template displays Pinyin for Mandarin, which is not ideal for a POJ entry. That's why I created Template:poj of. I agree to merge the two templates if the some technical problems are solved. Wikijb (talk) 00:40, 5 November 2023 (UTC)Reply
Thanks for bringing up this other template. IMO, without discussion, that template should not have been created either. Ideally, POJ entries should be dealt with in the same way. With these different templates, we have three to four ways for dealing with POJ entries, which is messy. — justin(r)leung (t...) | c=› } 00:49, 5 November 2023 (UTC)Reply

Deleted, though it's moot since it's no longer used anywhere following the conversion of all the entries from Min Nan to Hokkien. Theknightwho (talk) 23:57, 10 March 2024 (UTC)Reply

Thesaurus:wild edit

The semantic connections of the listed words are all over the shop. Thesaurus:awesome is sufficient. This, that and the other (talk) 11:16, 7 November 2023 (UTC)Reply

Category:Requests for date by source edit

Now that we have Category:Requests for date by language, this is no longer needed. Almost all the subcategories only have a single entry. This, that and the other (talk) 06:46, 11 November 2023 (UTC)Reply

Oh, I'm still using this (via rfdatek or rfquotek templates?). Nobody told me I had to change. Equinox 20:52, 5 December 2023 (UTC)Reply
Perhaps I should add some background on this deletion request for those not familiar with the history. Back in the day, Wiktionary imported a vast number of entries from {{R:Webster 1913}}. This dictionary includes quotations attributed to the author only. No further bibliographic details are given. A template {{rfdatek}} was created to flag these insufficiently attributed quotes. It categorised each quote into a subcategory based on author (e.g. Cat:Requests for date/Chaucer, Cat:Requests for date/Shakespeare and so on). Over a number of years, many editors (with the lion's share of the work done by WF, I think) chipped away at this backlog to the point where none of the original Webster {{rfdatek}}s still exists. Any uses of {{rfdatek}} are later additions by other editors. In this situation, unlike the original Webster imports where large numbers of quotes were drawn from a small selection of authors, there is no trend in the application of {{rfdatek}}, meaning that the author-by-author subcategories now only have one or two entries each - making them rather pointless. The language-by-language categorisation at Cat:Requests for date by language is now more than sufficient, and also captures those entries which are tagged with {{rfdate}} rather than {{rfdatek}}.
(Webster 1913 also sometimes indicates that a certain sense of a word was used by such-and-such author without giving a quote. These are tagged with {{rfquotek}}. WF has also been working on this backlog, which has likewise been broken up into author subcategories under Cat:Requests for quotations by source. But I'm not proposing to delete that category tree just yet.) This, that and the other (talk) 10:22, 10 January 2024 (UTC)Reply

Wiktionary:Requested entries (ǃXóõ) edit

I believe this page exists only because of the exotic appeal of the language. There has not been a major study of the language since Traill's 1999 dictionary, which is also the only collected dictionary in the language and therefore the only place where words to add would be found. Essentially, this means that anyone who adds a word to Wiktionary:Requested entries (ǃXóõ) must be getting it from the dictionary, and already has the definition in front of them. I dont think this is a good use of our time. Best regards, Soap 14:30, 16 November 2023 (UTC)Reply

  • Not so far as I know ... I've posted an update below, but I'm not aware of this language ever having literature .... that is, nothing is written in !Xoo, only about it. The most there may be is a short story inside of one of these other documents, and that would of course be translated in that document. Soap 14:47, 21 February 2024 (UTC)Reply
Comment: In an unrelated discussion outside Wiktionary, someone showed me more resources, but these are not dictionaries, most are not accessible online, and not all of them are even about ǃXóõ (they merely mention it). So my reasoning is still the same, as I would say the Traill document is still the only major study of the language, but I want to clarify there is more than just the single resource. Soap 13:02, 21 February 2024 (UTC)Reply
  Support. MedK1 (talk) 21:37, 29 February 2024 (UTC)Reply

Appendix:Mordvinic word lists (edited) edit

@Anazarenko, Surjection We already have a word list, it contains cited words; This "version" is just full of neologisms instead of the more commonly accepted borrowings and Latin-script Mordvinic, which is neither supported nor used by the overwhelming majority of speakers. Thadh (talk) 12:14, 19 November 2023 (UTC)Reply

Yeah, Heikki Paasonen was wrong. Transliteration is a crime. https://www.mv.helsinki.fi/home/rueter/Paasonen/ORIGINALS/mw_styles_a_.shtml Anazarenko (talk) 12:22, 19 November 2023 (UTC)Reply
BTW, would you be kind enough to provide specific examples of these "neologisms" or will we talk in general terms? Anazarenko (talk) 13:57, 19 November 2023 (UTC)Reply
Translations from NorthEuraLex are (unfortunately) largely incorrect or imprecise. That's why I posted the edited list, although some Russophiles may not like the fact that I actually omitted most of the new (borrowed in the second half of the 20th century) Russian loanwords. Anazarenko (talk) 14:00, 19 November 2023 (UTC)Reply
  • incorrect, imprecise or incomplete
Anazarenko (talk) 14:10, 19 November 2023 (UTC)Reply
@Anazarenko: Please refrain from implying anyone here is a "Russophile". And you do not get to ignore sources just because of your political opinions. Also, what are your sources for the source being "largely incorrect or imprecise"? Are you the Mordvinic speech communities? Are you a native speaker of either language at all? Did you speak to natives about this, ask them what words they used, and published these interviews? Because there is absolutely no reason for anyone to believe your word against a published resource unless you give any evidence of you being any kind of authority at all. Thadh (talk) 19:49, 19 November 2023 (UTC)Reply
I am not a native user (although I specialize in Uralistic), but each of the words I added comes from dictionaries created with the help of native speakers. Nothing was invented by me. I'll post a list of all the sources used below the list soon. Anazarenko (talk) 21:04, 19 November 2023 (UTC)Reply
  • Uralistics
Anazarenko (talk) 21:07, 19 November 2023 (UTC)Reply

Template:lookfrom edit

This template generates:

Pages starting with “word”.

Compare this to {{prefixlanglemma}}, which now looks like this after I just spruced it up:

English terms starting with “word”

{{prefixlanglemma}} is superior because it is limited to terms in the current language, but it takes a language code when {{lookfrom}} does not. I propose that we delete the current {{lookfrom}} template, and move {{prefixlanglemma}} to {{lookfrom}} while simultaneously using a bot to add a language code to all invocations. This, that and the other (talk) 08:28, 23 November 2023 (UTC)Reply

Template:Icelandic adjectival declension absolute edit

Template:Icelandic adjectival declension indeclinable edit

Every declined form in these templates is the same. The tables are therefore pointless and should be replaced by a note in the headword line saying that the term is indeclinable. This, that and the other (talk) 08:40, 23 November 2023 (UTC)Reply

@Numberguy6 @Helrasincke pinging active editors with Icelandic knowledge This, that and the other (talk) 10:50, 3 December 2023 (UTC)Reply
Most of the terms using the template are adjectives based on the present participle which are indeed indeclinable. I agree that a table is superfluous here. As mentioned by @Urszag, a solution that preserves the categorisation would be ideal. As for being able to be used in all cases/numbers, a usage note should suffice. Helrasincke (talk) 11:29, 3 December 2023 (UTC)Reply
I agree. Numberguy6 (talk) 17:38, 3 December 2023 (UTC)Reply
I'm not an Icelandic editor, but there are two benefits that appear to my naive eyes: 1) it makes it explicit that the word can be used in all cases and numbers, and 2) the "Pages that link to "Template:Icelandic adjectival declension indeclinable"" lists words in this category. For 2), the solution could be some label that actually sorts these words into a proper category.--Urszag (talk) 11:15, 3 December 2023 (UTC)Reply

December 2023 edit

Module:R:Grimm edit

Migrated to the more generic Module:R:Wörterbuchnetz. Jberkel 18:59, 16 December 2023 (UTC)Reply

Appendix:Mass Effect edit

I would like a verdict on keeping or deleting this page. Check WT:FICTION. I do not want to participate in debate, only accept the decision and move on. Thanks! --Geographyinitiative (talk) 05:21, 17 December 2023 (UTC)Reply

Keep per being clearly within WT:FICTION- see my argument at Talk:Ardat-Yakshi etc. I can see I have stirred up the pot on WT:FICTION and pages that were not touched for years are being deleted. I think WT:FICTION is great, and Appendices of Fancruft are exactly what a website created in the 2000's would be about. Now we live in the 2020's, and the spark has to be snuffed out. I provide, offer, nor wish to make any further argument- if your 2023 mind has to eliminate everything good from the 2000's, I will comply. The word "cruft" is not an argument. --Geographyinitiative (talk) 06:03, 17 December 2023 (UTC)Reply
Delete fancruft. The claim of "eliminating everything good from the 2000's" is silly. I want to keep dictionary words from the 2000s since this is a dictionary. I do not want to keep encyclopaedic topics, cookie recipes, or kitten photos here, since those are not for dictionaries — 2000s or otherwise. Equinox 10:48, 17 December 2023 (UTC)Reply
Review WT:FICTION --Geographyinitiative (talk) 12:33, 24 December 2023 (UTC)Reply
Delete There are already Mass Effect wikis + Wikipedia which document this sort of stuff so it won't get lost. Maybe it could be of linguistic interest to conlangers, but does Mass Effect even have proper conlang(s)? Jberkel 11:33, 17 December 2023 (UTC)Reply
Review WT:FICTION --Geographyinitiative (talk) 12:33, 24 December 2023 (UTC)Reply
Did you want an opinion, a clarification of WT:FICTION, or just use the vote to keep your work from getting deleted? – Jberkel 23:42, 25 December 2023 (UTC)Reply
 
Me coloring outside the lines
When I made this Appendix, I didn't realize I was stepping on a raw nerve of the community- you all do what seems best- opinions, clarifications, deletions, etc. I would like to note that I do not care if "my" work is deleted. The question is ultimately "is this appropriate for the Wiktionary project?" and if I color outside the lines, it needs to be erased. I am such a bizarre person, but I'm also partially self-aware of that fact, so I try to cooperate when normal people tell me I'm going too far. lol --Geographyinitiative (talk) 11:54, 26 December 2023 (UTC)Reply
Keep: As far as I ccan see, this page doesn't violate policy. I don't like appealing to the existence of third-party wikis, which often supply an inferior user experience with stuff like ads, to justify deletionism. Lists of words and names are not comparable to cookie recipes or kitten photos. --Urszag (talk) 04:10, 20 December 2023 (UTC)Reply
That's because we don't have a policy on what should go in the Appendix. I feel like we could really do with a set of overarching guiding criteria that define the scope of the namespace, which could evolve into a more formal policy after several years of trial and error. Without any guidance, it's very difficult to know whether to keep or delete this page. I could probably make a bona fide argument for either case. This, that and the other (talk) 08:14, 20 December 2023 (UTC)Reply
I guess keep, per CFI. However, I would recommend Geographyinitiative to find some cites that do not other reference Mass Effect for some of the words. CitationsFreak (talk) 22:41, 25 December 2023 (UTC)Reply
If the policy allows us to keep this dreck, the policy is wrong. Delete. PUC23:58, 25 December 2023 (UTC)Reply
Keep per WT:CFI and WT:FICTION. In my opinion, there's not much sense in deleting this appendix specifically while keeping others like Appendix:Dungeons & Dragons and Appendix:Magic: The Gathering. If some people don't think any of those appendices should be here, I suppose we can talk / discuss / vote about the possible idea of changing the current policies. But in my opinion, the policy is OK as it is and I think we should instead create more fiction appendices and expand our coverage of fictional terms. --Daniel Carrero (talk) 00:26, 30 December 2023 (UTC)Reply

"Wiktionary has grown beyond a standard dictionary and now includes a thesaurus, a rhyme guide, phrase books, language statistics and extensive appendices." Wiktionary:Main Page --Geographyinitiative (talk) 17:24, 13 February 2024 (UTC)Reply

Category:Coptic terms derived from Greek edit

Category:Coptic given names from Greek edit

Category:Coptic female given names from Greek edit

Category:Coptic male given names from Greek edit

The way we define Greek and Ancient Greek pretty much excludes any borrowing from the former into Coptic while it was a living language. In fact, after going through the entries in the main category starting with the first letter in the Coptic alphabet I was unable to find any that had modern Greek in their etymologies. These are all due to misuse of the {{given name}} template's "from" parameter: i.e., |from=Greek instead of |from=Ancient Greek. The clincher is that this main category has no borrowing subcategory, while the Ancient Greek equivalent does.

There are still 82 entries left where "Greek" needs to be changed to "Ancient Greek" in the templates, or I might have speedied these myself. It does give us an opportunity, though, to consider what might be done to spot blatant mismatches such as these between the etymology templates and the name templates- maybe not in real time, but as a periodic bot or AWB task fed from the dumps. This is unusual in being categorically 100% wrong, but you can be sure that there are similar errors scattered through other derived terms categories Chuck Entz (talk) 01:58, 25 December 2023 (UTC)Reply

@Chuck Entz This is an issue that comes up with any language that has a name frequently used to refer to its ancestors: cf. Mongolian, French etc. The real issue is that we need to overhaul our name templates, since they use their own bespoke system that simply categorises entries based on whatever you put in the from= parameter. This is useful when used with things that aren't languages, but with languages it simply causes a headache. Pinging @Benwing2 who may have ideas on how to fix this. Theknightwho (talk) 19:12, 25 December 2023 (UTC)Reply

Category:Physical actions edit

This top-level category has only two bottom-level subcategories: Cat:Hit and Cat:Rub. These should be handled by Thesaurus entries, not by categories. This, that and the other (talk) 01:33, 27 December 2023 (UTC)Reply

Delete. Ioaxxere (talk) 07:13, 27 December 2023 (UTC)Reply

Category:English idiomatic construction prototypes edit

Links to a nonexistent appendix. Not sure what's going on here. @DCDuring? Ioaxxere (talk) 07:50, 27 December 2023 (UTC)Reply

As it says on the tin, it is experimental. Obviously it is an experiment that has been abandoned. I don't think anyone here is a follower of construction grammar (or whatever). DCDuring (talk) 13:53, 27 December 2023 (UTC)Reply

Created in 2004, I assume we don't need it anymore. Ioaxxere (talk) 07:50, 27 December 2023 (UTC)Reply

Template:bo-noun edit

Template:bo-adj edit

Template:bo-adverb edit

Template:bo-numeral edit

Template:bo-phrase edit

Template:bo-post edit

Template:bo-pronoun edit

Template:bo-proper noun edit

Template:bo-interj edit

Template:bo-particle edit

Tibetan headword templates. All of these are completely pointless: they're just a wrapper for {{head}} which do absolutely nothing except remove almost all of the functionality. Worse than nothing. Theknightwho (talk) 23:06, 29 December 2023 (UTC)Reply

Delete. @Benwing2 for the replacement. This, that and the other (talk) 04:32, 21 February 2024 (UTC)Reply
@Theknightwho @This, that and the other Done. Benwing2 (talk) 05:49, 21 February 2024 (UTC)Reply
So, I was just about to add in comparatives and superlatives for Tibetan adjectives to {{bo-adj}}, since in Tibetan, adjectives that follow the common form, for example མང་པོ (mang po, many), also form comparatives in predictable ways (e.g. མང་བ (mang ba, more) or མང་ང (mang nga, more)), and superlatives are all formed with the addition of the particle ཤོས (shos). It would be fairly trivial to implement this.
However, I just saw that now no there is no {{bo-adj}}…can we bring this back?
As for the others, they are probably not needed, although {{bo-pronoun}} could have been easily outfitted with a "desc" parameter like {{en-pronoun}} and served the same purpose.
Hermes Thrice Great (talk) 03:45, 4 March 2024 (UTC)Reply
IMO you are welcome to reimplement {{bo-adj}} with comparatives and superlatives (although keep in mind if they are completely regularly formed by the addition of a comparison word before them, it might be superfluous to include this info in the headword). However I would wait for User:Theknightwho and User:This, that and the other to chime in. Benwing2 (talk) 03:54, 4 March 2024 (UTC)Reply
No objection. It looks like comp/sup adjectives are formed by suffixing, and might even be somewhat regular, so this would be a good use case for a langusge specific template.
@Benwing2 have there ever been discussions about making {{head}} take care of all the language specific logic, so we don't need language specific templates whenever custom functionality is wanted? Or is that a total non-starter due to Lua memory issues? This, that and the other (talk) 07:56, 4 March 2024 (UTC)Reply
@This, that and the other I don't think this is a non-starter. In fact, we have several modules (more like subsystems) that have language-specific information attached to them. The closest to what you're thinking of is probably the language-specific support in Module:form of, which supports additional per-language parameters to handle inflected forms of participles, comparative/superlative adjectives, etc. where the term on the pagename is an inflected form of a term that is itself an inflected form of a lemma. The additional parameter specifies the underlying lemma, e.g. on the Gothic participle form 𐌰𐍆𐌻𐌴𐍄𐌰𐌽𐌳𐌰 (aflētanda), we have the following:
  1. {{infl of|got|𐌰𐍆𐌻𐌴𐍄𐌰𐌽𐌳𐍃||nom|m|s|prespart-of=𐌰𐍆𐌻𐌴𐍄𐌰𐌽}}
which displays as
  1. nominative masculine singular of 𐌰𐍆𐌻𐌴𐍄𐌰𐌽𐌳𐍃 (aflētands), the present participle of 𐌰𐍆𐌻𐌴𐍄𐌰𐌽 (aflētan)
Potentially we could do something similar to add support for per-language and per-POS inflection parameters. The main issue here is that there's a great deal of language-specific logic associated with the headword modules of many languages, so if we were to try to create a general mechanism to support it all through {{head}} (and allow languages to turn off individual features, which IMO is also important), the result might be an incomprehensible monstrosity. Instead of that, I have considered implementing a general framework for creating headword modules, similar to the general framework we currently have in place for inflection modules in Module:inflection utilities. This would provide out-of-the-box features that are wanted or needed by most headword modules as well as additional features that could be enabled on a per-language basis, and the ability to fall back to custom logic for complex cases. We would still have per-language headword templates like we have now but it would help standardize the params of those templates and ensure that as much as possible the same functionality is available on all of them. It could also auto-generate most of the documentation of the headword templates implemented through it, which is a big problem currently. I wrote about 150 lines of such a framework when I started reworking the Persian headword module with the intention of having the reworked Persian headword module use the new framework, but I never finished either of them. Benwing2 (talk) 08:58, 4 March 2024 (UTC)Reply
It would definitely be great to have a way that makes it really easy to develop headword modules/templates for new languages, so that new functionality can be easily implemented without losing the core parameters of {{head}} via a naive template-that-transcludes-{{head}} implementation.
As for centralising all headword templates into {{head}}, the different handling of the positional parameters would be an obstacle - not necessarily insurmountable, but editors who would need to switch from typing {{fr-noun|f}} to {{head|fr|noun|g=f}} would need to be convinced that there was some benefit to the change. This, that and the other (talk) 09:54, 4 March 2024 (UTC)Reply
I'm not sure we want to force people to use {{head}} for all headword templates; even with the shortcuts I created some time back (so you can write {{h|fr|n|g=f}} instead of {{head|fr|noun|g=f}}, I think there's benefit to having language-specific templates for the more common cases that have significant functionality customized to the particular language. Benwing2 (talk) 00:26, 5 March 2024 (UTC)Reply
@Benwing2 Customisation is good, but having what is effectively a headword API would be far better than the current solution, where >50% of headword templates are a net negative. A lot of editors seem to think having language-specific headword templates is important, even if they do nothing. Theknightwho (talk) 11:40, 5 March 2024 (UTC)Reply
Yes. I don't think we're disagreeing on anything. Benwing2 (talk) 22:58, 5 March 2024 (UTC)Reply

January 2024 edit

Several issues:

  1. Not specific to any one simplification system, so it's a random mix of Chinese and Japanese characters without any language-specific indication.
  2. Is it supposed to refer to characters which were unchanged by simplification? Presumably not (since that would include almost all of them), but a strict reading of the name would include them.
  3. What about situations like , 𠕅 and 𠕂 where simplified Chinese simplifies all three to the first one?

None of this is explained, and the entries seem to be pretty random. At the very least if we keep this, we should subcategorise by simplification system. Theknightwho (talk) 09:47, 7 January 2024 (UTC)Reply

@Theknightwho IMO this should be converted to an Appendix with proper explanations, similarly to what User:Nicodene did with Appendix:Survivals of the Latin nominative in Romance (which used to be a collection of categories with explanations provided in HTML comments, where no one saw them). If no one steps up to do the conversion, we should just dump the category contents in an Appendix and delete the category. Benwing2 (talk) 07:37, 2 March 2024 (UTC)Reply

Template:cite edit

See Wiktionary:Grease_pit/2024/January#old_uses_of_T:cite_that_don't_work_right. The relatively few (<500) uses of this should be changed to templates like {{cite-book}} (and cite-web, etc) or, in many cases e.g. on citations pages, {{quote-book}} (quote-web, etc). - -sche (discuss) 01:46, 16 January 2024 (UTC)Reply

Keep, but deprecate. There is no need to make old forms of pages unreadable. --RichardW57m (talk) 09:39, 16 January 2024 (UTC)Reply
Actually, the use of cite seems to make the pages unreadable already, which is what prompted the grease pit discussion... - -sche (discuss) 18:25, 17 January 2024 (UTC)Reply
Delete. I removed it from one reference template where it was used. I also switched all uses on Citations: pages to the appropriate quote-* template, as they were broken. Now with less than 300 uses, it can be deleted outright after the uses are replaced with cite-*. It does not need to be preserved forever in a deprecated state. This, that and the other (talk) 01:10, 18 January 2024 (UTC)Reply
Delete. Benwing2 (talk) 07:34, 2 March 2024 (UTC)Reply
Orphaned and deleted. The ~300 uses is well below the minimum threshold of 1,000 uses that I normally consider for deprecation instead of deletion. Benwing2 (talk) 03:46, 9 March 2024 (UTC)Reply

Appendix:ǃKung word lists edit

The data is corrupted by OCR. Even the English glosses, in some cases I can't tell what the word is supposed to be (e.g. "slamp").

I started "correcting" the entries by assuming the author or typesetter had intentionally substituted with ASCII letters due to DB limitations, e.g. ǂ with "=+" or similar, and ǁ with "ll", but it now looks like it's OCR corruption and so cannot be fixed without verifying every word with the original source, and my "corrections" have presumably added their own errors (as well as obscuring the corruption of the text). E.g. an L at the beginning of a morpheme might be a dental click, but sometimes may actually be an L. There are other letters like "ü" are presumably also click letters, but I have no idea which one. So the page has essentially no value and is not of the minimal quality we would expect for Wiktionary. kwami (talk) 19:07, 29 January 2024 (UTC)Reply

This should be at Wiktionary:RFDO. Andrew Sheedy (talk) 21:47, 29 January 2024 (UTC)Reply
Ok, moved. kwami (talk)

kwami (talk) 22:27, 29 January 2024 (UTC)Reply

Delete. It is unfortunate, but in such a case unless we have access to the original OCR source and someone is willing to proofread and fix the errors, the word list gains us negative value and should be deleted. Benwing2 (talk) 07:33, 2 March 2024 (UTC)Reply

Appendix:English collocations edit

+subpages, which are mostly lame. I added the remaining collocations to main entries SpAway (talk) 23:49, 29 January 2024 (UTC)Reply

Delete. Ultimateria (talk) 18:17, 3 February 2024 (UTC)Reply
Delete. Equinox 02:22, 12 February 2024 (UTC)Reply
Delete. Jberkel 21:37, 26 February 2024 (UTC)Reply
Deleted. Benwing2 (talk) 05:03, 1 March 2024 (UTC)Reply

February 2024 edit

Template:list:place names in England with caer in Welsh edit

Pinging the creator @Llusiduonbach.

I'm afraid I don't really see the point of this one: can't this simply be dealt with by putting them under the derived terms at Welsh caer? We definitely don't need this at every entry in the list. Theknightwho (talk) 21:33, 9 February 2024 (UTC)Reply

Agreed. This, that and the other (talk) 00:20, 10 February 2024 (UTC)Reply
@Theknightwho Fair enough. Go for it! Llusiduonbach (talk) 11:20, 10 February 2024 (UTC)Reply
@Theknightwho I've removed the template from entries and added the derived terms to Welsh caer. Thanks / Diolch. Llusiduonbach (talk) 11:53, 10 February 2024 (UTC)Reply

Category:Old_Galician-Portuguese_verb_inflection-table_templates edit

Regular verbs should be conjugated automatically once there's already an automatic template responsible for regular conjugations. Such tool has been developed by Benwing with the assistance of the Galician and Portuguese community. Duplicated verbs should be deleted either, they were used as essential tests.

Highly regular verbs:

Template:roa-opt-conj (contar) edit

Template:roa-opt-conj (tornar) edit

Template:roa-opt-conj (beber) edit

Template:roa-opt-conj (bever) edit

Template:roa-opt-conj (foder) edit

Template:roa-opt-conj_(tolher) edit

Template:roa-opt-conj (repartir) edit

Duplicated verbs:

User:MedK1/ogp/Template:roa-aplazer edit

User:MedK1/ogp/Template:roa-aprazer edit

User:MedK1/ogp/Template:roa-plazer edit

User:MedK1/ogp/Template:roa-prazer edit

Thalyson2019 (talk) 14:55, 22 February 2024 (UTC)Reply

Delete the templates. They are all unused and obsolete. As for the user pages, these belong to MedK1. If they no longer want them, they can be deleted, otherwise they will be kept. This, that and the other (talk) 09:58, 29 February 2024 (UTC)Reply
Delete. Benwing2 (talk) 03:28, 2 March 2024 (UTC)Reply

Template:dra-pro-noun edit

Template:dra-pro-pronoun edit

Template:dra-pro-adj edit

These do absolutely nothing, and are simple wrappers for {{head}}. User:AleksiB 1945 - it's not a good idea to create templates like this, because all they do is reduce the functionality, since the more obscure parameters now aren't possible to use. Headword templates should only be created if they do something special. Theknightwho (talk) 21:02, 24 February 2024 (UTC)Reply

Template:dra-pro-verb edit

This has an extra parameter for transitivity, but (a) it isn't being used by any entries, and (b) that doesn't justify the loss of the rest of the functionality, since it's trivial to simply add a label in the way we normally do for other languages. Theknightwho (talk) 21:07, 24 February 2024 (UTC)Reply

Module:parameters/lite edit

This was created to be a less intensive version of Module:parameters, back when memory issues were causing us major issues; a number of features have been stripped out, including the check for invalid parameters, which means that it can't be used to catch invalid template inputs.

It's no longer in use, and I see no clear need for it going forward since the memory limit was doubled, as no page even comes close to the limit. Theknightwho (talk) 13:27, 26 February 2024 (UTC)Reply

Template:desc/sl-tonal edit

This is just {{desc}}, but adds the label "tonal orthography" after it. I'm not even sure whether it follows the same format as {{desc}} anymore, since @Benwing2 changed how it worked. Either way, it's a wikicode mess, and a pointless maintenance headache that will inevitably get forgotten about. Theknightwho (talk) 16:50, 28 February 2024 (UTC)Reply

@Theknightwho There is also {{l/sl-tonal}} and maybe some others. The reason for these is that there are two different diacritic systems for Slovene, one that marks tones as well as vowel length and the other which just marks vowel length, and references to Slovene terms are (or maybe were) a mess, with some using one system and some the other. In general you can convert from tonal -> non-tonal but not the other way around, and we were trying to move everything to tonal. Unfortunately, however, the two systems use the same (or at least overlapping) diacritics but for different purposes, so it's not possible to simply autodetect all uses of the non-tonal orthography and flag them automatically. So I created the special tonal templates to indicate that a given term uses the tonal orthography. Note that this was done a long time ago before I was very conversant with Wiktionary conventions. Someone will need to survey the current Wiktionary state to see whether the non-tonal orthography is still used; if so it might make more sense to distinguish the two orthographies with etym-lang codes. Benwing2 (talk) 23:48, 28 February 2024 (UTC)Reply
@Rua who added a lot of the Slovene infrastructure. Benwing2 (talk) 23:49, 28 February 2024 (UTC)Reply

Category:Livonian compounds with kū etc. edit

There are nine such categories:

Essentially these categories are categorizing compound terms made up of specific words, e.g. pǟva (day), vālda (white) and mer (sea). In general, we don't categorize in this fashion; certainly not in English, for example. The set of words out of which such categories are made seems to be chosen essentially arbitrarily and if we did this consistently, it would lead to endless category bloat. @Neitrāls vārds who created the categories and Template:liv-compoundcat. Benwing2 (talk) 06:45, 29 February 2024 (UTC)Reply

Delete. I've added the pages in these categories to the Derived terms sections where they belong, except the three compounds with vālda because the page doesn't exist. Ultimateria (talk) 19:08, 1 March 2024 (UTC)Reply

March 2024 edit

Template:rfv-t edit

Effectively a duplicate of {{t-check}}. Theknightwho (talk) 23:51, 1 March 2024 (UTC)Reply

Delete. Benwing2 (talk) 03:27, 2 March 2024 (UTC)Reply

Now part of "root-stem nouns" (-c/-j/-h are not suffixes). Exarchus (talk) 12:51, 3 March 2024 (UTC)Reply

Delete. I complained about things like this when they were first implemented. There even used to be Category:Sanskrit bh-stem nouns but I deleted it awhile ago. Benwing2 (talk) 03:56, 4 March 2024 (UTC)Reply

Template:nan-coll edit

Template:nan-lit edit

Min Nan-specific forms of (colloquial) and (literary). Completely unnecessary. Theknightwho (talk) 19:20, 4 March 2024 (UTC)Reply

@Theknightwho Support although they link to language-specific pages describing what "colloquial" and "literary" mean in this context; I would maintain those links using language-specific label entries. Benwing2 (talk) 00:18, 5 March 2024 (UTC)Reply

Appendix:Irish given names edit

I brought up Appendix:Irish given names at WT:RFC due to multiple issues (addressed there). I have cleaned up the page to some extent but I think that it may be better to delete it since there’s already Category:Irish given names which renders the appendix redundant. 2001:BB6:B84C:CF00:6068:6AE:AFF4:590A 17:56, 9 March 2024 (UTC)Reply

The Help: namespace edit

Most of our help pages were written by long-gone users in the 2000s and hardly touched, updated, or even looked at since then. This includes our main help page Help:Contents, which is linked on the sidebar. This leads me to conclude that our help pages are doing more harm than good, and should be completely reorganized and rewritten. The Help: namespace only encourages this proliferation of long-forgotten help pages, and should be removed. Instead, we should create a single well-maintained help page at Wiktionary:Help which contains everything that a newcomer would need to know that can be read in nore more than a few minutes. Any additional advanced help (e.g. bots, templates, etc.) should be created as a subpage of this: this ensures that every help page links to Wiktionary:Help. Ioaxxere (talk) 20:29, 9 March 2024 (UTC)Reply

And all old subpages of User:HippieBot/Entries in Encarta online not in Wiktionary. They have been anti-blued and refined into a new list. Father of minus 2 (talk) 12:57, 10 March 2024 (UTC)Reply

The regenerated lists also exclude titles with no corresponding Wikipedia article, which may not have been in the scope of the original list. I'd rather keep User:HippieBot/Entries in Encarta online not in Wiktionary/all to preserve the original list, but I'll delete the rest when I get a chance later. This, that and the other (talk) 22:08, 10 March 2024 (UTC)Reply

Appendix:1000 most common Vietnamese words edit

Vietnamese. This is actually a list of the 1000 most common English words translated (and often badly translated) to Vietnamese. Deletion of this page has been suggested before. MuDavid 栘𩿠 (talk) 03:34, 14 March 2024 (UTC)Reply

Appendix:Adjectives indicating shape edit

Discussion moved from Wiktionary:Requests for moves, mergers and splits#Appendix:Adjectives indicating shape.

To Appendix:English adjectives indicating shape. The appendices are not just for English. — excarnateSojourner (ta·co) 01:26, 3 March 2024 (UTC)Reply

This seems like something to handle via categories. Theknightwho (talk) 10:54, 3 March 2024 (UTC)Reply