New to bots on Wikipedia? Read these primers!
Operator: Sheep8144402 ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 16:08, Friday, October 21, 2022 ( UTC)
Function overview: Fix any font tag Linter error
Automatic, Supervised, or Manual: automatic, may be supervised to reduce mistakes
Source code available: User:SheepLinterBot/1 for regexes, User:SheepLinterBot/1/Signature submissions#Completed per the table
Links to relevant discussions (where appropriate): 1 (especially this) 2 3 4
Edit period(s): varies
Estimated number of pages affected: varies, usually few hundred to few thousand for one sig, millions in total
Namespace(s): any applicable that have obsolete font tags linter errors updated 26 November 2022
Exclusion compliant (Yes/No): no
Function details: (This BRFA was originally made to fix TWA-related linter errors but was withdrawn (and postponed) because I kinda changed my mind back then.) Fixes any signature with font tag linter errors I may request that the bot fix, so the estimated number of pages may vary per sig. The linter errors it fixes varies depending on what I put in the queue, although I may use regex expressions to try to clear all the other font tags linter errors at once.
Originally it replaces MalnadachBot 12 due to issues involving many edits in a single page to fix linter errors; you can see here why the bot makes many edits to a single page to fix linter errors. Some of the regexes come from here to start and then I came up with more to minimize the number of font tags being left over after an edit.
Edit as of 22 December 2022: Originally it was planned that I fix signatures that have other linter errors as well, but because doing such on base user talk pages triggers the "you have new messages" notification even when the edit is minor for my main account, I will also request approval to fix signatures that have other Linter errors as well, i.e. missing end tags. Actually, nevermind; that is gonna be left for MalnadachBot 12. This bot task aims to take over MalnadachBot fixing font tags.
Also note that it may take a few days to build those regexes because in reality I have a lot of work to get done so I may have less time to build those regexes and put them all at once. Sheep ( talk) 11:54, 25 October 2022 (UTC) reply
If you have made more such edits from your main account, please fix them. IMO it is okay if the bot skips more pages, the important thing should be that the bot does not replace one error with another. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ ( talk) 15:00, 3 December 2022 (UTC) reply
insource:/\<font/
is not ideal then, so maybe we come up with a plan; I have
this page where you can submit signatures that Approved for extended trial (100 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Primefac ( talk) 11:24, 11 January 2023 (UTC) reply
<b>[[User:Deiz|<FONT STYLE="verdana" COLOR="#000000">Dei</FONT><FONT COLOR="#FF3300">zio</FONT>]]</b>
can be caught by regexes and turns into <b>[[User:Deiz|<span style="verdana;color:#000000;">Dei</span><span style="color:#FF3300;">zio</span>]]</b>
, but I don't know if that is the correct replacement for the signature since font style="verdana" isn't correct. In earlier times, whenever I stumbled with that signature, I would replace it with <b>[[User:Deiz|<span style="font-family:verdana;color:#000000;">Dei</span><span style="color:#FF3300;">zio</span>]]</b>
since "verdana" is a font face and I thought it would be acceptable to use "font-family" CSS as the replacement. And in later times I thought it was not valid so I just replaced it with <b>[[User:Deiz|<span style="color:#000000;">Dei</span><span style="color:#FF3300;">zio</span>]]</b>
. I do not know what I should go with.<b>[[User:Deiz|<span style="color:#000000;">Dei</span><span style="color:#FF3300;">zio</span>]]</b>
. The trial looks good otherwise.
ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (
talk)
02:18, 12 January 2023 (UTC)
reply
The very last test of 300 edits before this bot task is approved is now complete. Here are the results:
Test of 300 edits | Regexes used | Edits % (ratio) |
---|---|---|
15 December 2022 | Special:Permalink/1127480757 | 60.5% (1:1.653) |
15 January 2023 | Special:Permalink/1133798228 | 65.6% (1:1.525) |
18 January 2023 | Special:Permalink/1134207566 | 63.1% (1:1.585) |
1 page was skipped due to characters in the Unicode Private Use Area, and 1 page was skipped due to not having font tags (there was a false positive when trying to get pages with font tags), so they had to be discounted in the ratio. Also, I had to manually skip one page due to two consecutive span tags in a wikilink when trying to fix font tags wrapping one wikilink and text around it. Apparently with the font style/class regex, a signature ended up getting replaced with span tags outside a wikilink. So either I have to make it two separate regexes, or you can submit the signature to my submission page so the bot can get the fix correct.
Regexes are made to ignore external/interwiki links, images, nowiki, math and hidden comments. To know how strong my regexes are, I use two things for two scenarios. If the bot was made to not skip pages with font tags, I would use the font tag percentage. If the bot was made to skip pages with font tags, I would use the edit-to-page ratio. Currently I use the ratio because I will make the bot skip pages with font tags; it's better for other editors complaining about MalnadachBot making many edits to a single page to fix font tags, doing such creates fewer errors when editing pages, and it is also easier to calculate. After the last test of 300 edits, either this BRFA can move on to the last extended trial, with half of the edits made with random pages and the other half from the sample, or it can go to straight approval. Sheep ( talk • he/him) 13:29, 18 January 2023 (UTC) reply
{{ BAG assistance needed}} No edit by BAG since seven and a half days. Sheep ( talk • he/him) 00:12, 20 January 2023 (UTC) reply
New to bots on Wikipedia? Read these primers!
Operator: Sheep8144402 ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 16:08, Friday, October 21, 2022 ( UTC)
Function overview: Fix any font tag Linter error
Automatic, Supervised, or Manual: automatic, may be supervised to reduce mistakes
Source code available: User:SheepLinterBot/1 for regexes, User:SheepLinterBot/1/Signature submissions#Completed per the table
Links to relevant discussions (where appropriate): 1 (especially this) 2 3 4
Edit period(s): varies
Estimated number of pages affected: varies, usually few hundred to few thousand for one sig, millions in total
Namespace(s): any applicable that have obsolete font tags linter errors updated 26 November 2022
Exclusion compliant (Yes/No): no
Function details: (This BRFA was originally made to fix TWA-related linter errors but was withdrawn (and postponed) because I kinda changed my mind back then.) Fixes any signature with font tag linter errors I may request that the bot fix, so the estimated number of pages may vary per sig. The linter errors it fixes varies depending on what I put in the queue, although I may use regex expressions to try to clear all the other font tags linter errors at once.
Originally it replaces MalnadachBot 12 due to issues involving many edits in a single page to fix linter errors; you can see here why the bot makes many edits to a single page to fix linter errors. Some of the regexes come from here to start and then I came up with more to minimize the number of font tags being left over after an edit.
Edit as of 22 December 2022: Originally it was planned that I fix signatures that have other linter errors as well, but because doing such on base user talk pages triggers the "you have new messages" notification even when the edit is minor for my main account, I will also request approval to fix signatures that have other Linter errors as well, i.e. missing end tags. Actually, nevermind; that is gonna be left for MalnadachBot 12. This bot task aims to take over MalnadachBot fixing font tags.
Also note that it may take a few days to build those regexes because in reality I have a lot of work to get done so I may have less time to build those regexes and put them all at once. Sheep ( talk) 11:54, 25 October 2022 (UTC) reply
If you have made more such edits from your main account, please fix them. IMO it is okay if the bot skips more pages, the important thing should be that the bot does not replace one error with another. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ ( talk) 15:00, 3 December 2022 (UTC) reply
insource:/\<font/
is not ideal then, so maybe we come up with a plan; I have
this page where you can submit signatures that Approved for extended trial (100 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Primefac ( talk) 11:24, 11 January 2023 (UTC) reply
<b>[[User:Deiz|<FONT STYLE="verdana" COLOR="#000000">Dei</FONT><FONT COLOR="#FF3300">zio</FONT>]]</b>
can be caught by regexes and turns into <b>[[User:Deiz|<span style="verdana;color:#000000;">Dei</span><span style="color:#FF3300;">zio</span>]]</b>
, but I don't know if that is the correct replacement for the signature since font style="verdana" isn't correct. In earlier times, whenever I stumbled with that signature, I would replace it with <b>[[User:Deiz|<span style="font-family:verdana;color:#000000;">Dei</span><span style="color:#FF3300;">zio</span>]]</b>
since "verdana" is a font face and I thought it would be acceptable to use "font-family" CSS as the replacement. And in later times I thought it was not valid so I just replaced it with <b>[[User:Deiz|<span style="color:#000000;">Dei</span><span style="color:#FF3300;">zio</span>]]</b>
. I do not know what I should go with.<b>[[User:Deiz|<span style="color:#000000;">Dei</span><span style="color:#FF3300;">zio</span>]]</b>
. The trial looks good otherwise.
ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (
talk)
02:18, 12 January 2023 (UTC)
reply
The very last test of 300 edits before this bot task is approved is now complete. Here are the results:
Test of 300 edits | Regexes used | Edits % (ratio) |
---|---|---|
15 December 2022 | Special:Permalink/1127480757 | 60.5% (1:1.653) |
15 January 2023 | Special:Permalink/1133798228 | 65.6% (1:1.525) |
18 January 2023 | Special:Permalink/1134207566 | 63.1% (1:1.585) |
1 page was skipped due to characters in the Unicode Private Use Area, and 1 page was skipped due to not having font tags (there was a false positive when trying to get pages with font tags), so they had to be discounted in the ratio. Also, I had to manually skip one page due to two consecutive span tags in a wikilink when trying to fix font tags wrapping one wikilink and text around it. Apparently with the font style/class regex, a signature ended up getting replaced with span tags outside a wikilink. So either I have to make it two separate regexes, or you can submit the signature to my submission page so the bot can get the fix correct.
Regexes are made to ignore external/interwiki links, images, nowiki, math and hidden comments. To know how strong my regexes are, I use two things for two scenarios. If the bot was made to not skip pages with font tags, I would use the font tag percentage. If the bot was made to skip pages with font tags, I would use the edit-to-page ratio. Currently I use the ratio because I will make the bot skip pages with font tags; it's better for other editors complaining about MalnadachBot making many edits to a single page to fix font tags, doing such creates fewer errors when editing pages, and it is also easier to calculate. After the last test of 300 edits, either this BRFA can move on to the last extended trial, with half of the edits made with random pages and the other half from the sample, or it can go to straight approval. Sheep ( talk • he/him) 13:29, 18 January 2023 (UTC) reply
{{ BAG assistance needed}} No edit by BAG since seven and a half days. Sheep ( talk • he/him) 00:12, 20 January 2023 (UTC) reply