It would be great if all or some of this can be done using the tool, would save a lot of time. Manually adding the row and data, would be the last option. Also ping @MPGuy2824 --Venkat TL (talk) 18:22, 14 September 2022 (UTC)
Brookfield Properties
I was encouraged to post here by User:Epicgenius. Brookfield Properties (my employer) was known as "Brookfield Office Properties" from 2011-2017, and as a result there are still many articles that refer to the company that way even though the company is now known only as "Brookfield Properties." Epicgenius showed me these search results showing instances of "Brookfield Office Properties" in articles, all of which should be changed to "Brookfield Properties" except for historical references and appearances of the term within references.
Similarly, GGP Inc. was acquired by Brookfield in 2018, and was then known as "Brookfield Properties Retail Group" for a period of time after that. But now the retail group no longer exists as its own company, but only as a group within Brookfield Properties. So all instances of "Brookfield Properties Retail Group" currently appearing in articles (as shown in these search results) should be changed to "Brookfield Properties," except for historical references and appearances within references.
Finally, the same goes for another old name, "Brookfield Properties Corporation" (search results here), though there are only a small handful of examples of this case that are not historical.
I would be happy to assist whoever steps up here in identifying which instances are historical and thus should not be changed (in most cases it's obvious from context). Thank you! Claudiailagan (talk) 11:44, 24 August 2022 (UTC)
Hi everyone. I see that my request may have demanded too much legwork on the part of the regular editors here, so I created a userspace draft with a simple list of all the articles that need to be fixed, at User:Claudiailagan/Brookfield Properties naming errors. (I already weeded out all the historical references to the three old names for Brookfield Properties, where no correction is necessary.) I would greatly appreciate someone helping carry out this task, or at least letting me know if further work is necessary on my part. Thank you, Claudiailagan (talk) 20:23, 12 September 2022 (UTC)
Hi Claudiailagan, I'll assist you here however rather than attempting to do this with AWB, pick off say a couple a day, manually. I see that you have been revising a few yourself. Would you please strike-through any on your list page if already attended to. Do you have a link to any commercial material/website that confirms business naming? Neils51 (talk) 10:26, 14 September 2022 (UTC)
I don't know if this is a bot request or an AWB request, but I thought I would start here. There are over 1,000 pages that use span tags with hex colors missing the # symbol. They look like <span style="color:0099FF">, but they should look like <span style="color:#0099FF"> (note the # symbol). Some of these are due to bad edits by a regex I used to employ, but there are many others.
Is there anyone here willing to sweep through these articles and add the missing # symbols? It will result in editors' color preferences for text being displayed as intended. I have been able to fix these problems semi-automatically with code like: str = str.replace(/(\<span style\=\"color:)([a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9])/gi, '$1\#$2'); but you may have a better regex. As far as I know, there are no valid color names expressed as words that contain six a–f characters in a row, so the above regex should be safe. – Jonesey95 (talk) 16:15, 20 July 2022 (UTC)
Of the search results, only two are in the article space. Some of the other results are actually part of a user signature, which I guess we are not going to edit (Talk:Internet_Watch_Foundation_and_Wikipedia signature of user Celarnor). The two articles can be edited manually. For the others, I am not sure. Considering they are not in the article space, should we leave them as they are? Vpab15 (talk) 16:43, 20 July 2022 (UTC)
Some of them, possibly the majority, are the result of invalid conversion of font tags (without the #, which works) to span tags (which require the # to render a color) by myself and other editors cleaning up Linter errors. In those cases, it was the original intention of the editors to display the color, so fixing the span tag is the right thing to do. In cases where the span tags has always been like this, it was clearly the editor's intent to display a color, even if it didn't work right (or maybe it used to work?). I can go through and fix them myself if necessary, but I do not have access to AWB and cannot get it due to my OS, so I thought I would ask here first. – Jonesey95 (talk) 16:59, 20 July 2022 (UTC)
You are correct, there are no valid colors. I checked. I think it's supposed to rain in the morning, so I'll take a stab, I do agree with your point that it was how it was meant to be shown. Also, you mention OS. As a mac user, may I interest you in WP:JWB instead of AWB? Happy Editing--IAmChaos02:48, 21 July 2022 (UTC)
Thanks. I've had JWB on my to-take-a-look-at list for a while. I use AutoEd, which is good enough for most things, but it's not great for mass small edits because its workflow is a bit clunky. – Jonesey95 (talk) 04:26, 21 July 2022 (UTC)
I got namespaces 0 and 1 loaded and did A lot were signatures (bc it was talkspace) User:PenyulapUser:Blanchardb and User:Hansen Sebastian came up a lot I noticed, which may have been the conversions from <font> you mentioned earlier, as they were mostly older comments. I loaded just the first two namespaces due to loading times, but my final tally was Pages saved: 167; Null-edits: 2; Pages skipped: 24; Other: 0; . 26 that JWB didnt edit. I'll go back and look at them after I do the other namespaces. If anyone wants to take over the task before I get to it tonight or tomorrow - the regex I used is in a subpage of my userspace desk. Happy Editing--IAmChaos19:13, 21 July 2022 (UTC)
ns 2&6 8 12 14 100 118 done. Saved 67 pages JWB didn't parse 13 with an edit. Most of those namespaces didnt even have any pages matching your search. I will go back and do talkspaces(including project and template. But I realized that the way I was doing it was only solving the first instance per page, so does anyone know how I can fix that? Happy Editing--IAmChaos04:21, 22 July 2022 (UTC)
@IAmChaos, add the RegEx flag 'g' for global. According to the search there are still ~1167 pages left, so I'll try to do them some time today. ― Qwerfjkltalk06:35, 22 July 2022 (UTC)
Just saying thank you for raising old AfDs. Seriously, not sarcastic as some raise with clean up edits. Super helpful to then un-watch list those that were before temporary watchlisting. And good luck with the actual purpose as well of course StarMississippi02:50, 22 July 2022 (UTC)
I have been working on these slowly, and other editors have dealt with a chunk of them as well, but the upgrade to a new version of search has meant more regex timeouts and worse search results (see VPT for discussion). There are at least 2,500 instances of just one editor's signature, and who knows how many more that are not this editor's signature. – Jonesey95 (talk) 16:08, 14 September 2022 (UTC)
I did a further 125 or so, until I realised that the disambiguation has been reverted. So, should I change the remainders? Not many remain though. —CX Zoom[he/him](let's talk • {C•X})14:35, 14 September 2022 (UTC)
At the moment, there seems to be ~183 instances of the misspelling "pubishersweekly.com" in articles. It seems to appear in both work and url parameters (or equivalents) of various citation templates, so preferably the incorrect URLs should be changed to publishersweekly.com, while the instances where it's used to indicate the publication's title should be changed to "Publishers Weekly". Thanks! Bridget(talk)23:54, 9 October 2022 (UTC)
A while back, I figured out that the automatic citation tool was generating this error with Publishers Weekly. I now know to manually replace the letter "l" in the url. Until someone figures out why this happens, you will continue to see this typo. Rublamb (talk) 17:07, 10 October 2022 (UTC)
Done - 22 of 23 "What links here (all NS)" pages converted. Editor of 23rd page notified (appears to be massive bot-generated list in userspace). VanIsaac, GHTVcontWpWS00:00, 14 October 2022 (UTC)
No, because its default value is no punctuation at all and it is a lot more intuitive that way (especially since people not completely familiar with the template might insert incorrect full stops everywere otherwise). 1234qwer1234qwer416:56, 29 November 2022 (UTC)
If anyone's up for this, try the regex (Population: \{\{Ua-pop-est2021\|[\d,]+)\}\}\. Carriage returns \r don't appear in wikitext, they are converted to \n (I think). — Qwerfjkltalk21:39, 29 November 2022 (UTC)
I hvae tested the template on .ir, .int and .press domain categories and it works fine no matter how many characters the domain has. all parent cats are added by the template plus the hatnote and enough description. Thanks JeeputerTalk15:56, 4 January 2023 (UTC)
De-linking circular redirects on stars and exoplanets
There are numerous articles where an exoplanet is a circular link to its host star, or vice versa. Due to the systematic naming conventions of exoplanet articles, nearly all cases can be de-linked by AWB with no false positives and at most a handful of false negatives.
Most star articles use a {{starbox begin}} template, and most exoplanet articles use {{infobox planet}}. Thus, we can use these templates as a proxy for articles about stars and exoplanets, respectively.
Exoplanet names consist of the host star appended with a lowercase Latin letter, starting with b for the first discovery around a star; there may or may not be an intermediate space. For example, the first planet discovered around 55 Cancri is 55 Cancri b. This naming convention is not used anywhere in the Solar System, so with {{infobox planet}} there should be no false-positive hits that are Solar System bodies.
In multiple star systems, an exoplanet's host star may be labeled by a capital letter; for example, 55 Cancri b may also be called 55 Cancri Ab, but like most multiple stars, 55 Cancri's article is about both A and B. Circumbinary planets like Kepler-16b are commonly referred to without the host stars' letters, but if they appear they would appear together in parentheses, in this case Kepler-16(AB)b.
A few stars have disambiguators that would need to be dropped, but the only star/planet pair I know where this would apply is Pollux (star)/Pollux b, both of which have standalone articles.
The links to be removed are planets which redirect back to the host star, or stars which redirect back to their planet, under the titles extrapolated from the article name using the above rules. Circular links caused by navigation boxes can be ignored; see Category:Exoplanet navigational boxes and Category:Constellation navigational boxes.
There should be zero false positives under the above assumptions except for other rare types of circular link, and the number of false negatives should be small enough that they can be remediated by hand.
generally, such link updates should be done before the page moves. After moves, it usually gets confusing as to which target the link should point to. —usernamekiran (talk)19:13, 8 March 2023 (UTC)
[[Luis Díaz (Colombian footballer)]] -> [[Luis Díaz (footballer, born 1997)]] – post-move cleanup, previous title will need to be redirected to the disambiguation page. ■ ∃ Madeline ⇔ ∃ Part of me;09:27, 6 April 2023 (UTC)
[[Lucca (footballer)]] -> [[Lucca (footballer, born 1990)]]
Can you help me clean up following this page move, please? I've performed it in order to distinguish this article from another footballer I mentioned in the previous message.
@GoingBatty My bad, I forgot to mention that I've already added more details about both footballers in the disambiguation page for "Lucca", so I don't need that anymore.
I was mainly worried about direct wiki-links (the ones I can look for from the "What links here" section of each page)... Oltrepier (talk) 14:10, 10 April 2023 (UTC)
We discussed this on Discord and I can't think of a legitimiate reason for <span lang="en" dir="ltr"> to be in the wikicode. I think these should be mass removed. Here's a list of where they occur. cc @Chlod and SWinxy: If no one objects, let's remove them all using AWB. An example removal would be converting <span lang="en" dir="ltr">Test</span> to Test.–Novem Linguae (talk) 07:21, 24 April 2023 (UTC)
There might be legitimate uses btw. For instance you could have an English part inside a German quote on the English wiki. Doubt those would be very common however. —TheDJ (talk • contribs) 09:57, 24 April 2023 (UTC)
Done. I did mainspace and draftspace. I think the others can be left alone. There's lots still on talk pages, some in userspace, and a few in other miscellaneous places. –Novem Linguae (talk) 01:54, 25 April 2023 (UTC)
Spans for other languages and text directions
There are about 1,000 uses of <span lang= and 150 uses of <span dir=. Should this feature of MediaWiki be removed on enwiki? It seems like it's people pressing buttons they shouldn't press rather than any intentional thing. SWinxy (talk) 20:22, 24 April 2023 (UTC)
Unlike the span lang=en dir=ltr above, most of these non-en non-ltr ones appear to be correct usages. That is, they are marking text that is in other languages, distinguishing it from surrounding en ltr text.
However, I am not sure I understand the point of marking foreign language text with spans. Does this change anything visually for the reader? (I don't think it does.) Maybe it's a screen reader / MOS:ACCESS thing? (Seems more likely, anyone know for sure?) –Novem Linguae (talk) 20:56, 24 April 2023 (UTC)
Requesting the replacement of Infobox Indian state legislative assembly constituency with {{Infobox Indian constituency}} on usage pages. This replacement can be a drop-in as it doesn't need to change or replace any parameters. Additionally, it would be nice to add |type=SLA in every replacement.
For example, the change may be as follows:
{{Infobox Indian state legislative assembly constituency
| name = {{{name}}}
| 1 = a
| 2 = b
| 3 = c
... ... }}
to
{{Infobox Indian constituency
| name = {{{name}}}
| type = SLA
| 1 = a
| 2 = b
| 3 = c
... ...}}
I initially proposed this in Wikipedia:Bot requests, but as it did not receive any response and it is a one-time task, I am relisting the proposal here.
If adding "type" makes the process more complex, then the replacement process can be done without the type, no problem. Thank you very much. Prarambh20 (talk) 13:18, 30 April 2023 (UTC)
Qwerfjkl, the former is a redirect to the latter, so this should not be done. Add the |type= param if you want, but please do not just replace the templates. Primefac (talk) 14:20, 30 April 2023 (UTC)
Wouldn't it be better to present all the usage under one template? If it is redirected template, then what is the problem? Prarambh20 (talk) 14:34, 30 April 2023 (UTC)
@Prarambh20, I'm just using a hastemplate search. Doesn't seem to be catching all of them, so I'll keep on running it until there aren't any more. I'll notify you when this is properly finished. — Qwerfjkltalk16:55, 2 May 2023 (UTC)
A recent CFR has renamed categories specifying "Victoria (Australia)" to specify "Victoria (state)" instead. Some redlink categories remain in articles and other pages, for various reasons.
The AWB task required is to visit all pages in the first category and make edits like this which will move them to the second cat. Thanks in advance. --Redrose64 🌹 (talk) 17:54, 7 May 2023 (UTC)
As of today, Fort Bragg has been renamed to Fort Liberty. There seems to be a lot of pages with the old name in them, which could mean some pages would be missed if they were all updated manually. If someone could use AWB to update the name on these pages, I would greatly appreciative it. Thank you for your time and have a great day! DiscoA340 (talk) 23:36, 5 June 2023 (UTC)
It won't always make sense to rename to the new name. If the new name didn't exist at the time of a historic incident that references the place for example. MOS:PLACE says "A place should generally be referred to consistently by the same name as in the title of its article. An exception may be made when there is a widely accepted historical English name appropriate to the given context. In cases where such a historical name is used, it should be followed by the modern name in round brackets (parentheses)". Thus it will be context sensitive which name to use. When referring to the fort in a historical context, it would probably be as "Fort Bragg (Fort Liberty)". This only needs to be done on the first occurrence of Fort Bragg in an article. -- GreenC00:55, 6 June 2023 (UTC)
As a bonus, there may be a few pages with an existing "R from" or similar template. In these cases it would be nice to wrap such templates within the Rcat shell. – FayenaticLondon18:52, 8 May 2023 (UTC)
It looks like JJMC89 has done a subset. Btw @Fayenatic london: {{R fully protected}} is redundant in a {{R shell}}, per: When appropriate, protection levels are automatically sensed, described and categorized. For example, UTC is showing duplicate paragraphs in the shell; it needs only {{R from initialism}} and not {{R fully protected}} 73.93.5.246 (talk) 21:33, 8 May 2023 (UTC)
You are right, thanks. I have edited UTC accordingly.
So, in cases where there is another "R from" or similar template, that only needs an Rcat shell wrapper, as that will then generate the protection category. – FayenaticLondon21:41, 8 May 2023 (UTC)
Technically yes, in some/most cases [1] (~204), no in others [2] (~88). But it's something that's considered editor-hostile enough (see case c) to be worth fixing. I could take care of it by AWB, but I'm trying to avoid mindlessly mashing save 292 times over an hour. Headbomb {t · c · p · b}22:32, 25 June 2023 (UTC)
Unsupported parameter removal in 300+ category talk pages
Resolved
A recent update to Template:WPMILHIST to use an updated version of WPBannerMeta has left 300+ category talk pages with the same unsupported parameter value: the parameter |1=CAT is no longer supported or needed, since the template now knows it is on a category page. If someone could remove the pipe, "CAT", and the line break following, like this, I would appreciate it. The list of pages is here. Thanks. – Jonesey95 (talk) 14:42, 8 July 2023 (UTC)
[[Everything I Love]] -> [[Everything I Love (Alan Jackson album)|Everything I Love]] and [[Everything I Love (song)|Everything I Love]] -> [[Everything I Love (Alan Jackson song)|Everything I Love]]. Cleanup for more accurate disambiguation. Ten Pound Hammer • (What did I screw up now?)19:35, 20 July 2023 (UTC)