text:
ᏗᏓᏰᏠᎯ

Noun

 * 1) surgeon

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

title: ᏗᏓᏰᏠᎯ


text:
Wiktionary:Grease pit/2021/December

Can't add vote to active votes
Wiktionary:Votes/2021-12/User:Fytcha for admin needs to be in Votes/Active but it doesn't work when I do it. Please help. Also can we make this process easier? I don't think I've ever been able to make a vote work without asking for help and I've been here like 15 years. I follow all the instructions carefully but no dice. Equinox ◑ 03:22, 2 December 2021 (UTC)
 * I agree. Something always goes wrong with this procedure, and the error message is always hopelessly unhelpful. Mihia (talk) 22:56, 27 December 2021 (UTC)

Edit doesn't appear in history
This 22 July 2016 edit from an anon IP shows the text "1. Creatures in the pokemon game" which does not appear in the history of pocket monster, and there's no record of deletion or any logs other than creation. The anon has no contributions, not even deleted contributions, and no block or other logs. How is this possible? DAVilla 12:13, 3 December 2021 (UTC)
 * It was an edit attempt not published. AbuseFilter triggers a warning to the user trying to save such an edit. Then he can confirm to publish it anyway or not. --Vriullop (talk) 21:18, 3 December 2021 (UTC)
 * Ah OK, thank you. DAVilla 15:21, 5 December 2021 (UTC)

Contents List Pushing Down Conjugation Templates
If placed on the right via Gadgets under Preferences, the Table of Contents pushes conjugation templates like down and away from the header. --Apisite (talk) 23:02, 5 December 2021 (UTC)
 * Many such tables could be narrowed without grievous harm to appearance to coexist on friendlier terms with RHS table of contents. DCDuring (talk) 04:02, 6 December 2021 (UTC)

Wanted: Mediawiki support for the language of a section
The way Mediawiki and Wiktionary work, every entry here is completely riddled with repetitions of the language code, for example "nn" in a Nynorsk entry: ... ... ... . Isn't it time that we ask Mediawiki developers for a way to declare a whole section (from one h2 heading to the next) to have the same default value for the language parameter? It seems such a change would save us so much work, so many potential errors. Instead of passing the language code as 1st parameter (or named parameter lang=) to each template call, the templates could just use a system parameter which would somehow be set in the background for the entire section of a page (just like  is set). --LA2 (talk) 17:42, 7 December 2021 (UTC)
 * I think we went through this at some point in the past if you want to search for old discussions. DTLHS (talk) 17:45, 7 December 2021 (UTC)
 * See T122934. One long-standing blocking task (T114072) has been marked as resolved, so maybe this is getting closer. – Jberkel 17:55, 7 December 2021 (UTC)

 * Not bad. But we also don't want to litter every page and section with some . It should just work, as soon as I write ==English== or ==Nynorsk==. How hard can it be? --LA2 (talk) 18:10, 7 December 2021 (UTC)

 * One approach that has come up multiple times in the past is to have each language section be its own dedicated page -- essentially, its own container at a unique database address -- so all the data in that container would be for that language. This would make it trivial to watch only those languages one wants.  (Case in point, for myself personally, I care about a, but not about anything else on that page.  Seeing edits to entries for languages I don't care about is just noise.)  Depending on implementation, splitting languages out to their own pages might also help us deal with certain memory issues.  We could still show all languages for a given graphemic representation via transclusion.  But this has also been shot down every time it is brought up.
 * "It should just work", and "How hard can it be" -- ah, you appear to be new here. :)  (Not literally "new" per your edit history, but perhaps "new" to these kinds of discussions.)  Carry on, and good luck!  ‑‑ Eiríkr Útlendi │Tala við mig 18:57, 7 December 2021 (UTC)

 * If all content was moved to subpages, one per language section, and the main page (e.g. a, ask, good) just contained the whole would look just the same to the reader. As soon as you click "edit" next to a section heading (which would have to be present in each subpage), you would just edit that subpage. This would be possible under the current Mediawiki software, but templates would have to pick out the components of the PAGENAME. And someone would have to update the list of inclusions in the mainpage, when new sections are added or removed. It would be a big change to all editors, and you could technically still put ==Danish== in the /pl subpage.
 * In addition to my edit history, I also used to maintain my own wiki software (2001–2003), so I'm not "new" in that field either. It should be possible to make a available to templates, analogous to PAGENAME. Some templates want the name ("English"), some want the code ("en"). Translating between them should be easy. --LA2 (talk) 20:04, 7 December 2021 (UTC)
 * That's how I understood it would work (magic word or similar). Maybe we should poke them again on phabricator, now that the other ticket is resolved. – Jberkel 20:33, 7 December 2021 (UTC)
 * , I have no argument about your technical ideas or expertise. I merely meant to humorously bring up my own frustration about how such proposals have so often gotten mired in community hemming and hawing or outright opposition.  Your expressions of "It should just work", and "How hard can it be" suggest that you might not have experienced these disappointments.  The human element here often proves more difficult than the technical.  I admire your hopefulness, and would also like to see us (the EN Wikt editor community) do something more effective with our platform.  ‑‑ Eiríkr Útlendi │Tala við mig 18:46, 8 December 2021 (UTC)

Akkadian and Hittite fonts
It would be nice if we could display the appropriate fonts for Akkadian and Hittite. They currently do not represent very faithfully the language as it was written. There are some great fonts we can use here. Does anybody know how to go about this? ObnoxiousCoder (talk) 23:34, 7 December 2021 (UTC)
 * I notice that if you click the gear icon on the left sidebar, a menu pops up providing an option to apply certain webfonts. (One is a clone of Comic Sans, the other a font designed to make reading easier for those with dyslexia.) I am not sure if this list could also be expanded to include fonts for scripts like Cuneiform that aren't widely supported.
 * Alternatively, administrators could edit the site's JavaScript and CSS to load the font directly, accomplishing the same thing as the pop-up menu, although given the file size of webfonts, it seems prudent to only run such code on pages that need it. Presumably the code could detect the presence of a particular language section on a page, for example.
 * If those options are all ruled infeasible, the only solution remaining may be to ask users to install such a font locally. 70.175.192.217 19:51, 10 December 2021 (UTC)

Dutch groter als/groter dan
Hi,

I couldn’t help but notice the third entry for the preposition ‘als’. It says ‘als’ may be used as ‘than’ in nonstandard sentences. Using it like that is widely believed to be incorrect, should the entry be marked as such? The Dutch wiktionary doesn’t include ‘than’ at all.

Blue red links
When I use Cyrillic vowels with acute accents in Macedonian headword-line templates in order to indicate the stress of the forms or related terms that I am supplying, the latter appear as blue if a target page exists, even though that page itself will not have the acute accent in its title; in other words, the acute accents are appropriately stripped in the linking process. However, they still cause the page on which they appear to be assigned to "Macedonian POS with red links in their headword lines". For example, диригент currently has диригентка as a feminine equivalent in the headword line, and the link is blue because a page for диригентка exists, but if I respell it as "дириге́нтка", the link will remain blue and assign диригент to "Macedonian nouns with red links in their headword lines" even so. Furthermore, if I respell it as дириге́нтка OR диригентка, диригент will not be assigned to the aforementioned category. It would perhaps be desirable to change the code which populates red link categories so that it disregards links which actually appear as blue on the page. The whole point of creating "Macedonian POS with red links in their headword lines" was to help me and my fellow contributors to create pages which do not yet exist. With the false positives due to the use of acute accents, the utility of the red link categories is undermined. Martin123xyz (talk) 21:30, 10 December 2021 (UTC)
 * Should be fixed. Benwing2 (talk) 00:42, 13 December 2021 (UTC)
 * Thank you. It works well now. Martin123xyz (talk) 07:23, 13 December 2021 (UTC)

Pre-filling language names for RFVN and RFDN
One of the challenges faced at WT:RFVN and WT:RFDN is that it is not always easy to identify the language of each challenged term. In order to normalise a practice of writing the language name at the beginning of the listing, I'd like to suggest a preload system where the language name is automatically filled in when the user lists the RFV/RFD, similar to how rfv-sense pre-fills the text "Rfv-sense".

From a technical standpoint this could be accomplished by creating Template:rfv/preload with the content  and changing the pre-filled section creation link in rfv to something like

Then, when you click the "+" link, the text area will be pre-filled with the relevant language name, for instance:  A similar thing could be done for rfv-sense, rfd etc. This, that and the other (talk) 04:34, 16 December 2021 (UTC)
 * I like this idea, it's much better than hoping that every editor remembers to manually add something that can be automatically generated. JeffDoozan (talk) 01:08, 17 December 2021 (UTC)
 * If someone would make me a template editor I would do it myself... I have the template editor right on Wikipedia if it's any help... This, that and the other (talk) 10:42, 20 December 2021 (UTC)

 * I'd be very grateful to any template editor or administrator who would be willing to assist, whether by implementing the proposal, or by granting the rights so I can implement and test it myself. This, that and the other (talk) 11:08, 24 January 2022 (UTC)
 * I can temporarily lower the protection level of rfv to autopatrollers if you want. Just ping me when you're done, okay? — Fytcha〈 T | L | C 〉 13:22, 24 January 2022 (UTC)
 * @Fytcha: Thanks, that would be great. I want to do it for rfv-sense, rfd etc too, but let's attack one at a time. This, that and the other (talk) 13:24, 24 January 2022 (UTC)
 * Lowered it for rfv and rfv-sense for now. Ping me when you need more and/or are done with these two. :) — Fytcha〈 T | L | C 〉 13:28, 24 January 2022 (UTC)
 * @Fytcha Done those. Now and ? They're the only other ones I can think of. This, that and the other (talk) 13:44, 24 January 2022 (UTC)
 * Unprotected. — Fytcha〈 T | L | C 〉 13:48, 24 January 2022 (UTC)
 * @Fytcha The only one left now is rfc, but I can handle that myself. Thanks very much for your assistance! Maybe one day I'll get to be a big boy and edit templates all by myself. This, that and the other (talk) 14:01, 24 January 2022 (UTC)
 * You're welcome! — Fytcha〈 T | L | C 〉 14:03, 24 January 2022 (UTC)
 * @Fytcha I'm very sorry, but I've found a bug in my code: I failed to check what would happen on multi-word language names (see -lending as an example). Could you please apply the change here to the other four templates (namely, wrapping the call to langname in a  magic word? This, that and the other (talk) 02:38, 25 January 2022 (UTC)
 * Done, please verify my four changes. — Fytcha〈 T | L | C 〉 02:46, 25 January 2022 (UTC)
 * @Fytcha looks great, thanks! This, that and the other (talk) 02:55, 25 January 2022 (UTC)
 * There are now several non-mainspace pages in CAT:E due to the impossibility of infering language codes for rfdo. This needs to be addressed. It seems silly to require adding "und" as a language code in such cases. Chuck Entz (talk) 14:58, 24 January 2022 (UTC)
 * @Chuck Entz That's because people are putting in information that is not a language code into the first parameter. As far as I can see, this would never have worked even before my changes, so I have just edited these invocations in order to fix them. Apologies for the mess! This, that and the other (talk) 00:30, 25 January 2022 (UTC)

Referencing a glossary in Wikisource
I'm currently trying to create an entry for an Old English word whose gloss can be found in a glossary on Wikisource. Would someone be able to help me make a reference template for this? Here is the glossary: Bright's Anglo-Saxon Reader/Glossary

Make Template:lb stop categorizing in the Citations namespace.
If Template:lb is in the Citations namespace, it will currently categorize the same way it would in the mainspace. For example, a label of "Scouting" in Citations would put a Citations page in Category:en:Scouting. Any way to solve this issue? And are there other templates that cause similar issues in the Citations namespace that now would be a good time to address as well? PseudoSkull (talk) 18:45, 22 December 2021 (UTC)

Fully Implementing Template:R:Century 1911
, many of the parameters listed in the documentation for Template:R:Century 1911 have not been implemented, see the "Examples" section of the documentation for straightforward evidence. Would anyone be willing to implement them, maybe in a way similar to that of Template:R:Century 1914? Thank you and take care. —The Editor's Apprentice (talk) 02:13, 21 December 2021 (UTC)
 * Done. I removed  as what is actually being referenced is Century 1911 (which will never change), not the website itself. This, that and the other (talk) 11:26, 21 December 2021 (UTC)
 * Fair enough! Thanks for the quick work and response. —The Editor's Apprentice (talk) 21:00, 21 December 2021 (UTC)
 * While we are at it, could we add a parameter to indicate whether the relevant entry is in the main Dictionary, the Supplement, or both? At present the user has to click through to one or the other as the url is not present. At some point, could the template be enhanced to automagically go to the actual entry page instead of requiring the user to click through or the url to be added? DCDuring (talk) 22:39, 21 December 2021 (UTC)

Wikidata integration?
Hi. I have been active on Wikidata for a while and recently the connection from Wikidata to WT went live on 2 Wiktionaries.

This is an important step in separating view and model IMO and makes wiktionaries potentially a lot more valuable when they present data that is stored in Wikidata instead of mixing data and presentation as we do now.

ML and NLP seems to me to be on the rise and good dictionaries for stemming etc. are missing for many languages. WT and WD can help build a better world with good multilingual support easily available if we work together. Do we have consnsus for starting this transition?--So9q (talk) 09:44, 22 December 2021 (UTC)
 * I think most people aren't aware what's going on, can you give a short summary? As usual, there has been very little information from the Wikidata project itself, and very few editors are active in both. Will it be possible to edit data on Wiktionary, or do you always have to go through Wikidata? Are there statistics/overviews on what kind of data is currently available, ordered by language? Where does it make sense to use the data? – Jberkel 00:08, 23 December 2021 (UTC)

 * Certainly there is no such consensus. In my view it is a great strength to be machine illegible. DTLHS (talk) 01:41, 23 December 2021 (UTC)
 * I think on a basic level that's the fundamental difference between the projects: Wiktionary is geared towards human readers, like traditional users of a paper dictionary, whereas Wikidata optimizes for data reuse, like above-mentioned ML models/algorithms. In the future probably fewer people will care to know what part of speech a word is; AI-based auto-correction tools do the job for you. – Jberkel 08:36, 23 December 2021 (UTC)
 * Exactly. The strength is resistance to colonization by machine learning zealots. DTLHS (talk) 17:45, 23 December 2021 (UTC)
 * I would be very interested in this. Separating the model from the view would have benefits both for ML and Wiktionary itself, but it would be an enormous undertaking, as the current dataset is a Mandlebrot of edge cases. As the previous responses have mentioned, it's build by humans for humans and its greatest strength is the ease with which a new user can add and edit not only the data but also the structure and I doubt there would be any consensus for changes that would dramatically alter that. Can you provide some more information about which other projects were migrated, how it was done, and how their communities have responded? JeffDoozan (talk) 12:32, 23 December 2021 (UTC)
 * If Wikidata can use what we have, more or less as is, why do we even need to cooperate? If there are relatively minor changes that would make it easier for Wikidata to do so, couldn't they be addressed on a case-by-case basis? Some higher degree of uniformity in presentation might be acceptable. I am quite sure that there is no consensus here to do any violence to any human language to fit it into any particular model that Wikidata might have.
 * So far, in the area of taxonomic names, one of the most highly structured sublanguages, I have not been impressed by the quality of some of what Wikidata had to offer. Images associated with species were sometimes wrong and images associated with genera were not of type species, even though type species pictures were available in Commons. For taxa I have tried to use drawings where possible instead of photographs, but Wikidata didn't seem to help with that. The one area for which Wikidata might help is the collection and maintenance of the various identifiers used by different taxonomic databases for taxonomic names. DCDuring (talk) 16:23, 23 December 2021 (UTC)
 * What kind of quality control does Wikidata have when it comes to foreign language translations of terms? I personally have little trust in their correctness, see for instance the German protologism here. I would be strongly opposed to bringing the foreign language data from Wikidata here to Wiktionary. Fytcha (talk) 17:02, 23 December 2021 (UTC)
 * What you linked to is the Wikidata representation of Wikipedia, the actual lexical data is stored in a different namespace . For example, for there is wikidata:Lexeme:L1836. That entry has gender information, a Duden identifier and inflected forms with pronunciation data. I'm not sure if there is a way to specify translations in WD, but there is a link to the "concept" of alcohol Q47146337 (“active ingredient in alcoholic beverages”) which could be used to find equivalents in other languages.  The primary sense ("ethanol") is not listed in WD for that lexeme. – Jberkel 17:31, 23 December 2021 (UTC)

A small thing with the rfap template
It would be nice if instead of "if you have a microphone", it also read "you are a native speaker with a microphone". We don't want to encourage people to record for languages they don't really speak. Vininn126 (talk) 13:59, 22 December 2021 (UTC)
 * I've gone ahead and implemented the change. Good call. Ultimateria (talk) 23:06, 22 December 2021 (UTC)

Question about TOCs
It appears all entries that contain definitions for multiple languages have TOCs. What I'm confused by is the one-language words. Some have TOCs, some don't. To use some examples from Special:Random, demonología in Spanish does not have one, but boaro in Italian does. 70.172.194.25 02:53, 25 December 2021 (UTC)

 * I would guess that it has something to do with the number of headers, since those are the only things that show up in TOCs. Of your two examples, demonologia has only the one l2 header with two l3 headers, while boaro has one l2 header with three l3 headers and an l4 header. I added an extra l3 header to demonologia in preview, and the system displayed a TOC as soon as I clicked preview again. Likewise, I commented out everything between the "Italian" and "Noun" headers in preview, and the TOC disappeared- but it came back when I un-commented the "Pronunciation" header and clicked preview again. I don't know if it matters how many are which level, but you can test it for yourself by trying all kinds of combinations in preview, as long as you don't click "Publish changes" to save them. Chuck Entz (talk) 05:36, 25 December 2021 (UTC)

 * See . Creating a ToC on very short pages would be a counterproductive waste of space. Equinox ◑ 05:39, 25 December 2021 (UTC)

Two new Russian categories - one new and one to be created yet
I have just created a new Russian category: Category:Russian abstract nouns, which should be able to cover a large number of nouns formed from adjectives (-ость adjectives) (as a shortcut, rather than creating a full definition, which is just a repetion of adjective senses).

The category seemed a bit problematic, so I used:

Not sure if this is ideal.

Also, I used verbal noun templates on some new words like :. The term wasn't added but I'd like it to be added to Category:Russian verbal nouns automatically.

Are you happy for these new categories to be added? Please fix if anything needs fixing. --Anatoli T. (обсудить/вклад) 04:47, 27 December 2021 (UTC)
 * The categories seem OK with me and I can fix the category code to define them properly. However, I'd prefer it if you can gloss the terms whenever possible, e.g.

# : meticulousness or # If there are several senses, I think it's fine to gloss the most common ones and write   to stand for the rest. Also, I'm curious why you are using instead of just  (which already categorizes properly). Finally, is it correct to gloss a noun like as the verbal noun of both  and, since it's morphologically derived from the former rather than the latter? If so I should probably fix the form-of templates so you can write something like or even  and have it work correctly. Benwing2 (talk) 05:08, 27 December 2021 (UTC)
 * I agree with your points and I started changing. I used since it's the way it was used so in Macedonian and other entries (probably not categorising by this template call) and I wondered why Russian lacks this category.
 * Abstract nouns in and verbal nouns in  are mostly predictable in how they are formed from adjectives and verbs and have predictable declension and stress patterns, so it would be ideal if these could somehow be added to the accelerated entry creation or generated by bots but I have no idea how difficult it is. :) --Anatoli T. (обсудить/вклад) 05:27, 27 December 2021 (UTC)
 * It is pretty easy to add accelerator support for abstract nouns and verbal nouns (and to add a parameter to to support specifying verbal nouns in the headword). It's also not that difficult to support generating them programmatically if you specify + or +; for the latter case I can reuse the code that generates past passive participles since as far as I know the verbal noun can be derived fairly directly from the participle. I will probably add the accelerator support first and then the   support. Once this is done I will look into modifying existing entries by bot to incorporate /. Note that I did this already for . (In that case I did it semi-automatically and manually cleaned up the entries in the process, but there are too many nouns in -ость and -ение/-ание/-яние/-тие to do it this way: about 900 in -ость, about 950 in -ение, about 600 in -ание, about 100 in -тие and maybe 50 in -яние.) Benwing2 (talk) 07:04, 27 December 2021 (UTC)

Can anyone explain what/where this is, and how I edit its content? Mihia (talk) 17:27, 27 December 2021 (UTC)

 * It's a template: Template:U:en:who and whom. "U" is a pseudo-namespace for usage notes, like "R" for references. This, that and the other (talk) 06:11, 28 December 2021 (UTC)
 * Thanks, duh, I'm sure I searched for "template:u:..." and nothing came up, but now it does. Maybe I'm going mad. Mihia (talk) 09:42, 28 December 2021 (UTC)

Dodgy WT:ACCEL
I auto-made sobrevaluarlas, and it looks dodgy. Compare comerlas, which is in the format I was expecting to see. I can't fix them! Br00pVain (talk) 21:11, 27 December 2021 (UTC)

Making Template:quote-av handle non-fiction works better
Currently, Template:quote-av prefaces quote with "spoken by :" if values for the  and   parameters are given. If the  parameter is not given a value, no preface occurs. This function, formatting, and naming of parameters makes quoting non-fiction audio-visual works, as well as fiction works were someone plays themself, awkward. Is someone willing to modify the template, as well as Template:cite-av, to remedy the situation? One solution for the formatting would be to switch the parameters so that the format is "spoken by :" and have it display if there is no role parameter as "spoken by :". If there is a role, but no actor given it could be "spoken by (role):" Maybe a good alternative name for the parameter  would be. (As a side note, if a signed langue is being quoted, I don't know how much it makes sense to say the quote is "spoken" by someone. Maybe a parameter called  could be created as a boolean if set to   or   it replaces the word "spoken" with "signed".) Thanks and take care. —The Editor's Apprentice (talk) 00:02, 29 December 2021 (UTC)

Fixing plurals in ms-noun
When this template is used in Jawi (Arabic script) lemmas, the plurals are displayed as two like found in. Actually, plurals in Jawi is only and not. The latter is only used for Rumi (Latin script). Please remove the latter for Jawi lemmas. --Tofeiku (talk) 03:15, 29 December 2021 (UTC)

Community Wishlist Survey 2022 is coming. Help us!
The Community Wishlist Survey 2022 starts in less than two weeks (Monday 10 January 2022, 18:00 UTC). We, the team organizing the Survey, need your help.

Only you can make the difference

How many people will hear and read about the Survey in their language? How many will decide to participate? Will there be enough of you to vote for a change you would like to see? It all depends on you, volunteers.

Why are we asking?

 * We have improved the documentation. It's friendlier and easier to use. This will mean little if it's only in English.
 * Thousands of volunteers haven't participated in the Survey yet. We'd like to improve that, too. Three years ago, 1387 people participated. Last year, there were 1773 of them. We hope that in the upcoming edition, there will be even more. You are better than us in contacting Wikimedians outside of wikis. We have prepared some images to share. More to come.

What is the Community Wishlist Survey? It's an annual survey that allows contributors to the Wikimedia projects to propose and vote for tools and platform improvements. Long years of experience in editing or technical skills are not required.

Thanks, and be safe and successful in 2022! SGrabarczuk (WMF) (talk) 03:15, 29 December 2021 (UTC)

Monthly Discussion Pages
You may not be aware of it, but monthly discussion pages wouldn't be on anyone's watchlist unless they were created in a certain way before being used. For the second year in a row, no one has done this. Last year, I went ahead and created all the pages at the last minute to avoid having new discussion stop showing on everyone's watchlist. This year, I created just the ones for January, but would like us to set up a process so it doesn't depend on one person.

Note that failing to do this won't prevent the creation of the new pages, but the new pages won't be on anyone's watchlist.

It's not all that complicated: it takes advantage of the fact that moving a page causes every watchlist that includes the old location to have the new location added with the same settings as the old one, but without removing the old one. There are three steps required for each page created: Once the January page is finished, you can then use this page to create the next one and the next one, etc. As long as the chain of moves is unbroken, they will all be in the same watchlists.
 * 1) Move the old page to the new one, leaving a redirect
 * For instance, you would move Wiktionary:Grease pit/2021/December to Wiktionary:Grease pit/2022/January.
 * Wiktionary:Grease pit/2021/December is now a redirect to Wiktionary:Grease pit/2022/January
 * 1) Move the new page back to its old location over the redirect, leaving a redirect behind
 * Wiktionary:Grease pit/2021/December is now the same as it was before you moved it away and moved it back.
 * Wiktionary:Grease pit/2022/January is now a redirect to Wiktionary:Grease pit/2021/December.
 * 1) Replace the redirect in the new location with discussion month

The series in question:
 * 1) Beer parlour
 * 2) Etymology scriptorium
 * 3) Grease pit
 * 4) Information desk
 * 5) Tea room

Some considerations:
 * It's best to have as little time as possible between the first and second steps when an active discussion page is moved, to avoid edit conflicts
 * I'm not sure if it's necessary, but: to be safe, I would recommend starting with the most recent active page in a series, so the status in everyone's watchlists is as up to date as possible.
 * This needs to be done by an admin: the relevant pages are protected against moving by anyone else.

This whole process was started by who has said she will share her script for doing this. Chuck Entz (talk) 19:08, 31 December 2021 (UTC)
 * I did share the script, but I forgot where. In some BP or GP page somewhere. —Rua (mew) 20:18, 31 December 2021 (UTC)

title: Wiktionary:Grease pit/2021/December


text:
ᏓᏁᎶᏗᎭ

Verb

 * 1) he/she/it is playing with him/her/it

title: ᏓᏁᎶᏗᎭ


text:
Wiktionary:Grease pit/2021/January

Combining diacritics
brought a very strange redirect page to my attention. It's for a combining diacritic that puts a double dot under a letter, as in "x" vs. "x̤". This indicates murmured voicing, and is pretty much equivalent to the letter it redirects to, ʱ. I have a few questions:

What do we do with combining diacritics? While it's technically possible to search for this character, as a practical matter it's very difficult to copy it from anywhere using the normal user interface. We have it in the edit tools at the bottom of the edit window (under "IPA and enPR"), but if you run into it use somewhere combined with another character, I don't know of any way to select it in order to copypaste it without selecting the other character. I also have my doubts as to whether one can link to it using wikisyntax. The usual method, [[̤]], displays it, but there's no hyperlink.

Assuming someone knows how to isolate the character and get it into the search box, is it a good idea to have this as a redirect to a free-standing character that looks nothing like it? Should we put an character info box for its code point at the target page? Or is this a case for "Unsupported titles"? Chuck Entz (talk) 09:52, 1 January 2021 (UTC)

 * For the record, there is actually a link above in the example of the normal wikisyntax, its probably just too tiny to click on manually. The Linkclump chrome extension can be used, or you can check the dom manually DannyS712 (talk) 09:57, 1 January 2021 (UTC)

 * Specialized IPA keyboards should be able to create a standalone combining diacritic. —Suzukaze-c (talk) 10:08, 1 January 2021 (UTC)
 * As I said, it's technically possible to do all the normal things, but as a practical matter, if you know enough to figure out how to search for it, you probably already know what it means. Chuck Entz (talk) 10:15, 1 January 2021 (UTC)

 * Isn't this what U+25CC is for? If we want to have a separate entry for U+0324  (as opposed to redirecting to ʱ, since the latter really isn't used for breathy-voiced vowels), couldn't/shouldn't it be at ◌̤? —Mahāgaja · talk 10:24, 1 January 2021 (UTC)
 * Yeah, I'm inclined to think the content (and hence, redirect target) should either be at ◌̤ or at an Unsupported Title, rather than just redirecting to a different character, and ◌̤ has the advantage of being a regular, mainspace entry. What we really need to consider, if we're trying to make this findable / reachable, is creating redirects or see-also links from any characters it appears under, like Chuck's example of x̤. - -sche (discuss) 17:34, 4 January 2021 (UTC)

WOTD “yesterday” link
It should link to “Wiktionary:Word of the day/2020/December 31”, not “Wiktionary:Word of the day/2021/December 31” (Main Page). J3133 (talk)
 * The same thing happened on Dec 31, when "tomorrow" linked to 1 Jan 2020, instead of 2021. The right word, new dawn, has appeared today however. DonnanZ (talk) 23:54, 1 January 2021 (UTC)

Discussion Monthly Pages
I move-protected all the discussion forums after a page-move vandal hit some of them, which makes the usual method of creating these using a bot more complicated. Just to be on the safe side, I did my best guess at an imitation of the technique (move the last page of the previous year to the name for the new monthly page, move it back, move the redirect at the name for the new page to the name for the next page, move that to the next page name, etc, then replace the contents of the string of redirects with discussion month).

I'm pretty sure the desired effect of adding new months to everybody's watchlists was accomplished for the January pages, but beyond that, I'm not so sure. Since my account settings add pages I create to my watchlist, I have no way to check- they would be added to my watchlist either way. Given the importance of having all the monthly discussion pages on everybody's watchlists, this should be checked, and, if need be, fixed. Chuck Entz (talk) 17:18, 1 January 2021 (UTC)
 * All 2021 pages are on my watchlist. J3133 (talk) 17:27, 1 January 2021 (UTC)

Category:en:Places in England
Message: Lua error: not enough memory. It may be a temporary error. DonnanZ (talk) 23:58, 1 January 2021 (UTC)
 * It's OK now. DonnanZ (talk) 06:12, 2 January 2021 (UTC)

Wrong entries in Category:German multiword terms
The category contains many terms which aren't multiword terms.

Most compounds and derivatives (Category:German compound words; Category:German words by prefix, Category:German words by suffix) aren't multiword terms, and a hyphen inside of a compound or derivative doesn't make it a multiword term.

See and compare: Would be inside the category or not? I guess because there's no hypen inside the term, it wouldn't be inside of the category. vs. vs. /
 * vs.
 * vs.
 * vs. several terms in Category:German words suffixed with -frei
 * vs.
 * vs. (from, *Bestell is not a word and  only a form of )
 * (the - is not used for combining but for censorship like * in f*ck) vs.

--Der Zeitmeister (talk) 10:26, 2 January 2021 (UTC)
 * (there are no *Tic/tic, *Tac/tac and *Toe/toe)

 * Same deal in Proto-Eskimo. I don't know what a hyphen indicates in Proto-Eskimo, but these words aren't indicated to be polymorphemic.__Gamren (talk) 18:41, 2 January 2021 (UTC)
 * Even in English, G-d isn't a multiword term. —Mahāgaja · talk 18:56, 2 January 2021 (UTC)
 * The algorithm isn't very smart about handling hyphens. You can add a language to  in Module:headword/data to disable adding a term to 'multiword terms' if it has a hyphen in it, but I'm not sure how to make it smart enough to handle all the cases above. Maybe it should be conservative and not add a page to 'multiword terms' based only on a hyphen. What do people think? Benwing2 (talk) 02:27, 4 January 2021 (UTC)
 * I think it would be better to err on the side of exclusion from the category. It's much easier to add de manually to an entry that requires it than to remove it from one to which it's added automatically. —Mahāgaja · talk 07:58, 4 January 2021 (UTC)
 * OK, I added German and Proto-Eskimo to, and added a flag nomultiwordcat to  to disable the category on a case-by-case basis. (There was already noposcat; I also added nogendercat to disable auto-addition of gender-based categories such as Category:German masculine nouns.) I think it makes sense at least for English to have Category:English multiword terms added based on hyphens, since the vast majority of hyphenated words are in fact multiword terms. However, if all this is still insufficient, there are some other things that could be done: (1) have the code check to make sure all hyphenated components exist as words; (2) reverse the sense of   so it functions as an inclusion list rather than an exclusion list. Note that (1) wouldn't catch G-d, but it would catch cases like g-ddamn. Benwing2 (talk) 02:45, 5 January 2021 (UTC)

 * Some other languages where this is an issue are being discussed at Information desk/2021/March. - -sche (discuss) 22:27, 7 March 2021 (UTC)

Category:Hawaiian Creole language
The relevant Lua code needs to be updated to get rid of the module error that currently occurs when attempting to create this category with. I'm not familiar with any of the Lua code on this site so I don't know how to resolve this problem myself at the moment. User: The Ice Mage talk to meh 17:58, 3 January 2021 (UTC)
 * No Lua work necessary. The error message said to add the name of a country, and I put in and it worked. — Eru·tuon 18:05, 3 January 2021 (UTC)

Category:Guamo language's family
Wikipedia lists the family as Guamo–Chapakuran with a question mark...would someone be able to add data for that language family to Wiktionary, or is it better not to due to uncertainty or something? User: The Ice Mage talk to meh 20:10, 3 January 2021 (UTC)

I also have a different question relating to Guamo: I can see it's an extinct language, so I'm wondering how do I get the category page to say that? User: The Ice Mage talk to meh 20:50, 3 January 2021 (UTC)
 * Add 1 to auto cat. —Mahāgaja · talk 21:28, 3 January 2021 (UTC)

Category:Kamakã languages
Another thing I found on Special:WantedCategories for which data is apparently not set up yet. Wikipedia says it's a subfamily of Macro-Jê languages. User: The Ice Mage talk to meh 20:22, 3 January 2021 (UTC)

Category:Olukumi language
When trying to create this using it gives an error that references ...does anyone know how to fix this? User: The Ice Mage talk to meh 16:30, 4 January 2021 (UTC)
 * The error occurs because our canonical spelling of the language name is Ulukwumi. So either the category needs to be renamed CAT:Ulukwumi language or the canonical name needs to be changed at Module:languages/data3/u. —Mahāgaja · talk 17:35, 4 January 2021 (UTC)

Not enough memory
Well...a. What do we do with a page where it starts in entry 97? Esszet (talk) 01:27, 5 January 2021 (UTC)
 * Does anyone know what to do? This is a huge problem for the page. Esszet (talk) 02:13, 9 January 2021 (UTC)
 * Yes, there are a handful of pages like this (and there will only be more in the future). One solution is to create separate pages (messy but it works) and the other is to have someone working on the backend fix it (cf. T188492). —Justin ( koavf ) ❤T☮C☺M☯ 04:31, 10 January 2021 (UTC)
 * According to Aklapper, it needs to be fixed here. Esszet (talk) 00:45, 12 January 2021 (UTC)
 * Isn't splitting pages according to language only a messy solution because it breaks with our established format? What if we moved all our entries to a new namespace, say Word: or Dictionary:, with the same pagename scheme as reconstructions, and then keep mainspace as disambiguation pages?__Gamren (talk) 21:59, 29 March 2021 (UTC)

Template:R:fr:GDT/testcases
This page has been cluttering up Category:ParserFunction errors since mid-November. Is there any way to control what shows up in that category like there is with Category:Pages with module errors? Or do we need to edit this to get rid of the test cases? Chuck Entz (talk) 15:24, 5 January 2021 (UTC)

Invalid ISBN
If you go to the page, I have added an example sentence under the definition for Etymology 1 under the Chinese header. (Put aside whether this is a good example sentence for the moment- I plan to use this book elsewhere anyway.) There's a message there that says "Invalid ISBN". According the book itself, the ISBN of the book is 7-80053-740. The ISBN can be seen here:. There is no guidance at Template:ISBN for what I should do. The link on the Template:ISBN page to the ISBN Converter no longer works. I found an online resource that says that the ISBN for this book is not 7-80053-740 but is instead 7-80053-740-1. Should I trust that source or the book itself? Seeking guidance generally. --Geographyinitiative (talk) 11:02, 9 January 2021 (UTC)
 * An ISBN has only 10 or 13 digits (one introduced  after finding out 10 digits is too little for all books in the world). The last digit of either an ISBN-10 or ISBN-13 is a check digit calculated from the other digits, serving for computers to calculate whether and display if there might be a typo. Therefore the first ISBN you write here is an incomplete ISBN whereas only the latter can be perfect. Fay Freak (talk) 11:51, 9 January 2021 (UTC)
 * Thank you for your informative response. Based on what you have said, is the nine digit ISBN I'm looking at here "wrong"? Did the publishers of this book make a "mistake"? Or did they omit something that is obvious? What should I do if I run into nine digit ISBNs in the future? Should some kind of note be added to Template:ISBN? --Geographyinitiative (talk) 11:55, 9 January 2021 (UTC)
 * It’s not your fault in any case if an ISBN given by the book publisher is invalid, so there is nothing to worry. Although you can brute-force check the digits 0-9 to whether they validate. (In ISBN-10 the check digit is not only 0-9 but also possibly X.) Fay Freak (talk) 12:00, 9 January 2021 (UTC)
 * Corrected per WorldCat. —Suzukaze-c (talk) 12:02, 9 January 2021 (UTC)

I am learning a lot about ISBNs. You can see some more of my bad work at Category:Pages with ISBN errors. I would like to solve all these problems somehow and create a note on Template:ISBN that gives guidance for what to do when you get "Invalid ISBN" (maybe as simple as "go to Wiktionary Grease Pit" or "look it up at xxx database") --Geographyinitiative (talk) 12:09, 9 January 2021 (UTC)

Question about 2 language categories from WantedCategories
I have found 2 instances where Wiktionary is using one name for a language, but Wikipedia is using another, with the one used by Wiktionary just being a redirect. Does anyone have opinions on which names we should use on Wiktionary? User: The Ice Mage talk to meh 16:51, 9 January 2021 (UTC)
 * Eastern Karaboro (redirects to Kar language)
 * Fortsenal (redirects to Kiai language)

Incidentally, I just noticed that Wiktionary is already using the name Western Karaboro for a related language. User: The Ice Mage talk to meh 16:53, 9 January 2021 (UTC)

swapping Recht haben and recht haben possibly with their history
In Duden online, the recommended form is the lowercase one, so the uppercase form should be the "Alternative form" and the lowercase form, the primary entry.

Due to the swapping, I don't know how moving could be done (unless I use a temporary third pagename, which is deleted afterwards). Obviously, a copy-paste wouldn't be very elegant, and the history of the two pages should be preserved. I'd like to ask someone with the right authorization to do it more professionally. Thank you in advance. Adam78 (talk) 17:41, 9 January 2021 (UTC)
 * I don't think they should be swapped. The only thing changing is the definition and possibly the etymology- the conjugation tables are the same. Chuck Entz (talk) 18:02, 9 January 2021 (UTC)

 * According to korrekturen.de "Recht haben" was the single prescribed form from 1996 (1st Rechtschreibreform) till 2004/2006. On the other hand, "recht haben" is the standard form since ages. Possible this info should be in the entries in some way, but possible better sourced and with 2004 or 2006 instead of "2004/2006". --46.91.98.89 11:57, 11 January 2021 (UTC)

Label modules are driving me up the wall
I am trying to add Category:Extremaduran Spanish to entries via a label, such as at. I would think that it should be added to Module:labels/data/subvarieties but note that labels "Andalusia" and "Canary Islands" are not at this module: instead, they are at Module:labels/data/regional. I added it there but there is no category that is created, nor is it linked in the label. What do I do to fix this? I have been running around trying to find what turns " into a valid label that creates a link and adds an entry to Category:Canarian Spanish but I can't find it to save my life. Help, please. —Justin ( koavf ) ❤T☮C☺M☯ 04:30, 10 January 2021 (UTC)
 * Also Category:Huelvan Spanish and this edit. —Justin ( koavf ) ❤T☮C☺M☯ 04:47, 10 January 2021 (UTC)
 * Also Category:Riojano Spanish; I didn't even bother adding it to a module this time because there's no point in going far off track. —Justin ( koavf ) ❤T☮C☺M☯ 04:58, 10 January 2021 (UTC)
 * Category:Belizean Spanish works! Caramba. —Justin ( koavf ) ❤T☮C☺M☯ 07:21, 10 January 2021 (UTC)
 * To add: Category:Leonese Spanish, Category:Palencian Spanish, Category:Zamoran Spanish, Category:Cantabrian Spanish. —Justin ( koavf ) ❤T☮C☺M☯ 09:17, 10 January 2021 (UTC)
 * Category:Rioplatense Spanish and if I can find attestable terms, Category:Brazilian Spanish and Category:Saharan Spanish. Any help? —Justin ( koavf ) ❤T☮C☺M☯ 03:48, 14 January 2021 (UTC)
 * Maybe also Category:Equatoguinean Spanish. – Jberkel 11:04, 9 February 2021 (UTC)

 * IIRC one of the two modules named above doesn't actually do anything / get called on(?). (My impression is that they should be combined.) - -sche (discuss) 09:40, 9 February 2021 (UTC)

Template:R:fa:Gazophylacium
R:fa:Gazophylacium links to the wrong page because the pages in the book run backwards. See for example. The link to page 297 generates a Google Books URL with pg=PA297 which links to the page numbered 220. The correct URL contains pg=PA220 to link to page 297. I think this is impractical to do right with templates alone, but maybe somebody here has an idea. Vox Sciurorum (talk) 20:03, 10 January 2021 (UTC)
 * I linked the archive.org version instead where the book does not run backwards. --Vahag (talk) 06:16, 11 January 2021 (UTC)

Gëzuar Vitin e Ri and its links that don't work
The entry in the title shows the expression with a link under each word, namely Gëzuar Vitin e Ri. Now, the entries Gëzuar and Vitin don't exist, because Gëzuar is capitalized and the entry is gëzuar without the capital, and vitin is an inflected form of vit (and also it's capitalized, vitin exists). As for Ri, it should link to ri. I would correct that myself, but I find myself confronted by an opaque template, namely { { head|sq|interjection } } outputting. What can we do to fix this? MGorrone (talk) 14:17, 11 January 2021 (UTC)

Also, why does that template output the expression with links at the entry, but this bold "January" here in the GP? MGorrone (talk) 14:17, 11 January 2021 (UTC)
 * I fixed the links. sq without an explicit   argument takes the name of the current page (here, January) and formats it by the default method of breaking the word at spaces and linking the components.   If you add a   argument you can control the formatting yourself.  Vox Sciurorum (talk) 14:20, 11 January 2021 (UTC)

Category:en:Dictionaries
Someone has to update the relevant Lua modules so that this category can be like all other topical categories, being set up by simply using. I would do it, but I couldn't quite figure out what module to edit...I think the description " terms related to dictionaries." would be fine, and we should keep its parent categories as they are right now. User: The Ice Mage talk to meh 15:39, 11 January 2021 (UTC)

Esperanto terms spelled with Ĥ
The basic Esperanto alphabet contains the letter Ĥ. It is the most uncommon letter of the alphabet. I think it would be a good idea to automatically populate the category Category:Esperanto terms spelled with Ĥ with words that contain the letter. This can be acomplished by adding the following piece of code the line 136 of the module Module:eo-headword. The page is protected, so I cannot add or test this proposal myself.

if mw.ustring.match(PAGENAME, "[ĥĤ]") then table.insert(tracking_categories, "Esperanto terms spelled with Ĥ")

22:39, 12 January 2021 (UTC)

 * You should edit Module:languages/data2. I have added the standard characters A-PRSTUVa-pRSTUVĉĈĝĜĵĴŝŜŭŬ. DTLHS (talk) 22:44, 12 January 2021 (UTC)

 * I also found that location, but I was unsure if that is the right location, since Ĥ is a standard character of Esperanto, it is not like Æ in English. 23:15, 12 January 2021 (UTC)

 * I think the letter Ĥ should be included among the standard characters at Module:languages/data2, because is part of the standard alphabet in Esperanto. --Rajzin (talk) 23:21, 12 January 2021 (UTC)
 * It doesn't matter. The only thing this field is used for is to populate these categories. DTLHS (talk) 23:26, 12 January 2021 (UTC)
 * Can you also add 0-9 to the standard characters? 02:40, 13 January 2021 (UTC)
 * Added. DTLHS (talk) 02:42, 13 January 2021 (UTC)
 * I agree that the proposal is probably worth implementing. Ĥ may not be a nonstandard character in Esperanto, but it is subject to some controversy in the Esperanto community - you can more or less divide Esperanto speakers into people that use Ĥ and people that don't.
 * Ĥ is the rarest letter by far and considered by some to be difficult to pronounce, making some Esperanto speakers advocate avoiding its use whenever possible (usually by changing Ĥ to K), leading to a whole class of alternative forms. (ĥemio vs. kemio, teĥniko vs. tekniko, etc.) Other speakers don't agree, and actively support keeping the letter alive.
 * So in my opinion there is real practical use to having an exhaustive list of Esperanto words on Wiktionary that contain Ĥ. --Rajzin (talk) 23:21, 12 January 2021 (UTC)

Add Italian standardChars at Module:languages/data2
In order to make Category:Italian terms by their individual characters automatic. J3133 (talk) 08:57, 13 January 2021 (UTC)
 * Added. DTLHS (talk) 03:52, 14 January 2021 (UTC)

Requesting a new parameter in template "inflection of"
I'd like to request the addition of a new parameter in. The name of the parameter might be 2p or 2po, the displayed text should be second-person-object form and the entire text should be linked to Appendix:Glossary. An example entry would be látlak. A discussion about this parameter is here: Template talk:hu-conj-unified/doWork. Thank you. Panda10 (talk) 18:48, 14 January 2021 (UTC)

I think Module:form_of/data and/or Module:form of/data2 need to be extended. I don't have the permission to edit them. If we check their history, we can find people who are authorized and whom we might personally contact. Adam78 (talk) 13:59, 15 January 2021 (UTC)

 * I added it to Module:form of/data2 and I updated látlak. It worked. Panda10 (talk) 18:29, 15 January 2021 (UTC)

Great! Thank you! :) Adam78 (talk) 18:38, 15 January 2021 (UTC)

Add Category:Terms spelled with * (by language)
E.g., “Category:Terms spelled with K (by language)” would contain the subcategories Category:Chinese terms spelled with K, Category:Irish terms spelled with K, Category:Italian terms spelled with K, Category:Latin terms spelled with K, Category:Portuguese terms spelled with K, Category:Spanish terms spelled with K, and Category:Welsh terms spelled with K. J3133 (talk) 08:48, 15 January 2021 (UTC)

Here, I presume: Module:category tree/poscatboiler/data/characters. J3133 (talk) 10:45, 16 January 2021 (UTC)
 * I fixed up your code. The original reason for not having an umbrella category like this is because of Japanese kanji character categories like Category:Japanese terms spelled with 守; we'd end up with thousands of new umbrella categories, each holding a single Japanese category. I made it so that Japanese and Okinawan categories don't have an umbrella category, and other languages do. In general, all you need to do to add an umbrella category is to remove  and add   or similar (and add a raw entry for "Terms by their original characters subcategories by language"). In this case, it was trickier because the existing code assumed that there was a language in the category and used it to italicize and link the character in the description, breadcrumb and title. I changed it to use Translingual as the language for this purpose for the umbrella categories. Benwing2 (talk) 19:18, 17 January 2021 (UTC)

Question on customized acceleration layout and form creation with a bot
Are the language subpages to Module:accel for specific customization for a language? For Hungarian Module:accel/hu was recently deleted because I assume the standard code handled it. What type of customization is allowed? Whatever can be achieved with Lua? I'd like to understand it because the new conjugation acceleration added to would need some adjustments. Discussion about the current issues can be found in the Acceleration testing section on Template talk:hu-conj-unified/doWork. If we wanted to create the verb forms with a bot, would it be connected to the acceleration function or the bot works entirely separately? Panda10 (talk) 00:40, 16 January 2021 (UTC)

Bookmarklets
Bookmarklets and Help:Tips and tricks/Bookmarklets are two rather old pages providing some bookmarklets. Do these still work at all? WP's article on explains that increased browser security now tends to prevent this technique from working. Should the pages be retired or updated in some way? Equinox ◑ 10:01, 16 January 2021 (UTC)

Not enough memory II
According to the people at the Phabricator, the memory issues we're having (see a and i) need to fixed here. Esszet (talk) 16:51, 17 January 2021 (UTC)
 * Ya. "50 MB ought to be enough for anybody." – Jberkel 16:59, 17 January 2021 (UTC)
 * So now what? Esszet (talk) 17:28, 17 January 2021 (UTC)
 * No solution for the foreseeable future, except forking the website and doing things our way. PUC – 17:31, 17 January 2021 (UTC)
 * Really? There's nowhere we can request more memory? Esszet (talk) 21:15, 17 January 2021 (UTC)
 * We requested. The answer was no.  We should plan on splitting the page into parts.  Vox Sciurorum (talk) 15:14, 18 January 2021 (UTC)
 * Or use fewer modules on big pages... e.g., tolerate subst:ing more templates on such big pages... - -sche (discuss) 09:42, 9 February 2021 (UTC)

Old Slavic font size
Why are Old East Slavic and Old Church Slavonic rendered in a larger font size? Looks like a bug to me, maybe a missing native script/font entry in a table somewhere? Compare to,  to. (Seen using Chrome on Chrome OS and Firefox on a Mac.) Vox Sciurorum (talk) 15:13, 18 January 2021 (UTC)
 * We treat Cyrillic and Old Cyrillic as two different scripts. On my computer, Old Cyrillic script is shown in a font that looks quite different from the modern Cyrillic script; it has the sort of uncial look shown in the "Image" column at Early Cyrillic alphabet. —Mahāgaja · talk 18:00, 18 January 2021 (UTC)
 * On my computer the scripts are almost identical except for size. Here are two letters to compare: orv =>  and ru} => .  The old form is taller than the Latin letters and almost identical in shape to the modern form (possibly very slightly more tapered, not triangular like the Wikipedia image).  The modern form is the same height as Latin capital letters. Vox Sciurorum (talk) 18:55, 18 January 2021 (UTC)
 * Old Cyrillic script is set to 125% font size at MediaWiki:Common.css. This makes sense for most of the fonts specified there under, which cause the script to display in Uncial style and look clearer when displayed slightly larger. However, if you don’t have any of the first 11 fonts listed, you’ll end up with text in fallback fonts such as Code2000 or DejaVu Sans, which use the modern  style of Cyrillic, but unfortunately, it’ll still render in a larger size. — Vorziblix (talk · contribs) 15:36, 20 January 2021 (UTC)

How long does it take for all the transclusions of a template to update?
A fair proportion of https://en.wiktionary.org/wiki/Special:LintErrors/missing-end-tag?namespace=0 is down to one module which was fixed earlier today.

Manually purging 30,000 entries is time consuming. Can it be automated? ShakespeareFan00 (talk) 19:45, 18 January 2021 (UTC)

Multilingual Cuneiform font for usage in Wiktionary
Hello everybody in Ancient Oriental studies,

Although not a scientist, I would like to get in touch, thanks for your attention. I am a typeface designer and, in loose collaboration with researchers at several academic institutions in Germany, currently developing a new digital Cuneiform font family, which will be cross-checked and finalized in the course of 2021. The family will consist of the following fonts:

1. Neo-Assyrian forms, alongside Persian and Ugaritic Cuneiform

2. Neo-Babylonian forms

3. Old Babylonian forms as canonized by Unicode

4. Classical Sumerian forms (plus the most important archaic variants) for etymological purposes.

The idea is to develop one multilingual typeface family with a harmoneous design. Its main purpose is to bring together Old Babylonian forms and their Neo-Assyrian counterparts for better use in Dictionaries or sign lists such as on Wiktionary. The font family can be licensed for free. I would be excited if Wiktionary would use it as a webfont, if technically possible with your CMS. Then, characters could be displayed in ancient and more recent shapes, making study a richer experience. The design follows a lapidar style, while I regard cursive a domain of hand-rendering skills or photographic reproduction of existing tablets.

I am aware of a similar project already existing, maintained by German designer Johannes Bergerhausen, to whom I offered to add Neo-Assyrian glyph shapes to his “DecodeCuneiform” font, but however, there seem to be no resources currently.

The first chunk of work to be finished will be font (1) and (2) – Neo-Assyrian and Neo-Babylonian variants according to Rykle Borger and Henri Labat. Font (3) will mainly follow Unicode (Steve Tinney) and Catherine Mittermayer.

Unfortunately, I was not able to add an image for a first impression, much more I would be indeed excited to get in touch with the Cuneiform community on Wiktionary.

All the best from Berlin, Roman Wilhelm

http://www.roman946.de http://www.romantype.net

Language tabs gadget - default language
I'd like to suggest that the languages tab gadget have a default language setting. When I'm looking up a word it's usually for the same language every time, but every time I go to a page I have to scroll/find the right language. To remove this, I've enabled the tab gadget and added a greasemonkey script that sets the anchor to the language I want. I've put a copy of the script on the gadget discussion page, but if when a user enabled the gadget it added a menu to the top bar providing a dropdown with a language selection, save that as a cookie, jump to that tab, would improve the UX I think. Discussion of this type of use has taken place before.

I'm happy to do this if someone's able to provide a bit of guidance, I've got no idea how to edit a gadget and have limited experience in JS.

Alwaysmpe (talk) 18:03, 19 January 2021 (UTC)

WT:ACCEL doesn't merge simple past and past participle
See. It would be preferable for WT:ACCEL to recognise that bliked is both past forms, and generate only one line, as shown in my correcting edit that followed. Equinox ◑ 07:50, 20 January 2021 (UTC)
 * Agreed. This only happens because blike has alternative past tense forms different from the past participle forms; it wouldn't happen with a completely regular verb like open. I'll add this to my backlog of things to do. Benwing2 (talk) 02:47, 25 January 2021 (UTC)

Add nows parameter to Template:ws
In order to not add “[]” after the term; e.g., at Thesaurus:body of water, run would use nows because its Thesaurus page is unrelated to water (note that the template is protected). J3133 (talk) 10:36, 21 January 2021 (UTC)
 * ✅.  will hide the WS link. --Yair rand (talk) 06:36, 28 January 2021 (UTC)

Template:tea room sense fix
Add / before (where is {{code|| {{#if:{{{m|}}}|{{{y}}} }}), because, e.g., {{temp|tea room sense|y=2020|m=August}} links to “Wiktionary:Tea room2020/August” (the template is protected). J3133 (talk) 10:36, 22 January 2021 (UTC)
 * {{done}} Chuck Entz (talk) 20:04, 22 January 2021 (UTC)

Limiting characters in head
Is it possible to trigger a warning or error from head if I enter an Ottoman Turkish word that uses a character not in the set at ? In particular, I've made a couple mistakes where I used U+06A9 keheh when I meant U+0643 kaf. They are very similar in connected form. In English a similar mistake would result in the word being added to a category, words spelled with (some non-Latin letter). Vox Sciurorum (talk) 00:20, 23 January 2021 (UTC)
 * The easy way is to add a list of standard characters to Module:languages/data3/o. DTLHS (talk) 01:01, 23 January 2021 (UTC)

Category:Proto-Huitoto-Ocaina language
I was going to create this but I just want to confirm, should I set the countries for this as Colombia and Peru? That seems to be what Witotoan languages says. User: The Ice Mage talk to meh 21:01, 25 January 2021 (UTC)
 * We don't usually specify countries for proto-languages anyway; their urheimaten are not necessarily where their descendants are currently spoken. —Mahāgaja · talk 22:01, 25 January 2021 (UTC)
 * I see, that makes sense I guess. Can you show me what/how to edit so that this category will be created properly without any Lua errors..? User: The Ice Mage talk to meh 16:47, 26 January 2021 (UTC)
 * The problem was that  wasn't actually marked as a reconstructed language at Module:languages/datax. I've remedied that now and created the category. —Mahāgaja · talk 18:00, 26 January 2021 (UTC)
 * I see, thanks. :) User: The Ice Mage talk to meh 21:27, 26 January 2021 (UTC)

Latin: stative and inchoative verbs category+usage note
There's a systematic relationship in Latin between these two types of verbs, the former almost invariably in, the latter likewise invariably in (some outliers include ~, and there are pairless ones as well, like puer/llāscō "to attain boy/girlhood"). I've added a usage note to this extent to, and I think it would be beneficial to have a template that would substitute the same description and add the corresponding pair for both of these. Come to think of it, perhaps we'd need two templates, one for each type - unless we want a global template for many different verb types/aspects/Aktionsarten (such as factitive, iterative, durative, delimitative etc). I suspect there are other languages where this template could come in handy as well - it doesn't need to be Latin-only. Other languages could pair different aspects - Russian currently handles this in the headword, but doesn't explain the difference or precise type when there's more than one pair, as seen here, so could benefit from such a global template as well.

Currently all verbs in -scō seem to be automatically added to (I'm guessing this is done by the la-conj template), but there isn't one for stative verbs. While it tentatively appears that every verb in -scō is inchoative, this isn't the case for -eō verbs like and, and even  is doubtful - an inchoative formed to it wouldn't make sense at any rate; so a stative category wouldn't simply double , and in addition will be able to be applied to verbs of other conjugations. With this in mind, I suppose the stative category should be tied to the usage note, and not the conjugation template; and I also think it makes sense if the template adds the inchoative category too, thus allowing to bypass the conjugation template's autocategorisation.

Now to the practical part: firstly I wonder if anyone doesn't think this is a good idea; and secondly, since I'm programmingly-challenged and have no experience creating wiki templates or categories, I ask that somebody be so kind as to create these for me, or else offer me some guidance in doing that myself. Brutal Russian (talk) 04:14, 27 January 2021 (UTC)
 * A template specific for these Latin entries would be a useful addition. It is very simple to make, and requires zero programming knowledge; you can model it after, for example. A global template is probably a bad idea, as we have very different ways of linking these kinds of forms in different languages, and a one-size-fits-all approach just isn't appropriate. —Μετάknowledge discuss/deeds 06:56, 27 January 2021 (UTC)

Category:Insular Indo-Aryan languages
I attempted to create this but I get a Lua error:

Does someone with better knowledge of the Wiktionary Lua code know how to fix this? User: The Ice Mage talk to meh 16:55, 27 January 2021 (UTC)
 * I figured it out. At Module:families/data,  had a line , but if a family isn't in Wikidata, the line should be omitted completely rather than simply having nothing between the quotation marks. —Mahāgaja · talk 19:19, 27 January 2021 (UTC)
 * I've edited Module:data consistency check to check all modules for invalid Wikidata items (at least egregiously invalid ones like this), so this will be noticed and corrected more quickly next time. — Eru·tuon 19:57, 27 January 2021 (UTC)

Creating a redlinks category
I created Category:Ottoman Turkish redlinks and Category:Ottoman Turkish redlinks/m over a week ago. They are empty. What ritual do I need to perform to have them populated? Vox Sciurorum (talk) 13:29, 29 January 2021 (UTC)
 * The language code needs to be added to the list as redlink category, which requires an admin or a template editor. First, though, we need to consider whether it's a good idea: the redlink category module has been responsible for a number of "out of memory errors" over the years. That said, all of the entries in the exclusion list (over 300 in all) are in either Latin or Han characters (and ar for Arabic is one of the enabled codes), so I think we're okay. I added it. Chuck Entz (talk) 18:15, 29 January 2021 (UTC)
 * It will take quite a while for the system to update, since the template is transcluded in every entry that uses our templates for linking. I went through a few of the entries in Category:English terms derived from Ottoman Turkish to find a couple with redlinked translations and did null edits to confirm that it was working.
 * I noticed that redlinks in etymologies don't add the category- I'm guessing they bypass the more basic linking functions that call redlink category. On the one hand, adding the redlink category checking might increase the overall memory load, and etymologies have a rather high percentage of erroneous forms. On the other hand, terms in etymologies tend to have more interest to the general readership than translations in the same languages, since they're more likely to be from historical periods and languages that only specialists study. Chuck Entz (talk) 18:56, 29 January 2021 (UTC)
 * I've added Ottoman Turkish to User:Jberkel/lists/wanted/languages so that it will have a wanted entries list linked from User:Jberkel/lists/wanted/latest when the next batch is generated. User:Jberkel's wanted entries lists take from more link templates, including etymology templates, so they have some entries that the redlink categories miss. (See this search for the templates that use . Only a few, basically and  and translation templates.) — Eru·tuon 21:37, 29 January 2021 (UTC)
 * These have now been generated: User:Jberkel/lists/wanted/20210401/ota. Sorry, list generation was a bit delayed because of memory issues. And apparently we'll have HTML dumps soon, so we'll be able to perform a more global analysis of missing entries. –Jberkel 08:15, 12 April 2021 (UTC)

How to link to the entry /me?
How can I fix the redlink at Appendix:Variations_of_"me"? Equinox ◑ 17:56, 29 January 2021 (UTC)
 * Using l instead of a bare link works. I don't know if there's a more elegant solution. —Mahāgaja · talk 20:01, 29 January 2021 (UTC)
 * Just use a colon:  produces /me. —Μετάknowledge discuss/deeds 20:02, 29 January 2021 (UTC)

Quoting from an app
How should we quote from a language-teaching app in a foreign language? In this entry - I didn't use any quote template, I don't like it that way and it doesn't categorise. --Anatoli T. (обсудить/вклад) 11:22, 30 January 2021 (UTC)
 * Another rather awkward quotation from a program I've added today is at . --Anatoli T. (обсудить/вклад) 00:50, 3 February 2021 (UTC)
 * Another templateless quotation I added recently is at . --Anatoli T. (обсудить/вклад) 09:37, 14 February 2021 (UTC)
 * A corpus belonging to an app probably isn't durably archived. That, combined with the facts that it's not accessible to searching by the public and that it's artificially constructed in my opinion makes them unattractive for citing purposes. From CFI, [The "conveying meaning" criterion] filters out (...) made-up examples of how a word might be used, which arguably covers all material of this type.__Gamren (talk) 23:24, 29 March 2021 (UTC)

Spurious newlines
A "qualifier" template next to a "ux" template, e.g.:

for me, in both Edge and Chrome, produces this:

 * (UK usage) He looks better for having lost weight.

Is there any way to suppress the unwanted line break while still using recommended templates? (Of course, I know it can be done by removing the templates.) Mihia (talk) 18:23, 1 February 2021 (UTC)
 * Template:ux has a "q" parameter. DTLHS (talk) 18:25, 1 February 2021 (UTC)
 * Aha! Thank you! Mihia (talk) 18:48, 1 February 2021 (UTC)

title: Wiktionary:Grease pit/2021/January


text:
ᏡᏡ

Noun

 * 1) purple martin

title: ᏡᏡ


text:
شرزه‌پلنگ

Etymology
From.

Noun

 * 1)  a ferocious, raging leopard
 * 2) * 10th Century CE, Ferdowsi, Shahnameh
 * "fa"

- کنون من شوم سوی برزو بجنگ تو شو سوی هومان چو شرزه‌پلنگ

title: شرزه‌پلنگ


text:
Wiktionary:Grease pit/2021/February

Out of memory!
Requests for verification/Non-English has run out of memory. All the tricks I know for reducing memory usage don't apply to a page outside of mainspace. One possibility might be nowikis or subst: for ping-type modules, since they're useless after the initial edit when they're added. Another possibility would be mocking up the output of some of the CJKV and Thai templates, because they use exorbitant amounts of resources to produce transliterations. Or maybe some of the completed/resolved rfvs could be archived early. Chuck Entz (talk) 05:41, 3 February 2021 (UTC)
 * The ultimate solution is to close more RFVs. (Have you closed any recently?) The proximate solution is probably just to archive a bunch of threads early, as you said. —Μετάknowledge discuss/deeds 06:29, 3 February 2021 (UTC)
 * I expect that RfVs for non-English language definitions would take longer to close properly, giving them a fair chance, given the smaller numbers of those competent to find cites, exercise judgment about what definition a cite might support, and rewrite the definition to fit the cites found. Why wouldn't we split the page along the lines of script or language family? DCDuring (talk) 19:52, 3 February 2021 (UTC)
 * This discussion is already being held at Beer parlour/2021/February. —Mahāgaja · talk 10:33, 4 February 2021 (UTC)

Moving pages
If the main definition of an entry is at A, and B is defined as, let's say, "Alternative form of A", then can I move the main definition from A to B using the "Move" feature, or do I have to copy and paste everything manually? What is the recommended way of carrying out this procedure? Mihia (talk) 18:46, 5 February 2021 (UTC)
 * It could be done, but it's usually not worth the trouble, especially since preserving the revision history of both pages can get tricky, and might require an admin. Although there's a risk when moving content from one page to another of breaking the chain of attribution necessary for the Creative Commons license, that can be solved by mentioning the other page in your edit comment, as in "adding definitions from A". Chuck Entz (talk) 19:54, 5 February 2021 (UTC)
 * OK, thanks. Mihia (talk) 20:17, 5 February 2021 (UTC)

nocat
has an undocumented "nocat" parameter. Anyone know what this is and on what basis one would use it? Mihia (talk) 18:50, 5 February 2021 (UTC)
 * That parameter is used on a lot of templates; setting it to 1 means the template won't put the entry into the category it normally would (in this case, "CAT:Languagename present participles"). I've mostly seen it used when the headword line is "xyz" or the like, which already categorizes the entry, so having present participle of categorize as well would be redundant. infl, on the other hand, doesn't categorize, so I think it makes sense to change xyz to xyz. (For English, though I usually change it verb so that the entry says the form in question is both a past participle and a gerund, since all English ing-forms are both.) —Mahāgaja · talk 10:05, 6 February 2021 (UTC)
 * Thanks. Mihia (talk) 18:09, 9 February 2021 (UTC)

Interwiki linking of proverbs and other pages with minor differeces
A_caballo_regalado_no_le_mires_el_diente. and When_in_Rome,_do_as_the_Romans_do. do not seem to have the desired effect, same as and. Interwiki linking is apparently still blocked to pages that are only redirects. How to solve the problem then? Taylor 49 (talk) 19:49, 8 February 2021 (UTC)
 * mediawiki.org/wiki/Extension_talk:Cognate#Does_Cognate_create_links_to_redirection_pages?
 * mediawiki.org/wiki/Extension_talk:Cognate#Cognate_on_Wiktionary:_discussion_about_redirects
 * https://phabricator.wikimedia.org/T163717
 * https://phabricator.wikimedia.org/T165061
 * Discussion year 2017
 * A 4-year wait is nothing in WMF-land :) But it looks like there's some movement now in T165061. Jberkel 00:14, 2 March 2021 (UTC)
 * Eppur si muove! According to the ticket status this is now implemented and will be deployed soon. – Jberkel 10:42, 15 March 2021 (UTC)

"blends" in blend category
Does anyone know where does the word "blends" in pages that use the template blend get the string of the word "blends" to put in the categories' name (e.g. Category:English blends)? I have searched for it in modules and templates and found nothing for it. RXerself (talk) 22:46, 6 February 2021 (UTC)
 * Is Module:category tree/poscatboiler/data/terms by etymology what you're looking for? —Mahāgaja · talk 23:25, 6 February 2021 (UTC)
 * I don't think so. It seems to be used by autocat not Template:blend. I tried changing the entry for "blends" there and use the show preview button for the airbill page and it does not change the label for category "English blends". RXerself (talk) 06:44, 8 February 2021 (UTC)
 * Take a look at the template definition in Template:blend. You'll see the following:
 * Note in particular the  part; this is what causes a category like Category:English blends to appear. Benwing2 (talk) 05:14, 10 February 2021 (UTC)
 * OMG I forget to look it there at first! Thank you very much. RXerself (talk) 07:12, 10 February 2021 (UTC)
 * OMG I forget to look it there at first! Thank you very much. RXerself (talk) 07:12, 10 February 2021 (UTC)

Change to category tree not reflected in category pages
I edited Module:category_tree/topic_cat/data/Human to insert a new subcategory, Category:Collectible card games between Category:Card games and Category:Magic: The Gathering, which previously had a parent-child relationship. However, when I view Category:en:Card games, I see both Category:en:Magic: The Gathering and Category:en:Collectible card games as direct children in the "Subcategories" section. Also Category:en:Collectible card games does not show Category:en:Magic: The Gathering as a subcat. But other aspects of the UI do reflect my intended hierarchy. At Category:en:Magic: The Gathering, the breadcrumb links at the top include "Collectible card games" as a parent, and Category:en:Collectible card games is included in the parent categories at the bottom of the page. Is there a step I missed? I tried purging the cache at Category:en:Card games (by appending "?action=purge" to the url), but it had no effect. Colin M (talk) 00:14, 7 February 2021 (UTC)
 * It's there now. Categories aren't affected by purging the cache. Updating categories requires either an actual edit (a null edit will do) or an automated process that has an edit queue which is usually already full of older changes from all over Wikidom. If you don't want to wait, do null edits on the affected categories. Chuck Entz (talk) 06:07, 7 February 2021 (UTC)

Links to incubating Wiktionaries
With Template:tt+, you can easily link translation into foreign languages: after the translation, a link will appear in superscript. After learning, for example, that the German translation for 'house' is Haus, you can click the link and consult de:Haus to find out more. By the advances of Wikimedia software, it can even link to non-existent Wiktionaries as long as there is a test wiki in Incubator. Yay for our developers!

But there's one bug. The lemmas of those test wikis are still out of reach. When I try to use {tt+} for the Zealandic Wiktionary, for example puut (Zealandic for 'frog'), zea:puut does not redirect to incubator:Wt/zea/puut but to incubator:Wt/zea/Vòblad, the Main Page of the project.

As you can see, this doesn't bring users much further (even though they will now be informed of the test wiki's existence). And since I write quite elaborate entries on this test wiki, I want them to be read and I do think they can be very helpful to those interested in the language. I understand this is a problem that stretches beyond Wiktionary, but it might be in its particular interest, since unlike Wikipedia, it actually makes use of the possibility to link to incubating wikis by using a regular interwiki link. Steinbach (talk) 18:09, 7 February 2021 (UTC)
 * This practically requires Lua for it to be implemented, and even then manually updating the link of Wiktionaries that exist. However, I'm not convinced we should be linking to Wiktionary editions that are still in the Incubator. — surjection ⟨??⟩ 21:40, 7 February 2021 (UTC)

Lua error: not enough memory
This error seems to pop up now and then in long pages. It's currently visible in the second half of 我, and doesn't go away with a simple purge. Is this a known issue? //Rotsee (talk) 21:29, 7 February 2021 (UTC)
 * Yes; Lua memory errors. — surjection ⟨??⟩ 21:33, 7 February 2021 (UTC)

Old Latin links
At Reconstruction:Proto-Italic/denɣwā, the Old Latin descendant links to dingua. I am led to believe that we no longer use "Old Latin" as a L2 header. Can the template be amended to link to the #Latin anchor? This, that and the other (talk) 03:34, 10 February 2021 (UTC)
 * Pinging as the last person to edit Module:languages/datax, which might be the problematic module (although I really have no idea). This, that and the other (talk) 11:02, 25 February 2021 (UTC)
 * Uhhh... if Old Latin isn't considered separate from Latin, why don't you just use the code la in the entry? Why would we use or have a code for an unrecognized language?__Gamren (talk) 11:09, 25 February 2021 (UTC)
 * My question was motivated by the fact that someone (not me) has used the itc-ola code in a lot of these Proto-Italic reconstruction entries (Reconstruction:Proto-Italic/dwenos is another). I assumed it was practice in these cases to preserve the "Old Latin:" text but point the link to #Latin. If not, why is itc-ola in Module:languages in the first place? This, that and the other (talk) 11:18, 25 February 2021 (UTC)
 * At Votes/2019-08/Abolish the Old Latin header it was voted to abolish Old Latin as a separate language from Latin. Our Old Latin entries have all been reincorporated into Latin, but "itc-ola" is still a full-fledged language code; no one has yet changed it to an etymology-only code. Once that happens, Category:Old Latin language and all its subcategories should be deleted, as it has been superseded by CAT:Old Latin. —Mahāgaja · talk 12:26, 25 February 2021 (UTC)

Ugly Cites from Quiet Quentin
Hey- I recently used Quiet Quentin to create some citations on Huangchi. However, the two cites I added are ugly as hell compared to my beautiful archive.org cites. Is there any way to improve them from what they are now? I ask this because I anticipate that I will be using Quiet Quentin a lot over the coming months: Google Books has access to some materials/has searchable OCR that archive.org does not, so I am forced to use Google Books. I am not satisfied with these citations at all. --Geographyinitiative (talk) 17:50, 10 February 2021 (UTC)
 * The code for formatting is found at MediaWiki:Gadget-QQ.js. Can you specify what you think is wrong with it?__Gamren (talk) 11:14, 25 February 2021 (UTC)

Add misspelling parameter to head templates
Because misspellings are not supposed to be in lemma categories (see ) and the only workaround is copying the information into (e.g., Special:Diff/61800642).

Compare

with

. J3133 (talk) 09:56, 11 February 2021 (UTC)
 * This can be done but I'm not sure it should. My alternative is to simply use without any inflections. Benwing2 (talk) 03:32, 12 February 2021 (UTC)

Help with
I'd like to add three values to the template. They are all infinite categories, so they can go between the converb and the gerund in the template.
 * General temporal participle - formed by adding -də/-da to the subject non-past participle
 * Adverbial participle of intensification formed by adding -ca/cə to the first-person plural past simple.
 * Specific temporal participle - formed by adding -kən (no vowel harmony) to the third-person singular future indefinite

Thanks in advance! Allahverdi Verdizade (talk) 20:32, 12 February 2021 (UTC)

 * Done. (Note: for such infinite tense names, I use names that you created. I also applying these on accel-forms) BengkelBerkah05 (talk) 13:27, 13 February 2021 (UTC)
 * Thanks a million! One more thing: for adverbial participle of intencification, it's formed from first-person plural past simple, that is for the verb it should output olduqca, whereas it now outputs *oldumca. Can you please fix this? Allahverdi Verdizade (talk) 18:05, 13 February 2021 (UTC)x

 * Now, I fixed the error (see Special:MobileDiff/61816421). BengkelBerkah05 (talk) 02:31, 14 February 2021 (UTC)
 * Thank you! How about the negative forms? It should also output olmayanda, olmadıqca and olmayaraq. Allahverdi Verdizade (talk) 10:52, 14 February 2021 (UTC)
 * On a different note: the template currently contains a factual error. third-person singular present perfect does not end on -miş in modern Azerbaijani, but on miş-dir. This copula -dir is obligatory for third person singular. Can you add that too? (It has four harmonic variants, but you probably know that). Allahverdi Verdizade (talk) 15:31, 14 February 2021 (UTC)
 * Done. BengkelBerkah05 (talk) 08:27, 16 February 2021 (UTC)
 * Thank you. The only thing that remains to be done now is mirroring all changes for the negative as well. Allahverdi Verdizade (talk) 10:49, 16 February 2021 (UTC)

WT:ACCEL in Swedish
Hello! I am wondering how acceleration could be added to swedish form templates? I've looked some into it and I'm too scared to experiment on any of the templates or modules. There are some acceleration on the Swedish adjective headword template Template:sv-adj, but apart from that all forms of any word would have to be added manually. It would make it much easier for me and others, and would make it less likely making errors if it was semi-automatic. I would like to request (and suggest) starting with the noun templates located here:

Can anybody either instruct me, or even better, make the requested changes in the templates? --Fringilla (talk) 21:57, 13 February 2021 (UTC)
 * I've changed to illustrate it, which is inherited by templates that use it, such as . Basically, you just need to pass to the  template the parameter accel-form, exchanging pipes for | . Also, are you aware that in order to actually use it, you have to turn it on in your Preferences->Gadgets?__Gamren (talk) 12:20, 25 February 2021 (UTC)
 * Thank you very much! It seems to affect some of the templates already pointing to that one, like Template:sv-infl-noun-c-ar. However it seems most of the noun (and verbs use another) templates use a module (Module:sv-nouns) in which I can't find any links. That is where I got stuck when I tried doing this the first time. But I will check out other Modules and compare how they do it, unless you maybe know how to add the changes in the Module? --Fringilla (talk) 13:09, 25 February 2021 (UTC)
 * It seems that task is delegated to links.full_link, i.e. the function full_link in Module:links, which takes an accel parameter.__Gamren (talk) 23:07, 25 February 2021 (UTC)

Form-of templates not bolding the linked-to word
In e.g. frenchified or frenchise, the main entry which is being linked to is no longer presented in bold. Seems to be due to a recent change, as cached pages still have bold until I purge the cache. Bolding is absent both when I am logged in and when I am logged out, across several browsers. - -sche (discuss) 03:17, 15 February 2021 (UTC)
 * Sorry, I broke this, am fixing it now. Benwing2 (talk) 03:42, 15 February 2021 (UTC)
 * Should be fixed. Benwing2 (talk) 03:58, 15 February 2021 (UTC)
 * Thanks for the speedy fix. :) - -sche (discuss) 07:09, 15 February 2021 (UTC)

Inconsistency between and
J3133 (talk) 05:16, 15 February 2021 (UTC)
 * equivalent to the English .
 * equivalent to English .
 * equivalent to English .
 * equivalent to English .

Technical maintenance planed
A maintenance operation will be performed tomorrow morning UTC time (Wednesday 17th at 07:00 AM UTC).

It will impact all wikis and is supposed to last up to one minute.

During this time, new translations may fail, and Notifications may not be delivered. For more details about the operation and on all impacted services, please check on Phabricator.

A banner will be displayed 30 minutes before the operation.

Thank you, SGrabarczuk (WMF) 17:45, 16 February 2021 (UTC)

Add termlang parameter to
E.g., : “key” should link to Appendix:English pronunciation not Appendix:Translingual pronunciation, however it should be in Category:Translingual terms with IPA pronunciation not Category:English terms with IPA pronunciation, as the term is translingual (thus ). J3133 (talk) 08:08, 17 February 2021 (UTC)

Audio red links
Is there any way we can find a list of all pages using which generate a red link? i.e. there's no actual audio file there. I assume Wonderfool has made a huge number of errors when batch-uploading low-quality audios over the years. Oxlade2000 (talk) 13:31, 17 February 2021 (UTC)
 * Category:Pages with broken file links —Suzukaze-c (talk) 04:28, 23 February 2021 (UTC)

Reference template: switches based on edition
Trying to make a newly-created template cover both editions of the book, but have no template creation experience and can't figure this out on intuition alone. If 2 edition is specified, change year and ISBN (I've put these in the template) and add ", Second Edition" to the title, as seen on the cover (eg. on Amazon). Perhaps it's better to make this optional and revert to the 1st edition otherwise - but having edition as third parameter is unintuitive. On the other hand, specifying edition every time might seem bothersome at first but you get used to it. Brutal Russian (talk) 21:58, 17 February 2021 (UTC)
 * I think I have it, but please double check that the ISBNs correspond to the correct editions. You didn't say which was which, and I can't figure it out from Google Books. At the moment, it's giving 978-0-9747927-5-0 for the second edition and 978-0-9895142-7-9 for the first. —Mahāgaja · talk 22:11, 17 February 2021 (UTC)
 * Thank you, that works like a charm (I have swapped the ISBNs), but I'm still wondering how one would go about using a parameter (edition) to change another one (the title), but without displaying the first of these, to avoid "Second Edition, 2nd edition". Also, if I want "edition=2" to also give the same result as "edition=2nd", do I use #switch? Brutal Russian (talk) 22:34, 17 February 2021 (UTC)
 * I'm not sure. cite-book's own edition simply outputs whatever you put in, so 2 will give "2 edition", second will give "second edition", new will give "new edition", 2020 will give "2020 edition". I think it would be more intuitive for this template's edition to behave the same way. On the other hand, as long as there are only two editions, I could write the template so that if edition has any value at all, it will give the info for the second edition. Then 2, 2nd, second, 2020 would all have the same behavior. One drawback to that is that counterintuitive inputs like 1, 1st, first, 2009, your text here would all also give the information for the second edition. Another drawback to that is that it wouldn't work if there were to be a third edition at some point in the future. But if you like, we can certainly change 2nd to second if you prefer to have the word "second" spelled out. —Mahāgaja · talk 08:00, 18 February 2021 (UTC)
 * Yep,  is the right way to go. Something like   should get ,  , and   to all give the same results. If you want to have the title change by edition but not show the edition parameter, you could delete the edition parameter entirely and just have something like

 * But I don’t know why you’d do that instead of just leaving the edition out of the title and having it as a separate edition parameter. — Vorziblix (talk · contribs) 18:41, 18 February 2021 (UTC)
 * Why, because yolo :D For curiousity - I just want to figure out how the syntax works; in case I come across a book that actually changes its title across editions - in fact this very book is currently listed on amazon/Outline-Historical-Comparative-Grammar-Second/dp/0989514277 as '(Second Edition) 2nd ed. Edition ' xD, which gave me an idea to also list it here like that - not to mention the better visibility. An additional complication this would avoid is the fact that worldcat once confusingly lists the 2nd, corrected printing of the first edition of this book as '2., corrected ed'. Any way, thank you for the help, I've now implemented the simple edition switch. One thing I couldn't figure out is how to replace the automatically-supplied "edition" with its upper-case equivalent, obviously because OCD. Is that even possible? Brutal Russian (talk) 23:00, 19 February 2021 (UTC)

does not wrap around images
E.g., see elephas. J3133 (talk) 10:35, 20 February 2021 (UTC)

 * MediaWiki:WikiHieroTempFix.js. —Suzukaze-c (talk) 04:26, 23 February 2021 (UTC)
 * Hopefully fixed, Special:Diff/61879426. I don't remember why the inline-block was needed, but I can't immediately find anything that breaks if it's removed. — surjection ⟨??⟩ 11:15, 23 February 2021 (UTC)

Does the anagram-adding bot still run?
I was expecting to see monotheism pop up at nomotheism... Equinox ◑ 04:24, 23 February 2021 (UTC)
 * runs the anagram bot. The tasks he runs and their frequency does not seem to be posted. —Μετάknowledge discuss/deeds 22:12, 1 March 2021 (UTC)
 * I got bored running scripts. Maybe one day I will run it again. DTLHS (talk) 03:48, 2 March 2021 (UTC)
 * I like entries that are anagram-proof. I regard anagrams as a waste of space. DonnanZ (talk) 14:38, 14 March 2021 (UTC)

Template:ne-conj
I'm not really sure why this has a module error on the template page and not on the documentation page, but something needs to be fixed: this template has been in CAT:E for one reason or another for weeks. Pinging, whose work on the module and the template documentation is responsible. Chuck Entz (talk) 18:11, 27 February 2021 (UTC)

Category:Reference templates lacking the author or editor parameters
I don't know who uses this, but I noticed R:Lexico references are ending up in this category, and I don't understand why - for example. DonnanZ (talk) 17:00, 1 March 2021 (UTC)
 * Because R:Lexico calls cite-book but doesn't use author or editor. —Mahāgaja · talk 21:58, 1 March 2021 (UTC)
 * Thanks, I'll ping, who's the only one who has edited it lately, to see if that was the intended result. DonnanZ (talk) 23:58, 1 March 2021 (UTC)
 * requested for this tracking category to be added some time back as he was working on something. Victar, do you still need it? — SGconlaw (talk) 04:36, 2 March 2021 (UTC)
 * I once asked for this function to be noinclude'd so that only the templates themselves, not the articles they're used in, would be in the cleanup categories, and was told (I don't remember by whom) that having all the articles in the category as well would help attract attention to the problem. Seems a little passive-aggressive to me, but OK. —Mahāgaja · talk 08:46, 2 March 2021 (UTC)
 * I don't recall... -- 10:48, 2 March 2021 (UTC)
 * OK, in that case I’ll remove the tracking categories. — SGconlaw (talk) 15:30, 2 March 2021 (UTC)
 * ✅. — SGconlaw (talk) 19:03, 2 March 2021 (UTC)
 * Oh. So nobody wants the category? DonnanZ (talk) 19:23, 2 March 2021 (UTC)

 * : I have now noticed a lingering red link from this deleted category, which was hidden previously (before the deletion), see . Does R:Lexico need altering? DonnanZ (talk) 17:10, 6 March 2021 (UTC)
 * It was a caching issue. I did a null edit and the category disappeared. itself doesn't create any tracking categories. — SGconlaw (talk) 17:15, 6 March 2021 (UTC)
 * I tried the same thing! Anyway, it's gone. DonnanZ (talk) 17:21, 6 March 2021 (UTC)

title: Wiktionary:Grease pit/2021/February


text: Category:Latin terms derived from Epic Greek


text: Category:English terms derived from Epic Greek