Wikisource:Bot requests/Archives/2018

Please do not post any new comments on this page. This is a discussion archive first created in 2018, although the comments contained were likely posted before and after this date. See current discussion or the archives index.

Realign pages 19 onwards of Index:Jardine Naturalist's library Bees.djvu

Following up a request at WS:S. This file has had two pages inserted before page 19 - the pages 19 onwards are now offset by 2. Could a bot move pages 19–372 upwards by two (so they become 21—374)? Inductiveload—talk/contribs 17:54, 28 March 2018 (UTC)

Done. Sorry for the missing bot flag in RC :-(.— Mpaa (talk) 17:57, 6 April 2018 (UTC)

This section was archived on a request by: — billinghurst sDrewth 05:35, 16 May 2018 (UTC)

OCR and scans are shifted by one page

Is it possible to shift the OCR for Index:A History Of Mathematical Notations Vol I (1928).djvu one page further? That is, the OCR for page n currently is shown on page n-1. Thank you. χ_chi (talk) 14:10, 10 April 2018 (UTC)

Done. OCR text aligned is djvu file.— Mpaa (talk) 21:23, 16 May 2018 (UTC)

This section was archived on a request by: — Mpaa (talk) 21:23, 16 May 2018 (UTC)

Replace <center> with {{center}}

This is a reletively common but low-priority lint error that could easilly be corrected by bot(just replace "<center>" with "{{center|" and "</center>" with "}}"). JustinCB (talk) 21:31, 18 January 2018 (UTC)

It would also need to handle any attributes of the <center> tag. JustinCB (talk) 02:14, 23 January 2018 (UTC)

not done at this time Please seek a community consensus prior to unilaterally changing works for lint issues. — billinghurst sDrewth 05:42, 23 January 2018 (UTC)

Ok, thanks anyways. JustinCB (talk) 12:29, 23 January 2018 (UTC)

This section was archived on a request by: — billinghurst sDrewth 20:59, 23 July 2018 (UTC)

Reset proofreading status of Page:s flagged by Linterrors to "Problematic"

The reasons for this are partly so that it's possible to see just how broken Wikisource is, and partly so that any fixes are properly tracked through the proofreading process.

Given that there are at least 100,000 and growing pages with Linter extension defined issues, it would be impractical for a user to mark these manually. ShakespeareFan00 (talk) 18:12, 19 January 2018 (UTC)

I hope the pages with errors isn't growing, for I'm fixing pages(except for that issue with the templates, but I don't know if that caused any significant brakeings). I think the number of high priority errors has decreased at least. JustinCB (talk) 02:22, 23 January 2018 (UTC)

Not done I don't favour this as a method to progress at this time. 1) due to the fact that the text is what we proofread and grade, not the formatting; 2) it takes two steps to validate a work, and these pages will not require that action. I do not agree with the concept that the pages are problematic in the page status step, nor that this should start as a bot discussion as a means to resolve. Please take your discussion to WS:S, and resist unilateral decision-making versus community consensus. — billinghurst sDrewth 05:39, 23 January 2018 (UTC)

I don't favor it either, for you can look at Special:LintErrors, and it would require the text to be re-proofread in addition to having their lint errors corrected. JustinCB (talk) 12:35, 23 January 2018 (UTC)

This section was archived on a request by: — billinghurst sDrewth 21:00, 23 July 2018 (UTC)

Fix Inline Templates Spanning Multiple Paragraphs

This consists of closing the template at the end of each paragraph, then re-opening it at the beginning of the next paragraph for as many paragraphs as the template spans. JustinCB (talk) 02:22, 23 January 2018 (UTC)

not done at this time; there is a discussion about linter errors in WS:S and progressing in the manner at this time, in this way, is not suitable for the corpus of the fixes required. — billinghurst sDrewth 05:34, 23 January 2018 (UTC)

Yeah, I'm doing a lot of corrections to this manually, and I'm sure others are doing it, too. By the way(Not sure if this belongs here or at another discussion), if an inline template is over an entire paragraph, any whitespace at the end of the paragraph must be either placed outside the template or removed. JustinCB (talk) 12:32, 23 January 2018 (UTC)

Thanks anyways for considering it. JustinCB (talk) 12:34, 23 January 2018 (UTC)

This section was archived on a request by: — billinghurst sDrewth 21:00, 23 July 2018 (UTC)

Removal of full stops in running headers

Requesting removal of full stops from Index:page running headers in Index:Compromises (Repplier).djvu. I have been removing them, as I remember to, when validating, but often forget. While it is *merely* header matter, I would like it to be consistent, for I plan on nominating the lot of essay works by Repplier for FT once they are fully validated. Thanks if someone can. Londonjackbooks (talk) 18:10, 8 July 2018 (UTC) Done— Mpaa (talk) 22:03, 9 July 2018 (UTC)

Thank you, @Mpaa: Londonjackbooks (talk) 09:38, 10 July 2018 (UTC)

This section was archived on a request by: — billinghurst sDrewth 21:00, 23 July 2018 (UTC)

Metamorphoses

Metamorphoses (Miller) just needs a bot to go through and create each of the pages from the existing PDF. There are over 400 pages. Too many to do by hand. Just granpa (talk) 13:38, 23 July 2018 (UTC)

@Just granpa: Please use one of the OCR tools available through your gadgets. The Google OCR tool is newly introduced and said to be better. Either that or we look to find a scan with an existing OCR layer. — billinghurst sDrewth 21:05, 23 July 2018 (UTC)

I am adding support for googleOCR in wikisourcetext.py (not merged yet, see https://gerrit.wikimedia.org/r/#/c/pywikibot/core/+/446973/). If someone wants to give it a try.— Mpaa (talk) 23:16, 23 July 2018 (UTC)

I already have the OCR tool. Like I said there are over 400 Pages. Too many to do by hand. Just granpa (talk) 06:31, 24 July 2018 (UTC)

Done with the script above.— Mpaa (talk) 22:03, 24 July 2018 (UTC)

Thank you. Saved me a lot of work. Every other page was Latin so I didn't transclude the even pages. I wasn't sure whether I was supposed to transclude the introduction so I left it out. Just granpa (talk) 09:48, 25 July 2018 (UTC)

Welcome. Per process, 'not proofread' pages should not be transcluded in Main ns. This is to avoid perception of poor quality of this site for occasional visitors. If you are going to proofread the text soon, it is OK anyhow. As side-note, I would split the different Books in subpages, otherwise it is a lot of pages to be transcluded at once.— Mpaa (talk) 21:28, 25 July 2018 (UTC)

Your bots OCR tool is making too many mistakes. Its not worth my time and energy to keep correcting it. When you get your bot working right then let me know. Just granpa (talk) 20:39, 27 July 2018 (UTC)

@Just granpa:, you need to complain with Google then. I think you have seriously underestimated the effort it takes to get a text fixed. When you get your ideas clear about it, you let me know.Mpaa (talk) 23:39, 27 July 2018 (UTC)

Do you really think I can't see what's going on here? You Are Not Invisible. Just granpa (talk) 15:58, 28 July 2018 (UTC)

This section was archived on a request by: — Mpaa (talk) 22:03, 24 July 2018 (UTC)

Move closing </poem> tag from footer into the body (Page namespace)

The poem tags don't transclude across pages. If the closing poem tag is put into the footer by someone who doesn't realize this, it'll look OK on the page: namespace, but like garbage in the main: namespace after transclusion. (Garbage = you'll see the raw open <poem> tag and then a wall of text.)

I'm trying to transclude Index:Paradise lost by Milton, John.djvu, which is fully validated, and every page has the closing poem tag in the footer. This results in transclusions that look like this: Paradise Lost (1890)/Book 2. (I fixed book 1 manually and then realized that this was a dumb idea.)

I would propose that we have a bot run through the Page namespace, identify all the places where this tag is placed in the footer, and to move it accordingly into the very bottom of the body. --Mukkakukaku (talk) 18:47, 28 October 2018 (UTC)

I have also seen pages with poem in the header. Such cases should be taken care of as well.— Mpaa (talk) 21:21, 29 October 2018 (UTC)

I have done this work for now. I think that, at the beginning at least, it might be better to run it on demand, as there might be some corner cases for headers and footers that might not be obvious to me right now.— Mpaa (talk) 21:48, 29 October 2018 (UTC)

E.g. something like <poem style="font-style:italic;"> in the header— Mpaa (talk) 23:18, 29 October 2018 (UTC)

@Mukkakukaku: is this still a required request? — billinghurst sDrewth 21:45, 7 August 2019 (UTC)

Done (so it seems)

This section was archived on a request by: — billinghurst sDrewth 11:50, 15 August 2019 (UTC)

Use of Match and split

Is it normal for the Match and Split Phe-bot to not be running, and how does one get it going again?Jasonanaggie (talk) 22:19, 20 September 2018 (UTC)

It is not normal for it not to be running (especially as I was trying to match-and split a page when I found it wasn't running). As @Phe-bot is run by @Phe, I believe pinging them should do the trick. -Einstein95 (talk) 01:07, 25 September 2018 (UTC)

@Phe, @Phe-bot: the bot is not running again (or still not running) — "match_and_split robot is not running. Please try again later." —Beleg Tâl (talk) 01:08, 4 October 2018 (UTC)

This section was archived on a request by: — billinghurst sDrewth 09:14, 29 March 2020 (UTC)