Wikisource:Administrators' noticeboard

(Redirected from Wikisource:AN)
Administrators' noticeboard

This is a discussion page for coordinating and discussing administrative tasks on Wikisource. Although its target audience is administrators, any user is welcome to leave a message or join the discussion here. This is also the place to report vandalism or request an administrator's help.

  • Please make your comments concise. Editors and administrators are less likely to pay attention to long diatribes.
  • This is not the place for general discussion. For that, see the community discussion page.
  • Administrators please use template {{closed}} to identify completed discussions that can be archived
Report abuse of editing privileges: Admin noticeboard | Open proxies
Wikisource snapshot

No. of pages = 3,831,489
No. of articles = 956,504
No. of files = 19,507
No. of edits = 12,417,617

No. of pages in Main = 557,125
No. of pages in Page: = 2,823,347
No. validated in Page: = 549,855
No. proofread in Page: = 978,405
No. not proofread in Page: = 1,051,093
No. problematic in Page: = 38,267
No. of validated works = 5,637
No. of proofread only works = 4,595
No. of pages in Main
with transclusions = 349,926
% transcluded pages in Main = 62.81
Σ pages in Main

No. of users = 3,039,948
No. of active users = 377
No. of group:autopatrolled = 484
No. in group:sysop = 22
No. in group:bureaucrat = 3
No. in group:bot = 16

Checkuser requestsEdit

  • Wikisource:checkuser policy
  • At this point of time, English Wikisource has no checkusers and requests need to be undertaken by stewards
    • it would be expected that requests on authentic users would be discussed on this wiki prior to progressing to stewards
    • requests by administrators for identification and blocking of IP ranges to manage spambots and longer term nuisance-only editing can be progressed directly to the stewards
    • requests for checkuser

Bureaucrat requestsEdit

Page (un)protection requestsEdit

Requesting page protection for {{left sidenote}} and {{right sidenote}}Edit

Given what happened (see above) I am of the view that as highly visible and widely used templates, these along with their respective style-sheets should be protected from general editing, with someone appropriate identifying a STABLE version and then protecting that version. Thanks.ShakespeareFan00 (talk) 09:46, 2 June 2021 (UTC)


Interface administratorsEdit

Hi. Please see I do not remember if this was already discussed and how it is going to be addressed. Comments and suggestions welcome.   Comment As far as I am concerned I would trust any admin who feels skilled and confident enough to tackle such edits.— Mpaa (talk) 21:05, 29 October 2018 (UTC)

I can handle the technical aspects of it. However, it can take me a while to get around to tasks that take longer than a few minutes, so I don't want to create a false expectation of being able to handle time sensitive matters on my own. —Beleg Tâl (talk) 02:35, 30 October 2018 (UTC)

We should decide how to address the fact that EnWS has no m:interface administrators. I see basically the following options. Please add/amend as you feel appropriate.

Option A - Assign right on demand when needed

Option B - Assign right permanently to willing Admins, to be reviewed in the confirmation process

As I said above, I am for the simplest one.— Mpaa (talk) 21:28, 30 October 2018 (UTC)

Option C - Assign right permanently to selected Admins, after approval process, to be reviewed in the confirmation process

Option C sounds like you're being volunteered (based on the lack of the word 'willing'). ;) --Mukkakukaku (talk) 06:27, 31 October 2018 (UTC)

Option D - assign the rights to all the admins, who have already been vetted for community approval, and then whoever has the ability and desire can make use of it as they will and as needed. —Beleg Tâl (talk) 13:33, 31 October 2018 (UTC)

Option D would make the most sense for us. For anyone to get themselves to the point that we trust them with the admin tools just so that they can mess around in the interface, they would be playing a very long game. Beeswaxcandle (talk) 22:05, 2 November 2018 (UTC)
I agree with Beeswaxcandle, Option D, although I would also be fine with the right only going to admins who express an interest. BD2412 T 23:00, 2 November 2018 (UTC)
It is so rare I disagree with Beeswaxcandle but this must be one of those times. The whole point of this change is to prevent the ignorant from accidentally screwing up - insulting as the implications undoubtedly are! As such under the new regime trust is no longer enough; perhaps somebody ought to draw up some kind of eligibility examination…? 23:03, 2 November 2018 (UTC)
That hasn't been an issue for us yet, and accidental changes are easily reversed. If we had more users it would be more of a problem, but as it stands this kind of distinction is more cumbersome than helpful in my opinion. —Beleg Tâl (talk) 00:08, 3 November 2018 (UTC)
As much as I like the idea of making all existing admin interface admin, IA were separated from regular adminship specifically to reduce attack surface(from hackers), and it was pretty dangerous if the access fell into the wrong hand, I'd rather propose having existing admin request right from bureaucrat and could be granted at the bureaucrat's discretion, and should be automatically removed if no action after two month.Viztor (talk) 02:13, 10 August 2019 (UTC)
  •   Comment we discussed it when the rights were split, and it was agreed that it could be assigned on a needs basis. That has been done at least once for me with the temporary assignation of the IA rights. — billinghurst sDrewth 05:58, 10 August 2019 (UTC)
    Note that WMF Legal requires 2FA to be enabled for users who are to be assigned this right, so bureaucrats will have to verify this before doing so. MediaWiki's 2FA implementation is also sufficiently finicky that one may not want to enable it without proper consideration. --Xover (talk) 08:21, 10 August 2019 (UTC)
    What's wrong with the 2FA implementation? I haven't had any issues with it at all. —Beleg Tâl (talk) 22:17, 10 August 2019 (UTC)
    Ah, sorry, I should have been more clear. I am going on hearsay, mostly from admins on enwp (a crotchety bunch if ever there was one), and my own assessment of the documentation at meta. The main complaints are that the implementation in general is a little bit primitive (as is to be expected since WMF rolled their own instead of federating with one of the big providers), and that there is no way to regain access to your account if something goes wrong with the 2FA stuff (if your phone is stolen etc.) unless you happen to know one of the developers personally. None of these are in themselves showstoppers, and many people are using it entirely without issue. The phrasing sufficiently finicky that one may not want to enable it without proper consideration was not intended to discourage use, but merely to suggest that it is worthwhile actually giving it a little thought before requesting it be turned on. --Xover (talk) 17:52, 11 August 2019 (UTC)
    Okay, gotcha. As it happens, Wikimedia 2FA does include emergency access codes for use when your phone is unavailable. —Beleg Tâl (talk) 19:56, 11 August 2019 (UTC)

Formal requirements related to 2FAEdit

Picking up this again…

I finally got so annoyed by our inability to fix even simple stuff stuff that requires Interface Admin permissions that I hopped over to meta to figure out what the actual requirements are (versus the should stuff). As it turns out, the 2FA stuff is (surprise surprise) as half-baked as most such Papal bulls from the WMF: 2FA is required for intadmin, but there is no way for bureaucrats to actually check whether an account has that enabled. The result of this is that even on enwp (where they take this stuff really seriously) they do not actually try to verify that 2FA is enabled before they hand the permission out: they check that the user is in the right group so that they can turn on 2FA, remind the person in question of the requirement, but otherwise take it on faith (trust). There's a request in for the technical capability to verify 2FA (and I think Danny is even working on it), but it seems mostly everyone's waiting for 2FA to be enforced by the software.

Meanwhile, anyone with existing advanced permissions (i.e. +sysop) have the capability to enable 2FA, and anyone with a particular reason (e.g. that they need it to get Interface Administrator permission) can apply to be a "2FA Tester" and thus gain the ability to turn it on.

The net result is that our bureaucrats (ping Hesperian and Mpaa) can assign this permission so long as we somehow somewhere make at least a token effort to make sure those getting the bit have 2FA enabled. Whether that's an addition to, or footnote on, Wikisource:Adminship, or the bureaucrats asking/reminding the user when it comes up, or… whatever… I have no particular opinion on. Since the previous community discussions have been actively adverse to regulating this stuff in detail, and absent objections, I think "Whatever Hesperian and Mpaa agree on" is a reasonable enough summary of consensus.

I still think we should have an actual policy for Interface Administrators (or section on it in Wikisource:Adminship) and some facility for permanently assigning the permission (ala. +sysop; but intadmin tasks are not one-and-done like +sysop tasks, they often require iterative changes over time and need to fit into a overall architecture), but so long as there is no appetite for that, something that we can point to and say "That's how we handle the 2FA requirement" if the WMF should ever come asking. --Xover (talk) 07:37, 10 February 2020 (UTC)

  Question Is there anything further that the community thinks we need to discuss? — billinghurst sDrewth 01:36, 1 October 2021 (UTC)

I just added Special:Diff/11740077 as a quickrestatement of meta:Interface administrators, which is already linked from the top of Wikisource:Interface administrators. Basically "you should be using 2FA". If there are more formal ways to check in future, then we can update the information. FWIW, I have it on, which is a little annoying when I accidentally fat-finger the logout button, but otherwise seems unproblematic. Inductiveloadtalk/contribs 07:46, 1 October 2021 (UTC)
Should? "Required" is my understanding. There was a heated phabricator ticket about the WMF moving to have the allocation undertaken by stewards following their checking for 2FA being in place, rather than local 'crats. The counter argument was that local crats snould be able to check status and apply the rights. The ticket is stalled as a rethink is seemingly in play. — billinghurst sDrewth 08:14, 1 October 2021 (UTC)
It's a paraphrase of what I wrote, but I changed the text there to "required" since it's not just an expectation. Inductiveloadtalk/contribs 10:08, 1 October 2021 (UTC)

Request moveEdit

Hello. Could you please move "Siamese Interim Administrative Charter Act, Buddhist Era 2475 (1932)" to "Translation:Act on Interim Charter for Public Administration of Siam, 2475 Buddhist Era" and change its namespace from "main" to "translation"? Thank you so much. --KhaoNiaoMaMuang (talk) 12:21, 11 December 2020 (UTC)

  Done The above has been moved. Wikidata item needs to be moved. --kathleen wright5 (talk) 21:10, 11 December 2020 (UTC)

@Kathleen.wright5: The WD items should be updated when you do the moves, or very quickly afterwards. — billinghurst sDrewth 01:29, 13 December 2020 (UTC)
If anyone is interested in working on this particular backlog, there are about 80+ works (mostly Thai legal documents) that need to be moved from Mainspace to Translation space. —Beleg Tâl (talk) 21:04, 12 December 2020 (UTC)
If someone can map out the required conversions from {{header}} to {{translation header}} then I can run through them. Just too busy to do all the thinking of the conversions. Would be wanting indications of which lines add/remove/change, to make the bot tasking easier. — billinghurst sDrewth 01:32, 13 December 2020 (UTC)
@Billinghurst: Most of them are obvious - title=<title>, author=<author>, etc. The interwiki link [[th:<pagetitle>]] gives you the values for language=th and original=<pagetitle>. If shortcut and/or year are omitted, they need to be added as blank parameters. Finally, any instance of override_translator = [[Wikisource:Translations|Wikisource]] needs to be removed. —Beleg Tâl (talk) 14:24, 14 December 2020 (UTC)

Need an Index: ns page move stopperEdit

We need to toughen our defences against Index: and Page: ns moves. My suggestion is an abuse filter that selectively prohibits, or at the bare minimum warns people that it is not advisable. Before I do anything, would like to hear people's thoughts. Recovering from moves of this type is an issue, especially as it happens pretty quietly.

We don't have good automated rights that AF can leverage at this point in time, though there are numbers of measures that we can apply to restrict or pass actions. — billinghurst sDrewth 05:02, 30 May 2021 (UTC)

Sounds like a good idea, but I'm not familiar enough with the goings-on to have a strong opinion how to do it. Can you describe the problem a little more specifically and/or one or two of the things you think should be done about it? Does this have to with IPs, new accounts, experienced users making poor decisions, intentional vandalism, ..? -Pete (talk) 16:13, 2 June 2021 (UTC)
We do have Special:AbuseFilter/36, which is exactly for this. Perhaps add a warning actions to it and see if that stops people. Be very clear why they are being warned: "Please be extremely careful when moving pages in the Index or Page namespace if you are not an administrator. Non-administrators cannot suppress redirects, which means you cannot move other pages to where the moved page used to be. Moved index pages that have any existing sub-pages need to have the orphaned redirects deleted. It's much easier to ask an admin to do this (at WS:AN) directly rather than asking them to tidy up after a move with redirects left behind." Inductiveloadtalk/contribs 23:08, 2 June 2021 (UTC)
Yeah, that looks good. And I think a warning is the right level for this, at least to start. We have a relative frequent occurrence of people that create a new index after goofing the file name of the first, so the opposite problem is also relevant (it just has smaller consequences). Xover (talk) 06:06, 3 June 2021 (UTC)
Ok, Special:AbuseFilter/36 will now warn the user with MediaWiki:Abusefilter-warning-Non-admin Index-Move, then allow the user to continue (but also tag the edit). Inductiveloadtalk/contribs 18:01, 4 August 2021 (UTC)


As administrators we need to make better use of our general means of announcements to our community, especially where we have either a significant proposal or have made a significant change to policy and templates, and want to capture all our users, and spasmodic users. We have all been pretty rubbish at that general comms in the past while and I think that we should at least think about what we want to better broadcast. — billinghurst sDrewth 09:02, 4 July 2021 (UTC)

This is just the banner that shows up above the watchlist correct? I think that's reasonable. Is there anywhere else we should be remembering to post such content - mailing lists, social media, etc? —Beleg Tâl (talk) 01:47, 7 July 2021 (UTC)
Correct, and it is persistent. As it is watchlist, only logged in users, and they can dismiss it once read. Wikisource-L, Twitter: @wikisource_en are possibles for some things. My reason for the watchlist is that it is our editors, and it is persistent, so very targeted, and low noise threshold. — billinghurst sDrewth 03:46, 7 July 2021 (UTC)
Huh, I had utterly forgotten Wikisource-l existed! Twitter seems more like advertising/evangelism than operational notices (one fine day a New Texts bot can post there!). Inductiveloadtalk/contribs 06:34, 7 July 2021 (UTC)
Indeed. Please don't post RfC or policy discussion notices to Twitter! Xover (talk) 07:02, 7 July 2021 (UTC)
Amen! And especially since low participation is a much bigger problem in our policy/rfc type discussions than excessive numbers of comments or discussions. The better attended a given discussion is the stronger any resulting consensus will be, and, if we do it right, the better it will reflect the position of the community as a whole. Xover (talk) 06:46, 7 July 2021 (UTC)

Import helpEdit

Please import books listed at Wikisource:Requested_texts#Import_5_books_about_Malayalam_language. These books were written for English speakers to learn Malayalam words, and the definitions are all in English. Thank you. Vis M (talk) 00:15, 20 August 2021 (UTC)

This doesn't require an administrator. Probably better requested at Wikisource:Scriptorium/Help if you are looking at assistance in how to do these. — billinghurst sDrewth 00:26, 20 August 2021 (UTC)
I think only admins and importers can do interwiki-import while preserving page history. Special:Import gives permission error for me. Vis M (talk) 11:50, 20 August 2021 (UTC)
Apologies, I misunderstood the request as you were referencing requested texts.
If you have those works at mlWS, why would we import them here? Is mlWS planing on deleting it? We can simply link to the work where it is now, if the work is within scope at mlWS. FWIW no one has import rights to bring works from mlWS to enWS, and from memory our 'crats cannot allocate the right. I think that we need to step right back and work out what it is that is needing to be done, and what is the appropriate place for the work, as it may be be situated at mulWS if it is not to be hosted at mlWS. — billinghurst sDrewth 13:24, 20 August 2021 (UTC)
Those are books about Malayalam language written for English readers/audience. mlWS will not delete it, it is indeed with in its scope. I think enWS also can have it here as its target audience is English language readers. Vis M (talk) 01:55, 22 August 2021 (UTC)
Hi, adding my 2c here—from briefly skimming through the texts, a significant portion of the texts appears to be in Malayalam. The may be within the scope of enWS since it's written in English and uses Malayalam words with context. The other works are more dicey—a significant amount of text is in Malayalam, which might warrant it being hosted on mulWS as opposed to enWS. On the other hand, works such as Index:Tamil studies.djvu also have a significant amount of text in another language (Tamil, in this case) which I would've expected to have been hosted on mulWS instead.
Is there a formal guideline of sorts that gives an idea of how much non-English text in a work is alright for a work hosted on enWS? Off the top of my head I'd say texts which use non-English words and phrases sparingly could be hosted here, but I can't really think of anyplace this has actually been mentioned. WS:Language policy redirects to WS:Translations, which doesn't have any info regarding this. C. F. 23:38, 24 August 2021 (UTC)
@User:Clockery Works that are literally half non-English (as in a side by side translation), and works such as a English-(non-English) dictionary seem to be considered 'obviously' in scope by the community here, so the bar where things start being problematic is pretty low. I think if the work is 'usable' to an English language reader, it's probably fine here. That being said, it would probably be easier to maintain just one place, and use an interwiki link. Jarnsax (talk) 00:34, 25 August 2021 (UTC)
My understanding is that multi-lingual works were in the aegis of mulWS, and that typically works were hosted at one wiki. There are some works that are side-be-side, English/another language, and those have split and are respectively imported using the series explained at Template:Iwpage. It was why I mentioned mulWS, in my initial response. — billinghurst sDrewth 00:51, 25 August 2021 (UTC)
  Comment One thing we probably want to eventually sort out is mainspace presentation and export of works using {{iwpage}}. Since the content is loaded by JS in the page namespace, it doesn't work on transclusion and it therefore won't work on export. Which is a big shame for things like Loeb Classical Library since that's kind of the whole point.
I don't have any immediate idea about how to deal with this (other than throwing up hands and doing it all at enWS!), but I have a sneaking suspicion we'll need at least some server support (either from MW, the export tool, or both). And we'll also likely need to figure out a One True Way to format side-by-side texts in a flexible, exportable and generally not-horrific way. Inductiveloadtalk/contribs 06:12, 25 August 2021 (UTC)

On the general subject, we need clearer rules on this, and those rules shouldn't dissociate us from stuff like the Loeb Classical Library, which is the modern collection of Latin & Ancient Greek works in English. There's a lot of translated material only available in bilingual editions, and that needs to be clearly accessible from here.--Prosfilaes (talk) 20:13, 25 August 2021 (UTC)

I'd like to hear from mulWS (@Zyephyrus, @Ankry, @VIGNERON: as some representatives) on the hosting of dual language works. We we can link to works easily, though it doesn't show up in our searches. I would also be happy to place {{interwiki redirect}}s at the titles (and we can work out WD later). I don't really want to duplicate works as 1) they are dynamic in our proofreading space, 2) they will typically have different templates, 3) duplication is unneeded. — billinghurst sDrewth 00:00, 26 August 2021 (UTC)
Here are some examples:
For instance, this book: Latin text and English indications, useful on both. Do we place it on (talk) 12:59, 28 August 2021 (UTC)
Or this one, Ancient Greek and French, might be on and offer links to both and
I admired the work of VIGNERON on br.wikisource with the {{iwpage|fr}} template used to show the French text}}. All these bilingual or multilingual texts would be moved to Do you think this a good solution ? There would be one place and only one to keep these kinds of documents. Would it be convenient and appropriate for all of them? --Zyephyrus (talk) 21:37, 28 August 2021 (UTC)
I haven't really given this a lot of thought, so I may be way off base and end up completely changing my mind… But my immediate thought is that iff we're to delegate something to mulWS we should explicitly take it out of scope (as in not permitted by WS:WWI) for enWS. To say we permit something but it should mostly be done at mulWS seems unworkable; and having content here that is actually managed at mulWS is untenable (different policies, different practices, different culture; no visibility on watchlists, etc.).
I also generally agree with Prosfilaes' stance above, but reserve the right to modify that due to technical or practical realities.
I suspect that a really good solution to this would require software support so that a given Page:-namespace page can more easily exist at multiple projects at once. And I don't think that is likely to occur in any reasonable timeframe. Xover (talk) 08:11, 29 August 2021 (UTC)

  Comment Links Template:iwpage/Special:WhatLinkshere/Template:iwpage (which is essentially the same at each wiki and s:br:Special:WhatLinkshere/Template:iwpagebillinghurst sDrewth 14:10, 29 August 2021 (UTC)

Category:External links on protected pages & Category:Templates used in Mediawiki namespaceEdit

We have a bit of a maintenance issue in that external links in protected templates and mediawiki: ns are being missed when we are updating links. To assist, I have created the above parent tracking category to label such pages. We obviously cannot use it on Mediawiki: pages, so will have to be content with putting it on the corresponding talk page. I am working through creating subcats for each WMF tool that I find as they are more likely need to be what is changed, and will do some checks. I will note that as some of these pages use conditional code or includeonly so may be a little tricky to find by searching. [Reminder to not unnecessarily hide things to just avoid visual errors in non-display namespaces or ugly display code.] I am hoping that this will also allow us to check these a little more easily as we have suffered some link rot. I think that we may also need to put some checking categories on these so we can at least check these yearly, though haven't got that far and welcome people's thoughts.

I have also identified that we have had some templates transcluded to the mediawiki: ns that have not been protected. Can I express that any such templates need to be fully protected. If you are using a template within another template, then all subsidiary templates also need to be protected. Noting that it often it can be safest to simply use html span and div code and embedded css.

On that note, if we are protecting templates, it is better practice to use separate {{documentation}} so the docs can readily updated without someone asking for editing of protected templates. This is not pointing fingers, as some of these are old static pages that don't readily get traffic, and reflect older generation practices.

I welcome any suggestions/feedback here, and any help perusing of the template: and mediawiki: namespaces for targets. — billinghurst sDrewth 08:39, 26 September 2021 (UTC)

Seems we already have Category:MediaWiki namespace templates, I will transition to that and update categories. — billinghurst sDrewth 10:07, 26 September 2021 (UTC)

Edit request for MediaWiki filterEdit

I've been going through pages with defaultsort conflicts, and it occurred to me that this would be easier if there were a category analogous to Category:Authors with DefaultSort error. So I'd like to request that Category:Works with DefaultSort error be created and added to MediaWiki:Duplicate-defaultsort. Thank you! —CalendulaAsteraceae (talkcontribs) 09:43, 17 January 2022 (UTC)

@CalendulaAsteraceae   Done . This is a good idea, because the current (anti-)pattern of explicit DEFAULTSORTs makes it impossible to do this automatically in the header template (i.e. strip of "A/The" if present). This cat gets us a small step closer to being able to strip most of them out as redundant. Inductiveloadtalk/contribs 10:12, 17 January 2022 (UTC)
@CalendulaAsteraceae also I have added the defaultsort parameter to {{header}}.
The task now is to transition all the manual defaultsorts to either that parameter, or, for most(?) of them, do it by stripping A/An/The in the Lua function. I'm not sure the best way to move forward, but one way would be:
  • Temporarily hide the warning text in MediaWiki:Duplicate-defaultsort in mainspace (leave it enabled in other namespaces), but leave the category
  • Enable the auto-sorting (i.e. stripping of A/An/The) in Lua
  • All the mainspace pages with conflicting sort keys will then drop into the category, but won't spew big red errors
  • The category can be processed (probably with some kind of script, since most of the conflicts are likely "Foo, A" vs "Foo" and easy to handle
  • Once the category is empty, strip the rest of the DEFAULTSORTs, since if they're not throwing errors they must be redundant.
  • Now the pages are transitioned to the parameter, reinstate the warning text
This is not the only way to do it: you could also
  • Migrate all explicit DEFAULTSORTS in mainspace to the defaultsort parameter, then enable auto-sorting and then go back over all pages and remove redundant keys, or
  • Migrate all explicit DEFAULTSORTS in mainspace to the defaultsort parameter, but just delete any which will become redundant, then enable auto-sort. This will have short period when some pages will sort by their "A/An/The".
Anyway, let me know if you need any more edits to facilitate whichever method you prefer! Inductiveloadtalk/contribs 10:53, 17 January 2022 (UTC)
@Simon Peter Hughes: You do a lot of work in this area. Do you have any input here?
@Inductiveload: Not sure whether it's relevant, but keep in mind that we have some bad habits involving not bothering with the full title in defaultsort so long as the string used will kinda sorta sort properly mostly. Also, the sortkey should include any article stripped at the end so that titles that differ only in the article will sort correctly among themselves. Also, we have a lot of garbage data in title fields that we probably don't want to throw unprocessed into the magic word. Hmm. And then there's the "Sort key" field in the Index: that could maybe be used for something here… Xover (talk) 12:49, 17 January 2022 (UTC)
@Xover putting the article at the end is indeed how Module:Auto sort does it, which is what I would suggest Module:header eventually could use. The current manual ones are done both with and without, e.g. A Dictionary of Music and Musicians, which is literally the first result for insource:DEFAULTSORT that begins with an article.
The least "exciting" way would be to continue to use the subpage name, rather than the title parameter, because that won't change too much. If we wanted to use the title parameter, or inhale from an index page (rather hard, since most header invocations do not know what the index is), that would be a next step.
The first steps will have to be removing the manual DEFAULTSORTs, since, because none of them have been set with noerror or noreplace, it's impossible to do anything at all until they are changed to template params (or bot through and add noerror/noreplace, which is yet another option for moving forward). There are 132k+ instances, so it's going to be pretty painful whatever happens (and that's why I have never bothered to address it myself). Inductiveloadtalk/contribs 13:08, 17 January 2022 (UTC)
@Inductiveload: Now that Category:Works with DefaultSort error is clear and I've had a little time to think about it, I think your first proposed method for transitioning to auto-sorting sounds good! (Assuming you or someone can do the script part, because I sure can't.) And I'm happy to do stuff like manually resolving the trickier conflicts. —CalendulaAsteraceae (talkcontribs) 05:58, 12 February 2022 (UTC)
@Inductiveload: Thank you! I don't particularly have a preference among the different ways of transitioning pages to use the defaultsort parameter. I do have an edit request, though—could you add | defaultsort = {{{defaultsort|{{SUBPAGENAME}}}}} to the header in {{A catalogue of notable Middle Templars, with brief biographical notices}}? Pages in that work had been putting manual DEFAULTSORTs on each page, and I removed that from the preload. —CalendulaAsteraceae (talkcontribs) 02:32, 18 January 2022 (UTC)
No, please don't do that. There is nothing wrong with individual defaultsort, and it was purposeful to not have it in the template. Having a hidden defaultsort can be problematic. — billinghurst sDrewth 11:00, 18 January 2022 (UTC)

Please delete multiple pages in Index:History of Oregon Literature.djvuEdit

I hope this request is not too much of a hassle. If it is, let me know, and I am willing to continue to deal with it manually. It's a rather painstaking one.

I proofread (and part-proofread) a number of pages of Index:History of Oregon Literature.djvu prior to realizing (thanks to ShakespeareFan00) how very incomplete the underlying scan was. I have now repaired the scan (manually inserting the missing pages), and I have moved all the pages I'm able to as a non-administrator. But the remaining pages that need to be moved need to overwrite pages that are now redirects or no-text pages, due to the previous page moves.

So, I am hoping that an administrator can can delete all pages starting with scan page 140 that are either:

  • Blank, i.e. without text, showing up with grey highlight on the index page, or
  • Redirects, showing up with no highlight on the index page.

I'll note, I will likely come back for a second round of this, after I've followed up this request with some more page moves.

If this request is in any way unclear, please either ignore it entirely, or ask for clarification. Thank you for any assistance. -Pete (talk) 09:06, 2 February 2022 (UTC)

@Peteforsyth: The time-consuming and hard (requires understanding of the specific work / the problem) part is picking out the pages to work on. If you give me a list of pages I can automate the delete or move itself. For deletes, either a flat list of pages, or make a temporary category and tag all the pages to be deleted with that category. For moves, a list of page name to move from and page name to move to, and whether or not you need to have redirects at the old name or not. With this input I can have a bot do the job in relatively short order. Xover (talk) 09:50, 2 February 2022 (UTC)
140 147 152 209 210 304
The full range of 309 to 330 (though a few do not exist)
437 438 445 446 447 502 569 570
range: 600 to 623
Does that do the trick? Thank you! -Pete (talk) 10:25, 2 February 2022 (UTC)
@Peteforsyth: Well, not quite. The software here doesn't understand the concept of "pages in the book", it needs to get the list of wikipages to work on from somewhere. If all the pages are in a category it can look up all pages in that category and delete those, or the list can be manually constructed in this format:
List of wikipages
Page:History of Oregon Literature.djvu/140
Page:History of Oregon Literature.djvu/147
Page:History of Oregon Literature.djvu/152
Page:History of Oregon Literature.djvu/209
Page:History of Oregon Literature.djvu/210
Page:History of Oregon Literature.djvu/304
Page:History of Oregon Literature.djvu/309
Page:History of Oregon Literature.djvu/310
Page:History of Oregon Literature.djvu/311
Page:History of Oregon Literature.djvu/312
Page:History of Oregon Literature.djvu/313
Page:History of Oregon Literature.djvu/314
Page:History of Oregon Literature.djvu/315
Page:History of Oregon Literature.djvu/316
Page:History of Oregon Literature.djvu/317
Page:History of Oregon Literature.djvu/318
Page:History of Oregon Literature.djvu/319
Page:History of Oregon Literature.djvu/320
Page:History of Oregon Literature.djvu/321
Page:History of Oregon Literature.djvu/322
Page:History of Oregon Literature.djvu/323
Page:History of Oregon Literature.djvu/324
Page:History of Oregon Literature.djvu/325
Page:History of Oregon Literature.djvu/326
Page:History of Oregon Literature.djvu/327
Page:History of Oregon Literature.djvu/328
Page:History of Oregon Literature.djvu/329
Page:History of Oregon Literature.djvu/330
Page:History of Oregon Literature.djvu/437
Page:History of Oregon Literature.djvu/438
Page:History of Oregon Literature.djvu/445
Page:History of Oregon Literature.djvu/446
Page:History of Oregon Literature.djvu/447
Page:History of Oregon Literature.djvu/502
Page:History of Oregon Literature.djvu/569
Page:History of Oregon Literature.djvu/570
Page:History of Oregon Literature.djvu/600
Page:History of Oregon Literature.djvu/601
Page:History of Oregon Literature.djvu/602
Page:History of Oregon Literature.djvu/603
Page:History of Oregon Literature.djvu/604
Page:History of Oregon Literature.djvu/605
Page:History of Oregon Literature.djvu/606
Page:History of Oregon Literature.djvu/607
Page:History of Oregon Literature.djvu/608
Page:History of Oregon Literature.djvu/609
Page:History of Oregon Literature.djvu/610
Page:History of Oregon Literature.djvu/611
Page:History of Oregon Literature.djvu/612
Page:History of Oregon Literature.djvu/613
Page:History of Oregon Literature.djvu/614
Page:History of Oregon Literature.djvu/615
Page:History of Oregon Literature.djvu/616
Page:History of Oregon Literature.djvu/617
Page:History of Oregon Literature.djvu/618
Page:History of Oregon Literature.djvu/619
Page:History of Oregon Literature.djvu/620
Page:History of Oregon Literature.djvu/623
Page:History of Oregon Literature.djvu/631
Always keep in mind that computers are dumb as bricks: a human always has to tell them what to do in excruciating detail. So in this case I had to translate your page number ranges into a flat list of wikipages. I made the assumption that the numbers were the physical page indexes. If instead you meant the logical page numbers (the ones printed in the book, and that you've mapped to physical page indexes in the <pagelist …> tag) then the list will have to mapped from the one to the other. (and to be clear, I need you to check that the list above is correct / what you want deleted before I push the button)--Xover (talk) 11:33, 2 February 2022 (UTC)
BTW, I tried to write down some instructions to make it easier to make mass action requests to admins here. Feedback on whether these are helpful and understandable would be appreciated. Xover (talk) 14:54, 2 February 2022 (UTC)
Thanks much. I've taken note of your instructions where I can find them next time, and I'll get you any feedback (but at first blush it seems plenty clear). For some reason, your bot seems to have missed this range (though it was in your list). Maybe it's just operating slowly, or maybe something went wrong:
Page:History of Oregon Literature.djvu/600
Page:History of Oregon Literature.djvu/601
Page:History of Oregon Literature.djvu/602
Page:History of Oregon Literature.djvu/603
Page:History of Oregon Literature.djvu/604
Page:History of Oregon Literature.djvu/605
Page:History of Oregon Literature.djvu/606
Page:History of Oregon Literature.djvu/607
Page:History of Oregon Literature.djvu/608
Page:History of Oregon Literature.djvu/609
Page:History of Oregon Literature.djvu/610
Page:History of Oregon Literature.djvu/611
Page:History of Oregon Literature.djvu/612
Page:History of Oregon Literature.djvu/613
Page:History of Oregon Literature.djvu/614
Page:History of Oregon Literature.djvu/615
Page:History of Oregon Literature.djvu/616
Page:History of Oregon Literature.djvu/617
Page:History of Oregon Literature.djvu/618
Page:History of Oregon Literature.djvu/619
Page:History of Oregon Literature.djvu/620
Page:History of Oregon Literature.djvu/623
-Pete (talk) 16:53, 2 February 2022 (UTC)
@Xover: Oh, wait. It looks like ShakespeareFan00 is working to address these problems, maybe in a different way, I'm not sure if what they're doing is aligned with this request or not. So, probably best not to take any further action until we've heard from them? -Pete (talk) 16:58, 2 February 2022 (UTC)
@ShakespeareFan00: As best I can tell, the approach you're taking is going to require a bunch of my work to be redone, which is what I was hoping to avoid. For instance, by deleting the content instead of the page at Page:History of Oregon Literature.djvu/328, you have made it impossible to move the fully proofread page at Page:History of Oregon Literature.djvu/306 into its proper location. If I'm misunderstanding something, please let me know. But I was trying to approach this in a way that would not require any pages to be proofread a second time. I'd prefer if the final list of pages could be deleted. I'm fine with manually moving pages once the target pages have been deleted. -Pete (talk) 17:04, 2 February 2022 (UTC)
Please list WHICH pages are wrong and by how many pages they need to be moved. ShakespeareFan00 (talk) 17:09, 2 February 2022 (UTC)

:: Unless you have done any new proofreading, I believe the most straightforward solution at this point would be if Xover could just run the bot on the initial list he put together (above), which appears to be entirely correct.

I have not requested that any pages be moved, because I can't think of a programmatic way to express that. I've already manually moved dozens of pages, and I'm happy to manually move dozens more. If you think it's better to move them in a programmatic way, I'll probably need some help formulating that request. The offset shifts many times, due to the presence of many illustrated plates and many pages having been omitted in the initially-uploaded scan. -Pete (talk) 17:16, 2 February 2022 (UTC)
Oh, never mind, now I see that you're moving pages as well as replacing content. I can't really tell what your vision is, so I'm not going to recommend any action here, don't want us all working at cross purposes. I'll probably just delete all these pages from my watchlist for a while until everything settles down, I don't think I can contribute usefully as it is now. (But I do need to scan those remaining 2 pages before the library book is due. I'll make that my last contribution for a while.) -Pete (talk) 17:27, 2 February 2022 (UTC)
@ShakespeareFan00: Think, talk, then act; especially for a work someone else is actively working on. Please discuss with Peteforsyth and agree on a course of action before moving pages around.
There's no real advantage to moving pages programatically, vs. manually, but unless you want redirects it's often best to have an admin do it. And for any admin to do it in a reasonable time frame it needs to be automated. If you would prefer to move with redirects and then ask for deletion of the redirects afterwards that's fine too. Xover (talk) 17:35, 2 February 2022 (UTC)
Perhaps someone can sit down and carefully document which page rages are incorrectly placed now? ( Where I'd replaced content, It was that I'd re OCR'ed a page, that had been a redirect, or previously been marked as a blank and now wasn't.)

These are some of the ranges that I think are in the wrong place (I've got no objections to my good faith efforts being overwritten during page moves.)

This table contains errors, I think I have corrected them in the version below. -Pete (talk) 21:07, 11 April 2022 (UTC)
Old Page (Djvu) Offset needed.
301-308 +22
443-439 +22
448-460 +22
461-463 +6
557-599 +24

(There may be others)

The pagelist itself should now be correct and complete, however. ShakespeareFan00 (talk) 17:45, 2 February 2022 (UTC)

Thank you both for your efforts. I've thought it through, and given what seems like a choice between "sit down and carefully document" vs. "just re-proofread the affected pages", I think I prefer the latter. Is it OK if we just stop the deletions, and stop any further moves unless the mover is certain that the source page is superior to the target?
And if so, can we move any further discussion/planning back to Index talk:History of Oregon Literature.djvu, since I don't think that approach will require any administrative intervention?
Appreciate both your efforts a great deal. I especially appreciate the guidance on how to approach this sort of thing, and I'll consult it in the future if I have a similar need. -Pete (talk) 18:39, 2 February 2022 (UTC)
That sounds like a good plan. If you do end up needing any bulk actions please feel free to request them here. Xover (talk) 18:44, 2 February 2022 (UTC)
Xover, see above, I think it's only those ranges I identifed that are affected. For someone with admin level rights, a move should be straightforward.ShakespeareFan00 (talk) 21:25, 2 February 2022 (UTC)
Thanks for doing this, it looks pretty good. But:
433 should be +22 (and I'm guessing some of the pages following it should share that offset as well). And there seems to be a typo in the 2nd row of the table, "|443-436||+12" (note that the page sequence goes down not up), so I'm not sure what's intended there. I did spot-check the other rows (as in, checked one or two pages in each range) and they seemed good. Do note, if taking this approach it would be good to start with the last row of the table and work backward, as at least one or two of the pages will "overlap." -Pete (talk) 21:46, 2 February 2022 (UTC)
@ShakespeareFan00: Could you take another look at this? Looks like your table is really close. -Pete (talk) 09:29, 4 February 2022 (UTC)

I'd like to get back to proofreading this. @ShakespeareFan00: it seems like we were almost there, and if you're not up for double-checking your work here, I think after another review, I'm fairly confident that the second row should simply read "433-459" instead of "443-439". If so, it can easily be combined with the following row, as the ranges overlap. I've looked at enough of the pages to be reasonably sure that would take care of it; @Xover: could you move the pages as indicated in the (edited) version of the table below? If by chance a handful of errors result, I'll just take care of them by hand. -Pete (talk) 21:07, 11 April 2022 (UTC)

Corrected table:

Old Page (Djvu) Offset needed.
301-308 +22
433-460 +22
461-463 +6
557-599 +24
I am not touching this again until it's in a KNOWN state, and all the existing pages are re-aligned. This is why I try and check the pagelist before anything else is done. ShakespeareFan00 (talk) 22:24, 11 April 2022 (UTC)
@ShakespeareFan00: I have not asked you to touch it again, I've asked you to double-check your own work here on this discussion page. Your table above has some errors; as I understand it, you intended the table to address the problems you caused. You're welcome to not engage further, that's fine, and indeed your clear expression that you will not touch it is more useful than simply walking away from the discussion, because it allows me to know that your work on this will not again collide with mine. But please don't insinuate that I caused the problems with this one. I have been trying to communicate with you from the start.
I do appreciate your efforts to help with this -- very much. You have been extremely helpful with many of my transcription efforts, and I have learned many things from you. It is greatly appreciated. But please don't miss the fact that the lack of communication is the very thing that caused this particular work to be such a mess. -Pete (talk) 22:33, 11 April 2022 (UTC)
I'm sorry if I sounded too strong, and I certainly didn't mean to insinuate anything, if anything my strongly worded comment above was mostly aimed at myself. I'll have another look at your updated table. ShakespeareFan00 (talk) 23:00, 11 April 2022 (UTC)
Thank you for acknowledging that, and I must confess I was also a little overwrought in my own message above. It's true that in my initial enthusiasm I transcribed a bunch of pages before checking for missing pages, as you've pointed out. I've never known that approach to backfire quite as spectacularly as it has in this instance. I regret that approach and I appreciate both of your efforts to help resolve it. I've been stressed about some totally unrelated stuff, and I think I was taking that out here without realizing it. Sorry. -Pete (talk) 00:27, 12 April 2022 (UTC)
See my revised request below, I made some further checks and listed every single page, because I wasn't sure of the ranges given earlier.
I've batched up the requests, and they should be done in the order presented, so as to as avoid 'moving' the wrong versions.
ShakespeareFan00 (talk) 06:00, 12 April 2022 (UTC)

Russia—Ukraine conflict on-wikiEdit

Just a note that the ongoing Russia—Ukraine conflict (and I am deliberately not characterizing it beyond identifying it) is currently creating echoes on-wiki across Wikimedia projects, with Wikimedians sympathising with one or the other of the involved parties acting or reacting on-wiki to events happening IRL. It is very likely this kind of thing will spill over to English Wikisource too (for example, speeches by representatives of the parties or by third parties are in scope) and by its very nature it is an issue apt to engender very strong feelings and emotional responses. I urge all admins to be on the lookout for on-wiki behaviour or actions that appear motivated in some way by this conflict and step in to manage such situations before they spin out of control, but with diplomacy and sensitivity in a very difficult situation for many.

Also, if you are an admin with a personal stake in this conflict or very strong feelings about it, please leave admin actions that are at all related to it to other admins. We've seen otherwise intelligent and level-headed admins on other projects act on what they feel is a moral imperative but entirely outside policy. There may indeed be trolling or propaganda being perpetuated on-wiki that we need to manage, but if you have a personal stake or very strong feelings you are probably not going to be the best person to make the judgement call of where to draw the line.

Hopefully we can keep this place a fussy, dusty, and what most would consider pretty boring place rather than import IRL conflicts. Xover (talk) 07:05, 28 February 2022 (UTC)

In agreement. Ineuw (talk) 23:45, 1 March 2022 (UTC)
Agreed. Telling us any existing conflicts may catch our attention.--Jusjih (talk) 03:44, 26 April 2022 (UTC)

Move request for Castelvines y MontesesEdit

I'd like to request that Castelvines y Monteses and its subpages be moved to Castelvines y Monteses (Cosens) etc. without leaving redirects, to make room for a translations page. Thanks! —CalendulaAsteraceae (talkcontribs) 02:22, 10 April 2022 (UTC)

@CalendulaAsteraceae:   Done Xover (talk) 17:53, 23 April 2022 (UTC)

Page realignment request:Index:History of Oregon Literature.djvuEdit

The 'realignment' below should be done in the 'batch' order presented to avoid moving the 'wrong' pages. Thanks. ShakespeareFan00 (talk) 06:01, 12 April 2022 (UTC)

Batch 1
Old page pp New page
Page:History of Oregon Literature.djvu/301 (pp 289) Page:History_of_Oregon_Literature.djvu/323
Page:History of Oregon Literature.djvu/302 (pp 290) Page:History_of_Oregon_Literature.djvu/324
Page:History of Oregon Literature.djvu/303 (pp 291) Page:History_of_Oregon_Literature.djvu/325
Page:History of Oregon Literature.djvu/305 (pp 293) Page:History_of_Oregon_Literature.djvu/327
Page:History of Oregon Literature.djvu/306 (pp 294) Page:History_of_Oregon_Literature.djvu/328
Page:History of Oregon Literature.djvu/307 (pp 295) Page:History_of_Oregon_Literature.djvu/329
Page:History of Oregon Literature.djvu/308 (pp 296) Page:History_of_Oregon_Literature.djvu/329

ShakespeareFan00 (talk) 23:15, 11 April 2022 (UTC)

Batch 2
old page pp newpage
Page:History_of_Oregon_Literature.djvu/461 (pp 425) Page:History of Oregon Literature.djvu/467
Page:History_of_Oregon_Literature.djvu/462 (pp 426) Page:History of Oregon Literature.djvu/468
Page:History_of_Oregon_Literature.djvu/463 (pp 427) Page:History of Oregon Literature.djvu/469
Batch 3
old page pp newpage
Page:History_of_Oregon_Literature.djvu/433 (pp 415) Page:History_of_Oregon_Literature.djvu/455
Page:History of Oregon Literature.djvu/434 (pp 416) Page:History of Oregon Literature.djvu/456
Page:History of Oregon Literature.djvu/435 (pp 417) Page:History of Oregon Literature.djvu/457
Page:History of Oregon Literature.djvu/436 (pp 418) Page:History of Oregon Literature.djvu/458
Page:History of Oregon Literature.djvu/439 (pp 419) Page:History of Oregon Literature.djvu/461
Page:History of Oregon Literature.djvu/440 (pp 420) Page:History of Oregon Literature.djvu/462
Page:History of Oregon Literature.djvu/441 (pp 421) Page:History of Oregon Literature.djvu/463
Page:History of Oregon Literature.djvu/442 (pp 422) Page:History of Oregon Literature.djvu/464
Page:History of Oregon Literature.djvu/443 (pp 423) Page:History of Oregon Literature.djvu/465
Page:History of Oregon Literature.djvu/444 (pp 424) Page:History of Oregon Literature.djvu/466
Page:History of Oregon Literature.djvu/448 (pp 428) Page:History_of_Oregon_Literature.djvu/470
Page:History of Oregon Literature.djvu/449 (pp 429) Page:History_of_Oregon_Literature.djvu/471
Page:History of Oregon Literature.djvu/450 (pp 430) Page:History_of_Oregon_Literature.djvu/472
Page:History of Oregon Literature.djvu/451 (pp 431) Page:History_of_Oregon_Literature.djvu/473
Page:History of Oregon Literature.djvu/452 (pp 432) Page:History_of_Oregon_Literature.djvu/474
Page:History of Oregon Literature.djvu/453 (pp 433) Page:History_of_Oregon_Literature.djvu/475
Page:History_of_Oregon_Literature.djvu/454 (pp 434) Page:History_of_Oregon_Literature.djvu/476
Page:History_of_Oregon_Literature.djvu/455 (pp 435) Page:History_of_Oregon_Literature.djvu/477
Page:History_of_Oregon_Literature.djvu/456 (pp 436) Page:History_of_Oregon_Literature.djvu/478
Page:History_of_Oregon_Literature.djvu/457 (pp 437) Page:History_of_Oregon_Literature.djvu/479
Page:History_of_Oregon_Literature.djvu/458 (pp 438) Page:History_of_Oregon_Literature.djvu/480
Page:History_of_Oregon_Literature.djvu/459 (pp 439) Page:History_of_Oregon_Literature.djvu/481
Page:History_of_Oregon_Literature.djvu/460 (pp 440) Page:History_of_Oregon_Literature.djvu/482

ShakespeareFan00 (talk) 05:13, 12 April 2022 (UTC)

Batch 4
old page pp newpage
Page:History of Oregon Literature.djvu/571 (pp. 547) Page:History of Oregon Literature.djvu/595
Page:History of Oregon Literature.djvu/572 (pp. 548) Page:History of Oregon Literature.djvu/596
Page:History of Oregon Literature.djvu/573 (pp. 549) Page:History of Oregon Literature.djvu/597
Page:History of Oregon Literature.djvu/574 (pp. 550) Page:History of Oregon Literature.djvu/598
Page:History of Oregon Literature.djvu/575 (pp. 551) Page:History of Oregon Literature.djvu/599
Page:History of Oregon Literature.djvu/576 (pp. 552) Page:History of Oregon Literature.djvu/600
Page:History of Oregon Literature.djvu/577 (pp. 553) Page:History of Oregon Literature.djvu/601
Page:History of Oregon Literature.djvu/578 (pp. 554) Page:History of Oregon Literature.djvu/602
Page:History of Oregon Literature.djvu/579 (pp. 555) Page:History of Oregon Literature.djvu/603
Page:History of Oregon Literature.djvu/580 (pp. 556) Page:History of Oregon Literature.djvu/604
Page:History of Oregon Literature.djvu/581 (pp. 557) Page:History of Oregon Literature.djvu/605
Page:History of Oregon Literature.djvu/582 (pp. 558) Page:History of Oregon Literature.djvu/606
Page:History of Oregon Literature.djvu/583 (pp. 559) Page:History of Oregon Literature.djvu/607
Page:History of Oregon Literature.djvu/584 (pp. 560) Page:History of Oregon Literature.djvu/608
Page:History of Oregon Literature.djvu/585 (pp. 561) Page:History of Oregon Literature.djvu/609
Page:History of Oregon Literature.djvu/586 (pp. 562) Page:History of Oregon Literature.djvu/610
Page:History of Oregon Literature.djvu/587 (pp. 563) Page:History of Oregon Literature.djvu/611
Page:History of Oregon Literature.djvu/588 (pp. 564) Page:History of Oregon Literature.djvu/612
Page:History of Oregon Literature.djvu/589 (pp. 565) Page:History of Oregon Literature.djvu/613
Page:History of Oregon Literature.djvu/590 (pp. 566) Page:History of Oregon Literature.djvu/614
Page:History of Oregon Literature.djvu/591 (pp. 567) Page:History of Oregon Literature.djvu/615
Page:History of Oregon Literature.djvu/592 (pp. 568) Page:History of Oregon Literature.djvu/616
Page:History of Oregon Literature.djvu/593 (pp. 569) Page:History of Oregon Literature.djvu/617
Page:History of Oregon Literature.djvu/594 (pp. 570) Page:History of Oregon Literature.djvu/618
Page:History of Oregon Literature.djvu/595 (pp. 571) Page:History of Oregon Literature.djvu/619
Page:History of Oregon Literature.djvu/596 (pp. 572) Page:History of Oregon Literature.djvu/620
Page:History of Oregon Literature.djvu/597 (pp. 573) Page:History of Oregon Literature.djvu/621
Page:History of Oregon Literature.djvu/598 (pp. 574) Page:History of Oregon Literature.djvu/622
Page:History of Oregon Literature.djvu/599 (pp. 575) Page:History of Oregon Literature.djvu/623

Batch 5
old page pp newpage
Page:History of Oregon Literature.djvu/557 (pp. 535) Page:History of Oregon Literature.djvu/581
Page:History of Oregon Literature.djvu/558 (pp. 536) Page:History of Oregon Literature.djvu/582
Page:History of Oregon Literature.djvu/559 (pp. 537) Page:History of Oregon Literature.djvu/583
Page:History of Oregon Literature.djvu/560 (pp. 538) Page:History of Oregon Literature.djvu/584
Page:History of Oregon Literature.djvu/561 (pp. 539) Page:History of Oregon Literature.djvu/585
Page:History of Oregon Literature.djvu/562 (pp. 540) Page:History of Oregon Literature.djvu/586
Page:History of Oregon Literature.djvu/563 (pp 541) Page:History of Oregon Literature.djvu/587
Page:History of Oregon Literature.djvu/564 (pp. 542) Page:History of Oregon Literature.djvu/588
Page:History of Oregon Literature.djvu/565 (pp. 543) Page:History of Oregon Literature.djvu/589
Page:History of Oregon Literature.djvu/566 (pp. 544) Page:History of Oregon Literature.djvu/590
Page:History of Oregon Literature.djvu/567 (pp. 545) Page:History of Oregon Literature.djvu/591
Page:History of Oregon Literature.djvu/568 (pp. 546) Page:History of Oregon Literature.djvu/592

ShakespeareFan00 (talk) 05:56, 12 April 2022 (UTC)

@ShakespeareFan00, @Peteforsyth:   Done Please check that I didn't mess up anything. Xover (talk) 17:30, 23 April 2022 (UTC)
@Xover: Thank you! I'm traveling and won't be able to check closely for a week or so, but I appreciate the effort and the note! -Pete (talk) 21:01, 24 April 2022 (UTC)

request move volume ZoologistEdit

Could an administrator please move the index of a volume of The Zoologist?

It's about Index:The Zoologist - Volume 4.djvu. It should be moved to Index:The Zoologist, 1st series, vol 4 (1846).djvu, to have it conform to other volumes of The Zoologist, that are indexed, especially in the 3rd and 4th series. Thanks, --Dick Bos (talk) 10:44, 13 April 2022 (UTC)

@Dick Bos: The Index: page needs to be at the same name as the associated File:; which in this case is on Commons, so you'll first need to request a move there and then we can move the Index: and Page: pages here. Xover (talk) 17:33, 23 April 2022 (UTC)
@User:Xover, thank you. Done. --Dick Bos (talk) 17:41, 25 April 2022 (UTC)

Trying to transclude "The Queen Bee"Edit

I am trying to transclude "The Queen Bee" to the page Grimm's Household Tales, Volume 1/The Queen Bee, but it says my action may be harmful. 17:27, 19 April 2022 (UTC)

Annoyingly, your edit was caught in a global filter because it appeared like vandalism (non-logged-in users removing large amounts of contiguous text are a common signature of vandalism at most wikis). The good news is that you only need 10 edits to become an "established enough" editor for the filter to no longer apply. This is a global filter, so we can't change it immediately here. However, if we see lots of these hits, we should probably get the filter changed to allow edits if the wiki is a Wikisource and the edit contains "<pages". Inductiveloadtalk/contribs 22:46, 19 April 2022 (UTC)
@Inductiveload: IP editors never get autoconfirmed, so that won't help here. Xover (talk) 17:34, 23 April 2022 (UTC)
@192.107: if you give us the details (Index: link and relevant pages) we can transclude it for you. Alternately, it is really recommended to register a user account (entirely free, and you don't even need to provide an email address if you don't want to). With a user account it's much easier to communicate, and after something like 10 edits you get extended permissions that exempt you from some spam filters, let you move pages, etc. Xover (talk) 17:38, 23 April 2022 (UTC)

Renaming request for Author:Pierre Banet-RivetEdit

Hi! I'd like to rename Author:Pierre Banet-Rivet in Author:Paul Banet-Rivet. I don't know were the name Pierre comes from; I was able to locate his birth certificate (see on Wikidata) and it is definitely Paul. --Jahl de Vautban (talk) 19:00, 22 April 2022 (UTC)

@Jahl de Vautban:   Done Xover (talk) 19:19, 22 April 2022 (UTC)

New index page broken?Edit

Just created Index:The Private Life Of Helen Of Troy(1926) (IA dli.ernet.524076).pdf and there’s a big error message and size of 0. What’s going on? feydey (talk) 17:42, 25 April 2022 (UTC)

feydey I told the form that the page was pdf, and now it works.--RaboKarbakian (talk) 23:58, 25 April 2022 (UTC)
Thanks. feydey (talk) 08:30, 26 April 2022 (UTC)

m:Requests for comment/Global de-adminship for JusjihEdit

A user is requesting to "global de-admin" (sorry I really don't know how likely if this could be happened) @Jusjih: which in requestor's claim, has many disruptive and abusive behaviors in several Chinese-language projects and Meta-Wiki, the requestor is also mentioned en.wikisource here where Jusjih is also an administrator, but didn't say anything else on their en.wikisource's behaviors. Do any of our adminships that may or may not familiar Jusjih's works know how to resolve it? --Liuxinyu970226 (talk) 05:18, 29 April 2022 (UTC)

  • I have commented on a similar section on the Wikipedia administrator's noticeboard to the effect that I have seen nothing from Jusjih on this project that would merit de-adminship. BD2412 T 06:22, 29 April 2022 (UTC)
I have done the same on the meta RFC. Beeswaxcandle (talk) 09:05, 29 April 2022 (UTC)
Hello all, en.wikisource will no longer be included in the scope. Your opinions will be still welcomed if you will. Thank you. Zhxy 519 (talk) 00:45, 30 April 2022 (UTC)
I have added my thoughts at meta as well. BD2412 T 06:23, 30 April 2022 (UTC)
We should still consider whether to directly adopt w:Wikipedia:No personal attacks and w:Wikipedia:Assume good faith while cited by w:Wikipedia:Don't remind others of past misdeeds.--Jusjih (talk) 18:06, 7 May 2022 (UTC)

Move request for The paradise, or garden of the holy fathersEdit

Could The paradise, or garden of the holy fathers and its subpages linked in the TOC be moved to The paradise, or garden of the holy fathers/Volume 1 etc.? (The paradise, or garden of the holy fathers/Volume 2 and its subpages should not be moved.) Once this is done I'd also like for The Paradise or Garden of the Holy Fathers to be moved to The paradise, or garden of the holy fathers. Thanks! —CalendulaAsteraceae (talkcontribs) 21:06, 5 May 2022 (UTC)

Question: Why is "..., or garden..." in the title? It does not appear on the work's title page. --EncycloPetey (talk) 22:04, 5 May 2022 (UTC)
@EncycloPetey: Wow, I didn't notice that! I have no idea, and would be happy for you to take it out. —CalendulaAsteraceae (talkcontribs) 05:12, 7 May 2022 (UTC)
It appears on the full title page: Page:Theparadiseoftheholyfathers.djvu/9. But I would agree that a better page name would be The Paradise, or possibly The Paradise of the Holy Fathers.
In any case, this does not look like a simple move: there are a gazillion subpages in a complicated work structure that currently does not use subpages in a sane way. See Special:PrefixIndex/The paradise, or garden of the holy fathers/. In other words, I think this needs a bigger cleanup and a well-tought-out subpage structure. The Paradise/Volume 1/Book 1/Chapter 1 for The History of Abba Isidore for example.
That kind of cleanup is possibly best handled manually by someone with +sysop (for which I do not have the spare cycles currently, sorry). Alternately, given a list of page moves I can have a bot do it. If so, the format would be:
[[From page 1]]
[[To page 1]]
[[From page 2]]
[[To page 2]]
Or any other variant with from a delimiter to that I can easily transform it. Xover (talk) 11:24, 7 May 2022 (UTC)
Thank you! —CalendulaAsteraceae (talkcontribs) 23:51, 9 May 2022 (UTC)
Just to note, I haven't forgotten about this but I am waiting for the fix to phab:T307826 to get deployed to PAWS. If it's really pressing I can work around it by running from a local checkout of HEAD, but that's a bit of a hassle so I'll just wait for the deployment unless I'm nagged on. :) Xover (talk) 13:11, 13 May 2022 (UTC)
@CalendulaAsteraceae:   Done The bugfix finally got deployed so I've run the move. Please check the results and update the internal links as needed (let me know if you need any batch regex replacements there). Xover (talk) 06:10, 23 May 2022 (UTC)
@Xover: Thank you! Could you update the links in the TOC for Volume 1? Page:Theparadiseoftheholyfathers.djvu/13, Page:Theparadiseoftheholyfathers.djvu/14, Page:Theparadiseoftheholyfathers.djvu/15, Page:Theparadiseoftheholyfathers.djvu/16, Page:Theparadiseoftheholyfathers.djvu/17. —CalendulaAsteraceae (talkcontribs) 07:40, 24 May 2022 (UTC)
@CalendulaAsteraceae:   Done Xover (talk) 14:15, 24 May 2022 (UTC)
Pages to move

Protected edit request for Module:ISO 639Edit

I'd like it if there were an option in Module:ISO 639 to specify an error message if the language code isn't recognized. The way I'd do it is like this—unless there are uses of the module where it's important that it return nil if the language code isn't recognized, in which case I can adjust accordingly. Thanks! —CalendulaAsteraceae (talkcontribs) 21:56, 5 May 2022 (UTC)

@CalendulaAsteraceae: The convention is that functions return nil to signal an error, particularly this kind of error, and it's generally bad practice to hard code error messages down in library code (for all sorts of reasons). This kind of behaviour is better handled closer to the user layer, but possibly aided by a function in the library to check whether the code exists and returning a boolean on which the error message can be made conditional. What's the context / use case? Xover (talk) 11:32, 7 May 2022 (UTC)
@Xover The use case is that {{ISO 639 name}} has an option to provide a default value if the code isn't recognized, and now that the template is using Module:ISO 639, I want to make sure that functionality still works. Which, now that I'm typing this, I'm realizing could be done with just an option in the module to provide a default value, something like this.
(Another question: what's a good way to do error-categorization for {{ISO 639 name}}?) —CalendulaAsteraceae (talkcontribs) 22:49, 7 May 2022 (UTC)
@CalendulaAsteraceae: Error categorization is just outputting whatever category you want at some point where the wikimarkup could validly appear. I wish the MW devs would move categories out of page content and into metadata for a page, and allow an API from Lua to set cats in a structured way. But for now it's just a matter of spitting out a text string with the category markup and hoping it'll be in some valid context that doesn't mess up formatting.
But what is the use case for having a default language if an invalid language code is provided? In what situation would you want some random and possibly changeable language name returned? As an interface guarantee, "returning either a valid language name or nil" is a lot cleaner than "… or possibly some default value, picked either by a template or module developer, or provided by the end user, that may or may not understand what it means and what the template does, and may or may not be stable over time, and may or may not be a valid language name under some standard or local convention or colloquially or in the user's head."
nil is a "default value" of a sort, that has the precise semantics "something went wrong". When something goes wrong you generally want either calling code or the invoking user to be made aware of that fact immediately so that they can fix it. Returning some seemingly valid output is directly contrary to this goal: it obfuscates the fact that we are in an error situation and thus makes it harder to fix. Xover (talk) 10:47, 8 May 2022 (UTC)
Thank you for explaining! —CalendulaAsteraceae (talkcontribs) 22:34, 9 May 2022 (UTC)

DIFFERENT protected edit request for Module:ISO 639Edit

It's occurred to me that it would be nice if the list of recognized language codes were available outside the module, and the simplest way to do that would be like this: move the lookup table outside of the language_name function, and add this function:

Get the list of all recognized ISO 639 (-1, -2 or -3) codes.
function p.language_codes()
	return pairs(langs)

Would this be possible? —CalendulaAsteraceae (talkcontribs) 21:56, 15 May 2022 (UTC)

…possibly pairs doesn't do what I want it to there, but the substance of the request still stands. —CalendulaAsteraceae (talkcontribs) 00:11, 16 May 2022 (UTC)
Yeah, it definitely doesn't, and I'm no longer sure what I wanted a table of all valid ISO codes for, so never mind. —CalendulaAsteraceae (talkcontribs) 09:10, 30 May 2022 (UTC)

Protected edit request for Template:Progress barEdit

I've created Module:Progress bar, which implements {{progress bar}} in Lua (and adds support for changing the width of the bar). I've tested this at Template:Sandbox and as far as I can tell everything works. Assuming there's nothing I've missed, I'd like for Template:Progress bar to be edited to this:

<templatestyles src="Progress bar/styles.css" />
<includeonly>{{#invoke:Progress bar|progress_bar
|not_proofread={{{not proofread|}}}

Thank you! —CalendulaAsteraceae (talkcontribs) 08:06, 30 May 2022 (UTC)

@CalendulaAsteraceae FYI, I don't think you need to verbosely pass through all the parameters: you're using Module:Arguments which happily pulls the arguments out of the mw.getCurrentFrame().getParent(). All you should need is {{#invoke:Progress bar|progress_bar}} (I think) Inductiveloadtalk/contribs 19:52, 31 May 2022 (UTC)
@Inductiveload Awesome, thank you! —CalendulaAsteraceae (talkcontribs) 21:31, 31 May 2022 (UTC)
Updated edit request:
<templatestyles src="Progress bar/styles.css" />
<includeonly>{{#invoke:Progress bar|progress_bar}}</includeonly><noinclude>
CalendulaAsteraceae (talkcontribs) 09:18, 4 June 2022 (UTC)


Hello, I noticed an ip which was vandalising User:Mpaa and kept vandalising (page blanking and content removal) this administrators userpage. The ip: Special:Contributions/2601:183:CB81:6460:F078:25B3:3716:3BE6. They might need to be blocked or the page might require protection. Thanks, Terasail (talk) 15:37, 2 June 2022 (UTC)

@Terasail: Blocked. PseudoSkull (talk) 15:39, 2 June 2022 (UTC)

Bulk move request for Index:Pastorals Epistles Odes (1748).djvuEdit

See also: Index talk:Pastorals Epistles Odes (1748).djvu

Source pagenum in print Destination
Page:Pastorals_Epistles_Odes_(1748).djvu/34 (pp 112.) Page:Pastorals Epistles Odes (1748).djvu/126
Page:Pastorals_Epistles_Odes_(1748).djvu/35 (pp 113.) Page:Pastorals Epistles Odes (1748).djvu/127
Page:Pastorals_Epistles_Odes_(1748).djvu/36 (pp 114.) Page:Pastorals Epistles Odes (1748).djvu/128
Page:Pastorals_Epistles_Odes_(1748).djvu/37 (pp 115.) Page:Pastorals Epistles Odes (1748).djvu/129
Page:Pastorals_Epistles_Odes_(1748).djvu/38 (pp 116.) Page:Pastorals Epistles Odes (1748).djvu/130
Page:Pastorals_Epistles_Odes_(1748).djvu/39 (pp 117.) Page:Pastorals Epistles Odes (1748).djvu/131
Page:Pastorals_Epistles_Odes_(1748).djvu/40 (pp 118.) Page:Pastorals Epistles Odes (1748).djvu/132
Page:Pastorals_Epistles_Odes_(1748).djvu/41 (pp 119.) Page:Pastorals Epistles Odes (1748).djvu/133
Page:Pastorals_Epistles_Odes_(1748).djvu/42 (pp 120.) Page:Pastorals Epistles Odes (1748).djvu/134
Page:Pastorals_Epistles_Odes_(1748).djvu/43 (pp 121.) Page:Pastorals Epistles Odes (1748).djvu/135
Page:Pastorals_Epistles_Odes_(1748).djvu/44 (pp 122.) Page:Pastorals Epistles Odes (1748).djvu/136
Page:Pastorals_Epistles_Odes_(1748).djvu/45 (pp 123.) Page:Pastorals Epistles Odes (1748).djvu/137
Page:Pastorals_Epistles_Odes_(1748).djvu/46 (pp 124.) Page:Pastorals Epistles Odes (1748).djvu/138
Page:Pastorals_Epistles_Odes_(1748).djvu/47 (pp 125.) Page:Pastorals Epistles Odes (1748).djvu/139
Page:Pastorals_Epistles_Odes_(1748).djvu/48 (pp 126.) Page:Pastorals Epistles Odes (1748).djvu/140
Page:Pastorals_Epistles_Odes_(1748).djvu/49 (pp 127.) Page:Pastorals Epistles Odes (1748).djvu/141
Page:Pastorals_Epistles_Odes_(1748).djvu/50 (pp 128.) Page:Pastorals Epistles Odes (1748).djvu/142
Page:Pastorals_Epistles_Odes_(1748).djvu/51 (pp 129.) Page:Pastorals Epistles Odes (1748).djvu/143
Page:Pastorals_Epistles_Odes_(1748).djvu/52 (pp 130.) Page:Pastorals Epistles Odes (1748).djvu/144
Page:Pastorals_Epistles_Odes_(1748).djvu/53 (pp 131.) Page:Pastorals Epistles Odes (1748).djvu/145
Page:Pastorals_Epistles_Odes_(1748).djvu/54 (pp 132.) Page:Pastorals Epistles Odes (1748).djvu/146
Page:Pastorals_Epistles_Odes_(1748).djvu/55 (pp 133.) Page:Pastorals Epistles Odes (1748).djvu/147
Page:Pastorals_Epistles_Odes_(1748).djvu/56 (pp 134.) Page:Pastorals Epistles Odes (1748).djvu/148
Page:Pastorals_Epistles_Odes_(1748).djvu/57 (pp 135.) Page:Pastorals Epistles Odes (1748).djvu/149
Page:Pastorals_Epistles_Odes_(1748).djvu/58 (pp 136.) Page:Pastorals Epistles Odes (1748).djvu/150
Page:Pastorals_Epistles_Odes_(1748).djvu/59 (pp 137.) Page:Pastorals Epistles Odes (1748).djvu/151
Page:Pastorals_Epistles_Odes_(1748).djvu/60 (pp 138.) Page:Pastorals Epistles Odes (1748).djvu/152
Page:Pastorals_Epistles_Odes_(1748).djvu/61 (pp 139.) Page:Pastorals Epistles Odes (1748).djvu/153
Page:Pastorals_Epistles_Odes_(1748).djvu/62 (pp 140.) Page:Pastorals Epistles Odes (1748).djvu/154
Page:Pastorals_Epistles_Odes_(1748).djvu/63 (pp 141.) Page:Pastorals Epistles Odes (1748).djvu/155
Page:Pastorals_Epistles_Odes_(1748).djvu/64 (pp 142.) Page:Pastorals Epistles Odes (1748).djvu/156
Page:Pastorals_Epistles Odes_(1748).djvu/65 (pp 143.) Page:Pastorals Epistles Odes (1748).djvu/157
Page:Pastorals_Epistles_Odes_(1748).djvu/66 (pp 144.) Page:Pastorals Epistles Odes (1748).djvu/158
Page:Pastorals_Epistles_Odes_(1748).djvu/67 (pp 145.) Page:Pastorals Epistles Odes (1748).djvu/159
Page:Pastorals_Epistles_Odes_(1748).djvu/68 (pp 146.) Page:Pastorals Epistles Odes (1748).djvu/160
Page:Pastorals_Epistles_Odes_(1748).djvu/69 (pp 147.) Page:Pastorals Epistles Odes (1748).djvu/161

ShakespeareFan00 (talk) 07:52, 9 June 2022 (UTC)

The range Page:Pastorals_Epistles_Odes_(1748).djvu/70 to Page:Pastorals_Epistles_Odes_(1748).djvu/76 are blank and should be at the end of the work as indicated by the pagelist for the Index. ShakespeareFan00 (talk) 07:54, 9 June 2022 (UTC)

Done. Mpaa (talk) 20:54, 10 June 2022 (UTC)

Index:The complete works of Count Tolstoy (IA completeworksof02tols).pdfEdit

A new DJVU scan was uploaded for Volume 2 (with some missing pages re-instated) as a Djvu (see: Wikisource:Proposed_deletions#The_complete_works_of_Count_Tolstoy), and so the pages here were migrated back from the PDF to the new scan, and any transclusions were updated.

Because I can't delete the generated redirects when migrating pages between scans, it will need an Admin to do this, and I am requesting this here.

Done, I have removed all pages in Vol.2 pdf.Mpaa (talk) 21:41, 17 June 2022 (UTC)

I had also migrated the relatively small number of pages for Index:Complete_Works_of_Count_Tolstoy_-_20.pdf as well.

This leaves Volume 9 to be migrated across and Volume 1 carefully compared between the DJVU and PDF versions.

ShakespeareFan00 (talk) 14:03, 16 June 2022 (UTC)

Index Migration:Edit

Source: - Index:The complete works of Count Tolstoy (IA completeworksofc09tols).pdf
Destination:- Index:Complete Works of Count Tolstoy - 09.djvu
Page-ranges: 1-12,16,18-24, 179-182, 213, 239-242, 289-292, 324-326, 323-326, 363-366, 407-412
ShakespeareFan00 (talk) 14:10, 16 June 2022 (UTC)

Done. Mpaa (talk) 21:09, 17 June 2022 (UTC)

Index MigrationEdit

Source:Index:The complete works of Count Tolstoy (IA completeworksofc01tols).pdf
Destination:Index:Complete Works of Count Tolstoy - 01.djvu
Page-ranges: 109-112 , 168, 187-188, 290, 544

Done, most of the pages were already existing, so no move was done for them. Mpaa (talk) 21:18, 17 June 2022 (UTC)

Source: Index:The_complete_works_of_Count_Tolstoy_(IA_completeworksofc19tols).pdf Destination: Index:Complete Works of Count Tolstoy - 19.djvu Page-range: 93

Done. Mpaa (talk) 21:18, 17 June 2022 (UTC)

Which with the moves of Volume 2, 9 and 20 will allow removal of the PDF based Index for the entire set in favour of the DJVU versions. ShakespeareFan00 (talk) 14:27, 16 June 2022 (UTC)

Left to do: rm all pages in Page/Index ns relative to pdf versions.Mpaa (talk) 21:43, 17 June 2022 (UTC)

Migration of pages due to updated source file.Edit

Source oldid pp (if relevant) Destination
Page:The Complete Peerage Ed 1 Vol 6.djvu/483 . . Page:The_Complete_Peerage_Ed_1_Vol_6.djvu/11
Page:The Complete Peerage Ed 1 Vol 6.djvu/484 Page:The_Complete_Peerage_Ed_1_Vol_6.djvu/12
Page:The Complete Peerage Ed 1 Vol 6.djvu/485 Page:The_Complete_Peerage_Ed_1_Vol_6.djvu/13
Page:The_Complete_Peerage_Ed_1_Vol_6.djvu/2 9861036 (TOC) Page:The Complete Peerage Ed 1 Vol 6.djvu/14
Page:The_Complete_Peerage_Ed_1_Vol_6.djvu/3 9861037 (pp001) Page:The Complete Peerage Ed 1 Vol 6.djvu/15
Page:The_Complete_Peerage_Ed_1_Vol_6.djvu/4 9861038 (pp002) Page:The Complete Peerage Ed 1 Vol 6.djvu/16
Page:The Complete Peerage Ed 1 Vol 6.djvu/5 (pp003) Page:The Complete Peerage Ed 1 Vol 6.djvu/17
Page:The Complete Peerage Ed 1 Vol 6.djvu/6 (pp004) Page:The Complete Peerage Ed 1 Vol 6.djvu/18
Page:The_Complete_Peerage_Ed_1_Vol_6.djvu/7 9861042 (pp005) Page:The Complete Peerage Ed 1 Vol 6.djvu/19
Page:The_Complete_Peerage_Ed_1_Vol_6.djvu/8 9861043 (pp006) Page:The Complete Peerage Ed 1 Vol 6.djvu/20
Page:The Complete Peerage Ed 1 Vol 6.djvu/9 (pp007) Page:The Complete Peerage Ed 1 Vol 6.djvu/21
Page:The Complete Peerage Ed 1 Vol 6.djvu/10 (pp 008) Page:The Complete Peerage Ed 1 Vol 6.djvu/22
Page:The Complete Peerage Ed 1 Vol 6.djvu/11 (pp 009) Page:The Complete Peerage Ed 1 Vol 6.djvu/23
Page:The Complete Peerage Ed 1 Vol 6.djvu/12 (pp 010) Page:The Complete Peerage Ed 1 Vol 6.djvu/24
Page:The Complete Peerage Ed 1 Vol 6.djvu/13 (pp 011) Page:The Complete Peerage Ed 1 Vol 6.djvu/25
... ... (Same shift occcurs upto) ...
Page:The Complete Peerage Ed 1 Vol 6.djvu/470 (pp468) Page:The Complete Peerage Ed 1 Vol 6.djvu/482
Page:The Complete Peerage Ed 1 Vol 6.djvu/471 (pp469) Page:The Complete Peerage Ed 1 Vol 6.djvu/483
Page:The Complete Peerage Ed 1 Vol 6.djvu/472 (pp470) page:The Complete Peerage Ed 1 Vol 6.djvu/484
Page:The Complete Peerage Ed 1 Vol 6.djvu/473 (pp471) Page:The Complete Peerage Ed 1 Vol 6.djvu/485
Page:The Complete Peerage Ed 1 Vol 6.djvu/474 (pp472) Page:The Complete Peerage Ed 1 Vol 6.djvu/486
Page:The Complete Peerage Ed 1 Vol 6.djvu/475 (pp473) Page:The Complete Peerage Ed 1 Vol 6.djvu/487
Page:The Complete Peerage Ed 1 Vol 6.djvu/476 (pp474) Page:The Complete Peerage Ed 1 Vol 6.djvu/488
Page:The Complete Peerage Ed 1 Vol 6.djvu/477 (pp475) Page:The Complete Peerage Ed 1 Vol 6.djvu/489
Page:The Complete Peerage Ed 1 Vol 6.djvu/478 (pp476) Page:The Complete Peerage Ed 1 Vol 6.djvu/490
Page:The Complete Peerage Ed 1 Vol 6.djvu/479 (pp477) Page:The Complete Peerage Ed 1 Vol 6.djvu/491
Page:The Complete Peerage Ed 1 Vol 6.djvu/480 (pp478) Page:The Complete Peerage Ed 1 Vol 6.djvu/492
Page:The Complete Peerage Ed 1 Vol 6.djvu/481 (pp479) Page:The Complete Peerage Ed 1 Vol 6.djvu/493
Page:The Complete Peerage Ed 1 Vol 6.djvu/482 (pp480) Page:The Complete Peerage Ed 1 Vol 6.djvu/494

ShakespeareFan00 (talk) 07:53, 19 June 2022 (UTC)

@ShakespeareFan00: We can deal with this once the deletion discussion is completed. Please don't make multiple requests about the same work in different venues. Xover (talk) 08:54, 19 June 2022 (UTC)