Wikisource:Bot requests/Archives/2021

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

Conversion of article names that do not use a standard single quote mark

This section was archived on a request by: Xover (talk) 18:08, 30 March 2021 (UTC)

This are for articles in Royal Naval Biography that use other single quotes instead of ' single quote ' Here are two examples:

The M‘Farland currently uses left single quotation mark ‘ ‘
The O’Neill currently uses right single quotation mark ’ ’

These may be only two examples in the whole lot but I don't know how to check the rest. If there are more, those articles need to be moved to ' single quote '

I was going to suggest checking A Naval Biographical Dictionaryas well, but the creators of those articles seem to have used Mc etc:

A Naval Biographical Dictionary/McFarland, James — which appears in the text as James M‘Farland (‘)

so avoiding the use of single quotes completely. --PBS (talk) 16:06, 30 March 2021 (UTC)

@PBS: There were only about 35 of these so I've gone ahead and moved them, leaving redirects at the curly-quoted name since that's what the internal links use. Please check that the ones you've seen / find look ok (in case I've misunderstood / messed up somewhere). --Xover (talk) 18:01, 30 March 2021 (UTC)

I only know about the two I listed here, so thank you. -- PBS (talk) 18:06, 30 March 2021 (UTC)

Conversion of {{FI}} to {{large image}}

This section was archived on a request by: Xover (talk) 18:07, 30 March 2021 (UTC)

Now that User:Inductiveload has created the template {{large image}} which is less storage- and bandwidth-heavy than {{FI}}, I am converting all the templates in the 5+ volumes of Once a Week that I did so far. There are quite a lot that are all the exact same pattern, except that I wasn’t consistent about top and bottom margins, so I hope a bot can take care of them. It would be like so (note that this only applies to images that have no caption):

1. Convert to {{large image|[[File:filename|500px|center]]|max-width=100%|style=margin-top: Npx; margin-bottom: Mpx;}}

EITHER {{FI|file=filename|width=500px|cstyle=margin-top:Npx;margin-bottom:Mpx}}
OR {{FI|file=filename|width=100%|cstyle=margin-top:Npx;margin-bottom:Mpx;max-width:500px}}

2. Convert to {{large image|[[File:filename|450px|center]]|max-width=90%|style=margin-top: Npx; margin-bottom: Mpx;}}

EITHER {{FI|file=filename|width=450px|cstyle=margin-top:Npx;margin-bottom:Mpx}}
OR {{FI|file=filename|width=90%|cstyle=margin-top:Npx;margin-bottom:Mpx;max-width:450px}}

3 etc. The same for 400px/80%, 375px/75%, 350px/70%, and 300px/60%.

Levana Taylor (talk) 19:42, 15 February 2020 (UTC)

Done. Mpaa (talk) 16:19, 16 February 2020 (UTC)

Thank you very much! But I don't see why Volume 9, page 220 didn’t get fixed, for just one example. The bot only found things in volumes 5, 7, and 8, and I know I used the same pattern elsewhere. One problem I see is that the {{FI}} in Volume 2 contain the (useless) parameter "align = center," see Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/633 for an instance, but that doesn’t apply to volume 9. Levana Taylor (talk) 16:29, 16 February 2020 (UTC)

Done. 1) I wrongly assumed all pages were starting with "Page:Once a Week Volume", 2) parameters were in different positions, I assumed only above cases were to be found.

The following are left out, in addition to the ones with caption, please take a look at them. I checked a couple and they have 'alt' param or 'min-width:500px;max-width:675px;' or similar.

Cheers. Mpaa (talk) 21:57, 17 February 2020 (UTC)

This list is done. Levana Taylor (talk) 01:43, 18 February 2020 (UTC)

This is great! Do you plan to add support for captioning? Or is there a major obstacle to that? -Pete (talk) 22:15, 17 February 2020 (UTC)

Thank you Mpaa! If the only additional parameter in addition to the patterns you already used is "caption," the output pattern would be as follows, for the style in OAW (Inductiveload deliberately didn’t build captions into Largeimage so as to keep it stripped down & allow separate formatting of the captions):
<div style="margins">
{{large image|[[File:filename|width(px)|center]]|max-width=width(percent)}}
{{c|{{fs90|caption}}}}
</div>

Levana Taylor (talk) 00:35, 18 February 2020 (UTC)

Done. Left:

Mpaa (talk) 21:11, 18 February 2020 (UTC)

Umm… when in the above output pattern I wrote <div style="margins"> I meant, for example, <div style="margin-top:25px; margin-bottom:20px;"> but you literally put <div style="margins"> everywhere! Levana Taylor (talk) 23:33, 18 February 2020 (UTC)

<sigh> You changed notation so I thought you really meant it like that. Not easy to fix automatically, will be faster by hand than to implement the logic. What I can easily do is to replace "margins" using a default of 20px&20px for top&bottom as it is the most popular choice. Otherwise, it needs to be done by hand, looking at MpaaBot contributions on Feb,18, looking at the delta in history comparison and copy it to the latest revision. Sorry about that.Mpaa (talk) 08:17, 19 February 2020 (UTC)

Sorry about being confusing! I would prefer top:25px, bottom:20px which works best for the new way of doing captions. Using that should be plenty good enough for 99 out of 100 pages. Levana Taylor (talk) 09:41, 19 February 2020 (UTC)

Done (maybe :-) ). Mpaa (talk) 17:43, 19 February 2020 (UTC)

Great! Thank you very much for spending so much time working on this. Would it take you long to pull up a list of any OAW pages that still contain {{FI}} or its sister template {{FIS}}? (I am still working on converting a few of the more complex uses of FIS to Img float or something else). Levana Taylor (talk) 18:00, 19 February 2020 (UTC)

See this query. Mpaa (talk) 20:20, 19 February 2020 (UTC)

OK. For now I will continue using {{FI}}, and assume that at some point somebody will figure out the most straightforward way to add captions. I'm not worried about formatting for most of the stuff I do, I just want it to look more or less OK -- much more interested in making high quality text and graphics available to the masses. -Pete (talk) 08:26, 19 February 2020 (UTC)

Stray unprintable characters or non-standard spaces in section headers

This section was archived on a request by: Xover (talk) 06:40, 31 March 2021 (UTC)

Would you it be possible to try to standardize spaces to ASCII 32 for all section headers in:

Sample change: [1][2]. This would have the advantage that the article title matches the section header. Also, while editing the pages, it might be worth putting them the category for the work (Category:A Naval Biographical Dictionary). Thanks! Jura1 (talk) 23:24, 5 April 2020 (UTC)

@Jura1: The issue with the proposal is that changing the tag in the Page: namespace will require exactly the same change to the article in section tag in the transclusion, the one in the section parameter. Then we will be needing to move the pages so the pagename matches the section and transclusion, which then will mean editing each preceding and next articles for the respective next and previous links. That is a lot of work, and fraught with risks of breaking transclusions and not knowing what is borken, and where. (FWIW I checked a few pagenames and the same spaces appear in the name, and the section, which is not surprising as they will have been built from the same master list. I am not seeing the "difference" problem that you are identifying.)

With regard to categorisation, it has not been our practice to categorise each subpage of a work with a parent category, especially as tools are able to drill down levels in categories. The subpage itself does that categorisation, and I am not certain of the benefit that you envisage from the proposed categorisation for the community. Such an output replicates an existing index (in the work, or curated), or a table of contents, or the special:prefixindex that you generated earlier.

I do agree that the non-standard spaces is not ideal, I don't think that the proposed solution has the value to undertake. I do not see that things are broken, eg. broken searches, or the lookahead typing. In fact, I say that your changes are problematic when you undertake then if we undo your edits, we then have to undo, undo, undo, undo, undo as a chain reaction. Maybe you should stop doing something without demonstrated value. — billinghurst sDrewth 11:30, 6 April 2020 (UTC)

Maybe it's just query server that is broken and not the browser correcting it on the fly.

If it's preferred to revert things over sorting things out .. do whatever you prefer. Jura1 (talk) 11:42, 6 April 2020 (UTC)

I don't want to be in a situation with half-fixes, as there is an ugly complexity, to moves and fixes and aligning headers, and related pages, and each linked set of 3 curated pages. The intra-related nature of our works in main namespace means that half-fixes can kill pages. We really need concerted and considered efforts with changes, and a clear value which outweighs doing nothing. — billinghurst sDrewth 12:59, 6 April 2020 (UTC)

I dug into this a bit, and it turns out that MediaWiki has special syntax magic for non-breaking spaces: both normal ASCII space and non-breaking space are converted to underscore in links (good luck finding that documented anywhere!). In other words, Main Page and Main Page (and even Main Page) are equivalent. This means we can actually replace the non-breaking spaces in the source in both mainspace and Page: and it should just work (no page moves needed). Worst case we'll have to touch edit some pages to force them to update. There are also just ~20 Page: pages and ~60 mainspace pages affected by this so if worse comes to worse it's feasible to reverse any changes manually.

I'll take a stab at it tomorrow if time allows, or in the next couple of days in any case. --Xover (talk) 21:56, 30 March 2021 (UTC)

Done and checked. Thanks to this bit of MW syntax magic it turned out to be pretty straightforward after all. --Xover (talk) 06:40, 31 March 2021 (UTC)

Template:Header to Template:Translation header

This section was archived on a request by: Xover (talk) 20:44, 2 April 2021 (UTC)

We have a situation that I am parking here for broader consideration, especially as it is not one that I have the best familisarisation. We have moved numbers of main ns works to the Translation namespace due to their being Wikisource-sourced translations. Numbers have been moved and not converted to use {{translation header}}. They take a little bit of manipulation based on knowledge of the works, though that should be evident from the language of the work. We need to review https://en.wikisource.org/w/index.php?title=Special:WhatLinksHere/Template:Header&namespace=114&limit=500 and automate those that can be automated, and either manual update the remainder, or look to populate with information that allows for automation. — billinghurst sDrewth 01:35, 15 January 2016 (UTC)

Can someone who likes working in Translation: ns please advise on the requirements for converting these works. There will be something like "header" to "translation header"; addition of language parameter (and use the categorisation to determine that parameter). What else needs to happen? — billinghurst sDrewth 21:56, 7 August 2019 (UTC)

In order to make working with this backlog slightly more convenient, I've temporarily added a tracking category for pages in the Translation: namespace (ns:114) that transclude {{header}}. Category:Translations using plain header template is still populating (will take a while), but can be used to track this backlog. If someone comes up with good requirements for these conversions we could probably profitably add the instructions to the category page (if there are manual steps involved). --Xover (talk) 12:49, 31 March 2021 (UTC)

Hmm. At the very least we'll need to add |language= and |original=. By policy |original= should be an interwiki link to the untranslated text on |language= Wikisource, but in practice this will be extremely rare so this will only be an empty but required parameter. ~~We also need to make sure |translator= is set, and that it is not set to anything except "wikisource".~~ We could probably also blindly add {{incomplete translation}} and be right far more often than we are wrong, but that's a different matter. --Xover (talk) 13:51, 31 March 2021 (UTC)

Ah, no, the |translator= parameter should simply not be there; Wikisource translation is hard-coded for {{translation header}}. --Xover (talk) 13:58, 31 March 2021 (UTC)

And |language= and |original= are used to autogenerate an interwiki link, so any manual interwiki in the old syntax should be removed. We need to check up on using Wikidata for IW on translations too, but that's a separate issue (it affects all translations, not just this subset). --Xover (talk) 14:10, 31 March 2021 (UTC)

Also need to keep an eye out for page name and |language=. Both should be the translated one (English), not the original (that goes in |original=). --Xover (talk) 14:15, 31 March 2021 (UTC)

Hmm. Do we have a convention for how to list Wikisource translations on Author: pages? --Xover (talk) 14:19, 31 March 2021 (UTC)

Done Thanks to the efforts of (among others) CalendulaAsteraceae, all 1400+ of these have now been converted to {{translation header}} (or {{translation subpage}}) and the tracking category (which I'll nuke shortly) is empty. Yay! Good job everyone! --Xover (talk) 20:43, 2 April 2021 (UTC)

Mass delete The despatches of Hernando Cortes.djvu

This section was archived on a request by: Xover (talk) 09:34, 2 April 2021 (UTC)

Requesting the deletion all the pages of Page:The despatches of Hernando Cortes.djvu/2 etc. — Ineuw (talk) 02:43, 2 April 2021 (UTC)

Doing… --Xover (talk) 09:24, 2 April 2021 (UTC)

Done --Xover (talk) 09:33, 2 April 2021 (UTC)

Move "left page breaks" to {{pagenum}}

The (mostly historical) use of {{page break|x|left}} is overloading the page break template with a non-breaking function. This is now delegated to {{pagenum}}, which makes the page numbers compatible with H:LAYOUT.
Task: convert simple usages of anything of the format {{page break|x|left}} to {{pagenum|x}}.
Instances of the former can be found in Category:Page breaks with number indicated on the left.

Inductiveload—talk/contribs 08:20, 25 August 2021 (UTC)

preparing list list preparation. (we should really categorise things like this). — billinghurst sDrewth 13:36, 25 August 2021 (UTC)

Done — billinghurst sDrewth 13:10, 27 August 2021 (UTC)

Thank you: Template and docs updated. Inductiveload—talk/contribs 13:20, 27 August 2021 (UTC)

This section was archived on a request by: — billinghurst sDrewth 13:10, 27 August 2021 (UTC)

ReOCR Index:The Son of Tarzan.djvu

A preliminary evaluation of the OCR shows that it yields almost flawless results. Therefore, I'm asking to reOCR the work to prepare it for the November MC. Languageseeker (talk) 22:37, 7 October 2021 (UTC)

@Languageseeker:, I think it is no longer necessary. I have cleaned up the text, added {{rh}}, chapters, etc.; it is in pretty good shape. Images are needed though. Mpaa (talk) 22:56, 9 October 2021 (UTC)

@Mpaa: Request Withdrawn. Thank you for your work on this text. Languageseeker (talk) 02:27, 18 October 2021 (UTC)

This section was archived on a request by: withdrawn — billinghurst sDrewth 13:33, 18 October 2021 (UTC)

ReOCR Index:This side of paradise (IA sideofparadise00fitzrich).pdf

This is a text that has no proofreading done on it. The OCR is from 2006 and is of quite poor quality. I am requesting that the text be reOCRed. Since the image quality is quite poor, it also might make sense to create a fresh DJVU from the IA scans. Languageseeker (talk) 02:27, 18 October 2021 (UTC)

Not done I am unaware of anyone having an OCR bot. For the new version of the output, best to put a request to [[[WS:S]] rather than here. — billinghurst sDrewth 13:32, 18 October 2021 (UTC)

The text for the djvu version seems OK to me. Maybe reuploading the djvu file is enough. Mpaa (talk) 17:58, 18 October 2021 (UTC)

This section was archived on a request by: Mpaa (talk) 22:17, 16 January 2022 (UTC)

Add headers/footers Merge multiple gap templates

Can somebody add Index:Fragment of a novel written by Jane Austen.pdf {{rh/1|( )}} to the header and {{right|}} to the footer from Page 101 to 187. Languageseeker (talk) 18:16, 29 December 2021 (UTC)

Done Mpaa (talk) 14:30, 30 December 2021 (UTC)

This section was archived on a request by: Mpaa (talk) 22:17, 16 January 2022 (UTC) Mpaa (talk) 22:17, 16 January 2022 (UTC)

Merge multiple gap templates

The following discussion is closed:

The requested action was evidently controversial, so consensus needs to be established before it is actionable.

Some editors have been using multiple instances of {{gap}} (i.e. ) {{gap}}{{gap}}{{gap}}{{gap}}{{gap}} instead of {{gap|10em}}. Can a bot please fix these, as in this edit? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:21, 27 April 2021 (UTC)

We can get a bot to do the fix, though finding the pages is the issue. I am unaware of a tool that counts the uses of a template on a page and judges its correctness. If you have a list of pages, or you have /special:prefixindex/ then I can have a look to see what we can do. — billinghurst sDrewth 13:14, 24 May 2021 (UTC)

Being pedantic, one reason to repeat "gap" is to be sure that several "gap"s always give a multiple spacing of "gap", regardless of the default value, should this be changed in future (e.g. see a case like Page:The complete poems_of Emily Bronte.djvu/112). It depends on how likely this scenario is and possible consequences. Maybe a 'per work' approach would be more robust, making explicit the spacing also in case of a single "gap"? Mpaa (talk) 20:03, 5 September 2021 (UTC)

The opposite is true; if the default gap changes, then multiples of it will change at the same time; but 10em will always be 10em. As for finding them, the bot would need to scan all pages that transclude the template. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:43, 6 September 2021 (UTC)

Then, in the page I posted, you also need to explicitly state the spacing for the 'single gap' occurrences, not just collapse the 'multiple gaps'.Mpaa (talk) 20:15, 6 September 2021 (UTC)

@Pigsonthewing: It would have been polite to advise me, for what you termed 'abuse' of gap or whatever, I couldn't decide if you were joking. I do this habitually and happy to discuss why … elsewhere. CYGNIS INSIGNIS 21:57, 5 September 2021 (UTC)

Why would I? This is a generic issue, not a complaint about your behaviour. If you have objections, you should raise them here, or they are likely to be overlooked. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:43, 6 September 2021 (UTC)

I am not sure why this request was controversial, but as it evidently was I am going to tag it as resolved at some point fairly soon. To get it actionable it needs to be hashed out to a consensus, probably on WS:S, addressing both the preference for using multiple {{gap}} templates and the technical concern raised about its defaults etc. Xover (talk) 10:31, 10 April 2022 (UTC)

This section was archived on a request by: --Xover (talk) 05:28, 3 September 2022 (UTC)

Wikisource:Bot requests/Archives/2021

Contents