Misplaced Pages

This is an old revision of this page, as edited by J04n (talk | contribs) at 00:04, 30 December 2023 (→Thank you!: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Archives

2009–2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023

This page has archives. Sections older than 90 days may be automatically archived by Lowercase sigmabot III when more than 20 sections are present.

Template:Source in source

Thanks for putting this up for deletion. I just looked for the page to nominate it and discovered that you had already done so. Regards, Rjj (talk) 17:53, 30 September 2023 (UTC)

Thank you!

Dear Jonesey95, i'm sorry you had work with my article. Meanwhile i do have a "vademecum" (in Word) with all the various info on the German and the English wikipedia, and i sincerely hope that i won't make so much mistakes anymore. Kind regards, and again, Thanks! Naomi Hennig (talk) 20:11, 30 September 2023 (UTC)

You did all of the difficult work. I just came in with a tiny broom and dustpan to tidy up a bit. – Jonesey95 (talk) 22:04, 30 September 2023 (UTC)

Linter errors on fresh Signpost articles?

Hmm... I just noticed this. Has this been going on for longer than just this issue? Is there something in the publishing script that needs to be fixed? jp×g 06:34, 4 October 2023 (UTC)

One of the pages was missing its ending block/article templates. I don't know whether the addition of those templates is semi-automated or manual. Other pages were missing closing italic markup, which has nothing to do with the publishing scripts. Unfortunately, there is nothing in the MediaWiki software that prevents or warns against the creation of new syntax errors. – Jonesey95 (talk) 14:14, 4 October 2023 (UTC)

Template:uncat

Hi. See diff. I am confused. I saw categories on both the template and the doc page before you added {{uncat}} back.

• Template:Header test
• Template:Header test/doc

--Timeshifter (talk) 21:24, 4 October 2023 (UTC)

That's just a tracking category auto-added by a template, not a category that helps editors find the template, see other templates like it, and figure out which one they should use. – Jonesey95 (talk) 21:26, 4 October 2023 (UTC)

Thanks. I added a topic category to {{sticky header}}. I will leave out a topic category for {{header test}} since it is just for testing stuff. It has come in very handy for that. --Timeshifter (talk) 22:27, 4 October 2023 (UTC)

OK. Being in Category:Uncategorized pages will keep it off of the report, so as long as that stays, I don't have a problem with it. – Jonesey95 (talk) 00:41, 5 October 2023 (UTC)

GOCE script hangs up

Hi again, Jonesey. I've had good luck with the script the last couple of drives, but this section has brought me to my knees:

== ] (]) ==
{{GOCE Article list
|articles = 
# {{Completed}} ] (33)
# {{Completed}} ] (397)
# {{Completed}} ] (1,092)
# {{Completed}} ] (371‎)
# {{Completed}} ] (171)
# {{Completed}} ] (190)
# {{Completed}} ] (34)
|total-articles = 7
|total-words = 2,288
|rollover-words = 0
}}

I've corrected their input errors to the drive page on my input file (which is copypasted here), but the script won't get past this and I can't see anything else wrong; do you? Thanks for your help and all the best, Miniapolis 18:45, 5 October 2023 (UTC)

I don't see a problem. Are you sure it's getting hung up on this one? It may be processing this one and getting stuck on the next one. Is there a weird hidden character that is left over from your removal of the zero-word article line? If so, it didn't survive the copy-paste above. I haven't run the script for a few years now, but I'd be willing to take a look at your input file and the script output if you post them in a sandbox. – Jonesey95 (talk) 19:58, 5 October 2023 (UTC)

Thanks for your offer to help, Jonesey. The input and output files are at User:Miniapolis/GOCE sandbox, and I've already tried reformatting the all-caps username :-). All the best, Miniapolis 22:40, 5 October 2023 (UTC)

I found an extra hidden character after "371" in one of the counts. Copy out what is on the page now. – Jonesey95 (talk) 01:32, 6 October 2023 (UTC)

Thanks so much! Unfortunately, though, the script still hung up there. I removed SAMBOT2000xp, and it worked; I'll add them manually. I wonder if it's a thing with that uppercase sig. One of these days, please tell me how you found that hidden character. Thanks again and all the best, Miniapolis 12:57, 6 October 2023 (UTC)

Ah, well. That's not too many to add manually. I copied the entire text into a text editor on my computer (in my case BBEdit for Mac OS) and told the software to show me all of the spaces and invisible characters. There was one right after "371" and before the closing parenthesis. I was able to backspace to remove it, even though I couldn't see it. – Jonesey95 (talk) 13:13, 6 October 2023 (UTC)

September 2023 GOCE drive award

		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 September 2023 Backlog Elimination Drive. Congratulations, and thank you for your contributions! Dhtwiki (talk) 10:42, 7 October 2023 (UTC)

Incorrect Edits to Lester Fuess Eastman page in 2020

A team of colleagues, Cornell administrators, and former PhD students all worked together in 2019 and 2020 in preparing a comprehensive wikipedia page for Prof. Lester Fuess Eastman late of Cornell University and you removed very large chunks of content from this article. We would like it restored but it appears we will now need to redo the entire article. Do you have a sense of why you took this action? Please respond at your earliest convenience. LEVlamb (talk) 03:50, 15 October 2023 (UTC)

(talk page watcher) @LEVlamb: You refer, presumably, to the reversion by Jonesey95 of these three edits. I fully agree with Jonesey95 on that one. The edits completely broke the referencing used in the article and created a mess at the bottom of the page. The additional content was entirely unreferenced, and so failed the policy on verifiability; it also failed the policy on neutrality. Further, you would appear to have a conflict of interest. --Redrose64 🌹 (talk) 07:54, 15 October 2023 (UTC)

Yes, what Redrose64 said. Refer especially to the conflict of interest link, given your explanation. – Jonesey95 (talk) 14:00, 15 October 2023 (UTC)

The material was prepared by the former students and colleagues of Lester Eastman. I do no agree that their description of his research would be a conflict of interest or biased. His research is well know and he had many patents and published articles to reinforce this description of his work. I was the aggregator of various contributors and not its author. 2600:4040:5E0A:8000:F4E8:922A:C9B5:B6D4 (talk) 19:18, 15 October 2023 (UTC)

In this case, the Misplaced Pages parameters in the COI policy seem overly restricitve. Who better than scientific colleagues and associates to describe a peer or mentor's contribution to science or technology? I am conferring with the authors to see if they would like to pursue it further, but it appears that another venue will be a better platform for capturing additional dimensions related to his research and the important scientific developments stemming from it.If they agree, we will leave it as limited by jonesey95 and review the relevance and accuracy of more recent additions / edits. 2600:4040:5E0A:8000:F4E8:922A:C9B5:B6D4 (talk) 20:16, 15 October 2023 (UTC)

See WP:COIEDIT, which explains how to request changes to pages for which you have a COI, including pages about people who are your friends, employers, mentors, or colleagues. It is not difficult. In any event, the primary reason for the revert was a technical one: the edit in question introduced a large batch of technical errors onto the page. – Jonesey95 (talk) 00:42, 16 October 2023 (UTC)

Tech News: 2023-42

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

Recent changes

• The Unified login system's edge login should now be fixed for some browsers (Chrome, Edge, Opera). This means that if you visit a new sister project wiki, you should be logged in automatically without the need to click "Log in" or reload the page. Feedback on whether it's working for you is welcome.
• Edit notices are now available within the MobileFrontend/Minerva skin. This feature was inspired by the gadget on English Misplaced Pages. See more details in T316178.

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 17 October. It will be on non-Misplaced Pages wikis and some Wikipedias from 18 October. It will be on all wikis from 19 October (calendar).

Future changes

• In 3 weeks, in the Vector 2022 skin, code related to addPortletLink and #p-namespaces that was deprecated one year ago will be removed. If you notice tools that should appear next to the "Discussion" tab are then missing, please tell the gadget's maintainers to see instructions in the Phabricator task.

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

MediaWiki message delivery 23:45, 16 October 2023 (UTC)

Page mover right

Shall I go ahead and give you the page mover user right so you can move categories with history instead of having to move them by cut-and-paste? * Pppery * _{it has begun...} 00:32, 19 October 2023 (UTC)

That would probably be quite useful! Is there a primer somewhere that explains how to use this user right and how to avoid its potential pitfalls? As with template editing, I can imagine it being a source of interesting screw-ups. – Jonesey95 (talk) 00:33, 19 October 2023 (UTC)

I think the standard template below should explain everything relevant. When it comes to categories, I think you already know how to avoid most of the pitfalls (since template-generated categories are the most common one), except that even though you have the ability to push the button the social expectation is still that all moves go through CfD. * Pppery * _{it has begun...} 00:37, 19 October 2023 (UTC)

Hello, Jonesey95. Your account has been granted the "extendedmover" user right, either following a request for it or demonstrating familiarity with working with article names and moving pages. You are now able to rename pages without leaving behind a redirect, move subpages when moving the parent page(s), and move category pages.

Please take a moment to review Misplaced Pages:Page mover for more information on this user right, especially the criteria for moving pages without leaving a redirect. Please remember to follow post-move cleanup procedures and make link corrections where necessary, including broken double-redirects when suppressredirect is used. This can be done using Special:WhatLinksHere. It is also very important that no one else be allowed to access your account, so you should consider taking a few moments to secure your password. As with all user rights, be aware that if abused, or used in controversial ways without consensus, your page mover status can be revoked.

Useful links:

• Misplaced Pages:Requested moves
• Category:Requested moves, for article renaming requests awaiting action.

If you do not want the page mover right anymore, just let me know, and I'll remove it. Thank you, and happy editing! * Pppery * _{it has begun...} 00:37, 19 October 2023 (UTC)

Thanks for the links. I have read the relevant pages. For now, I will stick to pages affected by this CFD. I suspect that it means that I will run afoul of Liz and Bearcat, and possibly others, who keep a close watch on category problems. I hope that they will be willing to post here with gentle messages when I do something out of order.

I also suspect that since there are 1,000+ categories involved in that CFD, that the category error reports will be in a bit of turmoil over the next couple of days as gnomes work to edit userboxes, other templates, and individual pages that assign categories, and then move the categories, or possibly do those things in a slightly different order. I don't see an efficient way to do it without leaving some temporary red links lying around for a period of hours or even a couple of days, but I'm open to learning if there is a standard workflow. – Jonesey95 (talk) 03:34, 19 October 2023 (UTC)

I am tracking these member/participant category moves at User:Jonesey95/sandbox4 if anyone is interested. Many category moves require a template edit followed by a few individual page edits to tidy up before the member category is empty. – Jonesey95 (talk) 06:12, 19 October 2023 (UTC)

If you haven't noticed already, you might want to look at the ucat param in Template:User WP/switch. -- WOSlinker (talk) 10:57, 19 October 2023 (UTC)

Yes, I've looked at it a few times. What I take away is that when {{User WP}} is used in a userbox, you have to move the category first so that it exists and passes the ifexist test. At that point, the pages will reassign themselves. I haven't figured out what to do with category redirects that already exist, so I'm leaving those for later, or for more experienced editors. – Jonesey95 (talk) 14:27, 19 October 2023 (UTC)

You change the name of category on WikiProject userboxes

Hi, hope you are doing well, I have notice you have changed name of usercategory of userboxes in WP:CVJK but the old category is still there. Kindly move the category from Category:WikiProject Chenab Valley members to Category:WikiProject Chenab Valley participants which is actually supposed by you. Thank you. ❯❯❯ Chunky aka Al Kashmiri (✍️) 04:41, 20 October 2023 (UTC)

 Done. Over 1,000 category pages are being moved, so you may see red-linked categories over the next couple of days. – Jonesey95 (talk) 04:46, 20 October 2023 (UTC)

Category:WikiProject Dallas-Fort Worth members

Hello, Jonesey95,

I see you moved the category page over to its new title. Are you also going to move all of the category contents? Moving the category page is just the easy, first step in the process of recategorizing all of these pages. Thank you. Liz 07:09, 20 October 2023 (UTC)

In short, yes. In general, I am moving pages to the new category before moving the category page itself (by adjusting template or userbox code), but sometimes the process reverses those steps. As I wrote above, there are over 1,000 of these categories, populated by hundreds of templates. Some of the pages move automatically because they use {{User WP}}, and some of the pages need to be adjusted manually or moved by modifying templates. The process will take a few days. I am keeping a master list of all of the categories to ensure that I don't leave behind any stragglers. – Jonesey95 (talk) 14:20, 20 October 2023 (UTC)

PS to Liz: If you or another admin adds the rest of the category list to Misplaced Pages:Categories for discussion/Working/Large, the bot will take care of most of the categorization of individual user pages. – Jonesey95 (talk) 15:17, 20 October 2023 (UTC)

Speedy CFD

Categories proposed for speedy renaming need to wait 48 years hours. Can you please not jump the gun on ones that weren't in the original nomination? Timrollpickering (talk) 21:41, 20 October 2023 (UTC)

I would be happy to comply if I knew which categories you were talking about. I think I have applied speedy tags only to categories related to the CFD that were in the way of moves. – Jonesey95 (talk) 21:48, 20 October 2023 (UTC)

Category:WikiProject Animation members by work groups was only tagged today yet moved immediately. Timrollpickering (talk) 22:00, 20 October 2023 (UTC)

Hmm, I didn't notice anything different about the banner; I must be a bit banner-blind after a couple thousand edits related to this CFD. I think I found that category by trolling through Category:Wikipedians by WikiProject and looking for any remaining categories with "member" in the name. – Jonesey95 (talk) 22:27, 20 October 2023 (UTC)

48 years? How is that 'speedy'?

—Trappist the monk (talk) 22:14, 20 October 2023 (UTC)

Broken linter fix

Hi Jonesey95, thanks for fixing linter errors! I hate broken HTML and am happy about everyone who fixes it. Would you mind re-trying at Template:Editnotices/Page/Wikipedia:Administrator intervention against vandalism? Thank you very much in advance! ~ ToBeFree (talk) 15:45, 21 October 2023 (UTC)

Thanks for AGF with that dumb edit. I put the table closing tag in the wrong place! – Jonesey95 (talk) 20:24, 21 October 2023 (UTC)

October blitz bling

		The Modest Barnstar
		This barnstar is awarded to Jonesey95 for copy edits totaling over 2,000 words (including rollover words) during the GOCE October 2023 Copy Editing Blitz. Congratulations, and thank you for your contributions! Miniapolis 13:10, 24 October 2023 (UTC)

DYK lints

Per this diff: I'm using User:SD0001/DYK-helper.js for my noms, so that is where the bad tags are coming from. Might be worth pinging them about or making a TE request. jp×g 04:06, 25 October 2023 (UTC)

@SD0001: Looking at this, I see what is up: line 443 and line 452 can be changed.

Line 443 from

		' | hook = ' + params.hook + (params.source ? (' <small>Source: ' + params.source + '</small>') : '');

to

		' | hook = ' + params.hook + (params.source ? (' {{smalldiv|1=Source: ' + params.source + '}}') : '');

Line 452 from

			(params ? (' <small>Source: ' + params + '</small>') : '');

to

			(params ? (' {{smalldiv|1=Source: ' + params + '}}') : '');

Haven't tested this so I am not 100% on it working properly but I can't think of a reason why it wouldn't work. jp×g 04:11, 25 October 2023 (UTC)

It may need a line break before the {{smalldiv}}. This may break the bullet continuity. It will need some testing, I imagine. I see five or so of these per month, and other editors are probably fixing more, since template space is essentially free of Linter errors and we work hard to keep it that way. – Jonesey95 (talk) 04:38, 25 October 2023 (UTC)

CS1

Thanks for the heads-up about having posted to an unwatched talk page. Didn't realize at the time. I moved it to WT:CS1.  — SMcCandlish ☏ ¢ 😼  02:03, 26 October 2023 (UTC)

Tech News: 2023-45

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

Recent changes

• In the Vector 2022 skin, the default font-size of a number of navigational elements (tagline, tools menu, navigational links, and more) has been increased slightly to match the font size used in page content.

Problems

• Last week, there was a problem displaying some recent edits on a few wikis, for 1-6 hours. The edits were saved but not immediately shown. This was due to a database problem.

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 7 November. It will be on non-Misplaced Pages wikis and some Wikipedias from 8 November. It will be on all wikis from 9 November (calendar).
• The Growth team will reassign newcomers from former mentors to the currently active mentors. They have also changed the notification language to be more user-friendly.

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

MediaWiki message delivery 21:03, 6 November 2023 (UTC)

Lint lint lint lint lint lint lint lint

yet another bizarre thing from signpost history.... this time it's Template:S-s which is apparently used in many old Signpost issue pages, and also transcluded onto approx 2.7k user talk pages. The situation is basically this:

• {{S-s}}, a very short and easy name.
• Misplaced Pages:Signpost/Template:Cover-item, a horrible name (and also doesn't follow the Signpost template naming scheme).

are basically the same template with some minor differences. I have experimented with (and succeeded at) coming up with a way for the current form of S-s (i.e. the version in user talk space) to be easily substed. The rest of its 5k transclusions are just from Signpost issue pages and archive pages and single pages themselves, i.e. very easy to just fix. What I think would probably be best is to:

1. Subst current user talk instances of {{S-s}} (I think this is what's causing the fostering errors)
2. Move the code from Signpost/item to {{S-s}}
3. Update Signpost pages that invoke Signpost/item (approx. 1k) to invoke {{S-s}}
4. Profit (all Signpost issue/archive pages use the same templates for cover items).

I think this should go hand-in-hand with some other mass changes, since it's going to be a very long AWB run, that goes over a bunch of pages: what else in user talk space needs to be fixed? Do you have a script that you can add regexes to? Is there something I can add to my own script? jp×g🗯️ 01:02, 8 November 2023 (UTC)

Alternately, maybe all of that damn substing could be avoided if we just figured out what was causing the fostered content errors and fixed it (?) jp×g🗯️ 01:04, 8 November 2023 (UTC)

I don't think we should do substing of {{s-s}} on 21,000 old user talk pages. Also, it might be OK to have two templates if they had reasonable names. I think we should just (a) figure out the problem and fix {{s-s}} if necessary and then (b) move one or both templates to much better names, leaving redirects. {{s-s}} is a bad name left over from the old Wild West days of Misplaced Pages. No judgment on the old-timers who made it; we have just learned how to name templates better in the past 15 or so years. Does {{s-s}} actually need to be changed, or is renaming enough? – Jonesey95 (talk) 01:55, 8 November 2023 (UTC)

Ha! I was quite frightened by that 21k number as well. It is misleading, though. Nearly all of those are caused by the Signpost issue pages themselves using {{s-s}}, so fixing them has nothing to do with editing user pages (the upstream issue pages can be fixed and the userspace transclusions will disappear). There are only a couple thousand userpages which have them hardcoded into their own source. I am still somewhat concerned about that, because it is a large number of pages. But I don't think it is impossible. jp×g🗯️ 02:32, 8 November 2023 (UTC)

Either way, can we just move {{s-s}} to {{Signpost article link old}} or Misplaced Pages:Misplaced Pages Signpost/Templates/signpost-article-link-old or something similar, adjust its documentation, and be done with it? I don't see anything broken. – Jonesey95 (talk) 15:46, 8 November 2023 (UTC)

Unused templates report

Hey, did you do anything to exclude templates from the unused report? The latest update removed about 1k pages and I can't seem to find a pattern of what they all share. Gonnym (talk) 11:07, 16 November 2023 (UTC)

Not me. You could ask the bot operator or VPT, or wait a day to see if it fixes itself. It may have been a temporary server issue. – Jonesey95 (talk) 14:35, 16 November 2023 (UTC)

Tech News: 2023-47

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

Changes later this week

• There is no new MediaWiki version this week.
• Starting on Wednesday, a new set of Wikipedias will get "Add a link" (Quechua Misplaced Pages, Romansh Misplaced Pages, Romani Misplaced Pages, Rundi Misplaced Pages, Aromanian Misplaced Pages, Tarandíne Misplaced Pages, Rusyn Misplaced Pages, Kinyarwanda Misplaced Pages, Sanskrit Misplaced Pages, Sakha Misplaced Pages, Santali Misplaced Pages, Sardinian Misplaced Pages, Sicilian Misplaced Pages, Scots Misplaced Pages, Sindhi Misplaced Pages, Northern Sami Misplaced Pages, Sango Misplaced Pages, Serbo-Croatian Misplaced Pages, Sinhala Misplaced Pages, Slovak Misplaced Pages, Slovenian Misplaced Pages, Samoan Misplaced Pages, Somali Misplaced Pages, Albanian Misplaced Pages, Serbian Misplaced Pages, Sranan Tongo Misplaced Pages, Swati Misplaced Pages, Southern Sotho Misplaced Pages, Saterland Frisian Misplaced Pages, Sundanese Misplaced Pages, Silesian Misplaced Pages, Tamil Misplaced Pages, Tulu Misplaced Pages, Telugu Misplaced Pages, Tetum Misplaced Pages, Tajik Misplaced Pages, Thai Misplaced Pages, Turkmen Misplaced Pages, Tagalog Misplaced Pages, Tswana Misplaced Pages, Tongan Misplaced Pages, Tok Pisin Misplaced Pages, Turkish Misplaced Pages, Tsonga Misplaced Pages, Tatar Misplaced Pages, Twi Misplaced Pages, Tahitian Misplaced Pages, Tuvinian Misplaced Pages, Udmurt Misplaced Pages, Uyghur Misplaced Pages, Uzbek Misplaced Pages, Venda Misplaced Pages, Venetian Misplaced Pages, Veps Misplaced Pages, West Flemish Misplaced Pages, Volapük Misplaced Pages). This is part of the progressive deployment of this tool to more Wikipedias. The communities can configure how this feature works locally.
• The Vector 2022 skin will have some minor visual changes to drop-down menus, column widths, and more. These changes were added to four Wikipedias last week. If no issues are found, these changes will proceed to all wikis this week. These changes will make it possible to add new menus for readability and dark mode. Learn more.

Future changes

• There is an update on re-enabling the Graph Extension. To speed up the process, Vega 2 will not be supported and only some protocols will be available at launch. You can help by sharing what you think about the plan.

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

MediaWiki message delivery 00:53, 21 November 2023 (UTC)

Tidy Fonts

Thanks, but I have the tidy fonts well in hand per my edit agreement with Primefac for these pages with Tidy Fonts that you were aware of. I have been asking him for small sets that I found manageable and despite my agile response in delinting these pages, you forced nearly all pages of my request yesterday to take two edits. If you could ignore the remaining 140 or so pages with Tidy Font errors so that we aren't duplicating efforts and unnecessarily bothering these admin with multiple edits, that would be great. Thanks, Zinnober9 (talk) 16:55, 26 November 2023 (UTC)

What I'm reading is that you own the tidy font link list. Hmm. OK. I generally make sure to leave behind only obsolete tags, mostly font tags, since they are lower priority and more readily fixable by bots. If Legobot ever comes back, it can clean up most font tags and should be able to add other easy obsolete tag patterns. Thanks for being part of the de-linting team! – Jonesey95 (talk) 17:15, 26 November 2023 (UTC)

Normally I wouldn't care and would be very happy for the assistance, but I feel I'm more on the hook for these since these are admin archives and they've been special requests that I've instigated. I want to bother the admins as little as possible and not leave things behind for later when we have access now, especially since there isn't a bot running obsoletes and other easier stuff at the moment. I should be done with the remainder in the next few days.

Not sure which error I'll focus on next, but whatever it will be, it won't be something that I feel any sort of ownership over, and I'd be very happy to have your knowledgeable assistance on if you so desire! Zinnober9 (talk) 00:20, 27 November 2023 (UTC)

ArbCom 2023 Elections voter message

Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Misplaced Pages arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:31, 28 November 2023 (UTC)

November 2023

This is your only warning; if you remove or change other editors' legitimate talk page comments again, as you did at Template_talk:Infobox_drug, you may be blocked from editing without further notice.
You know...you've already pissed me off several times by making false claims, don't add to it by editing my comments. Lint schmindt. Don't do it. This. Likewise: You can not like it, but stop falsely portraying my proposed edit as adding unreferenced info to wikipedia and not following the RFC. Be aware that that false assertions of personal attacks are themselves personal attacks. Knock it off. All of it. RudolfoMD (talk) 12:04, 29 November 2023 (UTC)

You're in the wrong here. That was a syntax error, the only one of its kind in all of Misplaced Pages at the time, that was negatively affecting the display of the rest of the page. My fix was routine and was clearly allowed by Misplaced Pages guidelines. Please take a deep breath and assume good faith. – Jonesey95 (talk) 13:21, 29 November 2023 (UTC)

Partly. Struck warning. You too. This is worth reading and links to a relevant guideline: Welcome to Misplaced Pages. Everyone is welcome to contribute constructively to the encyclopedia. However, discussion pages are meant to be a record of a discussion; deleting or editing legitimate comments is considered bad practice, even if you meant well. Even making spelling and grammatical corrections in others' comments is generally frowned upon, as it tends to irritate the users whose comments you are correcting. Take a look at the welcome page to learn more about contributing to this encyclopedia. Thank you.. It's standard warning {{uw-tpv1}}. I have now figured out that while your edit messed up the indentation of my comment which followed, which I had to fix, your edit did reduce later indentation back to normal also. Can you accept this? : "Even making spelling and grammatical corrections in others' comments is generally frowned upon, as it tends to irritate the users whose comments you are correcting." Why not act in good faith and stop falsely portraying my proposed edit as adding unreferenced info to wikipedia and not following the RFC? FYI, I presume you'll be pleased to hear I added the black box warning sourcing to wikidata too, so now it's redundant.

WP:TPO. I fixed a formatting error in your post that broke the formatting for the rest of the page, including indenting subsequent section headers. If I hadn't done it, another gnome would have come along within the hour to do exactly the same thing. You keep accusing me, someone who assumes good faith, is a trusted and experienced template editor, and links to guidelines, of things that are untrue. Does that sort of behavior work for you in the rest of your life? In my experience, that sort of behavior is not going to help you get the edit you want at {{Infobox drug}}. You continue to accuse me of disruption and libel, and I would rather not hear from you again. – Jonesey95 (talk) 01:00, 30 November 2023 (UTC)

@RudolfoMD compare the position of the level two headers at these two links (scroll to the top to confirm that these links refer to your edit):

• Special:Diff/1187422798#Edit request 15 November 2023 – header is all the way left
• Special:Diff/1187422798#Unreferenced data is being pulled from Wikidata – header is indented 6.4em

After Editor Jonesey95's edit, notice the position of the second header:

• Special:Diff/1187423835#Unreferenced data is being pulled from Wikidata – header is all the way left where it belongs

Editor Jonesey95 correctly fixed the formatting error introduced in your edit. You owe him an apology. (and yes, I fixed the markup-nesting error in your OP.)

—Trappist the monk (talk) 01:44, 30 November 2023 (UTC)

Nonstandard font color names don't translate

I noticed in your edit of 20:23, 29 November 2023 (UTC) of User talk:Jimbo Wales/Archive 201, you changed

] (]): (uncomment to show rendering:)

to

] (]): QuackGuru (talk)

As noted at MW:Help:Lint errors/obsolete-tag: <font color="x"> accepts some nonstandard font color names such as burntorange and vermillion, which are not on the list of 16 HTML colors or the list of 124 X11 colors. The replacement <span style="color: ..."> markup recognizes only color names on these lists. So, Quackguru's signature font colors get lost in translation. Not sure if you want to do anything about it, just passing this along. Feel free to remove the fonty display from this comment to remove two obsolete HTML lint errors. —Anomalocaris (talk) 09:16, 30 November 2023 (UTC)

Those colors do not appear to be supported by font tags either (they both show as red – possibly #E00000 and #B00000, respectively, which do not appear to match valid CSS named colors – here on my talk page in the browser), so I'm inclined to consider this a GIGO and not worry about it. Blue links to both pages are a reader-friendly degradation mode. I'll give it a thought, but I don't see a great way to fix my regexes. I suppose I could have a giant list of all of the colors in each of my color-replacement regexes, but ugh. Thanks for the note; I appreciate knowing when I'm doing something that doesn't work exactly as I expect. – Jonesey95 (talk) 15:45, 30 November 2023 (UTC)

This may be a browser thing - it is known that some browsers are more tolerant of incorrectly-formed HTML than other browsers may be; and colour values may be among those where different browsers have different ways of failing gracefully.

As a historical note, the early HTML specs only allowed the 16 basic colour names; one or two browsers provided 100 or so extra color names, and once these began to be recognised by the majority of browsers, they became formalised as what we now know as the X11 colours. Other changes have occurred: orange was added to the basic set at some point, which now has 17 colour names; and more recently, rebeccapurple was added to the X11 set for CSS Color Module Level 4, but not all browsers recognise it yet. --Redrose64 🌹 (talk) 00:07, 1 December 2023 (UTC)

As another historical note, it was QuackGuru's signature that led me to put in that note at MW:Help:Lint errors/obsolete-tag. —Anomalocaris (talk) 09:38, 1 December 2023 (UTC)

George Hamilton of Greenlaw and Roscrea

Dear Janesey95, I wanted to report progress on one of the problems you pointed out concerning the MOS compliancy of the timeline tables that I have added to certain biographies. On 14 April 2023 you pointed out to me on the example of the article George Hamilton of Greenlaw and Roscrea that I should:

1. explain the use I made of non-standard (MOS:ITALIC) Italics
2. comply with MOS:DATE
3. comply with MOS:DONTHIDE

I made progress on No. 2 by finding that right-aligning solves the problem. In this way I can comply with MOS using the dmy format and still have the year stand out more to help the reader browsing for an event in a certain year.

I have implemented this on the cited example (George Hamilton of Greenlaw and Roscrea) and some others (e.g. Antoine Hamilton) and will slowly change it in the many other timelines I made. Concerning problem number 1, I still just explain my particular use of italics in a initial remark (is this good enough?) and concerning number three my timelines still do not comply. I consider that it is admissible to present them collapsed. The DONTHIDE rule suffers many generally accepted exceptions such as collapsed ahnentafels and many collapsed navigational boxes. I find that DONTHIDE treats Misplaced Pages like a paper encyclopedia and forbids us to take advantage of what can be done in a web-based one. Besides the table shows and hides itself without problems in mobile view. With thanks and best regards, Johannes Schade (talk) 19:32, 2 December 2023 (UTC)

The date alignment looks better. I made a couple of adjustments for accessibility and formatting. – Jonesey95 (talk) 00:03, 3 December 2023 (UTC)

Dear Jonesey95, thanks for looking into this. Sorry to still bother you. I struggle to understand your "ajustments for accessibility and formatting". You made two changes: the first concerns the table caption (or title), in the second you reduced the italics to just "italics".

1. You changed:

|colspan=3|Timeline -> |+Timeline

With your version we fall into the case of a table with caption in Help:Table#Collapsible tables where the collapsed version shows the caption and then the "show" control in the next line below it. I find this is not very satifactory because it is not obvious for the reader that it is a table that has been collapsed. The caption looks like a section heading. Also it wastes space by occupying two lines.

I therefore thought it better to pretend that the table had no caption by including the caption in the first header row. The collapsed table then shows as a table cell holding the caption and the "show" control. I feel this is much more satisfactory. The reader can tell immediately that it was a table that has been collapsed. This is similar to the way navboxes are collapsed, which are essentially also tables.

2. Another example of me abusing italics contrary to MOS:ITALICS. I intended to indicate that this is a remark, not really a table content. Perhaps I should prefix this with "Remark:".

An example of the newest type of timetable can be found in the article Felim O'Neill of Kinard, which also has a collapsed navbox. Dear Jonesey95, thank you again for your attention and for letting me profit from your deep understanding of the MOS. Best regards, Johannes Schade (talk) 20:30, 3 December 2023 (UTC)

All data tables need a table caption for accessibility. Accessibility is a core policy of Misplaced Pages. See MOS:TABLECAPTION. I think "Remark:" is fine. You could also put the note at the bottom of the table, since it's a sort of table legend. – Jonesey95 (talk) 20:53, 3 December 2023 (UTC)

Dear Jonesey95. Yes, I want to comply with MOS:TABLECAPTION, even if it is only a how-to guide and not a Misplaced Pages guideline and there are many tables in FAs that do not have a "|+" caption. If the collapsed table is displayed in two lines; that is not a major obstacle. I think I found a neat way how to display the "caveat" about the lack of precision and the "remark" about the use of italics for historical background dates. Please have another look at George Hamilton of Greenlaw and Roscrea. With many thanks for your patient guidance. I learned a lot from you, Johannes Schade (talk) 20:42, 7 December 2023 (UTC)

This would all be easier for you if complied with MOS:DONTHIDE, but if you are OK with a two-line table header when it is collapsed, I'm not going to fight about it. As for "it is only a how-to guide", I linked to it because Misplaced Pages:Manual of Style/Accessibility#Data tables, a guideline, is not as detailed. – Jonesey95 (talk) 23:18, 7 December 2023 (UTC)

Dear Jonesey95, of course you are right, MOS:Accessibility#Data and WP:Manual of Style/Tables both explicitly prescribe table captions. I looked a bit at tables in recent FAs and found that "class=wikitable ..." is usually preferred over the use of the "Table" template; also that "class=nowrap" on the |+ line keeps the collapsed table on one line. So I made corresponding changes. I am not so sure about my use of the "border:none" style that displays the caveat and remark as if they were not part of the table but above it. Is that acceptable? Some might use footnotes, but I find footnotes can be too easily ignored. Quite a few recent FAs have collapsed tables, e.g. the FA Argosy (magazine) (6 December 2023). Despite MOS:DONTHIDE they do not seem to be forbidden. WP:Manual of Style/Tables#Appearance states "Consideration may be given to collapsing tables which consolidate information covered in the prose." I think the timeline table does "consolidate information covered in the prose" and is not direct content. With many thanks and best regards, Johannes Schade (talk) 16:21, 8 December 2023 (UTC)

Tech News: 2023-49

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

Recent changes

• The spacing between paragraphs on Vector 2022 has been changed from 7px to 14px to match the size of the text. This will make it easier to distinguish paragraphs from sentences.

MediaWiki message delivery 23:48, 4 December 2023 (UTC)

Revert

Hi, I just saw you reverted my edit on Template:K-Electric F.C squad. The department or "club" has been already dissolved since 3-4 years ago. See:

https://footballpakistan.com/2021/03/ke-footballers-left-to-make-hard-choices-express-tribune/

https://footballpakistan.com/2020/10/huge-blow-as-k-electric-all-set-to-disband-football-team-express-tribune/

https://footballpakistan.com/2020/11/footballers-stage-protest-against-k-electric-disbanding-team-the-news/

Or the recent https://www.geosuper.tv/latest/22734-pff-calls-36-players-for-national-training-camp Throwawayjamal047 (talk) 12:33, 6 December 2023 (UTC)

See WP:TFD if the template is no longer useful. Blanking the template is not appropriate. – Jonesey95 (talk) 15:17, 6 December 2023 (UTC)

November 2023 GOCE drive award

		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 November 2023 Backlog Elimination Drive. Congratulations, and thank you for your contributions! Dhtwiki (talk) 10:19, 7 December 2023 (UTC)

Need a page to be created

Hi, I have seen your userpage on Misplaced Pages and it looks amazing. Can you please help me to create a Misplaced Pages page about a Company named as TechMatter (Pvt) Ltd.

I will be waiting for you.

Thanks Jawwadimran05 (talk) 12:56, 8 December 2023 (UTC)

See Help:Your first article. – Jonesey95 (talk) 14:17, 8 December 2023 (UTC)

Template:Species lists for pine subfamilies sidebar

Hi Jonesey. Any objection if I delete this via WP:G7? You made one edit to add a documentation page. - Dank (push to talk) 16:54, 9 December 2023 (UTC)

No objections. – Jonesey95 (talk) 20:58, 9 December 2023 (UTC)

Guild of Copy Editors December 2023 Newsletter

Guild of Copy Editors December 2023 Newsletter Hello, and welcome to the December 2023 newsletter, a quarterly digest of Guild activities since September. Don't forget that you can unsubscribe at any time; see below. Election news: The Guild needs coordinators! If you'd like to help out, you may nominate yourself or any suitable editor—with their permission—for the Election of Coordinators for the first half of 2024. Nominations will close at 23:59 on 15 December (UTC). Voting begins immediately after the close of nominations and closes at 23:59 on 31 December. All editors in good standing (not under current sanctions) are eligible, and self-nominations are welcome. Coordinators normally serve a six-month term that ends at 23:59 on 30 June. Drive: Of the 69 editors who signed up for the September Backlog Elimination Drive, 40 copy-edited at least one article. Between them, they copy-edited 661,214 words in 290 articles. Barnstars awarded are listed here. Blitz: Of the 22 editors who signed up for the October Copy Editing Blitz, 13 copy-edited at least one article. Between them, they copy-edited 109,327 words in 52 articles. Barnstars awarded are listed here. Drive: During the November Backlog Elimination Drive, 38 of the 58 editors who signed up copy-edited at least one article. Between them, they copy-edited 458,620 words in 234 articles. Barnstars awarded are listed here. Blitz: Our December Copy Editing Blitz will run from 10 to 16 December. Barnstars awarded will be posted here. Progress report: As of 20:33, 10 December 2023 (UTC), GOCE copyeditors have processed 344 requests since 1 January, and the backlog stands at 2,191 articles. Other news: Our Annual Report for 2023 is planned for release in the new year. Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Dhtwiki, Miniapolis and Zippybonzo. To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

Message sent by Baffle gab1978 using MediaWiki message delivery (talk) 20:53, 10 December 2023 (UTC)

Would you consider becoming a New Page Reviewer?

Hi Jonesey95, we need experienced volunteers.

• New Page Patrol is currently struggling to keep up with the influx of new articles. We could use a few extra hands on deck if you think you can help.
• Reviewing/patrolling a page doesn't take much time but it requires a good understanding of Misplaced Pages policies and guidelines; Misplaced Pages needs experienced users to perform this task and there are precious few with the appropriate skills. Even a couple reviews a day can make a huge difference.
• Kindly read the tutorial before making your decision (if it looks daunting, don't worry, it basically boils down to checking CSD, notability, and title). If this looks like something that you can do, please consider joining us.
• If you would like to join the project and help out, please see the granting conditions. You can apply for the user-right HERE.
• If you have questions, please feel free to drop a message on my talk page or at the reviewer's discussion board.
• Cheers, and hope to see you around — ❯❯❯ Raydann 16:13, 11 December 2023 (UTC)

Raydann, thanks for the invitation. By the way, there is an unclosed <div> in this message. Please adjust your template or copy/paste wikitext, and please fix the pages where you have posted this message. I have added a closing div tag above. Thanks. – Jonesey95 (talk) 02:49, 12 December 2023 (UTC)

Duly noted. Thank you so much for noticing this. I'll fix this asap. Cheers! ❯❯❯ Raydann 08:03, 12 December 2023 (UTC)

Tech News: 2023-50

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

Recent changes

• On Wikimedia Commons, there are some minor user-interface improvements for the "choosing own vs not own work" step in the UploadWizard. This is part of the Structured Content team's project of improving UploadWizard on Commons.

Problems

• There was a problem showing the Newcomer homepage feature with the "impact module" and their page-view graphs, for a few days in early December. This has now been fixed.

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 December. It will be on non-Misplaced Pages wikis and some Wikipedias from 13 December. It will be on all wikis from 14 December (calendar).

Future changes

• The 2023 Developer Satisfaction Survey is seeking the opinions of the Wikimedia developer community. Please take the survey if you have any role in developing software for the Wikimedia ecosystem. The survey is open until 5 January 2024, and has an associated privacy statement.

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

MediaWiki message delivery 02:10, 12 December 2023 (UTC)

December 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 December 2023 Copy Editing Blitz. Congratulations, and thank you for your contributions! Miniapolis 02:27, 18 December 2023 (UTC)

Seasons Greetings!

Hello there, thanks for all of your contributions to Misplaced Pages! Wishing you a Very Merry Christmas and here's to a happy and productive 2024! ♦ Dr. Blofeld 20:10, 18 December 2023 (UTC)

signpost barrage

I am raising some major hell with WegweiserBot, let me know if there are any huge panoplies of lint errors I need to fix. S jp×g🗯️ 06:32, 21 December 2023 (UTC)

The only Linter errors I am seeing in the Signpost area are the same missing closing div tags that have been in Misplaced Pages:Misplaced Pages Signpost/2014-12-17/Featured content and friends. I think I listed them at the Signpost page a while ago. – Jonesey95 (talk) 15:08, 21 December 2023 (UTC)

Documentation

I feel like the templatedata at Template:Section header/doc is enough for documentation. Any more I should add? Aaron Liu (talk) 18:01, 22 December 2023 (UTC)

TemplateData is not documentation; it is code that tells the Visual Editor how to interact with the template. A couple of examples are always helpful. You may know what format |3= accepts, for example, but anyone else would have to use trial and error or look at the code. – Jonesey95 (talk) 19:57, 22 December 2023 (UTC)

I have discovered that not showing up in TOC was only because of the __NOTOC__ magic word, not because it was transcluded... I've converted the template into a wrapper.
However, why does being JSON that tells VE (and TemplateWizard) how to do stuff preclude being documentation? Or do you mean that the only thing missing was full examples and an example for |3= Aaron Liu (talk) 03:24, 23 December 2023 (UTC)

I admit that I was trying to help you learn from your own errors; I find that the lessons stick better that way. In creating examples, you appear to have discovered that |3= was not functional. That is a good reason to create a testcases page, but you can usually find basic errors like this when writing documentation with a few examples. – Jonesey95 (talk) 04:48, 23 December 2023 (UTC)

Thanks for cleaning up PostgreSQL

Hi,

Thanks for the cleanup to PostgreSQL, especially the lead, which I mostly introduced the problems into.

I'm curious why you added the comma to the sentence: "After a review in 2007, the development team decided to keep the name PostgreSQL and the alias Postgres." (I'm hoping for some guide I can use to improve my future writing.)
kop (talk) 19:59, 22 December 2023 (UTC)

I strongly prefer the addition of a comma after an introductory prepositional phrase. I think it improves clarity and flow. See here and here for grammar explanations. – Jonesey95 (talk) 20:04, 22 December 2023 (UTC)

A solstice greeting

❄️ Happy holidays! ❄️

{{u|Sdkb}}  06:42, 24 December 2023 (UTC)

Merry Christmas

Merry Christmas and a Prosperous 2024!

Hello Jonesey95, may you be surrounded by peace, success and happiness on this seasonal occasion. Spread the WikiLove by wishing another user a Merry Christmas and a Happy New Year, whether it be someone you have had disagreements with in the past, a good friend, or just some random person. Sending you heartfelt and warm greetings for Christmas and New Year 2024. Happy editing, ‑‑Neveselbert (talk · contribs · email) 17:35, 25 December 2023 (UTC) Spread the love by adding {{subst:Seasonal Greetings}} to other user talk pages.

‑‑Neveselbert (talk · contribs · email) 17:35, 25 December 2023 (UTC)

Thank you!

		What a Brilliant Idea Barnstar
		Thank you so much for your innovative idea to help with my problem at infobox album and your quick implemention! J04n(talk page) 00:04, 30 December 2023 (UTC)