User talk:Jonesey95 is a topic that has captured the attention of people of all ages and backgrounds in recent years. Since its emergence, it has aroused unprecedented interest and generated debates in all areas. As it has evolved, it has managed to cross borders and has influenced the way people think, act and relate. In this article, we will explore the different aspects of User talk:Jonesey95 and its impact on society today, as well as the possible repercussions it may have in the future.
This page has archives. Sections older than 90 days may be automatically archived by Lowercase sigmabot III 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)
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)
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)
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.
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)
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)
{{Infobox calendar date today}} would probably do, though it would be better if it had the option to suppress irrelevant calendars?
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)
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.comhttps://bestencyclopedia.com/Template:Box. Thanks, Flamefang (talk) 03:47, 18 January 2025 (UTC)
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)
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)
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)
<!-- Categories below this line and interwikis at Wikidata, Thanks -->
and
<!-- Categories below this line, please; interwikis at Wikidata -->
Why my text breaks the category? Although they have the same structure.
<!-- Please place categories where indicated at the bottom of this page and interwikis at Wikidata (see ]) --> cannot break categories as it is on the top of the page.
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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).
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)
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)
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)
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)
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)
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)
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)
I had found
<font face="Viner Hand ITC" color="2F4F4F">'''Ed ] ] <sub>'']''</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)
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
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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 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)
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)
Ok, what I wanted to do was change the template name “Exo bus” to “ARTM bus terminal” to reflect the changes.
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)
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)
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)
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)
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)
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)
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)
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)
@Anomalocaris: Lurker here. Re the hyphen, people often join bits of web pages and such into titles, quite often with a spaced hyphen between them. But the spaced hyphen is an abomination, imho, with no role in proper orthography, English or otherwise. I often do a global replace of spaced hyphen to spaced en dash, then go back and fix the file names, because that's one place where the practice is common and not so easy to fix. In ref titles, made up or otherwise, I don't see a reason to ever tolerate spaced hyphens. It's basically just the lazy typist's way of indicating a dash. Dicklyon (talk) 16:57, 31 March 2025 (UTC)
Template link
That template link you added here is very handy, since that's often where the most important fixes are to be found. But it would be so much more useful if it was only there when the list of linking templates is not empty. I expect you know that already, so I suppose it's not so easy to conditionalize it that way. Thanks for all you do. Dicklyon (talk) 16:50, 31 March 2025 (UTC)
I suppose it would be not too hard to make a bot that would go through the items on this report and filter them by various criteria into other reports. I might know a bot writer would could take that on. Dicklyon (talk) 15:51, 1 April 2025 (UTC)
Hey Jonesey, reaching out regarding this edit. Is the perspective that we need to include the full name? I figured it'd be acceptable and easy to understand if simply "WrestleMania" was included instead of "WrestleMania 22". Hey man im josh (talk) 17:43, 1 April 2025 (UTC)
I think that's how it's supposed to work. The documentation for the template says The name of this redirect, correctly capitalised, if it differs from the redirect target. It appears that you can also leave |1= out entirely, which may be the easiest thing to do. – Jonesey95 (talk) 17:46, 1 April 2025 (UTC)
Hmmm, I see. Tried to keep things simple, and while I personally think it should, in idea, be acceptable, I'll be mindful of being more accurate with the full title moving forward. You would think though that the parameter would then be unnecessary if it was simply meant to match the target. Hey man im josh (talk) 18:00, 1 April 2025 (UTC)
Jonesey
I...just have to ask, since I first saw you on the Charlotte County Islands template (which is under construction, thanks; problem is there's 100+ islands which would overwhelm the general NB talkpage)...are you the Jonesey of S Cove? Because hilarious if so! Fundy Isles Historian - J (talk) 19:59, 1 April 2025 (UTC)
Nope, that must be someone else. That template popped up on one of my error reports, which is why I came to fix it. If you decide to restore the template after making articles for all 100+ islands, please check all of the links; some of them were pointing to islands that are not in New Brunswick. – Jonesey95 (talk) 23:05, 1 April 2025 (UTC)