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/Archive2025.

Archives

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

Question for later

Small question, no rush. Hope you are enjoying your Wiki-vacation. Is there a way to tag or "report" a template that has no documentation of usage so that it could be flagged for "needs documentation" so some could be added? I ran across {{TGVweb}} and mistook where it goes on a page due to the complete lack of usage documentation. It had been bulleted on two articles and they report a stripped div when bulleted. Reading the statement, I initially mistook it to be akin to {{stub}} that displays at the top, but upon further inspection I've discovered it's more closely associated with {{Source-attribution}}.
Thanks, happy new year. Zinnober9 (talk) 17:51, 4 January 2025 (UTC)[reply]

(talk page watcher) @Zinnober9: Try {{Improve documentation}}. It must be placed inside <noinclude>...</noinclude> tags, unless there is a documentation subpage, in which case it goes in there. --Redrose64 🦌 (talk) 19:05, 4 January 2025 (UTC)[reply]

Great, that sounds like what I am seeking. Thank you! Zinnober9 (talk) 19:18, 4 January 2025 (UTC)[reply]

Here's an example edit that I do all the time, typically for uncategorized, undocumented templates. Make sure to put the noinclude tag immediately after the template content, on the same line, and then start the documentation template on the next line. Creating a documentation subpage is better, but that can be done in a subsequent edit without breaking anything (and a select few editors really don't like separate /doc pages for certain template types, and I got tired of trying to persuade them otherwise). – Jonesey95 (talk) 15:59, 7 January 2025 (UTC)[reply]

Dusky dolphin

Hello, I just submitted the article to FAC. Would you be able to clean up the formatting of the references. Thank you. LittleJerry (talk) 16:43, 7 January 2025 (UTC)[reply]

Done. Happy to do it. – Jonesey95 (talk) 20:57, 7 January 2025 (UTC)[reply]

Template:The Popular User Award

Please leave the template like that, unless you will cause an edit war. Raph Williams65 (talk) 22:50, 7 January 2025 (UTC)[reply]

If you want to experiment with broken syntax, please do so in your own User space. The page was showing up on multiple error reports; we are trying to keep template space free of syntax errors. – Jonesey95 (talk) 22:51, 7 January 2025 (UTC)[reply]

Education by force?

Hello and thank you for your edit to my user page. As you noted, I do mind, and I would have preferred you educate me about the topic of "linter errors" which I had never heard of before, with a comment on said page rather than editing my page for me. I find this weird.

Good day.

Kether83 (talk) 15:04, 8 January 2025 (UTC)[reply]

That is why I linked to the Special page in my edit summary; you can learn all about Linter syntax errors from there. The specific errors on your page were obsolete <strike>...</strike> tags and an unclosed <p> tag; the rendering of your user page should not have changed at all. With three million errors to fix, prior notification would cause far too much noise on editors' talk pages and on their watchlists. – Jonesey95 (talk) 15:47, 8 January 2025 (UTC)[reply]

Template:Today in AD and AH (and AM and SH)

And for your net trick, by any chance are you up for rewriting these templates as navbars? (because, in sidebar form, they are not displayed to the large majority of visitors). 𝕁𝕄𝔽 (talk) 17:26, 8 January 2025 (UTC)[reply]

{{Infobox calendar date today}} would probably do, though it would be better if it had the option to suppress irrelevant calendars?

let's keep the discussion in one place: user talk:Gonnym#template:Infobox calendar date today --𝕁𝕄𝔽 (talk) 19:23, 8 January 2025 (UTC)[reply]

I don't know how {{navbar}} would be useful in this context. It is used in some of the templates, but "rewriting these templates as navbars" does not make sense to me. If you meant {{navbox}}, that template is not visible on mobile either.

I don't have an opinion on rewriting them or using a different base template. My main interest was in moving them to reasonable names so that they were not improperly stored as subpages of a redirect. – Jonesey95 (talk) 20:28, 8 January 2025 (UTC)[reply]

Yes, navbox, sorry. And I didn't realise that they are suppressed too.

. 𝕁𝕄𝔽 (talk) 21:31, 8 January 2025 (UTC)[reply]

Red Links

Why are red links okay? Esagurton (talk) 14:56, 16 January 2025 (UTC)[reply]

I linked to Wikipedia:Red link on your talk page. You removed my message, which is an acknowledgement that you have read the message and are aware of its contents (see WP:REMOVED for more details). Please read Wikipedia:Red link. – Jonesey95 (talk) 17:04, 16 January 2025 (UTC)[reply]

Discussion about "Label" or "distributor"

Hi. The discussion remains no further comment since last year. If you're interested, feel free to give your input, as well as Simplifying "Release history" tables discussion. 2001:D08:2951:5D13:181B:6FF1:4587:5831 (talk) 09:16, 17 January 2025 (UTC)[reply]

Query about Edit to the Kaiserreich Wiki on August 14th regarding a Linter error-detection bug

Hi Jonesey95, it appears as if you edited our "Box" template back in August of last year, seeking to work around a Linter error detection bug - judging by the username and note left with the edit. Unfortunately the edit broke the template, presumably unintentionally. Frankly the matter of Linter errors is above my head, but instead of just undoing the edit I'm reaching out in the hopes of there being a way to both fix the page and avoid the error. We'd appreciate it if you could fix the page, otherwise I'll just undo the edit. Here's the template page in question: https://kaiserreich.fandom.com/wiki/Template:Box. Thanks, Flamefang (talk) 03:47, 18 January 2025 (UTC)[reply]

I'm pretty sure that I have never visited that wiki. My guess is that my edit was included as attribution when that page was imported from another wiki. Ask the technical people at that wiki what "w:c:kaiserreich>Jonesey95‎" means in the edit summary; that might help you track down the source of the edit, and it may also help you determine if that page has dependencies that need to be imported or modified. – Jonesey95 (talk) 05:55, 18 January 2025 (UTC)[reply]

Judging by the page history the edit in question is https://kaiserreich.fandom.com/wiki/Template:Box?diff=42159&oldid=39750 the time, date and edit summary of which correspond exactly with our https://en.wikipedia.org/w/index.php?title=Template:Box&diff=prev&oldid=1240325678 so it's definitely imported from here to fandom. As for "w:c:kaiserreich>Jonesey95", this is a link to the non-existent user page, required for attribution under CC BY-SA. Some of the people at WP:VPT should be able to explain its format, but the "kaiserreich" part definitely indicates the specific domain within Fandom, and "Jonesey95" is of course yourself. I would say that if Fandom choose to import pages from Wikipedia, the imported page becomes Fandom's maintenance burden, not ours. --Redrose64 🌹 (talk) 15:12, 18 January 2025 (UTC)[reply]

Taking you up on the lint thing again

Hi. I'm back! Can you give this mass message a once over for errors? I am hoping to get it out ASAP. Thank you! Julie JSFarman (talk) 02:35, 20 January 2025 (UTC)[reply]

Done. Thanks for asking. – Jonesey95 (talk) 03:01, 20 January 2025 (UTC)[reply]

I may have messed it up in my constant tweaking. I got a message saying there was a linter error before I hit send. Would you mind giving it another check? (Sorry and thanks again.) JSFarman (talk) 20:01, 20 January 2025 (UTC)[reply]

Done; I have my Lint-checker set up to ignore a buggy condition that the mass message system still checks. I also tweaked the image to make it look nicer (IMO); feel free to undo that part. – Jonesey95 (talk) 22:05, 20 January 2025 (UTC)[reply]

Message sent! It looks so much better. Thank you x 100000000! JSFarman (talk) 22:42, 20 January 2025 (UTC)[reply]

Humpback

Hello. Sorry I interrupted your CE, I'm done for now. LittleJerry (talk) 23:53, 21 January 2025 (UTC)[reply]

No worries. I've been doing bits of it at a time. – Jonesey95 (talk) 01:07, 22 January 2025 (UTC)[reply]

How does my edit broke the template?

Hi

You can see the same edit in other template in category section. Like {{Infobox tectonic plate/doc}}. Shkuru Afshar (talk) 21:09, 23 January 2025 (UTC)[reply]

Compare

and

Why my text breaks the category? Although they have the same structure.

cannot break categories as it is on the top of the page.

"" makes them comments. So, they should have no effect. Shkuru Afshar (talk) 21:28, 23 January 2025 (UTC)[reply]

You removed a pipe, which removed categories from the template. Please edit carefully. – Jonesey95 (talk) 00:03, 24 January 2025 (UTC)[reply]

Also, your edit to infobox tectonic plate/doc had a typo in it, which I fixed. Please preview and check the results of your edits. – Jonesey95 (talk) 00:07, 24 January 2025 (UTC)[reply]

January 2025 GOCE drive award

		The Working Wikipedian's Barnstar
		This barnstar is awarded to Jonesey95 for copy edits totaling over 8,000 words (including bonus and rollover words) during the GOCE January 2025 Backlog Elimination Drive. Congratulations, and thank you for your contributions! Dhtwiki (talk) 12:02, 3 February 2025 (UTC)[reply]

Sportsperson infobox

The infobox now shows the medal template as purple after your change. Could you fix it? MarqueesCalaway (talk) 20:40, 3 February 2025 (UTC)[reply]

When reporting a problem, always link to an example page. I am looking at Template:Infobox_sportsperson#Examples in both regular and dark mode, and it looks fine. – Jonesey95 (talk) 23:58, 3 February 2025 (UTC)[reply]

Yes but in this case, Bryan Snyder, people use different colors to show college/professional teams and however you changed the template made it to where these colors no longer change. MarqueesCalaway (talk) 02:05, 4 February 2025 (UTC)[reply]

Thank you for linking to an example. That helped me figure out the interaction between the two infobox templates. I think the problem is fixed now, but if you notice any other articles that are not working right, please contact me. Thanks. – Jonesey95 (talk) 06:46, 4 February 2025 (UTC)[reply]

I believe the issues is fixed. I do see the show and hide button do not change colors now, but that can be overlooked. Thank you. MarqueesCalaway (talk) 13:58, 4 February 2025 (UTC)[reply]

Infobox neighborhood quarter

Re [1]: I considered Template:Infobox settlement but it is unusable. Hawkeye7 (discuss) 01:31, 4 February 2025 (UTC)[reply]

We'll see. I suspect it would work just fine. Feel free to link to a sandbox or draft page where you are trying to use this new template or trying to translate the French template. I think we can make Infobox settlement work. – Jonesey95 (talk) 01:36, 4 February 2025 (UTC)[reply]

Here's a Sandbox mock-up. Hawkeye7 (discuss) 02:55, 4 February 2025 (UTC)[reply]

I've gotten it pretty close. If you turn Infobox quarter into a wrapper for infobox settlement, you should be able to style it as you please. – Jonesey95 (talk) 07:00, 4 February 2025 (UTC)[reply]

Thank you! It seems very odd to have the map at the top when it is conventionally at the bottom. (I am curious as to what created the blue bar above the module.) I have to be prepared to defend the use of Template:Infobox settlement when the article comes up for review. Hawkeye7 (discuss) 20:55, 4 February 2025 (UTC)[reply]

The blue bar above the module is due to my clumsy hacking of {{Infobox public transit/sandbox}} for use as a child module; it was not set up for that purpose and needs some refinement. I'm not sure what you mean about the map placement; if you look at Paris or Vienna or any other settlement article, the map is near the top of the infobox, before the labeled items. – Jonesey95 (talk) 00:44, 5 February 2025 (UTC)[reply]

The French version of Paris has the map down the bottom. Hawkeye7 (discuss) 01:24, 5 February 2025 (UTC)[reply]

OK. When you said "conventionally at the bottom", I thought you meant here at the English Wikipedia, where this discussion is happening. – Jonesey95 (talk) 05:35, 5 February 2025 (UTC)[reply]

Thanks for your help. Hawkeye7 (discuss) 19:07, 7 February 2025 (UTC)[reply]

Module Gallery

Do you know if this edit might have broken the template Gallery on 300+ pages? Something's messing with the alts and the timing's about right. Zinnober9 (talk) 04:50, 7 February 2025 (UTC)[reply]

It appears to have broken the use of {{FIAV}}. – Jonesey95 (talk) 14:40, 7 February 2025 (UTC)[reply]

I've messaged that editor. Still not sure how what they changed is causing the error, but hopefully FIAV/alt usage is enough to identify the issue and be fixed. Thanks, Zinnober9 (talk) 16:29, 7 February 2025 (UTC)[reply]

Resolved. Zinnober9 (talk) 21:02, 7 February 2025 (UTC)[reply]

Why that revert version over another? I see the conversation at Template_talk:Gallery#Caption_not_accepting_external_links, so I realize there's other issues at play, but I'm just surprised you reverted to the version with these 300+ errors, and not one further back without. Did Arthurfragoso fix something more majorly seen and undoing that was less desirable? Zinnober9 (talk) 03:25, 10 February 2025 (UTC)[reply]

I just went farther back and will let Arthurfragoso figure it out with the help of the new testcases. – Jonesey95 (talk) 03:29, 10 February 2025 (UTC)[reply]

Ok. I hope there's a simple solution and wish Arthurfragoso/anyone else figuring out these updates to Gallery good luck.

A little unrelated but since we are talking, it's looking like HTML5-incompatible misnesting errors will be nearly all addressed and eliminated by this time next week or next. Exciting to have the Higher priority errors nearly all gone!! According to Wayback it looks like we had about 40-50k High priority errors in late 2022 when I started joining in on this project. Progress!! :) Zinnober9 (talk) 04:59, 10 February 2025 (UTC)[reply]

Indeed. I have been chipping away at them over the past few months. They are mostly one-by-one errors, but sometimes I find a batch of 5 to 30 identical ones that I can process quickly. – Jonesey95 (talk) 05:00, 10 February 2025 (UTC)[reply]

Infobox settlement/doc

Per your edit, the text "variation of the US" is too vague, does it mean "USA" or "United States" or something else? Please clarify this documentation. Thanks!!!! • Sbmeirow • Talk • 06:44, 8 February 2025 (UTC)[reply]

Done. The code is in {{Infobox settlement/pref}}. – Jonesey95 (talk) 07:12, 8 February 2025 (UTC)[reply]

Module:Routemap

I added a meters-to-feet conversion to the {{BScvt}} subsection, but I can't figure out how to change m2f to just m in the output. Thanks in advance for your help. Useddenim (talk) 18:03, 11 February 2025 (UTC)[reply]

It looks like the next step is to add one or more testcases at {{BSsplit/testcases}}. Once I see what you are trying to do, I may be able to tweak the code to get the output you want. – Jonesey95 (talk) 21:31, 11 February 2025 (UTC)[reply]

Never mind. You don't need new code. This is what you need: {{BScvt|150|in=ft|x}} →

150 m

490 ft

– Jonesey95 (talk) 21:39, 11 February 2025 (UTC)[reply]

No, that's ↑ not it. Currently {{BScvt}} converts metres to yards, which it appropriate for the lengths of tunnels and bridges, but I also want the option of metres to feet (the standard measure of elevations).

{{BScvt|100|in=m}} →

100 m

109 yd

{{BScvt|100|in=m2f}} →

100 mi

161 km

but the output should display "m", not "m2f". Useddenim (talk) 00:38, 12 February 2025 (UTC)[reply]

See above. 150 m, 490 ft. That is the output you are requesting, you just have to ask for it in a backwards way, per the template's rather limited documentation. – Jonesey95 (talk) 01:38, 12 February 2025 (UTC)[reply]

You don't seem to be getting it. |in=feet converts feet to metres. When |in=m is specified, metres is converted to yards. I want to also be able to convert metres to feet. Useddenim (talk) 02:29, 12 February 2025 (UTC)[reply]

Maybe I am misreading this: {{BScvt|150|in=ft|x}} →

150 m

490 ft

. As far as I can tell, that is taking 150 m as an input and outputting 490 ft. The unnamed parameter tells the template to do the reverse of what it would normally do: show the ft/m conversion, but read the number as meters and do a m/ft conversion. If that is not what is happening, it would be great if you or someone else would explain what is happening there. – Jonesey95 (talk) 05:56, 12 February 2025 (UTC)[reply]

You're right. It seems that the code was significantly rewritten when it was converted to Lua and merged into the Routemap module. Useddenim (talk) 15:03, 12 February 2025 (UTC)[reply]

Infobox pharaoh

https://en.wikipedia.org/wiki/Menkauhor_Kaiu

Thanks for undoing my change - can you suggest an alternative to div then? The `center` template perhaps? The inconsistency in these infoboxes is driving me insane. I wish the data within them was actually coherent so that the information can be used outside of a visual context. 2A00:23C8:2433:8F01:6C6E:36B9:8A2C:7AB9 (talk) 12:41, 17 February 2025 (UTC)[reply]

What is your goal? The div tags appear to be working fine. – Jonesey95 (talk) 14:41, 17 February 2025 (UTC)[reply]

Dusky dolphin

Hello. Would you be able to make sure the source formatting is consistant? Thank you. LittleJerry (talk) 14:03, 18 February 2025 (UTC)[reply]

Done. – Jonesey95 (talk) 15:26, 18 February 2025 (UTC)[reply]

Insource searches

Is there an existing cheat sheet/guide for insource searching syntax? Wanted to see if I could do a search with a "font face" closer, but haven't been able to get that to work. Signatures I've gotten to work and submitted so far have been mostly from copying and adjusting from similarly built existing searches from the sig sub page, but I keep running into font faces. Would like to build up my insource search term syntax knowledge so I'm better at free handing it rather treating them all as than fill in the blanks and praying it works. Zinnober9 (talk) 22:58, 20 February 2025 (UTC)[reply]

Try this somewhat technical page first: Help:Searching/Regex. If that is gibberish to you, paste an example here of what you want to search for, and I'll use it as an example to show you how to search for it. Use <syntaxhighlight>...</syntaxhighlight> tags to wrap your example code. – Jonesey95 (talk) 01:42, 21 February 2025 (UTC)[reply]

I had found

<font face="Viner Hand ITC" color="2F4F4F">'''Ed [[User:the_ed17/Newcomers|<font color="000080">17</font>]] [[User talk:the_ed17|<font color="2F4F4F">for President</font>]]  <sub>''[[User:the_ed17/Vote|<font color="2F4F4F">Vote for Ed</font>]]''</sub></font face color>'''

and I've seen ed17 often on various pages (but with varying sigs), so thought it was worth trying to search for the phrase

 >Ed</font>]]''</sub></font face color>'''

(or something similar) to see if it were worth adding but had something off with this search . I'm not seeing the adjustment I need at this moment from that help page but rather sure it was in the font face portion since this also was invalid. Will look at the help page some more tomorrow, but a working case would be great if it suits you. I had found this sig on User:The ed17/Archives/9/A, but cleared that earlier. Just in case that were the last page with it, I've temporarily stuck it on my sandbox so there's one result to find. Zinnober9 (talk) 02:54, 21 February 2025 (UTC)[reply]

You have a stray > character at the start of the second string that does not appear in the first one. In your linked search, you also put an extra \ at the end of the search string. Once you remove those, you only need to put a backslash in front of each metacharacter:

insource:/Ed\<\/font>\]\]\'\'\<\/sub>\<\/font face color>\'\'\'/

The metacharacters that need to be preceded by \ in insource search strings are

 . + * ? | { [ ] ( ) " \ # @ < ~

The syntax is very picky. If you make one little error, you may not get the results you want. Come back for help any time. And for bonus fun, here's a broader search for "</font face color>" – Jonesey95 (talk) 03:25, 21 February 2025 (UTC)[reply]

Thank you! I had thought it had been something awkward with having a two/three word tag, but no, the usual nemesis "extra \" strikes again. I see from correcting those searches that this wasn't as fruitful a sig search as I'd hoped I was finding. I'll hit those manually since 10 pages or fewer. Yesterday's bigger finds and the knowledge from this conversation make up for it though. Thanks, Zinnober9 (talk) 21:06, 21 February 2025 (UTC)[reply]

2025

@Jonesey95 Can you please clarify the edits you reverted in List of political parties in India? What is the problem with the template nowrap? Was the table not looking better in the previous revision? XYZ 250706 (talk) 05:23, 24 February 2025 (UTC)[reply]

As far as I know, I did not revert any edits at that article. I removed content that was causing syntax errors. {{Nowrap}} is an inline template that can't be used on block content. In other words, it can't be used around content that has line breaks (multiple lines) in it. Doing so causes a syntax error. As its documentation indicates, nowrap should be used sparingly. If you decide to use it, make sure its content does not contain any line breaks or other block content. That may mean enclosing individual lines or small strings of text rather than whole sections. – Jonesey95 (talk) 05:29, 24 February 2025 (UTC)[reply]

February 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 February 2025 Copy Editing Blitz. Congratulations, and thank you for your contributions! Miniapolis 18:24, 24 February 2025 (UTC)[reply]

Dash spacing for Michelin Chicago

You recently had an edit on the List of Michelin-starred restaurants in Chicago where you made a small change to dash spacing. Do you have the MOS that refers to this change. I'd like to add it to the Michelin Guide style guide. Thanks. Expandinglight5 (talk) 18:29, 24 February 2025 (UTC)[reply]

I think MOS:YEARRANGE is what you are looking for. – Jonesey95 (talk) 19:58, 24 February 2025 (UTC)[reply]

Edit summary comment

Hi - re this edit summary, when I source code edit I use the toolbar option for striking text; the problem (?) appears to be with the toolbar. If you're aware of a better, automated way to strike text, am all ears, although I see no visual difference in the changes you made. If there's a particular legacy issue, again, would appreciate being pointed in the direction of an MoS guideline or some such. FWIW neither Help:Wikitext#Strikethrough nor Help:HTML_in_wikitext#s make mention of a problem using <s>...</s>. Thanks and regards, Goldsztajn (talk) 02:23, 25 February 2025 (UTC)[reply]

Thanks for those links. I'm surprised that nobody had updated those pages since Linter tag misnesting started being flagged by the MediaWiki software seven years ago. I have done so now. If you want to use the toolbar's <s>...</s> tag insertion method, you could select each line of text individually, which should give you results like those in this edit. Pinging Left guide and PhilKnight, who may also benefit from these links. – Jonesey95 (talk) 05:09, 25 February 2025 (UTC)[reply]

Goldsztajn (talk) 06:37, 25 February 2025 (UTC)[reply]

Dusky dolphin again

Hello, I plan on renominating the article soon. Does the prose look okay? LittleJerry (talk) 16:25, 25 February 2025 (UTC)[reply]

When I stopped by to tidy the citations, it looked like someone had done a nice copy edit. I see that it is on the GOCE Requests list. Someone, possibly me, will get to it relatively soon. – Jonesey95 (talk) 16:28, 25 February 2025 (UTC)[reply]

2022 Italian election

Why did you undo my changes by removing the maps I had inserted? Scia Della Cometa (talk) 22:15, 25 February 2025 (UTC)[reply]

You removed table captions, which are required for accessibility, and left unmatched div tags. It looked like a disruptive edit to me. Please be more careful. – Jonesey95 (talk) 22:17, 25 February 2025 (UTC)[reply]

Ok, but it was enough to correct my mistake, it was clear that it was not a disruptive edit...--Scia Della Cometa (talk) 22:24, 25 February 2025 (UTC)[reply]

Since your edit had so many errors and changes, it was not clear what your intention was. Reverting was the cleanest way to give you a chance to implement the changes in the way you want, while ensuring that the syntax is balanced and the page complies with MOS. – Jonesey95 (talk) 22:26, 25 February 2025 (UTC)[reply]

Ok, I should have fixed it anyway.--Scia Della Cometa (talk) 22:29, 25 February 2025 (UTC)[reply]

Guild of Copy Editors 2024 Annual Report

Guild of Copy Editors Annual Report

Our 2024 Annual Report is now ready for review.

Highlights:

Introduction
Membership news and election results
Summary of Drives, Blitzes and the Requests page
Closing words

– Your Guild coordinators

To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

Sent by MediaWiki message delivery (talk) 06:36, 2 March 2025 (UTC)[reply]

Obsolete tags in sigs

It's been a year since this comment. Has this happened? WhatamIdoing (talk) 23:31, 3 March 2025 (UTC)[reply]

Has what happened? It looks like blocking the saving of obsolete tags in signatures was implemented. Have you seen evidence to the contrary? If that's not what you're asking about, what are you asking? – Jonesey95 (talk) 03:56, 4 March 2025 (UTC)[reply]

Have we moved on to the next step, so that sigs with obsolete tags won't be posted? WhatamIdoing (talk) 16:37, 4 March 2025 (UTC)[reply]

I'm pretty sure that there is a general consensus against preventing people from publishing invalid syntax, including signatures. We might be able to do something about people's custom signatures that have invalid text, though, if any still exist (it looks like they do). There was a discussion somewhere about having a bot go through and delete broken custom signatures after notifying the affected editors; I do not recall the details. Have you come across any recent (posted in 2024, for example) signatures with Linter errors in them? – Jonesey95 (talk) 20:18, 4 March 2025 (UTC)[reply]

I haven't paid attention to the sigs; I just ran across the old discussion and wondered whether the process had been finished. WhatamIdoing (talk) 20:41, 4 March 2025 (UTC)[reply]

User:JamJamSvn

Good work on User:JamJamSvn using {{User:Ilikepie2221/UBX/MadeArticles|...|nolink=yes}}. I couldn't figure this one out. The user then fixed it another way restoring the link. —Anomalocaris (talk) 08:05, 5 March 2025 (UTC)[reply]

That works. – Jonesey95 (talk) 14:06, 5 March 2025 (UTC)[reply]

Thanks both of you. Sorry if I disrupted anything! JamJamSvn (talk) 14:53, 5 March 2025 (UTC)[reply]

Move needed Talk:Lat (cartoonist)/Long (CSI: NY)

If you can, please move Talk:Lat (cartoonist)/Long (CSI: NY) to Talk: Lat/Long (CSI: NY) without leaving a redirect. Gonnym (talk) 15:51, 5 March 2025 (UTC)[reply]

Done. Pages with slashes in the name are odd birds. – Jonesey95 (talk) 15:56, 5 March 2025 (UTC)[reply]

Could you also move Talk:Text Adventure Development System/PNVS back to Talk:TADS/PNVS? Gonnym (talk) 14:31, 9 March 2025 (UTC)[reply]

And Talk:Gulf (disambiguation)/2000 Project to Talk:Gulf/2000 Project. Thanks! Gonnym (talk) 14:45, 9 March 2025 (UTC)[reply]

Update

https://en.m.wikipedia.org/w/index.php?title=User:Johnj1995&action=edit&redlink=1

https://en.m.wikipedia.org/wiki/Draft:Huskies_de_Rouen

someone very similar to your name here ☝️ 93.140.113.64 (talk) 06:20, 6 March 2025 (UTC)[reply]

ARTM bus terminals

I spent a lot of time these last few days updating the pages of Montreal metropolitan bus terminals which were displaying incorrect information for years.

I edited lots of info which took hours. The list of terminals can be found here at Annex 1: https://www.artm.quebec/wp-content/uploads/2024/02/2521_ARTM_Corpo_PDI_2024_WEB_V4.pdf all the bus lines on each page are the correct ones.

I understand the need for references and edit summaries but before reverting my edit you could ask for more sources next time. Mtlfiredude (talk) 22:01, 12 March 2025 (UTC)[reply]

Please use an edit summary for every edit. Also, creating {{ARTM bus terminal}} when an appropriate template already existed was not a good look. And you broke the |name= parameter. Please be more careful. – Jonesey95 (talk) 23:12, 12 March 2025 (UTC)[reply]

Ok, what I wanted to do was change the template name “Exo bus” to “ARTM bus terminal” to reflect the changes.

Anyhow, I will be more careful, thanks. Mtlfiredude (talk) 11:15, 13 March 2025 (UTC)[reply]

Why? The relevant article title is Exo (public transit). The buses say "Exo" on the side. – Jonesey95 (talk) 14:12, 13 March 2025 (UTC)[reply]

ARTM is the transit authority, Exo is a transit operator. Exo does not own that infrastructure, so they’re not « Exo bus terminals », they belong to the ARTM. Mtlfiredude (talk) 12:25, 17 March 2025 (UTC)[reply]

Your argument is not with me; it's with the consensus about the article's title and the common name that is used to describe the places. If reliable sources call these places ARTM bus terminals, then your name changes make sense. If sources call them Exo bus terminals, then calling them ARTM terminals on Wikipedia goes against our guidelines. I recommend that you discuss it at the talk page for the article. – Jonesey95 (talk) 12:58, 17 March 2025 (UTC)[reply]

Will do Mtlfiredude (talk) 02:43, 21 March 2025 (UTC)[reply]

Template:Transl

Numerous articles utilize this template, and the present presentation of these articles are mess due to your alterations. Can the prior model be reinstated? TinaLees-Jones (talk) 00:38, 14 March 2025 (UTC)[reply]

Sorry for making it worse before I made it better. Numerous articles were very broken because of an undocumented RfD template that was placed on that page. I have fixed the underlying code problem and restored the page to its previous state. If any pages are broken after you perform a null edit, please link to one, and I will take a look. – Jonesey95 (talk) 00:42, 14 March 2025 (UTC)[reply]

Hellenic Police: dashes

You edited Hellenic Police changing hyphens to en dashes, for example, the en dash in the title in {{Cite web |title=Γενική Διεύθυνση Προστασίας Επισήμων και Ευπαθών Στόχων – Ελληνική Αστυνομία |url=https://www.astynomia.gr/elliniki-astynomia/eidikes-ypiresies/geniki-diefthynsi-prostasias-episimon-kai-efpathon-stochon/ |access-date=October 29, 2024 |website=astynomia.gr}}. If you are aware of clear guidance on this, please let me know. My view is that punctuation in non-English languages should mostly be preserved. However, if the original script is Latin or Greek, I will usually change curly quotes and apostrophes to straight quotes and apostrophes, and nested quotes (including in article titles) to single. I don't change quotes and apostrophes around in Arabic, Korean, or other scripts. In Arabic I am especially reluctant because I assume that curly single quotes imply an Arabic character. And I assume that most languages don't necessarily use en dash and em dash as we do, so when I copy an article title or proper noun from a non-English source, I leave the hyphens and don't convert to the dash that we would use in English. Again, if you can point to guidance on this, I'd like to see it.

But composing this message leads me to actually try out the URL. Lo and behold, the actual page title is just "Γενική Διεύθυνση Προστασίας Επισήμων και Ευπαθών Στόχων"; "Ελληνική Αστυνομία" is the website. So that means probably all of the page titles need to end before the dash. And the page summary needs to say so, and there should probably be a message on someone's talk page saying, please list page title as just the article title, append the website name. —Anomalocaris (talk) 01:30, 17 March 2025 (UTC)[reply]

Fixed Hellenic Police to remove many occurrences of "– Ελληνική Αστυνομία" from article titles and insert instead |publisher=Hellenic Police. Found the culprit: same editor as who kept reverting you, added a comment on their talk page. —Anomalocaris (talk) 02:06, 17 March 2025 (UTC)[reply]

Nice work with removing the web site titles. If I am so inclined, I generally change citation titles to match MOS, including changing spaced hyphens to spaced dashes. See MOS:CONFORM, which is about quotations, but I think the same principles apply, as we are essentially quoting the title of something. I also change titles like "Bill Smith : Medal of Honor" to remove the space before the colon (MOS:COLON: "no space should precede a colon"); I see that construction in French titles, mostly. I don't see a problem with tidying bits like this to make our pages consistent with respect to MOS. – Jonesey95 (talk) 02:43, 17 March 2025 (UTC)[reply]

OK, so if you find some web page with a title "Celebration July 6-7" do you mark it up as |title=Celebration July 6–7 with an en dash? —Anomalocaris (talk) 04:28, 17 March 2025 (UTC)[reply]

Definitely. – Jonesey95 (talk) 12:59, 17 March 2025 (UTC)[reply]

OK, do you change |title=Citing 'lost faith,' pastor quits to |title=Citing 'lost faith', pastor quits?

Generally not, but only because I don't notice those. I have no objection to the change. – Jonesey95 (talk) 20:47, 17 March 2025 (UTC)[reply]