text:
Wiktionary:Grease pit/2020/March

Bot cleanup request
We have 120 Swedish entries using ad hoc tables from 2013. Can someone replace them with ? Ultimateria (talk) 02:25, 2 March 2020 (UTC)

Reconstruction:Frankish/wīpan
This was NOT vandalism, like the filter told me.
 * Yeah, the entry looked correctly formatted to me. However, the correct page for this content is Reconstruction:Proto-West Germanic/wīpan because Frankish has been merged into Proto-West Germanic by Votes/2020-01/Make Frankish an etymology-only variant of Proto-West Germanic. — Eru·tuon 02:57, 3 March 2020 (UTC)

Permission error trying to create page "أغروم"
Trying to create the page أغروم (Algerian Arabic for bread), I get this weird permission error:

 * You do not have permission to create this page, for the following reason:

 * The title "أﻏﺮوم" has been banned from creation. It matches the following blacklist entry: .*[\x{FB50}-\x{FDC7}\x{FE70}-\x{FEFC}].*

Seems like something went wrong with the regular expression... פֿינצטערניש (Fintsternish), she/her (talk) 12:09, 7 March 2020 (UTC)
 * You've got two different sequences of code points there, though they look identical when rendered in a font and font engine with Arabic letter joining. أﻏﺮوم is bad (it contains the Arabic Presentation Forms that are blacklisted, U+FECF ARABIC LETTER GHAIN INITIAL FORM & and U+FEAE ARABIC LETTER REH FINAL FORM &), أغروم is good (it contains U+063A ARABIC LETTER GHAIN & and U+0631 ARABIC LETTER REH &) and you can edit it without getting in trouble with the title blacklist. — Eru·tuon 16:26, 7 March 2020 (UTC)

Not enough memory
The page a, o and mi seems not to have enough memory to store the word in all languages. StrongestStrike (talk) 02:31, 11 March 2020 (UTC)
 * It's not memory for storage, but memory for programming done by templates. Unfortunately, there are too many languages with "o" and "a" and the like as a term (a has 114 of them)- we only have 50 MB for the whole page, and it can take a MB just for the headword template. It seems like at least a year that we've had these un-fixable module errors. See CAT:E for the rest of them. Chuck Entz (talk) 03:07, 11 March 2020 (UTC)
 * I've done a bit more research and left new comment on T188492. I think at this point we don't have any other choice than to have the memory limit raised. – Jberkel 22:08, 14 March 2020 (UTC)

I am an old lady
I am an old lady, who knows nothing about computers, scripts and Lua, and who does some greek edits here and at el.wiktionary, where I have been trying to unify and update some declension modules. The two Lua creators of el.wiktionary are gone for some years now. Erutuon has already helped with crucial corrections and I wouldn't wish to bother him once more -thank you Eru!!-. I can see how busy you all are but if you ever have time: I cannot make one stem (stem["3"]) work at el:Module:zz. It is a patchwork of copypastes and I am very embarassed to show it to experts. Please do not bother too much. If it is something easy, just a little tip to the right direction would be very helpufl. If it is tricky, I can always use the old modules. Thank you. ‑‑Sarri.greek ♫ | 17:41, 13 March 2020 (UTC)
 * Done, thank you! ‑‑Sarri.greek ♫ | 01:41, 21 March 2020 (UTC)

Status of “definition popups”?
Can we get Navigation Popups to show the definitions of a word, as at it:abbaside, where I, with Navigation Popups enabled, get definitions when hovering over the links Abbasidi, pittura (multiple definitions and even a picture) and sillibazione (while, incidentally, aggetivo and relativo merely show “m sing”) ? I for one would find this very helpful indeed, and I imagine I am far from alone.

There was a Grease pit discussion in April 2012 about this; it seems that back then it could be done with pretty heavy hacking. Our documentation of our version of Navigation Popups says nothing about this (or about anything, really). This would ideally just happen when Navigation Popups were enabled, and also in page previews, if they exist apart from Navigation Popups. PJTraill (talk) 19:44, 14 March 2020 (UTC)
 * It broke many years ago and nobody technically knowledgeable has gotten around to fixing it. might know how. —Μετάknowledge discuss/deeds 19:51, 14 March 2020 (UTC)
 * Thanks, maybe I shall take a look myself, as it is rather a sad state of affairs – but it would be a lot faster if someone knowledgable were to do it. PJTraill (talk) 21:23, 14 March 2020 (UTC)
 * So, the version on Wikipedia that the gadget imports has since been changed to encapsulate its variables, so that other scripts can't modify them. (Normally good practice, but since we're trying to irresponsibly mess around with things, it's inconvenient.) If one uses the old versions of the WP gadget, and then imports Connel MacKenzie's script that messes with it, then it works. Any objections to forking the old version (or a slightly modified version of the current) onto MediaWiki:Gadget-popups.js and re-adding the other script? Pinging, who removed it in 2017 after things started breaking. --Yair rand (talk) 06:18, 17 March 2020 (UTC)
 * I have no objections to anything that actually works! —Μετάknowledge discuss/deeds 23:16, 18 March 2020 (UTC)
 * +1. - -sche (discuss) 06:07, 19 March 2020 (UTC)
 * : Thanks for your action, which seems to have made this function far more useful. I am not sure when it works (not always! e.g. bathing suit but not birthday suit, which starts with Alternative forms, Etymology , Pronunciation ), but I am seeing much more relevant content than before. PJTraill (talk) 10:49, 6 April 2020 (UTC)

Lua error: not enough memory at "se" page
Apparently Lua is running out of memory on the se page (already at the Slovene inflections) which prevents me from making use of the Swedish entry. --RayZa (talk) 00:23, 15 March 2020 (UTC)
 * A very kludgy workaround is to click Edit and then Show preview for just the Swedish section, which only uses a fraction of the memory. Chuck Entz (talk) 03:19, 15 March 2020 (UTC)

A new Bulgarian reference template
Can someone make a new new Bulgarian reference template so that a parameter is passed to the end of this URL:, e.g. to look up the word :. Calling, this dictionary is more informative, IMO, than. --Anatoli T. (обсудить/вклад) 23:44, 15 March 2020 (UTC)
 * I've made one myself - . --Anatoli T. (обсудить/вклад) 06:34, 17 March 2020 (UTC)

Memory Mystification at βάρβαρος
There's nothing really remarkable about this entry: no translation table, only two language sections, and a descendants list with 14 languages. Previewing the Ancient Greek section shows 22.99 MB of memory used, while the Greek shows 8.67 MB. Commenting out both sections to leave only βαρβάρα shows 870 KB.

And yet, after I added the entry to the redlink category exclusion list to clear an out of memory error, previewing the whole entry shows 47.27 MB. Commenting out βαρβάρα at the top causes that to jump to 49.08 MB!

As I always do, I checked for changes in any of the transcluded modules, and these are the only ones with revisions in the past few days:, , and - all very boring, routine edits that don't seem to be related. The only wildcard I can see is User:Isomorphyc's inscrutable sharded data modules, but those are in most Ancient Greek entries, and I've never seen an out of memory error in an Ancient Greek entry before.

Something very strange is going on here. There's absolutely nothing to explain the 14+ MB difference between the memory usage of all the parts as previewed and that of the entry as a whole. I'm worried that this kind of thing may cause more 32MB entries to suddenly run out of memory- and we've got lots of those. Chuck Entz (talk) 03:11, 16 March 2020 (UTC)

Alternative spelling not alternative spellings
Is it possible to generate a page of all entries containing "alternative spelling of" which down use ? To be put at Todo/untemplatized alternative spellings. I'd imagine we have a few dozen. 150 tops. --Alsowalks (talk) 18:26, 16 March 2020 (UTC)

Automatic elsewhere
I remember we have a page somewhere, possibly off-site, which shows the entries which appear in the most other-language Wiktionaries but not en.wiktionary, like User:DTLHS/elsewhere but better, as it is autoupdated. Where was that list? It should appear at User talk:DTLHS/elsewhere too, so I don't forget about it. --Alsowalks (talk) 18:35, 16 March 2020 (UTC)
 * I miss you, not literally, that's actually its name. --Vriullop (talk) 07:51, 17 March 2020 (UTC)

Templates seem to generate more-or-less random tracking categories
E.g. trans-top at Orwellian. The current revision of this page has translations in a little over a dozen languages and of them, Arabic, Chinese/Mandarin, Danish, Dutch, Greek, Norwegian (Bokmål and Nynorsk), Occitan, Persian, Swedish, and Turkish are all redlinks but the only hidden categories generated by the template are Category:Mandarin redlinks and Category:Mandarin redlinks/t. Why not Category:Occitan redlinks? Is this deliberate or an oversite? If it's deliberate, what is the rationale? I have noticed similar behavior in other instances but this one caught my attention today. Thanks. —Justin ( koavf ) ❤T☮C☺M☯ 19:03, 18 March 2020 (UTC)
 * The rationale is that it's expensive and only certain languages are enabled. DTLHS (talk) 19:06, 18 March 2020 (UTC)
 * I understand it's not all that hard to turn the tracking on (or off) if one desires to work on blueing redlinks. DCDuring (talk) 19:13, 18 March 2020 (UTC)
 * I believe there's now a bot that periodically generates a list of red links. So tracking them live may no longer be needed. —Rua (mew) 19:16, 18 March 2020 (UTC)
 * Do you propose 1.) removing all these tracking categories, 2.) including all of them, or 3.) something else? Seems like if a bot makes the lists, we could easily remove the categories. —Justin ( koavf ) ❤T☮C☺M☯ 05:44, 20 March 2020 (UTC)

size of etyms
Looks like some Anglo-Norman (and Old French) mentions are in a font bigger than the rest. See reprisal or abash. Sobreira ►〓 (parlez) 21:30, 18 March 2020 (UTC)
 * In my browser the Anglo-Norman and Old French words in both etymology sections are the same size as the rest of the text. — Eru·tuon 22:14, 18 March 2020 (UTC)
 * I have the same problem for terms in many language when they use whatever underlies (also shared by many other templates). I have the problem in Firefox, but not in Chrome. What browser do you use? DCDuring (talk) 03:05, 20 March 2020 (UTC)

templates: prefix, pre
It seems that the templates prefix and pre are not categorising terms under categories of words that use that prefix. An example is, which uses in the etymology, but it doesn't place the term in Category:English words prefixed with fore-. Can someone please take a look and correct this ? Leasnam (talk) 06:44, 19 March 2020 (UTC)
 * I can't find any examples of this problem, and is categorising correctly. In any case, you should probably be using  instead. —Μετάknowledge discuss/deeds 16:40, 19 March 2020 (UTC)
 * It appears to be working now. I noticed it first at, and yes, I swapped prefix/pre for af/affix and got it working. Now I've switch it back to pre and it's working fine. Leasnam (talk) 18:45, 19 March 2020 (UTC)
 * The category reappeared after User:DTLHS reverted some edits by User:Benwing2, which somehow had removed the "prefixed with" category at . — Eru·tuon 20:21, 19 March 2020 (UTC)
 * Tracked the problem to the line . That removed the "words prefixed with fore-" category from   but   was then not used. I've restored User:Benwing2's edits but with the offending line deleted. — Eru·tuon 20:35, 19 March 2020 (UTC)

transliteration removals
Hello,

Are all those transliteration removals justified? I think that at least some of them are not, since a standardized way to transliterate do exist (for Indian scripts in particular). 176.147.224.55 14:16, 19 March 2020 (UTC)
 * Some may not be. I think was handling this. —Μετάknowledge discuss/deeds 16:41, 19 March 2020 (UTC)
 * Yuck. This guy has reappeared after we went through and cleaned up his previous changes. I can write a script to blanket revert all his changes, but the problem historically has been that he mixes good changes with bad ones. We need someone who knows the languages in question to review some of the changes and let us know if they all need to be reverted. Benwing2 (talk) 04:04, 20 March 2020 (UTC)
 * The good changes I see are unnecessary, so I think a blanket revert is the way to go. —Μετάknowledge discuss/deeds 04:17, 20 March 2020 (UTC)

 * Are all those transliteration removals justified? It depends. I support removal of Burmese translations. The current standard is MLCTS but there could be whatever. There are very few cases where the manual is justified, if the spelling is abnormal, as with . Perhaps such cases where manual transliteration is required (even if an automated exists) for certain languages should be marked in comments. For Indic languages, like any Dravidian no manual is required.
 * Hindi and other north Indian - should be case by case, the majority should be automated.
 * Thai and Khmer - if terms are defined and use the pronunciation templates - the automatic transliteration is more accurate. Otherwise, the manual may be justified, e.g. Khmer currently showing "chaekkouhluuvaakii" (auotomated) but should be "chaekkouslouvaakii". --Anatoli T. (обсудить/вклад) 04:28, 20 March 2020 (UTC)

 * As for the Russian transliterations, as in, the manual transliteration is required. --Anatoli T. (обсудить/вклад) 04:35, 20 March 2020 (UTC)

Reference error
Tried to cite the pronunciation I found for the page bolete and added the reference in the pronunciation section for the English entry, for some reason the URL popped up down in the Latin entry. I'm not sure how to fix this or what went wrong in the first place. Could someone let me know what to do do avoid this in the future? Thanks 2WR1 (talk) 14:23, 19 March 2020 (UTC)
 * Fixed. You need to create a References section in the English section; it won't appear magically. Take a look at the source of bolete to see what I did. Also, please don't give references as bare URLs — we have lots of reference templates to format them, in this case . —Μετάknowledge discuss/deeds 16:45, 19 March 2020 (UTC)
 * Thanks so much for the help, I'll keep it in mind for the future! 2WR1 (talk) 04:02, 25 March 2020 (UTC)

Edit of article listed under 'hīo'.
I wrote up the article 'hīo' to create an entry for the variant of the Old English word ''. At the time I did not know how to add the article to the general list of headings under 'hio'. Having figured out how to do so, I have added it under said general listing and was attempting to get rid of my now spurious and superfluous creation.
 * Deleted hīo. In future, you can just put on the page to request a deletion in uncontroversial cases like this. — Eru·tuon 20:39, 21 March 2020 (UTC)

Bot Request- frk
15 hours ago, User:Mahagaja switched the language code frk (Frankish) from a full language to an etymology-only language. He spent 7 hours fixing the resulting module errors, and I've spent about 9 hours. After all of that, there are about 200 entries in CAT:E- and there are lots more that haven't shown up yet.

I would like to request for someone with a bot to fix a subset of these that are straightforward and don't need human input.

 * To start with, change all instances of:

to:

You'll also need to add an * to the term linked to if it doesn't already have one

The same goes for the codes ca, enm, es, frm, frp, gl, it, nrf, oc, pt and wa, though the most important ones are en, fr, enm and frm.

These are all languages that cannot have either borrowed or inherited from Frankish.

 * The other part is changing frk to gmw-pro in all instances of m and l that aren't preceded by an etymology template with which they could be merged (and adding * as needed).

Since this is just for cutting the task down to size, you don't have to worry about edge cases- when in doubt, skip it.

Also see the discussion of this on Mahagaja's talk page. Chuck Entz (talk) 06:22, 23 March 2020 (UTC)
 * I'll see about doing this. Benwing2 (talk) 01:04, 24 March 2020 (UTC)
 * I take it that Old French *can* borrow from Frankish? If so I will fix up all the Old French uses of (there are a lot of them), using my quick "manually-assisted" bot process (i.e. I am checking them manually to make sure the use of  is correct). Benwing2 (talk) 01:29, 24 March 2020 (UTC)
 * Also, some guidance on ? Presumably an Old French verb cannot from a Frankish noun (e.g. Frankish *fōdar -> Old French forragier)? What about cases like Frankish *sporo -> Old French esperon, or Frankish *frumjan -> Old French fornir, or Frankish *wala + *hlaupan -> galoper, or Frankish *haifst -> Old French hastif? I assume these should use  as there is some reshaping or morphological addition going on. Benwing2 (talk) 01:40, 24 March 2020 (UTC)
 * I left Old French out of the list because I honestly don't know, and I didn't want to delay work on the obvious stuff during the time it took to find out. Chuck Entz (talk) 01:45, 24 March 2020 (UTC)
 * (edit conflict) I wonder if we should rethink the restriction that disallows etymology-only languages like 'frk' in and . Consider this, for example (from ):
 * causes an error but is a very natural use of this template with this language code. Benwing2 (talk) 01:47, 24 March 2020 (UTC)
 * BTW I reduced the number from 429 -> 276 after applying the first part of your proposed fix (except for adding * where necessary, I'll get to that next). Benwing2 (talk) 01:49, 24 March 2020 (UTC)
 * OK, I went ahead and modified, , and  to allow etymology languages and link appropriately to their non-etymology parent. Hope there are no objections to this. Benwing2 (talk) 02:46, 24 March 2020 (UTC)
 * If people agree with this, I can fix certain other templates like and variants and //etc. to work similarly. Benwing2 (talk) 02:56, 24 March 2020 (UTC)
 * I'm assuming this is temporary? —Rua (mew) 14:26, 24 March 2020 (UTC)
 * I would be hesitant about allowing etymology-only languages in translations. At the very least we I think we should modify the t backend to disallow translations in unattested languages or anything else outside of mainspace. Chuck Entz (talk) 15:00, 24 March 2020 (UTC)
 * I agree that t shouldn't accept etymology-only languages, or reconstructed languages or non-mainspace conlangs either, for that matter. —Mahāgaja · talk 15:22, 24 March 2020 (UTC)
 * I haven't touched or friends, only, ,  and . I'm not sure why we should disallow etymology-only languages for these basic linking templates; the average user won't know which languages are etymology-only and which ones aren't, and won't understand why a given etymology-only language is disallowed in these templates. We could "fix" this by issuing an error that says something like "'frk' is an etymology-only language and disallowed, please use 'gmw-pro' instead", but why bother when we can just as easily accept the etymology-only language? It also seems to me there's useful info in specifying an etymology-only language in  or , it says the term is particular to that lect. Benwing2 (talk) 01:25, 25 March 2020 (UTC)
 * Interesting idea. This adds another step to the processing of these templates, including the generation of User:Jberkel/lists/wanted (pinging User:Jberkel), but that's easy to do if you already have code that handles etymology templates like . In theory it will ease splitting etymology languages into full languages, in the rare cases when that happens: templates would not have to be updated because they would already use the etymology language code, if people use the feature. At the moment using an etymology language code has no effect on the template output, except in . — Eru·tuon 23:03, 7 April 2020 (UTC)
 * Interesting idea. This adds another step to the processing of these templates, including the generation of User:Jberkel/lists/wanted (pinging User:Jberkel), but that's easy to do if you already have code that handles etymology templates like . In theory it will ease splitting etymology languages into full languages, in the rare cases when that happens: templates would not have to be updated because they would already use the etymology language code, if people use the feature. At the moment using an etymology language code has no effect on the template output, except in . — Eru·tuon 23:03, 7 April 2020 (UTC)

is so useless
is not working as documented. terms with diacritics are linking to wrong entries. The 2nd parameter is actually gender not "The word to link to." What's the point of having all these complex modules and templates if a translation is replaced with this and it's wrong: or. Of course любо́ў and حُبّ don't exist but любоў and حب do. Take a look at love.

The regular templates: любо́ў and work as expected. --Anatoli T. (обсудить/вклад) 07:49, 23 March 2020 (UTC)
 * It is working as documented, but the point of t-simple is to reduce server load in various ways, including by not having diacritic stripping, automatic language name generation, or automatic transliteration. You type:

{{t-simple|be|любоў|alt=любо́ў|f|langname=Belarusian|tr=ljubóŭ}} And here:
 * 1 is the language code,
 * 2 is the word you want to link to, in its page name form. This should be  without the diacritic.
 * alt is the form you want to display, with diacritics
 * 3 or g is the gender
 * langname is the language name
 * tr is the transliteration
 * So it works, but it's a lot less user-friendly than t. That's the price we pay for reducing server load and thus out-of-memory errors. —Mahāgaja · talk 08:39, 23 March 2020 (UTC)

 * Thank you for the explanation. I have now moved translations at love for both noun and verb to love/translations. Not sure now if I can apply  on all translations or use the regular  and  templates. Whoever applied the, did a poor a job by breaking all interwiki links and displaying existing entries in red. --00:24, 25 March 2020 (UTC)
 * You didn’t get it. You are breaking the interwiki links yourself by not providing the page name in raw form to the template. The template is not supposed to recognize that diacritics have to be stripped, on the contrary it must not because the whole point is never to run these processes like deriving page names from spellings with diacritics because they cost computing resources. What you are right to observe however that this template is not simple for the user: it is the simple for the server. Fay Freak (talk) 00:41, 25 March 2020 (UTC)
 * What? I did get it. Adding that way wasn't my doing. If someone ran a bot or did it manually, should have considered what the result was going to be. They should write, instead of .--Anatoli T. (обсудить/вклад) 00:47, 25 March 2020 (UTC)
 * There are still some messed-up links at (Russian, Hebrew, Arabic …), so the IP in December failed the template too. Somebody might run a bot to do the following: In invocations of, check (with the typical suspect languages needing diacritics in dictionary forms) for links with diacritics and unspecified scripts, and fix or at least list the cases. There are not many pages using the template, otherwise I would suspect there are probably many IPs who do it wrongly and it would be a periodical bot job, but still by our own eyes we would not notice all and could make further wrong. Fay Freak (talk) 01:16, 25 March 2020 (UTC)
 * It's all over the place. I am fixing where I see where I can when I'm willing to. If the regular templates are so resource hungry, then maybe the should be used for new translations. A bot should be able to fix the current mess. BTW, don't jump to conclusions who breaks what next time. Hint: read the discussion carefully and check the history, like you did now. --Anatoli T. (обсудить/вклад) 01:34, 25 March 2020 (UTC)
 * I found it independently of what you wrote. So you actually may have pointed out – what you wrote is difficult to understand – that people use the template wrongly. But still the template works “as expected”, just that people do not work with it as expected. Fay Freak (talk) 01:56, 25 March 2020 (UTC)

Descendants header
At, the "Descendants" header is not visible, despite the fact that it is on the page. Can someone please look into this ? Leasnam (talk) 15:49, 23 March 2020 (UTC)
 * The problem is with, which is 's creation. —Μετάknowledge discuss/deeds 16:56, 23 March 2020 (UTC)
 * I don't immediately see the problem in the template. Does anyone else? —Rua (mew) 17:00, 23 March 2020 (UTC)
 * the css on html fixed it, for what it's worth. -- 17:13, 23 March 2020 (UTC)
 * Thanks, All ! Leasnam (talk) 01:25, 24 March 2020 (UTC)

Categories for other then japanese Hani
I think, that on en.wikt should be such categories as e. g. Category:Chinese terms spelled with 定, Category:Korean terms spelled with 定, Category:Vietnamese terms spelled with 定, Category:Cantonese terms spelled with 定, not only Category:Japanese terms spelled with 定 (I mean for all corresponding (=if exists in that language) Hani, not only 定); followed also by categories such as Category:Chinese terms spelled with 定 read as ding4/Category:Chinese terms spelled with 定 read as dìng or/and Category:Chinese terms spelled with 定 read as ㄉㄧㄥˋ. The former category should be categorized not only as is (for Japanese) but also to commom category: Category:Terms spelled with 定, gathering info about all languages, that use Hani 定. Any tips for that? Thank you. --Kusurija (talk) 17:19, 23 March 2020 (UTC)

Proto-West Germanic irregular verbs
Should templates for Proto-West Germanic irregular verbs be created? StrongestStrike (talk) 15:52, 24 March 2020 (UTC)

Something wrong with WOTD?
The yesterday/tomorrow links seem to be red links due to a doubled-up forward slash in the URLs. Equinox ◑ 19:51, 24 March 2020 (UTC)
 * Fixed. — Eru·tuon 20:49, 24 March 2020 (UTC)

Overline above large Roman numerals
Module:foreign numerals does not add an overline above large Roman numerals, showing a million as MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM... instead of $\overline{M}$. This is a problem in Module:number list/data/la for the New Latin numeral. J3133 (talk) 12:04, 25 March 2020 (UTC)
 * I'm not familiar with this convention, but I've made the module emit numbers 5000 and over with overline diacritic (U+0305) and numbers 5,000,000 and over with a double overline diacritic (U+033F). I didn't like the idea of using inline CSS, though it's used in and Wikipedia articles like 1000000, and though the overline and double overline diacritics won't join together when multiple numerals that use the same diacritic are in sequence. — Eru·tuon 05:11, 31 March 2020 (UTC)

Should categorise
At cymotrichous, and elsewhere, there is a cool Pronunciation bit, where the IPA is embedded in the audio file. It looks lovely, but doesn't categorise the entry into Category:English terms with IPA pronunciation. I'm sure a little fiddle with Template:audio-IPA or Template:audio-pron could fix that. You know what...those templates can probably be merged (along with Template:audio too, i guess) --Guiri Falso (talk) 15:21, 25 March 2020 (UTC)
 * Displaying the IPA in the caption for the audio file is a bad idea, not only because the entry isn't categorized, but also because it makes showing variant pronunciations unwieldly. I'm going to standardize that entry now. —Mahāgaja · talk 16:48, 25 March 2020 (UTC)

Yiddish verb conjugation template should allow for alternate forms
With the Yiddish verb זײַן there are two forms each for the 2nd plural and 1st/3rd plural: זענט/זײַט and זענען/זײַנען. Unfortunately Template:yi-conj doesn't seem to allow for listing alternate forms, only for overriding the standard conjugation with one form. I would appreciate if someone could change this when they have the chance. Sorry if this is the wrong place to ask. Thank you. פֿינצטערניש (Fintsternish), she/her (talk) 11:45, 30 March 2020 (UTC)

Non left-to-right writing systems in page title
Hi everyone, I’m from the French Wiktionary and I have a question regarding the writing direction in the title. We just added this Manchu word and we have a problem with the page’s title. As you can see, it is written from left to right but we want it written as in this page, that is verticaly. How did you achieve this? I already looked into the Common.js page but didn’t find anything related. Is it some kind of template? Thanks in advance Darmo117 (talk) 22:26, 30 March 2020 (UTC)
 * It's done through headword-line templates and MediaWiki:Common.css. Module:headword adds a display title (via and other headword-line templates) that applies the script class   to the header, and the common CSS file applies the rule   to that class. The display title in ᠪᡳᡨᡥᡝ (added by ) is equivalent to   so the CSS rule makes the top header display vertically. — Eru·tuon 22:44, 30 March 2020 (UTC)
 * , I was wondering: at el. we do it with el:Module:title. But in the Category they do not appear vertical. Is there a trick we can add to make them vertical in the Category without the other modules (head, etc) involved? ‑‑Sarri.greek ♫ | 07:25, 31 March 2020 (UTC)
 * Thanks a lot to both of you, I’ll look into it Darmo117 (talk) 10:29, 31 March 2020 (UTC)

New suggestion for category tree language pages
Hi! I am from Turkish Wiktionary, and recently I have adapted the view design of the language categories in a responsive way. Therefore, we now have a decent page when these categories are visited on the mobile website. You can try one by entering this page on your mobile phone: tr:Kategori:İngilizce. We could adapt the same styles here? ~ Z  ( m ) 20:52, 31 March 2020 (UTC)

Correct usage of template:wikipedia
I was considering adding a wikipedia link to https://en.wikipedia.org/wiki/Oni on the page for oni, and possibly to 鬼#Japanese. In order to figure out the correct usage of the template, I looked at the source of 山, but I only ended up confused.

The Chinese section does this which looks like this:

The Japanese section does this

which looks like this:

and also puts it in the Etymology 1 subheading, which appears to be wrong.

Why is the Chinese version subtly different? The icon is smaller and multiple languages are listed in a single box, while the other has a separate box for each. Also, in all cases except the English, the link shows up on hover as https://en.wikipedia.org/wiki/{lang}:{term}. This redirects to https://{lang}.wikipedia.org/wiki/{term}, but why doesn't the link point there to begin with? 71.168.173.2 20:54, 1 April 2020 (UTC)

 * Chinese is different because a user made a Wikipedia template tailored for inclusion of multiple Chinese lects. —Suzukaze-c◇◇ 08:27, 24 April 2020 (UTC)

title: Wiktionary:Grease pit/2020/March


text:
Wiktionary:Grease pit/2020/April

stehen
Could someone please fix the composed forms section in the conjugation template in stehen? The perfect should be ich habe gestanden resp. ich bin gestanden, the pluperfect ich hatte/war gestanden, the future II ich werde gestanden haben/sein. Thanks in advance. --Akletos (talk) 08:41, 2 April 2020 (UTC)
 * Fixed, looks like some anon edit broke it. If that's the case, it was broken for more than 4 years. :( – Jberkel 11:10, 2 April 2020 (UTC)
 * : The compounds with separable prefix don't have a zu-infinitive (aufzustehen) and there should be a space before the / in the subj II sections (ich stünde auf / ich stände auf) (The tables of the inseparable compounds don't have this issue). Could you correct those, too? --Akletos (talk) 14:22, 2 April 2020 (UTC)
 * Done, does it work as expected? – Jberkel 14:57, 2 April 2020 (UTC)
 * Works fine. Thanks a lot! --Akletos (talk) 15:06, 2 April 2020 (UTC)

Font size
Is anyone else noticing the Wiktionary font size recently varying slightly, seemingly at random, or is it something to do with my browser or local setup? Mihia (talk) 18:52, 2 April 2020 (UTC)
 * I have been wondering about my font sizes, which seem to vary oddly between scripts (e.g. Cyrillic rather small), though not within a single script, but thought that might be a consequence of using Gentium (via custom CSS). PJTraill (talk) 21:57, 2 April 2020 (UTC)
 * Just to clarify, I am talking about the same font/script appearing slightly larger or smaller, with no seeming explanation. Right now it looks slightly larger. This also happened a day or so ago, and then it went back to normal size, and now it's changed again, without me having (knowingly) done anything. Other websites seem unaffected. Mihia (talk) 22:28, 2 April 2020 (UTC)
 * Could you have accidentally zoomed in or out. I have occasionally done so in FF. DCDuring (talk) 23:20, 2 April 2020 (UTC)
 * No, I don't think so. Anyway, that would presumably affect all websites, which isn't what I see. Mihia (talk) 09:32, 3 April 2020 (UTC)

and I were discussing this yesterday. An update to the skin Vector was made which changed the base value of css, increasing it by roughly 123%. I'm not very happy about this change either. -- 19:05, 3 April 2020 (UTC)
 * Thanks, that would explain it. I suppose we'll get used to it. Mihia (talk) 00:06, 12 April 2020 (UTC)

Alphagram argument to ?
I see that has an optional parameter a for the alphagram, which appears to do nothing at all. Does anyone know why or have any plans? Somebody attempted to use it, but that was quashed. PJTraill (talk) 22:04, 2 April 2020 (UTC)
 * You can search for anagrams like this, is one use. DTLHS (talk) 22:10, 2 April 2020 (UTC)

 * Yes, ordering the letters is a conventional way to look up anagrams in certain word books (Scrabble etc.). Why is it an extra parameter though? Couldn't the code work out what the alphagram is, on its own? Equinox ◑ 22:16, 2 April 2020 (UTC)
 * Then you wouldn't be able to search for it, unless it was actually displayed on the page. It also saves on Lua memory, probably. DTLHS (talk) 22:17, 2 April 2020 (UTC)

 * Thanks, that seems a reasonable answer, though it does rely on people filling it in (¡correctly!) PJTraill (talk) 22:42, 2 April 2020 (UTC)
 * It's updated by a bot periodically. DTLHS (talk) 22:45, 2 April 2020 (UTC)

Template:ang-decl-noun-i-m
The entries for, have in their declension templates a nom-acc plural ending in -as. The template used, Template:ang-decl-noun-i-m, should be returning a plural in -e. I checked the template and see nothing wrong. Can someone please investigate what is generating the -as ending ? Leasnam (talk) 14:22, 3 April 2020 (UTC)
 * NM, there actually was something coded in the template that should not have been there. I've updated it. Leasnam (talk) 14:25, 3 April 2020 (UTC)

Template fiddle
I'd like to see how many of my audios I screwed up on, so I was thinking about putting something in Template:audio where if it produces a red link, it'll be categorised in Category:Audio screwups or something. I don't touch Modules, I still haven't learned them, sorry about that. And sorry if I make some errors, too. It is inevitable, with my amazing rate of productivity. Sometimes I clean up after myself, at times after others, at times people clean up after me, elsewhen nobody cleans up at all or other users clean up after other non-me entities. So, please make the category and give me another cleanup list to work on. --Gorgehater (talk) 18:23, 3 April 2020 (UTC)

 * FTR these show up in Category:Pages with broken file links. - -sche (discuss) 03:57, 23 April 2020 (UTC)

affix sorting error
sragionare belongs to the category Category:Italian words prefixed with s-, but it's being sorted under A instead of R. The other pages under A that don't belong appear to be in both prefix and suffix categories. Ultimateria (talk) 19:31, 3 April 2020 (UTC)
 * Yeah, currently is adding the categories  . The prefix category is taking the suffix as its sortkey. Maybe instead the sortkey should be the base if it is present, or else the suffix. — Eru·tuon 02:18, 4 April 2020 (UTC)

Module:zh-pron
Please change local hanzi = "^[⺀-⺙⺛-⻳⼀-⿕々〇〡-〩〸-〻㐀-䶵一-鿯" .. mw.ustring.char(0xF900) .. "-" .. mw.ustring.char(0xFA6D) .. mw.ustring.char(0xFA70) .. "-" .. mw.ustring.char(0xFAD9) .. "𠀀-𪛖𪜀-𫜴𫝀-𫠝𫠠-𬺡𬺰-𮯠" .. mw.ustring.char(0x2F800) .. "-" .. mw.ustring.char(0x2FA1D) .. "]$" to	local hanzi = "^[⺀-⺙⺛-⻳⼀-⿕々〇〡-〩〸-〻㐀-䶿一-鿼" .. mw.ustring.char(0xF900) .. "-" .. mw.ustring.char(0xFA6D) .. mw.ustring.char(0xFA70) .. "-" .. mw.ustring.char(0xFAD9) .. "𠀀-𪛝𪜀-𫜴𫝀-𫠝𫠠-𬺡𬺰-𮯠" .. mw.ustring.char(0x2F800) .. "-" .. mw.ustring.char(0x2FA1D) .. "𰀀-𱍊]$" to provide support for Unicode 13.0. Thanks. --沈澄心✉ 03:22, 6 April 2020 (UTC)
 * ✅. — Eru·tuon 08:34, 8 April 2020 (UTC)

IPA retraction diacritic
The of IPA is represented in Unicode as the subscript minus U+0320 (COMBINING MINUS SIGN BELOW). So, applied to a, I expect to see ̠. But in the font used, which looks like Lucida to me, it renders as, which (at least on my Mac) looks like a barbell (a vertically compressed H shape). This is utterly confusing. Would it be possible to convert this to standard underscoring as when using, resulting in ? --Lambiam 11:41, 7 April 2020 (UTC)
 * The rendering looks right to me, on Windows (both Firefox and Chrome), with no serifs on the diacritic as you describe. Rather than changing our rendering, maybe you could play with your common.css page to show IPA text in a font that works better? —Mahāgaja · talk 13:30, 7 April 2020 (UTC)
 * I don’t have a common.css page or for that matter any *.css page on Wiktionary, so this may be the default look for all Mac users. I now know what the barbell diacritic stand for, so for me personally the confusion is no longer an issue. --Lambiam 07:50, 8 April 2020 (UTC)

Module:zh-glyph/phonetic
Please change  (simplified form) to   (traditional form). Thanks. --沈澄心✉ 11:56, 8 April 2020 (UTC)
 * And also  to , thanks. --沈澄心✉ 05:45, 27 April 2020 (UTC)
 * Done. -- Huhu9001 (talk) 02:25, 2 May 2020 (UTC)

da-noun not allowing manual head=
I tried to delink the headword line at 🇨🇬, but it doesn't recognize head. Ultimateria (talk) 20:37, 9 April 2020 (UTC)
 * da-noun had base for this purpose, but that's not the standard name in headword-line templates so I've added head as an alternative. — Eru·tuon 20:47, 9 April 2020 (UTC)

Category:en:Civil parishes of England

 * I have noticed that cc/England must be used with place for civil parishes. I tried a different approach with the large number of places named, but no joy; I had to add the category manually. DonnanZ (talk) 23:28, 10 April 2020 (UTC)

DonnanZ (talk) 19:57, 27 April 2020 (UTC)
 * Apologies. I will add functionality to to include hidden holonyms. That should allow you to tag an entry with cc/England for categorization purposes but not have it display. Benwing2 (talk) 00:06, 28 April 2020 (UTC)
 * Ah, OK, it's yet to be done? I tried it with, England is displaying. DonnanZ (talk) 09:56, 28 April 2020 (UTC)
 * Civil parishes could be split into counties, although some counties, such as Greater London, may have none or very few. DonnanZ (talk) 14:24, 28 April 2020 (UTC)
 * I'll get to it today or tomorrow. It might be something like an ! at the beginning of a holonym to suppress its display. Benwing2 (talk) 15:11, 28 April 2020 (UTC)

Renaming the serial semicolon template
Currently the template for serial semicolons, akin to serial commas, is located at Template:;. Unfortunately, trying to visit the page throws a "Bad title" error, making the code of the template and its documentation difficult to view. Given that, I propose renaming the template, what it should be renamed to I am undecided on. I am not really worried that such a renaming would cause any disruption because. In addition to being unsure what the template should be renamed to, I am unsure how to rename the page. When I go to the specific version of Special:MovePage that would normally be used in the renaming of the page an "No target" error appears. The alternative that comes to mind for me is deleting the page and then pasting its content at the new destination, but I have reservations about deleting the preexisting revision history, and therefore making it difficult to attribute who has contributed to the template. Any ideas, guidance, or advice would be appreciated. —The Editor's Apprentice (talk) 19:08, 12 April 2020 (UTC)
 * I've moved with Pywikibot to, leaving a redirect. I think  should still be used because it's the more intuitive title since it's similar to . It often can't be accessed due to a known server bug, but it still can be used as a template with no problem. — Eru·tuon 19:26, 12 April 2020 (UTC)
 * Awesome! Leaving Template:; is a smart solution. A specific and consistent bug makes sense. Thanks for the assistance. —The Editor's Apprentice (talk) 22:30, 12 April 2020 (UTC)

Template:isAccelerated
Is there a technical reason the documentation for this template is on the main page, as opposed to the documentation subpage? — surjection ⟨??⟩ 13:09, 14 April 2020 (UTC)
 * I don’t see any documentation for this template, either on the main page or on its documentation subpage. In fact, this is a documentation template, so what you probably think to be its documentation is the output of the template. —Tacsipacsi (talk) 00:08, 16 April 2020 (UTC)

Escaping from italics in a "non-gloss" definition
The "non-gloss definition" template puts its argument in italics, but sometimes it would be desirable to be able to escape out the italics for certain words or elements. However, this kind of thing, which might be expected to work, actually does not:

The output remains all in italics.

Should this work? Would it be possible to make it work?

I think there are other templates with the same shortcoming, but offhand I can't remember what they are. Mihia (talk) 21:58, 14 April 2020 (UTC)
 * I think it is a product of modules ignoring the wikiformatting character " ' ' ", but it might be from CSS overriding such wikiformatting. It causes me aggravation with respect to generic and subgeneric taxonomic names, which are supposed to be in italics used in running text in a vernacular language, except when the running text is in italics when it is supposed to contrast typographically, ie, appear as non-italic characterss. Among the templates that suppress in-argument " ' ' " (but not bold " ' ' ' ") are and . I wish these worked as, , and  do. DCDuring (talk) 00:33, 15 April 2020 (UTC)
 * You can always do this:, but that's cheating and should never be used for real (it's never a good idea to write code that relies on how things currently happen to be implemented internally in someone else's code). Chuck Entz (talk) 02:20, 15 April 2020 (UTC)
 * I wonder why it would work in e.g. and not in e.g. ? Perhaps there is someone with the technical knowledge and inclination who could look at this and just do in the one what is done in the other? Mihia (talk) 19:50, 15 April 2020 (UTC)
 * encloses the text in  so   isn't involved at all and the regular way of toggling italics doesn't work. MediaWiki:Common.css applies italic formatting to the   class. I've added another rule that un-italicizes italics (  tags, generated by the   syntax) within the   class. This should fix the issue. — Eru·tuon 20:03, 15 April 2020 (UTC)
 * Does it fix it with all the templates mentioned as having the problem of all templates that use "use-with-mention"? DCDuring (talk) 20:53, 15 April 2020 (UTC)
 * No, but the same sort of rule fixes italics in and  (and other templates that use the   class). I'll have to watch for any bad side-effects though. — Eru·tuon 21:12, 15 April 2020 (UTC)
 * Aha! It now works in ! Thank you! Mihia (talk)
 * Thanks. DCDuring (talk) 14:36, 16 April 2020 (UTC)

Module:utilities
This function omits the sort key "if the final sort key ends up being identical to the page name". However, there are some cases where a sort key that is identical to the page name but differs from DEFAULTSORT is needed. Example: アイアイ. -- Huhu9001 (talk) 05:16, 15 April 2020 (UTC)
 * Good catch. If DEFAULTSORT is present and different from the page title, a sortkey identical to the page title will have an effect. Since Lua doesn't have a way to access the DEFAULTSORT value, I've made  add the sortkey even if it's identical to the page title. — Eru·tuon 05:39, 15 April 2020 (UTC)

(, the author.) displays a "republished in (Please provide a date or year)" note for the 1678 edition, which is not a republishing, but a first edition; my attempts to fix that have gotten me confused. I could use some help. grendel|khan 17:20, 15 April 2020 (UTC)
 * OK, I think I've fixed it. Thanks for highlighting the error. — SGconlaw (talk) 17:36, 15 April 2020 (UTC)
 * Ah! I didn't notice the double-pipes there; thank you for fixing that. grendel|khan 02:11, 16 April 2020 (UTC)

Belarusian animacy not passing with genders from headword parameters
Belarusian nouns are not added to Category:Belarusian inanimate nouns or Category:Belarusian animate nouns, if the full gender is given like this: with g=m-in at e.g., it only understands if the animacy is specified with a=i or a=a.

Can this be fixed? --Anatoli T. (обсудить/вклад) 12:10, 16 April 2020 (UTC)

 * Belarusian nouns, which use the method that works are added to the maintenance category Category:be-noun with a. --Anatoli T. (обсудить/вклад) 00:19, 17 April 2020 (UTC)
 * Should be fixed. Benwing2 (talk) 19:13, 3 May 2020 (UTC)
 * Thank you. More requests for fixing Belarusian are coming! --Anatoli T. (обсудить/вклад) 22:55, 3 May 2020 (UTC)

Template with two TemplateData tables
Hello, I was using the visual editor to insert instances of Template:mention and continually noticed that the visual editor did not automatically provide the field for the term mentioned. This seemed odd to me because the documentation, where TemplateData is often stored, for the template is a redirect to Template:link/documentation and when I use Template:link with the visual editor the term field, along with many others, is automatically provided. I think this is because the TemplateData for Template:mention as viewed on the template page contains two TemplateData tables, one copied over from Template:link/documentation and another which is local to Template:mention. I personally think it would make the most sense to delete the local template data for Template:mention and leave the TemplateData from Template:link/documentation predominate, this is what is done for Template:l-self and Template:m-self. Any feedback on what might be a better way to resolve the issue would be appreciated. Also, please note that I myself cannot edit Template:mention since it can only be edited by administrators and template editors. Thanks. —The Editor's Apprentice (talk) 18:44, 16 April 2020 (UTC)
 * It has been over a month at the point since my original post, so I wanted to follow and be a little more decisive: The fact the Template:link/documentation contains TemplateData suggests to me that consensus was formed that all of the link templates should have the same TemplateData. With that, my request if for someone with template editor permissions to remove the TemplateData which is stored locally at Template:mention. Thanks. —The Editor's Apprentice (talk) 19:50, 25 May 2020 (UTC)
 * I've removed the template data from because it and  use the same module function  in Module:links/templates with no separate logic. I don't know how template data works and don't use the Visual Editor myself, so please tell me whether the thing in the Visual Editor that uses template data still works after this change. — Eru·tuon 20:21, 25 May 2020 (UTC)
 * Thanks much for the quick action and response! The function that uses TemplateData still works for Template:mention and now better than previously as it works as intented, that is in the same way as Template:link. —The Editor's Apprentice (talk) 20:34, 25 May 2020 (UTC)

Can we find/categorize uses of that aren't newsgroups?
I've just recently created to point to mailing list archives. Some unknown number of quotations (example here) say "Usenet" but do not actually point to newsgroups, rather to mailing lists also archived on Google Groups. Is there a way to add a maintenance line or (preferably) a maintenance category for citations where the newsgroup parameter, for example, doesn't contain a dot? grendel|khan 19:54, 17 April 2020 (UTC)

 * does this work? —Suzukaze-c◇◇ 02:09, 26 May 2020 (UTC)

 * That's perfect; thank you! grendel|khan 02:42, 26 May 2020 (UTC)

pt accelerated feminine nouns
Is there any way I can change the output for female equivalents of Portuguese nouns to ? I see that there was a subpage for Portuguese at the accel modules, but it was deleted to use the common framework. Related languages don't even have accelerated creation of these forms though. Ultimateria (talk) 17:26, 18 April 2020 (UTC)

Formatting of nested numbered lists
Where we have grouped senses with nested numbering (using "##" syntax), the generated layout is presently like this:

 * 1. ...
 * 2. ...
 * 1. ...
 * 2. ...
 * 3. ...
 * 1. ...
 * 2. ...

How feasible would it be to change this to:

 * 1. ...
 * 2. ...
 * 2.1. ...
 * 2.2. ...
 * 3. ...
 * 3.1. ...
 * 3.2. ...

? Mihia (talk) 02:43, 19 April 2020 (UTC)
 * You can do this via CSS, using counters. Check out this StackOverflow answer for an example. - TheDaveRoss  12:09, 20 April 2020 (UTC)
 * forgot to ping. - TheDaveRoss  12:11, 20 April 2020 (UTC)
 * Thanks. Could this be applied globally, so that everyone would by default see the nested numbering? Is this feasible? Mihia (talk) 17:36, 25 April 2020 (UTC)
 * Then,, why is the first version default and not vice versa? Default is supposed to be recommended by the designer. The second version looks much more logcial and preferable to me... ‑‑Sarri.greek ♫ | 19:13, 26 April 2020 (UTC)
 * The first style is the default for numbered lists on MediaWiki. The second could be made default by updating the common.css files, though I think a broader discussion ought to take place to change such a fundamental stylistic feature of the site. I think the second is preferable as well, I would support switching to it. - TheDaveRoss  20:44, 26 April 2020 (UTC)
 * It's feasible, but it's probably a good idea to see what people think first. The style I use is decimal, lower-latin, lower-roman (top level, 1., 2., 3.; second level, a., b., c.; third level, i., ii., iii.). Not sure where I got it from. OED and and  use upper-roman, decimal, lower-latin (I., II., III.; 1., 2., 3.; a., b., c.), which would give Wiktionary an old-fashioned vibe. I'm not sure I like the decimal.decimal.decimal format because it's verbose and reminds me of academic papers... — Eru·tuon 20:57, 26 April 2020 (UTC)
 * Thanks. More comments are encouraged, in order to gauge what format people prefer. Mihia (talk) 02:14, 27 April 2020 (UTC)
 * I support 3.1, 3.2, ... style. -- Huhu9001 (talk) 02:04, 2 May 2020 (UTC)
 * I recognize this is probably seen as necro-ing a dead thread, but I thought it would be worth noting that I also support the decimal style being discussed/proposed being made the default. —The Editor's Apprentice (talk) 19:58, 25 May 2020 (UTC)

Trouble making an Okinawan conjugation table - romanization broke
I'm trying to make a conjugation table template set for Okinawan. My incomplete work so far is located at Template:ryu-conj-palatal, Template:ryu-verbconj-auto, and Template:ryu-verbconj-row, and its module backend is at Module:ryu. Currently I'm stuck with a romanization bug. As seen here, the template is currently outputting the correct kana form of the shuushikei むちゅん, but it is romanizing like junk; it coughed out "muchiュn", converting the small hiragana into a katakana instead of romanizing ちゅ = chu.

Other notes:

 * Due to how Okinawan verbs work, verb lemmas end in a stem-final mora, followed by another kana, and a moraic nasal. Some forms (such as terminal かちゅん and perfective かちゃん) require only the latter two items to be deleted, and some others (like the mizenkei-based forms) require the deletion of all three of these items to attach an ending.
 * Okinawan has more flexible syllable phonotactics than Japanese. Syllables like /t͡ɕe/ are very commonplace.
 * Okinawan has no standardized orthography. Currently I'm using a phonemic hiragana method that uses a choonpu to mark long vowels.
 * Many Okinawan verbs alternate between palatal stems and non-palatal stems.
 * I wanted to also keep the number of verb conjugation templates to a minimum, so instead of making k-, g-, t-, d-stem templates separately I made Template:ryu-conj-palatal and used a bunch of switches instead.

Any help?

mellohi! (僕の乖離) 22:01, 19 April 2020 (UTC)
 * I’m not sure where the error occurs, but if むちゅん is romanized as muchiュn, that means むち and ゅん are romanized separately. — T AKASUGI Shinji (talk) 22:49, 19 April 2020 (UTC)
 * Yeah, I think that's caused by  in Template:ryu-verbconj-row. — Eru·tuon 22:52, 19 April 2020 (UTC)
 * Removed the periods, and the romanization is working properly. Cheers! mellohi! (僕の乖離) 23:17, 19 April 2020 (UTC)
 * Sorry for the late reply, seems like you guys got everything figured out! I was also attempting to do so @User:MiguelX413/sandbox. MiguelX413 (talk) 15:36, 20 April 2020 (UTC)

Webster 1913 links
I have come across a couple of cases where the links no longer work, where I get a "404 Word not Found" message; e.g. at. DonnanZ (talk) 23:04, 19 April 2020 (UTC)
 * I see that is an interesting situation, but I don't believe it is in error. Looking at a PDF of the dictionary apparently sourced from Project Gutenberg (WARNING: This file is very large (15,000+ pages), click at your own risk!) the term was in the dictionary, and is on page 1,255 of the PDF. The thing that tipped me off to why there is a problem was the fact that was a top level term under which  was listed. What seems to be the case is that the person who organized the information for websters1913.com did it based off of the top level terms, a style that sticks with how the dictionary was designed. Thus, when searching for  no entry is found. You can find the evidence for this at the bottom of websters1913.com's entry for bell, where the information on  is. I would change Template:Webster 1913 so that it would process an optional parameter allowing a target other than the page name to be set, but the template is unfortunately protected in such a way that I can not. I would suggest asking a template editor your familiar with or the person who most recently edited Template:Webster 1913 to make the necessary change. —The Editor's Apprentice (talk) 04:52, 20 April 2020 (UTC)
 * Okay, parameter 1 in can now be used to specify the Webster entry to link to (diff). — Eru·tuon 06:09, 20 April 2020 (UTC)
 * Thanks, I hope there isn't too many cases like that, they may have to be found by trial and error. DonnanZ (talk) 08:46, 20 April 2020 (UTC)

Chrome 81 - Template:he-defective spelling of links not clickable
User:Pinnerup reported that the links from were not clickable. After some testing, we figured that the problem is specific to Chrome/Chromium and that Chrome 80 is not affected, but 81 is, and I've confirmed that the latter is affected. It seems that with the current HTML structure,

  defective spelling of                     אוהל

all pointer events to the inner form-of-definition-link span are ignored, and trying to hover over the cursor over the link (even with DevTools) will only find the outer span.

Would it be possible to get rid of one of the two spans (since doing that manually fixes the link), or is this possibly a Chrome regression/bug that should be reported? Some other notes:
 * having a link inside two spans works fine, so it's something more specific than that
 * if only the HTML file (no assets) is saved, the link also works fine, so it has to be something more specific than even that

— surjection ⟨<tt>??</tt>⟩ 15:51, 21 April 2020 (UTC)

Lua error in an article
Hello everyone. Can anyone please fix the article 人? It looks horrible with so many "lua error"s. I don't know why. The error starts below Japanese section. Please fix that. Thank you. --Humberto del Torrejón (talk) 01:53, 22 April 2020 (UTC)
 * My suspicion is that there is something seriously wrong with this "lua" implementation, or parts thereof. Somewhere I think I saw mentioned that there should be 50MB of memory available. The entire source of this page is only about 63K, so on that basis it is needing 800 times the size of the entire source to process the page. That does not seem remotely right or reasonable to me. However, if there is some reasonable explanation for it then I am happy to be corrected. Mihia (talk) 00:13, 27 April 2020 (UTC)
 * And Wiktionary:Grease pit is currently 2,100 bytes. If you look at the stats, the post-expand include size is 1,077,361 bytes. There are approximately 157 modules called by the entry that fill in data, handle formatting, linking, language-specific markup, categories, etc. Without the modules there would be astronomical amounts of research and typing to do a page like this. Sure, there are inefficiencies that come from using general-purpose templates and modules that have code and data for things that aren't in the entry, but they do a lot of necessary things in millions of other entries- and only run out of memory in these 19 or so. We need to figure out how to fix this, but it's not the kind of problem you think it is. Chuck Entz (talk) 04:01, 27 April 2020 (UTC)

and linking to #English sections on external sites
Obviously these two sites are unlikely to have an "English" section to target. I don't think it was always like this but I don't see any recent changes to the templates or to Module:wikipedia. DTLHS (talk) 23:53, 22 April 2020 (UTC)
 * I'm not seeing the problem. Are you still experiencing it? Do you have any particular entry with the problem. DCDuring (talk) 06:04, 27 April 2020 (UTC)
 * All entries. For example hammerkop. DTLHS (talk) 16:11, 27 April 2020 (UTC)

Plug in look-up tool?
Hi there, I couldn't see a better place to ask: does anyone know if there are any browser plug-ins that let a user do a tool tip Wiktionary look up? eg: If not somebody should write it! But the idea seems so blindingly obvious (as in, the pages are structured to facilitate things like this) I wondered if it had already been done.
 * user specifies in preferences look up language and Wiktionary language space, eg German, en.
 * user browses page, eg https://de.wikipedia.org/wiki/Heimat_(Filmreihe)
 * user hovers over word (or indicates look up through a key combo), eg "Heimat"
 * tool pulls up "en.wiktionary.org/wiki/Heimat#German."
 * tool presents relevant definition as a hover

JimKillock (talk) 09:29, 24 April 2020 (UTC)

 * Depending on your browser, you might have built-in lookup features that you can customise, usable from the address bar. See User:Equinox/How_to_be_fast. Equinox ◑ 13:21, 24 April 2020 (UTC)
 * Looking back at how Safari works, you can do this with Wikipedia already (select / depress word, choose wikipedia from the lookup options.) I will take a look to see if that is customisable / customisable enough to get the relevant definition (it may not be) JimKillock (talk) 14:11, 24 April 2020 (UTC)
 * I think you mean Wiktionary/Look Up tool but it is not working anymore. You can try an add-on for Firefox. --Vriullop (talk) 17:19, 24 April 2020 (UTC)
 * Yes these are exactly the kind of tool I was hoping for. Shame the first isn't working. The developer of the second says he can only get the API to deliver definitions for English – this is a bit surprising, it would be handy to know if he has missed something, or else help him raise a ticket for new kinds of request to the API. JimKillock (talk) 16:43, 25 April 2020 (UTC)
 * See Wikimedia Apps/Wiktionary definition popups in the Android Wikipedia app. It was experimental only developed for English. --Vriullop (talk) 19:17, 25 April 2020 (UTC)
 * See also dictionaries.io for MacOs / Win / Kindle; this repurposes Wiktionary data in exactly this way. Seems to do the job! JimKillock (talk) 18:04, 27 April 2020 (UTC)

Confused about how poscatboiler deals with nested categories
Looking at Category:Latin words by suffix, I'm confused about why some of the nested categories, like "Latin words suffixed with -o (adverb)", appear only in the expandable/collapsible sublist under "Latin words suffixed with -o", but others, like "Latin words suffixed with -ies (adverb)", appear twice: once in the sublist for "Latin words suffixed with -ies" and once in the main, non-collapsible list. What affects the way these kinds of categories display? I assume it would be better for all of them to only appear once, in the collapsible lists.--Urszag (talk) 16:49, 24 April 2020 (UTC)
 * Actually, Category:Latin words suffixed with -o (adverb) is in Category:Latin words by suffix, but it's at the end under ō, not under o where it should be. Fixed. — Eru·tuon 18:30, 24 April 2020 (UTC)
 * Thanks. I'm not sure whether the current behavior is optimal: now all categories are showing up for me even when collapsed, and uncollapsing/expanding the blanket category displays an additional link to all of the subcategories. Shouldn't the subcategories instead be hidden when the blanket category is collapsed? At least it's consistent now, though.--Urszag (talk) 02:34, 30 April 2020 (UTC)

pictures out of place
I think we mentioned this before, recently as well. On pirksts, the picture and labels are not very useful because you can only see half the letters in the words, and they're in the wrong place. WTF? --Vitoscots (talk) 14:54, 26 April 2020 (UTC)
 * I think at some point there must have been a change to something that has systematically broken these picture labels. It could be that the coordinates originally referred to the top left of the text, but now refer to the centre of the text, or something like that. This would shift all the labels to the left. Mihia (talk) 21:04, 26 April 2020 (UTC)

Template:blend without links to the components?
I don't think e.g. Everlark and Peeniss should link to the component words, since they are fictional names that would fail WT:FICTION. Can the template support this? How? Equinox ◑ 15:41, 26 April 2020 (UTC)
 * Sure, you can do that by changing to . Or maybe the components should link to Wikipedia. — Eru·tuon 21:00, 26 April 2020 (UTC)

mul = Translingual
When language code  is used in etymology templates, it shows up as "Translingual" (capitalized as if it were a name, but it's not) and linking to Translingual language, which is a redlink. Can someone please fix these bugs? —msh210℠ (talk) 13:15, 27 April 2020 (UTC)
 * To get what you want, you need to uncapitalize the word "Translingual" in Module:languages/data3/m, and add a correct wikipedia link to Q20923490. -- Huhu9001 (talk) 15:43, 1 May 2020 (UTC)
 * I've pointed the link to Translingualism. At first I also decapitalized "Translingual", but then I reverted myself because that changed the names of all the categories pertaining to, which is a more dramatic change than I feel like making at the moment, especially since I don't have a bot to clean it up. —Mahāgaja · talk 21:54, 1 May 2020 (UTC)
 * Well in this case, you can also get to "function export.format_etyl" in mod:etymology, and insert

. This hopefully will leave the category names unchanged. -- Huhu9001 (talk) 01:34, 2 May 2020 (UTC)
 * That prospect intimidates me too., y'all have edited that module the most; is one of you willing to make the above-mentioned edit? —Mahāgaja · talk 07:40, 2 May 2020 (UTC)
 * Done. I wish it could be done with the language data module, but I don't want to work that out right now. — Eru·tuon 06:36, 3 May 2020 (UTC)

Copying templates from Wikipedia
There are a couple of templates -- https://en.wikipedia.org/wiki/Template:Clarify and https://en.wikipedia.org/wiki/Template:DISPLAYTITLE -- that I would like to have available in Wiktionary. Can I just copy and paste these and it will work, or is it more complicated than this? Mihia (talk) 17:12, 27 April 2020 (UTC)
 * Don't copy templates from Wikipedia. The primary reason for this is not technical, but out of respect for the fact that we are different wikis, and we generally have our own ways of handling things. We already have for the former purpose, and the latter is not even a template, but rather a MediaWiki magic word, so it's already available here, as you'll see if you try to use it. —Μετάknowledge discuss/deeds 17:28, 27 April 2020 (UTC)
 * OK thanks. Mihia (talk) 17:45, 27 April 2020 (UTC)
 * ... however, doesn't seem to be what I want. It says "Use this template in the definition line of a  foreign  word to request a clarification if the translation into English is ambiguous." I want something to put against an English definition of an English word, and also, ideally, to have a parameter for explaining the reason. Do you (or anyone) know of anything that would serve this purpose? Mihia (talk) 17:52, 27 April 2020 (UTC)
 * It is this template. The documentation restricts it to foreign words for no reason. Even if the claim that the template is but for foreign words is bolded and underlined (bad style on the web for something that is not a link) it still appears that people slept when making, maintaining and revamping this template and its documentation, which my mind is clear about because we made an overview of the request templates half a year ago. Fay Freak (talk) 18:04, 27 April 2020 (UTC)
 * OK thanks, I've used that. If anyone has an interest, the template could be generalised even more, e.g. to read just "clarification needed". It refers to "definition", but it needn't be a definition that needs clarifying (for example, it could be a reference). Also, ideally, there could be a parameter to explain in what way the thing needs clarifying; this could be visible by a click or mouseover. Mihia (talk) 19:41, 27 April 2020 (UTC)
 * Hmmm. It might be better to facilitate accurate categorization by having a separate template (redirect) for the most common types of requests for clarification, as well as an explicit cat= parameter. DCDuring (talk) 14:03, 30 April 2020 (UTC)

Why are history diffs suddenly in monospace font?
e.g.. Equinox ◑ 18:49, 29 April 2020 (UTC)
 * I was wondering that too. It's not only me then. —Rua (mew) 19:14, 29 April 2020 (UTC)
 * I suspect it's related to . Chuck Entz (talk) 02:18, 30 April 2020 (UTC)
 * It was announced at Wikimedia Tech News/2020. Now it uses the same font as the edit area. You can change it in your preferences. --Vriullop (talk) 06:53, 30 April 2020 (UTC)
 * Except that it messes up combining diacritics. Not good. —Rua (mew) 15:34, 30 April 2020 (UTC)
 * Ya, combining diacritics appear over the following character instead of over the expected one. I tried Noto Mono on the theory that might be better, but I get the same behavior.  Meanwhile, Consolas behaves correctly, putting the combining diacritics where they belong.  ‑‑ Eiríkr Útlendi │Tala við mig 17:10, 30 April 2020 (UTC)
 * Everson Mono treats combining diacritics better, if you feel like installing it. I have it set as the font for  and   tags, so it is used on Module, JavaScript, and CSS pages, and in the output of   tags. However, the change to the diff font has apparently been at least temporarily reverted due to another bug. — Eru·tuon 18:50, 30 April 2020 (UTC)

What's the best way to implement ?
I'm putting together to link to the 1911 Britannica. (And will be adding a template for the 1889 Ninth Edition (there is some call for quotes from Macaulay's articles, for example). However, I'm unsure of how to link to given pages, as the Internet Archive's link numbers have a variable offset, depending on the number of unnumbered illustrated-plate images included up to that point. Should I just have the template take a URL as a parameter? It seems a bit clunky to do that. grendel|khan 02:21, 30 April 2020 (UTC)
 * Link to Wikisource. --Elvinrust (talk) 02:24, 30 April 2020 (UTC)
 * If the offset varies throughout each volume, then the only rigorous (though painful) way is to work out what all the different offsets are and program the template accordingly. A lazier way is to require editors to manually specify the URL. — SGconlaw (talk) 06:28, 1 May 2020 (UTC)

Category pages missort words with Template:prefix
This was brought up in 2011 on the talk page for Template:prefix, but still hasn't been fixed. Entries using Template:prefix are currently alphabetized by the prefix on category pages, which is inconsistent with the behavior of Template:affix, which causes alphabetization by the base. As an example, see Category:Latin words prefixed with ob-, where words like obaemulor obliviscor obtrudo are listed under O when they should be listed under A, L and T respectively.--Urszag (talk) 02:43, 30 April 2020 (UTC)
 * This fixes it, I think. Now has the sortkey aemulor as desired. — Eru·tuon 08:03, 30 April 2020 (UTC)
 * Thanks for the quick fix! I assume it will just take some time for the rest of the pages in the category to update?--Urszag (talk) 08:30, 30 April 2020 (UTC)
 * Yeah. Hard to predict how long exactly. — Eru·tuon 08:42, 30 April 2020 (UTC)
 * Thanks again; now all of the entries with the prefix template look like they are sorting correctly. I just noticed that a similar issue exists with Template:confix (examples: contumax sorting on -ax in Category:Latin_words_prefixed_with_con-, bicinctus sorting on -us in Category:Latin_words_prefixed_with_bi-): would you be able to edit the module to fix that also?--Urszag (talk) 21:59, 8 May 2020 (UTC)
 * Yep. This should do it. — Eru·tuon 01:18, 9 May 2020 (UTC)

Wikidata notifications
Anyone know how to turn off notifications about Wikidata pages being linked to Commons categories? I turned off notifications here, at the Commons and at Wikidata using “Preferences” and I’m still getting the unwanted notifications. — SGconlaw (talk) 06:25, 1 May 2020 (UTC)
 * Where do you get these notifications? At the top of the page, in your Notifications notice badge 1 notice.svg notices? Or in your watchlist? Via email? Or maybe at some other place? —Tacsipacsi (talk) 18:24, 1 May 2020 (UTC)
 * Yes, in my notices at the top of my page. — SGconlaw (talk) 18:41, 1 May 2020 (UTC)
 * Can you show a screenshot of a such notification? If I’m right what kind of notification it is, it needs to be disabled on Commons, in the “Connection with Wikidata” row. —Tacsipacsi (talk) 23:29, 1 May 2020 (UTC)
 * that’s what is puzzling me. I disabled the “Connection with Wikidata” notifications not only at Commons but everywhere else (Wikidata, Wikipedia, and Wiktionary), and yet I’m still receiving them. — SGconlaw (talk) 06:43, 3 May 2020 (UTC)
 * OK, it looks like perhaps I forgot to save my change to the preferences at the Commons. I’ve now stopped receiving notifications, it seems. Thanks. — SGconlaw (talk) 04:17, 9 May 2020 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Wiktionary:Grease pit/2020/April