Wiktionary:Grease pit

Definition from Wiktionary, the free dictionary
(Redirected from Wiktionary:BUG)
Jump to: navigation, search

Wiktionary > Discussion rooms > Grease pit

Welcome to the Grease pit!

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

The Grease pit is a place to discuss technical issues such as templates, CSS, JavaScript, the MediaWiki software, extensions to it, the toolserver, etc. It is also a place to think in non-technical ways about how to make the best free and open online dictionary of "all words in all languages".

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

Permanent notice

  • Tips and tricks about customization or personalization of CSS and JS files are listed at WT:CUSTOM.
  • Other tips and tricks are at WT:TAT.
  • Everyone is encouraged to expand both pages, or to come up with more such stuff. Other known pages with "tips-n-tricks" are to be listed here as well.

Grease pit archives edit
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017


Contents

September 2017

Different Arabic and Persian fonts[edit]

Why do some Persian words appear on different pages (linked with a 'See also') from their Arabic etymons spelt exactly the same way? I don't know of any need for glyphic variation between the two languages, apart from new Persian letters like /p/ and /g/, and some problem with alif maqsura. Examples are كتف kitf/ketf (shoulder) and دليل dalîl (proof); but they appear on the same page (as I would expect for all such) with دار dâr (house) and دفتر daftar (notebook). (If I have a choice, the Persian font is much better looking, like proper print.) --Hiztegilari (talk) 10:55, 1 September 2017 (UTC)

The first example features ك vs. ک. The second example features ي vs. ی. —suzukaze (tc) 10:59, 1 September 2017 (UTC)
In cases where the two glyphs are identical, though, such as كتف vs. کتف and دليل vs. دلیل, I wonder if a hard redirect would be a better solution. We can still use separate pages for words in which ك/ک and ي/ی appear differently. —Aɴɢʀ (talk) 13:19, 1 September 2017 (UTC)
If we did that, the pagename would show codepoints that are never used for Persian, which is a problem from my perspective (people searching for Persian will probably use a Persian input method, which produces the right codepoints). With updating of {{also}}, being on separate pages poses no real issue in terms of users navigating to words. —Μετάknowledgediscuss/deeds 16:47, 1 September 2017 (UTC)
The correct solution to this problem would be to redesign Unicode from scratch. Until we can do that, we'll have to settle for having them on separate pages. --WikiTiki89 18:10, 1 September 2017 (UTC)

Diacritic stripping function[edit]

Is there a diacritic stripping function built into Lua? If not, anyone know of a streamlined method? --Victar (talk) 15:26, 1 September 2017 (UTC)

If there were, I wouldn't trust it. Module:links does something like that, depending on the language. Ask at the Grease pit for more information. Chuck Entz (talk) 15:48, 1 September 2017 (UTC)
Thanks, I'll check it out. Whoops, I meant to post this there. Will move. --Victar (talk) 16:05, 1 September 2017 (UTC)
What language, what diacritics do you specifically want to remove. DTLHS (talk) 16:43, 1 September 2017 (UTC)
@DTLHS: I'm working on a declension table module for PII, so I'm just removing acute accents. --Victar (talk) 16:53, 1 September 2017 (UTC)
If you have a list it can be added to Module:languages/datax. Or if you don't want it to apply to every PII entry you could just put a hardcoded table in your module. DTLHS (talk) 17:06, 1 September 2017 (UTC)
@DTLHS: I need to strip acute accents from the declension suffixes if an accent exists on the stem. Module:User:Victar/iir-decl-noun --Victar (talk) 17:12, 1 September 2017 (UTC)
Module:ine-common has a variety of functions for manipulating accents that might be useful. —Rua (mew) 17:32, 1 September 2017 (UTC)
Perfect, thanks @CodeCat. --Victar (talk) 17:35, 1 September 2017 (UTC)

WM attention to "the two-stage page loading problem"[edit]

Here is the beginnings of a discussion thread on Wikimedia-l on a matter directly relevant to us, based on my recollection of discussions:

Michael Peel email@mikepeel.net via lists.wikimedia.org 9:09 PM (4 hours ago)

to Wikimedia This is possibly the most annoying feature of the Wikimedia projects at the moment. You access a page. Then you start reading or editing it. And then suddenly the page jumps when a fundraising banner / central notice / gadget / beta feature loads. So you have to start reading the page again, or you have to find where you were editing again, or you have to undo the change you just made since you made it in the wrong part of the page.

I understand that this isn't intentional. Presumably there is a phabricator ticket about this. But how can we fix this - does this need more developer time, is this an external problem that we need someone else to fix, or is this a WONTFIX?

--

James Heilman jmh649@gmail.com via lists.wikimedia.org 11:25 PM (2 hours ago)

to Wikimedia I just put forwards a proposal to fix part of this issue Mike :-)

https://en.wikipedia.org/wiki/Wikipedia_talk:Twinkle#Button_load_issues

The TW button is easy to fix at least I am told, once I get consensus. Amir fixed one of the buttons earlier today.

  • Does this also relate to the timing problem that leads to the all-too-frequent failure of certain JS-implmented features (show-hides most annoyingly) to load? DCDuring (talk) 05:37, 2 September 2017 (UTC)
    • Should someone here who is technically knowledgeable follow this and push our view of the problem. DCDuring (talk) 05:40, 2 September 2017 (UTC)
Hooray! The main problems in general editing (for me at least) are the entire tab bar (or the space directly below it), causing the edit box to jump downward, and the late-loading Citations tab on that bar, causing some tabs to jump rightward. Equinox 09:37, 2 September 2017 (UTC)

No more automatic link for plural creation?[edit]

What happened to the automatic link that would load if you tried to create an English plural form? Now I just get a blank page. — SGconlaw (talk) 17:49, 2 September 2017 (UTC)

You need to reenable it in your preferences. DTLHS (talk) 17:53, 2 September 2017 (UTC)
Thanks. How did it get turned off? — SGconlaw (talk) 18:34, 2 September 2017 (UTC)
By moving and/or renaming the file, which, if I remember correctly, was for good reasons. It would have been a good idea, though, to let people know it would happen. But then, hindsight is 20/20. Chuck Entz (talk) 18:41, 2 September 2017 (UTC)
Now that we have the hindsight, I hope future changes of this kind will be seamless. Equinox 18:48, 2 September 2017 (UTC)
  • Inconveniences likes this are good. It makes you reconsider whether you actually need the gadget. I might as well make this a feature - turning random gadgets off at random intervals. Dixtosa (talk) 19:28, 2 September 2017 (UTC)
    • My immediate assumption when the form creation gadget stopped working was that it had broken, not that I needed to re-enable it. If there were some way to distinguish between those situations, the idea might work. (Or maybe you're joking.) — Eru·tuon 19:52, 2 September 2017 (UTC)
      • A notice at "News for editors" would have been welcome. — SGconlaw (talk) 20:07, 2 September 2017 (UTC)

Wildcard Contributions Searches[edit]

The Wiktionary:Per-browser preferences have stopped working for me. Given the sad state of my system, it's not worth the trouble of troubleshooting. There was only one thing it it I ever used: there was a thing that popped up in Special:Contributions pages that allowed me to do wildcard searches on IP. It wasn't exactly a masterpiece of user-interface design, but I was able to look for IP users who were changing their IPs, but staying within their ISP's local allocation. Would it be possible to have a regular gadget or a special page that would allow the same thing?

Basically it would take "77.37.156.*", or, even better, "77.37.156.23/24" as input and give a combined list of edits by every IP within that range. This capability is especially helpful when contemplating a range block, because it helps refine the range needed and makes it possible to check if anyone has made legitimate edits from within it. Thanks! —This unsigned comment was added by Chuck Entz (talkcontribs).

The code behind the gadget was deleted. Pinging @TheDaveRoss. Dixtosa (talk) 07:15, 3 September 2017 (UTC)
I had not realized that this was being used by anyone, or that it was added to the per-browser preferences. Restored. - TheDaveRoss 13:54, 3 September 2017 (UTC)
@TheDaveRoss Well, now the user interface works like it used to, but it doesn't do anything- there's no list of edits. Chuck Entz (talk) 14:03, 4 September 2017 (UTC)
@Chuck Entz, I have copied the latest source of the gadget from wp. Is it working now? Dixtosa (talk) 15:53, 4 September 2017 (UTC)
Yes. Thank you! Chuck Entz (talk) 18:06, 4 September 2017 (UTC)
@Dixtosa Did you move it to somewhere global so I can delete it again from my userspace? - TheDaveRoss 14:03, 6 September 2017 (UTC)
@TheDaveRoss, now you can delete your page. Dixtosa (talk) 16:55, 6 September 2017 (UTC)

Testcases fail but are identical?[edit]

Module:ha-headword/testcases- as far as I can tell the expected and actual cells for "aeionū̀ (m)" and "aeionā̀ (f)" are identical, but still failing- why? —This unsigned comment was added by DTLHS (talkcontribs).

It might be because the testcases use the combined Unicode character [A WITH ACUTE] while the module itself outputs the letter + the combining diacritics [LATIN LETTER A + COMBINING ACUTE]. Use mw.ustring.toNFD() to break A WITH ACUTE into pieces and mw.ustring.toNFC() to do the reverse. —suzukaze (tc) 23:42, 2 September 2017 (UTC)
Thanks, I didn't realize it was that easy. DTLHS (talk) 23:49, 2 September 2017 (UTC)

Mobile App Word Game[edit]

Hi,

I am looking for some advice on changing the downloaded version of the Wiktionary so that the size and formatting of the data is in a workable format for my purposes. I am investigating how to rearrange the data into the following columns (preferably with some type of delimiter):

COL1 (The word)|COL2 (The meaning)

Is this at all possible?

Regards,

John.

Are you interested in a particular language? What about words that have multiple meanings? Are you interested in both lemmas and nonlemmas (cat vs cats)? DTLHS (talk) 16:41, 6 September 2017 (UTC)

inc-mgd[edit]

This language (already added) needs MOD:Brah-translit as a translit module. —Aryaman (मुझसे बात करो) 20:05, 6 September 2017 (UTC)

@Aryamanarora: Yes check.svg Done. — Eru·tuon 21:51, 6 September 2017 (UTC)

"Derived terms" thing not working at -thermic[edit]

When clicked, the arrow turns around as if to expand a list, but no list appears. (Using latest Chrome.) Equinox 21:16, 6 September 2017 (UTC)

Fixed. DTLHS (talk) 21:17, 6 September 2017 (UTC)

Redlinks from reconstruction pages[edit]

I was looking over Category:Proto-Indo-Iranian redlinks and I noticed that the redlinks from reconstruction pages, like those for PIE, aren't included in the list. Is that by design? Is there some way I can generate this list? --Victar (talk) 13:52, 7 September 2017 (UTC)

I don't know the reason, but {{redlink category}} only categorizes in mainspace pages. That could be changed using {{#switch:}}. — Eru·tuon 18:38, 7 September 2017 (UTC)
@Erutuon: Yeah, I don't see why not. Do we need a vote to add reconstruction pages? --Victar (talk) 02:42, 8 September 2017 (UTC)
@Angr, CodeCat, JohnC5, Metaknowledge what are your thoughts on this? --Victar (talk) 17:20, 9 September 2017 (UTC)
I don't have strong feelings one way or the other. I guess it makes sense to include links from the Reconstruction namespace as well, and probably Appendix namespace too. —Aɴɢʀ (talk) 17:24, 9 September 2017 (UTC)
I'm fine adding the Reconstruction namespace, though I don't know why the Appendix should be added. Do we put any lemmata in the Appendix now? —JohnC5 21:56, 10 September 2017 (UTC)
Okay, no objections so far and I can't think of a reason why not, so redlinks will now be tracked in the Reconstruction namespace. — Eru·tuon 22:39, 10 September 2017 (UTC)
Thanks, @Erutuon! --Victar (talk) 21:40, 12 September 2017 (UTC)
@JohnC5: We have lots of lemmas in Appendix namespace: Swadesh lists, lists of names, various other lists (e.g. Appendix:Burmese units of measure). —Aɴɢʀ (talk) 22:18, 12 September 2017 (UTC)
@Angr: Yep, I wasn't paying attention. Thanks! —JohnC5 22:46, 12 September 2017 (UTC)
I think it is useful to track the words in wordlists and stuff, so I've added the Appendix namespace. — Eru·tuon 23:20, 12 September 2017 (UTC)
Hmm, @Erutuon, it doesn't seem to be working right, i.e Proto-Indo-European *kʷékʷlos is coming up in Category:Proto-Indo-Iranian redlinks. --Victar (talk) 05:41, 14 September 2017 (UTC)
@Victar: Oh... good catch. That's because the page *čakrám doesn't exist. I'll have to make Module:redlink category check the pagename Reconstruction:Proto-Indo-Iranian/čakrám instead. — Eru·tuon 05:51, 14 September 2017 (UTC)
Yes check.svg Done (diff). — Eru·tuon 20:22, 14 September 2017 (UTC)
@Erutuon: Gangbusters! --Victar (talk) 20:47, 14 September 2017 (UTC)

what happened to the nocap parameter for the bor template?[edit]

I get an error message when I use this now? What gives?! Word dewd544 (talk) 14:21, 7 September 2017 (UTC)

See this conversation, essentially the inclusion of the "borrow" text is getting phased out. - TheDaveRoss 15:25, 7 September 2017 (UTC)
In other words, if you want to write {{bor|...|nocap=1}}, write {{bor|...|notext=1}} instead and write in "borrowing from" by hand. —Aɴɢʀ (talk) 12:20, 8 September 2017 (UTC)
Oy vey, what's with all the changes? I see. Well that's fine actually, as long as the ones that used "nocap" have been automatically converted to having "Borrowed from" as text before it. I guess this does make sense since it gives us more flexibility in using the template as part of an etymology, without having to use the "notext" parameter. Thanks. Word dewd544 (talk) 15:55, 8 September 2017 (UTC)
I (and probably others) have been doing some of those conversions, hopefully we are well along the way to having everything cleaned up. - TheDaveRoss 17:58, 8 September 2017 (UTC)
For the record, this change in {{bor}} was voted and approved here: Wiktionary:Votes/2017-06/borrowing, borrowed. --Daniel Carrero (talk) 18:02, 8 September 2017 (UTC)
Wait a sec, just to make things clear: so now it isn't even good practice to just start an etymology with the borrowed template without a notext, even if it's at the beginning of an etymology, because that will be phased out soon too? So always use notext=1 and write out "Borrowed or borrowing from..."? Word dewd544 (talk) 22:51, 22 September 2017 (UTC)
Isn't it obvious? DCDuring (talk) 23:47, 22 September 2017 (UTC)
DCD, you may think you're being funny, but it's really just low-quality trolling. Stop it. —Μετάknowledgediscuss/deeds 23:49, 22 September 2017 (UTC)
My severe ADD prevented me from reading the aforementioned discussion and vote on the matter. Word dewd544 (talk) 01:00, 25 September 2017 (UTC)

Lua memory errors related to Wikidata use in Module:senseid[edit]

There are quite a few pages in CAT:E with Lua memory errors. I think they are due to recent changes by @CodeCat in Module:senseid. Now, if a sense id formatted with {{senseid}} is a Wikidata id (QN), then the module does a bunch of stuff with the it: checking if the id is for a planet, continent, country, language, taxon, emotion, etc. Some part of this process is taking enough memory to cause quite a few pages to run out of memory.

I can see two obvious options: disable the Wikidata stuff in Module:senseid entirely, or create a list of the pages on which the function should not run (those currently running out of memory). — Eru·tuon 19:13, 8 September 2017 (UTC)

I thought there was an agreement not to include anything which uses Wikidata in the main namespace without approval. Was use of senseid with Wikidata discussed? - TheDaveRoss 19:24, 8 September 2017 (UTC)
The rationale was that since it currently only adds tracking categories it didn't need a discussion. DTLHS (talk) 19:28, 8 September 2017 (UTC)

(edit conflict) Hm, I might be wrong. I don't see {{senseid}} in fish, one of the pages that recently ran over the memory cap, for example. Maybe it's something else. But I don't feel like going through and checking each page. — Eru·tuon 19:27, 8 September 2017 (UTC)

Toggling the wikidata code on and off didn't seem to have much of an effect on memory- the template uses about 1 MB for the first invocation either way. —This unsigned comment was added by DTLHS (talkcontribs) at 19:28, 8 September 2017 (UTC).
I was wondering this myself as the errors started appearing, but they seem to be unrelated to the Wikidata stuff. —Rua (mew) 19:35, 8 September 2017 (UTC)
If I remove the translation table from language, usage drops from 50 MB to 10 MB. Was anything changed in Module:translations or the templates it depends on? Maybe a change in the Lua implementation itself? —Rua (mew) 19:44, 8 September 2017 (UTC)
I've been looking at recent changes in the Module namespace. It's hard to answer your question, because there are a lot of modules involved in an actual use of Module:translations: language and script data modules, transliteration modules, other modules that are loaded by another module when that module is loaded. — Eru·tuon 20:02, 8 September 2017 (UTC)
I still don't really understand why there are these extra restrictions on the use of Lua. —Rua (mew) 20:25, 8 September 2017 (UTC)
What extra restrictions are you referring to? — Eru·tuon 20:59, 8 September 2017 (UTC)
The memory limits based on how many Lua-fied templates you use on a page. A page shouldn't need more memory just because it has more Lua on it, because each template runs in its own sandbox. Different invocations don't need to share memory, so once one is finished processing, the memory should be freed. The only memory that should be kept across invocations is loadData stuff. If one invocation of {{t}} uses X amount of memory, then each invocation of {{t}} uses its own separate X amount of memory. The fact that memory usage accumulates when more invocations are added, indicates to me that there is something wrong with how Scribunto handles memory. —Rua (mew) 21:11, 8 September 2017 (UTC)
I'm tempted to agree, but I wish I knew just what all the accumulated memory was: previously loaded modules, module output, loaded data modules? It seems that previously loaded modules at least aren't shared between template invocations, as can be seen when I dump a representation of the package.loaded Lua variable on a page that uses other templates (see the current revision of Module:sandbox). But maybe there is other inaccessible memory usage in the Scribunto extension that counts towards the limit. — Eru·tuon 21:55, 8 September 2017 (UTC)
A possibility is that the software processes all Lua invocations in parallel threads, but using a shared memory pool. Since each template and module expansion is completely independent of any others, it's very parallelisable. On the other hand, the more parallel processing is done, the less memory each thread has for itself. If this is indeed how it's done, they could be more smart about it. For example, rather than just bailing out with an "out of memory" error, they could just throttle/stall some threads until some memory is freed up again once other threads finish, then resume. —Rua (mew) 22:39, 8 September 2017 (UTC)
To me, it looks like the Lua invocations are processed in order, so the invocation at which memory runs out moves higher up the page when there is more memory used. I also recall an odd case in which one template (I think it was {{zh-der}}) ran out of memory, but the ones after it didn't. So it looked like the one template went over the limit, but then its memory was freed up and the smaller-memory templates after it were able to run. — Eru·tuon 19:37, 9 September 2017 (UTC)
But then if each individual template doesn't run over the limit, why do we run over the limit when we have many of them? That shouldn't happen. The page would be just fine if only it didn't try to use more memory than was available. —Rua (mew) 20:09, 9 September 2017 (UTC)
Clearly there must be something adding more memory with each new use of Lua. But I don't know what or how. — Eru·tuon 20:16, 9 September 2017 (UTC)
You'd almost think they didn't want us to use it, and would prefer us to start using slow and clumsy template logic again... —Rua (mew) 20:50, 9 September 2017 (UTC)
All of the source code is fully viewable by anyone if you think you can improve it. DTLHS (talk) 20:51, 9 September 2017 (UTC)

Swahili classes >2[edit]

I can make pages for first, second, & third person conjugations of verbs, but what about the ma class, ki-vi class, & so on? Anjuna (talk) 05:33, 9 September 2017 (UTC)

@Science Bird: You can create these pages as well, although creating any of these inflected forms is not nearly as useful as creating lemma forms with definitions, because the inflected forms can always be created later by robots. —Μετάknowledgediscuss/deeds 11:13, 9 September 2017 (UTC)
Robots? Thank you. Is there a way to get them moving? Anjuna (talk) 13:44, 9 September 2017 (UTC)
We call them bots, and it's simply a matter of asking here for someone with a bot to do a particular task for you. In some cases, it may be better to wait until it's more clear what will need to be done and until there's enough potential work waiting to make a bot run worth it- but I have no idea if this is one of those cases. Chuck Entz (talk) 13:54, 9 September 2017 (UTC)

Distinguishing affixes that are identical in form[edit]

I want to have separate categories for prefixes that all take the form ma- but are distinct in use. I feel like this problem has been solved before somewhere, but I don't know where and how. @CodeCat, do you (or does anyone else) remember? —Μετάknowledgediscuss/deeds 02:04, 11 September 2017 (UTC)

@Metaknowledge: Category:English_words_suffixed_with_-er#mw-subcategories? —suzukaze (tc) 02:06, 11 September 2017 (UTC)
Thank you, the id1= (etc.) parameter does the job. —Μετάknowledgediscuss/deeds 18:56, 11 September 2017 (UTC)

Recentchanges tag filter inverse[edit]

Does anyone know if it's possible to filter recent changes for edits that are not labelled with a specific tag? DTLHS (talk) 04:19, 12 September 2017 (UTC)

No it is not possible.5.178.149.114 05:42, 12 September 2017 (UTC)

Template:quote categorizes the entry as having a usage example[edit]

For example, פרזלא is in the category Category:Aramaic terms with usage examples when it shouldn't be, because it only has a quotation. --WikiTiki89 20:07, 12 September 2017 (UTC)

Fixed. DTLHS (talk) 20:10, 12 September 2017 (UTC)

Visual Editor[edit]

The visual editor goes against all our style guidelines (see diff, for example). If this cannot be fixed, we should disable the visual editor entirely. --WikiTiki89 15:54, 13 September 2017 (UTC)

Abuse filter required[edit]

We're getting lots of English entries that are just the generated rfdef template, with no attempt to fill it in. (Part of speech varies.) Can we block these? Also, a lot of the entry titles are in Arabic script. Can we block any attempt to create an English entry with Arabic characters in the title? Equinox 22:52, 13 September 2017 (UTC)

  • Yes please - these are getting annoying. SemperBlotto (talk) 11:01, 19 September 2017 (UTC)
@Equinox: I am happy to try and create an edit filter, do you have a couple of diffs I could use as a basis/test? - TheDaveRoss 11:40, 19 September 2017 (UTC)
This Arabic-script one was just created: معلومات_عن_العادة_السرية. Equinox 13:23, 19 September 2017 (UTC)
Another: فتيات من ورقلة. Equinox 14:08, 19 September 2017 (UTC)
Another, created as sign-language rather than English: پروتز. Equinox 17:22, 19 September 2017 (UTC)
This last one is a bit different: Persian rather than Arabic, and a word that I think we actually ought to have (I reckon it means "prosthesis") rather than an entry that should never exist. —Μετάknowledgediscuss/deeds 22:24, 19 September 2017 (UTC)
I'm a little concerned about how to distinguish between the normal case with the new entry creator, where everything is preloaded with the empty templates and then edited by the contributor before saving, and the bad cases, where it's saved without being edited- they both start out identical. Chuck Entz (talk) 16:19, 19 September 2017 (UTC)
I created Special:AbuseFilter/72 which is currently only tagging such entries (rfdef). If the user clicks a template and edits before saving to remove the {{rfdef}} it is not tagged, however if they create the entry with the {{rfdef}} and intend to edit is further in subsequent edits we are never going to be able to capture that. - TheDaveRoss 11:42, 22 September 2017 (UTC)
I created some entries with {{rfdef}} only yesterday, for example ruibi. So we should probably choose some better way to recognise these edits. —Rua (mew) 11:52, 22 September 2017 (UTC)
It only flags new entries by anonymous users, so your creations would not be tagged. - TheDaveRoss 12:31, 22 September 2017 (UTC)
They are still getting through. SemperBlotto (talk) 19:50, 23 September 2017 (UTC)

Improvements coming soon to Recent Changes[edit]

Rc-beta-tour-welcome-ltr.gif

Hello

Sorry to use English. Please help translate to your language! Thank you.

In short: starting on 26 September, New Filters for Edit Review (now in Beta) will become standard on Recent Changes. They provide an array of new tools and an improved interface. If you prefer the current page you will be able to opt out. Learn more about the New Filters.

What is this feature again?

This feature improves Special:RecentChanges and Special:RecentChangesLinked (and soon, Special:Watchlist – see below).

Based on a new design, it adds new features that ease vandalism tracking and support of newcomers:

  • Filtering - filter recent changes with easy-to-use and powerful filters combinations, including filtering by namespace or tagged edits.
  • Highlighting - add a colored background to the different changes you are monitoring. It helps quick identification of changes that matter to you.
  • Bookmarking to keep your favorite configurations of filters ready to be used.
  • Quality and Intent Filters - those filters use ORES predictions. They identify real vandalism or good faith intent contributions that need help. They are not available on all wikis.

You can know more about this project by visiting the quick tour help page.

Concerning RecentChanges

Starting on 26 September, New Filters for Edit Review will become standard on Recent Changes. We have decided to do this release because of a long and successful Beta test phase, positive feedback from various users and positive user testing.

Some features will remain as Beta features and will be added later. Learn more about those different features.

If your community has specific concerns about this deployment or internal discussion, it can request to have the deployment to their wikis delayed to October 1, if they have sensible, consistent with the project, actionable, realistic feedback to oppose (at the development team's appreciation).

You will also be able to opt-out this change in your preferences.

Concerning Watchlists

Starting on September 19, the Beta feature will have a new option. Watchlists will have all filters available now on the Beta Recent Changes improvements.

If you have already activated the Beta feature "New filters for edit review", you have no action to take. If you haven't activated the Beta feature "New filters for edit review" and you want to try the filters on Watchlists, please go to your Beta preferences on September 19.

How to be ready

Please share this announcement!

Do you use Gadgets that change things on your RecentChanges or Watchlist pages, or have you customized them with scripts or CSS? You may have to make some changes to your configuration. Despite the fact that we have tried to take most cases into consideration, some configurations may break. The Beta phase is a great opportunity to have a look at local scripts and gadgets: some of them may be replaced by native features from the Beta feature.

Please ping me if you have questions.

On behalf of the Global Collaboration team, Trizek (WMF) 15:27, 14 September 2017 (UTC)

@Trizek (WMF): I guess the Watchlist filter beta is out now. Here is my main serious issue with it: it makes the Watchlist take a good amount of extra time to load, which is a severe issue for those who refresh their Watchlist frequently. I would hope there would be a solution that allows the Watchlist to load in the normal amount of time when no filters are active. In fact I'm disabling this feature, as the Watchlist is now unusable for me. --WikiTiki89 16:41, 19 September 2017 (UTC)

Why is domoic broken? -- Red Lua error[edit]

This syntax worked fine the other day. Equinox 22:17, 14 September 2017 (UTC)

@Erutuon DTLHS (talk) 22:22, 14 September 2017 (UTC)
@DTLHS, Equinox: Thanks for the ping. Yes, it was me. I believe it's fixed now. — Eru·tuon 22:44, 14 September 2017 (UTC)

Can't reply to LiquidThreads posts[edit]

@IvanScrooge98 I use LiquidThreads on my talk page. When I click reply to answer someone's post, a new window with a spinny thing appears as usual. However, the spinny thing is supposed to disappear and an edit window should appear instead. Now, the spinny thing stays forever. This makes it impossible for me to post anything in LiquidThreads. Can this be fixed, please? —Rua (mew) 13:41, 17 September 2017 (UTC)

@CodeCat: mmh, no clue. When I do, the “spinny thing” does not appear in a new window but right below the thread, giving me the same problem though. If I open the link in a new window, a perfectly normal editor appears, allowing me to reply. [ˌiˑvã̠n̪ˑˈs̪kr̺ud͡ʒʔˌn̺ovã̠n̪ˑˈt̪ɔ̟t̪ːo] (parla con me) 13:46, 17 September 2017 (UTC)
Ah, that works for me. Thank you for suggesting that. Still, the problem stands. —Rua (mew) 14:36, 17 September 2017 (UTC)

8-cell and categorising by characters[edit]

Category:English terms spelled with 8 is currently manually added to this page. Module:headword is supposed to automatically categorise terms by their characters, making this manual category superfluous. However, {{en-noun}} isn't adding this category automatically. Is something missing in our data? The same applies to Chinese on 69. —Rua (mew) 14:35, 17 September 2017 (UTC)

Something wrong with Tabbed languages[edit]

Some pages aren't displaying Tabbed languages correctly. At bod, the ==Volapük== line is at the very bottom of the page and all the Volapük info is inside the Swedish tab. At faen, it's the ==Norwegian Bokmål== that's at the very bottom of the page and all the Norwegian Bokmål info is inside the Bislama tab. But other pages with multiple languages are displaying everything correctly. —Aɴɢʀ (talk) 09:14, 19 September 2017 (UTC)

No ideas? It still isn't fixed. It's apparently related to the special characters in the language names, because changing them to ==Volapuk== and ==Norwegian Bokmaal== solves the problem, though obviously that's not a desirable solution. —Aɴɢʀ (talk) 10:54, 20 September 2017 (UTC)
Do you know where the code for tabbed languages is? --WikiTiki89 14:39, 20 September 2017 (UTC)
Never mind, found it. I'll take a look. --WikiTiki89 14:40, 20 September 2017 (UTC)

So here's what I found: A heading with no special characters looks like this in the HTML:

<h2>
  <span class="mw-headline" id="Bislama">Bislama</span>
  <span class="mw-editsection">...</span>
</h2>

While a heading with special characters looks like this:

<h2>
  <span id="Norwegian_Bokmål"></span>
  <span class="mw-headline" id="Norwegian_Bokm.C3.A5l">Norwegian Bokmål</span>
  <span class="mw-editsection">...</span>
</h2>

I'm guessing the line <span id="Norwegian_Bokmål"></span> is a new addition to support section links directly with special characters in addition to the old format. It doesn't look like the tabbed languages code knows how to handle that. --WikiTiki89 14:53, 20 September 2017 (UTC)

Is it fixed? --WikiTiki89 15:16, 20 September 2017 (UTC)
Seems to be. Thanks for your help! —Aɴɢʀ (talk) 15:29, 20 September 2017 (UTC)

Inflection templates categorizing in non-mainspace entries[edit]

Appendix:Snowclones/don't X me, Citations:elephant juice for example. Can this be disabled? DTLHS (talk) 18:51, 21 September 2017 (UTC)

It should be possible, but what are the cases in which categorization needs to be disabled? English headwords in Appendix and Citations namespaces, or any non-appendix-language headword in those namespaces? — Eru·tuon 00:58, 22 September 2017 (UTC)
Well, appendix languages should only categorize in appendices, reconstructed languages only in the reconstructed namespace, everything else only in the main namespace. Would that work? DTLHS (talk) 05:24, 22 September 2017 (UTC)
It's a little more complicated. {{citation}} uses {{cln}}, which is handled by the format_categories function in Module:utilities, and Latin has some Reconstructed entries (*genuclum), but it's not a reconstructed language. So sometimes the function needs to add categories in the Reconstruction namespace for regular languages, and in the Citations namespace. It might be okay to have the function only add categories to an Appendix page if the language is appendix-constructed, though. I doubt someone would use the function to categorize other types of Appendix pages, because it assumes that the title is in the language in question. For the headword in a citations page, there probably has to be a specific exception. — Eru·tuon 05:45, 22 September 2017 (UTC)
I'm still in favour of deleting appendix-constructed languages altogether. —Rua (mew) 12:16, 22 September 2017 (UTC)
Could there be "cat" and/or "nocat" parameters to allow for missing exceptions and reduce the need for excessive complication of template/Lua. DCDuring (talk) 12:20, 22 September 2017 (UTC)

Extra IPA characters in box below edit area[edit]

Would somebody be able to add ŋ̊ and ɲ̊ to the list of IPA characters in the clickable box below edit area (sorry, I don't know the technical name)? These are both used transcribing Icelandic words in IPA, and I am currently going through all the Icelandic nouns to add missing transcriptions so this would be very useful. Thanks, BigDom 10:45, 22 September 2017 (UTC)

A better solution in the long term would be to have buttons that add combining diacritics separately. Then you could make any combination you want. Wikipedia does it this way. —Rua (mew) 12:15, 22 September 2017 (UTC)
Yes, that would be even better. BigDom 13:46, 22 September 2017 (UTC)
The list of characters is called CharInsert, and it's located at MediaWiki:Edittools, while the script that makes it actually work is at MediaWiki:Edit.js. — Eru·tuon 17:40, 22 September 2017 (UTC)

Please add Persian translation of dotard[edit]

The entry dotard has been locked. Please add its Persian translation as follows:

  • language code: fa
  • translation: خرفت
  • transliteration: xereft

Thank you 4nn1l2 (talk) 12:02, 22 September 2017 (UTC)

Added and changed protection level. DTLHS (talk) 17:28, 22 September 2017 (UTC)

Tabbed languages miscategorising at balts[edit]

@Donnanz The Dutch tab is completely missing the categories. Instead they're placed under Latvian for some reason. —Rua (mew) 23:06, 22 September 2017 (UTC)

@CodeCat: Did you ping the right person? I have never edited the page. DonnanZ (talk) 23:16, 22 September 2017 (UTC)
<:ref name="LEV"/> is entered in the Latvian entry, but I have no idea why it comes before Dutch in the category listings and is separated from the rest of the Latvian categories. DonnanZ (talk) 23:53, 22 September 2017 (UTC)
Me and names, bleh. It was the other person with a D. I still can't remember it. —Rua (mew) 11:07, 23 September 2017 (UTC)
@Dixtosa I think. DTLHS (talk) 17:14, 23 September 2017 (UTC)
Yes, thank you, yet another person with a D. —Rua (mew) 18:17, 23 September 2017 (UTC)

MOD:languages/data3/a[edit]

Can someone change the ancestor for awa (Awadhi) to pka? And add MOD:hi-translit as the translit module for it. —Aryaman (मुझसे बात करो) 20:55, 24 September 2017 (UTC)

@Aryamanarora: Yes check.svg Done (diff). — Eru·tuon 05:21, 26 September 2017 (UTC)

Expensive parser function calls in [edit]

@Wyang, Suzukaze-c: This page is exceeding the limit of expensive parser function calls (500). I suspect this is because of all the Chinese templates that retrieve pinyin from other pages. There was a module error in the Korean headword because Module:headword was trying to find out if the page Wiktionary:Korean transliteration existed, but I fixed that by stopping the function call. (So now the Korean headword doesn't link to the transliteration policy page.)

Errors may pop up again if more Chinese usage examples or compounds with entries are added, or when more compounds get their own entries from which pinyin can be retrieved. A temporary solution would be to remove usage examples or compounds.

Perhaps a more permanent solution would be having a whole host of data modules for pinyin, or a database somewhere else that somehow acquires and stores the pinyin from our entries automatically, allowing it to be retrieved by the module less expensively. — Eru·tuon 08:24, 28 September 2017 (UTC)

Reduced the load a bit by removing some of the secondary compounds. Having a database-like structure would definitely be ideal. Wyang (talk) 09:05, 28 September 2017 (UTC)

Allowing Template:attention to ping people, is it feasible?[edit]

Is it possible to modify {{attention}} in some way so that, if you include a user's name in the text preceded by an @, then it pings the user in question to come look at the page? —Rua (mew) 12:05, 28 September 2017 (UTC)

Pings have to be signed. Chuck Entz (talk) 15:06, 28 September 2017 (UTC)
I would say it would be preferable anyway to ping them from the talk page instead. --WikiTiki89 18:03, 28 September 2017 (UTC)

News for editors link -- remove/fix?[edit]

The link at the top of the page, I mean. It makes the whole page sort of skip downwards when it loads, such that if you click before that, you probably misclick. Can it be removed (it doesn't really seem as important as its placement would indicate), or maybe have a space reserved for it or something Sorry if there's some obvious fix to it.__Gamren (talk) 15:51, 28 September 2017 (UTC)

Never mind, it was just this thing: MediaWiki:Sitenotice.__Gamren (talk) 13:07, 14 October 2017 (UTC)
Thank you! —Rua (mew) 15:24, 14 October 2017 (UTC)

Clueless Mobile Edits[edit]

There have been quite a lot of junk edits lately, and I suspect it has something to do with the capability of searching Wiktionary being added somewhere in the mobile interface without adequate explanation. That means people think that they're searching the web when they're actually searching Wiktionary, and that they end up editing or creating entries without realizing that's what they're doing.

What do you think about adding text to the edit screen saying something like:

  • You are editing a page at Wiktionary, an online dictionary, and your content will be added to the dictionary if you proceed. If that's not what you meant to do, please click "Cancel".

I'm hoping this will reduce the volume of random garbage that keeps getting added to entries for no apparent reason, though not everyone doing this reads English, and some won't care. Chuck Entz (talk) 23:50, 28 September 2017 (UTC)

I feel certain such people wouldn't read it, and don't read generally. Just more clutter. Equinox 09:15, 30 September 2017 (UTC)

Watchlist[edit]

What the blazes has happened to the my watchlist (I'm not aware of changing anything):

  • it's too "busy"
  • I can't see the old "hide" options
  • the current votes box is in the middle of the screen and squished "wanted"/"utilities" against the left margin
I could go on! — Saltmarsh. 06:46, 29 September 2017 (UTC)

TextExtracts[edit]

I came across butterfly and noticed that there is stuff before the page starts, that ends up in our search results and other forms of TextExtracts (like the sister search results on the Search page). It might be wise to add the "noexcerpt" class to templates like {{Commons}}, or alternatively add noprint to the configuration of classes that are ignored when generating the short textextracts. TheDJ (talk) 14:09, 29 September 2017 (UTC)

Importing a large list of words into multiple appendices[edit]

I've got a dump of all Russian terms from the Russian Wiktionary. I have removed all capitalised terms, terms with "-" and ".", so it's a list of all solid words. There are altogether 238,646 words. I'd like create some appendices, so that missing terms (red-linked) could gradually be filled. What is the maximum acceptable size of an appendix? I was getting errors about the size of the allowed files on 50,000 words, then reduced to 10,000. Now I am getting Wikimedia errors. Loading files like this will take for ever. Is there a quicker way? --Anatoli T. (обсудить/вклад) 06:30, 30 September 2017 (UTC)

10,000 words should be possible on a single page, assuming you are using plain links. What error are you getting? DTLHS (talk) 06:33, 30 September 2017 (UTC)
I got it now, thanks, after two retries. This is the first portion of the dump: User:Atitarev/Ru-wiki-solid-Russian-terms-dump/1, which is only 1/24th of the total. --Anatoli T. (обсудить/вклад) 06:36, 30 September 2017 (UTC)
@Atitarev I think I have a script which can remove the blue-links from those lists if you would like, or would you prefer to audit them and remove them manually? - TheDaveRoss 12:28, 2 October 2017 (UTC)
@TheDaveRoss: Thanks, the dumps are now at [[User:Atitarev/Ru-wiki-solid-Russian-terms-dump]] - 24 pages. It's too much to audit manually. I did already a basic cleanup, as much as I could, even if it still contains a lot of non-lemmas. It would be great if you could remove the blue links. Ideally, only those that have the Russian L2 header only. I will also need to split them by the first letter alphabetically rather than by number but I'll do it myself if you don't. Each page currently has exactly 10,000 terms, except for the last one - @User:Atitarev/Ru-wiki-solid-Russian-terms-dump/24. Note that words starting with "ё" are in the last page but they should follow "е".--Anatoli T. (обсудить/вклад) 12:45, 2 October 2017 (UTC)
@TheDaveRoss: Hello, please advise if you're still interested in helping and, which part you can do. --Anatoli T. (обсудить/вклад) 01:52, 9 October 2017 (UTC)
I will try and get to this this week. - TheDaveRoss 13:44, 10 October 2017 (UTC)

October 2017

Wiktionary:Administrators/List of administrators[edit]

Wouldn't it be possible to automatise this list, and add a self-updating column "Date of last edit"? --Barytonesis (talk) 18:57, 1 October 2017 (UTC)

abstinence of war is not a one-syllable word[edit]

For some reason, abstinence of war has ended up in Category:English 1-syllable words. I'm guessing this error has something to do with Template:IPA. That template hasn't been edited recently, though, so I'm not sure what's going on. MewBot has been making edits related to the category lately, so maybe User:CodeCat will know what the problem is? —Granger (talk · contribs) 18:30, 4 October 2017 (UTC)

{{IPA}} categorizes syllables for each parameter. In this case "ʌv" and "wɔɹ" are single syllables. DTLHS (talk) 18:31, 4 October 2017 (UTC)
Thanks, that makes sense. I see that it's in Category:English 3-syllable words too. Is there a way to remove the entry from those categories? —Granger (talk · contribs) 18:36, 4 October 2017 (UTC)
Remove the pronunciation since it can be found from the individual component words. DTLHS (talk) 18:39, 4 October 2017 (UTC)
I thought we decided that {{IPA}} should not add these categories at all. --WikiTiki89 18:45, 4 October 2017 (UTC)
Who is "we"? I think it works quite well. DTLHS (talk) 18:48, 4 October 2017 (UTC)
"We" is the WT:BP. But it looks like it's been improved since we had that conversation. Was there any discussion to reinstate this functionality? --WikiTiki89 18:53, 4 October 2017 (UTC)
What was agreed in a previous discussion that I found in this search was that the template needs a parameter that turns off syllable counting. Perhaps there is another discussion that I missed. I finally implemented that now. — Eru·tuon 19:58, 4 October 2017 (UTC)
Proxima Centauri apparently has 12 and 13 syllables. Equinox 21:08, 4 October 2017 (UTC)
Yes, it does. DTLHS (talk) 21:16, 4 October 2017 (UTC)
Now fixed, but I'm struggling to hear how it could be pronounced with 7 syllables. DTLHS (talk) 21:20, 4 October 2017 (UTC)
It's because -aʊə- counts as two syllables. Consider whether hour is 1 syllable or 2. —Rua (mew) 21:40, 4 October 2017 (UTC)

How do I turn off the new Recent Changes?[edit]

It would be fine, but on my old computer it's too slow to load all that script. I went to my Preferences, Beta features tab, but it's already unticked there. Saving didn't help. Equinox 18:37, 5 October 2017 (UTC)

I wish it didn't have to load, but was just available as soon as the rest of the page. All these gadgets with their own load delays annoy me. —Rua (mew) 18:48, 5 October 2017 (UTC)
I would like it a lot more if the list automatically updated periodically. DTLHS (talk) 20:27, 5 October 2017 (UTC)
What exactly do we have to do to go back to the old system? SemperBlotto (talk) 20:45, 5 October 2017 (UTC)
@SemperBlotto: you have to go to "Special:Preferences", then to the tab "Recent changes". There's the following tick box: "Hide the improved version of Recent Changes" - Rolls back the 2017 interface redesign and all tools added then and since. --Barytonesis (talk) 20:49, 5 October 2017 (UTC)
Found it. Thanks. SemperBlotto (talk) 20:53, 5 October 2017 (UTC)

new block page[edit]

When an admin blocks a user, we now get a new page with lots of white space that we have to scroll down. It doesn't seem to add any new function and is annoying. Is there any way we can get rid of it? SemperBlotto (talk) 05:43, 6 October 2017 (UTC)

I don't see it. Screenshot? DTLHS (talk) 05:47, 6 October 2017 (UTC)
After several minutes trying to remember how to take a screenshot - it's at
block Capture.PNG
SemperBlotto (talk) 06:01, 6 October 2017 (UTC)
Try adding these rules to your common.css: #blockiptext { display: none; } and .oo-ui-fieldLayout.oo-ui-labelElement, .oo-ui-fieldLayout.oo-ui-fieldLayout-align-inline { margin-top: .01em; } DTLHS (talk) 06:16, 6 October 2017 (UTC)
OK. I didn't have one of those. Created it with ONLY the above code. Seems to be better. It won't be long before I use it for real. Thanks. SemperBlotto (talk) 06:26, 6 October 2017 (UTC)
Gratuitous white space is modern and sexy. The scrolling is worth it. (but seriously why are these redesigns so damn ugly in Monobook) —suzukaze (tc) 06:55, 6 October 2017 (UTC)
It's been put back the way it was - excellent! SemperBlotto (talk) 06:16, 8 October 2017 (UTC)

Batch fix request[edit]

"From Borrowing from". Wyang (talk) 07:43, 6 October 2017 (UTC)

@Wyang: done. —JohnC5 09:00, 6 October 2017 (UTC)
@JohnC5 Thanks! Wyang (talk) 09:11, 6 October 2017 (UTC)

Getting a list of...[edit]

Entries (or language sections) with an unbalanced number of {}, or []? (potentially good cleanup list.) Wyang (talk) 09:12, 6 October 2017 (UTC)

While useful, it might be hard to find out which of them is unmatched on a long page. So I would suggest that the dump also includes an excerpt from the wikicode which highlights exactly which bracket is missing a pair. —Rua (mew) 10:38, 6 October 2017 (UTC)
On Wikipedia, w:User:BracketBot used to do something somewhat similar, but it hasn't been active since July 2016. I believe there used to be a Toolserver page that allowed users to find pages with unpaired brackets and highlighted the brackets in question, but I don't know if anything similar currently exists. —Granger (talk · contribs) 11:28, 6 October 2017 (UTC)
@Wyang User:DTLHS/cleanup/unbalanced brackets. DTLHS (talk) 17:09, 6 October 2017 (UTC)
@DTLHS Thanks! Wyang (talk) 22:43, 6 October 2017 (UTC)

Complex URLs don't work in single-bracket link syntax[edit]

See normalphobia, please advise. Equinox 17:13, 7 October 2017 (UTC)

You gotta escape those damn quotation marks. — Ungoliant (falai) 17:16, 7 October 2017 (UTC)

Link language in template m+[edit]

I noticed that {{m+}} is not linking the language to the Wikipedia article, unlike other similar templates. This is inconsistent. Can someone fix this, please? If no one does, I may try doing it by myself.

Examples:

  • {{m+|fr|qwerty}} = French qwerty (currently does not link to the Wikipedia article)
  • {{cog|fr|qwerty}} = French qwerty (currently links to the Wikipedia article)

Thanks in advance. --Daniel Carrero (talk) 21:38, 7 October 2017 (UTC)

And we also have {{noncog}}. Some of these should probably be merged. —Rua (mew) 21:47, 7 October 2017 (UTC)
{{m+}} was created in a discussion in July, and @Florian Blaschke requested that the language name be unlinked by default, because in many cases the language is well-known and the link isn't all that useful. I find that sort of convincing, but I recognize that it is somewhat confusing for the behavior of {{cog}} and {{noncog}} to be different from that of {{m+}}.
It is easy to change the default behavior in Module:links/templates, but note that there's currently a parameter that turns Wikipedia links on, so if the behavior of the template changes, current instances of the template should probably have the no-Wikipedia-link parameter added so that their display doesn't change. Or it could be resolved that the language name should always be linked. — Eru·tuon 22:14, 7 October 2017 (UTC)
Arguably, all languages should be linked by default in {{noncog}} and {{m+}} because that's what all other templates do: {{der}}, {{bor}}, {{inh}} and even the deprecated {{etyl}}. We could say this is the status quo. We are free to discuss and change that, of course, but I'd like any changes to be reflected in the other templates as well.
--Daniel Carrero (talk) 22:22, 7 October 2017 (UTC)
All those other templates are used in etymologies though, where people are likely to encounter languages they're not familiar with. Can the same be said for {{m+}}? Also, it is worth considering that years ago, we had a rule to link some languages in translations but not others. We eventually decided to make it consistent and not link any of the languages. Perhaps the same should be done here. —Rua (mew) 22:56, 7 October 2017 (UTC)
I prefer to use {{m+}} in etymologies when the language has already been mentioned. That way, the link appears only at the first mention of the language, but not at subsequent mentions, which would be annoying. —Aɴɢʀ (talk) 15:06, 8 October 2017 (UTC)

New editor -- horrid[edit]

What's with the new editor? This is appearing since last week. Everything is harder to do -- it loads slower, it sometimes grabs the wrong section for editing, lots of things are hidden now, and everything except typing takes more clicks than before.

Anyone know how to disable this monstrosity? ‑‑ Eiríkr Útlendi │Tala við mig 22:17, 7 October 2017 (UTC)

Check your preferences under "beta features". DTLHS (talk) 22:39, 7 October 2017 (UTC)
@DTLHS: THANK YOU. That was driving me batty. Nearly a textbook example of bad user experience. ‑‑ Eiríkr Útlendi │Tala við mig 00:02, 8 October 2017 (UTC)

Category:French words suffixed with -ment[edit]

As there are two different suffixes -ment (verb → noun vs. adjective → adverb), I've split this category in two (I'm not terribly satisfied of the naming, so I'm open to suggestions):

Would it be possible to run a bot that would assign all the entries using the POS header ===Noun=== to the first one, and the ones using ===Adverb=== to the second? --Barytonesis (talk) 17:22, 8 October 2017 (UTC)

Category:German words suffixed with -en and Category:Dutch words suffixed with -en need similar treatment: substance if adjective, denominative if verb. Additionally, Category:German adjectives suffixed with -en needs to be converted to Category:German words suffixed with -en (substance). —Rua (mew) 19:09, 8 October 2017 (UTC)
Category:English words suffixed with -ly > Category:English words suffixed with -ly (adjectival) and Category:English words suffixed with -ly (adverbial). --Barytonesis (talk) 19:54, 13 October 2017 (UTC)

Pull-down listing of reasons for reversions and undos[edit]

See Wiktionary:Beer_parlour/2017/October#Please.2C_please_reveal_the_cause_of_the_revert_in_the_edit_summary.

This seems to me a desirable change, though it might need BP discussion.

What would have to be done to provide pull-down listings of reasons for reversion or undoing of contributions? As to content the pulldown listing of reasons for entry deletion would be a start. DCDuring (talk) 19:06, 8 October 2017 (UTC)

If you want to leave a reason you can use undo instead of reversion. DTLHS (talk) 19:14, 8 October 2017 (UTC)
The pull-down menu would be useful to facilitate actually providing a reason, without typing, especially for reversion/undoing of contributions by newbies, anons etc. DCDuring (talk) 19:24, 8 October 2017 (UTC)

proscribed viri(i)[edit]

How can we lay-out in virus that both viri and virii are proscribed? Sobreira ►〓 (parlez) 11:51, 11 October 2017 (UTC)

  • Better now? —Aɴɢʀ (talk) 12:08, 11 October 2017 (UTC)
    • Thanks. I tried with the order, not with the numbers. Sobreira ►〓 (parlez) 12:34, 11 October 2017 (UTC)
      • Named parameters can come in any order. —Aɴɢʀ (talk) 17:23, 11 October 2017 (UTC)

catalyses (n) and catalyses (v)[edit]

My doubt: as in analyses, shouldn't catalyses have two etymologies? Would the plural of catalysis have also a different pronounciation from the present of to catalyse. Sobreira ►〓 (parlez) 12:34, 11 October 2017 (UTC)

Yes. DTLHS (talk) 17:27, 11 October 2017 (UTC)
Yes check.svg DoneAɴɢʀ (talk) 17:34, 11 October 2017 (UTC)

The Wiktionary search 'incategory:"English noun plural forms" incategory:"English third-person singular forms" -"Etymology 2"' found 4,791 such entries with no second Etymology. This would be an underestimate of the size of the total problem. DCDuring (talk) 18:47, 11 October 2017 (UTC)

It seems like a low priority unless the noun and verb forms have different pronunciations. DTLHS (talk) 18:56, 11 October 2017 (UTC)
I agree. It's a particularly high priority when one form has an alternative spelling (in this case, catalyzes) that the other form doesn't have. When only the pronunciation is different, the solution at houses is adequate IMO. —Aɴɢʀ (talk) 19:11, 11 October 2017 (UTC)

Pings not working[edit]

Pings for me haven't been showing up at all for about 3-4 days now. Anyone else experiencing the same? Wyang (talk) 20:09, 11 October 2017 (UTC)

Same here (test: @Wyang) DTLHS (talk) 20:18, 11 October 2017 (UTC)
I have no idea. Has anyone pung me lately? —Aɴɢʀ (talk) 20:21, 11 October 2017 (UTC)
Being discussed at w:Wikipedia:Village pump (technical)#Not receiving pings and phab:T177825. -- John of Reading (talk) 20:25, 11 October 2017 (UTC)
Ah, thanks. It's a pity that they downgraded it from high priority. I miss the pingable days; I feel people tend to be more active when they can see others have pung them at various places. Wyang (talk) 07:03, 12 October 2017 (UTC)
It does make it less easy to communicate, especially for those of use who like to use it in talk pages instead of using WT:TR. (BTW, pung lol... the entry for ping only has pinged as a past tense... do people actually use pung?) — justin(r)leung (t...) | c=› } 07:40, 12 October 2017 (UTC)
No, of course not. I said it as a joke. (But pung is only the past participle; the past tense would of course be pang.) It would also be possible to model it on bring and have ping – pought – pought. —Aɴɢʀ (talk) 08:36, 12 October 2017 (UTC)
Haha :D — justin(r)leung (t...) | c=› } 18:55, 12 October 2017 (UTC)
  • @Wikitiki89, as this explains our recent confusion over his pings not going through... but of course, my ping probably won't work. —Μετάknowledgediscuss/deeds 07:08, 12 October 2017 (UTC)
Try to updated yours preferences saving some change and then saving it back. It worked for me. On Special:Preferences#mw-prefsection-echo I changed to mention->email, I received a ping by email, I restored preferences back to "web" and now it is working fine onwiki. Of course, it won't work for pinging others, but for receiving pings to you. --Vriullop (talk) 16:05, 12 October 2017 (UTC)

Spacing issue[edit]

What's going on at bila#Swahili with the Arabic etymon? I'm not seeing a space between the words "Arabic" and بِلَا. —Μετάknowledgediscuss/deeds 19:47, 14 October 2017 (UTC)

I can see a space on my computer: [1]. Wyang (talk) 23:37, 14 October 2017 (UTC)
I can see it, too. — justin(r)leung (t...) | c=› } 00:41, 15 October 2017 (UTC)
What browser? Are you using any extensions or messing with fonts that could cause this? DTLHS (talk) 00:43, 15 October 2017 (UTC)
The problem only occurs on Safari. That's weird, but I guess I won't worry about it then. —Μετάknowledgediscuss/deeds 02:37, 15 October 2017 (UTC)

Adding Xiongnu and Xianbei as etymology-only languages[edit]

Would be handy for Chinese etymologies. How should I go about this, and what code should they have? Wyang (talk) 08:06, 15 October 2017 (UTC)

Module:etymology languages/data. I'm not sure of the exact rules for coming up with a code, but it looks like (closest parent language)-(three letters representing language). DTLHS (talk) 17:37, 15 October 2017 (UTC)
In this case you want to format them like Turduli (q.v.), as und-xnu and und-xbi or whatever three letters make sense to you. (Unless Xianbei is so clearly Mongolic that you'll want to be deriving terms back to Proto-Mongolic, in which case the code should begin with xgn-.) —Μετάknowledgediscuss/deeds 17:52, 15 October 2017 (UTC)
If they're etymology-only languages, they need a parent language (i.e. the language that they're considered a "dialect" of). That can be und, as it is for Turfuli, but in that case Xianbei probably shouldn't be given a code starting with xgn-. —Aɴɢʀ (talk) 19:58, 15 October 2017 (UTC)
Ah, thanks for pointing that out. They'd best be und. —Μετάknowledgediscuss/deeds 21:05, 15 October 2017 (UTC)
Thanks all. I added them under the codes of und-xnu and und-xbi. Wyang (talk) 07:55, 16 October 2017 (UTC)

Looking for small technical tasks+mentors for new contributors - got something in mind?[edit]

Hi everybody! Google Code-in (GCI) will soon take place again - a seven week long contest for 13-17 year old students to contribute to free software projects. Tasks should take an experienced contributed about two-three hours and can be of the categories Code, Documentation/Training, Outreach/Research, Quality Assurance, and User Interface/Design. Do you have an idea for a task and could you imagine mentoring that task? For example, do you have something on mind that needs documentation, research, some gadget or template issues on your "To do" list but you never had the time, and can imagine enjoying mentoring such a task to help a new contributor? If yes, please check out mw:Google Code-in/2017 and become a mentor! Thanks in advance! --AKlapper (WMF) (talk) 19:55, 16 October 2017 (UTC)

About show/hide sections[edit]

Hi you all! (Sorry for my English)

I am an Admin from Turkish Wiktionary and have been working on some extensions lately to improve Turkish Wiktionary in a level which English Wiktionary reached at this point. I updated the Commons.js file few days ago; this was inevitable, because we had to use "the show/hide" feature on translitions template. I managed to translate this feature with the "Visibility" title that shown on sidebar. But as you can see on this page, it doesn't work on mobile pages. We should do an extra change for that? If anyone can help, that would be nice. Thanks! HastaLaVi2 (talk) 08:46, 17 October 2017 (UTC)

@HastaLaVi2 See MediaWiki:Mobile.js. --Vriullop (talk) 12:13, 17 October 2017 (UTC)

Transcriptions[edit]

In what module is the code that shows transcriptions automatically when writing a non-latin scripted word in {{m}} or {{l}} etc.? We intend to use it at sv.wikt.Jonteemil (talk) 21:00, 17 October 2017 (UTC)

The code that handles these templates is in Module:links, but this module calls on a function in Module:languages to create a transliteration, where it gets forwarded to the language's transliteration module. Different languages have different transliteration modules. —Rua (mew) 21:02, 17 October 2017 (UTC)
See Category:Transliteration modules for a full list of the modules. The Language data modules specify which module is used by which language. — Eru·tuon 21:26, 17 October 2017 (UTC)
@Erutuon Thank you!Jonteemil (talk) 23:20, 17 October 2017 (UTC)

Memory issues[edit]

The page e doesn't check for redlinks and it uses {{t-simple}}. Despite that, it's still running out of memory before it gets to the end. What's the next step to fix this? —Μετάknowledgediscuss/deeds 06:05, 20 October 2017 (UTC)

It barely has any translations so that's not the problem. One possibility is splitting the page into language subpages (this is not currently possible, since many templates rely on the page name). DTLHS (talk) 06:08, 20 October 2017 (UTC)
Commenting out {{R:M&A}} frees up enough memory (~5 MB) to temporarily postpone the problem. It's odd that e failed but a doesn't. e has fewer languages (69) than a (99), transcludes fewer modules (94 vs. 150), and is shorter in terms of bytes. (And it's not at the beginning of the alphabet.) Unfortunately, there's no way to look at the memory usage of each module that is transcluded. I do think removing all the alphabet navigation templates would help. @Rua advocates getting rid of letter entries altogether, which would help even more. — Eru·tuon 09:32, 20 October 2017 (UTC)
I have managed to free up 7% of the Lua memory usage and a more than double as much significant amount of CPU usage i.e. page loading time by on one hand removing {{gloss}}, {{sense}}, {{qualifier}}, {{also}}, which has removed the most memory, and removing clutterings links of words like “and”, “his”, “but” on the other hand, which helped the CPU usage. Note that {{also}} takes 1 MB Lua memory while it is not even needed as on the translingual sections there are always the variants listed; thus I judge that the usage of {{also}} should be removed in letter pages. Palaestrator verborum (loquier) 11:02, 20 October 2017 (UTC)
I suggest removing all the "letter" entries and putting them in an appendix, leaving only the real words. —Rua (mew) 11:44, 20 October 2017 (UTC)
Would we have a clear link to this appendix from the single-letter word entries, e.g. from I? Equinox 14:36, 20 October 2017 (UTC)
Of course. Preferably, the Translingual entry would contain a list of all languages that use the letter, with Appendix links. —Rua (mew) 15:30, 20 October 2017 (UTC)

Strange code points for IPA characters?[edit]

I've noticed a number of edits over the past year or so like this one, where the diff highlights changes to strings that look identical in both the before and after versions.

In that particular edit, I noticed that the change maintained a typo I'd made earlier, where I'd accidentally entered a double-g and didn't notice. So I opened the page in the editor to fix it, and hit Ctrl+F in my browser and entered gg. Chrome found nothing.

Closer inspection revealed that the diff changed out regular ASCII g at U+0067 for the IPA Extensions ɡ at U+0261.

  • What utility is there in making this change? The IPA Extensions glyph appears to be visually identical. However, it is impossible for me to enter using my US 101 keyboard layout.
  • How many other glyphs are there in use in Wiktionary IPA contexts that are visually identical to ASCII characters?
  • What objections does anyone have to using the standard ASCII characters? These are both easier to enter, and easier to search for.

Curious, ‑‑ Eiríkr Útlendi │Tala við mig 15:48, 20 October 2017 (UTC)

Addendum: U+0067 g and U+0261 ɡ are rendered distinctly in Chome when using a monospace font, such as when wrapped in <code> tags above or in the Editor view when configured to use a monospace font. However, when simply displayed on the page in Wiktionary's default font, they look the same to me: g vs. ɡ. ‑‑ Eiríkr Útlendi │Tala við mig 15:51, 20 October 2017 (UTC)
@Eirikr: As you noticed, g and ɡ are not visually identical in all fonts. If you paste them into a word processor like Microsoft Word and view them in Times New Roman, you'll see the difference. U+0261 is a valid letter of the IPA, U+0067 isn't, so we use U+0261 in IPA transcriptions here. It's no different from using Cyrillic А and Greek Α correctly even though they're both visually identical to Latin A. As for other IPA letters that can be mistaken for regular Latin letters, depending on your font, the IPA letter ɑ may look identical to a, the IPA letters ǀ and ǃ may look identical to the punctuation marks | and !, and the IPA letters ɛ, ɸ, and ʋ make look identical to the Greek letters ε, φ, and υ. —Aɴɢʀ (talk) 16:34, 20 October 2017 (UTC)
I understand the basic point. However, IPA characters are hard to input (I can't seem to find U+0261 in the IPA and enPR quick-insert list in the Editor view), and graphically ambiguous. As noted on the WP page for the voiced velar stop /ɡ/, the regular "g" coded by U+0067 is an acceptable alternative that is visually identical in some fonts, and on some systems, U+0261 confusingly appears as something closer to ɣ (gamma).
Which brings me back to my first question: is there utility in using U+0261? I.e., is it useful? Or is this glyph technically correct, at the hazard of introducing more user confusion and processing difficulties? ‑‑ Eiríkr Útlendi │Tala við mig 19:27, 20 October 2017 (UTC)
PS: Please note that I am not arguing that U+0261 is not useful -- I am looking for reasoned input on the pros and cons, with a focus on usefulness versus risks. ‑‑ Eiríkr Útlendi │Tala við mig 19:31, 20 October 2017 (UTC)
U+0261 is in the "IPA and enPR" quick-insert list toward the end of the "Pulmonic consonants" section, after ɧ and before ɫ. The templates {{x2i}} and {{X2IPA}} make inputting easy because they let you type XSAMPA characters (all of which are simple ASCII characters) and get IPA characters output. The pros to using U+0261 in my opinion are (1) it's the correct character and (2) it's the character people will be expecting us to use. U+0067 is an acceptable alternative when it appears as an open-tail g (if you're writing a book in a font where U+0067 is open-tail, no one is going to notice, let alone, complain, if you use U+0067 to indicate a voiced velar stop), but is at best grudgingly accepted by phoneticians (less grudgingly by phonologists) when it appears as a loop-tail g. And if we were to switch over to using U+0067 consistently, I can almost guarantee you we would get complaints from know-it-all newbies and occasional editors saying that we're using the wrong character – and attempts from them to correct the character back to U+0261, but only sporadically in some entries and not others, leading to an inconsistent mess – and we would have to have this whole conversation over and over again. —Aɴɢʀ (talk) 20:01, 20 October 2017 (UTC)
There is an IPA keyboard layout that is pending for merge in xkeyboard-config, i.e. all keyboard layouts of free desktop, @Eirikr. The creator has also posted it on GithubGist so one can use it pre-release. It does also include the ASCII g though because the rest of the first level key points are ASCII-compatible, so you have to press Shift+Caps+g to explicitly write ɡ U+0261 LATIN SMALL LETTER SCRIPT G with that layout selected. If you have not switched to Linux yet, such custom layouts are surely a reason to do. I have not thought about the usage of it here yet, but for me it is a matter of course to use Linux as an editor here, and you might be interested because of the different input methods there, writing Japanese. Palaestrator verborum (loquier) 21:03, 20 October 2017 (UTC)
There's also an option to change to an IPA keyboard (SIL or X-SAMPA) right on the wiki editor (right bottom corner). There are various other keyboards you can install even if you don't use Linux. SIL's IPA Unicode Keyboards are good ones. — justin(r)leung (t...) | c=› } 21:48, 20 October 2017 (UTC)
@Eirikr: It is the same situation as the difference between and : it depends on what fonts you use and who you talk to :) —suzukaze (tc) 21:57, 20 October 2017 (UTC)
Thank you all for your input, and for your suggested workarounds.
  • @Aɴɢʀ, thank you for where to look -- I saw the version of U+0261 with the over-circle, but in scanning the list, I didn't see the other plain one further along. Any insight into how that list is ordered? I'm scratching my head about that.  :) And thanks too for the template pointers, I didn't know those even existed.
  • @Palaestrator verborum, justin(r)leung, I've used Linux in the past, and for a while I was on Mac, but due to work needs, I'm on Win 10 anymore. FWIW, I've found WinCompose (https://github.com/samhocevar/wincompose) an indispensable tool for multi-script support outside of the usual MS keyboard or IME framework. I will have to peruse the config (based on the old XOrg compose files) to see if the IPA extensions are lurking in there somewhere; if not, I'll add them to my setup.
  • @suzukaze, やはり。(^^)
  • @Anyone -- what font would be best for the default EN Wiktionary rendered display to differentiate these glyphs? Or would changing that be enough of a PITA that we shouldn't bother? ‑‑ Eiríkr Útlendi │Tala við mig 23:19, 20 October 2017 (UTC)

Template:def[edit]

I realize it's been deprecated and even nominated for deletion, but Template:def is producing random numbers at the ends of definitions (see here for an example). As long as it's still being used, it should at least work properly. Esszet (talk) 03:16, 21 October 2017 (UTC)

The number is the count of links (I don't know why it's counting the links). DTLHS (talk) 03:20, 21 October 2017 (UTC)
@Erutuon, Rua are the only people to have edited the module recently. —Μετάknowledgediscuss/deeds 03:47, 21 October 2017 (UTC)
Fixed. It was because of the string.gsub function, which returns the text as well as the number of substitutions. — Eru·tuon 03:55, 21 October 2017 (UTC)

Why can't we do one-click rollback for page moves?[edit]

See e.g. vandalism by User:Lopunny (who did it under another name recently too). Equinox 20:37, 21 October 2017 (UTC)

Not just recently: they've been doing it for a long time, all the while leaving clues so we'll know it's the same person. I think they want to be seen as the merry trickster leaving the stodgy old authority figure shaking his fist and sputtering "Curse you, Masked Bandit! Oooh, if I ever get my hands on you...".
Of course, the shows they're imitating have better writers, and the authority figures in them are cartoonish buffoons designed to set up the gags rather than unpaid volunteers who are just trying to help out.
I find the best approach is to block them, quietly clean up the mess and forget about them until their next lame attempt- it's not possible to shut them down completely, and making a big deal out of it just feeds into their mental Wile E. Coyote/Roadrunner narrative. Low-key strategies like abuse filters that slow them down and increase the hassle seem to work better- the Tar Baby vs. Brer Rabbit approach. Chuck Entz (talk) 22:36, 21 October 2017 (UTC)

Cross-references should default to current language[edit]

I'll pick an example of a problem I've seen many times in multiple languages.

The Swedish word kämpa has kamp in the "Related words" subsection. The link text is kamp rather than kamp#Swedish so it goes to the top of the kamp page. I have to scroll down to find the the Swedish word that was meant to be linked.

Is Wiktionary software smart enough to know a link is in a Derived terms or Related terms section and add the current language if it is missing? Alternatively, are there any bots smart enough to fix up all the missing languages in cross-references? (But not in definitions, because those tend to link to English words.) Vox Sciurorum (talk) 00:29, 22 October 2017 (UTC)

If you write {{l|sv|kamp}} instead of [[kamp]] then it will work. It would be nicer to default the simple-style links to the current language as you suggest, but I don't believe it is possible. Equinox 00:37, 22 October 2017 (UTC)
I think @Rua once did a bot run to fix bare links in derived / related terms sections- maybe she would do it again. DTLHS (talk) 00:39, 22 October 2017 (UTC)
I imagine JavaScript could make links in derived or related terms sections (or synonyms, antonyms) go to the language of the first level-2 header above them. But that would be done in your browser, not the Wiktionary server. — Eru·tuon 01:33, 22 October 2017 (UTC)

Bot request: removing DEFAULTSORT from Greek entries[edit]

It seems that Greek-alphabet entries at one point needed to use DEFAULTSORT to ensure that vowels with a tonos (a mark that shows which syllable is stressed) are treated the same as unmarked vowels for the purposes of alphabetical sorting. Apparently this is no longer required. Many Greek entries still have the DEFAULTSORT code included which should be removed: an ideal job for a bot.

A possible algorithm to use:

  • For each Greek-language page (it should be sufficient to trawl through all pages listed in Category:Greek language and all subcategories):
  • Check whether the page includes {{DEFAULTSORT:...}} (ignoring capitalisation). If it does:
  • Work out what the page name would be without diacritical marks. A sample substitution table of characters: (I was initially going for just the tonos, but why not cover everything, eh?)
With mark Without mark With mark Without mark
ά ἀ ἁ ἂ ἃ ἄ ἅ ἆ ἇ ὰ ά ᾀ ᾁ ᾂ ᾃ ᾄ ᾅ ᾆ ᾇ ᾰ ᾱ ᾲ ᾳ ᾴ ᾶ ᾷ α Ά Ἀ Ἁ Ἂ Ἃ Ἄ Ἅ Ἆ Ἇ ᾈ ᾉ ᾊ ᾋ ᾌ ᾍ ᾎ ᾏ Ᾰ Ᾱ Ὰ Ά ᾼ Α
έ ἐ ἑ ἒ ἓ ἔ ἕ ὲ έ ε Έ Ἐ Ἑ Ἒ Ἓ Ἔ Ἕ Ὲ Έ Ε
ή ἠ ἡ ἢ ἣ ἤ ἥ ἦ ἧ ὴ ή ᾐ ᾑ ᾒ ᾓ ᾔ ᾕ ᾖ ᾗ ῂ ῃ ῄ ῆ ῇ η Ή Ἠ Ἡ Ἢ Ἣ Ἤ Ἥ Ἦ Ἧ ᾘ ᾙ ᾚ ᾛ ᾜ ᾝ ᾞ ᾟ Ὴ Ή ῌ Η
ί ϊ ΐ ἰ ἱ ἲ ἳ ἴ ἵ ἶ ἷ ὶ ί ῐ ῑ ῒ ΐ ῖ ῗ ι Ί Ϊ Ἰ Ἱ Ἲ Ἳ Ἴ Ἵ Ἶ Ἷ Ῐ Ῑ Ὶ Ί Ι
ό ὀ ὁ ὂ ὃ ὄ ὅ ὸ ό ο Ό Ὀ Ὁ Ὂ Ὃ Ὄ Ὅ Ὸ Ό Ο
ῤ ῥ ρ Ρ
ύ ϋ ΰ ὐ ὑ ὒ ὓ ὔ ὕ ὖ ὗ ὺ ύ ῠ ῡ ῢ ΰ ῦ ῧ υ Ύ Ϋ Ὑ Ὓ Ὕ Ὗ Ῠ Ῡ Ὺ Ύ Υ
ώ ὠ ὡ ὢ ὣ ὤ ὥ ὦ ὧ ὼ ώ ᾠ ᾡ ᾢ ᾣ ᾤ ᾥ ᾦ ᾧ ῲ ῳ ῴ ῶ ῷ ω Ώ Ὠ Ὡ Ὢ Ὣ Ὤ Ὥ Ὦ Ὧ ᾨ ᾩ ᾪ ᾫ ᾬ ᾭ ᾮ ᾯ Ὼ Ώ ῼ Ω
  • If the contents of the {{DEFAULTSORT:...}} code matches the page name without marks (ignoring capitalisation):
  • Remove the {{DEFAULTSORT:...}} code entirely. If it's the only thing on that line, remove that line entirely.
  • Allow for line breaks: if there is a blank line both before and after the {{DEFAULTSORT:...}} then collapse these down into a single blank line.

I don't know, but it's possible that the same issue affects pages in other scripts. So an alternative might be to extend the mapping table above to cover lots more scripts, and to instead search for all pages containing {{DEFAULTSORT:...}}. Extending the bot for other scripts can be done as a later enhancement.

Thanks! -Stelio (talk) 20:46, 23 October 2017 (UTC)

@Stelio: It should be fine to remove the DEFAULTSORT in all cases, because sortkeys are automatically generated by the makeSortKey function in Module:languages. (If there are any errors in that function or the data that it uses, they can be fixed in the appropriate module, rather than on the page where the error occurs.) However, if there are any bare categories ([[Category:Greek autological terms]]), they will have to be converted to the corresponding category template ({{cln|el|autological terms}}), or the sortkey will be the unmodified root page name. I believe @DTLHS has a category-templatizing script. — Eru·tuon 21:40, 23 October 2017 (UTC)
I do. @Saltmarsh are you OK with this? DTLHS (talk) 21:43, 23 October 2017 (UTC)