text:
Wiktionary:Grease pit/2021/March

Language descendant trees
Our language categories are no longer showing descendant trees. What's going on? —Mahāgaja · talk 08:42, 2 March 2021 (UTC)
 * They're back now. —Mahāgaja · talk 08:29, 6 March 2021 (UTC)

Galizionario-Style Breakdown Needed
See Talk:A. --Apisite (talk) 23:15, 3 March 2021 (UTC)

ja-usex not parsing でした.
While editing ノンバイナリー, I received an error message, 'Lua error in Module:ja-ruby at line 590: Can not match " でした.

" and " でした. "'. This occurs even when I copy and paste ' でした. ' into both the kanji and kana lines of ja-usex, so I don't think it is user error. Does anyone know what is going on? Cnilep (talk) 01:16, 5 March 2021 (UTC)
 * Perhaps I should specify: it was the second of the three instances of ja-usex on that page that caused the trouble. I put an html comment there to remind myself and others where the problem occurred, and what the example should say. Cnilep (talk) 01:19, 5 March 2021 (UTC)
 * On a lark, I tried adding an arbitrary character to the lines, and it worked. '·

でした' parses, but 'でした' does not. Obviously this is not ideal, but I've put the arbitrary character in there for the time being. Cnilep (talk) 00:49, 7 March 2021 (UTC)
 * Invisible Unicode characters were the culprit. —Suzukaze-c (talk) 03:31, 7 March 2021 (UTC)
 * I don't understand how such characters could be in the string. I copied the kanji string, pasted a duplicate, and then converted it to kana. I copied and pasted just 'でした' several times, always getting the error message on preview. Is this some issue with my IME? Or was there something after the final '%' that I was unaware of? Cnilep (talk) 11:59, 7 March 2021 (UTC)

Rhymes:German/aɪ̯bən
Something seems to broken; the page doesn't show the tool for adding new rhymes. --Akletos (talk) 13:21, 5 March 2021 (UTC)
 * I vaguely remember hearing that that tool had been disabled, though I don't remember by whom or why. —Mahāgaja · talk 08:29, 6 March 2021 (UTC)
 * Searching the Grease Pit archives for "rhyme", the most recent discussion I can find is August 2020 when Dixtosa improved it but it was apparently still working. Someone proposed switching to categories, but I didn't think that had happened yet. I don't see any recent edits to the tool, though. Maybe some Mediawiki change broke it. - -sche (discuss) 01:20, 9 March 2021 (UTC)

Different numbers of comparatives and superlatives in "en-adj"
This is a pretty pathological case, but the adjective "forward" appears to have two comparative forms yet three superlative forms. Is there any way to specify this through "en-adj"? I have tried a few things but can't get it to work. Mihia (talk) 20:54, 5 March 2021 (UTC)

"Lua error in Module:ne-conj at line 692: chunk has too many syntax levels"
The template page (but not the documentation page that it transcludes!) for ne-conj has had this error for weeks now. Could someone please fix it?

Thanks! Chuck Entz (talk) 22:43, 7 March 2021 (UTC)

RFC 1 automatically generates a link
On both Wikipedia and Wiktionary, in both Firefox and Chrome, I notice that if I write "RFC 1", "RFC 2", etc, it automatically generates a link to  etc. Is this something the Mediawiki software is doing? For me, it was unexpected and undesirable because I was writing in reference to a Wikipedia RfC. I can, of course, override it by explicitly supplying my own link or writing RfC 1 with a lowercase f, so I suppose it's not a big deal. - -sche (discuss) 01:09, 9 March 2021 (UTC)
 * These are deprecated magic links (they also occur for ISBNs and PMIDs). You can prevent them occurring by using nowiki (e.g.  turns into RFC 1, where as   or   turns into RFC 1 ). GreenComputer (talk) 15:53, 9 March 2021 (UTC)
 * Fix ping. GreenComputer (talk) 15:54, 9 March 2021 (UTC)

Error in Greek declension template: dual dative and accusative have no article
I just noticed that the inflection table at συλλαβή has no article in the dual dative and accusative, where instead of ταῖν συλλαβαῖν & τὼ συλλαβά you have just συλλαβαῖν & συλλαβά. The table is wholly produced by a template, so it is the template that includes the mistake. What do we do? MGorrone (talk) 14:39, 9 March 2021 (UTC)
 * Can this be fixed at Module:grc-decl, please? —Mahāgaja · talk 14:48, 9 March 2021 (UTC)
 * I believe I have fixed the issue with . Apparently you can't use ipairs in that way. —*i̯óh₁n̥C[5] 01:00, 10 March 2021 (UTC)

Font for Rumi spelling of Malay terms
At لوق the "lok" in "Rumi spelling lok" appears in a much larger font. The head is generated by ms. Removing  still leaves a large "lok". How should this be fixed? Vox Sciurorum (talk) 15:30, 10 March 2021 (UTC)
 * Fixed by Fenakhay. Vox Sciurorum (talk) 16:04, 10 March 2021 (UTC)

Template problems
I just noticed μένω has the same uncontracted future twice, once as "Epic, Ionic" and once as "Uncontracted", and has the contracted one marked "Contracted". I tried correcting the latter with a titleapp=, but it was ignored. Should the "Uncontracted" table be removed? And how to we mark the Contracted one as such? MGorrone (talk) 18:29, 10 March 2021 (UTC)
 * I've removed the "Epic, Ionic" table as it was identical to the uncontracted table that followed (no distinct endings for Epic/Ionic as compared to Attic in this case). The fact that the contracted future table is labeled "Uncontracted" is a known problem (see Module talk:grc-conj) and is more widespread than this entry. —Mahāgaja · talk 18:33, 10 March 2021 (UTC)
 * Eventually, if I ever revamp Module:grc-conj, I would like to get rid of the convention of having uncontracted and contracted tables, and just show the forms that are actually attested or plausible in each dialect or group of dialects. The uncontracted forms of some verbs aren't actually attested and it's misleading to have them shown in a table and linked. (In some cases people have even created entries for these forms by mistake.) In the case of, if I remember right, Attic doesn't have any uncontracted future forms, so the uncontracted future table will just be gone, and we'll need a new table for Epic and Ionic. So I restored the template but put it in a HTML comment to remind us that we will need that table in the future. — Eru·tuon 20:24, 10 March 2021 (UTC)

Module converting diacritics in links
Greetings and salutations, noob here. I would have Latin, Sardinian and Venetian links convert diacritics into plain letters, as per this discussion. What module handles this, and is there anything else I should change? Brutal Russian (talk) 19:46, 10 March 2021 (UTC)
 * Latin already strips diacritics, or are there more diacritics you'd like to strip? Sardinian is handled at Module:languages/data2 and Venetian at Module:languages/data3/v. —Mahāgaja · talk 20:32, 10 March 2021 (UTC)
 * Thank yuo. It doesn't strip acutes, graves and circumflexes of the New Latin orthography, . That deûm tho - shouldn't that page be deleted? Brutal Russian (talk) 20:55, 10 March 2021 (UTC)
 *  Category:Latin terms by their individual characters has a bunch of suspicious words. Vox Sciurorum (talk) 00:16, 11 March 2021 (UTC)

Add y and m parameters to
Compare and. J3133 (talk) 08:16, 11 March 2021 (UTC)

Publish - watch this page - permanent
When saving a page there is a choice of how long to watch it for, it defaults to "Permanent" — is there a way of setting the default to less time, say "1 month". If there is I haven't found it. — Salt  marsh. 09:58, 11 March 2021 (UTC)
 * Yes, though I never tried it. You can click on  and then a list of time periods will show up. ॥ ☼ সূর্যমান ☽ ॥ 11:19, 11 March 2021 (UTC)
 * Thanks, yes - but I would like it to be set permanently to a shorter period - ie to always save the watch list for say a month, so that older edits/creations drop off after that. I was thinking that I might have missed something - if it ain't an option it doesn't matter! — Salt  marsh . 12:45, 11 March 2021 (UTC)
 * I prefer the permanent setting - but I use it only for entries I have created - it gives me a tally for those that way. DonnanZ (talk) 14:34, 14 March 2021 (UTC)

Personal templates
Is there any way I can create my own templates in a sandbox or something? Not in the main  namespace. ॥ ☼ সূর্যমান ☽ ॥ 11:23, 11 March 2021 (UTC)
 * Never mind, I figured it out. ॥ ☼ সূর্যমান ☽ ॥ 11:59, 11 March 2021 (UTC)

Requesting new rules to ACCEL to accomodate for verb forms in
has now a bunch of verb forms which have variants (dated and colloquial) which are generated correctly in the table but not yet by accel. To take an example, almaq: all 2pl-form have two variants, with and without optional -nı-, which is expressed as alırsı(nı)z in the template. The omission of -ni- is commonplace in speech, but considered too informal for writing (although it does occur), which is why the greenlink should produce this: alırsınız, i.e. the full form with a link to the reduced form in. If it could at the same time automatically create the alternative form alırsız, it would be just lovely. Allahverdi Verdizade (talk) 22:36, 13 March 2021 (UTC)

Lepcha Transliteration Discrepancy
I noticed a discrepancy at the Lepcha transliteration module. --Apisite (talk) 06:40, 14 March 2021 (UTC)

Sicilian conjugation table
I'm a fairly new user, and trying to add a conjugation table to a Sicilian word and getting extraordinarily lost. Am I supposed to be able to add stuff into templates per page, and if so, how do I do it? Alternately, if I go about making a template for Sicilian (which I'd... rather not be the one to do) how does that work? I have all the info, I'm good at the /language/ parts, the technical parts... are killing me a little. Elliott Dunstan (talk)
 * our Sicilian verb-inflection table templates are here. I assume that scn-conj-ari is the one you want for . You can follow the template documentation for instructions on how to use it, or take a look at the verbs that already use it listed at Special:WhatLinksHere/Template:scn-conj-ari. —Mahāgaja · talk 21:36, 15 March 2021 (UTC)
 * Oh, thank you! I think I got it working. I don't know why I didn't see those when I looked, but I think the template thing overwhelmed me a lot. Much appreciated. Elliott Dunstan (talk) 15:38, 16 March 2021 (UTC)

Collapsible etymology sections?
This comes down to usability, and folding away certain longer content.

Working in Japanese entries, I've recently encountered a user who wraps etymology details in a collapsible template, currently and, out of apparent concern that the etym section is too long and visually distracting.

I can see their point of view: long etymologies could be seen as a negative for usability, for users who are not interested in this content.

However, the template enforces two columns by default, which seems inappropriate and ugly for the kinds of explanatory text blocks that are common in etymologies.

I spent some time poking around to see if there were a different template that would allow for a similar collapsible element, but without the columns. This led me to a few questions.

 * There is the generically named pair of and .  For reasons that I don't know,  was designed to specifically mimic the  template -- it has the same yellow background, two columns by default, and it has the same "Add translation" text boxes.
 * This template's What Links Here shows that it isn't transcluded much, and in at least a few cases (such as in the Tea_room/2020/December thread), it has been used as a generic collapsible element, where the yellow background, columns, and "Add translation" portions are probably not wanted.
 * Can be safely repurposed to a more generalized use case, removing the translation-related formatting and inputs?  Would doing so break anything?
 * Ideally, would produce the same general effect as, only with different default text, and only one column.
 * Ideally, would produce the same general effect as, only with different default text, and only one column.

 * Alternatively, this template could be tweaked to allow a second argument to specify the number of columns. Presumably,   would still be the default, to minimize disruption.
 * It appears that in turn uses  to plop out the CSS needed for the columns.   is already parameterized, so it's just a matter of passing in the desired number.
 * Can be safely updated to specify the number of columns?  Would doing so break anything?
 * Can be safely updated to specify the number of columns?  Would doing so break anything?

 * JavaScript:
 * The above template-based approaches would require editors to manually add the  and   templates to get the content to collapse.  This approach is thus inherently scattershot, and a lot of work to maintain.
 * Would it be possible to use a JavaScript-based approach to collapse  sections (and any others), as we already do for quotations?
 * This would presumably apply to all  sections automatically, and a user's preferences could be configured to always expand or always collapse these sections.
 * If so desired, this might even be code-able to only collapse  (or other) sections longer than X number of lines, perhaps.

Curious as to the community's thoughts. ‑‑ Eiríkr Útlendi │Tala við mig 18:30, 16 March 2021 (UTC)
 * We have . J3133 (talk) 18:36, 16 March 2021 (UTC)
 * Yes, we do. But the bright green is, IMO, ugly, and it's jarringly different from the rest of our entry infrastructure.  Somewhere along the line, I'd also gotten the impression that we are encouraged to use the   and   templates instead.  ‑‑ Eiríkr Útlendi │Tala við mig 22:51, 16 March 2021 (UTC)
 * Following in the path of the online OED, we might have a (non-visually jarring, perhaps grey) autocollapsed box, where the title of the box will automatically show the first ~ line of its contents, followed by an ellipsis. Of course, changing EL to have the etymology below the definition might really be the way to go. —Μετάknowledge discuss/deeds 00:31, 17 March 2021 (UTC)
 * @Μετάknowledge, I'm curious, how would it work to put the etym below the defs, when we're organizing the entries based on the etyms? I have trouble visualizing what that might look like for any multi-etym entry.  ‑‑ Eiríkr Útlendi │Tala við mig 00:56, 17 March 2021 (UTC)
 * We recently had a discussion about this. Form 1, Form 2, etc would replace the numbered etymology sections, and the new (unnumbered) etymology sections would be nested one level lower, below their respective form. —Μετάknowledge discuss/deeds 01:00, 17 March 2021 (UTC)
 * Interesting. The general structure is fine by me, but using headers of ,   seems to confusingly suggest that the terms have different spellings / graphemes, which is a concern.  ‑‑ Eiríkr Útlendi │Tala við mig 03:44, 17 March 2021 (UTC)
 * As long as it's clear which etymology belongs to which section, there's no reason to have the actual etymology at the top of an etymology section. We might even have a different type of header for the "Etymology" organizational structure and the etymological content.
 * Another possibility would be to have the beginning and the end of any given section visually tied together, so you can see the section as a whole- like what we do with the language sections, but repeating the pattern fractally with narrower and narrower subsections. The idea is to have a given class of content live in a specific place in each level of organization- perhaps with the more concrete and simple things first, and the more abstract/theoretical and/or verbose stuff at the bottom. Another way to look at it is treating things like the etymologies and inflection tables as footnotes to the definitions and pronunciation information. That puts the concise and practical information at the top, and the supporting details at the bottom- sort of like the principle in news writing. We might even think about making the headword line the actual head of the whole section. I'm just sort of brainstorming at the moment- it will require a lot more thought to figure out how it would work in practice. Chuck Entz (talk) 04:53, 17 March 2021 (UTC)
 * Hmm, hmm, yes, interesting. I like the idea of visually tying things together better than we currently do.
 * I'm still struggling a bit to imagine the layout. We have various oddities in different languages to contend with, things like 🇨🇬 and, or the multiple different pronunciations of 🇨🇬.  Whatever we arrive at will have to accommodate all of this somehow.  I'm looking forward to what we can come up with.  ‑‑ Eiríkr Útlendi │Tala við mig 07:59, 17 March 2021 (UTC)

 * I am in favour of collapsible etymology sections where they are excessively long, having come across some lengthy Latvian ones for example. I have experimented with collapse, but can't get it to collapse properly. When using it, it collides with any Wikipedia links and added images opposite the etymology and a yawning gap is created, which is far from desirable. DonnanZ (talk) 12:12, 24 March 2021 (UTC)

 * I recall this coming up somewhere else just recently. My concern with collapsing the content is that it is then very easy for someone to not realize it's there; even a veteran editor and admin missed the collapsed table in cat last October. (Nonetheless, I do collapse very long content, including IIRC in that very entry, but also e.g. Iroquois.) Having the top line(s) of the content be displayed (in the same legible, non-greyed-out font as at present) and then fade out or terminate in an ellipsis mid-sentence might help with that. - -sche (discuss) 05:32, 27 March 2021 (UTC)

Hello how's things. I do have a suggestion (that does take some work of writers). Our translation collapsing boxes do allow the heading section to state the sense of the word that is being translated. This is helpful when two or more senses have their own separate lists of translations.

Entries with multiple etymologies could use the same kind of box. And the consistency with the collapsed boxes for derived terms and translations make things neat. 119.56.103.124 16:47, 31 March 2021 (UTC)

 * Shotgun thoughts: —Cool idea, been trying to do this too since the last discussion which I can't find—Related: cognates in the =ETY= section—Collapsibles easily missed - ellipsis definitely the way to go—In that shape moving it down wouldn't be as pressing; my own reason for doing so is that =ETY= is thematically related to =Derived terms= etc. So it would make sense to have these grouped up into a "meta section" below the definition. This would separate it from the thematically related =Alternative forms=, which I can live with as long as they're near =Pronunciation=.—On the subject of visually tying together, I stumbled upon again today and was pleasantly confused thinking that the definition section had finally acquired some visual cues, especially useful to visually group quotations and synonyms together with a definition. Alas! But something simple like this would go a long way towards improving the look and feel of the website.—Grouping definitions by Form without necessarily specifying POS could resolve the POS heading issue: click #1, click #2, click #3 Brutal Russian (talk) 04:24, 3 April 2021 (UTC)

Some of the links displayed using this template are malformed; in parts where commmas and/or dashes are used to indicate different forms the links that the template creates link to bad page names such as one with the comma and everything in the page title, instead of having 2 separate links when there are 2 forms listed for one inflection of the noun. User: The Ice Mage talk to meh 15:27, 17 March 2021 (UTC)

Pali Transliteration
I think the time has come to enable transliteration of Pali from non-Roman scripts. Module:pi-translit has been tested, and seems to me to be working. However, it would be nice to check its interaction with Pali templates before it is accepted. How do I test it out? In a world without protections, I would make an uncommitted edit to Module:languages/data2 to add field translit_module = "pi-translit" to m["pi"] and view content pages using the editor's preview facility. However, the module seems to be protected against my doing that sort of thing. Do I need to simultaneously sandbox a lot of infrastructure?

The Thai and Lao scripts each have different writing systems for Pali depending on whether or not one writes the short vowel 'a'. Sometimes one cannot tell which system an isolated word is in, and the word has different transliterations for the two systems. Is there any mechanism for passing the identification of the writing system to the transliterator? For example, is  if 'a' is unwritten, but  in the system where it is written. (This is a productive confounding of abugidic past active participles and alphabetic absolutives; the former are rare.) RichardW57m (talk) 14:43, 18 March 2021 (UTC)

Missing milestone
We passed 6,500,000 entries some time ago. Would anyone like to find out what it was and then update Wiktionary:Milestones? SemperBlotto (talk) 16:45, 20 March 2021 (UTC)
 * I figured we weren't counting half millions any more for some reason. Given deletions, I'm not sure there's a feasible way to find a meaningful answer to this now. —Μετάknowledge discuss/deeds 20:54, 20 March 2021 (UTC)
 * I think it should be possible to reconstruct this with the history log (replaying all insertions and deletions). Maybe it can be even done with some clever SQL. – Jberkel 21:47, 20 March 2021 (UTC)

Create pronunciation list
Please create a list of pronunciation of most used words (Frequency lists) with IPA and audio file. The table should have both IPA and the audio file to assist non native speakers in learning word pronunciations. Thank you -Vis M (talk) 22:52, 20 March 2021 (UTC) Example list:User:Vis_M/Pronunciation_list Vis M (talk) 16:36, 30 March 2021 (UTC)

"Recent additions to the category"
Hey- how can I get the "Recent additions to the category" box (like we can see on this page: ) onto this page: Han phono-semantic compounds? I want to use it to monitor this category and see what changes are made. Thanks for any help. Please ping me if you have an answer. --Geographyinitiative (talk) 15:11, 24 March 2021 (UTC)
 * By adding a DynamicPageList (e.g., see Category:Translingual proper nouns). J3133 (talk) 15:16, 24 March 2021 (UTC)

New line in CategoryTree
On MediaWiki:Common.css says that CategoryTree generates a new line but I think this is not correct, the new line is generated due to the template having an extra line right before the noinclude tag. I realized this while implementing the same temp on ku.wikt. The other affix-see templates doesn't have that line.--Balyozxane (talk) 11:54, 26 March 2021 (UTC)

Lua error: not enough memory at 一
Just bringing this to attention. Don't how long it's been like that. -45.58.196.55 19:06, 26 March 2021 (UTC)
 * Odd, I don't see any Lua memory warnings when I view the page. ‑‑ Eiríkr Útlendi │Tala við mig 19:12, 26 March 2021 (UTC)
 * Sorry, I have no idea what just happened but right after I verified the link in the heading the error fixed itself...? (This is what it looked like.) (And wiki didn't let an IP address editor use the Undo function.) -45.58.196.55 19:14, 26 March 2021 (UTC)
 * Right now, the page is using 52,312,651 out of the 52,428,800-byte maximum allowed. That translates to 0.11 MB below the 50 MB limit. All it takes is a minor tweak to one of the dozens of modules transcluded by the entry to take it over then line one way or the other. For that matter, it might just be a tiny random change in the way a server is processing the code. Think good thoughts- it might make a difference... Chuck Entz (talk) 23:30, 26 March 2021 (UTC)
 * See Lua memory errors. J3133 (talk) 19:16, 26 March 2021 (UTC)

Query
Hello!

Is it possible to see edits with the  tag that haven't been edited since? I namely looked into the logs for that tag but so many versions have been overwritten and hence does not need to be fixed. If there was a way to exclude the already fixed entries that would be appreciated. Thanks! Jonteemil (talk) 00:15, 27 March 2021 (UTC)
 * Not in the logs themselves. Someone would have to combine the log data with data from the edit histories. You could sort of infer how likely it is to have been overwritten by how old the most recent tag for an entry is: if there are edits since the tagged one that aren't in the log, it's been fixed. Not foolproof, since you can't predict when or if an entry is going to be edited- but it's better than nothing. Chuck Entz (talk) 01:45, 27 March 2021 (UTC)
 * You could conceivably generate a list yourself of entries without head templates, from the database dump. - -sche (discuss) 05:23, 27 March 2021 (UTC)

Data on Entries' Memory Usage?
Is there any way to survey entries to see if they're approaching the 50 MB memory limit? It would be nice to not have to wait until they end up in CAT:E to reduce memory usage.

If there's no way to directly access memory usage from a bot, perhaps there's some way for a bot to do the equivalent of "View Page Source" on a browser, since there's parser profiling data embedded as comments in the html listings.

We could narrow it down a bit, since almost all the out-of-memory-errors I've seen so far have been single-character entries in Category:Translingual lemmas or entries in Category:English lemmas with translation tables. The few exceptions have had literally dozens of L2s. I'm sure we could narrow it down further by using frequency/basic words lists. Chuck Entz (talk) 04:36, 27 March 2021 (UTC)

Fonts of entry titles
Recently I found most entry titles have changed to a serif font, while Chinese titles have remained sans-serif. Screenshot:. Does anyone else experience this? -- Huhu9001 (talk) 00:53, 28 March 2021 (UTC)

Who has designed and supports this?

 * Copied from Template talk:audio.

The look of player's menu is absolutely awful, the commonly used contrast "grey or dark grey on black" is very hardly readable and there is no any alternative for people with some visual problems or disabilities. Has someone of developers tried to use the "Settings", where the elements of list are shown in dark grey on black and don't have any tooltips? Settings UI is not resizable, no link to external help for users, no info whether the settings are saved for current session only or for subsequent use etc...

And nobody is interesting in fixing the "echo effect" at start of second and next playing of the same file, the bug which has been noticed more than 10 years ago and still happens on the last Google Chrome. --2A00:1370:8115:53ED:786E:9AE4:4090:1993 08:17, 28 March 2021 (UTC)

Crappy format of dates
I stumbled upon a few crappily-formatted quotes like in this edit, which gave the wrong year. I'm assuming we could find some more like that which have [year], [number] [month] or [year], [month] [number] and make a list of them, and see how many of them are the result of Wonderfolly. Yellow is the colour (talk) 19:35, 28 March 2021 (UTC)

 * |February|March|April|May|June|July|August|September|October|November|December)+%5B12%5D?%5B0-9%5D%5B^0-9%5D/ and |February|March|April|May|June|July|August|September|October|November|December)/—both are quite relaxed, so they catch as many incorrect dates as possible, at the cost of finding many false positives. —Tacsipacsi (talk) 20:10, 1 April 2021 (UTC)

Information_desk/2021/March
We have reader complains that mobile pages are always expanded which make the pages hard to see. This becomes a serious problem on LongPages with a hundred entries. Especially that TOC does not appear in mobile view.

I have verified with mobile view that this is the case on WT. Section headings always appear expanded.

I also went to the other WikiMedia projects and their section headers are minimized (collapsed).

Anyone knows why the difference in behavior and how to fix it? Need to call in help from ?119.56.97.84 05:55, 30 March 2021 (UTC)
 * I will go look for a meta developer to see if I can get some opinions. 119.56.103.124 16:58, 31 March 2021 (UTC)
 * This is a global setting active on all Wiktionaries (but not on other Wikimedia projects). It was discussed in T63447, and while I’m also embarrassed by this setting when I read Wiktionary on mobile (as I do a lot), I also understand the reasoning there. —Tacsipacsi (talk) 19:46, 1 April 2021 (UTC)

Alternatives to POS as headers
A recent Beer Parlour discussion talked about duplicated definitions for every POS header. This gets worse when multiple senses/etymologies, and even worser when there are declensions.

This discussion is about if better headers can be used to lessen such duplicated senses, and what form it can take. 119.56.103.124 16:58, 31 March 2021 (UTC)

title: Wiktionary:Grease pit/2021/March


text: Category:Terms derived from Epic Greek

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

title: Category:Terms derived from Epic Greek


text:
ᎧᏅᏫᎠ

Verb

 * 1) he/she is curing him/her, healing him/her, doctoring him/her

title: ᎧᏅᏫᎠ


text:
Wiktionary:Grease pit/2021/April

Sidebar again
It's Thursday again. Something has changed in new MediaWiki version and content under headings "In other projects" and "Visibility" appear in large font. See previous comment Grease_pit/2020/October. I think class definitions should be reviewed at MediaWiki:Gadget-AggregateInterprojectLinks.js and MediaWiki:Gadget-VisibilityToggles.js. --Vriullop (talk) 07:04, 1 April 2021 (UTC)

WT:TR problem with "throw a punch" section
Why does this section appear on the WT:TR "home page" (where we are advised not to make edits) but not on the April sub-page? The post is signed with a March date but appears under the April header! Equinox ◑ 15:54, 1 April 2021 (UTC)

 * It’s directly on WT:TR, see edit view. (I can’t do anything with it myself due to Special:AbuseFilter/43.) —Tacsipacsi (talk) 20:14, 1 April 2021 (UTC)

 * Thanks; seems OK now. Is that abuse filter bad? Who is Tacsipacsi? Questions for sober posterity. Equinox ◑ 05:38, 2 April 2021 (UTC)

see descendants
Hi, so there's this template that does nothing but add some text, with no parameters. I've had a glorious idea to add the same parameters to it as, so that you simply add  to convert a descendant into a redirect and it looks exactly like current:   +   example. In addition this template can be excluded from being transcluded through and so solve the ongoing issue of same-language descendants. It shouldn't throw up an error if no parameters are given though, as it's currently used in way too many pages (could use a bot to convert these). The idea seems bullet-proof; would it please somebody with permission to edit it to implement this? Brutal Russian (talk) 21:19, 1 April 2021 (UTC)
 * The example you provide is weird because isn't a descendant of, it's an alternative form of it. —Mahāgaja · talk 08:53, 2 April 2021 (UTC)
 * Yes, this is how this template is used. If the descendants go back to an alternative form, it's currently preferred to list them at the alternative form's page, and direct the reader to it using ; at the same time it's discouraged to list alternative forms as descendants, an unresolvable clash currently. I want to combine the functionality of with that of . Brutal Russian (talk) 16:15, 2 April 2021 (UTC)

Indexes for Sanskrit Lemma Categories
The indexes for Sanskrit lemma categories and the like assume that all entries will start in Devanagari. This makes it difficult to look non-Devanagari forms up, e.g. for maintenance work. It doesn't help that the sort algorithm and index disagree as to what the last letter is - the sort algorithm does not place ळ after the consonants of Classical Sanskrit. I'd like to add other scripts in the same fashion as for Pali.

This job will, inter alia, involve changing sa-categoryTOC from a redirect to categoryTOC-Devanagari to a fork from it. Does anyone want to take on this task, or should I just go ahead and do it myself? RichardW57m (talk) 13:42, 2 April 2021 (UTC)
 * Which indexes are you referring to? Anything under the Index: namespace is totally obsolete and should be nuked. Benwing2 (talk) 00:33, 5 April 2021 (UTC)
 * The one that looks like this:

in CAT:Sanskrit lemmas.
 * I'm suggesting it should be more like, but with entries appropriate to Sanskrit:

 * In this example, Latin, Devanagari, Thai and Tai Tham scripts are expanded because they have more than 200 entries in some categories. --RichardW57m (talk) 09:12, 8 April 2021 (UTC)
 * I see, you're referring to the language-specific table of contents templates. I think you should go ahead and change it if you want. Benwing2 (talk) 03:42, 9 April 2021 (UTC)

Wikidata
What happened to the link "Edit links" underneath the list "In other languages"? --Espoo (talk) 17:49, 3 April 2021 (UTC)

Additional tech gore included by
See Reconstruction talk:Proto-Germanic/dreuganą. —Rua (mew) 09:14, 6 April 2021 (UTC)
 * Commenting out mislead in desctree at Reconstruction:Proto-Germanic/dreuganą solves the problem, so somehow the problem is that whatever is finding gmw-pro at Reconstruction:Proto-West Germanic/dreugan is also grabbing too much text after the Descendants section, stranding "ology 2===" of the following ===Etymology 2=== header. I don't how to fix it, but that's where to start looking. —Mahāgaja · talk 11:37, 6 April 2021 (UTC)
 * Nobody? —Rua (mew) 19:36, 28 April 2021 (UTC)
 * After taking ~40 minutes to dig through mostly-undocumented code, I think I've traced the problem back to the  function in Module:descendants_tree.
 * Towards the end of that function, there's this bit:

 * Since the returned  includes that   portion that's showing up unwanted at Reconstruction:Proto-Germanic/dreuganą, I suspect the error is somewhere on line 31, but I am unfamiliar with Lua syntax details, and I don't understand what the underscore is doing there, nor do I understand what the   function does or what   indicates in this context.
 * (Incidentally, the challenges that Rua and I have faced in tracking this down provide further evidence that we need to rethink our stance against code comments.)
 * HTH, ‑‑ Eiríkr Útlendi │Tala við mig 22:41, 28 April 2021 (UTC)
 * Thanks for finding that. The second  call is meant to be removing the Etymology header and everything after it; fixed. (The   was receiving the second unused return value of , which isn't necessary.) — Eru·tuon 23:25, 28 April 2021 (UTC)

Some forms of the Latin don't have entries
Just to put this out there in case it went unnoticed: some forms of don't have entries (as is the case for ) yet others do (like ). Kritixilithos (talk) 12:49, 6 April 2021 (UTC)
 * I think the bot script to generate the entries for non-lemma Latin forms (User:SemperBlotto's bot) just skipped the forms that already had entries, as with (a verb form). Benwing2 (talk) 03:46, 9 April 2021 (UTC)
 * I've added manually now. —Mahāgaja · talk 07:45, 9 April 2021 (UTC)

New Language
I have found a language named 'Pamunkey' that doesn't have any language code. I have put some references to show proof it is a language with the Wikipedia link showing some extra references. I don't know if this is the place to do so but I'll just put it here. —101.98.133.254 04:15, 7 April 2021 (UTC)
 * So from the Wikipedia article, it looks like it's uncertain whether Pamunkey was even an Algongquian language. If we choose to create a code for it, I'd suggest we use the  prefix rather than the   prefix. Maybe  ? —Mahāgaja · talk 08:16, 7 April 2021 (UTC)

. If you are still interested include this in your common.js. Giorgi Eufshi (talk) 21:19, 13 April 2021 (UTC)

Declension substitutions; footnotes not working

 * Хелло, I'm having an problem. I attempted to automate the declension table of, which is almost identical to but requires removing some letters (idem, not iddem) and has two spellings for the forms where -m- is followed by -d-, the other spelling being -n-. It uses a simple substitution, which I expected to work only when the   appears outside the  , e.g.   – however, as you can see in the resulting genitive plural, it substitutes everywhere. How does one make it spit out forms with both -n- and -m-? Automating the iddem thing would be nice as well (currently it's forced on the word's page). Oh, and is there a way to have several forms be presented without like breaks, but with commas or slashes instead (useful for short ones like these)?
 * Additionally, while writing the notes I discovered that local.footnote doesn't work, e.g. on, and I'm clueless about fixing this myself. Daring to ping if he's not too busy :3 Brutal Russian (talk) 21:15, 14 April 2021 (UTC)
 * Well, I've just tried another approach, with form substitution, with the same result, which means the m>n letter substitution seems to be implemented somewhere else entirely. Brutal Russian (talk) 11:08, 15 April 2021 (UTC)
 * I see m being replaced with n in  in Module:la-nominal. Not sure what the right solution is. — Eru·tuon 01:49, 16 April 2021 (UTC)
 * I'll try to take a look at this tomorrow. Benwing2 (talk) 04:33, 17 April 2021 (UTC)
 * What is the existing issue with ? The declension looks OK to me as-is. Benwing2 (talk) 04:36, 17 April 2021 (UTC)
 * It's intended to give two spellings &,  & , but as Erutuon's found out, another module converts all instances of -md- into -nd-. If this is done with suffixes only, perhaps it could be made to automatically give both spellings because this vacillation extends to all such cases of suffixation of d- after -m. I want to see this because unlike the / that I removed, m and n are separate letters and not graphic variants of the same letter; though I might add back . Brutal Russian (talk) 11:35, 17 April 2021 (UTC)
 * Does the md/nd variation apply to *all* pronouns with suffixes beginning with d (e.g. )? If so we can just change the 'sufn' indicator to 'sufmn' and make it generate forms with both 'm' and 'n'. Benwing2 (talk) 15:09, 17 April 2021 (UTC)
 * Yes, it applies to all, and that would work a treat. And what about the possibility to list short forms in-line? (sorry about the edit conflict lol) Brutal Russian (talk) 18:00, 17 April 2021 (UTC)
 * I fixed the issue with optional m/n using . As for listing short forms in-line, that is a bit tricky as it depends both on the length of the forms and the size of the space available to fit the forms, e.g. you probably want the dative forms to show inline because they have three columns of space but maybe not the accusative singular forms to show inline because they have only one column of space. I'll think about how to implement this but it may take a bit to get to it. Benwing2 (talk) 17:05, 18 April 2021 (UTC)
 * Also fixed the footnote issue, although in general I'd recommend doing footnotes the way you've done them (so there's a footnote number by each affected form) instead of using a general footnote at the bottom. Benwing2 (talk) 17:52, 18 April 2021 (UTC)
 * Thanks a bunch! Yes, it does seem that the footnote could better be written on the individual pages, but there probably were some written using the argument that disappeared without anyone noticing when the implementation broke. However, am I right in thinking that a template like m can only be used in these notes if invoked by the module, which consumes memory, and thus square brackets are to be used instead, like iīsdem? Mostly out of curiosity. Brutal Russian (talk) 14:55, 20 April 2021 (UTC)

extra lines at season
I see two extra definition lines at season, presumably brought about by. Anyone know how to fix it? Yellow is the colour (talk) 21:25, 14 April 2021 (UTC)
 * I'm seeing the same thing, for example, in the entry for contemporary. Before the definition that uses senseid, an empty, numbered definition appears. --Frigoris (talk) 13:59, 15 April 2021 (UTC)
 * See below. Chuck Entz (talk) 14:17, 15 April 2021 (UTC)

Template:senseid is not working properly in the entry People's Republic of China
恨国党非蠢即坏 (talk) 22:44, 14 April 2021 (UTC)
 * The good news is that it was very simple to fix- I just added p (that's the only formatting parameter allowed by the module). The bad news is I have no idea why it was necessary, or why it worked. Neither the senseid template, nor the modules Module:senseid and Module:senseid/templates have been touched since February. The only explanation I can think of is something along the lines of w:WP:ITSTHURSDAY. Of course I know next to nothing about this part of the system, so someone may chime in with the obvious explanation that I missed. Chuck Entz (talk) 03:34, 15 April 2021 (UTC)
 * Yep, senseid is busted everywhere, see or even the senseid documentation itself. I have no idea why. This, that and the other (talk) 04:50, 15 April 2021 (UTC)
 * I left a comment at T278345. I couldn't see any relevant code changes on the MediaWiki side either, so we'll no doubt soon see whether the problem lies here or there. This, that and the other (talk) 04:58, 15 April 2021 (UTC)
 * I'm tempted to change the default in the module from <li> to <p>, which would fix the immediate problem, but I don't know what else that will break, or if there's a fix needed somewhere else. Chuck Entz (talk) 05:14, 15 April 2021 (UTC)
 * Tempting indeed, at least as a temporary fix. Note that the template doc of senseid says "When using this template with |tag=p you will also need to use senseid-close at the end of the relevant paragraph of definition. This is to ensure the correct markup is generated." For instance, when I tried tag=p on in preview mode, it dispayled extra space between the definition line and the usex below it. So it should only be an interim solution. This, that and the other (talk) 09:31, 15 April 2021 (UTC)
 * I just noticed that it causes the [quotations▼] control to end up on the next line, and it seems to add vertical whitespace in some other cases. It's better than an empty definition line, but it just shows how kludgy the workaround is. If there's no fix on the mediawiki end, I suppose we could add code to the javascript or the css to restore the old behavior. Chuck Entz (talk) 14:56, 15 April 2021 (UTC)
 * It seems to revolve around the use of a <li> tag to take the class="senseid" and and id="xyz" attributes. I wonder if there's some other, more inert tag that could be used. Chuck Entz (talk) 15:10, 15 April 2021 (UTC)
 * The issue is being fixed on the MediaWiki end: see T280260 with a patch to backport the fix to 1.37.0-wmf.1 (the version of MediaWiki we are running). The correct tag to use for anchors is <a name="..."> but MediaWiki doesn't allow it. I suspect the reason <li> was chosen was to make it easy for the senseid-highlighting to work. This, that and the other (talk) 23:47, 15 April 2021 (UTC)
 * Now ✅ in MediaWiki. This, that and the other (talk) 23:49, 15 April 2021 (UTC)

Is it fixed? I am still seeing the error (for example, at ), and neither purging the cache nor doing a blank edit causes it to go away. — SGconlaw (talk) 16:34, 16 April 2021 (UTC)
 * It's fixed for me. Perhaps different Wikimedia servers have different cached versions of the page, some with the error and some without it? — Eru·tuon 22:48, 16 April 2021 (UTC)
 * Still seeing the error … and refreshing the page did nothing. — SGconlaw (talk) 04:10, 17 April 2021 (UTC)
 * Still no change 15 hours later. — SGconlaw (talk) 18:00, 17 April 2021 (UTC)
 * OK, the problem seems to have finally gone away. — SGconlaw (talk) 18:17, 18 April 2021 (UTC)

Entry previews possible?
Can Wiktionary links have a page preview? On Wikipedia, links to other articles show the article preview on hover. A page preview of a linked Wiktionary entry could be useful. Most useful would be the preview of any Synonym sections on the linked page.

Template "Han ref" also starts to create spurious list element
The template also creates an empty list element before the first line. Example: 永, or any other Han-character entry that uses the template in the Translingual section.

Could this be related to the trouble with being discussed here?

By convention, the template is typically used as

*

That is, on a separate line that starts with an asterisk.

I tried removing the asterisk and in the preview it seems to produce the desired result. I don't know if it breaks anything else. --Frigoris (talk) 16:35, 15 April 2021 (UTC)

"Lua error: not enough memory" in te
I suppose something should be converted into a simpler format, but I don't know what and how to do it. Adam78 (talk) 14:45, 18 April 2021 (UTC)
 * See Lua memory errors. J3133 (talk) 09:05, 20 April 2021 (UTC)
 * Thanks, I read that page before, but I still wonder what to do at the moment, out of the options listed (or beyond them). I know that this issue has been handled before in the case of some other pages, e.g. in February 2018. I wonder if might kindly work magic again. Adam78 (talk) 11:42, 20 April 2021 (UTC)
 * Ah, but that was optimizing Module:languages, not a specific page, but maybe it's worth taking another look at it. We might be able to save some memory by splitting module data further. —Jberkel 12:25, 20 April 2021 (UTC)
 * After doing some local profiling it looks like we use ~12 MB just for language data on this page (for 100 unique language codes), so we should look at optimizing this a bit more. – Jberkel 15:43, 21 April 2021 (UTC)

Modify Module:hyphenation to check errors
There are errors like. It's uncovered by zh:Module:hyphenation in the category, but I think my code's false positive rate is not low, such as, is legit? EdwardAlexanderCrowley (talk) 08:58, 20 April 2021 (UTC)

Legit ones: for, plus many unicode varient related issues. EdwardAlexanderCrowley (talk) 09:24, 20 April 2021 (UTC)

 * Correct Hungarian hyphenations: asszony: asz-szony, pettyes: pety-tyes, mennyi: meny-nyi. Panda10 (talk) 23:57, 20 April 2021 (UTC)
 * Do French printers genuinely divide across a line break as prok·si·mi·té? I find that very hard to believe.  says not to divide on either side of x, so it should be proxi·mi·té. —Mahāgaja · talk 06:35, 21 April 2021 (UTC)
 * Also for  is wrong, but I can't figure out the right one. Anyway, My script at zhwikt is a temporary implementation, and I recommend applying a similar one to enwikt. For hungarian hyphenation, either we implement carefully, or we use a new param legit=1 to indicate the hyphenation is legit. EdwardAlexanderCrowley (talk) 02:20, 22 April 2021 (UTC)

Inviting : I've fixed tens of errors, and I'm expecting more, because all the pages I fixed have been used by zhwikt, and there're ~500,000 non-chinese pages on zhwikt, comparing to ~5,000,000 here. EdwardAlexanderCrowley (talk) 09:08, 2 May 2021 (UTC)
 * I understand the principle although it sounds like implementing this requires a lot of knowledge about how each individual language hyphenates. Benwing2 (talk) 17:21, 2 May 2021 (UTC)
 * Just get ride of the bar symbol, then turn all unicode variants into their base forms, then most errors can be discovered. It seems we only need to take care of Hungarian hyphenations. EdwardAlexanderCrowley (talk) 00:56, 3 May 2021 (UTC)

I need help structuring Translingual cuneiform pages
Hello experts!

I don't understand anything about templates and I need some help re-structuring the Translingual section of cuneriform pages, like the following one: https://en.wiktionary.org/wiki/%F0%92%80%AD

I would like have a similar structure to that of Translingual Han characters, something like the following page: https://en.wiktionary.org/wiki/%E7%94%9F#Translingual

This is what I would like to implement (and need help with):

 * 1) A nice big version of the cuneiform sign under the header "Cuneiform sign".
 * 2) Help understanding and modifying the "cuneiform sign" template.

Thank you! Sartma (talk) 13:34, 22 April 2021 (UTC)

 * Never mind, I managed! :D Sartma (talk) 17:13, 26 April 2021 (UTC)

I believed I have been wrongly accused of "various specific spammer habits".
I was just trying to edit the citations of the page "Ex-Mus" (which I created), and I put in this code:

The Religious Ads on My Atheist Videos Are Ridiculous. Genetically Modified Skeptic. 27 June 2020. "Resources for Ex-Mu's: https://exmuslims.org/join-us/"
 * 1) (The following quote is in the video description.)

I don't know why I am now unable to edit the citations of my own entry, and feel as if I wasn't actually spamming. Am I wrong here or is the bot just buggy?
 * : 99% of the time, when a new user adds a link to a youtube video like that, it's to promote something. The fact that you created a "plural of" entry without creating the main entry (what we call the lemma) strongly suggests that you created the entry solely to host the link, and everything you've included here points to the the video being solely for advocating a particular point of view. It may not be spam in the strictest sense of the word, but Wiktionary has a neutral point of view policy for a reason. It's not for me to say whether that point of view is good or bad, right or wrong- just that promoting or opposing points of view is not what a descriptive dictionary does. Besides which, I see very little evidence that meets the requirements of our Criteria for inclusion for that particular spelling being in actual use.
 * The upshot is that the abuse filter prevented you from adding something that you shouldn't have been adding to an entry that's already been deleted because a plural-of entry without a main entry to provide definitions and the like is utterly useless. The rest is a matter of wording.
 * If you do decide to create a lemma, it looks like it should be at ex-mu- if there's enough usage to justify an entry (FYI, youtube videos and their online descriptions aren't evidence for Wiktionary's purposes). Chuck Entz (talk) 09:48, 26 April 2021 (UTC)

Help creating a template to manage Akkadian roots (an Akkadian version of )
Hello! I'd like to have a template similar to or  for Akkadian entries, but I don't have the technical knowledge to create one. Can anyone help? Thank you! Sartma (talk) 17:11, 26 April 2021 (UTC)

 * Done! Thank you so much !

fur-categoryTOC
What could the template consist of? --Apisite (talk) 05:12, 27 April 2021 (UTC)

Getting inflection tables from Wikidata
Wikipedia now increasingly pulls some information from Wikidata (such as a city's population) into its info boxes. Similarly, Wiktionary could pull inflection patterns from Wikidata's lexemes. For some languages, such as Estonian, the coverage is starting to get really good. Has any branch of Wiktionary done this already? As an example, the English Wiktionary entry for päev (Estonian for "day") and the German counterpart de:päev, there are already declension pattern tables. But the French fr:päev and Swedish sv:päev don't have this, and so it would be easier to pull that information from Wikidata's d:Lexeme:L381851 than to implement the full inflection table locally in French and Swedish Wiktionary. --LA2 (talk) 17:34, 27 April 2021 (UTC)
 * It could be useful for smaller Wiktionaries. For en.wikt, which has more inflection data than any other Wiktionary, it would only mean relinquishing those data to another wiki where we don't have admin powers, cannot patrol edits or easily detect subtle vandalism, etc. —Μετάknowledge discuss/deeds 17:50, 27 April 2021 (UTC)

 * , I agree with what Μετάknowledge said. We have already implemented full inflection tables for most of what we need, and hosting that here gives us the ability to maintain that and restructure it as need arises.  For instance, there is some discussion about reworking the Japanese inflection tables for improved clarity and ease of use -- if these were hosted at WikiData, we could not easily do this.  I see no particular benefit for the EN Wiktionary in migrating all of our inflection table functionality to WikiData, and instead many disadvantages.  ‑‑ Eiríkr Útlendi │Tala við mig 00:14, 28 April 2021 (UTC)
 * Apart from the convenience of having stable data locally, by now Lua have no access to Lexemes, pending T235901. --Vriullop (talk) 06:14, 28 April 2021 (UTC)
 * A less radical change would be making English Wiktionary’s templates and modules more reusable: designing them so that human-readable text (except for that in the subject language, of course) is easily translatable (probably using the infrastructure of, or at least inspired by, Multilingual Templates and Modules), using TemplateStyles instead of Common.css styles wherever possible, etc. This way control remains here, but other, smaller wikis can more easily benefit from the development. I’m active both here and on huwiktionary, and I often have hard time adjusting modules imported from here so that they produce grammatically correct Hungarian output instead of English output, and eventual edits to the enwiktionary templates after the import are more than likely not to get there ever. —Tacsipacsi (talk) 15:53, 28 April 2021 (UTC)
 * I would be supportive of 's suggestion. I am not up to speed with coding our modules, in part due to the lack of documentation and code comments, as discussed elsewhere.  The broad idea of making our modules, well, more modular, seems like it might be low-hanging fruit when it comes to improvements.  ‑‑ Eiríkr Útlendi │Tala við mig 17:47, 28 April 2021 (UTC)

Trügenology
As I wrote here, there's a cosmetic error resulting from one of the scripts we use to scrape data from one page onto another. Can anything be done about it, either in individual cases or by editing the code directly, to make it appear normally? Thanks, — Soap — 22:09, 27 April 2021 (UTC)
 * See #Additional_tech_gore_included_by_{{desctree}} above. I just replied there.  ‑‑ Eiríkr Útlendi │Tala við mig 22:44, 28 April 2021 (UTC)

Plains Cree translations
Judging by existing entries and data I can see Plains Cree is written in both Canadian syllabics and Latin scripts, but right now it seems to get a generic treatment in trans-tables. Does anyone have the knowhow required to make it so that Wiktionary will treat it like Serbo-Croatian in trans tables by listing both scripts? User: The Ice Mage talk to meh 15:04, 29 April 2021 (UTC)

title: Wiktionary:Grease pit/2021/April


text:
Wiktionary:Grease pit/2021/May

Importing of the Alar dictionary corpus
Alar is an open source Kannada dictionary made by V. Krishna that has became a very popular online source and described as "comprehensive" by Deccan Herald, as well as received positive feedback from Kannada news sources (see links on the bottom of this page). Even better, its corpus is licensed under ODbL 1.0 (source), which allows for sharing, creating, and adapting the database (including for commercial use) given attribution, share-alike and keeping it open (althoug you can also add DRM to it if you also offer a free version), and is available as a single YAML file on Github. (side note: brought up some issues on Discord using this link from OpenStreetMap, however I think this applies to a specific situation on OSM where users can change the license of their contributions, while all contribution to WMF wikis are GDFL/CC-BY-SA dual licensed per meta:Licensing update, and the "produced works" should still be compatible with the project as even static images (as opposed to dynmaps or pure data) of WMF maps are still compatible with OSM's licensing as detailed here).

With over 150k Kannada entries with corresponding English definitions, it would significantly enhance our current coverage of the language, which has only 1122 lemmas as of present in Wiktionary. So, given these circumstances, can we use a tool to run through the file, incorporate these entries into Wiktionary, and properly attribute them to Alar/the data source? I think that, if we could, it would prove to be very useful, given the scope and pre-formatting of the entries' data as well as, more uniquely, how recent it is (not often is there open data like this for recent works, its usually for works that are old enough to be in the public domain). MSG17 (talk) 02:31, 5 May 2021 (UTC)
 * I'm not sure the license is compatible. People can use Wiktionary's data for commercial/restricted purposes; the Share-Alike requirement would seem to prevent that. —Μετάknowledge discuss/deeds 03:51, 5 May 2021 (UTC)
 * According to the full license text, the rights of users "explicitly include commercial use, and do not exclude any field of endeavour". As previously mentioned, as long as access to a free version of the data is offered, parallel restricted distribution is allowed (see 4.7.b in the full license). One again, I would like to point out that Wiktionary and other WMF projects are also ShareAlike licensed with the explicit motivation to make it easier to incorporate ShareAlike content. According to Creative Commons, the CC-BY-SA 3.0 license used is even more restrictive, stating "You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits." MSG17 (talk) 12:04, 5 May 2021 (UTC)
 * Indeed, CC-SA definitely does not exclude commercial reuse; that would by CC-NC (which is not allowed on Wikimedia projects except under a claim of fair use). —Mahāgaja · talk 20:40, 18 June 2021 (UTC)

Lua error: not enough memory
On se, starting at Serbo-Croatian, all I see "Lua error: not enough memory". If anything that's important and Lua-related was changed recently, maybe it would be a good idea to change it back. -Xbony2 (talk) 14:06, 5 May 2021 (UTC)
 * See Lua memory errors. J3133 (talk) 14:12, 5 May 2021 (UTC)
 * Ah. Thanks. -Xbony2 (talk) 15:05, 5 May 2021 (UTC)

Template:switch parser function
Is there a limit to the number of branches in a #switch function? — Salt  marsh. 06:47, 7 May 2021 (UTC)
 * "A #switch can contain over 1,000 branches, but for better speed should be split to have less than 100 branches, in each of multiple or nested parts.". —Μετάknowledge discuss/deeds 16:08, 7 May 2021 (UTC)

Alagoas, Amapá, and Sergipe
Alagoas is defined in the Portuguese section as "A state in the the Northeast Region of Brazil. Capital: Maceió." with an extra "the." Problem is, when I tried to edit it to remove the typo, I instead got a template saying "place|pt|state|macroregion/pt:Northeast Region|c/pt:Brazil|capital=pt:Maceió."

How do I fix this??

EDIT: Amapá has the same problem as well!

TheTheRemover (talk) 19:20, 11 May 2021 (UTC)

Search finds nothing
I listened to a Russian video and thought they said "можедельник", so I looked up this word here in English Wiktionary, but the search (Special:Search/можедельник) found nothing. It turns out there is an entry for можжевельник, which was the right word (juniper bush), I had only two letters wrong. But even a search for "можевельник" (just one letter missing, Special:Search/можевельник) gives no results at all. Is this really a state-of-the-art search function in the year 2021? Now, the same search in Russian Wikipedia (w:ru:Special:Search/можедельник) does find the entry. What's different? --LA2 (talk) 08:53, 16 May 2021 (UTC)
 * It's unfortunate that the search suggestions are less helpful here for Cyrillic text. The search engine is a MediaWiki extension that we on Wiktionary have little control over, and I don't know how the search suggestions work. You will be more likely to get an answer on a Wikimedia IRC channel like  on Freenode, or on mw:Help talk:CirrusSearch. Perhaps there are language-specific search suggestion rules and the search suggestions here are English-based and the ones on the Russian Wikipedia are Russian-based? Just a guess. — Eru·tuon 05:10, 17 May 2021 (UTC)
 * I just noticed in Tech News that they're working on fixing cross-site search inconsistencies like this: see the task T219550 on Phabricator. — Eru·tuon 21:38, 7 June 2021 (UTC)

and
I have created these two small form-of templates, as they are greatly used in Akkadian entries. However, most definitions are Sumerogram for". Should this be addressed or is of good enough? Cheers, Swaare (talk) 09:41, 17 May 2021 (UTC)

Different lemma inflections in headword lines
I've encountered a presentation issue with Pali verbs in some non-Roman scripts. Because emboldening does not work well in some scripts, enlargement is being used as an alternative or supplement. This is seen in both headwords and quotations and usage examples. Unfortunately, Pali verb roots should only be given in the Roman scripts; there is no benefit in giving them in other scripts, because they are not words. (The Pali names of roots end in vowels; their English names mostly don't.) How can I induce Module:headword to recognise that they are in the Roman script. --RichardW57m (talk) 12:48, 18 May 2021 (UTC)

 * I've found the answer. The solution is f1sc of head.  I implemented the solution in pi-verb on 20 February 2023.  --RichardW57m (talk) 10:09, 16 March 2023 (UTC)

I don't know if a similar consideration potentially applies to Sanskrit - perhaps they do intend to have dozens of manually translated and maintained pages for Sanskrit roots. It can be argued that Sanskrit roots are translingual. --RichardW57m (talk) 12:48, 18 May 2021 (UTC)

Character Folding
Do we control character folding for searches for Wikimedia-implemented searches of Wiktionary? For example, to find a Roman text word, I can generally find it without having to enter the diacritics. I assume this is done by some form of character folding. Do we control this mechanism? Could we set it up to not distinguish U+1004 MYANAMR LETTER NGA and U+105A MYANMAR LETTER MON NGA? In some (font-dependent) contexts, these two characters are indistinguishable. In the Default Unicode Collation Element Table (DUCET), and presumably therefore to ICU, they are defined to be as distinct as 'a' and 'b' are. Experimentation has shown that the search for a word encoded with one of the characters will not find a word encoded with the other. --RichardW57m (talk) 13:18, 18 May 2021 (UTC)

Have we, and if so how, solved the problem of multiple encodings for Malayalam chillus? --RichardW57m (talk) 13:18, 18 May 2021 (UTC)

Please make Wiktionary Read & Edit mobile lite app
Wiktionary would greatly benefit from an editing App as the literature search needed is very simple to add content to entries. Word translations and all can be conveniently added from a smartphone.

A mobile app is very much crucial and needed for Wiktionary. The old Wiktionary mobile app had 1 million+ downloads.

So please make a Wiktionary lite app/progressive web application based on monobook responsive skin or similar. Wiktionaries are losing huge number of potential edits due to the absence of an app. Thank you! Vis M (talk) 21:54, 18 May 2021 (UTC)
 * I actually requested this in last years Community Tech Wishlist, but Wikimedia has put apps on hold (and I think it wasn't that well received anyway). Unfortunate, as I think Wiktionary would really benefit from an app (theres definitely a lot of potential for features such as highlighting terms and getting definitions), but understandable. MSG17 (talk) 23:53, 4 July 2021 (UTC)
 * Yes, I had also made a request for making web apps for wikt:, voy:, etc. I wish they will make a web app one day Vis M (talk) 00:43, 5 July 2021 (UTC)

LCCN number apparently not recognized by catalog.loc.gov?
Hey- could you look at this LCCN for me? On the Dabancheng page, I've got a quotation from a 1993 book, and I want to add the LCCN link. When you click on LCCN: 93-83190 it says: "Your search found no results." But on this page in the book (near the top of the page) it clearly says "Library of Congress Catalog Card Number: 93-83190". What gives??? --Geographyinitiative (talk) 18:44, 19 May 2021 (UTC)

Translations — target languages
For some weeks now (on my screen at least) the "select target languages" option appears not to be working. However, on closer inspection today, it is working but the choice buttons are invisible. So you can make a choice, but only by guessing/clicking where the button might be. — Salt  marsh. 10:48, 21 May 2021 (UTC)
 * This should fix it. The stylesheet was linking to images that had apparently been moved. — Eru·tuon 08:19, 28 May 2021 (UTC)
 * thank you — Salt  marsh . 05:09, 29 May 2021 (UTC)

swahili verb conjugations
neither the template nor the module of sw-conj has been edited lately, so i assume that this is yet another instance of code changes lurking behind a template that isnt easy to see.

basically, i want to know if this is working as intended. don't get me wrong .... i love the way it looks now .... but i suspect Im in the minority. also, is it just sw-conj or have other templates also been expanded?

see Template:sw-conj/documentation for an example of what it looks like now.

thanks,

— Soap — 12:48, 22 May 2021 (UTC)
 * I tried to improve it. Did it help? This, that and the other (talk) 05:26, 17 June 2021 (UTC)
 * Not really, no .... I was being polite up top because I could tell that people put really hard work into this and I didnt want to make it seem like I had no apprciation for others' hard work.  But the change you made really just made the text bigger .... I was talking about the recent changes to the code, which I cant find because I assume theyre in a template somewhere.
 * Basically to spell it all out ... do we really need all those forms? It makes the whole page difficult to navigate on slower devices, both PC and mobile. I dont know if the code could be made to run faster if it loads as a collapsible by default, or if the browser would just load them all and then collapse ... so that might not help.  This discussion went for a month with no replies so I dont expect to turn the    community's opinion around, though .... and I get it, ... if people aren't complaining then there's not really a problem.      Thanks, — Soap — 11:04, 17 June 2021 (UTC)
 * Could you clearly explain what the problem is? In your original post you basically just said "look at the template" without any further information, assuming that it looks exactly the same for everyone and that the problem is obvious. Now you mention something about collapsible by default. Is the problem that it's uncollapsed for you? It's not uncollapsed for me unless I press "Show inflection" in the sidebar. — Eru·tuon 17:38, 17 June 2021 (UTC)
 * Yes it loads collapsed for me on my tablet, but on my PC it loads in full form and occupies 80% of the screen on penda (with a lot of the rest being Zulu).  i know now that not everyone sees the same thing, but i think it would be at least nice to make it load  collapsed by default on all devices.  thanks, — Soap — 21:22, 17 June 2021 (UTC)
 * Try clicking "Hide inflection" in the sidebar. That should collapse it. — Eru·tuon 21:37, 17 June 2021 (UTC)
 * Okay thanks, ...if to hide is the default behavior, I may have clicked it onto show some time ago and forgotten about it. Still i wish it were easier to see when and where a template has changed, because Ive certainly been looking at Swahili verbs before and not noticed such large templates. Thank you, — Soap — 15:50, 19 June 2021 (UTC)
 * There is a limit on how many bytes of output a template can deliver. I found that some of my cruder inflection tests hit it when I added transliteration.  Possibly that limit has changed.  As for all those forms, well every word in every language...  Some of the Indo-European inflection tables are quite impressive.   --RichardW57m (talk) 11:57, 22 June 2021 (UTC)

Categories added to documentation page because of examples
Hello,

I tried all possible combinations of noinclude's and includeonly's, but I don't seem to be able to prevent the documentation page of my template to be added to categories because of the examples shown on it. How can I present example keeping only the text output but not include the categories? Thx. Sitaron (talk) 20:10, 22 May 2021 (UTC)
 * I think you need to have your module check the namespace before adding categories. I can't think of any reason for a module to add categories in the Template namespace- really, the only namespaces with entries are mainspace (0) and Reconstruction (118). There are a few Appendix-only entries for artificial languages and the like, but not for languages that are allowed in mainspace. Chuck Entz (talk) 20:25, 22 May 2021 (UTC)
 * Thank you, it worked like a charm! Sitaron (talk) 20:58, 22 May 2021 (UTC)

quote-journal incorrect placement of translator
In isopiptesis, the article was translated by Shoemaker, but it reads as if the entire journal was translated by Shoemaker. Can this be fixed? This, that and the other (talk) 10:48, 23 May 2021 (UTC)
 * Ping This, that and the other (talk) 05:31, 1 June 2021 (UTC)
 * I'm thinking this can be fixed by placing the word "in" after the translator instead of before, but I'm not sure if this will break anything else. User:Sgconlaw you are more familiar with the semantics of these params; does this make sense? Is translator= always used for the translator of an article rather than of a collection? If so, how is the translator of the collection specified? Benwing2 (talk) 02:41, 12 June 2021 (UTC)
 * If the whole collection is translated by one person, you could argue in favour of adding a new parameter like "work-translator" that outputs the translator in its current position. Even so, it would not be absolutely incorrect to unconditionally place the translator in front of the article title, since they did indeed translate that article (along with all the rest of the articles in the work). This might be the simplest solution. This, that and the other (talk) 07:30, 13 June 2021 (UTC)

Romanian counties in Module:place/shared-data
I am currently working on etymologies of village names in Romania and the Category:ro:Villages in Romania category is getting a bit crowded, it would help to categorize them by county and, as far as I can tell, this would require a change in Module:place/shared-data, which is protected.

The county dictionary should look like this: Bogdan (talk) 12:20, 24 May 2021 (UTC)
 * Done. — Fenakhay ( تكلم معاي · ما ساهمت ) 10:43, 25 May 2021 (UTC)
 * Thank you, . The problem that we currently have everywhere "county/Vâlcea" rather than "county/Vâlcea County", so it categorizes them wrongly. It would be better to have something like there is for Russian, with the function "russian_placename_to_key" for Oblasts (making "obl/Arkhangelsk" to be categorized in Category:ru:Villages in Arkhangelsk Oblast). Bogdan (talk) 11:14, 25 May 2021 (UTC)
 * Added. — Fenakhay ( تكلم معاي · ما ساهمت ) 12:35, 25 May 2021 (UTC)
 * I changed the categories to include the suffix ", Romania", as I think it makes things a lot clearer; a category like Category:Villages in Neamț County is fairly obscure compared with Category:Villages in Neamț County, Romania. The key_to_placename entry was also missing, and I added it. I moved the existing categories created by User:Bogdan; the remaining higher-level categories will populate on Jun 4 when I run my script to create categories in Special:WantedCategories. Benwing2 (talk) 02:01, 2 June 2021 (UTC)

Categories at the bottom of each page
This is an idea I have been thinking about - can categories for each language, on a page with more than one language, be shown under each language instead of being grouped at the bottom of the page. For instance, the page for Arne has no less than six languages. Or is this a discussion for the Beer Parlour? DonnanZ (talk) 20:30, 24 May 2021 (UTC)
 * If you turn on Tabbed languages at Special:Preferences then the categories are grouped on the relevant language's tab. —Mahāgaja · talk 20:46, 24 May 2021 (UTC)
 * I can see a problem with editing each language (you can't click on the language heading), but I will give it a trial. Thanks. DonnanZ (talk) 21:40, 24 May 2021 (UTC)
 * If you click the small Edit button at the upper right of the tab frame, that opens the L2 heading for editing. —Mahāgaja · talk 09:51, 25 May 2021 (UTC)
 * Found it, thanks. DonnanZ (talk) 11:14, 25 May 2021 (UTC)

Another category problem
We have for many categories a box showing "Recent additions to the category", and another for "Oldest pages ordered by last edit". Past experience had taught me the latter box is rarely accurate, and I wouldn't mind if this feature was removed, as both boxes on the right-hand side of the page can interfere with the page layout. An example of this is Category:en:Places in Dorset, England, where the "Pages in category" listing is all in one column, instead of two, because the two boxes on the right drop below the start of the listing; the list of subcategories isn't long enough to compensate. Removal of the second box, "Oldest pages ordered by last edit", would cure the problem. Unless there are other bright ideas around. DonnanZ (talk) 21:01, 24 May 2021 (UTC)

Having modules check language name against language code in Reconstruction namespace
I just cleaned up a few Proto-West-Germanic entries that were sitting unnoticed in categories for Proto-Germanic, and it occurred to me that it would be fairly easy to flag such errors automatically: the language name is always right there between "Reconstruction:" and the the page name, and it's always the canonical name- our templates couldn't link to it otherwise.

Thoughts? Chuck Entz (talk) 09:11, 25 May 2021 (UTC)
 * I've written a program to generate a list of misplaced categories in Reconstruction entries from the SQL dump. It takes the full list of categories for each reconstruction page and eliminates any that reference the right language (part-of-speech categories, topic and list categories, and request categories like ), and eliminates tracking categories like or categories that reference something other than the language of the entry like requests for native script. Lots of special cases, but it works.
 * could also parse the wikitext and look for templates (like or ) where the language code doesn't match the title of the page. But it's a bit more indirect, requires writing out all the template-specific behavior, and I'd rather not make the poor overworked servers do this for us. Looking at the categories will at least catch many uses of the wrong language code in templates because they often add categories. — Eru·tuon 05:25, 26 May 2021 (UTC)
 * We could use a library of programs (compiled or not) and regexes to find such 'improvement opportunities', so we are not totally dependent on the authors and so we can build upon them. DCDuring (talk) 14:00, 26 May 2021 (UTC)
 * Just published the code to GitHub. This one would be easier to run than most of my programs and scripts. Most of the others, like these, require some more difficult tasks like compiling Lua and some Lua libraries written in C, and downloading modules from Wiktionary to places where Lua can find them. I could probably make it easier to set up if I spent some time figuring it out. A few people have asked to use some of my code and it was an involved process. It's even hard for me; I haven't transferred most of my scripts to my new computer so lots of my lists are out of date.
 * One option would be to put this stuff in a Toolforge tool so that multiple people could access it. Some of my scripts could be set up in my existing tool Templatehoard because they deal with templates. — Eru·tuon 18:54, 29 May 2021 (UTC)

Categories in user pages
Why is the category Category:English lemmas added to UserːEntity137/Sandbox, a user page? Does the template not check the namespace? J3133 (talk) 15:06, 29 May 2021 (UTC)
 * The title has the triangular colon ː... didn't notice until I saw it had . — Eru·tuon 17:52, 29 May 2021 (UTC)

Bug in Tibetan transliteration
Right now, for Tibetan, it auto-generates the incorrect Wylie transliteration 'ags pa. The correct form should be 'gas pa, as confirmed by the Tibetan Living Dictionary, which means there is a bug in Module:bo-translit. Can anyone fix this? RcAlex36 (talk) 02:44, 30 May 2021 (UTC)
 * Fixed. Bula Hailan (talk) 03:51, 31 May 2021 (UTC)

title: Wiktionary:Grease pit/2021/May