Jump to content

Wikipedia:Bot requests: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Tags: Mobile edit Mobile web edit Advanced mobile edit Reply
~aanzx (talk | contribs)
Line 420: Line 420:
:—[[User:Trappist the monk|Trappist the monk]] ([[User talk:Trappist the monk|talk]]) 15:56, 16 March 2023 (UTC)
:—[[User:Trappist the monk|Trappist the monk]] ([[User talk:Trappist the monk|talk]]) 15:56, 16 March 2023 (UTC)
::@[[User:Trappist the monk|Trappist the monk]] so most of the issue is resolved. Thank you for pointers. Hello @[[User:~aanzx|~aanzx]] can you please look into this. [[User:రుద్రుడు|రుద్రుడు]] ([[User talk:రుద్రుడు|talk]]) 16:45, 16 March 2023 (UTC)
::@[[User:Trappist the monk|Trappist the monk]] so most of the issue is resolved. Thank you for pointers. Hello @[[User:~aanzx|~aanzx]] can you please look into this. [[User:రుద్రుడు|రుద్రుడు]] ([[User talk:రుద్రుడు|talk]]) 16:45, 16 March 2023 (UTC)
:::I previously asked questions about same issue
:::# https://en.wikipedia.org/wiki/User_talk:Trappist_the_monk/Archive_6#CS1_error_for_Access_Dates_at_Kannada_Wikipedia
:::# https://en.wikipedia.org/wiki/Help_talk:Citation_Style_1/Archive_38#Access_date_error_on_kannada_wikipedia
:::I will go through it again and check if it fixes the issue.Thanks <span style="text-shadow: 0 0 8px silver; padding:4px; background: ivory; font-weight:bold;">[[User:~aanzx|~aanzx]] <sup>[[user_talk:~aanzx|<big>✉</big>]]</sup><sub>[[Special:Contributions/~aanzx|<big> ©</big>]]</sub></span> 23:59, 16 March 2023 (UTC)

Revision as of 23:59, 16 March 2023

This is a page for requesting tasks to be done by bots per the bot policy. This is an appropriate place to put ideas for uncontroversial bot tasks, to get early feedback on ideas for bot tasks (controversial or not), and to seek bot operators for bot tasks. Consensus-building discussions requiring large community input (such as request for comments) should normally be held at WP:VPPROP or other relevant pages (such as a WikiProject's talk page).

You can check the "Commonly Requested Bots" box above to see if a suitable bot already exists for the task you have in mind. If you have a question about a particular bot, contact the bot operator directly via their talk page or the bot's talk page. If a bot is acting improperly, follow the guidance outlined in WP:BOTISSUE. For broader issues and general discussion about bots, see the bot noticeboard.

Before making a request, please see the list of frequently denied bots, either because they are too complicated to program, or do not have consensus from the Wikipedia community. If you are requesting that a template (such as a WikiProject banner) is added to all pages in a particular category, please be careful to check the category tree for any unwanted subcategories. It is best to give a complete list of categories that should be worked through individually, rather than one category to be analyzed recursively (see example difference).

Alternatives to bot requests

Note to bot operators: The {{BOTREQ}} template can be used to give common responses, and make it easier to keep track of the task's current status. If you complete a request, note that you did with {{BOTREQ|done}}, and archive the request after a few days (WP:1CA is useful here).


Please add your bot requests to the bottom of this page.
Make a new request
# Bot request Status 💬 👥 🙋 Last editor 🕒 (UTC) 🤖 Last botop editor 🕒 (UTC)
1 Automatic NOGALLERY keyword for categories containing non-free files (again) 27 11 Anomie 2024-08-04 14:09 Anomie 2024-08-04 14:09
2 Clear Category:Unlinked Wikidata redirects 9 6 Wikiwerner 2024-07-13 14:04 DreamRimmer 2024-04-21 03:28
3 Fixing stub tag placement on new articles Declined Not a good task for a bot. 5 4 Tom.Reding 2024-07-16 08:10 Tom.Reding 2024-07-16 08:10
4 Adding Facility IDs to AM/FM/LPFM station data Y Done 13 3 HouseBlaster 2024-07-25 12:42 Mdann52 2024-07-25 05:23
5 Tagging women's basketball article talk pages with project tags Y Done 20 4 Usernamekiran 2024-09-05 16:55 Usernamekiran 2024-09-05 16:55
6 Bot that condenses identical references Coding... 12 6 ActivelyDisinterested 2024-08-03 20:48 Headbomb 2024-06-18 00:34
7 Bot to remove template from articles it doesn't belong on? 3 3 Thryduulf 2024-08-03 10:22 Primefac 2024-07-24 20:15
8 One-off: Adding all module doc pages to Category:Module documentation pages 7 3 Andrybak 2024-09-01 00:34 Primefac 2024-07-25 12:22
9 Draft Categories 13 6 Bearcat 2024-08-09 04:24 DannyS712 2024-07-27 07:30
10 Remove new article comments 3 2 142.113.140.146 2024-07-28 22:33 Usernamekiran 2024-07-27 07:50
11 Removing Template:midsize from infobox parameters (violation of MOS:SMALLFONT)
Resolved
14 2 Qwerfjkl 2024-07-29 08:15 Qwerfjkl 2024-07-29 08:15
12 Change stadium to somerhing else in the template:Infobox Olympic games Needs wider discussion. 8 5 Jonesey95 2024-07-29 14:57 Primefac 2024-07-29 13:48
13 Change hyphens to en-dashes 16 7 1ctinus 2024-08-03 15:05 Qwerfjkl 2024-07-31 09:09
14 Consensus: Aldo, Giovanni e Giacomo 17 5 Dicklyon 2024-08-14 14:43 Qwerfjkl 2024-08-02 20:23
15 Cyclones 3 2 OhHaiMark 2024-08-05 22:21 Mdann52 2024-08-05 16:07
16 Substing int message headings on filepages 8 4 Jonteemil 2024-08-07 23:13 Primefac 2024-08-07 14:02
17 Removing redundant FURs on file pages 4 2 Jonteemil 2024-08-12 20:26 Anomie 2024-08-09 14:15
18 Need help with a super widespread typo: Washington, D.C (also U.S.A) 32 10 Jonesey95 2024-08-26 16:55 Qwerfjkl 2024-08-21 15:08
19 Dutch IPA 4 3 IvanScrooge98 2024-08-25 14:11
20 AnandTech shuts down 9 6 GreenC 2024-09-01 18:39 Primefac 2024-09-01 17:28
21 Date formatting on 9/11 biography articles 5 2 Zeke, the Mad Horrorist 2024-09-01 16:27
22 Discussion alert bot 6 4 Headbomb 2024-09-08 12:29 Headbomb 2024-09-08 12:29
23 Regularly removing {{coords missing}} if coordinates are present BRFA filed 11 2 Usernamekiran 2024-09-07 13:19 Usernamekiran 2024-09-07 13:19
24 Latex: move punctuation to go inside templates 3 2 Yodo9000 2024-09-07 18:59 Anomie 2024-09-07 03:38
25 Removing spurious nobot notice BRFA filed 4 2 DreamRimmer 2024-09-07 12:55 DreamRimmer 2024-09-07 12:55
26 de-AMP bot
Resolved
4 3 Primefac 2024-09-09 16:01 Primefac 2024-09-09 16:01
Legend
  • In the last hour
  • In the last day
  • In the last week
  • In the last month
  • More than one month
Manual settings
When exceptions occur,
please check the setting first.


There was a fairly clear consensus in the discussion at Wikipedia:Village pump (technical)/Archive 202#Accelerated Mobile Pages links that "amp" links are a bad thing, and should be done away with. Can a bot be written that tests links to insure that a version with the ".amp" or ",amp" or "/amp" component removed will work, and if so, remove that component? BD2412 T 23:40, 4 January 2023 (UTC)[reply]

Good idea, but I think it would need a per-site rule list, e.g. amp.example.com/(.*) → example.com/$1, because each site is free to choose its own URL semantics. It's even possible that some sites can't be unpicked (raw page at /raw/87293410.html; AMP at /amp/1934872.html) or don't work without AMP at all. Certes (talk) 12:42, 5 January 2023 (UTC)[reply]
Coding... I can probably work on this; AmputatorBot offers an API for conversion of URLs, and a simple insource search returns many applicable results that can be further filtered with some regex. EpicPupper (talk) 18:16, 31 January 2023 (UTC)[reply]
BRFA filed. EpicPupper (talk) 06:39, 5 March 2023 (UTC)[reply]

Multiple requests

I am request a bot to:

  1. Remove/revert blank responses at Help:Introduction/feedback and the other feedback pages (though i question the usefulness of these pages altogether, looking at the responses).
  2. Automatically comment on WP:RFPP/E when the respective talk page is protected or redirects to a talk page (for example, if someone requests an edit to Wikipedia:Contents WP:Contact us/Licensing, the bot should comment that the talk page is protected).
  3. Comment at AIV, AIV/TB2, UAA, and UAA/BOT when the reported account is globally locked.

137a (talkedits) 18:49, 8 February 2023 (UTC)[reply]

Bot to notify users when they add CS1 errors

Hi everyone! The page Help:CS1 errors#Most common errors shows a few categories that are quite large. I am requesting a bot operator to write a bot that delivers user talk page messages similar to JaGa's DPL bot whenever a registered editor adds an article to one of the most common CS1 error categories. The bot could use the watchlist to see which user added which article to which category, and then add a new section on the user's talk page detailing what the error means and how to fix it, with text similar to what is posted at Help:CS1 errors. Per the conversation at Help talk:Citation Style 1#Bot to notify users when they add CS1 errors, ReferenceBot used to do this many years ago. Legoktm has archived the code, and A930913 has declared all their code on Labs as CC-BY-SA. Thanks! GoingBatty (talk) 15:11, 14 February 2023 (UTC)[reply]

@GoingBatty, looks like feedwatchlist is the API module needed, as there doesn't seem to be a relatedchahnges one. — Qwerfjkltalk 12:52, 15 February 2023 (UTC)[reply]
@GoingBatty, I've been looking at doing this with wikitech:Event Platform/EventStreams; I'll see if I have any luck. — Qwerfjkltalk 11:51, 16 February 2023 (UTC)[reply]
I'm wary about this... The citation templates are not always trivial to use - as seen in the vast amount of documentation that comes with them. If a lot of errors are being made by, say, new users, I'd be wary about bots bugging them to fix minutae that will require them to scour documentation and/or ping people for help, vs the patrollers just fixing the errors as probably currently happens. At worst it deters editing, at best it takes up more time on the part of potentially multiple editors vs what happens presently. ProcrastinatingReader (talk) 12:31, 16 February 2023 (UTC)[reply]
@ProcrastinatingReader, it wouldn't be too hard to include how to fix the problem. — Qwerfjkltalk 12:56, 16 February 2023 (UTC)[reply]
@ProcrastinatingReader: There are many categories of CS1 errors that patrollers such as myself can keep up with, and I agree that sending notification for those is not worthwhile. However, for those categories with 24k-54k pages, something else needs to be done. I hope that posting on user talk pages - with the appropriate portion of the documentation - will teach people what they did incorrectly and encourage them to fix their own mistakes. GoingBatty (talk) 17:23, 16 February 2023 (UTC)[reply]
I think that ReferenceBot did a pretty good job of notifying people in a reasonable way. Editors who understood the message were often grateful for the notice, just as I am when I receive a message that I have inadvertently added a disambiguation link to an article. Many of those editors were able to go back and fix their mistakes. Editors who didn't understand the message were likely to just leave it alone or never see it, which is fine; we can't expect everyone to understand all of this technical stuff perfectly.
Of note: you can see by the postings at User talk:A930913 that some editors wanted to ask questions about the notifications that they received, so there will need to be a few editors willing to field those editors' questions or fix the errors that those editors ask about. And of course there was often some gibberish posted there as well, so the bot operator and page watchers will need to be able to tolerate that level of noise. Huon and I found that talk page a useful place to spend some time, FWIW. – Jonesey95 (talk) 18:19, 16 February 2023 (UTC)[reply]
Ah. Yeah, I guess if it's done reasonably, including a quote of the relevant documentation to help fix the problem without actually needing to read the docs, then it could work. ProcrastinatingReader (talk) 11:44, 18 February 2023 (UTC)[reply]
@Jonesey95: Thanks for the additional background. I would be happy to be a bot talk page watcher. GoingBatty (talk) 02:59, 19 February 2023 (UTC)[reply]
@GoingBatty, can you provide some templated messages for each of the categories? — Qwerfjkltalk 17:15, 22 February 2023 (UTC)[reply]
@Qwerfjkl: Could you please provide an example of a "templated message"? If so, I could then copy text from the appropriate sections of Help:CS1 errors and adapt them for "templated messages". Thanks! GoingBatty (talk) 18:39, 22 February 2023 (UTC)[reply]
@GoingBatty, I'm planning on the bot posting messages similarly to ReferenceBot. I just need a default message for each category, explaining how to fix the problem. Something paraphrased from Help:CS1 errors would be great. — Qwerfjkltalk 20:00, 22 February 2023 (UTC)[reply]
E.g. for the no title given error (bare URL): "Please fix this by adding a descriptive title to |title=." — Qwerfjkltalk 20:06, 22 February 2023 (UTC)[reply]
@Qwerfjkl: By copying and tweaking the pages for ReferenceBot and User:A930913, I created the following pages (which will need to be tested):
However, I think I'm still missing the section called by User:Qwerfjkl (bot)/inform/middle where the details of each error come from and the suggestions to fix the text. Maybe A930913 can provide a suggestion. Thanks! GoingBatty (talk) 21:10, 22 February 2023 (UTC)[reply]
@GoingBatty, these look great! For /middle, I can pass on the error type (i.e. category), and a {{#switch}} statement could provide some guidance.
To test this out, I'll have the bot run and just add the messages to a sandbox instead of the user talk page. — Qwerfjkltalk 21:52, 22 February 2023 (UTC)[reply]
@GoingBatty, I've made a testing page at User:Qwerfjkl (bot)/CS1 errors. Note that the bot will deliver one message per edit (and page), but that edit may introduce multiple errors. — Qwerfjkltalk 18:03, 23 February 2023 (UTC)[reply]
I'm coming late to this thread, and it's been a heck of a long time since I helped set up ReferenceBot, but this discussion and this discussion may possibly be useful. – Jonesey95 (talk) 18:45, 23 February 2023 (UTC)[reply]
┌──────────────────────────────┘
@Jonesey95, I'd prefer to have the messages on enwiki, so it's easier to make any modifications necessary (some level of page protection is probably necessary). — Qwerfjkltalk 18:57, 23 February 2023 (UTC)[reply]
@Qwerfjkl: I can see the tweaks you made to the files and the improving results on User:Qwerfjkl (bot)/CS1 errors. Is it possible to add more info in the user talk message to guide users on how to fix the errors? It looks like the bot posts the user talk message about a minute after the error is made. Could the time be increased (maybe 15 minutes) to allow the user time to notice and fix the error on their own? Thanks! GoingBatty (talk) 21:26, 23 February 2023 (UTC)[reply]
@GoingBatty, it would be better if the messages were part of the template. I was thinking that the bot can pass in the category as a parameter, and the template uses a {{#switch:}} statement to prove a corresponding help message.
I'll see what I can do about waiting after the edit. — Qwerfjkltalk 22:19, 23 February 2023 (UTC)[reply]
The bot should now wait around 15 minutes, and will only post the message if the page is still in an error category. — Qwerfjkltalk 17:08, 24 February 2023 (UTC)[reply]
@GoingBatty, so could you look at adding some helpful messages to User:Qwerfjkl (bot)/inform/middle? The bot will pass in a {{{cat}}} parameter, which a switch statement can use to provide the info. I'll probably use |cat=Category:CS1 errors: bare URLCategory:CS1 errors: missing title when both are present, as those don't need separate error messages. — Qwerfjkltalk 16:54, 1 March 2023 (UTC)[reply]
@Qwerfjkl: Yes, but I'm not sure about the format. Could you please change "Category:Example" to "Category:Example1" and add "Text1", and then add Example2/Text2, Example3/Text3, and Example4/Text4? I'll then replace that with the real category names and helpful text. Thanks! GoingBatty (talk) 18:35, 1 March 2023 (UTC)[reply]
@GoingBatty, BRFA filed. — Qwerfjkltalk 16:59, 2 March 2023 (UTC)[reply]

Category:Wikipedia infobox backlog - articles needing infoboxes

I'm wondering if there's a possibility to create list(s) of articles tagged with "infobox needed" while including "{{Infobox..." in the article? So the unnecessary tags can be removed. Myself mostly interested in 1. Football 2. Sports 3. Bios. -Pelmeen10 (talk) 22:17, 14 February 2023 (UTC)[reply]

@Pelmeen10, all of this can be done with the search (including by topic). I don't have time to do this right now, I'll try later. — Qwerfjkltalk 22:24, 14 February 2023 (UTC)[reply]
@Qwerfjkl: I could submit a BRFA to do this with AWB if you like. Is that OK with you? GoingBatty (talk) 03:02, 15 February 2023 (UTC)[reply]
@GoingBatty, go ahead. — Qwerfjkltalk 08:31, 15 February 2023 (UTC)[reply]
@Pelmeen10 & @Qwerfjkl: BRFA filed. GoingBatty (talk) 19:28, 15 February 2023 (UTC)[reply]

Can we have an AIV feed a bot posts on IRC?

I used to have one but then the toolserver changed and somehow an account isn't easy to come by, now... (asked elsewhere before, maybe here will be more relevant...) ~Lofty abyss 05:16, 15 February 2023 (UTC)[reply]

@Lofty abyss, do you have the code for it? — Qwerfjkltalk 08:33, 15 February 2023 (UTC)[reply]
Well, I don't quite remember which specifically I used years ago, but on searching there seems to be several possibilities: https://www.mediawiki.org/wiki/Manual:IRC_RC_Bot https://www.mediawiki.org/wiki/Manual:MediaWiki-Recent_Changes-IRCBot https://en.wikibooks.org/wiki/MediaWiki_Administrator%27s_Handbook/Countervandalism_IRC_Bots
It's also, generally, what the cvn bots do already there, except this would need to be a more specific page that is watched. ~Lofty abyss 18:28, 15 February 2023 (UTC)[reply]
Doing... I can take a stab at this. EpicPupper (talk) 21:51, 20 February 2023 (UTC)[reply]

The code is avaliable here, though it may not work. The code is mostly written in PHP. — Qwerfjkltalk 11:12, 16 February 2023 (UTC)[reply]

Grape Cultivar Capitalization

I've noticed that there are widespread problems with compliance to MOS:BIOCAPS for grape cultivars and wine varietals. For instance, the MOS requires "Pinor Noir" to always be capitalized, but it is frequently written "Pinot noir" in Wikipedia. It would be helpful if someone could create a bot to properly capitalize grape varietal names per MOS. This would require taking something like List of grape varieties and checking that the names there don't conflict with non-grape terms. QuintinK (talk) 15:11, 16 February 2023 (UTC)[reply]

WP WikiProject Weather track maps

WP:WPWX is in need of a bot that can rewrite track map images using the new colors that were approved in a recent RfC. The bot would have to be able to utilize the track maker found here. These images are generated using input code that is run through the track maker software. NoahTalk 19:35, 25 February 2023 (UTC)[reply]

I raised issues regarding this task in a previous discussion (see here). I feel that this request is too vague and lacks context, so I'll restate it here for visibility.
Changing the old track maps would be in violation of c:COM:OVERWRITE unless there's prior cross-wiki support from all wikis which use those maps and from Wikimedia Commons to get the bot task approved. The RfC only took place on this wiki, and the local English Wikipedia-only consensus cannot be applied across all other wikis which use these maps. Thus, the only realistic option given existing consensus is to upload local versions of every track map (and subsequently upload a wiki-local version of every newly-uploaded track for the foreseeable future). In such case, over 5,574 new images will need to be uploaded—1,846 of which require secondary verification (to verify accuracy or to resolve missing data), and 592 of which needing reconstruction by other weather editors (due to missing or unavailable data). This doesn't count future track maps, of course. Chlod (say hi!) 02:04, 26 February 2023 (UTC)[reply]
@Chlod: How about we upload new images to commons and let other wikis choose whether or not they want to switch given that some of the other wikis do follow us? We leave the existing maps as they are. NoahTalk 02:11, 26 February 2023 (UTC)[reply]
@Hurricane Noah: That would not solve the issue of having to upload two versions to Commons, making the thousands of edits locally to switch to the new versions, and it would be out of the remit of English Wikipedia bot requests. Chlod (say hi!) 02:13, 26 February 2023 (UTC)[reply]
If we get a request on commons for a bot as stated below, we could upload both versions there from here on out and simply change the maps here with a bot once an accessible version has been uploaded to replace the one here. NoahTalk 02:39, 26 February 2023 (UTC)[reply]
It is fine to make derivatives on Commons if the bot gets approved for creation there. That is indeed out of scope here but that is in the realm of both social and technical feasibility.
I don't see an issue with making a couple thousand edits to update maps locally, if the images are actually expected to be preferred here. Either way, the images will be free, and we do not want to host free images here for any of several good reasons. Izno (talk) 02:22, 26 February 2023 (UTC)[reply]
They at least need to be changed at the local level considering the color scheme was approved via RfC. NoahTalk 02:28, 26 February 2023 (UTC)[reply]
I put in a request on commons for the images that don't require any additional work or verification prior to an upload. NoahTalk 02:59, 26 February 2023 (UTC)[reply]
@Hurricane Noah, could you detail the exact changes required for this task? What sorts of replacements should be made with the track maker? Thanks! EpicPupper (talk) 00:42, 28 February 2023 (UTC)[reply]
Keep in mind that the track maker part of this would need to take place on commons (request there is linked in my comment right above yours), however, the new images would have the adjusted color scheme which is shown below. The data is the same data used in the existing track maps (data can be found on each image page; there are databases containing the data) and these new maps would simply be new files. Commons:Category:Tropical cyclone track maps with track data as input code contains all the images that would be able to be redone via bot. The new images would need to placed within that category as well as Commons:Category:Tropical cyclone track maps with the 2023 scale.
Category Old Scheme New Scheme
Tropical Depression/Disturbance
Tropical Storm
Category 1
Category 2
Category 3
Category 4
Category 5
The on-wiki portion would involve changing all the existing file names within articles to match the files names of new track maps. NoahTalk 01:09, 28 February 2023 (UTC)[reply]
@EpicPupper:

WP WikiProject Weather timelines

WP:WPWX is also in need of a bot that can change colors within timelines on articles. This would only involve substituting in the new color parameters that were approved in a recent RfC. I can provide more specific details on this if anyone is able to do this. NoahTalk 19:36, 25 February 2023 (UTC)[reply]

@Hurricane Noah, I seem to recall something like this earlier. I may still have the code I used. — Qwerfjkltalk 19:58, 25 February 2023 (UTC)[reply]
@Qwerfjkl: Well... the colors are different now so the coding would be different, but yes, I see what you mean. The old request was at User talk:Qwerfjkl/Archive 9. Would you be willing to perform the changes? I could provide the new colors and appropriate categories of articles here. NoahTalk 20:03, 25 February 2023 (UTC)[reply]
Extended content
Atlantic/Eastern Pacific hurricanes
New text =

Colors     =
  id:canvas value:gray(0.88)
  id:GP     value:red
  id:TD     value:rgb(0.43,0.76,0.92)  legend:Tropical_Depression_=_≤38_mph_(≤62_km/h)
  id:TS     value:rgb(0.3,1,1)  legend:Tropical_Storm_=_39–73_mph_(63–117_km/h)
  id:C1     value:rgb(1,1,0.85)     legend:Category_1_=_74–95_mph_(118–153_km/h)
  id:C2     value:rgb(1,0.85,0.55)  legend:Category_2_=_96–110_mph_(154–177_km/h)
  id:C3     value:rgb(1,0.62,0.35)  legend:Category_3_=_111–129_mph_(178–208_km/h)
  id:C4     value:rgb(1,0.45,0.54)  legend:Category_4_=_130–156_mph_(209–251_km/h)
  id:C5     value:rgb(0.55,0.46,0.90)  legend:Category_5_=_≥157_mph_(≥252_km/h)

For all season-related articles with timelines in the categories (may need to check subcategories): Category:Atlantic Ocean meteorological timelines, Category:Atlantic hurricane seasons, Category:Pacific hurricane seasons, and Category:Pacific hurricane meteorological timelines

Pacific typhoons
New text =
Colors     =
  id:canvas value:gray(0.88)
  id:GP     value:red
  id:TD     value:rgb(0.43,0.76,0.92)    legend:Tropical_Depression_=_≤62_km/h_(≤39_mph)
  id:TS     value:rgb(0.3,1,1)    legend:Tropical_Storm_=_62–88_km/h_(39–54_mph)
  id:ST     value:rgb(0.75,1,0.75)        legend:Severe_Tropical_Storm_=_89–117_km/h_(55–72_mph)
  id:STY    value:rgb(1,0.85,0.55)    legend:Strong_Typhoon_=_118–156_km/h_(73–96_mph)
  id:VSTY   value:rgb(1,0.45,0.54)    legend:Very_Strong_Typhoon_=_157–193_km/h_(97–119_mph)
  id:VITY   value:rgb(0.55,0.46,0.90)    legend:Violent_Typhoon_=_≥194_km/h_(≥120_mph)

In addition, please change any values of TY within the actual part where storms are listed to STY since typhoon is now strong typhoon. The legend name also changes from typhoon to strong typhoon. The VSTY and VITY need to be added into the timelines since those statuses are now being included (the VSTY and VITY are within the coding above). A caveat is that articles dated 1972 or earlier need to use the colors for the Atlantic/Eastern Pacific.

For all season-related articles with timelines in the categories (may need to check subcategories): Category:Pacific typhoon seasons

North Indian
New text =
Colors     =
  id:canvas value:gray(0.88)
  id:GP     value:red
  id:TD   value:rgb(0,0.52,0.84)      legend:Depression_(31–50_km/h)
  id:DD     value:rgb(0.43,0.76,0.92)    legend:Deep_Depression_(51–62_km/h)
  id:TS     value:rgb(0.3,1,1)    legend:Cyclonic_Storm_(63–88_km/h)
  id:ST     value:rgb(0.75,1,0.75)        legend:Severe_Cyclonic_Storm_(89–117_km/h)
  id:VS     value:rgb(1,0.85,0.55)        legend:Very_Severe_Cyclonic_Storm_(118–165_km/h)
  id:ES     value:rgb(1,0.45,0.54)    legend:Extremely_Severe_Cyclonic_Storm_(166–220_km/h)
  id:SU     value:rgb(0.55,0.46,0.9)    legend:Super_Cyclonic_Storm_(≥221_km/h)

For all season-related articles with timelines in the categories (may need to check subcategories): Category:North Indian Ocean cyclone seasons and Category:North Indian Ocean meteorological timelines

South-west Indian
New text =
Colors     =
  id:canvas value:gray(0.88)
  id:GP   value:red
  id:ZD   value:rgb(0,0.52,0.84)   legend:Zone_of_Disturbed_Weather/Tropical_Disturbance_=_≤31_mph_(≤50_km/h)
  id:TD   value:rgb(0.43,0.76,0.92) legend:Tropical_Depression/Subtropical_Depression_=_32–38_mph_(51–62_km/h)
  id:TS   value:rgb(0.30,1,1) legend:Moderate_Tropical_Storm_=_39–54_mph_(63–88_km/h)
  id:ST   value:rgb(0.75,1,0.75)    legend:Severe_Tropical_Storm_=_55–73_mph_(89–118_km/h)
  id:TC   value:rgb(1,0.85,0.55)    legend:Tropical_Cyclone_=_74–103_mph_(119–166_km/h)
  id:IT   value:rgb(1,0.45,0.54) legend:Intense_Tropical_Cyclone_=_104–133_mph_(167–214_km/h)
  id:VI   value:rgb(0.55,0.46,0.9) legend:Very_Intense_Tropical_Cyclone_=_≥134_mph_(≥215_km/h)

For all season-related articles with timelines in the categories (may need to check subcategories): Category:Southwest Indian Ocean meteorological timelines and Category:South-West Indian Ocean cyclone seasons

Australian Region
New text =
Colors     =
  id:canvas value:gray(0.88)
  id:GP     value:red
  id:TL     value:rgb(0.43,0.76,0.92)  legend:Tropical_Low_=_<63_km/h_(<39_mph)
  id:C1     value:rgb(0.3,1,1)  legend:Category_1_=_63–88_km/h_(39-55_mph)
  id:C2     value:rgb(0.75,1,0.75)     legend:Category_2_=_89–117_km/h_(55-73_mph)
  id:C3     value:rgb(1,0.85,0.55)     legend:Category_3_=_118–159_km/h_(73-99_mph)
  id:C4     value:rgb(1,0.45,0.54)  legend:Category_4_=_160–199_km/h_(99-124_mph)
  id:C5     value:rgb(0.55,0.46,0.9)  legend:Category_5_=_≥200_km/h_(≥124_mph)

For all season-related articles with timelines in the categories (may need to check subcategories): Category:Australian region cyclone seasons and Category:Australian region meteorological timelines

South Pacific
New text =
Colors     =
  id:canvas value:gray(0.88)
  id:GP     value:red
  id:TDi    value:rgb(0,0.52,0.84)    legend:Tropical_Disturbance
  id:TD     value:rgb(0.43,0.76,0.92)  legend:Tropical_Depression
  id:C1     value:rgb(0.3,1,1)  legend:Category_1_=_63-87_km/h_(39-54_mph)
  id:C2     value:rgb(0.75,1,0.75)     legend:Category_2_=_88-142_km/h_(55-74_mph)
  id:C3     value:rgb(1,0.85,0.55)    legend:Category_3_=_143-158-km/h_(75-98_mph)
  id:C4     value:rgb(1,0.45,0.54)  legend:Category_4_=_159–204_km/h_(99–127_mph)
  id:C5     value:rgb(0.55,0.46,0.9)  legend:Category_5_=_≥205_km/h_(≥128_mph)

For all season-related articles with timelines in the categories (may need to check subcategories): Category:South Pacific cyclone seasons and Category:South Pacific meteorological timelines

Winter
New text =
Colors     =
  id:canvas value:gray(0.88)
  id:C0     value:rgb(0.3,1,1)  legend:Category_0_&_N/A_<_1.0_RSI
  id:C1     value:rgb(1,1,0.85)    legend:Category_1_=_1.0–3.0_RSI
  id:C2     value:rgb(1,0.85,0.55)  legend:Category_2_=_3.0–6.0_RSI
  id:C3     value:rgb(1,0.62,0.35)   legend:Category_3_=_6.0–10.0_RSI
  id:C4     value:rgb(1,0.45,0.54)  legend:Category_4_=_10.0–18.0_RSI
  id:C5     value:rgb(0.55,0.46,0.9)  legend:Category_5_≥_18.0_RSI

Category: Category:North American winters

@Noah, I can probably do this, but I'm busy right now with several bot tasks. If anyone else wants to take this on, go ahead; otherwise I'll try to start on this soon. — Qwerfjkltalk 10:59, 26 February 2023 (UTC)[reply]
@Qwerfjkl: Checking in since it's been nearly 2 weeks. NoahTalk 03:33, 11 March 2023 (UTC)[reply]
@Hurricane Noah, yes, sorry. I just took care of 3 BRFAs, so I'll start this one today hopefully. — Qwerfjkltalk 10:40, 11 March 2023 (UTC)[reply]
BRFA filed— Qwerfjkltalk 11:44, 11 March 2023 (UTC)[reply]

Can a bot please replace all instances of {{br list}} with {{br entries}}? I'm looking to have this redirect deleted as the target of both redirects, {{br separated entries}}, is designed for use in infoboxes to replace the use of <br /> in a delimited collection of entries; so, therefore, it is not a list template. Much obliged, ‑‑Neveselbert (talk · contribs · email) 20:48, 2 March 2023 (UTC)[reply]

@Neveselbert: Hello. Technically, I can create a bot task for that, but I think this task needs a wider discussion/conensus. —usernamekiran (talk) 21:06, 2 March 2023 (UTC)[reply]
Hi usernamekiran, I requested that {{br list}} be moved to {{br entries}} which was reviewed and fulfilled by an admin (UtherSRG), so I think this should be relatively uncontroversial. ‑‑Neveselbert (talk · contribs · email) 21:09, 2 March 2023 (UTC)[reply]
@Neveselbert: yes, I had already seen that :-) I'm not opposed to replace the entries, but renaming/moving a template and replacing entries in mainspace are different things. If any editor agrees here to replace them, I will do it also, I think Template:Br list is causing a double redirect. But I'm sleep deprived, and sleepy right now, so I may be getting confused about it (I'm on mobile). —usernamekiran (talk) 21:29, 2 March 2023 (UTC)[reply]
Sounds like WP:COSMETICBOT. — Qwerfjkltalk 21:37, 2 March 2023 (UTC)[reply]
yeah, that too. Actually that was the reason why I was hesitant to do it, but I wasn't able to pinpoint the reason. I really should sleep now. Did you see the redirects? —usernamekiran (talk) 21:41, 2 March 2023 (UTC)[reply]
I've fixed the 2x redir issue. - UtherSRG (talk) 22:02, 2 March 2023 (UTC)[reply]
There are two cases here that make it so that sometimes line breaks are applicable rather than an HTML list, which is what I believe you are differentiating on, so WP:CONTEXTBOT is applicable:
  1. The list should really be a {{unbulleted list}}.
  2. The list should really be a {{br separated entries}}, such as in an address.
If there is merit to work of this nature, it's to separate the two uses, but that cannot be done by a bot. AWB could perhaps do it reasonably quickly if the use of the names are skewed toward a certain use.
As for removal of template redirects, sometimes you can get away with it if the uses are few enough in number, but otherwise you may be dragged to WP:RFD, where I have not had general success with requesting deletion on semantic lines recently....
See also a recent discussion I had with @Hike395 at User talk:Izno/Archive 9#A neglected kind of list. Izno (talk) 23:08, 2 March 2023 (UTC)[reply]
Or adding the plainlist class to the relevant fields of the infobox and not needing templates like {{unbulleted list}}. Gonnym (talk) 23:17, 2 March 2023 (UTC)[reply]
I think it would be great to have a bot go through infobox parameters and convert {{br list}} to {{plainlist}} and {{enum}} to {{hlist}}. It would have to be done per infobox type, however, because there may be some parameters which really are expecting a multiline entry (as opposed to an actual list).
Per Gonnym: I also putting {{plainlist}} or {{hlist}} into the infobox itself, for uniformity. I believe this requires numbered parameters? That has proven to be controversial, because some editors don't like how numbered parameters make TemplateData very long. — hike395 (talk) 16:58, 3 March 2023 (UTC)[reply]
No. See infoboxes like Template:Infobox TV episode e.g. line 24 (which I had to support in Module:Infobox when I moved plainlist to TemplateStyles). Izno (talk) 20:04, 3 March 2023 (UTC)[reply]

Remove hyphens from "antisemitism" and "antisemite"

Wikipedia's Antisemitism article includes a reference to the correct (non-hyphenated) spelling of the word (footnote [a]), but other articles use the non-standard hyphen (e.g., this one).

This is not simply a cosmetic or even grammatical change, it has to do with the actual meaning of the term (see here and here).

In addition to the most widely used and adopted definition of antisemitism, from the International Holocaust Remembrance Alliance (IHRA), cited in the Wikipedia article, here are some other references to the importance of NO hyphen in the term, from experts and leaders in the field:

Nevet Basker (talk) 20:08, 7 March 2023 (UTC)[reply]

Special:Search/insource:"anti-semitism" and Special:Search/insource:"anti-semite". — Qwerfjkltalk 20:12, 7 March 2023 (UTC)[reply]
Is this really a suitable task for a bot? It's likely an easier task for human eyes (like through WP:AWB), as there are cases like "confirmed anti-Semite" in the Adolf Hitler article, which if a direct quote shouldn't be changed. Lee Vilenski (talkcontribs) 20:16, 7 March 2023 (UTC)[reply]
@Lee Vilenski, yes, those cases might need {{sic}} or {{not a typo}} instead. — Qwerfjkltalk 21:33, 7 March 2023 (UTC)[reply]
But "anti-semitism" is not a typo or an error; those templates are for marking actual typos or words that could be mistaken for errors. The lead of the article says also spelled anti-semitism or anti-Semitism. We generally do not do site-wide spelling enforcement on valid word variants unless there is an English Wikipedia guideline saying how a word with multiple variants should be spelled. This would typically be set via a tedious and energy-wasting RFC. Consistency within articles and topic areas is fine, but nobody should go around changing one variant to another. The OP should drop this particular stick. – Jonesey95 (talk) 21:51, 7 March 2023 (UTC)[reply]
This is a WP:CONTEXTBOT and would not be accepted at BRFA. Izno (talk) 21:17, 7 March 2023 (UTC)[reply]

Stub assessments with ORES

Hello, magic makers:

I would like a bot that assesses/rates articles as being stubs. This could be a one-time, large run, or perhaps after it's happened once, you'd like to do a smaller clean-up run once every 4–12 months. See more information and ➤links to potentially helpful code at User talk:The Earwig#WPMED.

Wikipedia:Content assessment#Statistics says that we have more than 420,000 articles that are tagged as being with the scope of one or more WikiProjects but don't have any quality assessment. It's likely that 50–60% of these are obvious stubs. The mw:ORES ratings for stubs are very reliable (some false negatives – which wouldn't be touched under this proposal – but no false positives). If we could get a bot to mark already tagged but unassessed articles as |class=Stub, this could save editors thousands of hours. WhatamIdoing (talk) 00:06, 9 March 2023 (UTC)[reply]

Thanks for the idea. I have a user script that applies stub templates, and my experience with that is that some Wikipedians think stubs should only be for very tiny articles, and will revert you if you stub something borderline. I also think that if an article talk page is set to |class=stub, there's an expectation that a very specific stub template (e.g. {{Primate-stub}}, {{US-politician-stub}}, {{Tennis-stub}}, etc.) be added to the main article. Overcoming these two issues, and getting the necessary consensus, could be challenging.
Wikipedia:Stub gives multiple rules of thumb, including ≤10 sentences, ~250 words, and ≤1,500 characters. Any of these is generally considered valid. ORES is more conservative than all of these. It regularly rates 8-sentence stubs and 200-word articles as being Start-class. However, that's okay, because I propose using it only for tagging things it believes are Stubs.
I have never seen any expectation that assessing an article for a WikiProject means you have to edit the article at all, even to add any sort of stub template. I've never received any similar complaint, and I've manually assessed more than 10,000 articles over the years. WhatamIdoing (talk) 04:57, 9 March 2023 (UTC)[reply]
@WhatamIdoing, I don't see any code at that discussion. Also, I would suggest getting clearer consensus for this first. — Qwerfjkltalk 07:18, 9 March 2023 (UTC)[reply]
In the link to https://en.wikipedia.org/w/index.php?title=User_talk:The_Earwig&oldid=760282026#Could_your_bot_tag_some_articles_for_me.3F. The code is in the collapsed box. WhatamIdoing (talk) 05:41, 10 March 2023 (UTC)[reply]
@The Earwig: We are already doing this at WP:MILHIST for all articles tagged as belonging to the project. Articles without an assessment are checked by the MilHistBot and rated Stub, Start, C or B using our five-point assessment system + ORES. Those rated B are sent for human re-checking. We also ran the Bot against all the project's articles marked as stubs, and reassessed them. Hawkeye7 (discuss) 09:26, 9 March 2023 (UTC)[reply]
@WhatamIdoing: I am willing to run the Bot against articles belonging to other projects on request. I can tell you that the Bot run did save our project a lot of work. New MilHist articles arrive at a rate of about 100 per day; most are stubs or starts but about 2% are rated B class. Every month the coordinators check them from a list submitted by the Bot on the coordinators' talk page. Nobody cares much about the articles with the lower ratings. Hawkeye7 (discuss) 19:54, 9 March 2023 (UTC)[reply]
Might be worth waiting until project-individual class assessments are used. — Qwerfjkltalk 19:57, 9 March 2023 (UTC)[reply]
I'd like this done for all WikiProjects, not just one at a time and only for the groups that are big enough and organized enough to make a request. There have never been any WikiProjects that object to have obvious stubs rated as being stubs instead of not being rated by anyone.
As I have said before, once you get past Stub-class, things get complicated. Wikipedia:WikiProject Highways has a very unusual definition of the minimum for Start-class, and things that might be C-class by other group's standards could still linger as stubs for them. But we don't need to worry about those complications if we assess only obvious stubs. If we assess only obvious stubs, then everyone will agree that their group's ratings have been correctly applied in the instances that we're applying them. WhatamIdoing (talk) 05:47, 10 March 2023 (UTC)[reply]
That makes sense, but you'd probably still need to get a wider consensus somewhere. Galobtter (pingó mió) 06:07, 10 March 2023 (UTC)[reply]
@Galobtter, whose consent are you interested in? We had bots rating articles ~15 years ago, so it's a traditional bot activity. Bot-assisted assessment predates the 2008 creation of Template:WPBannerMeta, and the |auto= parameter to mark assessments made by bots was in the original design of that template. I don't mind seeking the approval of anyone you want, but I'm not sure whom you think might object, and getting approval from the "wrong" people won't forestall any problems that you foresee. WhatamIdoing (talk) 02:52, 14 March 2023 (UTC)[reply]
@WhatamIdoing I don't have any particular objections; if ORES is as conservative in tagging stubs as you mention, there probably won't be any issues. (I was thinking some sort of discussion at WP:VPR just to make sure there are no objections, although yeah I guess you are right that unless you message every WikiProject someone might always object.) Galobtter (pingó mió) 03:12, 14 March 2023 (UTC)[reply]
Category:Unassessed articles contains articles that have been tagged with a project but have not been assessed. I'm not sure how you find articles that don't have talk pages yet. Hawkeye7 (discuss) 04:31, 15 March 2023 (UTC)[reply]
If you want to do that, then Wikipedia talk:WikiProject Council#Articles without Wikiprojects has a script. But I don't think that is a good step to take right now. WhatamIdoing (talk) 16:32, 15 March 2023 (UTC)[reply]
So you are only considering articles already tagged with a project but not yet given a class, and then only classing the ones ORES considers to be stubs? There are only about 2,000 articles currently in Category:Unassessed articles. I would estimate that about 240 of them would be stubs, based on Wikipedia:WikiProject Military history/Assessment#Statistics, where 12% of our articles are stubs. Hawkeye7 (discuss) 19:41, 15 March 2023 (UTC)[reply]
Wikipedia:Version 1.0 Editorial Team/Statistics says there are 407K unassessed articles right now. I assume (but I could be wrong) that it can't see anything that isn't tagged by some project. WhatamIdoing (talk) 21:04, 15 March 2023 (UTC)[reply]

Removal of Unused Fields in Templates

Hello Wikipedians,

I have seen a lot of unused fields in various templates from all over Wikipedia. Can there be a bot to remove the unused fields in templates?

This is but a suggestion and I am not sure whether it is necessary or not. But anyway, thank you. I'm Here to Help You (talk) 08:06, 11 March 2023 (UTC)[reply]

This is kind of a WP:PERENNIAL request. No, this will not be accepted. Izno (talk) 08:24, 11 March 2023 (UTC)[reply]
Apart from unused params normally being harmless which makes this a WP:COSMETICBOT situation, there are some templates where a parameter behaves differently when present but blank compared to when it is completely absent, and so the presence of a blank parameter may be intentional. --Redrose64 🌹 (talk) 10:47, 11 March 2023 (UTC)[reply]
Unused, no. Deprecated or invalid parameters, yes. However, those are two completely different things. Primefac (talk) 14:28, 11 March 2023 (UTC)[reply]

Sifting

Hello. Can someone go through Category:All free media and find files only used in userspace but doesn't have {{Userspace file}} or {{Esoteric file}}. Place the results at User:Minorax/upf using * [[:FILENAME.EXT]] --Minorax«¦talk¦» 09:31, 12 March 2023 (UTC)[reply]

@Minorax: I've had a go using Quarry. If it's close to what you need but not quite there, you can edit the query and click the Update link top right. I excluded images which are not used at all: they are debatably "only used in userspace" but probably not what you wanted. Certes (talk) 20:36, 12 March 2023 (UTC)[reply]
 Courtesy link: quarry:query/72229Novem Linguae (talk) 20:39, 12 March 2023 (UTC)[reply]
Thanks; I should have mentioned that I used Quarry just for testing. The finished SQL query is in User:Minorax/upf, wrapped in a {{Database report}} ready for SDZeroBot to run. Certes (talk) 21:12, 12 March 2023 (UTC)[reply]
Hello. Possible to run the query again? Removing uploads of Jonathunder and those tagged with {{Keep local}}. --Minorax«¦talk¦» 10:29, 13 March 2023 (UTC)[reply]
I've removed "Keep local" files and files linked only from User:Jonathunder. (Checking who uploaded the images is possible but might slow the query dramatically.) I'm afraid it didn't eliminate much. Certes (talk) 14:02, 13 March 2023 (UTC)[reply]
Thanks. :) --Minorax«¦talk¦» 14:05, 13 March 2023 (UTC)[reply]

I started making these changes, but there is too many for non-bot edits. In addition, in the citations, it might be worth removing the link to the Internet archive and removing the parameter with the status of a dead link.

Starting point:

  • basic search with category (there is more without the category filter).
  • Search pattern: ([^/])http:\/\/(?:www\.)?itsanhonour\.gov\.au\/honours\/\w+\/.+?aus_award_id=([0-9]+)[&\w=]+
  • Replacement code: $1https://honours.pmc.gov.au/honours/awards/$2

Nux (talk) 20:21, 12 March 2023 (UTC)[reply]

@Nux, try WP:URLREQ. — Qwerfjkltalk 20:48, 12 March 2023 (UTC)[reply]
OK, sorry, missed that. Moved. Nux (talk) 20:52, 12 March 2023 (UTC)[reply]

Report for untagged episode redirects

Is it possible to get a report in my userspace for a list of redirects to pages that have a list of episodes (using one of the templates {{Episode list}} or {{Episode list/sublist}}) for which the redirects are episode redirects whose title is the same (or similar - typos, disambiguation, etc.) to the one in the |Title= parameter (of the above templates) and that don't use {{R from television episode}} or {{Television episode redirect handler}}? An example would be And a Trauma in a Pear Tree which redirects to Law & Order: Special Victims Unit (season 24). Gonnym (talk) 12:23, 13 March 2023 (UTC)[reply]

Bot for MOS:CAPTIONS

Good afternoon. Is it possible to create a bot for MOS:CAPTIONS? I have corrected many pages by applying this rule, but with almost 7 million pages it's literally impossible to do them all, so I make this proposal. JackkBrown (talk) 14:36, 14 March 2023 (UTC)[reply]

@JackkBrown: Hi there! Which portion(s) of MOS:CAPTIONS would be appropriate for a bot? Removing a caption in a biography article's infobox if it is the same as the article title? GoingBatty (talk) 14:48, 14 March 2023 (UTC)[reply]
@GoingBatty: no, if it's possible, the removal of the full stop at the end of the caption if the sentence within the caption in question is not complete, and the addition of the full stop at the end of the caption if the sentence within the caption in question is a complete sentence; I don't know whether this difference can be taught to a bot. JackkBrown (talk) 14:57, 14 March 2023 (UTC)[reply]
Fixing WP:CAPFRAG in this way seems too much like a WP:CONTEXTBOT to be feasible to me. Lee Vilenski (talkcontribs) 15:01, 14 March 2023 (UTC)[reply]
@JackkBrown: Hi. Like Mr. Lee said, it will be a context bot. But that part comes after the bot is created. Like you said, creating/teaching the bot what a meaningful sentence is would be a hassle. —usernamekiran (talk) 15:15, 14 March 2023 (UTC)[reply]
I agree with Lee. This sounds like a WP:CONTEXTBOT. It is unlikely we could teach a bot to do this with a good accuracy rate, so this probably isn't a good bot task. –Novem Linguae (talk) 02:10, 15 March 2023 (UTC)[reply]

I don't know if this is the right place to request this but here goes. In 2022, the 910 area code gained a concurrent code of 472. Could a bot do a one time edit to add this new code to the |area_code= parameter in Template:Infobox settlement for each settlement article within the region. Thanks and have a good day! DiscoA340 (talk) 22:38, 14 March 2023 (UTC)[reply]

@DiscoA340: Hi there! How do you suggest making the list of each settlement article within the region? GoingBatty (talk) 18:07, 15 March 2023 (UTC)[reply]
@GoingBatty I was thinking like how other area codes are portrayed in the infobox. Like in the article Wake Forest, North Carolina, it's in an area with two codes, so it's linked as 919, 984. So for the 910/472 area code, a bot could add ", 472" to the same link to make the link in the parameter look like "910, 472". Since it only affected one area code, I think it could be simple for a bot to find all the articles needing updating but I'm not an expert on this. Thank you and have a great day! DiscoA340 (talk) 18:18, 15 March 2023 (UTC)[reply]
@DiscoA340, @GoingBatty, insource:/\| *area_code *= *910/ gives 11 pages. — Qwerfjkltalk 18:26, 15 March 2023 (UTC)[reply]
@Qwerfjkl: Thank you!
@DiscoA340: Updated these 11 pages manually. GoingBatty (talk) 18:36, 15 March 2023 (UTC)[reply]
Thank you @GoingBatty and @Qwerfjkl, have a great day! DiscoA340 (talk) 19:25, 15 March 2023 (UTC)[reply]
@DiscoA340, @Qwerfjkl: insource:/\| *area_codes? *= *\[\[ *Area code 910/ gives us another 203 articles. GoingBatty (talk) 19:31, 15 March 2023 (UTC)[reply]
I think that is what most articles have, sorry for the miscommunication. DiscoA340 (talk) 19:34, 15 March 2023 (UTC)[reply]
@DiscoA340:  Doing... with AWB. GoingBatty (talk) 19:39, 15 March 2023 (UTC)[reply]
@DiscoA340:  Done! Any more to update? GoingBatty (talk) 20:46, 15 March 2023 (UTC)[reply]
@GoingBatty I think that's it, thank you for your help! DiscoA340 (talk) 21:10, 15 March 2023 (UTC)[reply]

Fix date format errors in templates and use of non-latin numbers in template parameters

I have beem advised to report when i requested to replace templates or values if they contain non english numerals. I am using wpcleaner to fix checkwiki errors. To my surprise, many kannada wikipedia content creators diligently added cs1/2 templates for references. With Cite button you can create references, but there is a catch. You need to manually enter all parameters. Alas, very few read them. All kind of syntax errors are unintentionally created. The issue is with "cite button" of visual editor and lack of reftoolbar on source editing. Interface admin responded positively for my demand of upgrade of them. Future date format errors might disappear. Now, the use of kannada numerals can be discouraged. Now, what happens to old errors. I request to create a bot for all indo-aryan and dravidian language wikipedias or wikis which use basic cite button which automatically [1] fixes date format either by replacing whole template data or comment it out. [2] comment out if non latin digits are used in templates. These are the 2 primary issues found by me on kannada wikipedia. రుద్రుడు (talk) 09:34, 16 March 2023 (UTC)[reply]

Regardless of whether or not ve and reftoolbar get citation support, the current version of the kn:ಮಾಡ್ಯೂಲ್:Citation/CS1/Configuration is where local kn.wiki editors can adapt the cs1|2 suite to suit their language. MediaWiki knows most month names for the various wikis so editors at kn.wiki can set local_date_names_from_mediawiki to true (already done at line 575). What has not been done at kn.wiki is local digit definition. That is accomplished by replacing the indexes in the ['local_digits'] table (line 598) with the appropriate Kannada digits (as strings). Try that before committing to a bot.
Trappist the monk (talk) 15:56, 16 March 2023 (UTC)[reply]
@Trappist the monk so most of the issue is resolved. Thank you for pointers. Hello @~aanzx can you please look into this. రుద్రుడు (talk) 16:45, 16 March 2023 (UTC)[reply]
I previously asked questions about same issue
  1. https://en.wikipedia.org/wiki/User_talk:Trappist_the_monk/Archive_6#CS1_error_for_Access_Dates_at_Kannada_Wikipedia
  2. https://en.wikipedia.org/wiki/Help_talk:Citation_Style_1/Archive_38#Access_date_error_on_kannada_wikipedia
I will go through it again and check if it fixes the issue.Thanks ~aanzx © 23:59, 16 March 2023 (UTC)[reply]