Wiktionary:Grease pit - Wiktionary, the free dictionary

Wiktionary:Grease pit - Wiktionary, the free dictionary
Jump to content
From Wiktionary, the free dictionary
Latest comment:
13 hours ago
by Eirikr in topic
Help needed with Module:ja-pron
Wiktionary >
Discussion rooms
> Grease pit
Shortcut
WT:GP
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
All discussion pages
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
March 2026
Reading of the character
edit
Latest comment:
1 month ago
3 comments
2 people in discussion
The character
is read as "vành" (which means "belt") in Vietnamese. The character itself is phonetic-semantuc compound: 金 for meaning and 榮 (vinh) for pronunciation). It is used in a famous Vietnamese figure name "Phan Bá Vành" (潘伯鑅), one of the rebels who fought against Emperor Minh Mạng (明命).
"Lỏng" is totally unrelated (I can't understand who can think of that pronunciation)
~2026-13267-06
talk
11:04, 1 March 2026 (UTC)
Reply
Erminwin
PhanAnh123
Pinging a couple of Vietnamese speakers to take a look at this. Our entry current says
is "lỏng" but the user above says it should be "vành", can you check which is correct?
- -sche
(discuss)
05:53, 10 March 2026 (UTC)
Reply
(OK,
MuDavid has changed it
.)
- -sche
(discuss)
15:20, 10 March 2026 (UTC)
Reply
Tech News: 2026-10
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
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
Wikipedia 25
Birthday mode
is now live on Betawi, Breton, Chinese, Czech, Dutch, English, French, Gorontalo, Indonesian, Italian, Luxembourgish, Madurese, Sicilian, Spanish, Thai, and Vietnamese Wikipedias! This limited-time campaign feature celebrates 25 years of Wikipedia with a birthday mascot, Baby Globe. When turned on, Baby Globe is shown on
~2,500 articles
, waiting to be discovered by readers. Communities can choose to turn Birthday mode on by getting consensus from their community and asking an admin to enable the feature and customize it via
community configuration
on the local wiki.
Updates for editors
Sub-referencing
, a new feature to re-use references with different details has been released to Swedish Wikipedia, Polish Wikipedia and
a couple of other wikis
. You can
try the feature
on these projects or on testwiki and
betawiki
. Learnings from the first pilot wiki German Wikipedia have been
published in a report
. Reach out to the Wikimedia Deutschland team if you are
interested in becoming a pilot wiki
Paste Check
will become available at all Wikipedias this week. The feature prompts newcomers who are pasting text they are not likely to have written into VisualEditor to consider whether doing so risks a copyright violation. Paste Check
tags
all edits where it is shown for potential review. Local administrators can configure various aspects of the feature via
Special:EditChecks
Research
across 22 wikis found that Paste Check resulted in an 18% decrease in relative reverted-edits compared to the control group. Translators can
help to localize
this and related features.
The
Reader Experience team
will be standardizing the user menu in the top right for all mobile users so that it is closer to the desktop experience. Currently this user menu is only visible to users with Advanced Mobile Controls (AMC) turned on. The only change is that a couple buttons previously in the left-side menu will move to the top right for users who do not have AMC turned on. This change is expected to go out March 9 and seeks to improve the user interface.
[1]
Starting in the week of March 2, the emails sent out when an email address was added, removed, or changed for an account will switch to a substantially nicer and clearer HTML email from the prior plaintext one.
[2]
Notifications are currently limited to 2,000 historic entries per user, and extend back to 2013 when the feature was released. This is going to be changed to only store Notifications from the last 5 years, but up to 10,000 of them. This will help with long-term infrastructure health and help to prevent more recent notifications from disappearing too soon.
[3]
The
Global Watchlist
which lets you view your watchlists from multiple wikis on a single page continues to see improvements. The latest update improves label usage experience. The
extension
now allows activating the
language fallback system
for Wikidata items without labels in the viewed language, and showing those labels in the user’s preferred Wikidata language if no
uselang=
URL parameter is provided.
[4]
[5]
The Wikipedia Android team has started a beta test of
hybrid search
on Greek Wikipedia. Hybrid search capabilities can handle both semantic and keyword queries enabling readers to find what they’re looking for directly on Wikipedia more easily.
For security reasons, members of certain user groups are
required to have two-factor authentication
(2FA) enabled. Currently, 2FA is required to use the group, but not to be a member of it. Given that this model still has some vulnerabilities, the situation will
gradually change in March
. Members of these groups will be unable to disable 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 second half of March, users without 2FA will be removed from these groups. This applies to: CentralNotice administrators, checkusers, interface administrators, suppressors, Wikidata staff, Wikifunctions staff, WMF Office IT and WMF Trust & Safety. Nothing will change for other users. See the linked task for deployment schedule.
[6]
View all 27 community-submitted tasks that were
resolved last week
. For example, the issue preventing users from creating an instance in
Wikibase.cloud
has now been fixed.
[7]
Updates for technical contributors
To help ensure
fair use of infrastructure
, over the next month the Wikimedia Foundation will implement global API rate limits across our APIs. In early March, stricter limits will be applied to unidentified requests from outside Toolforge/WMCS and API requests that are made from web browsers. In April, higher limits will be applied to identified traffic. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see
Wikimedia APIs/Rate limits
The Wikidata Query Service Linked Data Fragment (LDF) endpoint will be decommissioned in February. This endpoint served limited traffic, which was successfully migrated to other data access methods that were better suited to support existing use cases. The hardware used to support the LDF endpoint will be reallocated to support the ongoing backend migration efforts.
[8]
The new Parsoid parser
continues to be deployed to additional wikis
, improving platform sustainability and making it easier to introduce new reading and editing features. Parsoid is now the default parser on 488 WMF wikis (268 Wikipedias), now covering more than 10% of all Wikipedia page views.
The process and criteria for
requesting exceptional access
to the high volume feed of the
Wikimedia Enterprise
APIs (at no cost for mission-aligned usecases),
have now been published
. This is to provide more thorough and clearer documentation for users.
Tech Blog
, the blog dedicated to the Wikimedia technical community
will be migrating
to
Diff
, the community news and event blog. The migration should be complete in April 2026, after which new posts will be accepted for publishing. Readers will be able to access posts – old and new – on the landing page at
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
17:51, 2 March 2026 (UTC)
Reply
Proper nouns wrongly categorising as uncountable
edit
Latest comment:
25 days ago
4 comments
4 people in discussion
e.g.
Barstovian
is a proper noun ("the Barstovian"). It should
not
automatically go into English uncountable nouns. It is countable (there is exactly one). It's not an uncountable mass like "some rice".
~2026-13595-69
talk
21:07, 2 March 2026 (UTC)
Reply
"bump" as the kids say. Serious error affecting thousands of entries.
~2026-14738-79
talk
18:44, 8 March 2026 (UTC)
Reply
What is the problem or what do you think is the problem here? Per
{{
en-proper noun
}}
, you can modify individual entries to have plurals or mark as "countable and non-countable" on a case-by-case basis. Do you think that we should convert the template to say that all proper nouns are countable? That would make many more thousands of entries incorrect. If it is the case that geologic periods are countable, then those individual entries need to have modifications made to them. —
Justin (
ko
vf
19:44, 8 March 2026 (UTC)
Reply
I would wonder why proper nouns are appearing in a bare "nouns" cat at all. Don't we treat them as a separate POS? If not, we ought to.
I agree with Eq that this categorisation is silly. What would be better? "English proper nouns that do not admit a plural?" "English singulare tantum proper nouns"? Just "English proper nouns with no plural"? (But I suspect lots of our proper noun entries are incorrectly marked as not having a plural to begin with.)
This, that and the other
talk
20:00, 29 March 2026 (UTC)
Reply
etymon - updates from the aftermath of the vote
edit
Latest comment:
1 month ago
3 comments
2 people in discussion
See also
Wiktionary:Beer_parlour/2026/March#Establishing_rules_for_derivation_categories
Based on comments on the vote, I think we should:
Update the appearance of the tree by making the button less intrusive and more like the quotations button and perhaps some changes to the tree itself (though I'm unsure exactly what)
Have the tree auto-hide on multiword entries and on entries with no higher steps.
Vininn126
talk
12:34, 3 March 2026 (UTC)
Reply
I definitely support the auto-hiding feature & making it like quotations, where the button would be after the etymology text.
TranqyPoo
✏️
15:45, 4 March 2026 (UTC)
Reply
I also think we could add a function to mark a node as being worth to open and read separately (i.e. contains some complexities that might be missed by looking at just the tree) (per Discord). @
Fenakhay
Ioaxxere
Catonif
Vininn126
talk
13:02, 17 March 2026 (UTC)
Reply
Problematic infrastructure for Chinese linking templates
edit
Latest comment:
22 days ago
3 comments
2 people in discussion
(This follows on, and extends, the unresolved discussion started over in the
Wiktionary:Grease_pit/2025/November#Request_for_change_of_handling_of_ZH_terms_in_Template:obor
thread.)
Many (all?) Chinese templates using the generalized "all Chinese varieties" language code
zh
now default to:
always providing both traditional and simplified Chinese forms
always providing the Mandarin pinyin
In many cases, this behavior is unwanted.
For instance, in etymologies for other languages that have borrowed Chinese terms, we often want to display only the traditional form -- the simplified form is inappropriate, and arguably just plain wrong, in these contexts.
Sometimes we know that a term was borrowed from "Chinese", but we do not know which specific Chinese lect. In these cases, giving the modern Mandarin pinyin by default is just plain wrong.
Sometimes we might even know that the term was borrowed from a northern lect, but the date of borrowing is before the emergence of the standardized pronunciation of modern Mandarin in the 1900s. In these cases again, giving the modern Mandarin pinyin by default is just plain wrong.
Sometimes we even know that a term was borrowed from (or even into) Mandarin, but before the spelling reforms that produced the modern simplified Chinese character forms. In such cases, displaying the simplified form is again just plain wrong.
We already have and use the
cmn
language code to signify "Mandarin Chinese". If a user specifically uses a template with the
zh
language code for generalized "Chinese of any variety", we should not default to showing only Mandarin pinyin. This is logically incorrect behavior, and confusing for users.
By way of examples:
The
{{
obor
}}
template incorrectly provides simplified spellings and modern Mandarin pinyin, as we see in the Japanese entry for
烏賊
ika
squid; cuttlefish
, as shown
here
(before I
fixed
the display). The spelling was borrowed into Japanese no later than 938, almost a millenium before modern Mandarin pronunciation was standardized, and over a millenium before simplified Chinese was even invented. When the
{{
obor
}}
template was first
added
to that Japanese entry back in 2022,
{{
obor
}}
behaved as expected and wanted -- it only displayed the spelling entered as a parameter argument (not showing additional unprovided forms), and it did not show any romanization (appropriately omitted, since this template is specifically about borrowing the graphemes—phonemes are wholly irrelevant). Later changes caused the template to now default to showing information that is unwanted and incorrect in this context.
For the Japanese
頁岩
entry, this term appears to have been coined in Japanese in the 1890s, and was then borrowed into written Chinese. In writing the etymology there, I explain how the 頁 character was used in Chinese originally to mean "head", and later as an alternative spelling for 葉 meaning "leaf; page; sheet", and how the Chinese pronunciations and senses relate to the Japanese pronunciations and senses. Given the timing of this term, any simplified form is wholly incorrect, and should not be shown. However, I still want to show the modern Mandarin pinyin.
After some searching, I've found that different templates use different approaches to suppressing the newer behavior. Some take a
//
(double-slash) after the term argument, and some take a
(asterisk) before the term argument. Neither feature is very well documented, nor is either obvious. In addition, in either approach, this suppresses
both
the simplified spelling
and
the pinyin -- it does not appear to be possible to suppress one or the other.
My specific requests
edit
Please rework how
{{
obor
}}
deals with Chinese to default to 1) only showing the written form actually supplied as an argument (if the user enters a traditional form, do not show the simplified, and vice versa), and 2) not show any romanization unless explicitly included/enabled (this template is specifically is about orthographic borrowings, independent of any pronunciation).
Please remove Mandarin pinyin from all
zh
templates. If users want Mandarin, they should use
cmn
templates instead.
Please decouple the display of traditional / simplified forms, from the display of romanization. These two separate outputs should be enabled/disabled using separate operators/parameters.
After decoupling spellings from romanizations, please 1) standardize on how to enable/disable simultaneous display of both traditional and simplified, and 2) actually document this so editors can easily figure out how to use these templates. Using appended
//
in some templates and prepended
in others is terrible usability.
‑‑
Eiríkr Útlendi
Tala við mig
21:23, 3 March 2026 (UTC)
Reply
Eirikr
A workaround is
{{obor|ja|ltc|-}} {{ltc-l|烏賊}}
-- just skip the word in obor and proceed with whatever form you want. Ping me
User:内存溢出的猫
plz!
📝瞄？
💬喵!
03:30, 1 April 2026 (UTC)
Reply
Thank you, yes, I've used a similar approach in other places where the derivation is clearly Middle Chinese. In this context though, using
{{
ltc-l
|烏賊}}
still outputs the phonetics, which is not relevant:
烏賊
MC
'u dzok
In other cases, where the derivation is more ambiguously just "Chinese", using
{{
zh-l
|烏賊}}
outputs incorrectly (for this context) both 1) the unwanted simplified spelling, and 2) the Mandarin pinyin:
烏賊
乌贼
wūzéi
) ‑‑
Eiríkr Útlendi
Tala við mig
18:34, 1 April 2026 (UTC)
Reply
Template:de-adj noun forms of
interacting strangely
edit
Latest comment:
1 month ago
2 comments
1 person in discussion
At
Andere
, the page was created with a German L2, an L3 pronunciation section, a regular Noun L3 with
{{
de-noun
}}
and a Declension L4- all of which was followed by
{{
de-adj noun forms of
|mn}}
. That template is designed to generate its own L3 Noun headers, headwords, and definition lines. So far, so good.
Later, an Aquitanian entry was added to the page above the German section. Still no problem. Then the Aquitanian entry was converted to Latin, leaving the L2 sections in the wrong order. Aside from
Category:Pages with language headings in the wrong order
being added to the page, no problem on the technical side.
After all of this, the German and Latin sections were switched by a bot. Now the page is in
Category:German entries with incorrect language header
. As far as I can tell, all of the headers are at the correct level and in the correct order.
If I preview the German section in edit mode, everything is fine. If I preview the entire page in edit mode, it has the "incorrect language header" category, but that goes away if I remove
{{
de-adj noun forms of
}}
. I know the template is parsing the entry, because it gives the L3 headers it creates the IDs "Noun_2" and "Noun_3" in the HTML, instead of the default "Noun_1" and "Noun_2", so I suspect it's the one adding the "incorrect language header" category. I suppose, though, that it might be just generating something that's faking out the normal wikitext-parsing done by one of the regular headword templates.
I'm out of my depth here, so I have no idea what's actually causing this, or why it only started after the L2 sections were switched. The automated detection of incorrect language headers is very useful for quickly finding out about language-code and formattting errors that people are making all the time, so it would be nice to get this fixed. I realize, though, that a bug that doesn't affect the actual content or display of the entries might not be a priority for those who
can
troubleshoot this.
Thanks!
Chuck Entz
talk
05:54, 5 March 2026 (UTC)
Reply
More data: the Noun L3 headers generated by this template have "[edit]" controls just like regular ones, but their links are for editing nonexistent sections in
Module:de-inflections
instead of for editing the named section in the page itself. Here are the html codings for a regular Noun L3 header at
Alleinerziehende
and template-generated ones at
Süchtige
(just the one section) and
Andere
(two sections):
Alleinerziehende

Süchtige

Andere
(1st):

Andere
(2nd):

You'll notice that all the template-generated headers are identical except for the
|section=
parameter, while the regular one has the name of the page in the
|title=
. As for the
Module:de-inflections
part, the executable part of the template consists entirely of:
{{#invoke:de-inflections|show_adj_noun_forms}}
None of this explains the odd behavior I mentioned above. A closer look at the module seems to indicate that it works by assembling the wikitext for the headers and the templates, and then transcluding it into the entry page, but I still haven't figured out exactly how that plays out in any given entry.
Chuck Entz
talk
08:19, 6 March 2026 (UTC)
Reply
Polytonic Greek
edit
Latest comment:
25 days ago
5 comments
2 people in discussion
At present, this wiki contains very few polytonic spellings of monotonic Greek words. I've slowly added a few, but there will come a problem with many polytonic forms of Greek nouns, verbs, and adjectives where the accent is on the ending, such as what we already have with
Ναυσικᾶ
, which calls
Template:el-n-genS
since
Template:el-nF-α-1
, which is the template called by the monotonic form,
Ναυσικά
, is designed for monotonic Greek only. While
Template:el-n-gen
and its variants seem fine to me as a short-term workaround, in the long term it'll probably be worth discussing having their own templates for these. The existing templates work fine as far as I know when the accent falls on the stem; see, for example,
ἀναγνώριση
With adjectives and especially verbs, it's only going to get worse. Again, the existing templates are fine to my knowledge when the accent falls on the stem (see, for example,
ἄλλος
), but take, for example,
καλός
. The template for the declension table currently produces correct forms for monotonic Greek, but when writing polytonic Greek, the genitive forms should take the circumflex, not the acute (e.g.
καλοῦ
), and it is inappropriate to reuse the Ancient Greek templates here since Wiktionary treats that as a separate language. I am unaware of current policy for how to deal with the polytonic spellings of the genitive of adjectives like this even in the short term.
I therefore propose something like this for the affected declension and conjugation templates, if it can be done:
Add an
optional
parameter to specify whether it should show monotonic forms only, polytonic forms only, or both monotonic and polytonic forms and default to monotonic only to avoid needlessly disrupting the existing entries. We should probably also adopt and enforce a policy not to display the polytonic forms in the declension and conjugation tables unless the user knows that they will be correct—if someone naïvely adds them to a word starting with a vowel, the polytonic forms will be missing the breathing.
Create new templates to handle cases where the lemma form takes or can take a circumflex on the ending (any second-conjugation verb will suffice as an example, say
αγαπάω/αγαπώ
—this one is also a good example of what I'm talking about as regards the policy I propose above).
I'm open to discussion about these matters.
StrangerCoug
talk
22:56, 5 March 2026 (UTC)
Reply
I personally do agree with this position, as other languages at Wiktionary, Russian, for instance, also have declension, and lemma entries with pre-reform spellings. This can be done for (modern) Greek as well.
Missileboi
talk
11:19, 25 March 2026 (UTC)
Reply
A good Russian example we can emulate might be
война
. In the pre-reform spelling, note the
in the dative and prepositional singular and how several of the plural forms end in
; in the reformed spelling, the
is changed to
and the final
is deleted. (This one uses a separate declension table in the page code for the pre-reform spelling but might be easier from a technical perspective to implement.) So I agree that modern Greek can do something similar to this.
StrangerCoug
talk
22:21, 25 March 2026 (UTC)
Reply
I've now run into a problem with
ἀντίθετος
in that
Template:el-decl-adj
doesn't recognize that the entry is in polytonic and suggests forms like
πιο ἀντίθετος
instead of
πιὸ ἀντίθετος
for the comparative and
ο πιο ἀντίθετος
instead of
ὁ πιὸ ἀντίθετος
for the relative superlative. I've suppressed it for now by calling
Template:el-decl-ος-η-ο
instead, but this is another example of how the templates were coded with only monotonic Greek in mind and how we should edit them to also support polytonic. Unfortunately, I don't know how to edit Wiki templates at all.
StrangerCoug
talk
19:49, 29 March 2026 (UTC)
Reply
I only really know some basics, not much, so we really need an experienced editor. This is one of the downsides to only using monotonic Greek, it makes it harder to add polytonic later. I believe it should have been done from the start.
Missileboi
talk
20:03, 29 March 2026 (UTC)
Reply
Formatting date as yyyy-mm-dd
edit
Latest comment:
1 month ago
5 comments
2 people in discussion
I want a template to generate a link to an archive site that has dates in the URL formatted as YYYY-MM-DD, given an date argument holding any of the date formats commonly used.
October 1, 1912
www.example.com/foo/bar/1912-10-01/baz
. Is there an existing template or module call to do that?
If not, I don't want to write my own module. Will
{{
#dateformat
:March 13, 1899|ISO 8601}}
do the right thing even if the user editing or viewing the page is a Martian with preferences to match? The documentation implies date formatting wants to respect users. I want to disrespect users, who will not see the generated text. If there is no way in the parser I can require the editor to input YYYY-MM-DD dates.
Vox Sciurorum
talk
) 16:17, 6 March 2026 (UTC)
Vox Sciurorum
talk
16:17, 6 March 2026 (UTC)
Reply
Vox Sciurorum
: you can use
{{#time:Y-m-d|{{{date}}}}}
. It seems like
{{#dateformat}}
can be used too, but I'm not familiar with it. —
Sgconlaw
talk
19:18, 6 March 2026 (UTC)
Reply
#time
does the job. Thanks.
Vox Sciurorum
talk
19:37, 6 March 2026 (UTC)
Reply
Vox Sciurorum
: you're welcome. —
Sgconlaw
talk
22:44, 6 March 2026 (UTC)
Reply
D'oh. I just noticed that
{{
#dateformat
:}}
in your post above is clickable. Clicking it takes you to the MediaWiki website, where it is explained that
{{
#dateformat
:{{{date}}}|ISO 8601}}
does the job too. —
Sgconlaw
talk
22:49, 6 March 2026 (UTC)
Reply
Special:AbuseFilter/122
edit
Latest comment:
1 month ago
2 comments
2 people in discussion
The second to last sentence in
the disallow message
for this filter is meant to be "If you absolutely need to refer to this particular character, use an escape sequence, such as, for example,
Ѹ
(HTML) for Ѹ.", but instead it shows "If you absolutely need to refer to this particular character, use an escape sequence, such as, for example,
(HTML) for Ѹ.", showing the actual character where it should show the HTML entity. This is because the source code has
Ѹ
where the entity is supposed to show, causing the browser to unescape it to "Ѹ". Let's fix this by double-escaping "Ѹ" as "Ѹ" in the source code, which the browser will unescape once to "&1144;".
We could probably also remove "for example" from that sentence, because that's redundant with "such as".
TTWIDEE
talk
20:55, 6 March 2026 (UTC)
Reply
Fixed. Thanks for noticing the issue.
- -sche
(discuss)
22:00, 6 March 2026 (UTC)
Reply
Tech News: 2026-11
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
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
All wikis will be read-only
for a few minutes on Wednesday, 25 March 2026 at
15:00 UTC
. This is for the datacenter server switchover backup tests,
which happen twice a year
. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
Last week, all wikis had 2 hours of read-only time, and extended unavailability for user-scripts and gadgets. This was due to a security incident which has since been resolved. Work is ongoing to prevent re-occurrences. For current information please see the
post on the Stewards' noticeboard
translations
).
Updates for editors
Users facing multiple blocks on mobile will now see the reasons for each block separately, instead of a generic message. This helps them understand why they are blocked and what steps they can take to resolve the issue. For example, users affected for using common VPNs (such as
iCloud Private Relay
) will receive clearer guidance on what they need to do to start editing again.
[9]
Later this week,
Suggestion Mode
will become available as a beta feature within the visual editor at all Wikipedias. This feature proactively suggests various types of actions that people can consider taking to improve Wikipedia articles, and learn about related guidelines. The feature is locally configurable, and can also be locally expanded with custom Suggestions. Current settings can be seen at
Special:EditChecks
and there are
instructions for how administrators can customize
the links to point to local guidelines. The feature is connected to
Edit check
which suggests improvements while someone is writing new content. In the future, the Editing team plans to evaluate the feature's impact with newcomers through a controlled experiment.
[10]
View all 23 community-submitted tasks that were
resolved last week
. For example, the issue where the cursor became misaligned during the use of CodeMirror’s syntax highlighting, which makes wikitext and code easier to read, has now been fixed. This problem specifically affected users who defined a font rule in a custom stylesheet while creating a new topic with DiscussionTools.
[11]
Updates for technical contributors
API rate limiting update: To help ensure
fair use of infrastructure
, global API rate limits will be applied this week to requests without a compliant User-Agent that originate from outside Toolforge/WMCS and to unauthenticated requests made from web browsers. Higher limits will be applied to identified traffic in April. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see
Wikimedia APIs/Rate limits
The new GraphQL API has been released. The API was developed as a flexible alternative to select features of the Wikidata Query Service (WDQS), to improve developer experience and foster adaptability, and efficient data access. Try it out and
give feedback
. You can also
sign up for usability tests
The
PTAC Unsupported Tools Working Group
continued improvements to
Video2Commons
in February, with fixes addressing authentication errors, large-file handling, task queue visibility, and clearer upload behavior. Work is still ongoing in some areas, including changes related to deprecated server-side uploads. Read
this update
to learn more.
Detailed code updates later this week:
MediaWiki
In depth
The Article Guidance team invites experienced Wikipedia editors from selected
pilot wikis
and interested contributors from other Wikipedias to fill out this questionnaire which is available in
Arabic
Bengali
Japanese
Portuguese
Persian
, and
Turkish
. Your answers will help the team customize guidance for less experienced editors and help them learn community policies and practices while creating an article. Learn more
on the project page
Tech news
prepared by
Tech News writers
and posted by
bot
Contribute
Translate
Get help
Give feedback
Subscribe or unsubscribe
MediaWiki message delivery
18:53, 9 March 2026 (UTC)
Reply
Meaning of "Nillenkäse"
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
The German word "Nillenkäse" is also a Translations entry from the English vulgar slang word "cock cheese". Shouldn't I add it?
~2026-15318-97
talk
21:52, 10 March 2026 (UTC)
Reply
Splitting of
Module:place/locations
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
the module, with over 300 kB in size, has become somewhat daunting to manage, as the documentation also states. I noticed this issue as I wish to implement
this previous proposal of mine
. it ideally should be split into submodules by countries. pinging @
Benwing2
Juwan
🕊️
11:05, 11 March 2026 (UTC)
Reply
search by last part of word
edit
Latest comment:
1 month ago
2 comments
2 people in discussion
For a while,
Dixtosa
talk
contribs
) maintained
a tool
that allowed looking up words in a given Wiktionary category based on their ending (rather than their beginning), e.g. all terms in
Category:English terms with IPA pronunciation
(or in "English lemmas", etc) ending in "jao". This tool seems to have stopped working ("Failed to execute statement"). Is there an alternative?
- -sche
(discuss)
22:53, 11 March 2026 (UTC)
Reply
You can use normal
Special:Search/incategory:"English lemmas" intitle:/jao$/
now.
Wiktionary:Wikimedia_Tech_News/2025#:~:text=metacharacters
Fish bowl
talk
02:53, 12 March 2026 (UTC)
Reply
Request enable
text=
for Lojban
edit
Latest comment:
1 month ago
2 comments
2 people in discussion
As the sole contributor to Lojban, I request lang code
jbo
be added to
Module:etymon/data/text_allowed
TranqyPoo
✏️
01:18, 12 March 2026 (UTC)
Reply
Done
by Fen (
diff
Juwan
🕊️
13:52, 23 March 2026 (UTC)
Reply
Missing Hani ranges in
Module:scripts
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
For example, at
{{
character info
}}
is producing
Category:Unspecified script characters
, and
{{
head
|zh|hanzi}}
has
class="None headword"
For reference:
{{
bestscript
|mul|𲨯}}
{{
bestscript
|zh|𲨯}}
is "None" (live: None / None).
Theknightwho
Benwing2
Fish bowl
talk
02:51, 12 March 2026 (UTC)
Reply
Orphaned reconstruction talk pages in the Appendix talk namespace
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
See
WT:Requests for moves, mergers and splits#Orphaned reconstruction talk pages in the Appendix talk namespace
. There are some arcane technical issues involved, so I had a hard time deciding whether to post it here or there.
Chuck Entz
talk
21:36, 13 March 2026 (UTC)
Reply
Rename Philippine Sign Language to Filipino Sign Language
edit
Latest comment:
1 month ago
2 comments
2 people in discussion
I think there aren't many entries but I saw the name isn't the official/legal one. The Wiktionary name should be updated even in
Wiktionary:List of languages
ysrael214
talk
01:56, 15 March 2026 (UTC)
Reply
Support
. Barring official/legal status, "Filipino Sign Language", or "FSL", is also the more popular & common term used to name the language. —
Yivan
000
view
talk
14:09, 19 March 2026 (UTC)
Reply
possible formatting error in
{{
ja-x-inline
}}
edit
Latest comment:
1 month ago
2 comments
2 people in discussion
葵#Noun
renders with an extra apostrophe ...
kōsho'
ki
. is this intentional?
Soap
19:52, 15 March 2026 (UTC)
Reply
Soap
, not intentional, someone should fix it. The regular template
{{
ja-usex
}}
(non-inline) produces the correct output.
Anatoli T.
обсудить
вклад
00:01, 16 March 2026 (UTC)
Reply
Tech News: 2026-12
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
Latest
tech news
from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.
Translations
are available.
Updates for editors
The
⧼codemirror-beta-feature-title⧽
beta feature, also known as
CodeMirror 6
, has been used for wikitext syntax highlighting since November 2024. It will be promoted out of beta by May 2026 in order to bring improvements and new
features
to all editors who use the standard syntax highlighter. If you have any questions or concerns about promoting the feature out of beta,
please share
[12]
Some changes to local user groups are performed by stewards on Meta-Wiki and logged there only. Now, interwiki rights changes will be logged both on Meta-Wiki and the wiki of the target user to make it easier to access a full record of user's rights changes on a local wiki. Past log entries for such changes will be backfilled in the coming weeks.
[13]
On wikis using
Flagged Revisions
, the number of pending changes shown on
Special:PendingChanges
previously counted pages which were no longer pending review, because they have been removed from the system without being reviewed, e.g. due to being deleted, moved to a different namespace, or due to wiki configuration changes. The count will be correct now. On some wikis the number shown will be much smaller than before. There should be no change to the list of pages itself.
[14]
Wikifunctions composition language has been rewritten, resulting in a new version of the language. This change aims to increase service stability by reducing the orchestrator's memory consumption. This rewrite also enables substantial latency reduction, code simplification, and better abstractions, which will open the door to later feature additions. Read more about
the changes
Users can now sort search results alphabetically by page title. The update gives an additional option to finding pages more easily and quickly. Previously, results could be sorted by Edit date, Creation date, or Relevance. To use the new option, open 'Advanced Search' on the search results page and select 'Alphabetically' under 'Sorting Order'.
[15]
View all 28 community-submitted tasks that were
resolved last week
. For example, the bug that prevented UploadWizard on Wikimedia Commons from importing files from Flickr has now been fixed.
[16]
Updates for technical contributors
A new special page,
Special:LintTemplateErrors
, has been created to list transcluded pages that are flagged as containing lint errors to help users discover them easily. The list is sorted by the number of transclusions with errors. For example:
Special:LintTemplateErrors/night-mode-unaware-background-color
[17]
Users of the
⧼codemirror-beta-feature-title⧽
beta feature have been using
CodeMirror
instead of
CodeEditor
for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages, for some time now. Along with promoting CodeMirror 6 out of beta, the plan is to replace CodeEditor as the standard editor for these content models by May 2026.
Feedback or concerns are welcome
[18]
The
CodeMirror
JavaScript modules will soon be upgraded to CodeMirror 6. Leading up to the upgrade, loading the
ext.CodeMirror
or
ext.CodeMirror.lib
modules from gadgets and user scripts was deprecated in July 2025. The use of the
ext.CodeMirror.switch
hook was also deprecated in March 2025. Contributors can now make their scripts or gadgets compatible with CodeMirror 6. See the
migration guide
for more information.
[19]
The MediaWiki Interfaces team is expanding coverage of REST API module definitions to include
extension APIs
. REST API modules are groups of related endpoints that can be independently managed and versioned. Modules now exist for
GrowthExperiments
and
Wikifunctions
APIs. As we migrate extension APIs to this structure, documentation will move out of the main MediaWiki OpenAPI spec and REST Sandbox view, and will instead be accessible via module-specific options in the dropdown on the
REST Sandbox
(i.e.,
Special:RestSandbox
, available on all wiki projects).
The
Scribunto
extension provides different pieces of information about the wiki where the module is being used via the
mw.site
library. Starting last week, the library also provides a
way
of accessing the
wiki ID
that can be used to facilitate cross-wiki module maintenance.
[20]
Detailed code updates later this week:
MediaWiki
In depth
The
2026 Coolest Tool Award
celebrating outstanding community tools, is now open for nominations! Nominate your favorite tool using the
nomination survey
form by 23 March 2026. For more information on privacy and data handling, please see the
survey privacy statement
Tech news
prepared by
Tech News writers
and posted by
bot
Contribute
Translate
Get help
Give feedback
Subscribe or unsubscribe
MediaWiki message delivery
19:35, 16 March 2026 (UTC)
Reply
nolink=1 nomultiwordcat=1 for vi-proper noun
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
MuDavid
was forced to write out "|head=Đà Nẵng" for
Đà Nẵng
to avoid red links to Đà and Nẵng, and same for
Sài Gòn
. To help out MuDavid, I was going to add "|nolink=1|nomultiwordcat=1" to the vi-proper noun for
Đà Nẵng
and
Sài Gòn
pages like I do at
Lu-liang
in the en-proper noun, but on the edit preview, I got this message:
The template Template:vi-proper noun does not use the parameter(s):
nolink=1
nomultiwordcat=1
Please see Module:checkparams for help with this warning.
I think we should add nolink and maybe nomultiworcat to vi-proper noun.
--
Geographyinitiative
talk
08:35, 18 March 2026 (UTC)
Reply
Duplicate audios
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
Fenakhay
in entries with quotation marks in the title, there sometimes happens to be audios where the URL uses the HTML codepoint
'
rather than a simple quotation
example
). when the AudioBot (
User:FenaBot
) scans the page, it then adds the correcectly formatted but duplicate audio (
example
). one should run a script to remove these HTML sequences from audios and clean up the duplicates
Juwan
🕊️
13:18, 19 March 2026 (UTC)
Reply
Template:rfclarify
: remove period
edit
Latest comment:
1 month ago
3 comments
2 people in discussion
Request (consensus) to remove the period (.) from the rendered text of
{{
rfclarify
}}
. It is unaesthetic, at least for me, especially when used with comments. See for example:
ra
TranqyPoo
✏️
03:01, 20 March 2026 (UTC)
Reply
Additionally, the 2nd-to-last closing parenthesis is italicized when a comment is used.
TranqyPoo
✏️
04:41, 20 March 2026 (UTC)
Reply
TranqyPoo
It looks like a couple of absentminded errors in the edit that added the parameter for the optional comment. Fixed.
Chuck Entz
talk
06:27, 20 March 2026 (UTC)
Reply
{{
fr-conj-auto
}}
gives incorrect conjugation for
bugger
and
débugger
edit
Latest comment:
1 month ago
4 comments
3 people in discussion
The template inteprets
bugger
and
débugger
incorrectly as regular verbs in /-ʒe/ (like manger) instead of the irregular /-ge/.
This includes the pronunciation and the inflections, creating forms like *
débuggeons
, *
débuggeais
, *
débuggeai
and *
débuggeasse
instead of the correct
débuggons
débuggais
débuggai
and
débuggasse
Sayoxime
they/he
talk
08:32, 20 March 2026 (UTC)
Reply
is the table at
tagger#French
correct?
Kedymera
talk
22:55, 20 March 2026 (UTC)
Reply
The table for
tagger
is correct @
Kedymera
Sayoxime
they/he
talk
16:17, 21 March 2026 (UTC)
Reply
Fixed
Saumache
talk
17:01, 21 March 2026 (UTC)
Reply
{{
R:sk:SDK
}}
incorrect redirecting (?)
edit
Latest comment:
1 month ago
2 comments
2 people in discussion
I don't know where to put this topic and I don't know if it's happening only to me, but in case move it elsewhere.
When I click on the hyperlink of a word (like in
slovo
dínom-dánom
etc.) to the Štúr dictionary portal, it'll always redirect into a Google search link of
botnet
The link of
Dictionary portal
works normally; only when it has this and less of it after the link:
?w=[WORD]&s=exact&c=[ID]&cs=&d
, then it redirects to the said Google search-up.
Pan1blG
talk
18:10, 21 March 2026 (UTC)
Reply
Pan1blG
}: This is the correct place. The cause seems to be that the website itself is doing the redirection. With all the bots scraping websites to feed to AI, a lot of websites have tightened up their code to exclude access by other than actual site visitors. Someone will have to figure out how to link to a result without the user being mistaken for a bot. In the meanwhile, the link to the site still works, so you can copy the term into the search bar there.
Chuck Entz
talk
19:43, 21 March 2026 (UTC)
Reply
Link to a non-existent appendix amongst Hittite verb inflection templates
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
Some of the Hittite verb conjugation templates reference a non-existent
Appendix:Hittite conjugation
. We should probably remove that link or create the page in question.
Graearms
talk
00:08, 23 March 2026 (UTC)
Reply
Aliases for Tabasco Zoque (zoq)
edit
Latest comment:
1 month ago
2 comments
2 people in discussion
Currently, there are no aliases listed for
Tabasco Zoque
zoq
). Judging by
the Wikipedia article's sources
, the language is often called
Ayapaneco
or
Ayapa Zoque
. Could an admin or template editor add these to
MOD:languages/data/3/z/extra
jlwoodwa
talk
01:28, 23 March 2026 (UTC)
Reply
Done
diff
).
Juwan
🕊️
13:28, 23 March 2026 (UTC)
Reply
Wikidata item for Otomi family (oto-otm)
edit
Latest comment:
1 month ago
4 comments
2 people in discussion
The
Otomi language family
oto-otm
) does not have any Wikidata item associated with it. I think that
Otomi
(Q36355)
is the item for this family. Could an admin or template editor add it to
MOD:families/data
jlwoodwa
talk
01:48, 23 March 2026 (UTC)
Reply
there appears to be some mismatches to be fixed in the Wikidata side. the items are quite unusual:
Otomi
(Q36355)
is associated with the article "Otomi language" (
oto
), to be inserted in the module at "Otomi" (
oto-otm
Oto-Pamean
(Q1270220)
is associated with the article "Oto-Pamean", in the module as "Otomian" (
oto
which one should be taken as authoritative?
Juwan
🕊️
13:24, 23 March 2026 (UTC)
Reply
The English Wikipedia article
Otomi language
does list the code
oto
in its infobox, but both
LOC
and
SIL
say that
oto
is the Otomi
an
language family. And indeed, it's the item
Otomian
(Q130372545)
that lists the ISO 639 identifier
oto
, not
Otomi
(Q36355)
. So as I see it,
The
Oto-Pamean family
omq-otp
; currently unassociated) should be associated with
Oto-Pamean
(Q1270220)
The
Otomian family
oto
; currently associated with
Oto-Pamean
(Q1270220)
) should instead be associated with
Otomian
(Q130372545)
The
Otomi family
oto-otm
; currently unassociated) should be associated with
Otomi
(Q36355)
jlwoodwa
talk
15:51, 23 March 2026 (UTC)
Reply
Done
diff
).
Juwan
🕊️
20:47, 23 March 2026 (UTC)
Reply
Tech News: 2026-13
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
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
Wikimedia site users can now log in without a password using passkeys. This is a secure method supported by fingerprint, facial recognition, or PIN. With this change, all users who opt for passwordless login will find it easier, faster, and more secure to log in to their accounts using any device. The new passkey login option currently appears as an autofill suggestion in the username field. An additional
"Log in with passkey" button
will soon be available for users who have already registered a passkey. This update will improve security and user experience. The
screen recording
demonstrates the passwordless login process step by step.
All wikis will be read-only
for a few minutes on Wednesday, 25 March 2026 at
15:00 UTC
. This is for the datacenter server switchover backup tests,
which happen twice a year
. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.
Updates for editors
Wikimedia site users can now export their notifications older than 5 years using a
new Toolforge tool
. This will ensure that users retain their important notifications and avoid them being lost based on the planned change to delete notifications older than 5 years, as previously announced.
[21]
Wikipedia editors in Indonesian, Thai, Turkish, and Simple English now have access to Special:PersonalDashboard. This is an
early version of an experience
that introduces newer editors to patrolling workflows, making it easier for them to move from making edits to participating in more advanced moderation work on their project.
[22]
The
Special:Block
now has two minor interface changes. Administrators can now easily perform indefinite blocks through a dedicated radio button in the expiry section. Also, choosing an indefinite expiry provides a different set of common reasons to select from, which can be changed at:
MediaWiki:Ipbreason-indef-dropdown
[23]
Mobile editors
at several wikis
can now see an improved logged-out edit warning, thanks to the recent updates from the Growth team. These changes released last week are part of ongoing efforts and tests to enhance
account creation experience on mobile
and then increase participation.
[24]
View all 36 community-submitted tasks that were
resolved last week
. For example, the bug that prevented mobile web users from seeing the block information when affected by multiple blocks has been fixed. They can now see messages of all the blocks currently affecting them when they access Wikipedia.
Updates for technical contributors
Images built using Toolforge will soon get the upgraded buildpacks version, bringing support for newer language versions and other upstream improvements and fixes. If you use Toolforge Build Service, review the recent
cloud-announce email
and update your build configuration as necessary to ensure your tools are compatible.
[25]
[26]
The
API Portal
documentation wiki will shut down in June 2026. API keys created on the API Portal will continue to work normally. api.wikimedia.org endpoints will be deprecated gradually starting in July 2026. Documentation on the API Portal is moving to
mediawiki.org
. Learn more on the
project page
Detailed code updates later this week:
MediaWiki
In depth
WMDE Technical Wishes
is considering improvements to
automatically generated reference names in VisualEditor
. Please check out the
proposed solutions
and participate in the
request for comment
Tech news
prepared by
Tech News writers
and posted by
bot
Contribute
Translate
Get help
Give feedback
Subscribe or unsubscribe
MediaWiki message delivery
16:51, 23 March 2026 (UTC)
Reply
Help with update - Got warning message due to "vandalism"
edit
Latest comment:
1 month ago
3 comments
2 people in discussion
Hi there - I'm pretty much new here and wanted to update the
Naranjo
page, but I got a vandalism warning message. Naranjo is the Spanish word for orange tree, but the definition there is only for the surname Naranjo (which is after the orange tree...). How do I make the update?
RAE source here
Thank you.
Morogris
talk
02:51, 24 March 2026 (UTC)
Reply
Nevermind, I tried again and it didn't flag anything. I'll work on making a reference section but please check if I'm doing it right. Thank you.
Morogris
talk
02:56, 24 March 2026 (UTC)
Reply
Hi, I happened to spot this, and noticed that, though your work looks fine, you put it in the wrong place -- under
Naranjo#English
rather than
naranjo#Spanish
. So as per note on your Talk page, I've moved it over for you and you can carry on from there.
--Eng
in
ear
05:26, 24 March 2026 (UTC)
Reply
Template:ine-bsl-conj-pres-j-fixed - Need sources for verb endings
edit
Latest comment:
1 month ago
1 comment
1 person in discussion
Does anyone have any sources that can be used to properly fill this template? I want Balto-Slavic verb pages to have verb inflection templates, as pretty much all of them lack one. It would also be highly appreciated if someone can provide sources for other verb tenses (imperfect, aorist/preterite, etc.) and mobile accent inflection paradigms.
Missileboi
talk
09:08, 24 March 2026 (UTC)
Reply
Unused interface messages
edit
Latest comment:
29 days ago
2 comments
2 people in discussion
Please delete the following interface message, as it is no longer used:
MediaWiki:Watchdetails
See
this SRM request
and
phab:T234776
NguoiDungKhongDinhDanh
00:13, 25 March 2026 (UTC)
Reply
Done
Justin (
ko
vf
15:14, 25 March 2026 (UTC)
Reply
Edit request: Add missing script code "Hebr" to trg (Lishán Didán)
edit
Latest comment:
29 days ago
3 comments
3 people in discussion
The language data definition for
trg
(Lishán Didán) in
Module:languages/data/3/t
is currently missing its script parameter.
When I create
trg
modules, I am currently forced to use manual script overrides (
sc = require("Module:scripts").getByCode("Hebr")
) to maintain proper text rendering because the global script auto-detector fails on
trg
entries (returning
None
). This missing data in the master array is what is populating the
"Lishán Didán terms with non-redundant manual script codes"
maintenance category.
Adding
"Hebr"
as the fourth parameter in the data array will allow the auto-detector to natively recognize the script so the tracking category can clear.
The code that forces the non-redundant pages is one line of code in
Module:trg-utilities
, and I can fix it imminently if the data module will be fixed (Removing lines 8, 405 as of
this
version)
Current code:
"trg"
"Lishán Didán"
56473
"sem-nna"
Proposed code:
"trg"
"Lishán Didán"
56473
"sem-nna"
"Hebr"
Could an administrator please apply this update? Thanks.
Avasay Sayava
talk
14:52, 25 March 2026 (UTC)
Reply
There is some kind of miscommunication. When I go to
Module:trg-utilities
and I
Ctrl+F
for "56473", I get no results. —
Justin (
ko
vf
15:13, 25 March 2026 (UTC)
Reply
Done
Fenakhay
حيطي
مساهماتي
15:17, 25 March 2026 (UTC)
Reply
Edit request: Reversion of the bogus Japanese sense at
edit
Latest comment:
28 days ago
4 comments
2 people in discussion
This diff
looks suspect for three reasons: (1) it calls the left radical normally referred to as "
阜偏
" ("kozatohen") by the name "ア偏" ("ahen"), which, while not totally crazy since the origin of 「ア」 is 「阝」, is a name I have never heard of, and a web search brings up zero results, so it certainly isn't mainstream; (2) even if accurate, it lists the name of the character as its sense; and (3) it was made by an account with
a poor track record
of contributing to kanji-related entries. Unfortunately the automated filters prevent me from undoing it, labeling my edit as harmful for reason "SLO". Could a human with privileges to do so please check my reasoning and revert this linked change? Thank you!
~2026-18788-02
talk
02:36, 26 March 2026 (UTC)
Reply
~2026-18788-02
: you should already be able to do it yourself. The SLO filter is designed to stop brand new accounts that start out making lots of edits in a very short period of time: typical of vandals who are trying to do as much damage as possible before they're spotted and blocked. You were going through the IP's contributions very rapidly and undoing them one after the other, which hit the filter's rate limit. Try to space your edits out more. It won't be that long until the filter stops seeing you as a new account, after which you can go as fast as you want.
Chuck Entz
talk
04:38, 26 March 2026 (UTC)
Reply
Understood. The term "SLO" was not explained, so I did not know.
~2026-18788-02
talk
15:10, 26 March 2026 (UTC)
Reply
Abuse filter messages are always a balance between informing people editing in good faith and not giving vandals clues on how to avoid the filter. This was the best I could come up with at the time I created it.
Chuck Entz
talk
03:43, 27 March 2026 (UTC)
Reply
Edit request: Removing the fanfic on Millicent
edit
Latest comment:
29 days ago
2 comments
2 people in discussion
a user for the past week has been attempting to insert what i can only describe as their fanfiction to the
Millicent
page. this is visible in the
history
tab.
while a user before me was able to remove it, it was re-added. when i attempted to remove it, the action was flagged as "potentially harmful", as it matched the "blanking article or replacing with unwikified text" rule.
~2026-18727-44
talk
06:49, 26 March 2026 (UTC)
Reply
Done
Sockpuppets blocked, page protected. Thanks for this. —
Justin (
ko
vf
06:56, 26 March 2026 (UTC)
Reply
Swiss Cheese (slang)
edit
Latest comment:
27 days ago
2 comments
2 people in discussion
The content I had written was the slang meaning of "Swiss Cheese" as violent shooting or perforating of a person. It's legit slang, but it depicts lethal violence, which is considered abusive or unsafe content on many sites. That's why it was getting restricted when I uploaded it.
I'm essentially describing
both common slang meanings
of the term:
A person with a lot of holes in their memory or knowledge.
(The problematic one) A violent sense of shooting a person repeatedly, metaphorically “full of holes” like Swiss cheese.
The second meaning is the one that is disallowed because it depicts violence or killing.
~2026-16168-29
talk
02:48, 28 March 2026 (UTC)
Reply
~2026-16168-29
Actually, the second meaning is already present at
Swiss cheese
. The reason the filter stopped you was that we don't put parentheses in entry titles for diambiguation, like Wikipedia does. There were also some problems with your formatting that got tagged.
As for
exϲess
, that was a matter of your replacing a "c" in a link at
yappatron
with a Cyrillic letter that looks almost exactly the same, then using it later to create a bogus page (now deleted). This wasn't a mistake, contrary to what you wrote at
exϲess
, because you put that letter back when someone replaced it with the correct one. I've blocked you for a month- this time- but if you try to pull anything like that again, it will be permanent. Also, be advised that some of the admins here can see the IP address behind your temporary account, so it won't keep us from spotting you if you get a new one.
Chuck Entz
talk
06:11, 28 March 2026 (UTC)
Reply
miazma
; two declension forms – one correct, one incorrect
edit
Latest comment:
26 days ago
1 comment
1 person in discussion
I've added a word
miazma
in which its declension
{{
sk-ndecl
}}
, specifically
genitive plural
, produces 2 forms, but only one of them is correct. I've added a
{{
notice
}}
element for this mistake. I know I can use
{{
sk-decl-noun
}}
but I don't want to use it. Is there a some kind of parameter option for
{{
sk-ndecl
}}
that would
prevent any second/alternative declension form from showing
Pan1blG
talk
20:21, 28 March 2026 (UTC)
Reply
Edit request: support lang codes of Zhuang languages
edit
Latest comment:
26 days ago
1 comment
1 person in discussion
zch, zeh, zgb, zgm, zgn, zhd, zlj, zln, zlq, zqe, zyb, zyg, zyj, zyn are missing in
Module:languages/data/3/z
; zhn and zzj are already there. Although it is discussed in
Wiktionary:Language_treatment
that only the macrolanguage za is treated as a language, the language codes should still be added for use in various templates.
Code
Language
Status
zch
Central Hongshuihe Zhuang
Active
zeh
Eastern Hongshuihe Zhuang
Active
zgb
Guibei Zhuang
Active
zgm
Minz Zhuang
Active
zgn
Guibian Zhuang
Active
zhd
Dai Zhuang
Active
zhn
Nong Zhuang
Active
zlj
Liujiang Zhuang
Active
zln
Lianshan Zhuang
Active
zlq
Liuqian Zhuang
Active
zqe
Qiubei Zhuang
Active
zyb
Yongbei Zhuang
Active
zyg
Yang Zhuang
Active
zyj
Youjiang Zhuang
Active
zyn
Yongnan Zhuang
Active
zzj
Zuojiang Zhuang
Active
— Ping me
User:内存溢出的猫
plz!
📝瞄？
💬喵!
22:04, 28 March 2026 (UTC)
Reply
Tech News: 2026-14
edit
Latest comment:
24 days ago
1 comment
1 person in discussion
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 Beta version of
Abstract Wikipedia
a new Wikimedia project which is language-independent, was launched last week. The project allows communities to build Wikipedia articles in their native language, which can be readily accessed by other users in their own languages. The wiki is powered by instructions from Wikifunctions and also based on structured content from Wikidata.
Updates for editors
The Growth team is running an A/B test to evaluate a clearer, more user-friendly message that promotes account creation on wikis. Currently when logged-out mobile users begin editing, they see a jarring warning message that can feel abrupt and discouraging. This also presents temporary account editing as the default rather than encouraging account creation. The test is running on ten Wikipedias, including Arabic, French, Spanish and German.
The Wikimedia Apps team is inviting feedback on
how editing should work on the Wikipedia mobile apps
. The discussion focuses on improving how users access editing tools when they tap "Edit". This is part of a broader effort to convert readers who develop an interest in editing, to access a more user-friendly pathway to start contributing.
View all 45 community-submitted tasks that were
resolved last week
. For example, an issue where citation fetching from the large newspaper archive
Newspapers.com
was no longer working, due to a block in
Citoid
requests, has now been fixed.
[27]
Updates for technical contributors
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:25, 30 March 2026 (UTC)
Reply
Preferences on Wiktionary, not Wikipedia
edit
Latest comment:
24 days ago
2 comments
2 people in discussion
Why does Wiktionary, have their own preferences for unregistered users, but not Wikipedia?
~2026-19918-85
talk
21:15, 30 March 2026 (UTC)
Reply
Because we are a separate project.
Vininn126
talk
21:21, 30 March 2026 (UTC)
Reply
Little typo fix
edit
Latest comment:
24 days ago
2 comments
2 people in discussion
At
Wiktionary:Utilities
there is a link to
Wiktionary:Coding_conventions
(sic, with underscore). No this isn't going to be an argument about
snake case
. Like every other link it should use a space, which works perfectly fine in links. THANK YOU FOR YOUR ATTENTION TO THIS MATTER.
~2026-19770-79
talk
01:28, 31 March 2026 (UTC)
Reply
Fixed by Fenakhay; there was another underscored link (“Wiktionary:Special_pages”), which I fixed.
J3133
talk
07:55, 31 March 2026 (UTC)
Reply
Feature suggestion - all pages with suffix
edit
Latest comment:
23 days ago
3 comments
2 people in discussion
The special pages include an "all pages with prefix" search. It strikes me that an "all pages with suffix" search would be similarly useful; perhaps even more so, as words with a common suffix (to my impression) generally have a tighter semantic connection than words with a common prefix.
A broader generalisation would be "all pages with morpheme", with "all pages including substring" giving a strict superset of that.
Lavateraguy
talk
12:55, 31 March 2026 (UTC)
Reply
See for example
Category:English terms suffixed with -osis
Vininn126
talk
13:01, 31 March 2026 (UTC)
Reply
That relies on pages being placed in the appropriate categories. The same applies to the lists in pages like
-chore
Lavateraguy
talk
14:03, 31 March 2026 (UTC)
Reply
April 2026
Updating and merging "see derivation" templates
edit
Latest comment:
22 days ago
1 comment
1 person in discussion
would it be justifiable to create a single templates for "see derivation". this include
{{
prefixsee
}}
{{
suffixsee
}}
{{
circumfixsee
}}
, etc. this would possibly only warrant a
|pos=
paramter to avoid edge cases.
additional bug reporting: the dependency module
Module:collapsible category tree
doesn't properly create language-specific strings, leaving them in plaintext.
Juwan
🕊️
22:37, 1 April 2026 (UTC)
Reply
user page can't edit
edit
Latest comment:
21 days ago
2 comments
1 person in discussion
i'm the same person who made the page but on an alt account for school. original page:
User:Percyjacksonfan1239/gōnaną
I'm the person who made the page, but on an alt as I can't access the original
Liamatschool
talk
13:10, 2 April 2026 (UTC)
Reply
i was adding a descendant of the fictional term
Liamatschool
talk
13:11, 2 April 2026 (UTC)
Reply
update of autocat
edit
Latest comment:
21 days ago
1 comment
1 person in discussion
Can we add ((cat:LANG numeral prefixes)) into ((cat:LANG numerals)) and ((cat:LANG prefixes)) as in
Category:Indonesian numeral prefixes
? I would suggest also Temporal and Spatial prefixes. Merci.
Sobreira
◣◥ 〒 @「
parlez
18:15, 2 April 2026 (UTC)
Reply
contributing to userpage
edit
Latest comment:
20 days ago
4 comments
3 people in discussion
i was contributing a word to
User:Percyjacksonfan1239/gʰeh₂n-
but it blocked me from doing so. may I add the word?
the article is fictional but fun.
it was
*gʰéh₂n-os
Proto-Hellenic:
*kʰā́nos
see there for further descendants
Liamatschool1
talk
12:27, 3 April 2026 (UTC)
Reply
Liamatschool1
: As this is part of
User:Percyjacksonfan1239
's user pages, you should ask that user (or log in, if it's your account under another name).
~2026-20486-19
talk
12:29, 3 April 2026 (UTC)
Reply
it is my account. I have this account as I can't log into that account at school.
Liamatschool1
talk
12:33, 3 April 2026 (UTC)
Reply
i, the same person as that, allow @
Liamatschool1
(my school account) to edit pages in my user pages
Percyjacksonfan1239
talk
20:48, 3 April 2026 (UTC)
Reply
Action Required: Update templates/modules for electoral maps (Migrating from P1846 to P14226)
edit
Latest comment:
20 days ago
1 comment
1 person in discussion
Hello everyone,
This is a notice regarding an ongoing data migration on Wikidata that may affect your election-related templates and Lua modules (such as
Module:Itemgroup/list
).
The Change:
Currently, many templates pull electoral maps from Wikidata using the property
P1846
, combined with the qualifier
P180
Q19571328
We are migrating this data (across roughly 4,000 items) to a newly created, dedicated property:
P14226
What You Need To Do:
To ensure your templates and infoboxes do not break or lose their maps, please update your local code to fetch data from
P14226
instead of the old
P1846
P180
structure. A
list of pages
was generated using Wikimedia Global Search.
Deadline:
We are temporarily retaining the old data on
P1846
to allow for a smooth transition. However, to complete the data cleanup on Wikidata, the old
P1846
statements will be removed after
May 1, 2026
. Please update your modules and templates before this date to prevent any disruption to your wiki's election articles.
Let us know if you have any questions or need assistance with the query logic. Thank you for your help!
ZI Jony
using
MediaWiki message delivery
talk
17:09, 3 April 2026 (UTC)
Reply
fair use image upload request
edit
Latest comment:
20 days ago
2 comments
2 people in discussion
i request that the word
absolute cinema
has an low resolution image of the original image macro
, because the word was coined from this image macro and it will help the person viewing the article understand more about the word. I will absolutely get why if my request is not made.
~2026-20612-36
talk
19:25, 3 April 2026 (UTC)
Reply
Upload it to Wikipedia Commons and I might do it shortly. Otherwise give me some time.
Saumache
talk
19:58, 3 April 2026 (UTC)
Reply
Categories and etymon: conflicts between etymology ids and sense ids in Latin entries
edit
Latest comment:
19 days ago
5 comments
4 people in discussion
Saumache
~2026-19565-13
Fenakhay
Jlwoodwa
Auteuil-Passy
Increased use of the etymon template is raising some technical issues in regard to categories and ids. An example is the Latin suffix
-us
. The etymon template at
-us
has ids such as "id=second declension" but there are subsenses with separate sense ids, e.g. "agent noun", "denominative adjective", "deverbal adjective", recently added as discussed here:
User_talk:Saumache#About_splitting_Category:Latin_terms_suffixed_with_-us
The ultimate etymology of the Latin second-declension nominative singular ending is mostly the same regardless of its function (although we also have a split for the Indo-European
*-os
and
*-ós
thematic words based on part of speech, function and ablaut).
This creates an issue with the auto-categorization for entries such as
fluxipedus
: here, the etymon id "second declension" was provided, but that produces a category "Latin terms suffixed with -us (second declension)" that is incompatible with the function-based categorization scheme based on sense ids.
Solutions:
It would be possible to always make separate etymology sections for each sense, but that seems awkward.
I think one of the following approaches seems preferable in the long run:
forbid ever using separate sense ids for categorization when the different senses have the same ultimate etymology (this would mean re-collapsing
Category:Latin terms suffixed with -us (denominative adjective)
Category:Latin terms suffixed with -us (deverbal adjective)
, etc.)
some technical way of having the etymon template at pages like
fluxipedus
accept a senseid as input, but for the sake of trees and etymology text, it connects to the etymon template with the appropriate etymology id. If it isn't possible to automatically detect which senseids go with which etymology ids, I'd imagine it would be fairly simple to allow the etymon template to have a parameter defining alternative id names that get aliased to the canonical id.
Other inconsistencies in categorization that I don't know how to fix easily:
For
Category:Latin terms suffixed with -a
, there is
Category:Latin terms suffixed with -a (adverb)
Category:Latin terms suffixed with -a (adverbial)
(just duplicates, I think, but I'm not sure what has to be changed where to merge them) and
Category:Latin terms suffixed with -a (agent noun)
Category:Latin terms suffixed with -a (feminine)
Category:Latin terms suffixed with -a (nominal)
(this is probably a case where subsenses share the same etymology, although the origin of agent nouns in -a is I think somewhat obscure)
Category:Latin terms suffixed with -ia
and
Category:Latin terms suffixed with -ia (abstract noun)
are duplicatess
Category:Latin terms suffixed with -ium
and
Category:Latin terms suffixed with -ium (abstract suffix)
are duplicates
Urszag
talk
22:52, 3 April 2026 (UTC)
Reply
Isn't
having the etymon template at pages like
fluxipedus
accept a senseid as input, but for the sake of trees and etymology text, it connects to the etymon template with the appropriate etymology id
how it already works?
jlwoodwa
talk
22:57, 3 April 2026 (UTC)
Reply
I assumed not, but maybe it does. I didn't see information about it at
Template:etymon/documentation
, but when I try it out, it looks like it might accept senseids in this manner.--
Urszag
talk
23:02, 3 April 2026 (UTC)
Reply
Multiple id's seems the way to go, but that would makes things even more tedious; waiting for Fenakhay.
You can add
-is
to the list, basically all entries hosting multiple suffixes that didn't use id's are bound to be trouble.
Saumache
talk
07:52, 4 April 2026 (UTC)
Reply
It already accepts sense IDs. It determines the etymon ID for the given sense ID, and the sense ID is used for categorisation when used in
|:af
, for example. —
Fenakhay
حيطي
مساهماتي
10:24, 4 April 2026 (UTC)
Reply
Etymon on a redirect page
edit
Latest comment:
18 days ago
2 comments
2 people in discussion
In the course of my usual Sunday Todo-list cleanup, I ran into something very odd: @
Hitsuji777
has created a page in the Reconstruction namespace that has both an etymon template and a redirect:
The page is
Reconstruction:Proto-Italic/lektos
Its entire contents:
#REDIRECT [[Reconstruction:Proto-Italic/leɣō]]
{{etymon|itc-pro|:af|*leɣō|*-tos}}
This puts the page in three categories:
Category:Proto-Italic terms suffixed with *-tos
Category:Proto-Italic terms derived from the Proto-Indo-European root *legʰ-
Category:Pages using etymon with no ID
In those categories, it shows up as an italicized page-name link:
Reconstruction:Proto-Italic/lektos
Clicking on the link redirects you to
Reconstruction:Proto-Italic/leɣō
The categorization part seems completely useless. To start with, the first and third categories apply only to the redirect page, not to the only page you will see if you click on the link. The second category also has a direct link to the redirect target, so the redirect link is just clutter.
That leaves the etymology tree part. Is there anything that the etymon template does that couldn't be accomplished by feeding the right parameters to the etymon templates pointing to it? For that matter, is there any reason not to make the redirect page into a form-of entry serving as a
soft
redirect to the target? It would at least have the advantage of telling people where they're actually going.
The reason I'm bringing this here and going into this level of detail is because I don't work with the etymon templates, so I don't know how to assess this kind of thing. I can't tell the difference between a clever new way to solve a problem and just putting your clothes on backwards because you haven't tried it before. I could delete it, but I like to fix things- even things I would never use myself. Either this will provide a chance to prevent bad practices by educating people, or educate me so I know when to leave things alone. Pinging @
Fenakhay
Ioaxxere
as the ones who can make sense of it all. Thanks!
Chuck Entz
talk
00:48, 6 April 2026 (UTC)
Reply
Hello, Chuck, thanks for letting me know. I created this page when making the etymology tree for Latin
lectus
bed
, which probably derives from the past participle of Proto-Italic
*leɣō
. I was under the impression that perhaps it was possible for redirect pages to hold etymon information specific to an inflection or form while still linking to the main page of the lemma, which would've been useful here to establish
lectus
's etymology and generate better trees for it and its descendants.
I later realized that the way the etymon template works doesn't allow for this behavior and added a simple derivation from the PIE root for the
lectus
entry without establishing any intermediary PIE or Proto-Italic morphology. My intention was not to categorize redirects of random inflections of words and I had just forgotten to remove the template from it after I realized it doesn't work.
I apologize if it caused any confusion or harm and it can be removed without any problem. Thank you for bringing it to my attention!
Hitsuji777
talk
01:08, 6 April 2026 (UTC)
Reply
Accident with Hindi terms अंधभक्ती and अंधभक्ति
edit
Latest comment:
18 days ago
2 comments
2 people in discussion
Hi all, I accidentally wrote an entry for the term "अंधभक्ति" (blind devotion) with the heading as a Hindi misspelling "अंधभक्ती." I'm trying to delete the entry, but I'm getting an error message. I have already created a new definition under the correct spelling, I just need to delete the old one.
Asclepiasincarnata
talk
06:54, 6 April 2026 (UTC)
Reply
Put
{{
}}
and request.
Chihunglu83
talk
06:58, 6 April 2026 (UTC)
Reply
Just a small nitpick...
edit
Latest comment:
3 days ago
2 comments
2 people in discussion
Whenever an etymology has
mul-tax
as one of its source languages (like at
xenacanthiform
azotobacterium
, and
bird-hipped
), the description reads "from/blend of/calque of taxonomic name...." Can this be changed to "from/blend of/calque of
the
taxonomic name..."? It's more grammatically correct.
Inpacod2
talk
13:55, 6 April 2026 (UTC)
Reply
this has annoyed me for some time. pinging @
Qwertygiy
who may be interested.
Juwan
🕊️
20:49, 20 April 2026 (UTC)
Reply
Tech News: 2026-15
edit
Latest comment:
17 days ago
1 comment
1 person in discussion
Latest
tech news
from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.
Translations
are available.
Updates for editors
The
CampaignEvents extension
now includes a new group goal-setting feature, enabling organizers to set and track event goals such as the number of articles created and participating contributors in real time. Similarly, participants can work toward shared targets and see their collective impact as the event unfolds. The feature is now available on all Wikimedia wikis. Learn more in
the documentation
The new
watchlist labels
feature (announced in
Tech News 2026-07
) is now available via VisualEditor, the source editor, and the 'watchstar' (or watch link, for skins that don't have a star icon). Previously it was only possible to assign labels via
EditWatchlist
. In all three places it is a new field following the expiry field.
View all 23 community-submitted tasks that were
resolved last week
. For example, the issue where talk pages on mobile with Parsoid are unusable after empty section headers, has now been fixed.
[28]
Updates for technical contributors
The
sub-referencing feature
, which lets editors add details to an existing reference without duplicating it, will be gradually rolled out to
more wikis
later this year. Wikis using the
Reference Tooltips
gadget are encouraged to update their version (typically at
MediaWiki:Gadget-ReferenceTooltips.js
as shown
here
) to ensure compatibility. Other reference-related gadgets may also be affected.
[29]
All Wikinews editions will be closed and switched to read-only mode on 4 May 2026. Content will remain accessible, but no new edits or articles can be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions.
The
Action API
has had several formats for requested output. One of them,
format=php
, is being removed soon. Please ensure your scripts or bots use the
JSON format
. This removal should affect very few scripts and bots.
[30]
The
Special:NamespaceInfo
page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia.
[31]
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
16:19, 6 April 2026 (UTC)
Reply
Dark mode gadget
edit
Latest comment:
16 days ago
6 comments
2 people in discussion
Please could someone enable
en:Wikipedia:Dark mode (gadget)
here? (not sure if I'm meant to ask here or if I'm supposed to create + ask on
MediaWiki talk:Gadgets-definition
instead - figured there's more chance of the request being seen here)
🔥Hot
M̶̰̓e̷̜̓s̵̼̊s̸̜̃
talk
edits
13:20, 7 April 2026 (UTC)
Reply
Courtesy link:
w:en:Wikipedia:Dark mode (gadget)
. —
Justin (
ko
vf
13:40, 7 April 2026 (UTC)
Reply
Why do we need this? Isn't there dark mode as part of MediaWiki software now? —
Justin (
ko
vf
13:41, 7 April 2026 (UTC)
Reply
whoops, didn't realize the interwiki syntax was different here. Anyway, the dark mode gadget makes it possible for logged-in users to enable dark mode on all skins, not just Vector 2022.
🔥Hot
M̶̰̓e̷̜̓s̵̼̊s̸̜̃
talk
edits
14:42, 7 April 2026 (UTC)
Reply
As an interface admin, I'm disinclined to port this over because it will require a lot of tinkering with the CSS and it has a number of shortcomings, as noted on that page. Maybe a more doable solution is that you have custom CSS? Which skin do you use here? —
Justin (
ko
vf
15:03, 7 April 2026 (UTC)
Reply
I use the Vector 2010 skin (I'm used to the layout), genuinely didn't realize that custom CSS is a thing. I'll take a look into that
🔥Hot
M̶̰̓e̷̜̓s̵̼̊s̸̜̃
talk
edits
17:18, 7 April 2026 (UTC)
Reply
parameter "q=" for
template:m
(and
template:l
edit
Latest comment:
8 days ago
2 comments
2 people in discussion
When detailing the spelling in the example
Brazilian spelling
elétron
for
-ão
, out of a habit (I can't recall from where anymore) I was writing a "q=" label for
{{
}}
, when I checked for a better suited parameter, but then I discovered that 1. q= is not in the documentation but works and 2. there is no better parameter. ※
Sobreira
◣◥ 〒 @「
parlez
09:09, 9 April 2026 (UTC)
Reply
Just use
{{
}}
. --
{{
victar
talk
}}
08:58, 16 April 2026 (UTC)
Reply
Module:number list/documentation – support for additional fields
edit
Latest comment:
12 days ago
2 comments
2 people in discussion
I've added
Jéinesch
Yenish
) numerals to
Module:number list/data/lb
using the fields:
jeinesch
jeinesch2
variant
The auto-generated documentation table at
Module:number list/data/lb/documentation
only shows "Cardinal" and "Ordinal" columns, so these new fields aren't visible. Could someone familiar with
Module:number list/documentation
update it to dynamically include additional fields present in the data?
Thanks!
Emilej01
talk
02:20, 10 April 2026 (UTC)
Reply
Fixed
. You needed to use

. —
Fenakhay
حيطي
مساهماتي
03:21, 12 April 2026 (UTC)
Reply
t:IPA
edit
Latest comment:
12 days ago
1 comment
1 person in discussion
I brought this up at
the relevant template talk page
a week ago but I think there's a better chance of getting a reply by mentioning it here:
Could the template be changed so that references are displayed after the punctuation (mainly commas)? I would try myself but I don’t want to mess anything up, e.g. I don’t know how complicated this is and how it would interfere with qualifiers, etc. An example of the references coming before the punctuation is at
faightear
which goes against general practice.
Saighneánach
talk
00:26, 12 April 2026 (UTC)
Reply
disallowed from editing
fuckery
's derived terms
edit
Latest comment:
5 days ago
2 comments
2 people in discussion
I noticed
mind-fuckery
was in the list of derived terms but not its dehyphenated counterpart, but when I went to go add it, my edit got flagged as "adding one bad word and nothing else" and blocked. (to be honest, I'm worried this edit will be flagged somehow) I understand why it was flagged, that is a fair blocking criterion, but I think maybe there should be an exception to swear-related entries for their respective swear words/derived terms of them to prevent this situation from happening again because it seems to be a false positive.
~2026-22268-88
talk
07:02, 12 April 2026 (UTC)
Reply
It would probably make sense to add a page title exemption to the filter.
Codename Noreste
talk
14:00, 18 April 2026 (UTC)
Reply
Tech News: 2026-16
edit
Latest comment:
10 days ago
1 comment
1 person in discussion
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
Experienced editors are invited to
test
the
Article guidance
feature, designed to help less-experienced editors create well-structured, policy-compliant Wikipedia articles. Testing instructions are
available
. Also, after reviewing
the outlines
, please provide feedback on the
project talk page
. Based on your input, the feature will be refined and transferred to the pilot Wikipedias to translate and adapt. Check out
the video
explaining the feature.
Updates for editors
On most wikis, all autoconfirmed users can now use
Special:ChangeContentModel
page to
create new pages with custom content models
, such as mass message lists, making custom page formats more accessible. Check
Special:ListGroupRights
for the status of your wiki.
[32]
The Growth team has launched an
account creation experiment
to evaluate whether adding an account creation button to the mobile web header increases new account registrations and encourages more mobile users to contribute to the wikis. The experiment is currently live on Hindi, Indonesian, Bengali, Thai, and Hebrew Wikipedia, and targets 10% of logged-out mobile web users.
View all 30 community-submitted tasks that were
resolved last week
. For example, an issue where VisualEditor could get stuck loading on Windows devices with animations turned off, has now been fixed.
[33]
Updates for technical contributors
Starting later this week, Abuse filter editors who have the
⧼codemirror-beta-feature-title⧽
beta feature enabled will have
CodeMirror
instead of
CodeEditor
as the editor at
Special:AbuseFilter
. This is part of the broader effort to make the user experience more consistent across all editors.
[34]
[35]
Tools and bots that access the
Notifications API
action=query&meta=notifications
) will need to update their OAuth or BotPassword grants to also include access to private notifications.
[36]
Due to a library upgrade, listings on category pages may be displayed out of order starting on Monday, 20th April. A migration script will be run to correct this, and will take hours to days depending on the size of the wiki (up to a week for English Wikipedia).
[37]
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
15:19, 13 April 2026 (UTC)
Reply
Adding "Babel" template to my Wiktionary Page
edit
Latest comment:
8 days ago
2 comments
1 person in discussion
Hello, I was just trying to add
{{#Babel:en-N|zh-N|ja-1|ko-1}}
to my Wiktionary User Page. Just that one template. Is there perhaps something I'm not doing correctly with that?
Blahhmosh
talk
16:54, 15 April 2026 (UTC)
Reply
Nevermind, it is solved.
Blahhmosh
talk
16:55, 15 April 2026 (UTC)
Reply
FWOTD image link
edit
Latest comment:
8 days ago
2 comments
2 people in discussion
Currently,
{{
FWOTD
}}
uses its second parameter directly as the page for the top-left icon to link to:
[[File:Wikinews commentary.svg|55px|link={{{2|example}}}|class=skin-invert-image]]
This means that, for instance,
Wiktionary:Foreign Word of the Day/2026/May 3
, for Latin
frūmentārius
, links to the nonexistent page
frūmentārius
. Should
{{
strip diacritics
}}
and
{{
logical to physical
}}
be used for the image's link?
jlwoodwa
talk
20:00, 15 April 2026 (UTC)
Reply
Fixed
. —
Fenakhay
حيطي
مساهماتي
20:25, 15 April 2026 (UTC)
Reply
Template & Module problem
edit
Latest comment:
8 days ago
1 comment
1 person in discussion
Hello,
So I'm trying to create a Template called "Template:xug-pron" and I'm trying to implement a Module called "Module:xug-pron". Basically it's a template that generates IPA pronunciations for text written in the Kunigami Language. It's proving to be quite difficult. I'm trying to base it off "Template:ryu-pron" and "Module:ryu-pron", all from the Okinawan language.
Blahhmosh
talk
23:22, 15 April 2026 (UTC)
Reply
Alphabetization messed up in Danish categories?
edit
Latest comment:
7 days ago
1 comment
1 person in discussion
I'm pretty sure it used to work, didn't it? Now, æ/ø/å is listed under z. See, for example,
Category:da:Cakes and pastries
or
Category:da:Christianity
.__
Gamren
talk
00:08, 17 April 2026 (UTC)
Reply
Έλλοπιήων
edit
Latest comment:
6 days ago
2 comments
2 people in discussion
I need to add this unlisted adjective form of 'Ionian'
Figout
talk
17:01, 17 April 2026 (UTC)
Reply
Figout
You would need to create the page for
Ἐλλοπῐεύς
Ellopĭeús
and add a dialectal inflection table. See
-εύς
-eús
and its inflectional chart specifically for Epic Greek. Or simply list the attested dialectal forms in a "Usage notes" section.
Graearms
talk
03:12, 18 April 2026 (UTC)
Reply
Font for Ottoman Turkish
edit
Latest comment:
3 days ago
5 comments
3 people in discussion
Fay Freak
Vox Sciurorum
Samubert96
M Ali Kara
Vahagn Petrosyan
Fenakhay
I propose the removal of
.ota-Arab
from
MediaWiki:Gadget-LanguagesAndScripts.css#L-260
, which, unless I'm missing something, is currently nothing aside from preventing Ottoman Turkish text from using Noto Naskh Arabic for those who have it installed. The font "Iranian Sans", as far as I can see, does not support
, as well as many of the characters used in
lexicographic notation
, all of which are supported by Noto Naskh Arabic, which in my opinion also looks cleaner overall.
Catonif
talk
14:05, 19 April 2026 (UTC)
Reply
Support
Fenakhay
حيطي
مساهماتي
14:17, 19 April 2026 (UTC)
Reply
I do not know how to preview with this change. I do not have permission to edit MediaWiki:Gadget-LanguagesAndScripts.css. I prefer the appearance of the font used for Ottoman Turkish compared to the font used for Arabic.
Vox Sciurorum
talk
14:50, 19 April 2026 (UTC)
Reply
Vox Sciurorum
Via your browser inspector there is a way to fiddle with CSS, which is actually the only way to do it (CSS changes cannot be previewed as you may think even with the edit rights). How do
بوڭار
(current Ottoman Turkish formatting) and
بوڭار
(current Arabic formatting) appear on your end?
Catonif
talk
16:25, 19 April 2026 (UTC)
Reply
I see two different fonts. I prefer the more angular form of the current Ottoman Turkish. I was not able to figure out how to ask my browser "what font is this text rendered in?"
Vox Sciurorum
talk
20:43, 20 April 2026 (UTC)
Reply
Uncreated citations page showing up as blue link
edit
Latest comment:
4 days ago
3 comments
3 people in discussion
This is odd. On some pages like
lying flat
and
tang ping
the citations page link is blue, but when clicked on, the "Wiktionary does not yet have a citations page" message is displayed. Even more oddly, when looking at the non-existent citations page (for example, "
Citations:tang ping
"), the discussions link is displayed as blue even though it does not exist. However, when viewed from the main entry page the discussions link is red. Any idea what's wrong? Something to report using the Phabricator? —
Sgconlaw
talk
20:03, 19 April 2026 (UTC)
Reply
Sgconlaw
, as I understand it, the very existence of the Citations tab and its behavior is under our control- though not at a level that you or I understand. That's not to say there might not be an element of the MW software interfering with our own software, but that shouldn't be the first guess.
Chuck Entz
talk
20:51, 19 April 2026 (UTC)
Reply
all red for me. maybe it's been reverted. i use custom CSS but i think in this case that doesnt matter because i've never made red links blue or blue links red or anything like that.
Soap
00:44, 20 April 2026 (UTC)
Reply
the new dialect map template
edit
Latest comment:
4 days ago
2 comments
2 people in discussion
i love this new map we've been developing. i just want to ask how the module chooses the colors for the dots? is it a hash of the word? because it seems random, and it seems that some of the words have nearly the same color. it would be great if we could make the most common words have the most divergent colors, or the ones that are used together (e.g. pop/soda being nearly the same color). see
Template:dialect_map/en/soft_drink
. @
Ioaxxere
as you've done most (maybe all) of the coding for this template. Thank you.
Soap
00:38, 20 April 2026 (UTC)
Reply
Soap
: The relevant part is in the DialectMap gadget:
MediaWiki:Gadget-DialectMap.js#L-1838
. In fact I have not done any of the coding in this area.
Ioaxxere
talk
01:00, 20 April 2026 (UTC)
Reply
On use of
{{
img
}}
edit
Latest comment:
2 days ago
3 comments
3 people in discussion
noting for other editors, please avoid using the template
{{
multiple images
}}
(alias
{{
img
}}
) for only one image. the template (by its name) is designed for multiple images. using for one image is undesirable as it breaks user preferences by setting a fixed pixel value.
if you wish to update it for your account, go to: Preferences > Apperance > Files > Thumbnail size.
Juwan
🕊️
14:52, 20 April 2026 (UTC)
Reply
I agree. —
Sgconlaw
talk
04:46, 22 April 2026 (UTC)
Reply
Perhaps the template could be updated to include more features like that and renamed.
Vininn126
talk
09:21, 22 April 2026 (UTC)
Reply
Tech News: 2026-17
edit
Latest comment:
3 days ago
1 comment
1 person in discussion
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
After two years of development,
⧼codemirror-beta-feature-title⧽
, also known as
CodeMirror 6
, is to be promoted out of beta on Tuesday, April 21. It brings better code and wikitext readability, reduction in typing errors, and other
benefits
to all users of the standard syntax highlighter. A huge thank you to volunteer
Bhsd
who developed many of the new features, including
code folding
autocompletion
, and
linting
[38]
A major update to the Wikipedia app for iOS is now rolling out, redesigning the interface to align with Apple's latest "Liquid Glass" visual design.
Download the latest version
and explore the update.
Updates for editors
Reading lists
is a feature which allows readers to save articles to a list for reading later. This feature is now in beta on Arabic, French, Indonesian, Vietnamese, and Chinese Wikipedias and by default for all new accounts on all Wikipedias.
An experiment which explores extending
Page Previews to mobile web
will be launched in the week of April 20 on Arabic, English, French, Italian, Polish, and Vietnamese Wikipedias. Page Previews are pop-ups that display a thumbnail, lead paragraph, and a link to open the full article of a blue link, thereby improving content discovery. The feature is already available on desktop and in the apps.
Read more about this experiment and others
On several wikis, logged-in editors who haven't
confirmed their email addresses
can now see a banner encouraging them to do so. Having the email address confirmed allows a user to restore access to the account if they lose it.
[39]
View all 15 community-submitted tasks that were
resolved last week
. For example, an issue where editing very large wiki pages in the 2017 wikitext editor caused slow loading, preview and scrolling lag, and performance issues when selecting, cutting, or pasting content, has now been fixed.
[40]
Updates for technical contributors
As part of the promotion of
CodeMirror
from a beta feature, all users will use
CodeMirror
instead of
CodeEditor
for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages.
[41]
The
mirrors.wikimedia.org
service for Debian and Ubuntu users will sunset and stop working on May 15. The resources for the service will be replaced with new and better options. Some users may need to switch to a different server which should take about a minute.
You can read more
[42]
The
image
and
oldimage
table will be removed from
wikireplicas
. If your tools or queries access
image
or
oldimage
directly, please update them to use the
file
and
filerevision
table before 28 May.
[43]
Following the recent implementation of global API rate limits on unidentified traffic, the Wikimedia Foundation will continue efforts to ensure
fair use of infrastructure
by applying global limits to identified API traffic beginning the last week of April. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see
Wikimedia APIs/Rate limits
and
Frequently Asked Questions
The
Attribution API
is now available as a
beta
. The API fetches information for crediting Wikimedia articles and media files wherever they are used. Reference documentation is available through the REST Sandbox special page available on all Wikimedia wikis (such as the
REST sandbox on English Wikipedia
). Share your feedback on the
project talk page
There is no new MediaWiki version this week.
Tech news
prepared by
Tech News writers
and posted by
bot
Contribute
Translate
Get help
Give feedback
Subscribe or unsubscribe
MediaWiki message delivery
15:00, 20 April 2026 (UTC)
Reply
Updating the interface fonts
edit
Latest comment:
2 days ago
2 comments
2 people in discussion
seeing the
discussion above
, I would suggest the interface editors to include fallbacks with Noto in our stylesheets. see my
commons.css
for a list all supported fonts.
Juwan
🕊️
15:07, 20 April 2026 (UTC)
Reply
"Noto" is mentioned over 70 times at
MediaWiki:Gadget-LanguagesAndScripts.css
. Can you pinpoint any specific examples to make it a little easier to know what to add and where? —
Justin (
ko
vf
15:25, 21 April 2026 (UTC)
Reply
Changing
Template:letter
to work in the Appendix namespace
edit
Latest comment:
3 days ago
1 comment
1 person in discussion
Currently,
Template:letter
always links to the main namespace, even when invoked in an appendix. I propose that if the template is invoked in an appendix, the links stay within the appendix.
Netizen3102
talk
02:45, 21 April 2026 (UTC)
Reply
Deletion of
{{
R:pl:PWN Encyclopedia
}}
edit
Latest comment:
2 days ago
5 comments
3 people in discussion
The service has been taken down it seems and I'm not sure when it's coming back up, so as of now instances of this template give essentially a bunch of deadlinks. Can we bot remove instances of this template and then delete it?
Vininn126
talk
07:54, 21 April 2026 (UTC)
Reply
Is that better than an archive link? —
Justin (
ko
vf
15:22, 21 April 2026 (UTC)
Reply
That's what's been done with
{{
R:pl:NFJP
}}
, but the problem is the website was only somewhat archived, and I'm not even sure if it was archived on websites we allow, so you end up with very patchy archiving.
Vininn126
talk
15:25, 21 April 2026 (UTC)
Reply
Vininn126
: if the reference template is widely used, I was going to suggest what @
Koavf
suggested, which is to replace the link with
...
. But as with similar templates like
{{
R:Lexico
}}
, editors need to check if individual webpages were archived, and remove the template when it points to those which weren't. —
Sgconlaw
talk
17:05, 21 April 2026 (UTC)
Reply
I wouldn't say widely.
Vininn126
talk
04:32, 22 April 2026 (UTC)
Reply
Jeiner
edit
Latest comment:
2 days ago
3 comments
3 people in discussion
En Jeiner kan have forskelige betydninger alt efter hvor i landet du kommer. Den mest rigtige betydning kommer dog fra landmændene. I det midtjyske ude på landet var det et meget stort kompliment at bliver kaldt en jeiner. Det betød nemlig at man både var helt utrolig pæn, meget klog og helt vildt sjov. Derfor var det kun de færreste der fik dette tilnavn. Fik man dette tilnavn var man noget helt specielt.
~2026-24687-98
talk
22:28, 21 April 2026 (UTC)
Reply
Courtesy link:
Jeiner
. —
Justin (
ko
vf
22:43, 21 April 2026 (UTC)
Reply
~2026-24687-98
. This is a English-language dictionary, not a place to write random comments in Danish. There's a reason the abuse filters won't let you write the above comment in the entry- you're basically taking a properly-formatted dictionary entry and replacing it with junk.
Chuck Entz
talk
04:41, 22 April 2026 (UTC)
Reply
Category sorting with etymon
edit
Latest comment:
1 day ago
5 comments
3 people in discussion
Prefixed terms that use
{{
etymon
}}
in their etymology sections are not being sorted correctly in their prefix category, see e.g.
hyperactivate
vs.
hyperactivated
in
Category:English terms prefixed with hyper-
. Can this be corrected?
Einstein2
talk
21:47, 22 April 2026 (UTC)
Reply
Ioaxxere
Fenakhay
Vininn126
talk
22:22, 22 April 2026 (UTC)
Reply
What’s the issue exactly? —
Fenakhay
حيطي
مساهماتي
22:45, 22 April 2026 (UTC)
Reply
Prefixed entries should be sorted by their root in prefix categories, i.e.,
hyperactivate
should have the sortkey
activate
and be placed under "A" in
Category:English terms prefixed with hyper-
. This works with
{{
af
}}
but not with
{{
etymon
}}
Einstein2
talk
23:24, 22 April 2026 (UTC)
Reply
Fixed
. —
Fenakhay
حيطي
مساهماتي
00:11, 23 April 2026 (UTC)
Reply
Help needed with
Module:ja-pron
edit
Latest comment:
13 hours ago
1 comment
1 person in discussion
Something is going sideways in how this generates the psedo-IPA indicating the pitch accent on each mora.
The entry at Japanese
又は
seems to generate correct real IPA, the second line in the
===Pronunciation===
section, but the first line is wrong.
This currently shows:
Tokyo
または
[màtáꜜ hà]
Nakadaka
– [2])
The problem is that the
hiragana here is the topic particle, which should be rendered as
wa
, not
ha
Given how this kana can be either
ha
or
wa
depending on context, and given the difficulties in getting it right consistently in code, it might be best to include some override feature, such as the
rom=
parameter included in many other Japanese templates.
Could someone have a look? Lua is outside of my skillset. ‑‑
Eiríkr Útlendi
Tala við mig
21:08, 23 April 2026 (UTC)
Reply
Retrieved from "
Categories
Wiktionary
Wiktionary-namespace discussion pages
High volume discussion pages
Hidden category:
Wiktionary pages with shortcuts
Wiktionary
Grease pit
Add topic