Wikisource:Administrators' noticeboard

Administrators' noticeboard

Wikisource snapshot

No. of pages = 4,048,742
No. of articles = 998,378
No. of files = 16,840
No. of edits = 13,242,494

---

No. of pages in Main = 575,821
No. of pages in Page: = 3,007,700
No. validated in Page: = 596,591
No. proofread in Page: = 1,092,146
No. not proofread in Page: = 1,053,265
No. problematic in Page: = 40,873
No. of validated works = 5,956
No. of proofread only works = 5,332
No. of pages in Main⁠
with transclusions = 368,246
% transcluded pages in Main = 63.95
Σ pages in Main⁠

---

No. of users = 3,081,251
No. of active users = 414
No. of group:autopatrolled = 492
No. in group:sysop = 21
No. in group:bureaucrat = 2
No. in group:bot = 16

Statistics
User preference statistics
Special:Statistics

Checkuser requests

• 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 requests

• To request a global rename, go to Special:GlobalRenameRequest.

Other

Interface administrators

Hi. Please see https://www.mediawiki.org/wiki/Topic:Unisfu5m161hs4zl. 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…? 114.73.248.245 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 2FA

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. Inductiveload—talk/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. Inductiveload—talk/contribs 10:08, 1 October 2021 (UTC)

Request move

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)

Import help

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. Inductiveload—talk/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 mul.ws?--Zyephyrus (talk) 12:59, 28 August 2021 (UTC)

Or this one, Ancient Greek and French, might be on mul.ws and offer links to both fr.ws and el.ws.

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 mul.ws. 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:iwpage — billinghurst sDrewth 14:10, 29 August 2021 (UTC)

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

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)

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

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)

@Xover:

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

631

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)

Protected edit request for Template:Progress bar

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
|total={{{total|}}}
|validated={{{validated|}}}
|proofread={{{proofread|}}}
|not_proofread={{{not proofread|}}}
|problematic={{{problematic|}}}
|notext={{{notext|}}}
|height={{{height|}}}
|width={{{width|}}}
}}</includeonly><noinclude>
{{documentation}}
</noinclude>

Thank you! —CalendulaAsteraceae (talk • contribs) 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) Inductiveload—talk/contribs 19:52, 31 May 2022 (UTC)

@Inductiveload Awesome, thank you! —CalendulaAsteraceae (talk • contribs) 21:31, 31 May 2022 (UTC)

Updated edit request:

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

—CalendulaAsteraceae (talk • contribs) 09:18, 4 June 2022 (UTC)

@Inductiveload, does the above code look good to you? —CalendulaAsteraceae (talk • contribs) 06:56, 22 July 2022 (UTC)

Still interested in this. —CalendulaAsteraceae (talk • contribs) 05:05, 7 August 2022 (UTC)

Index Migration

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.

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)

@Xover, You closed the DR, Can we know handle the page realignment request? ShakespeareFan00 (talk) 09:33, 31 July 2022 (UTC)

Sure. But I'm feeling too depressed and frustrated at this nonsensical hoarding of bulk-created junk to want to put effort into putting lipstick on it, so somebody else is going to have to take care of this request. Xover (talk) 09:38, 31 July 2022 (UTC)

Request at MediaWiki talk:Protectedpagetext

There is a request at MediaWiki talk:Protectedpagetext#Protected edit request on 25 July 2022. Can somebody more competent have a look at it? -- Jan Kameníček (talk) 08:50, 26 July 2022 (UTC)

I'll follow up. Xover (talk) 09:51, 26 July 2022 (UTC)

Edit request: merge Template:PD-US and Template:PD/US

I've created Module:PD-US, which allows {{PD-US}} and {{PD/US}} to be implemented in a much more streamlined way, and as the same template. Assuming the module really does work as well as I think it does, could {{PD/US}} be redirected to {{PD-US}}? —CalendulaAsteraceae (talk • contribs) 04:58, 25 August 2022 (UTC)

Ehm. Can someone remind me of the difference between {{PD-US}} and {{PD/US}}? And why we need {{PD-old-99-US}}, {{PD-old-80-US}}, {{PD-old-75-US}}, {{PD-old-70-US}}, {{PD-old-60-US}}, {{PD-old-50-US}}, {{PD-old-30-US}}, {{PD-old-25-US}} (and probably more that I didn't find in a quick search)? And why we're reporting this in strict ten year increments (that looks like an artefact of the limitations of templates rather than anything else).

What I'm saying is, presuming Module:PD-US works as intended, doesn't this just drop-in replace that whole cluster of twisty little templates? Xover (talk) 14:26, 25 August 2022 (UTC)

I believe that set of templates is meant to replicate various copyright durations worldwide; there's no point in mentioning e.g. life+55 because there's no nation that uses that. We could probably simplify it; there's not many nations below life+50, and that virtually guarantees they won't care about foreign copyrights and we host few works from them.--Prosfilaes (talk) 17:26, 25 August 2022 (UTC)

But we're not really describing jurisdictions, we're describing pma. terms as a concept and relating it to the time passed since this specific author's death. Why not just say "any country with a term longer than specific number of years since deathyear" (or however we phrase it)? Xover (talk) 17:37, 25 August 2022 (UTC)

@Xover: Historically, {{PD-US}} didn't have a death-year parameter, and {{PD/US}} required one. (I've migrated {{PD-US}} to use the module, so it has a death-year parameter now.) I'm pretty sure {{PD-old-99-US}} and so forth are just an artefact of the setup for {{PD/US}}, since they're not supposed to be used directly.

The other purpose of the pma buckets is to put works into PD-old-[years]-US categories like Category:PD-old-70-US. Do these categories serve a useful purpose? Because if not, it would be straightforward to remove the bucketing and simplify the license text like you suggested. —CalendulaAsteraceae (talk • contribs) 00:41, 26 August 2022 (UTC)

I suppose the buckets might have some use if we discover an issue that affects only a particular bracket, but I don't really see that as a likely scenario and tracking cats for such issues can be easily added when needed. So absent any other factors I'd be inclined to say we should just drop the bracketing and get rid of the helper templates. --Xover (talk) 05:49, 27 August 2022 (UTC)

PD-US is for works where the author’s death date is not known or for e.g. collective works where that would be difficult to determine. PD/US is for works where date-of-death is known, and sorts them into useful categories. CalendulaAsteraceae: Does your new module replicate the above? That’s the difference in the templates, so far as I know. TE(æ)A,ea. (talk) 01:49, 26 August 2022 (UTC)

@TE(æ)A,ea., yes, if you don't put a death-year parameter in, the module will just produce {{PD-US}}. —CalendulaAsteraceae (talk • contribs) 01:52, 26 August 2022 (UTC)

CalendulaAsteraceae: Also, it’s broken. TE(æ)A,ea. (talk) 02:25, 26 August 2022 (UTC)

@TE(æ)A,ea. I am very sorry about that. I didn't realize that {{license}} automatically adds an Author- prefix to the beginning of categories in the author namespace. —CalendulaAsteraceae (talk • contribs) 02:32, 26 August 2022 (UTC)

A demonstration:

{{PD-US}}

This work is in the public domain in the United States because it was published before January 1, 1928.

---

This work may be in the public domain in countries and areas with longer native copyright terms that apply the rule of the shorter term to foreign works.

{{PD-US|1982}}

This work is in the public domain in the United States because it was published before January 1, 1928.

---

The longest-living author of this work died in 1982, so this work is in the public domain in countries and areas where the copyright term is the author's life plus 40 years or less. This work may be in the public domain in countries and areas with longer native copyright terms that apply the rule of the shorter term to foreign works.

—CalendulaAsteraceae (talk • contribs) 23:08, 26 August 2022 (UTC)

Mass import from Wikibooks

Does anyone have any better way before I use Special:Import to import many pages per b:Wikibooks:Requests_for_deletion#Developing_A_Universal_Religion? b:Special:MovePage/Developing_A_Universal_Religion says that there are 116 subpages and the corresponding talk page has 20 subpages.--Jusjih (talk) 21:56, 10 September 2022 (UTC)

@Jusjih: I'm not aware of any better way than Special:Import.

However, that being said, is this really in scope for enWS? One thing is that the uploaded PDF is not previously published, but a modified edition made by the author for online distribution. But worse is that I find no trace of "Stephenson-Hockey Publishing" anywhere, except in connection with this book. Which means this is most likely an ad hoc vanity publisher, which doesn't actually count as previously published. And if the publisher was a real one, I'd question the author's public domain release, since that is not usually permitted under a standard publishing contract. I'd say this work, regardless of its relative merits, is probably out of scope on all Wikimedia projects (including Commons, whose scope policy would probably exclude it on roughly the same grounds as Wikibooks' does), and definitely on English Wikisource. Xover (talk) 07:33, 11 September 2022 (UTC)

Seeing your objection, I told Wikibooks about our talks here.--Jusjih (talk) 19:45, 11 September 2022 (UTC)

@Jusjih, @Xover:, is not it possible to use https://meta.toolforge.org/catanalysis to get a list of all pages with a certain prefix, then copy the list of Special:Export, get an xml dump with all the revision history and then import the xml dump to wikisource? I’m just suggesting a possible way to mass import, and not making any comments regarding this specific book, and if it’s in the scope of Wikisource. That’s not up to me to decide. -🇺🇦Слава🇺🇦Україні🇺🇦Героям🇺🇦Слава🇺🇦(talk)🇺🇦 09:05, 23 October 2022 (UTC)

@Slava Ukraini Heroyam Slava 123: Sure. But the XML dumps are pretty scary and there are lots of gotchas so it's really more of a tool of last resort. Xover (talk) 09:12, 23 October 2022 (UTC)

@Xover:, I see. I suggested this because that’s how Middle English Wikipedia was moved to Incubator Plus. -🇺🇦Слава🇺🇦Україні🇺🇦Героям🇺🇦Слава🇺🇦(talk)🇺🇦 21:03, 23 October 2022 (UTC)

A letter on "Uncle Tom's cabin"

I'm trying to transclude this document, but it's saying that there is no such index. I think it's because the DJVU file has quotation marks in its name. Could someone please help me with this?

For reference, the index file is Index:A letter on "Uncle Tom's cabin" (1852).djvu.

Thanks, Lizardcreator (talk) 03:55, 15 September 2022 (UTC)

@Lizardcreator The quotation marks can be escaped like so by replacing them with the HTML entity ", but I'm not sure if this is the ideal solution. This index is especially tricky because it includes both " and ' in the title; if an index title only contains double quotes, it can be wrapped with single quotes: see the transclusion of "A Modern Hercules," The Tale of a Sculptress (1899). Shells-shells (talk) 04:50, 15 September 2022 (UTC)

@Shells-shells: As a FYI, the even easier way to do this is using #tag, like {{#tag:pages||index=A letter on "Uncle Tom's cabin" (1852).djvu|from=...|to=...}} — billinghurst sDrewth 13:35, 19 March 2023 (UTC)

Time to review protected pages

Hi all,

Special:ProtectedTitles (pages that do not exist and are protected from creation) and Special:ProtectedPages (pages that exist but have protection applied to limit changes or moves) have amassed quite a lot of cruft that seem unlikely to still be in need of protection. In other words, it's about time we go through those lists and remove protection settings for pages that no longer need it.

For example, we have create protection for a bunch of pages with "naughty" titles that were spammed by a vandal years ago, but that are now very unlikely to be targeted. These should have their protection removed so they do not show up on that list (where they might give people ideas). Contrariwise, I Have a Dream is create protected because it is a copyvio that keeps getting added and so it still needs protection.

Each entry on those lists need that sort of assessment, and the goal is to have as few protected pages as possible (but not less than necessary). Main rule of thumb is: if the protection was the result of a problem several years ago, and has not been recurring or ongoing, then the protection is probably not now needed.

I will probably start going through the lists at some point, but this should definitely be a task that all admins help out with as their time and inclination allows. Xover (talk) 10:20, 20 November 2022 (UTC)

Re ProtectedTitles, I don't think that we should waste much time looking through the list, it is works we shouldn't have and vandal only pages that we will never have. If it is getting cruft that would expire, we would be better off having some rigour on the duration we use, and if we don't feel that the current dropdown is sufficient, then we can add to mewdiawiki:protect-expiry-options, otherwise I just typically just type a date YYYY-MM-D which works perfectly for me.

Re ProtectedPages, I would think that the only pages we would wish to review are those that are fully protected in the main namespace, why would we want to review others elsewhere? To what benefit? They are not system source users.

Run a light eyeball down the list … sure, though the best system approach is not hitting these things too hard with protection in the first place. If we think that the information about how to appeal or address a blocked page is insufficient, then let us look at the default messages, and how we can improve them. The list of default and adapted messages is at https://en.wikisource.org/w/index.php?title=Special:AllMessages&offset=Protect&limit=100 — billinghurst sDrewth 04:50, 21 November 2022 (UTC)

I would like to hide offensive titles from the public view unless any other comments.--Jusjih (talk) 04:14, 17 March 2023 (UTC)

I tried to hide an offensively named deleted template from the deletion and protection logs, but removing it from Special:ProtectedTitles requires unprotecting it. Revert my acts if desired.--Jusjih (talk) 03:40, 19 March 2023 (UTC)

@Jusjih: If there are log files that need oversight, then talk to a steward and get them to oversight, it won't be a matter for us with admin rights. Otherwise, it seems you are trying to have your pie and to eat it too. The pages are not existing, so there is not reason to hide them; they won't get indexed and shouldn't be searchable. Every time you do something you are creating logs, so these become overt in the logs. The listing at ProtectedTitles is system generated to show what we have blocked from being created, and as such is a list, and I doubt that it is especially indexed by bots. It seems that this is a solution in search of a problem. I am not seeing a general problem that needs fixing, especially from Joe Public's point of view. — billinghurst sDrewth 13:51, 19 March 2023 (UTC)

Then ProtectedTitles may need a new function from very privileged users to hide offensive things. I abstain from this topic.--Jusjih (talk) 02:34, 20 March 2023 (UTC)

It exists, it is called suppression (ws:Suppressors), rights explained at special:ListGroupRights, and for us we either need to elect two, or we utilise stewards in the absence of us having elected suppressors, per m:Oversight policy. — billinghurst sDrewth 05:39, 20 March 2023 (UTC)

Autopatroller Request for Seperation

Hi, I would love to request autopatroller status, if possible. I've been consistently making edits for over 3 years. I haven't had any complaints about major mistakes during this time. I just think it will be helpful to reduce the number of pages needing to be patrolled. Thanks! Seperation (talk) 10:03, 12 January 2023 (UTC)

Download button vs. download sidebar

I’m reporting this here because I think an administrator needs to fix a page. The download features in the sidebar don’t do the same thing as the “download” button which floats to the right of the title; see, e.g., here, where the “Download” button gets the whole book, and the download sidebar features only get a list of the books. TE(æ)A,ea. (talk) 20:15, 3 February 2023 (UTC)

Corruption on uploading new versions

This is an old problem that has never been dealt with. I have fruitlessly sought help in the usual places. On uploading new versions of files, they are often corrupted by the inclusion of File:Fileicon-pdf.png and the pages become hidden. I have brought this matter up before and it was thought it was because my pdfs had been through a pdf editor. I am now reviewing some older files before I had an editor and the same problem is still arising. These are straight forward simple pdfs. The file in question is Amulet 1833.pdf in Category "Poems by Letitia Elizabeth Landon in gift books". The pages are still there but they are hidden. They have been fully validated and transcluded. I was only making a very minor amendment. The problem is exacerbated by the fact that I cannot revert to the previous version. That I did and the corruption was carried back into that version too.

Could someone please repair Amulet 1833.pdf? and could someone please look carefully into this uploading problem and find out what is going on? This is making my work for wikisource more and more impossible.

Esme Shepherd (talk) 10:48, 6 February 2023 (UTC)

Hi Peter,

The problem is with the PDF files themselves, and they're causing MediaWiki (the software that implements this wiki) to choke when trying to extract things like page resolution and page count. This is not a general problem with PDF files because the vast majority of them work just fine. In other words, you need to look to whatever tools you are using to make these.

In addition, File:Amulet 1833.pdf appears to be yet another one of your self-compiled collections of things published in a variety of places, rather than a collection that has been previously published by a reputable publishing house (in practical effect they are your own self-published collections). Such arbitrary user-generated compilations are out of scope on English Wikisource and are very likely to be deleted whenever somebody gets around to going through your uploads looking to clean this up. Please stick to uploading previously published works as they were published. You don't have to actually proofread the entire original publication if it just contains one poem of interest, and we can absolutely host the poem on its own page as well as have Portal: pages for collecting them, but cutting out individual poems from disparate sources to make your own collection is not ok. Xover (talk) 12:42, 6 February 2023 (UTC)

Thank you for your attention. I would point out that these pdf files are in fact wholly from a single source and for years never gave the slightest problem and they are taken as they were published as you require. Not entire publications but only those pages of interest. If you want to see these original pages as they were published they can be found in File:The Amulet 1833.pdf They should also be visible in File:Amulet 1833.pdf but they have become hidden. I have been using this method since around 2016 when I received full approval for it. The pdfs are all put together in pages on my Mac and converted en bloc. Esme Shepherd (talk) 16:40, 6 February 2023 (UTC)

Please add domain to whitelist

Got my first spam filter notice. From what I can discern, I'm supposed to request that an administrator add the offending URL's domain to the site's whitelist. So here goes...

The offending URL: https://XXX/492jILlPtlA?t=132 (replace XXX with the standard YouTube domain triggered by the filter)

Transcript file: https://en.wikisource.org/w/index.php?title=Page:Final_Report_of_the_Select_Committee_to_Investigate_the_January_6th_Attack_on_the_United_States_Capitol.pdf/271&action=edit&redlink=1

The link connects to a video that is reflective of the content.

Let me know what I need to do differently if I have to do this again. Thank you. Snafu22q (talk) 09:14, 7 February 2023 (UTC)

@Snafu22q: Done — you can go ahead and try it now if you'd like, see if that works. PseudoSkull (talk) 15:35, 7 February 2023 (UTC)

It DID work. Thank you. Snafu22q (talk) 23:19, 7 February 2023 (UTC)

@Snafu22q: The urls for youtube are easily modified to get through the blacklist component. Number one is don't use youtu.be and instead utilise the full youtube.com url. Secondly where we have blacklist components that are based on the variable after the question mark eg. youtube.com/?somebit=this&anotherbit=that, you can usually swap the variables around to youtube.com/?anotherbit=that&somebit=this The blacklist is a heavyweight hammer for domain only listings, though when we play outside of the domain name then we typically have plenty of play space. — billinghurst sDrewth 04:33, 8 February 2023 (UTC)

Plus if you are truly wishing to maintain the full look you can always do something like [https://www.youtube.com/watch?v=492jILlPtlA&t=132s https://youtu.be/492jILlPtlA?t=132] and you get ZERO rejection. — billinghurst sDrewth 04:37, 8 February 2023 (UTC)

Threatening emails

I just received a threatening email from a user. I forwarded it to the Wikimedia Foundation. If anyone else received it, I'm not sure how else to deal with it without engaging the user further. (I've also blocked the user.) —Beleg Tâl (talk) 01:27, 17 February 2023 (UTC)

@Beleg Tâl: It is most definitely this user: Wikipedia:Long-term abuse/Projects PseudoSkull (talk) 02:06, 17 February 2023 (UTC)

Another whitelist request

Hello, Admin types. I've been bitten by the spam filter so this message is to request adding the offending URL to the Spam-whitelist.

The file I'm working on is page 330 of: https://en.wikisource.org/w/index.php?title=Page:Final_Report_of_the_Select_Committee_to_Investigate_the_January_6th_Attack_on_the_United_States_Capitol.pdf/

This is the string I was told triggered the filter: t.co/7JqTWYUgOr%22 (in item #272)

I was told in a previous request how to circumvent a YouTube URL from being activated, which I've used successfully now a number of times. If someone knows how to skirt this instance, I'd be interested in learning how.

Thank you. Snafu22q (talk) 08:21, 17 February 2023 (UTC)

Is there a form to submit requests to admins, like a ticket system? I asked for the above whitelist edit 9 days ago and nothing has been done as far as I know. I have no idea what their workload is, nor am I attempting to complain in any way, but now I have a couple of additional whitelist requests as well from the same work, and I just want to make sure I'm not making this harder than it needs to be.

In the event an admin reads this, the additional edits: (1) the first is like the original request ... though the string at the end is different, it starts the same: t.co/ and (2) from page 543, the string infowars.com is preventing the file from being saved.

Thank you. Snafu22q (talk) 09:01, 26 February 2023 (UTC)

@Snafu22q: The slavish replication of the link is not required, feel welcome to have a twitter.com url, if you do want a replica looking link, then feel free to follow the link, then put [https://twitter.com/(the link) t.co/7JqTWYUgOr%22], re the infowars link, just wrap it in <nowiki></nowiki>, no issue that it won't wikilink. — billinghurst sDrewth 12:51, 19 March 2023 (UTC)

Page protection?

Namely the following templates, which are widely used, assuming they do not have errors.

{{Internet Archive link}},{{IAl}},{{GBS}},{{HTl}}, {{HathiTrust link}} , {{IA small link}} and {{ext scan link}} ShakespeareFan00 (talk) 14:52, 26 February 2023 (UTC)

Done Though as a comment, we should have some rigour and stopped the proliferation of forked templates. If we need smaller text either just wrap it in {tl|smaller}} or if we need it as a template, then we should nest the parent template, not create yet another variation. If we have improvements, then we can have that flow through. — billinghurst sDrewth 14:06, 19 March 2023 (UTC)

Agreed, and there are efforts by others at the moment to consolidate certain templates as I understand it.ShakespeareFan00 (talk) 14:09, 19 March 2023 (UTC)

This is not about forcing to one template, I am talking about either having a base template and nesting that into parent template rather than all being done as a different construction. — billinghurst sDrewth 21:59, 19 March 2023 (UTC)

Edit requests for Template:RunningHeader

I've been working on migrating this template to Lua, and I'd like to implement my edits. I'm pretty happy with where it's at now, although I certainly welcome feedback.

Notes:

• The logic for {{RunningHeader}} is at Module:RunningHeader/core. Implementations of other running header templates are at Module:RunningHeader. This will allow Module:RunningHeader/core to be protected while still making it easy to edit the other templates.
• I've added support to {{RunningHeader}} for specifying the number of cells, meaning we won't need separate templates like {{Rh/5}}.
• I've added the styles for {{RunningHeader-centered}}, {{Rh/1}}, {{Rvh/header}}, {{Rh/1rv}}, and {{Rh/3}} to the stylesheet. (With the Lua module, the extra styles are the only reason we would need {{Rh/1}} and {{Rh/3}}.)
• Test cases: Template:RunningHeader/testcases.

Previous discussion:

• WS:Scriptorium#Code review for RunningHeader templates
• Template talk:RunningHeader#Merging the various running header CSS pages and Template talk:RunningHeader#Migrating this template to Lua

Specific edit requests:

1. Replace the contents of {{RunningHeader}} with

   <templatestyles src="RunningHeader/styles.css" />{{#invoke:RunningHeader/core|running_header}}<noinclude>{{documentation}}</noinclude>

2. Replace the contents of Template:RunningHeader/styles.css with

   /* Base style */
   
   .wst-running-header {
   	display: flex;
   	width: 100%;
   	text-align: center;
   	justify-content: space-between;
   }
   .wst-running-header-cell:first-child {
   	text-align: left;
   }
   .wst-running-header-cell:last-child {
   	text-align: right;
   }
   .wst-running-header-cell > p {
   	margin: 0;
   }
   
   /* 1 cell */
   
   .wst-running-header-1 {
   	justify-content: center;
   }
   .wst-running-header-1 .wst-running-header-cell:first-child {
   	text-align: center;
   }
   
   /* 3 cells */
   
   .wst-running-header-3.centered .wst-running-header-cell {
   	width:15%;
   }
   .wst-running-header-3.centered .wst-running-header-cell:nth-child(2) {
   	width:70%;
   }
   
   /* 4 cells */
   
   .wst-running-header-4 .wst-running-header-cell:nth-child(2) {
   	text-align: left;
   }
   .wst-running-header-4 .wst-running-header-cell:nth-child(3) {
   	text-align: right;
   }
   
   .wst-running-header-4.centered .wst-running-header-cell {
   	width: 20%;
   }
   .wst-running-header-4.centered .wst-running-header-cell:nth-child(2),
   .wst-running-header-4.centered .wst-running-header-cell:nth-child(3) {
   	width: 30%;
   	text-align: center;
   }
   
   /* Implement 'special' handling for some common situations */
   
   /* Single-line issue banner (type 1: issue and volume as small-caps) */
   
   .wst-running-header-3.__issuebanner1 .wst-running-header-cell:first-child,
   .wst-running-header-3.__issuebanner1 .wst-running-header-cell:last-child {
   	font-variant: small-caps;
   }
   .wst-running-header-3.__nc .wst-running-header-cell{
   	font-variant-caps: normal;
   }
   

Thanks! —CalendulaAsteraceae (talk • contribs) 03:50, 27 February 2023 (UTC)

Still interested in this. —CalendulaAsteraceae (talk • contribs) 04:26, 8 April 2023 (UTC)

Wikisource: Constitution of Texas

I tried to make edits to add sections which aren't already included (due to recent amendments) but was prohibited with a warning that it was "automatically disallowed". How can this be fixed so I can make the edits? Quidam65 (talk) 18:56, 7 March 2023 (UTC)

@Quidam65: I have reverted your changes. Our documents are static as they are published versions of a time. The 2022 version should be its own version, and I will see if I can resurrect it separately from your contributions. It also looks s though there is a need for some general fixing anyway in that space. — billinghurst sDrewth 14:02, 19 March 2023 (UTC)

I was able to get a copy of the edits and create a 2022 version, and create {{versions}}. We should be looking for a scanned back version, or a complete electronic form and marking it as such. — billinghurst sDrewth 21:53, 19 March 2023 (UTC)

Moving all subpages in one click

Hi, Could someone move Above the battle and all subpages to Above the Battle. It seems special permission is needed to do so. Thanks, Yann (talk) 22:27, 13 March 2023 (UTC)

Hi. Would be a good occasion to renane subpages from roman to numeral. Mpaa (talk) 08:13, 14 March 2023 (UTC)

Ah yes, I didn't think about that. I guess that can't be done automatically. Yann (talk) 11:57, 14 March 2023 (UTC)

Mpaa might be able to script it as a Bot request, maybe? —Beleg Tâl (talk) 12:56, 14 March 2023 (UTC)

Not needed, I did it manually. Thanks for your answers. Yann (talk) 15:22, 14 March 2023 (UTC)

 Comment [Oh I cleaned it up as it came up in a maintenance log.] We would not typically keep redirects as subpages, we have found that they become problematic. I moved to chapter specifically in the name, if we are moving we may as well update to the style. — billinghurst sDrewth 13:55, 19 March 2023 (UTC)

OK, thanks. Yann (talk) 16:23, 19 March 2023 (UTC)

Protected edit request

Can somebody have a look at the protected edit request at MediaWiki talk:Epub.css, please? -- Jan Kameníček (talk) 22:09, 24 March 2023 (UTC)

@Jan.Kamenicek: Done Xover (talk) 09:35, 25 March 2023 (UTC)

Hyperion Index Corrupted

The index for Hyperion, a romance.djvu is hosed up. Scanned text and source image are 2 pages off. Don't know how to fix it and doubt I would have the permissions if I did. snafu22q (talk) 07:48, 28 March 2023 (UTC)

This is a classic problem from that period of time when the IA-upload tool tried to convert pdf to djvu and didn't do it very well. Working on replacing the file. Beeswaxcandle (talk) 08:58, 28 March 2023 (UTC)

Updated file and Index now available. Beeswaxcandle (talk) 09:18, 28 March 2023 (UTC)

Move

Hi, Please move Confessions (Rousseau) and its subpages to The Confessions of Jean-Jacques Rousseau (Aldus, 1903) to make place for disambiguation. Thanks, Yann (talk) 11:21, 27 April 2023 (UTC)

The work as reproduced says "The Complete Confessions of J.-J. Rousseau", isn't that suitable? I can see 1903 if the remainder of the title is the same, however, the work currently produced doesn't have Aldus on the title page. — billinghurst sDrewth 11:29, 27 April 2023 (UTC)

This is the title used in the scans: Index:The Confessions of Jean-Jacques Rousseau, Aldus, 1903, v. 1.djvu. Aldus is to disambiguate from other editions with the same name. Yann (talk) 13:41, 27 April 2023 (UTC)

Although Aldus printed this several times, it is unlikely we will have several copies here, so the date could be omitted. Yann (talk) 15:32, 29 April 2023 (UTC)

Moved. I have omitted the publisher as well for now, mere existence of more editions is usually not a reason to disambiguate, we usually disambiguate only when we host more editions of the same work. I have also omitted the hyphen from the Rousseau’s name in the title to follow the original. --Jan Kameníček (talk) 21:44, 29 April 2023 (UTC)

After I was shown that there are already two indexes for two different editions, I moved it to The Confessions of Jean Jacques Rousseau (Aldus). --Jan Kameníček (talk) 22:03, 29 April 2023 (UTC)

File move right

Hi, Can I get the file move right please? Thanks, Yann (talk) 12:30, 7 May 2023 (UTC)

@Yann: So far as I know we don't use the filemover right on enWS (among other reasons, because the volume of them is not even a fraction of Commons'). Just drop your move requests here (or feel free to dump them on my talk page). Xover (talk) 17:30, 7 May 2023 (UTC)

Index:Rousseau - Profession of Faith of a Savoyard Vicar, 1889.pdf

Hi, Please delete this and all pages. I moved everything to Index:Rousseau - Profession of Faith of a Savoyard Vicar, 1889.djvu. Thanks, Yann (talk) 17:04, 13 May 2023 (UTC)

@Yann: Done Xover (talk) 20:14, 13 May 2023 (UTC)

@Yann: You can also mark such files for deletion with {{speedy|reason}}, just noting that it applies to all the subpages too. --Jan Kameníček (talk) 20:52, 13 May 2023 (UTC)

Edit request for Template:Greek

I've implemented this template in Lua. Code at Module:Greek, template at {{Greek/sandbox}}, test cases at Template:Greek/testcases. The Lua implementation is a significant improvement w.r.t. template include size. 1911 Encyclopædia Britannica/Hydraulics has problems due to heavy use of {{Greek}}, but User:CalendulaAsteraceae/Staging, which contains the same content but using {{Greek/sandbox}}, can be transcluded to Wikisource:Sandbox without issue.

Edit request: replace the content of {{Greek}} with

<templatestyles src="Greek/styles.css"/><includeonly>{{#invoke:Greek|greek}}</includeonly><noinclude>
{{documentation}}
</noinclude>

Thanks! —CalendulaAsteraceae (talk • contribs) 07:12, 14 May 2023 (UTC)

@CalendulaAsteraceae: Sorry about the lame response time. Do feel free to contact me directly for stuff like this; and have no compunction about nagging on me if you think I've forgotten about it. The new implementation mostly looks awesome, but it's a good idea to make sure you have test coverage for all (major) code paths and features: Template:Greek/testcases#With_a_wikt_link. Xover (talk) 17:27, 2 June 2023 (UTC)

Monthly Challenge

I noticed that the June monthly challenge page was not previously set up by anyone. I tried to help as it didn't even exist when I saw it. I would help with setting up the rest of it but I am not super profitient in HTML and I am unsure of what the upcoming month's works are. Usually, I just look at another similar example but I wasn't sure how to translate the code from May's monthly challenge to June's monthly challenge. Regardless, could someone fix that up? Seperation (talk) 01:24, 1 June 2023 (UTC)

@Inductiveload: Ping, since I saw you were active today. I can take a look, but I don't know how it works (so it'll be a bit time-consuming) and I don't know when I'll have the time for it. Xover (talk) 11:46, 1 June 2023 (UTC)

Hi @Seperation, @Xover - I didn't see this message earlier, but I did do a quick import of the May data to June this morning: Module:Monthly Challenge/data/2023-06. There are instructions in the Edit notice when you go to edit the page, but tl;dr, delete the [2] section as "expired", increase [0] and [1] to [1] and [2] (as the works in those sections are now one month older) and then add the [0] section with any new works for this month. The stats bot should then pick up all the works on its next run (at most 2 hours, but I prodded it to go off a bit sooner) and update the relevant stats data. The MC page itself should update immediately: only the aggregate statistics need the bot, the list of which pages are in the MC and the individual progress bars just use Mediawiki. @MER-C has done a good job of coming though and filling in and tidying up after that - thank you!

In general, MC admin to start a month is described at Wikisource:Community collaboration/Monthly Challenge/Administration. Inductiveload—talk/contribs 21:46, 1 June 2023 (UTC)

Someone needs to populate the page with about another 12 works - I've been adding some stuff but I think we need some more diversity to cater to wider interests. MER-C (talk) 17:22, 2 June 2023 (UTC)