User talk:Jonesey95

This talk page is automatically archived by MiszaBot III. Any sections older than 90 days will be automatically archived to User talk:Jonesey95/Archive2026.

GOCE script trouble (again)

Sorry to bother you, but the script is hanging up on Itcouldbepossible (57 articles) and I don't know why; I removed a stray space from D4vd, but can't find anything else. Three of their articles have since been deleted; would that be a factor? Thanks for any help. In solidarity, Miniapolis 21:40, 2 June 2026 (UTC)

I don't think the script knows or cares about deleted articles. It's been a long time since I have been able to run the script, but I recall a few tricks. I copied their list into a text editor and inspected it, and I don't see anything that catches my eye. Have you tried moving Itcouldbepossible's article list to the very end of the text input file? You could at least get output for everyone else, IIRC, and do that editor's counts using a spreadsheet or other means. Also, if you are handy a text editor, try replacing every article name with "XXX". Let me know if you would like me to calculate the table output for that editor; I am very handy with a text editor and a spreadsheet. – Jonesey95 (talk) 21:56, 2 June 2026 (UTC)

Many thanks for your prompt advice, and I was able to get everyone else's table output by moving Itcouldbepossible's article list to the end. If you could calculate that editor's output, that would be great; I'm always learning new stuff, but you're more knowledgeable than I am and we should get the barnstars out in a reasonable length of time. I wonder if the number of articles is an issue. Pinging @Dhtwiki:, who also hand-calculates this stuff. Thanks! In solidarity, Miniapolis 23:09, 2 June 2026 (UTC)

Itcouldbepossible's entry should look like this:

|-

| Itcouldbepossible (talk)

| 151,481

| 75,740.5

| 0

| 227,221.5

| 127,221.5

| 57

| 33

| 35,429

| 16

| Caretaker

Dhtwiki (talk) 00:10, 3 June 2026 (UTC)

@Miniapolis @Dhtwiki Are my edits creating a problem, sir and madam? If so, then I would like to apologize! I know my massive submission list for this drive is a huge wall of text, and I am sorry if having so many entries is breaking the barnstar script or making things difficult to process. If it helps get things working again, please feel free to just ignore the three deleted articles I copyedited from the GOCE/R page. They ended up getting deleted at AfD over notability concerns anyway, and I honestly don't mind at all if you deduct those word counts from my total to keep the script from timing out or breaking. Itcouldbepossible ^Talk 00:23, 3 June 2026 (UTC)

No worries. We have manual workarounds when our (somewhat fussy) script doesn't work for one editor's article list. Thanks for the copy edits! – Jonesey95 (talk) 00:38, 3 June 2026 (UTC)

I wanted to let everyone know, I've put together a fair few fixes for the old GOCE script and have gone ahead and generated the table for the May drive. You can find it here. I had a bit of a dig through the talk page archives and managed to track down an older version of the script. I've given it a thorough redesign and sorted out the bugs, mainly by adding robust regex handling to automatically catch those tricky edge cases that we previously had to fix manually. I haven't popped the new table onto the main barnstar page just yet, as I wanted to hold off and get the nod from the senior guild coordinators first. Please do have a look at the generated table when you have a spare moment, and let me know if anything needs tweaking. Itcouldbepossible ^Talk 01:46, 3 June 2026 (UTC)

Thanks all; I'll add Itcouldbepossible's entry to my output file with the totals and post it tomorrow. The GOCE script links to talk pages (very important when we're giving out the barnstars), and clearly distinguishes which rollover words to use and when. Itcouldbepossible, could you email your script to Dhtwiki or one of the other coords? I wonder if your entry may have had a non-printing character; Jonesey discovered one in another head-scratcher a while back, but I can't see them in Notepad. In solidarity, Miniapolis 02:38, 3 June 2026 (UTC)

@Miniapolis I am working on certain small fixes at this moment. I will email the same once I am done making the changes. Itcouldbepossible ^Talk 03:00, 3 June 2026 (UTC)

Thank you. You apparently came up with your script remarkably quickly. We don't include entries where the editors haven't done any work and thus haven't earned a barnstar; those possibly have in the past been manually edited out before the script is run. However, I question some of your numbers. For example, my 50% bonus should be 35,928 x .5 = 17,964, not 17,961; and your bonus should be (151,481 - 144) x .5 = 75,668.5, not 75,655. Dhtwiki (talk) 02:44, 3 June 2026 (UTC)

@DhtwikiThe issue came down to a rounding error that was slowly leaking half-points. The script calculates the 50% bonus line-by-line for every single article you logged. Because it was told to only output whole numbers, whenever it halved an odd-numbered word count (like your 10,561 words for Hell's Kitchen), it simply chopped off the .5 right then and there. Since you had exactly six articles with an odd number of words, the script ended up dropping exactly three points from your total. The exact same thing happened to me where I lost about thirteen points across my odd numbered entries. I have patched the script so it now matches our way of calculating things. Instead of applying the multiplier per article, it now tallies up all the bonus-eligible words into one aggregate total first, and only applies the 50% multiplier right at the very end. This completely stops any of those fractions from slipping through the cracks. Itcouldbepossible ^Talk 02:59, 3 June 2026 (UTC)

Please go through the modified version and let me know if the table should look somewhat like this. Itcouldbepossible ^Talk 03:09, 3 June 2026 (UTC)

It now looks good to me, especially with your 27 odd-word-count articles comporting with your number being off. I would put "n/a", instead of "0", where there is no applicable grand total. Otherwise, I can't think of anything more, other than marking Miniapolis's barnstars as not needing to be handed out ({{y}}). What language is your script in, and would you be willing to share it? The current script is not one that I can run on my iMac, and I have not gotten around to fashioning one of my own. Dhtwiki (talk) 04:39, 3 June 2026 (UTC)

 Done Script now uses "n/a" instead of "0". Itcouldbepossible ^Talk 04:48, 3 June 2026 (UTC)

@Dhtwiki The script has been written, or perhaps more accurately, rewritten, from an older version I happened to come across while digging through some archived talk page discussions. As it turns out, the trail led back to the very script you had in your very own userspace! The current version is written in Python 3.14, and from the little research I've done so far, it appears that iMac should support that version of Python without issue. I'd be more than happy to share the modified script, but I am yet to ascertain the means of sharing the same. Itcouldbepossible ^Talk 04:53, 3 June 2026 (UTC)

Yes, Python is what I thought I would write my script in and I do have both the old script and a non-working attempt in Python in my userspace. If you can point to where in your userspace your script resides, then I would make a copy of it that I could document and edit. It would be wonderful to have something as a backup to Miniapolis's having to run the old script or my laborious hand calculations. Dhtwiki (talk) 05:15, 3 June 2026 (UTC)

@Dhtwiki This should be working fine. User:Itcouldbepossible/GOCE-script Itcouldbepossible ^Talk 06:08, 3 June 2026 (UTC)

Excellent. Thank you so much. Dhtwiki (talk) 06:24, 3 June 2026 (UTC)

PS. My home for the GOCE scripts is here, in case anyone else is interested. Dhtwiki (talk) 06:27, 3 June 2026 (UTC)

Thanks, Dhtwiki; that page has Torchiest's original instructions (Attachment #1), which I'd lost – Jonesey's later instructions flesh them out. I copypasted your table syntax for Itcouldbepossible to the bottom of my output-file table and pasted it on the barnstar page, but the drive totals didn't generate for some reason and I copypasted your Totals line. Since I'm barely keeping my head above water with this (not a programmer), it's better for the GOCE if more than one person can do this. In solidarity, Miniapolis 13:50, 3 June 2026 (UTC)

@Miniapolis  Done I have fixed the issue. In the older versions of the script, those columns were hardcoded to print "0", which I recently updated to print "n/a". The script was never actually told to calculate the math for those specific columns. Itcouldbepossible ^Talk 15:41, 3 June 2026 (UTC)

I have updated the code accordingly. Itcouldbepossible ^Talk 15:43, 3 June 2026 (UTC)

@Miniapolis

The issue as I found out was not related to me (perhaps!).

I thought I'd share a quick rundown of why the old scoring script was causing so many headaches and how the new version sorts things out a bit. The old script basically had zero fault tolerance. The biggest flaw I noticed in it was how it searched for word counts. It would blindly grab whatever text was inside the very first set of parentheses it saw on a line. So, if someone logged an article like Hell's Kitchen (American TV series) season 12 with a word count of (10,561), the script grabbed the words "American TV series", tried to do maths on them, and immediately suffered a fatal crash. In the new script I fixed it by using regular expressions to scan the whole line and extract only the final set of brackets containing the actual numbers only. Another massive issue was with the punctuation. The old code simply couldn't cope with commas or tildes inside the numbers. If someone logged a cleanly formatted count like 35,928 or an estimate like ~20,000 (as was the case in the entries made by User:Lfstevens), the script would completely choke. Even worse, it had a hard coded technical limit, meaning if someone copyedited a massive article with more than 32,767 words, the script literally couldn't count that high and would trigger an overflow error. The new version, however, automatically purges commas before doing the maths and ignores all extra symbols. It has even happened in the past where participants often set up their sections early, leaving blank templates with empty brackets to fill in later. The old script would have either crashed trying to read these empty placeholders or would have forced a manual deletion of every single blank line before running the tool. The new code handles all of this automatically and skips over any empty placeholders without breaking the original calculations. Itcouldbepossible ^Talk 05:03, 3 June 2026 (UTC)

Thanks, Itcouldbepossible. When Torchiest wrote the script generating a barnstar table (no need for a leaderboard script), the drives were smaller but hand-calculating was becoming a problem; the other coords and I hand-edit the input file before running Torchiest's script. Can you generate a barnstar table with your script which removes the half-words and retains the header bolding? In solidarity, Miniapolis 13:50, 3 June 2026 (UTC)

@Miniapolis Can you please clarify what you mean by script which removes the half-words and retains the header bolding? Did I misinterpret Dhtwiki when they told me about decimals in the word count, or am I misinterpreting you? Itcouldbepossible ^Talk 15:34, 3 June 2026 (UTC)

You mentioned above that you had fixed the half-word issue, but User:Itcouldbepossible/May-GOCE has the decimals and no "USE/DO NOT USE THIS NUMBER FOR JULY" emphasis; the latter minimizes confusion when editors sign up for the next drive. I checked your entry in Notepad++ for stray non-printing characters; there are none, so the issue may be the size of the entry itself. In solidarity, Miniapolis 17:00, 3 June 2026 (UTC)

@Miniapolis I think I’m still misunderstanding something here. In an earlier reply, Dhtwiki explained the calculations to me, including how bonus points are handled for odd-numbered words. I also checked some of the previous barnstar pages and noticed that the Bonus Total and other columns contained decimal values there as well, which is why I assumed the current output was correct. Could you point out where I’m going wrong or what I may have misunderstood? As for the column headings, I believe they would need to be adjusted manually after the table is generated. I don’t think it’s possible to generate those headings dynamically in the current setup. One possible work-around would be to have the script detect the month in which it is run and automatically display the previous month in the heading, since the script is generally expected to be run only after a drive has concluded and the next month has begun. Let me know if you would like me to go ahead with that optimization. Itcouldbepossible ^Talk 14:01, 4 June 2026 (UTC)

(←) Dhtwiki, as lead coordinator, makes those decisions – not me. I'm a bit taken aback that you've come in from left field and kinda commandeered the drive in particular and the GOCE in general. I've seen this kind of behavior before, and it tends to be short-lived (and detrimental to the guild, which IMO benefits the encyclopedia). I've noticed that Dhtwiki and Jonesey95 (whose TP we seem to have hijacked :-) have taken a step back, and I have other things to do too. It wasn't good that running the script was entrusted to me; I found a problem with one entry, and asked for help. The script can be difficult, but I'm loath to change something that's been generally reliable transportation on the basis of one person new to the GOCE and its recordkeeping. Whatever we decide to do, more than one person has to be able to do. In solidarity, Miniapolis 20:28, 4 June 2026 (UTC)

@Miniapolis I think there's been a bit of a misunderstanding here, so I will just clear the air. I only stepped in to help out of genuine concern because, at the very beginning, it really seemed like my massive list of entries was the exact thing causing the script to crash and hold up the barnstar distribution of the drive. Since I know a bit of coding, I just wanted to fix the bottleneck. It's a completely different story that later on we found out other things were breaking it too, like Lfstevens' entry and some other older bugs in the code, but yeah, that's the only reason I wanted to step in. It was never my intention to jump in from nowhere and take up the administrative side without permission. About the sudden enthusiasm and then stepping back, well, I've actually been on this project for around 5 years or so, but I was inactive for almost two years. Since it's my summer vacation right now, I could put in a lot of wiki time and edit a ton. But again, as things reopen I might not be able to put in as much time as I am right now, so you're definitely not wrong about that! Now on the math side, just to reiterate one point, I am keeping the calculation of the decimal points intact because that's exactly as per the latest instructions given by Dhtwiki, and it also matches what I saw looking back at the old drives. In the future if it is so required that rounding off needs to be done, then I will add that on request. At the end of the day, it's totally a personal wish. If you want to use my python script, you can use it, or you can just go back to the old methods and use the original script. I just stepped in to help fix what I thought was my mess! Itcouldbepossible ^Talk 13:56, 5 June 2026 (UTC)

I just want to say that I appreciate the new script, which seems to work well and is in a language that should run under just about any operating system, give the popularity of Python, unlike Torchiest's script, which runs under Windows, not but MacOS. I might eventually master enough of the Python script's workings to make modifications, such as having it calculate blitz barnstars or the drive leaderboard itself. Of course, no script will work unless the drive page is audited for malformed entries and the like. As I never really got my mind around what Torchiest's script was doing, I can't be of much use in diagnosing its hiccups. Also, thanks for the titanic amount of copy editing that you did recently. Dhtwiki (talk) 22:45, 5 June 2026 (UTC)

Itcouldbepossible and Dhtwiki, thanks for your clarifications. I'm glad I'm no longer the only one who can generate a barnstar table with a script, although I think we're doing Torchiest a disservice (hence my GOCE backstory earlier). Jonesey, many thanks for the use of your TP :-). In solidarity, Miniapolis 23:18, 5 June 2026 (UTC)

I don't want to do disservice to the old script or our ability to rely on you to run it and the number of times that you have done so through the years. However, there's an advantage in having more than one script, in more than one scripting language, and one that is better documented than either of these scripts currently are. Ideally, that should allow more than one coordinator to efficiently calculate drive barnstars (the blitz barnstars, which I usually calculate manually, are much less complicated, but even there a script could be applied, someday). Dhtwiki (talk) 00:02, 6 June 2026 (UTC)

@Dhtwiki Thanks again Dhtwiki! Well, I personally feel that Python is just way more versatile since it can run on literally any operating system, whether you're on a Mac or Windows, so nobody gets locked out of using it. Now I have something for everyone. To make sure the script us actually useful for the team, I'll have decided to put together some detailed documentation over in my userspace soon. I'll write out exactly how to run the script step-by-step so that any of the coordinators can just pick it up and calculate the tables without having to guess how it works. Hopefully, having that ready to go takes a bit of the pressure off you and as well as Miniapolis! Itcouldbepossible ^Talk 02:19, 6 June 2026 (UTC)

(←) Dhtwiki, I never liked being relied on to run the script and couldn't agree more that several coordinators (ideally all, but ... ) should be able to run whatever script we end up using. We need a script of some kind for the drives because of the number of participants and the selective 50-percent-bonus articles. In solidarity, Miniapolis 02:06, 6 June 2026 (UTC)

@Miniapolis Just touching on your point about the selective 50-percent-bonus articles. Well, honestly you don't need to worry about that part at all anymore. The script I've managed to rebuild is actually designed to handle all of that automatically. It specifically hunts down those *O and *R markers and calculates the extra bonus points on its own, so it takes that manual headache completely out of the calculation. As I already said above, to make sure everything is easy to follow, I'll be putting up a detailed documentation under my userspace soon. Hopefully, having that guide will clear up any lingering confusion, and ensure that any coordinator can jump in and run the numbers whenever they need to! Itcouldbepossible ^Talk 02:23, 6 June 2026 (UTC)

Thanks; the lead coordinator determines which script we use. Torchiest's script does almost everything yours does; its main Achilles' heel seems to be that it didn't anticipate very large entries. In solidarity, Miniapolis 13:22, 6 June 2026 (UTC)

Just seeing this conversation. I wrote that script a long time ago as a convenience for myself originally. I was able to prep the information to work with the admittedly crude code, but then just passed it along for others to use. Didn't realize it was causing trouble. If there's a less buggy script, that's great. I'm sure I could write something better now, but it sounds like that's already been done. Cheers. —Torchiest ^talk_edits 04:53, 14 July 2026 (UTC)

@Torchiest You may find the latest script here. Itcouldbepossible ^Talk 15:18, 15 July 2026 (UTC)

May drive bling

		The Minor Barnstar
		This barnstar is awarded to Jonesey95 for copy edits totaling between 1 and 3,999 words (including bonus and rollover words) during the GOCE May 2026 Backlog Elimination Drive. Congratulations, and thank you for your contributions! In solidarity, Miniapolis 23:43, 4 June 2026 (UTC)

Template talk:Infobox book series question

Hello,

I see you're reasonably active on Infobox book series, and I had a question on it you might be able to answer. Currently in a featured list review, and one comment is that the image in the infobox needs alt-text. Unlike other templates, I don't see a field for this on that one. Is there a way to add one, or could one be added? Thanks! Already commented on the template talk page but thought I'd ping you directly. GeogSage ^{(⚔Chat?⚔)} 18:22, 6 June 2026 (UTC)

(talk page watcher) @GeogSage: I've replied at Template talk:Infobox book series#Adding alt text to images. --Redrose64 🌹 (talk) 22:45, 6 June 2026 (UTC)

Thanks Redrose64. – Jonesey95 (talk) 01:02, 7 June 2026 (UTC)

Guild of Copy Editors – June 2026 Newsletter

Guild of Copy Editors June 2026 Newsletter Hello and welcome to the June 2026 newsletter, a quarterly-ish digest of Guild activities since April. Election news: Nominations for the mid-year coordinator election ends at 23:59 on 15 June. Voting will last from 00:00 on 16 June to 23:59 on 30 June. Results will be announced on the election page. April Blitz: 18 of the 21 editors who signed up for the April 2026 Copy Editing Blitz copy edited 122,993 words in 56 articles. Barnstars awarded are here. May Drive: 34 of the 66 editors who signed up for the May 2026 Backlog Elimination Drive copy edited 543,972 words in 211 articles. Barnstars awarded are here. June Blitz: Our June 2026 Copy Editing Blitz will start on 14 June and finish on 30 June. Barnstars awarded will be posted here. Progress report: As of 22:40, 11 June 2025 (UTC), GOCE copyeditors have completed 132 requests since 1 January, and the backlog stands at 1,691 articles. Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators. To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

MediaWiki message delivery (talk) 22:57, 11 June 2026 (UTC)

Template:Infobox Jewish leader

Can you shed some light on Template:Infobox Jewish leader? This is 100% identical to {{Infobox religious biography}} the the sole exception that it automatically sets |religion=Judaism. Having a whole separate template and documentation to maintain just to avoid having to specify the religion seems unnecessary. I see that there was already a TFD last year that resulted in a merge, but then you made it a wrapper instead of actually merging... Was there some other discussion that changed the result?

For context, I'm doing a cleanup of {{Infobox religious biography}} and since Module:Template wrapper doesn't pass empty parameters up the chain, I'm not getting the necessary preview warnings for {{Infobox Jewish leader}} which is why I bring this up. Zackmann (^{Talk to me}/_{What I been doing}) 21:29, 13 June 2026 (UTC)

It seemed like the most effective way to accomplish the merge outcome. Can you provide an example of a transclusion or test case that is broken? If empty parameters need to be passed for some reason (that I can't think of), maybe the template wrapper module can be tweaked to allow that to happen.

Also, if you want to do a cleanup of {{Infobox Jewish leader}}, you can add a deprecated parameter or unknown parameter check to that template to generate error messages. – Jonesey95 (talk) 13:07, 14 June 2026 (UTC)

For example if you preview Zecharias Frankel you will see there are no preview warnings, but if you change the Infobox type to {{Infobox religious biography}} you will see the 8 invalid parameters. In the long run I guess not a big issue, but I will also note this is the only Infobox in Category:Templates calling Infobox religious biography. Just seems like if the TFD decision was "merge" it should be merged, not converted to a wrapper. However, FAR from the hill I want to die on today. Zackmann (^{Talk to me}/_{What I been doing}) 16:20, 14 June 2026 (UTC)

That page is not using any unsupported parameters, so no error message should be shown. As far as I can tell, the deprecated parameters that are present are not populated, so they shouldn't show an error message either. I guess I don't understand what you are trying to fix. – Jonesey95 (talk) 18:31, 14 June 2026 (UTC)

I agree with Zackmann here. A merge result is not a wrapper. If a wrapper was wanted, it should have been specially stated. Gonnym (talk) 16:51, 14 June 2026 (UTC)

I'm not sure what you are agreeing with, but I have no objections to anyone changing the template, as long as it does not become an independent template again. – Jonesey95 (talk) 18:31, 14 June 2026 (UTC)

This is a solution without a problem! Jonesey I just wanted to make sure I didn't miss something regarding why you chose to do a wrapper vs a straight merge. Since you have no objections I will take care of it. As I said, just wanted to make sure you didn't have an issue with doing the straight merge. I was worried there had been a discussion somewhere that I couldn't find where the decision was made to NOT merge, but to do a wrapper. That was my only question here. Zackmann (^{Talk to me}/_{What I been doing}) 18:39, 14 June 2026 (UTC)

Tech News: 2026-25

[trimmed by Jonesey95]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for technical contributors

• The roll out of global API rate limits is now complete, with limits enforced across all APIs and at the documented levels for all groups. Bots running in Toolforge/WMCS or with the bot user right on any wiki remain exempt. All bots should continue to follow the documented best practices to avoid being rate limited.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 16:46, 15 June 2026 (UTC)

Help required for infobox creation

Hi Jonesey, Could I enlist your help in creating a new infobox that I have just created? As you can see here, it's based on the Event infobox. I managed to get so far, but now I'm a little stuck, not knowing how to put it in the appropriate categories. Any assistance wouldl be much appreciated. Best,  Ohc ^{revolution of our times} 17:29, 17 June 2026 (UTC)

It looks like you did a good job so far. I created the tracking categories and tidied up some misguided parameter names that were probably copied over from an infobox that made bad choices that we have had to live with ("blank" instead of "custom", and numbering that only programmers use). I am confused by the non-standard parameter name |institution:retail%_=, which should probably be fixed before going live. That parameter description in the documentation says something about percentages, but no percent sign is displayed. Using a colon, a % symbol, and an underscore in a parameter name is non-standard and inadvisable. I might call it something like |institution_retail_ratio= and then give two or three examples in the documentation. – Jonesey95 (talk) 02:52, 18 June 2026 (UTC)

Many thanks for all your work on this. Indeed, you correctly guessed what I had intended the |institution:retail%= to show. I will add notes in the doc accordingly.  Ohc ^{revolution of our times} 11:29, 18 June 2026 (UTC)

Infobox settlement

Should I continue to ping you on the discussion on TM:Infobox settlement? I really value your input, but don't want to continue to bug ya if you are over this discussion. :-\ --Zackmann (^{Talk to me}/_{What I been doing}) 05:03, 18 June 2026 (UTC)

I don't have the energy for complex discussions every day, given IRL stuff. I contribute when I can. – Jonesey95 (talk) 14:10, 18 June 2026 (UTC)

Totally understand! Really value your input so chime in when you can. Zackmann (^{Talk to me}/_{What I been doing}) 16:20, 18 June 2026 (UTC)

AI

Do not remove AI tags, namely Special:Diff/1340129038, without fixing the issue.

Typos in an edit summary are also not a reason to remove legitimate edits. God forbid someone makes a typo; fortunately typos are not against guidelines, whereas AI-generated edits are. Gnomingstuff (talk) 13:03, 18 June 2026 (UTC)

Help required

We have the template here:

Template:list:Latin script letters/kix

And this-

Appendix:Latin script letters/kix

Please delete the ones that is not needed. Thanks ExfactoLexander (talk) 16:43, 21 June 2026 (UTC)

There is no page at Template:list:Latin script letters/kix or at Appendix:Latin script letters/kix. Please use square brackets and copy-paste to link to pages, as shown in this reply. – Jonesey95 (talk) 16:52, 21 June 2026 (UTC)

wikt:Template:list:Latin script letters/kix? Don't know about the other.

—Trappist the monk (talk) 16:56, 21 June 2026 (UTC)

Please check these three

wikt:Template:list:Latin script letters/kix

wikt:Template:Kix-alphabet

wikt:Appendix:Latin script letters/kix

ExfactoLexander (talk) 17:09, 21 June 2026 (UTC)

The middle one does not exist, and the third one does not have any similar pages. I don't know what you're trying to do, and I have very little experience with Wiktionary. If you need help on Wiktionary, it looks like wikt:Wiktionary:Information desk might be a good place to ask for it. – Jonesey95 (talk) 17:11, 21 June 2026 (UTC)

Sorry. The middle one is Wikipedia Template I created, not knowing the purpose. ExfactoLexander (talk) 17:16, 21 June 2026 (UTC)

OK. I have moved it to User:ExfactoLexander/Kix-alphabet in case you want to reference its content in the future. – Jonesey95 (talk) 17:18, 21 June 2026 (UTC)

June blitz bling

		The Minor Barnstar
		This barnstar is awarded to Jonesey95 for copy edits totaling between 1 and 1,999 words (including rollover words) during the GOCE June 2026 Copy Editing Blitz. Congratulations, and thank you for your contributions! In solidarity, Miniapolis 17:10, 22 June 2026 (UTC)

Tech News: 2026-26

[trimmed by Jonesey95]

• Sub-referencing is a new MediaWiki feature that allows editors to reuse references with different details. It will be deployed to most small and medium-sized Wikipedia language versions on June 23. The FAQ lists possible actions to take on your wiki to support the deployment. Check the rollout plan for the next deployment steps.

MediaWiki message delivery 13:03, 23 June 2026 (UTC)

Engvar redirects

Hi @Jonesey95, I'm not entirely sure what, if anything, should be done about this. But a user has recreated several templates which were deleted by TfD and made them into redirects to flexible templates, including ones with bizarre names like Template:En-029. They have been categorised so that they appear in the lists of Engvar templates e.g. Use Carribbean English is once again listed at Template:Use American English#See also. I just wanted to put it on radar because it's clearly an attempt to resurrect what has already been deleted by recent consensus. Dgp4004 (talk) 16:12, 23 June 2026 (UTC)

Feel free to take a look at Wikipedia:Redirects for discussion. I participate in WP:TFD, but not very often at RFD. I have removed the redirects from the Use X English template, since it implies that they are templates, but those templates were deleted because those variants of English could not be shown to have rules for written prose. – Jonesey95 (talk) 03:48, 24 June 2026 (UTC)

Dgp4004: Also see Template talk:Use English variant, discussion in progress. – Jonesey95 (talk) 21:57, 24 June 2026 (UTC)

Thank you. I have nominated them at Wikipedia:Redirects for discussion/Log/2026 June 26. I was also minded to nominate the below, but I am unsure how to nominate multiple redirects in the same discussion without spamming the page:

• {{Belizean English}}
• {{Belize English}}
• {{Use BzE}}
• {{BzE}}
• {{BZE}}
• {{Use Belizean}}
• {{BLZ English}}
• {{BZE English}}
• {{BZ English}}
• {{En-029}}
• {{En-BZ}}

and

• {{Caribbean English}}
• {{Use CarE}}
• {{CarE}}
• {{CSE}}
• {{Standard Caribbean English}}
• {{Caribbean Standard English}}
• {{Use Caribbean}}

Dgp4004 (talk) 12:18, 26 June 2026 (UTC)

I use Twinkle, which automatically notifies the creator and creates a new section on the RFD page. After that new section is created, I merge it like this. If you are not using Twinkle, just notify the creator that you are nominating the list above, copy and paste the RFD notice from Template:Use Belizean English to the other pages, and then use the instructions for multiple nominations on the RFD page, under "Repeat line 2 for N number of redirects". They are a little technical, but you can probably get it. Let me know if you need help. – Jonesey95 (talk) 12:51, 26 June 2026 (UTC)

Invoke statements and stripped lists

Hello,

Would you happen to know why the include/noincludes in the invoke clause (on line 2) are creating a stripped </li> error on these 9 Wikiproject pages? I briefly considered if it were the lack of a vertical bar between the limit=3 and the (second) list parameter, but that doesn't clear the error or breaks the preview (depending on where between them you place it). I also wondered if the second list was an issue of duplicate parameters, but not seeing removal of that second list as a solution. I'm tempted to outright remove the include/noincludes since that appears to display the same way and clears the error, but since I don't quite know what function the invoke is even serving here, I figured I should ask for a second opinion before doing that.

And on a similar note, do you know why or how to fix the abbr error with the mouse excerpt at Wikipedia:WikiProject_Portals/Newsletter_archive#Portals_WikiProject_update_#009,_15_June_2018? The mouse slide is decomposing the {{pl}} template causing a stripped abbr error on 64 pages. The inner "Transclude lead excerpt" template behaves, but the invoke statement of {{#invoke:String|replace|{{Transclude lead excerpt|paragraphs=1-3|files=1-2|more=|Mouse}}|%c|<br>||false}} changes that.

And while I'm here, do you see anything out of place with the SMILES section (under |data13=) on User:CFCF/Drug simple that would be causing the four errors on User:CFCF/Drug test of a missing/stripped/misnested ul/li/div combo? I know for certain that it's the SMILES parameter as the error goes away if the |SMILES= parameter is completely removed (not emptied, but removed outright), and the error remains if SMILES is the only parameter in the entire infobox on Drug test page.

Thanks for any insight, Zinnober9 (talk) 02:17, 27 June 2026 (UTC)

Those stripped /li tags are strange. They seem to pop up sometimes and not other times. This change seems to do the trick and probably doesn't break anything. It shows up to 300 articles on the page itself, but keeps the limit of 3 when the page is transcluded. There are similar pages here. – Jonesey95 (talk) 05:01, 27 June 2026 (UTC)

I fixed the mouse slide by adding Template:plural abbr to the list of templates excluded from these sorts of excerpts. That was an obscure one. – Jonesey95 (talk) 05:13, 27 June 2026 (UTC)

As for CFCF, the syntax highlighter gadget helped me identify a /div tag that was outside of an #if statement value when it should have been inside. The closing braces should have been highlighted yellow, but they were pink, which gave me a clue where something was wrong. – Jonesey95 (talk) 05:17, 27 June 2026 (UTC)

Great, thank you so much! I was clearing li errors by namespace, and hadn't looked at user space yet for the first issue. Planning on clearing the remainder of li over the next few days. I wasn't going to think of that one for the mouse. Nice solution. CFCF, bah. I looked at it, figured it was exactly that sort of misnested situation and still didn't spot it. I'm going to blame all the memorizing brackets for missing that one... Haven't found the gadget to play nicely with the syntax toggle on the editor, so have left the gadget off for now. Will give it another go though. Zinnober9 (talk) 13:26, 27 June 2026 (UTC)

Speedy deletion nomination of Category:Articles containing Kutenai-language text

A tag has been placed on Category:Articles containing Kutenai-language text indicating that it is currently empty, and is not a disambiguation category, a category redirect, under discussion at Categories for discussion, or a project category that by its nature may become empty on occasion. If it remains empty for seven days or more, it may be deleted under section C1 of the criteria for speedy deletion.

If you think this page should not be deleted for this reason you may contest the nomination by visiting the page and removing the speedy deletion tag. Liz ^{Read! Talk!} 17:18, 29 June 2026 (UTC)

Hmm, I wonder why the new category was created instead of just moving the existing category. – Jonesey95 (talk) 21:06, 29 June 2026 (UTC)

Template:Auto archiving notice/Archive CSD

Hi! You tagged this page and Template:Auto archiving notice/Archive Index for deletion as unused. Given that the pages warn you not to delete them for technical reasons, could you point me at what's changed recently so that theses pages are no longer needed? Rusalkii (talk) 00:13, 4 July 2026 (UTC)

Template:Auto archiving notice/doc was merged to Template:Talk header/doc, so the notice on the page no longer applies. The page has no incoming links. – Jonesey95 (talk) 02:27, 4 July 2026 (UTC)

Got it, deleted. Rusalkii (talk) 02:40, 4 July 2026 (UTC)

Speedy deletion nomination of Category:Hatnotes with links to nonexistent pages

A tag has been placed on Category:Hatnotes with links to nonexistent pages indicating that it is currently empty, and is not a disambiguation category, a category redirect, under discussion at Categories for discussion, or a project category that by its nature may become empty on occasion. If it remains empty for seven days or more, it may be deleted under section C1 of the criteria for speedy deletion.

If you think this page should not be deleted for this reason you may contest the nomination by visiting the page and removing the speedy deletion tag. Liz ^{Read! Talk!} 02:23, 6 July 2026 (UTC)

Chimpanzee cites

Hello. Would you be able to cleanup the cites for chimpanzee. See also Noleander's comments at the peer review. LittleJerry (talk) 15:37, 8 July 2026 (UTC)

 Done. – Jonesey95 (talk) 19:28, 8 July 2026 (UTC)

Lint errors

Hello Jonesey!

You've helped me a lot in the past to fix linter errors in my homewiki and the last time we talked we had only 1 category of errors to clean up. Recently, with all AI developments, I was able to build a supervised automatized pipeline and unleash Claude AI on that remaining category, thus greatly accelerating the clean up process. I'm happy to write down that finally, for the first time since creation, we have 0 errors!

Well, not really, since Duplicate IDs and Background color inline style rule exists without a corresponding text color errors still remain, quite a lot actually. Now obviously this begs the question: What is expected to be done with those kinds of errors? Am I to understand that they will be fixed further upstream and those no action at all is required by me for any of the cases? Is that assumption completely wrong? Something in-between? I've read a lot around about them, even asking different AIs, but they give no definitive answers about what to expect and how to handle them. - Klein Muçi (talk) 09:47, 10 July 2026 (UTC)

Congratulations!

At en.WP, most of the duplicate ID errors are caused by our citation templates, and there is no movement to fix them. I have not seen any movement to fix these errors at all on this Wikipedia.

The background color errors sometimes indicate a problem with how a page will look in dark mode. I recommend starting with templates. Find a page that uses the template, and switch to Vector 2022's dark mode to see if the template displays poorly. If so, figure out how to add a "color:" declaration where needed so that both light mode and dark mode work properly. I am not an expert at choosing these color options, but I have a set of notes for my use that I will copy below. One of these options usually works, but I don't always know which one it will be until I try them. There are definitely more sophisticated ways to fix the problems.

Colors in Wikipedia:
- default background color: #F8F9FA
- default background color in dark mode: #202122

Dark mode color fix: (this often makes explicitly chosen bg colors go away, so it's not great)
background-color: var(--background-color-base,#CEE0F2); 

Default color: 
color:var(--color-base,#202122);

To force black:
color:var(--color-base-fixed,#202122);

To force white:
color:var(--color-inverted-fixed,#ffffff);

I hope that helps. – Jonesey95 (talk) 13:59, 10 July 2026 (UTC)

Thank you!

So they are fixable on a wiki level, right? My main question is: Can I fix them as a wiki user if I so want or are they actually expected to be fixed on the actual Mediawiki software (like maybe Parsoid or even further upstream) with different PHP patches and I can't/shouldn't do much on the wiki level? This is the question that I don't see anywhere answered plainly. From your reply I kinda get that they are actually actionable from the normal/wiki admin user perspective. - Klein Muçi (talk) 16:30, 10 July 2026 (UTC)

The background colors are all fixable on your wiki. Some example edits: , , , , , , , , . – Jonesey95 (talk) 00:13, 11 July 2026 (UTC)

Thank you for the insight! That was all I needed. I've already started fixing them. - Klein Muçi (talk) 22:10, 14 July 2026 (UTC)

Gallery tags

Hi Jonesey95, I saw that you were the one who added the note about gallery tags not working with perrow= on the mw page for obsolete HTML tags. Coincidentally I ran into this with my bot on a different wiki, and so was wondering if there was a phab task for this that you'd filed, since I couldn't find one. — Tenshi! (Talk page) 18:54, 11 July 2026 (UTC)

I do not see a phabricator task, open or closed. I thought that it was documented at Mediawiki, but I don't see it now. Feel free to file a phab task. – Jonesey95 (talk) 19:03, 11 July 2026 (UTC)

July 2026 meetup in Portland (Online participation available!)

Northwest Library

Hey Jonesey95,

You're invited to the July 2026 meetup in Portland, Oregon! Join us either online or at the Northwest Library at 2:00 PM on Saturday, July 25.

Please RSVP at the link above, even if you might be interested, so we can know how many people to expect, and add your agenda items. Hope to see you there!

(To unsubscribe from these updates, remove yourself from this list. Sent via MediaWiki message delivery.) —TechnoSquirrel69 (talk) 22:00, 11 July 2026 (UTC)

AIC article row

How could the notes portion of Template:AIC article row be adjusted to allow block entries (containing linebreaks/linefeeds) without breaking the italics? I ask as the usage of this template on Wikipedia:AI noticeboard/2026-07-10 TheRealBasti has linebreaks in two of the row templates causing the page to be reporting lint, and it seems more realistic to address it at the template than have this reoccur elsewhere. Thanks, Zinnober9 (talk) 11:41, 14 July 2026 (UTC)

Fixed. I thought you were going to come to me with a difficult one! I replaced the inline i tags with block div tags, because the entire contents of the cell are wrapped, and we don't have to worry about span tags being put around the div tags. – Jonesey95 (talk) 13:10, 14 July 2026 (UTC)

Ah, of course. I keep forgetting we can italicize from div/span. Too used to them being separate. Thank you!

If you are really disappointed it wasn't a challenging question, I could come to you for the 36 stripped Wiki talk tags if you want... Zinnober9 (talk) 13:34, 14 July 2026 (UTC)

Well played. Yeah, I've looked at that page before. The phantom start tab / end tab ones are pesky. I haven't been able to tell if they are false positives or something that I just haven't figured out yet. I have fixed a few that are not those. – Jonesey95 (talk) 13:46, 14 July 2026 (UTC)

You got me motivated to figure out the talk header stripped double div tag issue. It turns out that {{start tab}} automatically inserts unclosed div tags, but not on any talk-space pages, which is very confusing. Fixes like these seem to do the trick. – Jonesey95 (talk) 14:17, 14 July 2026 (UTC)

Ah, that would explain why a verbatum copy of one of those pages to my sandbox is clean, and null editing the WT pages were still dirty. It was acting like there was a namespace conditional, but wasn't sure what and where to look for that. Very nice! Zinnober9 (talk) 14:26, 14 July 2026 (UTC)

EMPTY! Thanks for motivating me to figure this one out. I updated the {{start tab}} template documentation, which was confusing a lot of people, including me. – Jonesey95 (talk) 14:33, 14 July 2026 (UTC)

Got another curious few. Why does Wikipedia talk:Wikipedia Signpost/Omni-index have every row stating 1. instead of functioning correctly? I know that # breaks when there's extra lines between rows, but there's no obvious breaks on this page, and nothing obvious on the row template, unless transclusion breaks that for some reason. I've reported the table not being closed to the bot's talk page.

Also curious about the pre tag issue from Bawolff's pages since I cleared off all but 7 on non-COI pages, all on pages Bawolff isn't transcluding. Briefly considered if it were a nested situation (since pre tags can't nest), but that does a stripped error not an unclosed error. Haven't seen any issues on the COI pages they are coming from, but was a brief look. Zinnober9 (talk) 00:33, 15 July 2026 (UTC)

You were right to suspect whitespace in the Omni report.

As for the Bawolff pages, my first guess, without looking too much, is a bug in Module:Sandbox/Bawolff/COIEdit that fails to process Talk:Jacques Louis Vidal on the page User:Bawolff/Edit COI Summary/14 as intended. User:Bawolff may be able to look at their code and figure something out. My naive guess is that the "nextOffset, nextOffsetHeader" code that looks for headers is getting confused when there are headers inside of <pre>...</pre> tags, something that happens quite a bit when people are proposing edits to large chunks of a page. Maybe the code could skip everything inside of pre tags. – Jonesey95 (talk) 01:18, 15 July 2026 (UTC)

Ah, the classic "I know what it is, I'm looking at it, and still not seeing it". *d'oh*. Thanks.

The larger pages are known to hit post expand sizes, and seemed to be the first pages to start appearing when I was nearing the end of my pre tag elimination last month, but the smaller pages didn't make sense with that, so had brushed it aside until now. I agree, The pages I've looked at do appear to all break at the pre sections that contain a header within. Will inquire. Zinnober9 (talk) 14:43, 15 July 2026 (UTC)

Tech News: 2026-30

[trimmed by Jonesey95]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• Suggestion Mode offers edit suggestions within the VisualEditor for improving Wikipedia articles. All suggestions are community-configurable. The TextMatch feature is a way for volunteers to create custom local suggestions. The feature searches in articles for strings of text, and now includes support for regular expressions. This gives volunteers greater precision and flexibility over the kinds of local suggestions they can create. Note: Suggestions can be targeted based on the edit count of the person editing as well as other aspects of the page. You can find examples from other communities for inspiration, including TextMatches that detect: typos, grammar-errors, potential advertisements, clichés, incorrect dash or hyphen usage, non-specific time keywords, outdated names, and more. Any feedback is appreciated.

MediaWiki message delivery 05:44, 21 July 2026 (UTC)

Disambiguation link notification for July 26

An automated process has detected that when you recently edited Swimming at the 2008 Summer Olympics, a link pointing to the disambiguation page Christian Sprenger was added.

(Opt-out instructions.) --DPL bot (talk) 05:59, 26 July 2026 (UTC)

Tech News: 2026-31

[trimmed by Jonesey95]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• DiscussionTools' source mode and the 2017 wikitext editor will now offer autocomplete for links ([[), templates ({{), HTML and parser tags (<), and magic words (__), making it quicker and easier to insert links, templates, and other wiki markup while editing.
• From now on, wikis can restrict editing in the "User" namespace to only the page owner and certain user groups. Read the configuration documentation to learn more.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 18:47, 27 July 2026 (UTC)

Rename all userbox categories

You are invited to join the discussion at Wikipedia:Village pump (idea lab) § Rename all userbox categories. —⁠andrybak (talk) 00:05, 28 July 2026 (UTC)

The CfD nomination is ready at Wikipedia:Categories for discussion/Log/2026 August 12#All categories for userboxes. Please join the discussion there. —⁠andrybak (talk) 22:13, 12 August 2026 (UTC)

Thank you

Thanks for cleaning up so many of my messes today! Re this, in my defense that has been broken since November 9th.... However my defense false apart because I was the dumba$$ who broke it back on November 9th. Le sigh... Constantly learning and improving. Adding another check to my list. Thanks again. Zackmann (^{Talk to me}/_{What I been doing}) 23:14, 28 July 2026 (UTC)

Fun edge cases today! You didn't make any boring errors. Thanks for keeping my day interesting. Also, this discussion might interest you. – Jonesey95 (talk) 23:16, 28 July 2026 (UTC)

And re the November 9 error, I found it in Category:Pages with broken maps. Yet another page you might want to monitor for garbage leaking out of automated edits. – Jonesey95 (talk) 23:18, 28 July 2026 (UTC)

Glad I could give you something fun! Also saw this post. Hoping we can get Category:Articles with broken maps created so that I can monitor that and no have to filter through all the User pages and Drafts. But will add it to the list. Appreciate your help as always. Zackmann (^{Talk to me}/_{What I been doing}) 23:27, 28 July 2026 (UTC)

Query

Hello, Jonesey95,

I just ran into Category:Pages using Module:Routemap with conflicting parameters on the Empty Categories list and first, I have no idea what it is for (which is okay) but I also think if it is going to be empty a lot, you might put an empty categories template (it's often goes by "possiblyempty") or you could get an annoying CSD C1 notice. Thanks for your knowledge and taking care of behind-the-scenes business. Liz ^{Read! Talk!} 03:07, 29 July 2026 (UTC)

I always forget the magic combination of parameters to get a hidden possibly empty category. I think that I have fixed it. Thanks for the kind note. – Jonesey95 (talk) 05:01, 29 July 2026 (UTC)

Conditionals table closers removed

Got any idea why the bot removed the table closers here and here? I've removed the if statements from the tables outright on each so it doesn't repeat, but since they weren't one offs, I'm wondering why these were even set up this way. Seems unnecessary from the start. Zinnober9 (talk) 07:35, 30 July 2026 (UTC)

Those both happened in January 2024. You could ask the bot operator whether this issue has been fixed. The presence of the #if code looks like incomplete substitution of a template (or a copy and paste of Wikipedia:Content assessment/B-Class criteria), but I don't know why the bot would remove some but not all of the table markup. If it has happened recently, that would be more interesting.

Some pages, including Talk:Fitness to dive, were left alone. You could check the rest. – Jonesey95 (talk) 13:02, 30 July 2026 (UTC)

I've looked at about 40 the pages you linked (the first 20 and then all that have been last edited in 2026), and found no cases of it reoccurring. Cewbot behaved correctly in March of this year with the same setup, and there doesn't appear to be any section around that time on the operator's talk page discussing anything like this issue, so not looking like a repeating issue beyond these two with what I know currently. Will run it by the operator just to be sure it isn't an open issue. Thank you! Zinnober9 (talk) 16:33, 30 July 2026 (UTC)

Known and resolved shortly after it occurred, not an open issue (thankfully). Have a great weekend, Zinnober9 (talk) 12:30, 31 July 2026 (UTC)

Linter errors and Module use

Hi Jonesey95. Thank you for your edits to the Alfred Robert Grindlay infobox. I wanted to ask you a couple of questions on it if I may. Your updates now mean the 'Further government positions' and 'Further civic positions' sections now both appear to run into each other and sit below the family module. I had those two section sit at the top before the personal details, because they are additional formal offices, positions, etc. that were held therefore grouped them at the top as with other political info box, e.g. Clement Attlee (which is the structure I used). I want to set the box up correctly, but tit doesn't seem to make sense to have these elements moved to the bottom; would you agree? Secondly, how can the two boxes be stopped from running into each other after your edits? Any help on this would be much appreciated. Thank you.WidoWido (talk) 10:37, 3 August 2026 (UTC)

See the documentation for {{infobox officeholder}}. You can use |term_start4=, |term_start5=, etc. to list multiple positions. – Jonesey95 (talk) 11:38, 3 August 2026 (UTC)

Undo

Can you please Stop to delete my new things. it is for the future Summer Olympics 2028. Vincent (talk) 17:27, 3 August 2026 (UTC)

Please stop making useless templates. There is a lot of advice for you on your talk page. – Jonesey95 (talk) 21:54, 5 August 2026 (UTC)

July 2026 GOCE drive award

		The Modest Barnstar
		This barnstar is awarded to Jonesey95 for copy edits totaling over 4,000 words (including bonus and rollover words) during the GOCE July 2026 Backlog Elimination Drive. Congratulations, and thank you for your contributions! Dhtwiki (talk) 05:23, 4 August 2026 (UTC)

Redirect listed at Redirects for discussion

Redirects you have created have been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 August 11 § Template:AccountUser0/Badges until a consensus is reached. 1234qwer1234qwer4 06:15, 11 August 2026 (UTC)

<3

	The Hard Worker's Barnstar
	For tireless vigilance re English variety templates/redirects/etc and eeendless patience in engaging w/ diametrically opposed povs even when those editors fail to get the point, fs see and value the work even when it doesn't seem like it! (sorry for late barnstar, just learnt of these :) - Asdfjrjjj (talk) 01:07, 15 August 2026 (UTC)

(Ps also awarded to Dgp4004 but ifl that's ok b/c you've both been especially hard working and patient imo :) - Asdfjrjjj (talk) 01:16, 15 August 2026 (UTC)

2026 Wiknic in Portland, Oregon

Marquam Shelter

Hey Jonesey95,

You're invited to the 2026 Wiknic in Portland! Join us for a social potluck at 4:00 PM on Saturday, September 5.

Please RSVP at the link above, even if you might be interested, so we can know how many people to expect, or even add something to the menu. Hope to see you there!

(To unsubscribe from these updates, remove yourself from this list. Sent via MediaWiki message delivery.) —TechnoSquirrel69 (talk) 04:43, 15 August 2026 (UTC)

Tech News: 2026-34

[trimmed by Jonesey95]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• Special:ShortPages displays short pages by their size, but in many cases it gets filled with disambiguations and soft redirects, making it harder to find the short articles themselves. Starting this weekend, you will be able to choose not to include an article in the special page by adding the magic word __EXPECTSHORTPAGE__.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 21:01, 17 August 2026 (UTC)

Help at template Cite Q

Hi, I've been talking to Pigsonthewing about contributing to the Cite Q template/module, and I have a series of improvements I'd like to make starting with adding support for using Cite thesis, but there's a change in sandbox that needs to be deployed. I'm hoping to get it sorted and move on with some more testing, but don't want to clog up the sandbox with more changes. I'm using an offline git repository to mirror changes to the template and its sandbox, so I can keep it straight. I'd also like to get template edit rights at some point, which would make this a lot less tedious. Is there anything I can help with to move it onwards? — Jonathanischoice (talk) 11:41, 19 August 2026 (UTC)

I stay away from Cite Q unless it is causing problems. It looks like other editors have been able to help advance some changes. – Jonesey95 (talk) 21:56, 31 August 2026 (UTC)

Set index on epithet lists

I don't think that's an appropriate categorization. I think of epithets as similar in this respect to surnames or nicknames. I cite the most significant such list: List of people known as the Great. Clarityfiend (talk) 01:08, 21 August 2026 (UTC)

You're going to have to be more specific. I made 279 edits yesterday. – Jonesey95 (talk) 15:22, 21 August 2026 (UTC)

Gboldmap curiosity

Got any idea why this edit moving the | from the end of lines to the typical beginning of lines placement is now reporting bolding errors? It shouldn't make a difference, and my test has no display difference, but errors on the leading and clean on the trailing. I don't see something that calls to me within the Template:GBoldmap that would be causing this, and other templates don't seem to care if it's a leading or trailing. Thanks, Zinnober9 (talk) 01:02, 24 August 2026 (UTC)

Putting the template transclusion into Special:ExpandTemplates shows you the problem here. This edit is the fix, trimming whitespace before and after the parameter value, including newline characters. – Jonesey95 (talk) 02:01, 24 August 2026 (UTC)

That's one tool in the toolbox I just haven't gotten in the hang of using yet since deactivating the outer object of a nested set often reveals the culprit, or reviewing the last few edits leaves a telling breadcrumb trail. Neither was an option this time. Will make an effort to use it more often since it seems pretty powerful. I still wouldn't have gotten there on this one without you since I haven't used the trim template before and while I've seen the template, hadn't stop to think what it did/prevented. Very surprised GBoldmap lasted this long without it. Thanks again! Zinnober9 (talk) 22:49, 24 August 2026 (UTC)

Leave it to Zackmann08 to make an edit that is both not needed and finds a weird edge case. That's talent! /s – Jonesey95 (talk) 23:06, 24 August 2026 (UTC)

Wait, what did I do?! So confused. Zackmann (^{Talk to me}/_{What I been doing}) 03:10, 25 August 2026 (UTC)

You moved some pipes for no apparent reason, and it caused an edge-case Linter error. I got to solve a problem, which makes me happy. Fun times. – Jonesey95 (talk) 04:54, 25 August 2026 (UTC)

Hey I am more than happy to help you find these edge cases... Sorry it caused a headache but glad it helped solve this? Zackmann (^{Talk to me}/_{What I been doing}) 04:59, 25 August 2026 (UTC)

(talk page watcher) @Zinnober9: Generally speaking, leading and trailing whitespace (spaces, tabs, newlines) is significant for unnamed (positional) parameters, and only insignificant for named parameters and explicitly numbered parameters. Templates need to be specially coded to ignore leading and trailing whitespace for all params. If you had preceded the sixth parameter value with its number, thus:

{{GBoldmap|53.8499|-2.9974|SD|3448|3976| 6=Poulton Curve Halt
| NPE Maps=(1947)
| Vision of Britain=y
| Old OS Maps=(estimated 1925 to 1945)
| coord_type=railwaystation}}

it would have worked without needing to modify the code inside Template:GBoldmap. --Redrose64 🌹 (talk) 07:03, 24 August 2026 (UTC)

Ugh, that is such inconsistent behavior. The more I see of unnamed parameters, the more I dislike them. – Jonesey95 (talk) 13:17, 24 August 2026 (UTC)

Positionals seem fine in cases where the data is going to be uniform in input and/or has three or fewer parameters, but something like this where the two styles start to mix or need to be flexible and things start to become particular and unnecessary complainy, not a fan.

Certainly an interesting work around with the |6= though, would not have thought of that in this situation. Zinnober9 (talk) 22:52, 24 August 2026 (UTC)

Would a similar situation be occurring on Template:Script/Arabic? Since the addition of bdi tags to enwiki, I've disliked them for a perceived incompatibility issue with blocks of text (reporting missing and stripped bdi tag issues and disregarding block div format; ie behaving like a span in a div situation). but starting to wonder if it's not specifically the bdi tags, but how the templates have used them. I testing if this was a trim issue, I'm more confused. Added trim to Template:Script/Arabic/sandbox and compared the live template with the sandbox in my sandbox. They display the same (and both disregard break tags), and while trim did clear one case of an error, it was clean elsewhere in the same scenario without trim. Is this a bdi issue, or is this a trim/cleanup issue? Zinnober9 (talk) 19:43, 26 August 2026 (UTC)

It looks like {{trim}} works in that situation. bdi tags can't wrap block content, though, so the content containing multiple lines inside bid tags is invalid HTML, hence the Linter error. You might ask on the Linter help page what other editors have done to work around that issue. One fix would be to use br tags to put all of the text on a single line but render it as multiple lines. – Jonesey95 (talk) 19:53, 26 August 2026 (UTC)

Will do. br tags is what I've done in the past when there was an initial crop from pages that were archives or other unlikely to change pages. But I really don't like the idea of an inline tag being used for a template that will likely be used in blocks of text situations. Feels like leaving a door open. Zinnober9 (talk) 20:33, 26 August 2026 (UTC)

August 2026 GOCE blitz award

		The Modest Barnstar
		This barnstar is awarded to Jonesey95 for copy edits totaling over 2,000 words (including rollover words) during the GOCE August 2026 Copy Editing Blitz. Congratulations, and thank you for your contributions! Dhtwiki (talk) 05:39, 24 August 2026 (UTC)

Speedy deletion contested: Wintergreen (band)

Hello Jonesey95. I am just letting you know that I contested the speedy deletion of Wintergreen (band), a page you tagged for speedy deletion, because of the following concern: Article previously had a PROD denied. Thank you. BangJan1999 20:43, 24 August 2026 (UTC)

Tech News: 2026-35

[trimmed by Jonesey95]

• User Info card is a feature that helps patrollers see information about user accounts. So far, it has been available only in places such as page history, logs and recent changes. Now, it's possible to place it in the page content as well, using the {{#uic:}} parser function. It can be particularly useful in templates like {{Userlinks}} (or their specialized variants), as it will make it easier to see the context about a user on various noticeboard pages. The card will be displayed only to users who have it enabled in their preferences.

MediaWiki message delivery 20:43, 24 August 2026 (UTC)

Thank you

For your efforts, in the article space, to strongly encourage all editors, including the seasoned of many years, to leave meaningful edit summaries. I cannot say how many battles have been enjoined by misunderstandings, either from an incoming editor failing to read the edit summary of another, or for the earlier editor failing to explain clearly the what and why of their work. Bravo/brava, cheers. [A retired editor of many years, who still looks in, in the oddest places.] ~2026-44957-28 (talk) 04:58, 25 August 2026 (UTC)

Thanks. I don't know why this policy is not enforced. – Jonesey95 (talk) 05:18, 25 August 2026 (UTC)

Template:Ben Roberts-Smith sidebar

Hi Jonesey, Thanks for letting me know that all templates are required to have categories and documentation per guidelines. I've now added some categories.
I was wondering if you could point me in the direction of the relevent guideline/s that I should follow when drafting any documentation as well as any how-tos and any useful tools. While I may have the template editor perm this is the first template I've created myself. Almost all of my template editing has been for DYK.
Regards, TarnishedPath^talk 23:58, 27 August 2026 (UTC)

See the guideline at Wikipedia:Template namespace. Notably, Templates should be clearly documented as to their usage and scope. Also see Wikipedia:Categorization, which says Every Wikipedia page should belong to at least one category. – Jonesey95 (talk) 04:51, 28 August 2026 (UTC)

Cheers. TarnishedPath^talk 04:57, 28 August 2026 (UTC)

Template:Current Irish Air Corps Aircraft

I have reverted your blanket wiping of this template. This template was created because the author of Template:Active Irish Air Corps Aircraft refuses to allow ordered aircraft to be listed on it, which if you read the history and talk page of their template you will understand. Finestat (talk) 07:06, 31 August 2026 (UTC)

Forking of an existing template to make something that is essentially identical, and then replacing the original template in the articles with the new template, is not how things are done. I see why you did it, but it's not the right resolution to a content dispute. – Jonesey95 (talk) 13:19, 31 August 2026 (UTC)

Kudos

This may sound sarcastic (tone is impossible via text) but know that I mean this genuinely. Wanted to say kudos to you for keeping a calmer tone at Template talk:Infobox UK place. This debates drive me nuts and I admire your ability to rise above the bull shit. Zackmann (^{Talk to me}/_{What I been doing}) 02:38, 1 September 2026 (UTC)

Thanks. I have died on too many hills here on Wikipedia, eventually learning to moderate my reactions most of the time. One thing I have learned is that it doesn't matter how right I am if one or two (unreasonable) people (with bad arguments) disagree with my (amazing, brilliant, and supported by guidelines and policies) plan. The disagreement will mean that the plan will be stopped, either by those people or by a neutral third party who comes in, shrugs, and says "no consensus, status quo prevails". I got tired of getting zero results and learned to accept small improvements and try for subsequent improvements later. – Jonesey95 (talk) 04:19, 1 September 2026 (UTC)

That was immensely well said. Thank you! Zackmann (^{Talk to me}/_{What I been doing}) 04:21, 1 September 2026 (UTC)