Wiktionary:Grease pit

Wiktionary > Discussion rooms > Grease pit

Click here to start a new Grease pit discussion.

Wiktionary discussion rooms (edit) see also: requests

Information desk start a new discussion | this month | archives Newcomers’ questions, minor problems, specific requests for information or assistance.

Tea room start a new discussion | this month | archives Questions and discussions about specific words.

Etymology scriptorium start a new discussion | this month | archives Questions and discussions about etymology—the historical development of words.

Beer parlour start a new discussion | this month | archives General policy discussions and proposals, requests for permissions and major announcements.

Grease pit start a new discussion | this month | archives Technical questions, requests and discussions.

All Wiktionary: namespace discussions 1 2 3 4 5 – All discussion pages 1 2 3 4 5

A grease pit

Welcome to the Grease pit!

This is an area to complement the Beer parlour and Tea room. Its purpose is specifically for discussing the future development of the English Wiktionary, both as a dictionary and thesaurus and as a website.

The Grease pit is a place to discuss technical issues such as templates, Lua modules, CSS, JavaScript, the MediaWiki software, extensions to it, abuse filters, Toolforge, etc. It is also the second-best place, after the Beer parlor, to think in non-technical ways about how to make the best, free, open online dictionary of “all words in all languages”.

Others have understood this page to explain the “how” of things, while the Beer parlour addresses the “why”.

Permanent notice

• Tips and tricks about customization or personalization of CSS and JS files are listed at WT:CUSTOM.
• Other tips and tricks are at WT:TAT.
• Find information and helpful links about modules, Lua in general, and the Scribunto extension at WT:LUA.
• Everyone is encouraged to expand both pages, or to come up with more such stuff. Other known pages with “tips-n-tricks” are to be listed here as well.
  
  

Grease pit archives edit
2026 January February March April May June July August September October November December 2025 January February March April May June July August September October November December
Earlier years 2024 January February March April May June July August September October November December 2023 January February March April May June July August September October November December 2022 January February March April May June July August September October November December 2021 January February March April May June July August September October November December 2020 January February March April May June July August September October November December 2019 January February March April May June July August September October November December 2018 January February March April May June July August September October November December 2017 January February March April May June July August September October November December 2016 January February March April May June July August September October November December 2015 January February March April May June July August September October November December 2014 January February March April May June July August September October November December 2013 January February March April May June July August September October November December 2012 January February March April May June July August September October November December 2011 January February March April May June July August September October November December 2010 January February March April May June July August September October November December 2009 January February March April May June July August September October November December 2008 January February March April May June July August September October November December 2007 January February March April May June July August September October November December 2006 October November December

May 2026

Adding a parameter for showing "hypocoristics" in Czech and Slovak nouns

I've been editing the Augustín page which had August and Gusto listed in "Derived terms" subsection, but correctly those are hypocoristics (see here and here); Slovak dictionaries have/use abbreviation dom. (domáci výraz; domácky) for names (see here and here as an examples).
Although there are abbreviations of hypok. (hypokoristikum) and fam. (familiárny výraz; familiárny) in dictionaries – they are common for nouns (see here as an example).
So, I propose to add an parameter for both Czech and Slovak nouns (in cs-sk-headword) to be able to have/show hypocoristics, like they have augmentatives and diminutives.
I'd prefer hypc for hypocoristics.

(see also this on page 46/48 – Zoznam skratiek a značiek). Pan1blG (talk) 14:10, 1 May 2026 (UTC)

Special:AbuseFilter/56

I tripped the filter while trying to tag Citations:XXXVI which contains triple braces when I was trying to add {{delete}} to the page. It should use added_lines instead of new_pst. Tenshi Hinanawi (talk) 17:18, 2 May 2026 (UTC)

Misuse of Template:Latn-def, Template:Cyrl-def and Template:Arab-def in entries with the wrong script

The way {{Latn-def}} is configured, it might be paraphrased as "the name in {language of the language code parameter}, written in the Latin script, for the Latin script letter(s) {letter parameter(s)}.

That means that a name for a Latin-script letter in a non-Latin script such as Malayalam കെ (ke, “k”) gets into trouble both because the template tries to force the headword into the Latn script, but Malayalam does not have "Latn" as an allowed script in our modules, and because the template links to the equivalent of "Malayalam K/k" [without the language name] which again tries to make our modules accept Latin script letters as Malayalam. {{Cyrl-def}} and {{Arab-def}} have similar issues.

This raises the obvious question: how do we fix these entries? We would need to have a template that can be configured to, for example, accept the headword as a Malayalam term in the Malayalam script, but link to the Latin-script letters as Latin-script letters in a Latin-script language.

The alternative would be to not use a specialized definition template at all, as seems to be the practice for English alpha, beta, and all the rest of our English names for non-Latin-script characters.

If we go the latter route, we would need to change the documentation for the templates I mentioned to make clear that they should never be used except in entries in the appropriate script in languages that are allowed to be in the script in question, and that will link to terms in the script and language in question.

I should mention that I was trying to work out the details as I composed this, so I apologize if I ended up writing a book about something that should be simple and self-evident. Chuck Entz (talk) 20:24, 2 May 2026 (UTC)

anchor template does not work with apostrophe

I noticed with some Japanese glossary terms, namely kan'on and kun'yomi. I even added them manually but they still don't work. TE(æ)A,ea. (talk) 21:23, 2 May 2026 (UTC)

I'm not sure what exactly is going on, but I inspected the anchor template on the line for "kun'yomi" after your edits, and this is what I saw:

<span id="kun&#039;yomi" class="template-anchor" data-id="kun'yomi"></span>

<span id="kun" class="template-anchor" data-id="kun"></span>

<span id="kun&#039;yomi" class="template-anchor" data-id="kun'yomi"></span>

I would have expected <span id="kun&#027;yomi", but I'm not very good at this type of coding and I really have no clue. Chuck Entz (talk) 00:32, 3 May 2026 (UTC)

Template:R:xqa:DLT

User:Aydinguluzada "fixed" this template so that 33 of the 466 entries in Special:WhatLinksHere/Template:R:xqa:DLT are now in CAT:Pages with ParserFunction errors. Apparently the template is applying some kind of mathematic or logical function that chokes on comma-separated lists. While in theory it's good to have more bells and whistles in template code, ParserFunction errors are the polar opposite of that- the template stops doing even the most basic tasks and is utterly useless without troubleshooting. Would someone please fix this? Chuck Entz (talk) 21:18, 3 May 2026 (UTC)

@Chuck Entz: should be fixed. The problem is that some editors have given the parameter |page= values like 12, 39 when |pages= should have been used. (@Aydinguluzada, for your information.) — Sgconlaw (talk) 22:36, 3 May 2026 (UTC)

Tech News: 2026-19

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Article guidance team invites experienced editors of pilot Wikipedias—Arabic, Bangla, Japanese, Portuguese, Persian, Turkish, Simple English, Spanish, and French—to help translate and adapt sample outlines. These outlines will guide editors in creating clear, well-structured, and policy-compliant articles when using the feature once it is launched in May 2026. Simple instructions on how to translate and adapt the outlines are available.

Updates for editors

• The Product and Technology Advisory Council has published draft recommendations on a model that affiliates can follow when contributing to the technical space. Community members are invited to provide feedback on the recommendation until May 8th on the talk page.
• The number of available thumbnail size preferences in MediaWiki is being reduced to three standardized options—Small (180px), Regular (250px), and Large (400px), as part of ongoing efforts to improve performance and reduce strain on thumbnail services. As a result, existing preferences will be mapped to the nearest new size (for example, smaller selections like 120px or 150px will render at 180px, while larger ones like 300px or 360px will render at 400px). The preferences interface will soon be updated to reflect these changes, and users who wish to opt out or provide feedback can do so. [1]
• From now on, even when a permission expires automatically, users will receive an Echo notification similar to the standard notification for permission changes. There is a difference between this and Global reminder bot in that the latter reminds users a week before the rights are due to expire, so that they can renew the rights.
• View all 32 community-submitted tasks that were resolved last week. For example, the problem where the ULS language selector in Special:Translate would scroll vertically when it shouldn't, has been resolved. Previously, when users opened the "Translate to English" dropdown and typed certain inputs, the dialog would scroll vertically by a few pixels even when there was enough space to display all results. The dropdown no longer shifts unnecessarily when filtering languages. [2]
• The Global Watchlist, which lets you view your watchlists from multiple wikis on a single page, continues to improve. For example, watchlists for Wikibase sites such as Wikidata now support EntitySchema elements for better tracking. The Live Updates mode now refreshes the special page every 60 seconds to comply with the updated global API rate limits for improved real-time responsiveness. Additionally, a directionality bug that displayed links as "changes 3" instead of "3 changes" in mixed-direction lists has been fixed. [3][4][5]

Updates for technical contributors

• The second phase of global API rate limits has been rolled out to reduce the impact of AI crawlers and ensure fair, sustainable access to Wikimedia resources, prioritising human and mission-aligned traffic. Limits have been shifted from per-hour to per-minute, producing smoother traffic patterns and more predictable API load. Community users are not expected to be affected, and no action is required. Early indications show some User-Agent-based requestors are adjusting behaviour, and around 64% of automated API traffic has been identified. Monitoring continues, and Wikimedia Enterprise remains available for commercial support.
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 20:43, 4 May 2026 (UTC)

Add yadootz

---

YADOOTZ

YADOOTZ is a coined term referring to an emotional‑literacy framework created by author Jennifer Kottke. The system uses tools, structured steps, and visual metaphors to help individuals identify, interpret, and regulate emotional states. It is designed for use across age groups, including children, adolescents, and adults, and emphasizes accessible emotional awareness and self‑regulation practices. Wiktionary

Overview

YADOOTZ functions as a structured method for understanding internal emotional signals and developing skills for emotional clarity, expression, and regulation. The framework aligns with broader concepts of emotional literacy, which involve recognizing, naming, and working with emotions in a constructive way. Emotional literacy research highlights the importance of accurately labeling emotions, which can reduce emotional intensity and improve self‑regulation. scienceinsig...

Purpose and Use

The YADOOTZ system is used as a practical toolset for:

• Increasing emotional vocabulary • Supporting self‑regulation • Improving interpersonal communication • Helping users navigate stress, overwhelm, and complex emotional states

Its structure parallels established emotional‑literacy models that emphasize recognizing, understanding, labeling, expressing, and regulating emotions. Wikipedia

Usage Notes

According to the existing lexicographical entry, YADOOTZ is treated as a proper noun and is used as the name of a specific emotional‑literacy system. Additional references may be added as published sources become available. - ~2026-22079-32 (talk) 23:06, 5 May 2026 (UTC)

@~2026-22079-32 "Yadootz is a coined term". Please read WT:CFI: we don't include terms people made up, regardless of their alleged merits. The only way this will ever have an entry is if there is evidence of usage independant of those who coined it. Also, we're a dictionary, not a place to describe or talk about things. It's not a coincidence that your efforts to create an entry have all been blocked by abuse filters- please read our Entry layout page to get an idea of what you've been doing wrong (aside from trying to promote made-up nonsense, of course). Chuck Entz (talk) 03:40, 6 May 2026 (UTC)

The book is released today on Amazon explaining it as a new form of emotional literacy not just a made up word. I hope it will be in the dictionary soon. Thanks for your time. ~2026-22079-32 (talk) 14:40, 7 May 2026 (UTC)

Apply colour to some non-Latin based languages

Arabic: صَارَ الطَّقْسُ بَارِدًا. ― ṣāra aṭ-ṭaqsu bāridan. ― The weather became cold.

Korean: 날씨가 추워졌다. ― Nalssi-ga chuwojeotda. ― The weather became cold.

I think the colour highlights look good on the Arabic usex, can we apply to some other non-Latin based or to all languages?  Anatoli T. ^{(обсудить}/^вклад) 06:52, 6 May 2026 (UTC)

Any takers? Any disagrees with the request/proposal?

@Erutuon, @Benwing2, @Theknightwho Anatoli T. ^{(обсудить}/^вклад) 03:10, 25 May 2026 (UTC)

 Weak oppose In my humble opinion, the colour highlighting works better in the Arabic example, because it uses colour highlighting instead of bolding. I do not know enough about Arabic to know if it avoids using bolding in the same contexts that the Latin script uses it, but if that indeed is the case, then colour highlighting makes for a sensible alternative. Inversely, your Korean example does use bolding, and to my knowledge Hangŭl belongs to a large group of non‐Latin scripts that accept bolding as an option for highlighting. For all such languages (including Korean), bolding should be used to effect parallellism between the usage example and its corresponding Latin transliteration. Applying colour highlighting to text that is already bolded would in my view be redundant – but should others find this proposal desirable to implement, I shall not stand in the way. VulpesVulpes42 (talk) 08:35, 31 May 2026 (UTC)

it-verb

just a weird thing i noticed ... {{it-verb}} uses a self-link instead of a bold font for the headword. is it just a style choice? —Soap— 20:22, 6 May 2026 (UTC)

• Who cares? Produces the same thing—User:Vealhurl (talk 08:58, 24 May 2026 (UTC)

etymon zoom out bug(?)

I've got a weird bug (I guess), while I was adding etymons – it happened to me at lážo-plážo and story.
I use the source editing with realtime preview panel, and when the etymon's etymology tree grows big, it adds in a "Zoom out" button. And when I clicked on it, my edits got pushed (published). Pan1blG (talk) 20:28, 6 May 2026 (UTC)

@Pan1blG I cannot reproduce this. I tried enabling the realtime preview as you describe, but there was no "Zoom out" button, even on a page with a large tree such as pneumonoultramicroscopicsilicovolcanoconiosis. Ioaxxere (talk) 19:25, 7 May 2026 (UTC)

would it be possible to display all sense/etym ID's inline for a gadget?

i would like to make the etym and sense ID's visible inline. but i dont think i can do it with simple CSS because there's not just one CSS class. is it feasible to do this with a gadget? that way it'd be easier to see what links to what, and where senses might need to be added.

relatedly, is it in the works to migrate all uses of {{etymid}} (which i'm still using) to {{etymon}} with a tree=0 parameter? or would the latter be too computationally expensive since it runs a whole script in the background? if we do migrate, what will happen to {{senseid}}? thanks, —Soap— 17:42, 7 May 2026 (UTC)

Isn't the ShowIDs gadget already for this Hftf (talk) 17:46, 7 May 2026 (UTC)

okay, yes, thanks. i didnt see that when looking through the list of gadgets just now. still want to leave my thread up for the other question, unless that's been addressed somewhere too. again thanks —Soap— 19:36, 7 May 2026 (UTC)

{{desc|lang|[[term]] ~ term}}

@Benwing2, is there a reason why ~ was added to Module:etymology/templates/descendant in this diff?

splitchar = "[,~]",
subitem_separator_map = {[","] = "/", ["~"] = " ~ "},

I ask because it prevents me from using {{desc|iir-pro|[[*Hrā́šti]] ~ *Hráȷ́ati}} to produce Proto-Indo-Iranian: *Hrā́šti ~ *Hráȷ́ati, which I can normally do this with {{l|lang|[[term]] ~ term}}. --{{victar|talk}} 10:13, 8 May 2026 (UTC)

sub-theme

sub-theme is an alternative form of subtheme.

How to create/link? Jtneill (talk) 01:18, 9 May 2026 (UTC)

Naming of Old Armenian declension paradigms

For some reason, Old Armenian declension paradigm templates call these o-type, i-type, a-type, i-a-type, and so on. The name "type" will be understood by most, but isn't "stem" the correct word for this? Missileboi (talk) 08:24, 9 May 2026 (UTC)

Any way to stop WF's "subst:new en noun" abuse?

Entries like thermofluctuation. Maybe an abuse filter? ~2026-28136-81 (talk) 10:35, 9 May 2026 (UTC)

Template:init

This template looks misspelled to me. Shouldn't it be moved to Template:innit? PUC – 14:39, 10 May 2026 (UTC)

• Loll —User:Vealhurl (talk 08:56, 24 May 2026 (UTC)

Tech News: 2026-20

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Community Tech has published new guidance explaining how wishes on Community Wishlist are triaged and prioritized. The documentation is intended to help contributors write stronger proposals by clarifying the factors that influence prioritization decisions. Beyond vote counts, the guidance highlights considerations such as potential impact on the community when determining which wishes move forward.

Updates for editors

• The Reader Growth team is launching an experiment to test a new Share Card feature that allows readers to create visually engaging cards from Wikipedia articles or selected article sections and share them online, with each card linking back to the original article to help expand readership and article discovery. The mobile-only A/B test will be available to a portion of readers on Arabic, Chinese, French, Vietnamese, and English Wikipedia to better understand reading and sharing habits, and is scheduled to begin the week of May 18 and run for four weeks.
• The Android and iOS Wikipedia apps recently released the 25-day reading challenge into Beta, as part of efforts to drive reader engagement by encouraging users to complete reading milestones. To track their reading streak during the challenge, App users can add a widget featuring Baby Globe to their home screen. The challenge officially begins May 11.
• View all 17 community-submitted tasks that were resolved last week. For example, an issue where the global preference for enabling syntax highlighting in wikitext could unexpectedly disable itself after being turned on, has now been fixed. [6]

Updates for technical contributors

• The ResourceLoader module mediawiki.ui.input, deprecated since September 2023, will be removed this week. There is a guide for migrating from MediaWiki UI to Codex for any tools that use it. [7]
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 19:20, 11 May 2026 (UTC)

Hawaiian Creole ancestor

Currently, Hawaiian Creole does not have any ancestor listed, and is not in a lexifier category. As far as I can tell, it should have ancestor en, which will place it in Category:English-based creole or pidgin languages. jlwoodwa (talk) 00:52, 12 May 2026 (UTC)

List of missing translations by language?

Hey! I'm not quite sure where I should ask this, but this might be the place. Forgive me if I'm wrong^^ It involves statistics and data dumps if I'm not mistaken ...

I've recently started adding some translations in the German Wiktionary ... There I found a page (here) that lists all languages categorised by their number of translations, and it also provides a link for each language that makes a search query filtering for random German words that, e.g., have missing English translations (see here or click "fehlende Übersetzungen Englisch" on the original page).

This is really helpful, and it's possible to just browse this page and add some missing English translations (and also for other languages) for German terms in the German Wiktionary.

I haven't found this option yet in the English Wiktionary. I was wondering whether it even exists and would maybe like to add some missing German translations for English terms?

It's really useful, and, if it doesn't exist here, maybe it could get added? Otherwise I'd just be browsing the Wiktionary trying to find terms without German translations ...

VeryCreativeNameIKnow (talk) 10:01, 12 May 2026 (UTC)

@VeryCreativeNameIKnow: You can use this search to find all pages with at least one translation table and no German translation on any of the translation tables. If you change "hastemplate:trans-top" to "incategory:English lemmas" it will also include pages that don't already have a translation table. If you're on a translating spree, Category:Requests for translations of German quotations contains a list of German quotations that are missing English translations. Some unofficial, per-language translation stats are available at User:JeffDoozan/lists/translations. JeffDoozan (talk) 15:49, 12 May 2026 (UTC)

@JeffDoozan You're a gem ... your help is very much appreciated! Thank you so much! VeryCreativeNameIKnow (talk) 20:57, 12 May 2026 (UTC)

Why are my inquiries being flagged as harmful and "probably vandalism"?

unfortunately when creating something that automatically flags someone else, there will be errors, and as im being flagged in User talk:Frog x Lover for a comment where im just seeking help and clarification, and being threatened with an IP block if i try to resubmit the comment, this error is hirting my ability to contribute and collaborate. Im not vandalising. My discussion was nothing but productive. This seems kind of poinless to being up but i guess if it werent an issue the flag wouldnt direct me here. ~2026-27325-56 (talk) 15:29, 12 May 2026 (UTC)

Could someone please fix this template bugging out?

The third quote on this page is displaying the template text rather than parsing it: Citations:Niu Tīreni. I'm not sure if it's related but the URL is ignoring the vertical bar too. Thanks for your help. Thank you even more if you can tell me what went wrong. Cameron.coombe (talk) 02:42, 13 May 2026 (UTC)

Nevermind, found the culprit Cameron.coombe (talk) 02:44, 13 May 2026 (UTC)

mammock lost its base in the conversion to {{ety}}

this used to show as having an unknown base, but when it was converted to use the new tree format, that base disappeared altogether due to being nonstandardly written and now we just show mammock deriving from -ock. can this behavior be fixed? might be other words that lost information in the conversion process? thanks, —Soap— 23:07, 13 May 2026 (UTC)

for reference, the code as it was before the change is

{{suffix|en||alt1=mam (of obscure origin)|ock|gloss2=diminutive suffix}}.

I suspect it was written this way so that it wouldn't link to anything. i've done this a few times myself. will such words be deleted when converted to the tree template? —Soap— 23:09, 13 May 2026 (UTC)

@Soap: fixed the entry itself, but the bot shouldn't have removed the information (@Fenakhay). — Sgconlaw (talk) 23:46, 13 May 2026 (UTC)

thanks, but is it still possible to de-link it? otherwise someone clicking through might still think it comes from the word for mother, despite our label. —Soap— 01:17, 14 May 2026 (UTC)

@Soap: Wouldn't the better approach be to prefix it with an asterisk (i.e., so that it displays *mam? If the root is unattested and its meaning unknown, there's probably a better way to express that fact than "of obscure origin", which would only imply that the etymology of mam is unknown. Andrew Sheedy (talk) 20:41, 15 May 2026 (UTC)

That sounds like a good idea, but still doesn't solve the problem of how to delink it ... unless you intend it to link to Reconstruction:English/mam, which we don't typically do. I found a link to a reconstructed English term here, but we removed it in May 2024 after it came up at a discussion. —Soap— 20:53, 15 May 2026 (UTC)

It used to be that you could just add an extra pipe and it would shift it into a parameter that would display without the link (either intended for alternative forms or for transcriptions; I don't remember). But I find the template that is there quite confusing. Andrew Sheedy (talk) 22:40, 15 May 2026 (UTC)

I agree. I've fallen behind lately .... I find a lot of our new templates confusing, but I suppose we'll all have to learn them. In the meantime Fenakhay has fixed up the page. The parameter we wanted was <alt:>. —Soap— 01:45, 16 May 2026 (UTC)

Even without {{etymon}} these didn't really work right: When the code for linking started to track nonstandard scripts, there were tons of these non-linking link parameters that weren't in the script for the language code used. I spent a good chunk of my time converting them to glosses, qualifiers, etc. in order to get rid of these bogus new members in "[language] terms in nonstandard script" categories. In some ways it's a lost cause, though, since emoticons and abstract morphemes like ∅- are treated by the linking modules the same as Burmese mixed with Arabic. For instance, I sincerely doubt that Category:Navajo terms in nonstandard scripts (1680 members) actually contains any terms in nonstandard scripts... Chuck Entz (talk) 02:33, 16 May 2026 (UTC)

I think dumtho should be on here

if we keep dumtho it will become a new meta for speech and short our time of talking Farmdude200000 (talk) 08:40, 14 May 2026 (UTC)

Template:R:la:M&A format bugs

Most of the phrases end in a "." which gets removed by cutting off the final character when formatting it, but in some cases that "." is absent and a letter ends up getting truncated instead. In other cases the character which gets removed is a different punctuation mark which I think it would be better to preserve (e.g. "?", "!", or "...").

commoditas#References: missing "t"

quotus#References: missing "?"

descriptio#References: missing ")"

prospectus#References_2: missing third "." of "..."

There are also some footnote markers which are not removed. Some are removed in the Latin phrases, but the same is not done to the English phrases. None of the transcriber's notes are caught either because they contain a "T" before the number and don't match the pattern.

clarus#References: has a "[1]" in an English phrase

artificium#References: has a "[TR1]" in a Latin phrase Turluccup (talk) 09:11, 14 May 2026 (UTC)

Unexplained change in search results

At Wiktionary:Todo#Useful search queries, I have a search that I've been using at least once or twice a week for upwards of a year in its latest version:

• Has "trans-top" but not in English or Translingual lemmas/non-lemma forms

Today, I noticed that there are now 14 false positives: they are all in one of the categories the search is supposed to exclude (Category:English lemmas). Given that my search hasn't been changed recently, and that many of the pages in question show no revisions for months (the oldest is September of 2024), I can only conclude that something has changed with MediaWiki's CirrusSearch within the past week. Searching without the exclusions returns 143,360 results, which raises the obvious question of why the restrictive search only returns 14 false positives- not to mention why these specific 14 pages.

I tried navigating to the Todo page and clicking the search link in question using two different browsers on two different laptops (logged in on the current browser/laptop combination, logged out on the others). The results were identical. Just to be thorough, here are the 14 pages:

1. beauty spot
2. breechloading
3. citerior
4. endpoint
5. eruptive
6. fetal alcohol syndrome
7. natural logarithm
8. net profit
9. nucellus
10. under the impression
11. Kromfohrlander
12. Laestrygonian
13. Selma
14. Tabitha

Chuck Entz (talk) 05:29, 15 May 2026 (UTC)

Now Tabitha has dropped out of the results, with nothing to explain why. Chuck Entz (talk) 15:18, 15 May 2026 (UTC)

Right after that, handler joined the list, but then I discovered that they can all be made to go away with null edits- the search is returning no results as of now. I'm guessing there was something that temporarily disrupted the image of the database that the search engine uses and that everything's back to normal. This kind of randomness makes me nervous, but there's no point in random speculation about randomness- so I guess we're done here... Chuck Entz (talk) 16:31, 15 May 2026 (UTC)

My guess is that it was broken copies of pages caused by a breaking change in the language data modules that persisted for a couple of minutes, but is still bubbling through all of the pages. — SURJECTION ^{/ T / C / L /} 16:55, 15 May 2026 (UTC)

Category collapsing on mobile

How would people feel about the list of categories in entries being collapsed by default on mobile (with the option to expand them, and a feature that remembers whether they're expanded or collapsed)? It can be rather long on pages that have multiple different languages on them. — SURJECTION ^{/ T / C / L /} 14:13, 15 May 2026 (UTC)

 Support. — Fenakhay ^{(حيطي · مساهماتي)} 14:18, 15 May 2026 (UTC)

Created a new gadget for testing under appearance. It only applies in mobile view (the Minerva skin, to be more specific). — SURJECTION ^{/ T / C / L /} 17:40, 15 May 2026 (UTC)

Template:hit-conj-table

This template should probably be officially deprecated considering that it is entirely unused and has been supplanted by Template:hit-conj. Graearms (talk) 16:34, 15 May 2026 (UTC)

Mobile web bug

For the last few weeks, I’ve been experiencing a bug on the mobile website (I’m on Safari on iOS, if that makes a difference) where clicking on something often leads to the wrong thing loading, especially if anything on the page is collapsed. EnigmaticLucas (talk) 04:06, 16 May 2026 (UTC)

Displaying Wiktionary family name without categorization or Wikipedia link

Refresh my memory: what syntax would I use to expand a Wiktionary family code (in this case sai-ven for the Venezuelan Cariban languages) to its full name without linking to a nonexistant Wikipedia article and without adding derivation categories? If I need to link to the Wiktionary category page, that's fine. {{desc}} already does this, but the formatting is all wrong for running text.

Or is this one of the holes in our template coverage? If so, it's definitely not a priority- though I'm guessing it would be pretty easy to code. Chuck Entz (talk) 03:52, 17 May 2026 (UTC)

QQ not working (again)

Is QQ working for you? For me, it isn't. The problem seems to be that the Google API always gives you a RATE_LIMIT_EXCEEDED when you use it without an API key (example query). I've tested this on multiple devices and from multiple IPs, but maybe it's just me and it works for you. My fix was creating a free Google API key and injecting it into the QQ script via the browser console.

localStorage["MediaWikiModuleStore:enwiktionary"] = localStorage["MediaWikiModuleStore:enwiktionary"].replace("maxResults:20", "maxResults:20,key:'my-api-key'")

It works, but it gets overwritten from time to time. Would it be possible for Wiktionary to create an official API key or would that be too much of a hassle (considering security for example)?

Tc14Hd (aka Marc) (talk) 08:27, 18 May 2026 (UTC)

A shared Wiktionary key isn't really feasible for obvious reasons. You can plug in your own now via Wiktionary:Gadget preferences. — Fenakhay ^{(حيطي · مساهماتي)} 08:49, 18 May 2026 (UTC)

Thanks, that works for me. Tc14Hd (aka Marc) (talk) 09:07, 18 May 2026 (UTC)

@Fenakhay: How do you do that? QQ hasn't been working for me either and I relied on it quite heavily in the past. I don't see a gadget for an API key. Andrew Sheedy (talk) 01:46, 19 May 2026 (UTC)

Follow this guide to create an API key. If you have QQ enabled, you'll see an input box to put your API key at Wiktionary:Gadget preferences. — Fenakhay ^{(حيطي · مساهماتي)} 01:52, 19 May 2026 (UTC)

Don't forget to enable the Books API here. — Fenakhay ^{(حيطي · مساهماتي)} 01:53, 19 May 2026 (UTC)

Thank you! I never would've figured that out on my own. Hopefully it keeps QQ working for a while and not just temporarily. Andrew Sheedy (talk) 03:00, 19 May 2026 (UTC)

I am labeled as potentially harmful

help ~2026-27674-74 (talk) 20:21, 18 May 2026 (UTC)

This label is applied based on the kind of edits you do. In one case, you added to a talk page, but what you wrote was nonsense. If you don't edit like that, the label won't appear. ―Justin (koavf)❤T☮C☺M☯ 22:38, 18 May 2026 (UTC)

Tech News: 2026-21

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Abstract Wikipedia team has identified five potential pilot wikis to assess their interest in adopting abstract articles on their wikis. The pilots are Malayalam, Bengali, Dagbani, Arabic, and Indonesian Wikipedia. The feedback period will be open until May 22. If your community is interested in becoming a pilot, let us know on Meta.

Updates for editors

• An experiment to show Reading Lists to logged-out readers on mobile web will launch on May 18 across German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu Wikipedias, and will run for one month. The effort supports broader goals of helping readers save and organize articles for later reading, while encouraging habits that could lead to future Wikipedia contributions.
• To support a bookmark button in the Reading List beta feature, the "Tools > Action" menu has been updated to display icons, including the watch star indicator that helps editors identify temporarily watched articles. The icons now also match those used on mobile, improving consistency across platforms. The change is currently limited to the actions menu and mainly affects editors with privileged user rights. [8]
• Suggestion Mode was released as an A/B test for newcomer editors on the mobile website at ~15 Wikipedias. The experiment will measure the impact that Suggestion Mode has on the proportion of newcomer mobile web edit sessions that result in constructive (un-reverted) article edits. The experiment will also evaluate the feature's impact on editor retention, and monitor changes in revert and block rates.
• View all 27 community-submitted tasks that were resolved last week. For example, an issue in the Wikipedia Android app where images could sometimes fail to load after opening a recommended reading list notification, has now been fixed. [9]

Updates for technical contributors

• The Wikidata Platform team has published its backend replacement recommendation and accompanying technical architecture for the migration of the Wikidata Query Service (WDQS) away from Blazegraph. Feedback is invited until May 25th 2026, especially on potential gaps and impacts on advanced use cases. Wikidata community members and WDQS users are also encouraged to help identify high-impact tools and workflows that may need attention on this page. Feedback can be shared on the Migration talk page or during the next office hour. See the WDP team newsletter for more details.
• Detailed code updates later this week: MediaWiki

In depth

• On English, French, Japanese, and a few other Wikipedias, there was a trial of hCaptcha, a third-party bot detection service. The trial showed that hCaptcha effectively detects and deters some bad-faith automated activity, on its own and by giving checkusers and stewards signals to look into. Because the results were positive, hCaptcha will be rolled out across all wikis over the next few weeks. See the hCaptcha project page for technical information about the implementation and privacy protections. Learn more.
• The latest Community Tech update is now available, with progress across several Community Wishlist initiatives, including Reading Lists expansion from the mobile app to the website, new language support for "Who Wrote That" and the Personal Dashboard, improvements to 3D rendering and Charts, and upcoming work on talk page sorting, audio playback, and editing workflows. The update also shares current priorities, wishlist status trends, and opportunities for community feedback on future focus areas and the Wikimedia Foundation’s 2026–2027 Annual Plan. Read the full newsletter for details.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 20:21, 18 May 2026 (UTC)

POS and sense parameters for list templates

proposing a small change to make it easier to update the titles of our derivation/relation lists, relating to the {{col}} and affix-see templates (e.g. {{prefixsee}}, {{suffixsee}}; ideally should be merged, though that is a separate matter).

in entries with multiple etylogies or POS's (particularly English ones), multiple lists are separated across each section, which (for affixes) are marked with titles such as "Terms derived from X (noun)" or "[...] (verb)". or in Slavic entries, I see derived terms typically broken down the object's POS (not the subject of the entry).

as such, to avoid boilerplate, I would like to that this be a feature part of these templates. in this implementation, for a given list, there may be the following options:

• {{col|en|foobar|pos=adj}}

  Terms derived from foo (adjective)

  • foobar

• {{col|en|foobar|pos=agent noun}}

  Terms derived from foo (agent noun)

  • foobar

• {{col|en|foobar|t=code}}

  Terms derived from foo (“code”)

  • foobar

• {{col|en|foobar|list_pos=n}} (unsure about this param name)

  Adjectives derived from foo

  • foobar

 Juwan  🕊️🌈 17:33, 22 May 2026 (UTC)

side-question: what are your thoughts on how to deal with unsorted lists? what I have done is adding a header on a higher level with the title "Unsorted terms", "Unsorted terms derived from X" or variations thereof. see English -le, which I edited recently.  Juwan  🕊️🌈 17:36, 22 May 2026 (UTC)

I saw a thread on Reddit recently complaining about mixing derivation types (phrases in with single words). For Polish, derived and related terms tend to be divided by POS. I think some sort of sorting would be beneficial. I'll also comment that a lot of this is automatable with {{etymon}} once we decide a format. I like separating by POS, probably best based on the headword. Vininn126 (talk) 09:09, 23 May 2026 (UTC)

MediaWiki:UpdateLanguageNameAndCode.js and extra data

After you add a language code, you can click a button to trigger this "updater" to automatically add the language code to canonical name and canonical name to language code mappings to the other modules. Could the script also automatically add blank "extra data" fields to the "extra data" modules? If I didn't add them manually with content, it's because there was no content to add (so I sometimes forget to add a blank "no really, there is no extra content to add" section to those modules, so it'd be nice if the "updater" script could do it). - -sche (discuss) 16:55, 24 May 2026 (UTC)

Template:it:Musical notes

This was in a todo list as an uncategorized page. It seems decent enough as it is- should we do anything to integrate it into our list-template framework/categories? Chuck Entz (talk) 01:11, 25 May 2026 (UTC)

Multiple subst parameters in a usage example template is difficult, especially with right-to-left languages

(Notifying Alarichall, Benwing2, Esperfulmo, Erutuon, عربي-٣١, Fay Freak, Assem Khidhr, Fenakhay, Fixmaster, Roger.M.Williams, Zhnka, Sartma):

In {{ux}}, we use |subst= to replace certain parts of the sentence for transliteration purposes. One substitution is fine but if you have multiple, they are separated with a comma: This wikicode

{{ux|ar|الْيَوْمَ سَنُمَارِسُ الْفَرَنْسِيَّةَ بِطَرِيقَةٍ خَاصَّةٍ.|Today we will practice French in a special way.|subst=سَنُمَارِسُ//سَ-نُمَارِسُ,بِطَرِيقَةٍ//بِ-طَرِيقَةٍ,الْفَرَنْسِيَّةَ//ٱلْفَرَنْسِيَّةَ}}

Results in

الْيَوْمَ سَنُمَارِسُ الْفَرَنْسِيَّةَ بِطَرِيقَةٍ خَاصَّةٍ.

al-yawma sa-numārisu l-faransiyyata bi-ṭarīqatin ḵāṣṣatin.

Today we will practice French in a special way.

I'd like to have alternatives, with |subst2=, |subst3=, etc. Is that a good idea and doable?

Apart from that, boldfacing a word breaks the hamzatu l-waṣli rule, which works otherwise, as with الْفَرَنْسِيَّةَ, which normally wouldn't need to be substituted, if it wasn't following boldfaced سَنُمَارِسُ. Anatoli T. ^{(обсудить}/^вклад) 03:21, 25 May 2026 (UTC)

Somehow the definite article gets separated with a hyphen automatically. Do I understand that you want the Arabic text to automatically guide the transliteration to hyphenate? Why isn't/can't that work with other particles, if needed? Side note: please avoid ٱ unless it's Quran. It has no place in even the most diacriticized texts. Texts must remain natural. Thanks. --Esperfulmo (talk) 19:04, 25 May 2026 (UTC)

@Esperfulmo:

I want to add hyphenations where it is the normally practice to do so at Wiktionary, e.g. one-letter prepositions with the next word, e.g. بِطَرِيقَةٍ (bi-ṭarīqatin), rather than "biṭarīqatin", so |subst=بِطَرِيقَةٍ//بِ-طَرِيقَةٍ does that, still displaying with no hyphens in the Arabic text.

Re your side note, as you can see the Arabic exposed text is not showing any ٱ but I am sort of forced to use |subst=الْفَرَنْسِيَّةَ//ٱلْفَرَنْسِيَّةَ to drop the initial unwanted vowel. Boldfacing the previous word breaks the regular transliteration rule.

This is the same usex without boldfacing, no substitution is necessary on the same word (I reduced by one):

الْيَوْمَ سَنُمَارِسُ الْفَرَنْسِيَّةَ بِطَرِيقَةٍ خَاصَّةٍ.

al-yawma sa-numārisu l-faransiyyata bi-ṭarīqatin ḵāṣṣatin.

Today we will practice French in a special way.

Anatoli T. ^{(обсудить}/^вклад) 07:00, 27 May 2026 (UTC)

Sandboxing Tewa IPA Module

Hi all, I've drafted a pronunciation module at Module:User:BenPulliam/tew-IPA for Tewa (tew) that produces an IPA phonemic and phonetic transcription of forms written in the orthography of the San Juan Pueblo Téwa Dictionary (with additionally accomodation for common alternate glyphs used when writing the language,i.e. æ for ä, ' for ʼ). IPA mapping is based on observations from Kiowa-Tanoan: A Synchronic and Diachronic Study Test sandbox at Template:User:BenPulliam/tew-IPA/sandbox, testcases at Module:User:BenPulliam/tew-IPA/testcases. This is my first module, so I would appreciate any feedback before I move it to Module:tew-IPA. Thanks. BenPulliam (talk) 08:03, 25 May 2026 (UTC)

spurious links to Wikipedia articles for languages not listed

on Category:Proto-Permic language it links to Wikipedia claiming there's an article, but there is none. Is it possible to sensitize this to whether an article exists, as we apparently manage to do for the Commons link underneath it? I don't know what the underlying template or module is, since this page just uses auto-cat. Thanks, —Soap— 15:15, 25 May 2026 (UTC)

Tech News: 2026-22

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Following a successful account creation experiment, an improved logged-out edit warning message will be deployed to all Wikimedia wikis in the first week of June. The change will only affect logged-out users on mobile web who open an editing session. The updated experience is designed to encourage account creation more clearly, while still allowing users to edit with temporary accounts. Results from the experiment showed a significant increase in account creation, with a 27% relative lift among users shown the updated message. As expected, as more people funnel into account creation, temporary accounts decreased by a relative 16%. The experiment did not show any significant changes in constructive edit rates or other monitored contributor metrics. [10]

Updates for editors

• For security reasons, members of certain user groups are required to have two-factor authentication (2FA) enabled. Members of these groups will be unable to disable the last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the next few weeks, users without 2FA will be removed from these groups. Notably, this applies to bureaucrats. See the linked tasks for deployment schedules. [11][12]
• WMDE Technical Wishes will run an A/B test on 10 wikis, testing potential improvements for Reference Previews. The experiment will run for ~2 weeks at the end of May / beginning of June and will affect 10% of desktop readers on the participating wikis.
• After two successful experiments, the Reader Growth team is rolling out an Image Browsing beta feature for all Wikipedias on mobile on May 25. This means that anyone who has all beta features on by default will start to see this feature, and others can check the box to turn it on in their preferences. The beta feature will include a carousel of all an article's images at the top of the article, with controls for editors to exclude images from the article's carousel or to exclude an article from the feature entirely.
• View all 30 community-submitted tasks that were resolved last week. For example, three dimensional STL files were being rendered incorrectly by the media viewer 3D extension which is now fixed. [13]

Updates for technical contributors

• The legacy CSS classes tleft and tright have been replaced with floatleft and floatright as the former do not work consistently across all MediaWiki platforms, notably mobile web and mobile apps. Projects relying on these classes are encouraged to review related usage and plan for migration. Please note that floatleft and floatright may also be deprecated in future, although there are currently no plans to do so. Read more.
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 21:52, 25 May 2026 (UTC)

Marking arguments as obligatory vs. optional with {{+obj}}

{{+obj}} is very versatile and well-made, but I’ve found myself holding back from using it because I can’t find a way to mark whether the arguments it displays are obligatory or optional with the definition it follows. Is there some way to do this that I’m missing, or is this a genuine gap in what it can do? If it is not currently possible, should we implement it, and, if so, what wording should we use?

I think this distinction is very important to have; right now I mark obligatory such arguments in an {{lb}} label before the definition, and optional ones in parentheses after the definition; see jrj for examples of both. I would very much like to replace all of these with {{+obj}} if the distinction can be maintained somehow. — Vorziblix (talk · contribs) 23:06, 26 May 2026 (UTC)

Category:Proto-Bantu 2-letter roots

I stumbled upon the category Proto-Bantu 2-letter roots, which contains entries like *-túg- and *-gènd-. Who (or what) decided that those have two letters? MuDavid 栘𩿠 (talk) 06:43, 27 May 2026 (UTC)

Polish genders in the translation adder tool

(Notifying KamiruPL, Hythonia, Tashi, Vininn126, Sławobóg, Silmethule, Rakso43243, Darellur, Ilawa-Kataka, Benwing2): Would it be possible to get the proper Polish genders added to the translation adder tool? I had a look at MediaWiki:Gadget-TranslationAdder.js but I'm not familiar with JS so don't really know where to begin. At the moment whenever we add a "masculine" noun as a translation, we have to then edit the page manually to distinguish between m-pr (masculine personal), m-anml (masculine animal [or as it used to be called m-an, masculine animate - never really understood why we changed that as I think animate makes more sense]) and m-in (masculine inanimate). Although these all get called "masculine" they behave like separate genders and most modern analyses treat them as such. Likewise, for words that are pluralia tantum we only have the option "plural", but for Polish these should be vr-p (virile plural) and nv-p (nonvirile plural). Cheers, BigDom 09:47, 27 May 2026 (UTC)

 Support. Vininn126 (talk) 09:52, 27 May 2026 (UTC)

There should be one rule for all languages that specifies this, not just for Polish. Sławobóg (talk) 10:06, 27 May 2026 (UTC)

Survey (proposed direction for Wishlist)

You are invited to voice your opinion on a new community-proposed direction for the Community Wishlist. Thank you! MediaWiki message delivery (talk) 03:07, 29 May 2026 (UTC)

Swedish alphabetical sorting is bugged

Alphabetical sorting for Swedish is currently bugged. The Swedish alphabet contains the letters A through Z, followed by Å, Ä, and Ö, in that order. The bug currently afflicting Wiktionary instead makes Å sort as if it were a variant of Z. Take for instance the category Swedish obsolete forms, and jump to the letter Z. The header correctly includes the page zegell, along with several terms beginning with Å, that should instead be grouped under a separate header for Å.

I believe that the issue arises from a bug in Module:languages/data/2, which contains the following code:

m["sv"] = {
"Swedish",
9027,
"gmq-eas",
"Latn",
ancestors = "gmq-osw-lat",
sort_key = {
remove_diacritics = c.grave .. c.acute .. c.circ .. c.tilde .. c.macron .. c.dacute .. c.caron .. c.cedilla .. "':",
remove_exceptions = {"å"},
from = {"ø", "æ", "œ", "ß", "å", "aͤ", "oͤ"},
to = {"o", "ae", "oe", "ss", "z" .. p[1], "ä", "ö"}
},
standard_chars = "AaBbCcDdEeFfGgHhIiJjKkLlMmNnOoPpRrSsTtUuVvXxYyÅåÄäÖö" .. c.punc,
}

This code effects some desirable substitutions, like making the obsolete forms aͤ and oͤ sort like their modern counterparts ä and ö instead. However, the section "z" .. p[1] seems to be causing Å to incorrectly get counted as a variant of Z.

Moreover, in my view Ø should be sorted as Ö rather than as O. Would someone be willing to fix the code such that:

1. Å gets sorted as itself rather than as Z, and
2. Ø gets sorted as Ö rather than as O?

Thank you. VulpesVulpes42 (talk) 16:59, 29 May 2026 (UTC)

The sorting order is correct. We cannot enforce a category-specific sorting order, so we have to categorize letters after Z as Z + a private use symbol to ensure the correct order. The category headers can be fixed separately with a JavaScript gadget. — SURJECTION ^{/ T / C / L /} 19:31, 31 May 2026 (UTC)

@Surjection Please accept my apologies, but I have no knowledge of how to do that myself. According to this earlier discussion, a similar issue seems to have been solved for Danish with an edit to a gadget which I do not have permission to edit anyway. Moreover, I still feel strongly that the section to = {"o" should be replaced with to = {"ö". At any rate, thank you for looking into this! VulpesVulpes42 (talk) 20:07, 31 May 2026 (UTC)

Is Å the only letter that displays incorrectly under Z right now? I can fix the Ø issue. — SURJECTION ^{/ T / C / L /} 20:37, 31 May 2026 (UTC)

@Surjection Yes, from what I can see Å is the only letter incorrectly displaying under Z. VulpesVulpes42 (talk) 20:40, 31 May 2026 (UTC)

OK, I'll add it to the configuration of the gadget. — SURJECTION ^{/ T / C / L /} 20:41, 31 May 2026 (UTC)

@Surjection Thank you so much, I can confirm that Å finally is getting sorted correctly in categories now! As for your fix to Module:languages/data/2, it does not seem to have affected how Ø gets sorted in categories, but I appreciate the effort highly nonetheless. Maybe changes to such a central module simply take more time to fully propagate throughout the website. At any rate, the by far worst issue is resolved now, so once again: thank you very much! VulpesVulpes42 (talk) 06:53, 1 June 2026 (UTC)

Problem with Template:pa-IPA

At Punjabi واریاں (vāreyāṉ), "{{pa-IPA|واریاں}}" is displaying as "". As far as I can tell, one of modules (probably Module:pa-IPA) is generating invalid IPA, which is then fed into Module:IPA. This isn't the first time this has happened, though I couldn't tell you the specific entry or what was done to get rid of the error.

I suspect the root of the problem is that Module:pa-IPA is taking the output of the regular translit process for Punjabi, making a few replacements, then feeding it to Module:IPA. While it's true that most of the characters in the transliterations are valid IPA characters, the exceptions aren't always obvious. In some cases the "characters" are letter-diacritic combinations, which complicates things further.

I don't have the depth of knowledge in either Lua or Punjabi to fix this specific error or to redesign things so there won't be more errors later on. but it seems like there has to be a better way than this "correct it when it blows up" model.

Can someone fix this? Thanks! Chuck Entz (talk) 17:25, 29 May 2026 (UTC)

Another mammoth page?

Less than an hour ago, i was briefly in CAT:E for no apparent reason. When I chedked the embedded report in the generated source, I noticed that Lua memory usage has passed the 90 MB mark:

NewPP limit report

Parsed by mw‐web.codfw.canary‐5667c7d4fc‐zffgl

Cached time: 20260530215317

Cache expiry: 2592000

Cache expiry source: Template:R:ca:GDLC (currentyear)

Reduced expiry: false

Complications: [vary‐revision‐sha1, prevent‐selective‐update, show‐toc]

CPU time usage: 11.304 seconds

Real time usage: 13.344 seconds

Preprocessor visited node count: 47982/1000000

Revision size: 100865/2097152 bytes

Post‐expand include size: 1682146/2097152 bytes

Template argument size: 94894/2097152 bytes

Highest expansion depth: 21/100

Expensive parser function count: 417/500

Unstrip recursion depth: 0/20

Unstrip post‐expand size: 1169724/5000000 bytes

Lua time usage: 7.901/10.000 seconds

Lua memory usage: 95162886/104857600 bytes

Number of Wikibase entities loaded: 0/500

I wouldn't know if this is bad enough for us to go to the trouble of converting it to a mammoth page, but I thought I would bring it to the attention of those who might. Chuck Entz (talk) 22:08, 30 May 2026 (UTC)

It's not the first. (See: Wiktionary Monitor). — Fenakhay ^{(حيطي · مساهماتي)} 00:05, 1 June 2026 (UTC)

Module error in Japanese entry at 決まった

It looks ike this is missing a very basic parameter. I'm guessing that it's either something easy to fix by anyone who knows how the Japanese templates work, or something fundamentally flawed that shouldn't exist at this spelling. Can one of our Japanese editors take a look? Thanks! Chuck Entz (talk) 20:22, 31 May 2026 (UTC)

Automated quotation insertion

Are there any tools or gadgets or bookmarklets or whatever for automating the insertion of quotations?

For example, I often insert quotations using {{quote-web}}, {{quote-journal}}, and {{quote-book}}, and I have to manually fill title, author, URL, date, etc. in wikitext. On Wikipedia, at least some things can often be autofilled by URL, DOI, or ISBN when using the Cite . Is there something like this on Wiktionary? Amir E. Aharoni (talk) 23:43, 31 May 2026 (UTC)