Wikisource:Scriptorium

SpBot archives all sections tagged with {{section resolved|1=~~~~}} after 3 days and sections whose oldest comment is older than 30 days.

Announcements

August 2026 Wikimedia Café meetups regarding Next 25

Hello! There will be two Wikimedia Café discussion opportunities in August. Both sessions will focus on the Next 25 initiative, including framing the initiative. Participants may attend either or both Café sessions.

1. 29 August 2026 15:00 UTC (timestamp converter), at a time friendly to the Americas, Africa, and Europe
2. 30 August 2026 03:00 UTC (timestamp converter), at a time friendly to Asia and the Pacific

Please see the Café page for more information, including agenda details and how to register!

To subscribe or unsubscribe for Café notices on your talk page please go here.

༄ᨒ𖠰 Pine (✉) 01:02, 17 August 2026 (UTC)

Bot approval requests

• See Wikisource:Bots for information about applying for a bot status
• See Wikisource:Bot requests if you require an existing bot to undertake a task

Repairs (and moves)

Designated for requests related to the repair of works (and scans of works) presented on Wikisource

See also Wikisource:Scan lab

UK Legislation

Please move the following indexes to match file names.

• Index:Online Safety Act 2023 (Category 1, Category 2A and Category 2B Threshold Conditions) Regulations 2025.pdf --> Index:The Online Safety Act 2023 (Category 1, Category 2A and Category 2B Threshold Conditions) Regulations 2025 (UKSI 2025-226 kp).pdf
• Index:Online Safety Act 2023.pdf --> Index:Online Safety Act 2023 (UKPGA 2023-50 kp).pdf
• Index:Public Order Act 2023.pdf --> Index:Public Order Act 2023 (UKPGA 2023-15 kp).pdf
• Index:Dissolution and Calling of Parliament Act 2022.pdf --> Index:Dissolution and Calling of Parliament Act 2022 (UKPGA 2022-11 qp).pdf
• Index:Ireland Act 1949I (UKPGA Geo6-12-13-14-41 qp).pdf --> Index:Ireland Act 1949 (UKPGA Geo6-12-13-14-41 qp).pdf

ToxicPea (talk) 23:12, 9 August 2026 (UTC)

Done --Jan Kameníček (talk) 08:37, 16 August 2026 (UTC)

Penny Cyclopedia

Could someone move all of the connected pages to the Penny Cyclopædia seeing as the latter is the actual title? See Encyclopædia Britannica and New International Encyclopædia for examples. Nighfidelity (talk) 03:11, 8 July 2026 (UTC)

Y Done. Yann (talk) 12:50, 8 August 2026 (UTC)

Index:Nietzsche the thinker.djvu

Could someone move this to Index:William Mackintire Salter - 'Nietzsche the Thinker', 1917.djvu to match commons? ToxicPea (talk) 02:09, 14 July 2026 (UTC)

Now we can only move 100 subpages at a time, but settings should be changed, so that we can move more (at least 500 at a time). Yann (talk) 12:54, 8 August 2026 (UTC)

Done --Jan Kameníček (talk) 09:04, 16 August 2026 (UTC)

Index:Customs and Excise Management Act 1979.pdf

Thanks to User:Koavf's effort, the missing pages of Index:Customs and Excise Management Act 1979.pdf has been repaired. Consequently, can somebody help to move all pages of that index after page 6 (i.e. from the current p. 10) by 2 pages? For example, this page should be moved to p. 37 of the index, corresponding to the correct page number of the file.廣九直通車 (talk) 05:49, 29 July 2026 (UTC)

@Yann: Notifying admins who might help with moving pages.廣九直通車 (talk) 14:33, 23 August 2026 (UTC)

With so many pages, it should be done with a script. Yann (talk) 15:50, 23 August 2026 (UTC)

Thank you. So should I create a new request at WS:BR?廣九直通車 (talk) 13:52, 27 August 2026 (UTC)

Electoral purity and economy

This should be moved to Electoral Purity and Economy, which the title page uses. Nighfidelity (talk) 16:17, 20 August 2026 (UTC)

Other discussions

The Statutes at Large (Ruffhead)

Can the unproofread pages in The Statutes at Large (Ruffhead) be deleted? They haven't been touched since 2019. It's clear no work has been done there — it's just OCR text, so when someone remakes that page they'll get all the content back. In the meantime, they're a huge nest of lint errors. They also have no headers, and letting the pages get remade means that the header template can be used, which would make the project easier. Eievie (talk) 02:12, 21 July 2026 (UTC)

I would support getting rid of the ones that have lint errors, (or ones that haven't been edited in the past 3 or so years) but I have done some work on a few of them that I didn't finish the whole page, but did individual statutes on those pages, and so I left it as not proofread. Erblanchard57 (talk) 18:40, 13 August 2026 (UTC)

I too have some pages on there that are partly proofread. Arcorann (talk) 02:55, 3 September 2026 (UTC)

Seeking feedback on Mormon Standard Works

There are a few strands of Mormonism/the Latter-Day Saints movement, with by far the largest being the Church of Jesus Christ of Latter-day Saints. All Mormon groups have a compilation of what they consider sacred scripture known as the "Standard Works", which include Bible (King James) and the Book of Mormon, but also have varying editions of The Doctrine and Covenants and usual a compilation called The Pearl of Great Price. I'm not really sure how to represent the Standard Works as a kind of collective work here: I don't think that {{disambiguation}} or {{versions}} really makes sense, so I'm leaning toward a Portal page that represents what works we have hosted or scans on c: as well as listing how different groups arrange their standard works. Does anyone have a perspective on what the best practice would be here? ―Justin (koavf)❤T☮C☺M☯ 20:50, 26 July 2026 (UTC)

Based on your explanation, I would concur with your suggestion of a Portal, but I am no expert in the issues. --EncycloPetey (talk) 21:06, 26 July 2026 (UTC)

Agreed, this would be Portal material. —Beleg Tâl (talk) 23:28, 26 July 2026 (UTC)

I've been working on them a bit, and just have separated them by the group that published them (as in The Doctrine and Covenants.

Based on my understanding, pretty much all groups today accept the Book of Mormon but vary on whether or not it was divinely inspired/actually translated. The various groups have differing Doctrine and Covenants, and their various publications have different sections from their prophets/presidents following Joseph Smith. Only the Utah-based Church of Jesus Christ of Latter-day Saints and any groups that split off from them, after arriving in Utah, accept The Pearl of Great Price as a standard work, though some portions of the material in it is accepted by the other various groups. And then they all accept the Bible, and I think that page is fine as is. The Church of Jesus Christ of Latter-day Saints just recently acknowledged the faithfulness of other translations to the original manuscripts, and expanded their list of approved translations (in Dec. 2025).

If the decision to do a portal is is what is accepted, I would just suggest having portals for the individual churches, and have their own accepted standard works and their various editions listed on their own portals. I do think a versions page works well though, if they are split by group like I've done on The Doctrine and Covenants. Because otherwise, we still have a ton of different editions from the various groups and I think it would get messy if we had to have individual pages such as The Doctrine and Covenants (Latter-day Saint) or The Doctrine and Covenants (Community of Christ), or The Book of Mormon (Latter-day Saint), etc. So I'd just have one Doctrine and Covenants page, one Book of Mormon page, etc. with the separation based on groups listed there. Especially since they would all accept the pre-1844 publications, and those would have to have their own page as well (or be duplicated across the various group pages for each book).

Hopefully that makes sense. Erblanchard57 (talk) 17:14, 13 August 2026 (UTC)

That does make sense, unfortunately, so it's hard to know what to do here. Is it helpful to have portals for twenty Mormon/LDS groups individually? Or to try to cram all of the info into one large portal that is about Standard Works? Both? ―Justin (koavf)❤T☮C☺M☯ 18:05, 13 August 2026 (UTC)

Based on what I've seen, I don't think that a lot of the various individual groups publish their own editions; most of the smaller groups just use the Latter-day Saint editions. So I don't think it would devolve into 20 or more different pages, if we just do it by the publishing group on the individual pages of the various Standard Works I don't think it will get much larger than the current Doctrine and Covenants page. On a related topic, I've talked about the whole giant amounts of groups in the Latter Day Saint movement a little bit with User:Eievie at Category talk:The Church of Jesus Christ of Latter-day Saints, and I feel like we've come generally to a consensus there; I'm open to thoughts about that too. Erblanchard57 (talk) 18:30, 13 August 2026 (UTC)

D&C is also famous for being edited a lot over time, so the naming needs to account for edition/year too, not just sect. Eievie (talk) 00:03, 14 August 2026 (UTC)

Migration to Parsoid

Read this in another language

Hello everyone! I am glad to inform you that as the next step in the Parser Unification project, Parsoid will soon be turned on as the default article renderer on your wiki. We are gradually increasing the number of wikis using Parsoid, with the intention of making it the default wikitext parser for MediaWiki's next long-term support release. This will make our wikis more reliable and consistent for editors, readers, and tools to use, as well as making the development of future wikitext features easier.

If this disrupts your workflow, don’t worry! You can still opt out through a user preference or turn Parsoid off on the current page using the Tools submenu, as described in the Extension:ParserMigration documentation.

There is more information about our roll-out strategy available, including the testing done before we turn on Parsoid for a new wiki.

To report bugs and issues, please look at our known issues documentation and if you found a new bug please create a phab ticket and tag the Content Transform Team in Phabricator.

Content Transform Team 16:31, 3 August 2026 (UTC)

@MSantos (WMF): could you please tell us whenever you have a date? We've had bad experience with being warned of a deployment only one week before the fact. — Alien  3
3 3 08:11, 13 August 2026 (UTC)

Page:An Index of Prohibited Books (1840).djvu/46

Hi, The words on the right were placed there for typographical reasons and no longer need to be there. Shouldn't we render the lignes properly? Yann (talk) 13:19, 6 August 2026 (UTC)

Yes, unless you have a specific reason for replicating the specific layout, they should just be put onto the correct line, like on this page from the same work -- Page:An Index of Prohibited Books (1840).djvu/64. Qq1122qq (which looking at the edit history I see you were responsible for correcting!) (talk) 13:33, 6 August 2026 (UTC)

No, not on this page. But OK, done. Thanks, Yann (talk) 13:49, 6 August 2026 (UTC)

 This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. Yann (talk) 10:13, 9 August 2026 (UTC)

Request to add Edgar A. Guest poem "Little Things" (1926)

Hello, I would like to request the addition of a public-domain poem by Edgar A. Guest that does not appear to be available on Wikisource. Poem: Little Things Author: Edgar A. Guest Source: The Light of Faith. Chicago: Reilly & Lee Co., 1926, page 51. I own a copy of the 1926 book and can provide photographs of: the front cover, the table of contents showing the poem and page number, and the poem itself with the printed page number visible. If needed, I'm happy to upload those images to help verify the source. Text of the poem:

Little Things
Edgar A. Guest

Lord, make me strong enough to bear
My little round of anxious care.
The day returns. For this I pray:
Sufficient wisdom for the day.
Although I may not walk with kings,
Let me be big in little things.

Grace me with modesty and teach
me kindliness of thought and speech;
Let me not hasty be to chide
the children walking at my side,
And spoil with imperfections slight
The record which the day shall write.

Lord, make me big enough I pray
to triumph in a lesser way.
When petty disappointments rise,
Let me be patient, gentle, wise.
Missing the joy which greatness brings
Let me not fail in little things.

Lord, I would work and neighbor here,
Too big to hate, too wise to sneer.
I would be helpful, cheerful, kind,
Gentle of speech and broad of mind.
And though not far my circle swings,
Let me be great in little things.

Thank you for considering adding this work to Wikisource so it will be searchable and preserved for future readers. If additional information or photographs are needed, I'd be happy to provide them. Kind regards, Jenelle Chaplin Jenelle Chaplin (talk) 01:37, 7 August 2026 (UTC)

In general, requests to add a work should be made at Wikisource:Requested texts, and only if the work in question doesn't have an easily-accessible source file.

Since you own a copy of the book and can provide photographs, I would suggest making a PDF of the entire book (photographs can qualify as scans). Then you can add the text yourself. Edderiofer (talk) 02:04, 7 August 2026 (UTC)

There are several copies of that book on Internet Archive. So the best thing is to import one of those onto Commons, and then we can start working on the transcription here. -- Beardo (talk) 02:34, 7 August 2026 (UTC)

Ah, I must not have checked very well. Yeah, let's do that then. Edderiofer (talk) 02:43, 7 August 2026 (UTC)

It's at File:The Light of Faith (1926).pdf. Nighfidelity (talk) 19:34, 7 August 2026 (UTC)

That edition combines The Light of Faith and a separate book Harbor Lights of Home which has a copyright of 1928 - so this edition must be 1928 or later. -- Beardo (talk) 02:56, 17 August 2026 (UTC)

Work with no scan images

What is our current position on works when no scan images are available, but the text is?

The pamphlet "Recollections of New Street, Birmingham, in the Year 1817" was scanned and published by the British Library. The OCR file is still available via their API, but the PDF is no longer online, no doubt as a result of their recent hack problems.

I have taken the former and marked it up, for now, at User:Pigsonthewing/New Street 1817, and would like to move it to mainspace. No other online source appears to offer it in human-readable form. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:48, 8 August 2026 (UTC)

Without a scan to back it, the text would probably be tagged with {{no source}} and/or {{fidelity}} at the least. Nighfidelity (talk) 21:15, 8 August 2026 (UTC)

Neither would be true; but {{Second-hand}} might apply; I could live with that. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:22, 8 August 2026 (UTC)

Now published, as Recollections of New Street, Birmingham, in the Year 1817. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:53, 9 August 2026 (UTC)

I've replaced {{second-hand}} with {{no scan}}, since it's based on the OCR at least. If it was second-hand, it would not be allowed per WS:WWI#Second-hand transcriptions. —Beleg Tâl (talk) 02:21, 10 August 2026 (UTC)

The British Library does have a record of the text at least. Nighfidelity (talk) 21:19, 8 August 2026 (UTC)

Tech News: 2026-33

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• A new ChartWizard is now available on Wikimedia Commons for users interested in creating charts from their own data. The wizard makes the Chart extension more beginner-friendly by allowing editors to create charts, such as bar and pie charts, without needing to use JSON. Users can still switch to the JSON editor if they prefer. Feedback on the new tool is welcome on the wish talk page.
• View all 19 community-submitted tasks that were resolved last week. For example, an issue where the Wikipedia iOS app’s Picture of the Day widget displayed the same image every day instead of updating daily, has now been fixed. [1]

Updates for technical contributors

• Math formula SVG images will soon be generated in the browser instead of on the server. MathML continues to be generated on the server and renders in the browser without JavaScript. Wikibooks will see this change on 12 August, Wikisource on 19 August and Wikipedia from 20-27 August. You can try this by selecting "MathML with SVG image (client side MathJax rendering)" in your preferences. This change is part of deprecating RESTBase and deprecating Mathoid. [2]
• Category pages will soon support sorting entries by the time they are added to a category. This will make it easier to find recently or long-standing categorized pages. It will also improve workflows for maintenance categories such as deletion backlogs and other time-based review tasks. You can use cldsort=timestamp URL argument in category view to sort the entries. [3]
• Gadgets and user scripts on Wikimedia wikis may now use ES2018 features and ES2019 features in JavaScript code. Previously, the platform only allowed up to ES2017. MediaWiki validates the source code to protect functionality from syntax errors and to ensure scripts are valid in all supported browsers. [4]
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 20:45, 10 August 2026 (UTC)

Wikimedian in Residence at The Gazette (UK)

As of yesterday, I am Wikimedian in Residence at The Gazette (encompassing The London Gazette, The Belfast Gazette and The Edinburgh Gazette).

Please see w:Wikipedia:GLAM/The Gazette for details, and let me know if you have any suggestions or requests. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:14, 12 August 2026 (UTC)

That's great. My question is how you brokered this relationship. I think that interfacing with long-term periodicals/newspapers here in the States makes a lot of sense and I've never been able to get anyone to seem to care. ―Justin (koavf)❤T☮C☺M☯ 19:18, 12 August 2026 (UTC)

The project was advertised and I tendered. Wikimedia UK did the negotiation to set it up. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:11, 12 August 2026 (UTC)

Thanks for the info. Are all issues digitized and available online? That would be the main interest for Commons and Wikisource. Yann (talk) 19:30, 12 August 2026 (UTC)

They are, but I do not plan a bulk upload. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:10, 12 August 2026 (UTC)

Spam

This edit is spam, so keep an eye on the user @Activelife1234. Eievie (talk) 06:16, 13 August 2026 (UTC)

Thanks for reporting. User blocked. Yann (talk) 06:27, 13 August 2026 (UTC)

| notes =

Is the notes section of the template for a work meant to point out errors in dates or errors in names in the original text, and other notations like that? Or is it meant for something completely different? RAN (talk) 21:58, 14 August 2026 (UTC)

The documentation for the Header template states that the Notes field is "notes to explain the work, to add context, or to impart concise information that adds value to the reader; for example, use of {{listen}}". In other words, bibliographic notes. The types of notes you mention belong on the Talk: page, if they are needed at all. Beeswaxcandle (talk) 22:56, 14 August 2026 (UTC)

• Pointing out errors in the original text, sure sounds like "context … concise information that adds value to the reader". That is exactly what I see when I see a reprint of an historical text. Can you explains why/how it does not provide "context … concise information that adds value to the reader"? I don't see the word "bibliographic" used in the definition. Why such an extremely narrow definition of what "context" is? And why would you want it on the talk page, where people leave non-contextual comments and anecdotes. I am not sure why adding "concise information that adds value to the reader" such as corrections to dates and names, somehow excludes using {{listen}} or even why {{listen}} is considered context. --RAN (talk) 01:09, 15 August 2026 (UTC)

  The documentation I quoted describes the intended use of the notes field. The examples and wording seem to me to be directed toward explanatory information about the work itself, its publication, provenance, and related matters. That's why I referred to them as bibliographic notes. I wasn't suggesting that "context" is limited to bibliographic information in the abstract, only that the Notes field appears to be intended for that sort of material. Corrections to mistakes in the original text are certainly information that may be useful to readers. The question is not whether they add value, but whether they are the sort of explanatory notes contemplated by the Header documentation, or whether they are better suited to the talk page.

  In respect of your comment about people leaving non-contextual comments and anecdotes on a Talk: page, that is not the purpose of our Talk: pages and such comments should be deleted. If that would leave the Talk page blank, then tag it for speedy deletion with {{sdelete}}. Talk pages are for recording more extended bibliographical information (via the {{Textinfo}} template)—including source for non-scanned texts—and for discussions about how to improve texts.

  As for {{listen}}, I agree that it is not "context" in the ordinary sense of the word. To me, that example suggests that the Notes field is intended for ancillary information about the work and its presentation, rather than for textual criticism, emendations, or corrections. Beeswaxcandle (talk) 22:32, 15 August 2026 (UTC)

  Re "errors" in the text, it helps to be clear what you mean. E.g. are we talking about the text attributing authorship mistakenly, or including a forgery / misunderstanding of current events (e.g. responding to a report about another country that turned out to be false)? Those are more bibliographical. While errors in particular parts of the text are better handled by WS:Annotations, e.g. getting specific facts wrong, struggling with a foreign language / names / locations, scientific inaccuracies etc. MarkLSteadman (talk) 22:55, 15 August 2026 (UTC)

• Wikisource:Annotations covers changes made within the text like a wikilink or using the sic template within the text for typos. This is about adding a note in the "| notes = " area of the header to provide "context … concise information that adds value to the reader". Beeswaxcandle believes these notes belong on the talk page mixed in with other editor's comments or questions. I believe notes belong in the notes section of the header. If it comes down to personal taste, rather than a strict rule, we should side with the person doing the scanning and transcription and research. For instance, if an obituary states that a person was 75 when they died, but a birth certificate or a well researched biography shows that they were still 74, and would not have been 75 until their next birthday, that should be a note in the notes section because it provides "concise information that adds value to the reader". Not taking note of it, allows the error to be propagated. Hiding it on the talk page does not add value to the reader. No reader will see it there, only another editor specifically looking for it. --RAN (talk) 22:40, 29 August 2026 (UTC)

Failed to Open SeaDragon (another round)

I am getting this error when I try to create any page from Index:Anaximander and the Origins of Greek Cosmology.pdf, even though the Index was created two months ago. --EncycloPetey (talk) 00:21, 15 August 2026 (UTC)

 Comment Note that I can see the File just fine on Commons, and can view pages there, but the File does not show up on the local "File" page, nor does any image appear on the Index page. --EncycloPetey (talk) 13:47, 15 August 2026 (UTC)

@EncycloPetey: Solved. I've purged the cache of the file in Wikisource (adding ?action=purge to the URL). • M-le-mot-dit (talk) 16:23, 15 August 2026 (UTC)

Thanks. I had tried that and several other Purge methods both here and at Commons, but to no effect. --EncycloPetey (talk) 16:25, 15 August 2026 (UTC)

{{Gutenberg}}

Should this be deprecated seeing as linking to Project Gutenberg (despite what Help:Project Gutenberg says) has been discouraged for a while? Nighfidelity (talk) 21:07, 15 August 2026 (UTC)

I think we should definitely be consistent, but I also think that we should link to that site, particularly for works that we don't have here--that provides clear value to our readers who can access a work that is in the public domain and isn't here yet. ―Justin (koavf)❤T☮C☺M☯ 21:10, 15 August 2026 (UTC)

I agree with Justin. Yann (talk) 21:22, 15 August 2026 (UTC)

Strongly disagree with linking to PG for works that we don't host yet. We have evolved a long way from the state in 2006 when this template was set up—the major change being the introduction of ProofreadPage. The current uses of the template are historical and are gradually being replaced with scans, we don't need to add more to that backlog. It's also not our mission to provide a single bibliographical source for all available PD texts that are somewhere on the web. Even if new uses of this template were only on Portal and Author pages, it would derogate from the real value that we provide through our processes of making texts available here. So, yes, we should deprecate the template and mark the Help page as for historical interest only. Beeswaxcandle (talk) 21:50, 15 August 2026 (UTC)

Disagree with linking to PG works. If someone wants to curate links to Gutenberg works the correct place to do that is Wikidata/Wikipedia, not WS. In addition, it is awkward with our flow: When should the links be removed? When the Index is created? When it is validated? But even then it might be from a different edition, so does it need to be that edition? Unlike scan link --> Index link which has a natural and intuitive transition. And lastly, why not other sites? If you can link to [5] what about [6]. Having Project Gutenberg as a sui generis place is problematic as well as getting into quality curation of sites. 22:25, 15 August 2026 (UTC) MarkLSteadman (talk) 22:25, 15 August 2026 (UTC)

Also disagree to linking to PG works. Our role is not to maintain an index of transcriptions elsewhere. So yes to deprecation. — Alien  3
3 3 11:33, 16 August 2026 (UTC)

I do not support quick deprecation. Yet phasing out the links may be considered case by case, as PG does not even care about non-American copyright laws.--TunnelESON (talk) 04:31, 2 September 2026 (UTC)

Deprecation: "To declare something obsolescent; to recommend against a function, technique, command, etc. that still works but has been replaced." When saying "I do not support quick deprecation." Are you saying you don't support adding a please don't use message to the template? That adding new links is still recommended/encouraged? That you don't support doing so now but maybe we can revisit in 5 years? The actual process of deprecation, making the announcement is inherently quick. MarkLSteadman (talk) 12:42, 2 September 2026 (UTC)

Index:Young India.pdf

Hi, The scan was defective. I fixed it, but there are 2 pages only to validate. Thanks, Yann (talk) 16:42, 16 August 2026 (UTC)

Done. Thanks to everyone else who did much more work. ―Justin (koavf)❤T☮C☺M☯ 20:22, 16 August 2026 (UTC)

Breadcrumbs in the title

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

• 
  Current breadcrumbs
• 
  Proposed breadcrumbs

What do you think? Sophivorus (talk) 16:03, 17 August 2026 (UTC)

I support this, because it makes the links more visible. prospectprospekt (talk) 19:37, 21 August 2026 (UTC)

The current system is done automatically by the MediaWiki software. To change it would require backend work that I'm not sure is worth the effort. Arcorann (talk) 12:18, 3 September 2026 (UTC)

Shakespeare - First Folio facsimile (1910)

Is there a reason this isn't called Mr. William Shakespeare's Comedies, Histories, and Tragedies? Nighfidelity (talk) 20:11, 17 August 2026 (UTC)

Tech News: 2026-34

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Worklist feature for the Event Registration tool is now live on all Wikimedia wikis. With Worklist, event organizers can add the articles their event will focus on directly to the event page. The Worklist also powers Event Pathways which notifies other editors of the upcoming or ongoing event when they edit an article featured in the event's Worklist. This is the minimum viable version (MVP), and feedback is welcome. Organizers are encouraged to try the feature. A hands-on Worklist Setup Workshop will take place on 18 August at 16:00 UTC and 19 August at 11:00 UTC.

Updates for editors

• Special:ShortPages displays short pages by their size, but in many cases it gets filled with disambiguations and soft redirects, making it harder to find the short articles themselves. Starting this weekend, you will be able to choose not to include an article in the special page by adding the magic word __EXPECTSHORTPAGE__. [7]
• One new wiki has been created: a Wikipedia in Bole (w:bol:) [8]
• Starting the week of August 17, the page toolbar will wrap onto two lines when there is not enough horizontal space for all the buttons. This is a fully merged patch from the Reader Experience team which aims to reduce crowding in the Vector 2022 toolbar, that may occur on some language Wikipedias at certain screen widths.
• View all 16 community-submitted tasks that were resolved last week. For example, uploading large files to Wikimedia Commons has become more stable and less prone to failure following some fixes related to the “Could not acquire lock” upload error. [9]

Updates for technical contributors

• Debian Bullseye will reach the end of its Long Term Support on 31 August 2026. Some Cloud VPS projects still have instances running Debian Bullseye. Maintainers of those projects are encouraged to migrate to Debian Bookworm or Debian Trixie. A migration guide is available to help with the process, and users may also want to consider whether their workload is better suited to Toolforge. If you need help or cannot complete the migration by 31 August, please contact the Cloud VPS admins as soon as possible. Read more.
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 21:03, 17 August 2026 (UTC)

Display none template

Is the text in {{Display none}} read by screen-reading software? If not, do we have a template where that is the case?

My use case is for tables and column-headings which are empty in originals, but need to be described for users with a visual impairment. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:05, 20 August 2026 (UTC)

@Andy: wihth Edge, the text in {{Display none}} and {{Hidden text}} is not read aloud, but it is the case when using {{Transparent}}. • M-le-mot-dit (talk) 09:37, 20 August 2026 (UTC)

Cuthberts Collingwood

We have:

• Author:Cuthbert Collingwood
• Author:Cuthbert Collingwood, 1st Baron Collingwood

of which I just created the latter. Is it correctly titled, and how do we link to it from the former? Or should there be a disambiguation page? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:24, 20 August 2026 (UTC)

Per Help:Author pages#Page name - "The name of the page should not include titles." So yours should be Cuthbert Collingwood (1748-1810) and the other needs to be moved, with a disambiguation page created. -- Beardo (talk) 16:50, 20 August 2026 (UTC)

Thank you. All done I'd be grateful if someone could check. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:48, 20 August 2026 (UTC)

Am I on the right track? Albert Einstein letters.

Hello all. I'm still new here, but I'd like to transclude the letters that Einstein sent to Brunauer (see commons). I've now made an attempt at one handwritten letter: Albert Einstein to Stephen Brunauer - August 22, 1943 and wanted to ask if someone could have a look at both the transclusion and index and generally give me some advice or impression on how I've done. I have read through the guides and templates, but I'm sure I still missed some things. Also I know that the image files aren't great yet, but my skills are lacking in that area.

I thought about creating and adding all the letters in Einstein–Brunauer Letters, similarly the way you'd have an overview of volumes from a magazine. Although I haven't seen this done for letters here before, so I'm not sure if that's a good idea. Thanks in advance :) Neon700 (talk) 16:58, 20 August 2026 (UTC)

Index:Pilkington of Uganda (IA pilkingtonuganda00harf).pdf

Could someone please mark all the non-patrolled pages of this work as not proofread. Most of the pages have been marked as validated but they very clearly aren't. ToxicPea (talk) 07:32, 22 August 2026 (UTC)

<math> spanning pages

On these pages (Spherical Trigonometry (1914), p. 65 and 66) I'm having issues making a <math> block span the page break. Help:Fractions and functions doesn't say anything about such sitations. Has anyone done it successfully anywhere else? Eievie (talk) 19:10, 22 August 2026 (UTC)

@Eievie Unless a template has "/s" and "/e" variants, it won't by default work across pages (even if you close the template in the footer and open it in the header).

In this situation, I could see two non-ideal options. I have implemented one, which is just using noinclude/includeonly, and so required copying (validated) text from the second page to the former. The other option would be not using align, and, e.g. use a table for the alignment instead. This would have avoided needing to copy text, but might have introduced slight differences in styles between earlier (aligned) equations. If someone has a better approach, feel free to revert my edits. Regards, TeysaKarlov (talk) 21:00, 22 August 2026 (UTC)

@TeysaKarlov To clarify, this isn't a template, it's a tag. Does that make a difference? Eievie (talk) 21:09, 22 August 2026 (UTC)

@Eievie When I said about "/s" and "/e" variants, it was more just as a general heads up. But yes, the difference between template/tag does make a difference, and some tags should work as intended if placed in headers/footers (though I am not an expert). However, you were using both a tag (math) and part of the latex math interpreter (begin/end align). I don't think the latex interpreter part knows much, if anything, about how proofread page (or Wikisource) works, so I think it would have been a miracle if the align carried across pages. Regards, TeysaKarlov (talk) 21:25, 22 August 2026 (UTC)

@Gunjounoame Just pinging you to loop you in on this conversation. Eievie (talk) 21:16, 22 August 2026 (UTC)

Tech News: 2026-35

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• The Special:CreateAccount page has been simplified as part of ongoing work to modernize the account creation experience. The panel showing project statistics no longer appears next to the form on desktop and mobile web. Multiple account creation experiments show that a simpler form helps newcomers complete registration. [10]
• In order to improve page performance, images now load when they are viewed. This means images lower down an article will not load if a reader never scrolls to that part of the page, which may affect some image-related metrics. [11]

• View all 42 community-submitted tasks that were resolved last week. For example, an issue where image thumbnails in Abstract Wikipedia could fail to display after the corresponding file was moved on Wikimedia Commons, has now been fixed. Thumbnails will now update correctly when files are moved. [12]

Updates for technical contributors

• User Info card is a feature that helps patrollers see information about user accounts. So far, it has been available only in places such as page history, logs and recent changes. Now, it's possible to place it in the page content as well, using the {{#uic:}} parser function. It can be particularly useful in templates like {{Userlinks}} (or their specialized variants), as it will make it easier to see the context about a user on various noticeboard pages. The card will be displayed only to users who have it enabled in their preferences. [13]
• Due to user security and privacy risks, we have disabled access to Special:MyPage URLs when specifically using action=raw. If you are impacted by this, consider whether you can use an alternative approach. Special:MyPage URLs can still be accessed and used without action=raw. Specified user page URLs (e.g. User:Myusername) can still be used with action=raw. [14]
• Due to an update, the thumbnailing software has been improved. This includes upgrading librsvg to 2.60 and ImageMagick to 7, as well as resolving a number of long-standing thumbnailing bugs like rendering errors. [15]

• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 20:45, 24 August 2026 (UTC)

Index:Works of Gustave Flaubert, vol. 1, Madame Bovary.pdf

H, One page left to validate. Thanks for your help, Yann (talk) 14:56, 25 August 2026 (UTC)

 This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. Yann (talk) 18:05, 25 August 2026 (UTC)

Scrambles amongst the Alps

Hi, I am validating this work. Shouldn't the chapters (in capitals) in the table of content link to chapters? Yann (talk) 16:53, 26 August 2026 (UTC)

The links right after already link to the top of the chapter pages, so I don't think it'd be necessary. — Alien  3
3 3 18:20, 26 August 2026 (UTC)

OK. Thanks for answering. Yann (talk) 18:23, 26 August 2026 (UTC)

@Yann: I agree that they are not done correctly. The link to "Chapter 10" actually links to Scrambles_amongst_the_Alps/Chapter_10#pageindex_266. It should not be linking to page indices, but simply to the actual chapter in Mainspace. The Table of Contents links require cleanup. --EncycloPetey (talk) 23:34, 30 August 2026 (UTC)

@EncycloPetey: 266 is the first page of that chapter, so it doesn't really change anything. — Alien  3
3 3 08:03, 31 August 2026 (UTC)

No, the first page is page 222. Scan page 266 is the page of the scan which is page 222. This will confuse people, and it also means that someone arriving at the chapter from the link will not see the page header. So it does change several things. --EncycloPetey (talk) 13:04, 31 August 2026 (UTC)

Scan's page not displayed

The original scan's page is not displayed at Page:A pickle for the knowing ones (IA pickleforknowing00dextrich).pdf/36. What might be the reason? -- Jan Kameníček (talk) 15:18, 29 August 2026 (UTC)

• The image is dynamically resized based on the text; if there is a string of text too long (or with table formatting, the longest words in each column are too long), then the image will be smaller. In this case, the long list of commas pushes off of the screen, thus taking up all of the room where the image would have been. TE(æ)A,ea. (talk) 15:28, 29 August 2026 (UTC)

Index:Gandhi - The Story of My Experiments With Truth, vol. 1.pdf

Hi, Chapter 13 of Part 2 is titled What It Is to be a Coolie. Shouldn't it be What It Is to Be a Coolie with a capital B? Yann (talk) 09:58, 31 August 2026 (UTC)

Or it could be "What It is to be a Coolie" or "What it is to be a Coolie". The style has changed over the years, and even if the particular choice here is weird, I wouldn't bother with a {{SIC}} or anything. Maybe a {{sic}} if it really bothers you.--Prosfilaes (talk) 11:11, 1 September 2026 (UTC)

Bradshaw's Monthly Railway and Steam Navigation Guide

I have been having an argument with User:Pigsonthewing regarding this page, and we are at an impasse, so I am bringing it to the community at large for discussion.

• I told Pigsonthewing that if this page represents the work Bradshaw's Guide itself, then it MUST have a license tag (such as {{PD-US-periodical}}); whereas if it is a page "about" Bradshaw's Guide then it must be moved to Portal namespace where it belongs.
• Pigsonthewing disagreed with what I told them, and claims that the page does NOT need a license tag, despite being in Mainspace.

What is the community's consensus regarding this page? Does it require a license tag due to being a work in Mainspace? Does it need to be moved to Portal space due to the page not being a work? Or should we make an exemption to our standard practices and leave it as it is? —Beleg Tâl (talk) 15:08, 31 August 2026 (UTC)

For the record, it is my understanding that this page CANNOT be allowed to remain in mainspace with no license tag, and though we can make exceptions when supported by community consensus, I strongly oppose making any such exception. —Beleg Tâl (talk) 15:11, 31 August 2026 (UTC)

Prior discussion is at User talk:Pigsonthewing#Bradshaw's Monthly Railway and Steam Navigation Guide.

I have already invited User:Beleg Tâl to nominate the page for deletion, as their tag threatens to do; they have not done so. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:13, 31 August 2026 (UTC)

You will note that deleting the page is not among the options that I suggested for resolving this issue. (This is tangential to the current discussion, but I have proposed rewording the text of {{no license}} to reflect the fact that deletion is generally not the appropriate action to be taken, but the consensus was to keep the current wording) —Beleg Tâl (talk) 15:16, 31 August 2026 (UTC)

The tag you have repeatedly added to the page says "Pages with no license information may be nominated for deletion." Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:26, 31 August 2026 (UTC)

That is correct, the maintenance tag {{no license}}, which is used on pages with no license tag, mentions that such pages may be nominated for deletion. This page has no license tag, and as such may be nominated for deletion—but at no point did I ever say that I intended to do so, nor did I say that this would be the correct action. —Beleg Tâl (talk) 15:31, 31 August 2026 (UTC)

At the conversation linked above, Pigs/Andy notes correctly that many pages in the main namespace do not have a license tag, but all of those are some kind of version, translation, or disambiguation page (e.g. Bible). I don't know of any works in the main namespace that lack a copyright tag. If I'm reading this correctly, the work in question is a periodical, like The New Yorker or Harper's Magazine and those have license tags. Why wouldn't this periodical? I just don't see why this page is better off without a license tag. ―Justin (koavf)❤T☮C☺M☯ 15:27, 31 August 2026 (UTC)

The page in question is not "a work". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:30, 31 August 2026 (UTC)

Okay, but I am reading this correctly that it's a monthly magazine, similar to The New Yorker, correct? I just want to make sure that I know what it is that I'm seeing. ―Justin (koavf)❤T☮C☺M☯ 17:13, 31 August 2026 (UTC)

"Bradshaw's Monthly Railway and Steam Navigation Guide" was a monthly publication; whether it was a magazine or a book with many editions is up for debate.

The page in question is a list of such editions, not a transcluded work, and is the original work of Wikisource contributors, never having previously been published; so—like this discussion page—carries an "available under the Creative Commons Attribution-ShareAlike License..." statement which is entirely correct and adequate for the content of the page.

There are no grounds for nominating the page for deletion (much less deleting it) as the template it is still tagged with claims; and no grounds for moving it to Portal space, as Beleg Tâl has suggested doing. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:30, 31 August 2026 (UTC)

I further note that the template currently on the page is causing the page to be in Category:Works with no license template. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:34, 31 August 2026 (UTC)

I can understand both views.
A periodical is not a work in itself, as in it's not a published unit of text. Licenses in mainspace often correspond to a published unit of text. Different issues of a periodical could theoretically have different licenses.
(Goes without saying, it makes more sense to have individual issues be a subpage of a parent mainspace page, than to not have such a parent.)
However, when possible, putting a license on the parent page, as a global indicator of the copyright status of the contents hosted under that root page, is useful and helps organise content, and should generally be done.
(Also, maybe stop arguing? You've been at it for a while and clearly you're not going to convince each other of anything anytime soon.) — Alien  3
3 3 15:28, 31 August 2026 (UTC)

I've given up arguing, that's why I'm leaving it in the hands of the community. —Beleg Tâl (talk) 15:35, 31 August 2026 (UTC)

My personal opinion. For serial works, they should be tagged with the most permissive license like we tag authors, justifying the presence of the series at all. No valid parts of the series, no hosting. I would be in favor of adding a series flag to our license as a warning that individual volumes in the series may have their own licenses and that it is required to tag any volume specifically that is more restrictive. MarkLSteadman (talk) 16:31, 31 August 2026 (UTC)

Regarding a warning that individual volumes in the series may have their own licenses, &c.—this is exactly the function of {{PD-US-periodical}}, which is the tag I indicated should be placed on the page under discussion. —Beleg Tâl (talk) 23:03, 31 August 2026 (UTC)

It's not just for periodicals, a multi-volume history, biography, collection of papers, translation etc. may have different authors / publication dates. MarkLSteadman (talk) 02:01, 1 September 2026 (UTC)

Separately, that text is useless, it doesn't say anything informative about the status. Even though it starts with "PD-US" it doesn't make any statement that any of the content tagged is actually public domain in the US. It perfectly describes a periodical published from 2000 to 2003 that is likely copyrighted possibly into the next century. Separately being "PD-US" it is unclear whether it can be applied to a freely licensed periodical, like say an open-access journal. MarkLSteadman (talk) 13:45, 1 September 2026 (UTC)

Yeah, the name of the template makes no sense, but all it does is provide a license tag for works where individual parts of the work may have their own licenses —Beleg Âlt ^BT (talk) 20:18, 1 September 2026 (UTC)

It is most definitely a periodical, and should have a license tag for that, similar to the way that an author page has a license tag.--Prosfilaes (talk) 11:34, 1 September 2026 (UTC)

OCR tool not working

Tracked in PhabricatorTask T436551

The OCR tool is not working for me. It returns the following error.

Error from the OCR tool: Image URL must be for one of the following domain names: upload_wikimedia.org and uploadwikimedia-betawmflabs.org Chrisguise (talk) 18:55, 31 August 2026 (UTC)

I'm getting the same. I've had that (or something similar before) but it cleared shortly after. -- Beardo (talk) 19:10, 31 August 2026 (UTC)

Same for everyone everywhere it would seem; it has been flagged and will apparently be fixed in a few hrs: phab:T436551 Psephos (talk) 20:08, 31 August 2026 (UTC)

Tech News: 2026-36

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• A new format for the Community Wishlist is open for feedback. You can read the proposed ideas on Meta. This new process plans to improve how wishes are triaged, voted on, and prioritized in a way that is transparent and balanced across project families and language editions. This consultation is open for two weeks.

Updates for editors

• The latest release of the Wikipedia Android app includes updates to the Saved feature, bringing the app’s saving experience closer to iOS and Web. The update redesigns the Saved tab with an “All articles” view, removes the default “Saved” reading list, renames reading lists to “Collections,” and modernizes the article-saving experience. [16]
• The Reading Lists feature was enabled for all logged-in users on Bengali, Chinese, Czech and Vietnamese Wikipedias on August 25, after several months as a beta feature. Reading Lists will be available to all logged-in users on Arabic, French and Indonesian Wikipedias on September 1, followed by English Wikipedia on September 14, and all other Wikipedia wikis on September 28.
• At the end of the month, some logged-out readers on Bengali, Czech, Persian, English, and Polish Wikipedias using the Minerva skin on mobile will see an updated navigation bar in an A/B test. The test will compare the current navigation bar with a new version designed to make it easier to find information more quickly. The goal is to determine whether these changes encourage readers to return more often. This experiment will not change the experience for logged-in readers and/or editors.
• Editors who maintain redirects, templates, and categories used on redirect pages now have improved ways for finding and curating redirects. Previously, redirects pages could not be searched. Two new search keywords, onlyredirects: and withredirects:, now allow redirects to be searched directly and can be combined with existing keywords such as incategory:, intitle:, and insource:. [17]
• The ISBN lookup tools for generating citations were recently not working because of external service problems. Developers are working on solutions. [18]
• View all 30 community-submitted tasks that were resolved last week. For example, an issue where searching for pages by category using deepcat could return no results or unrelated results has now been fixed. [19]

Updates for technical contributors

• The domain of URLs for thumbnails is changing from upload.wikimedia.org to thumb.wikimedia.org. The old URLs will continue to work for the foreseeable future but MediaWiki will advertise the new domain instead. URLs to other types of media such as original files, videos and transcodes will still be served from upload.wikimedia.org. [20]
• The Wikimedia Math API is now deprecated. These endpoints will be fully sunset by the end of September 2026. Developers who call these endpoints should transition to alternative math rendering solutions, such as the native MathML or MathJax. Third-party MediaWiki installations that utilize the Math extension for formula rendering are required to upgrade to v1.43+ to avoid disruption of service.

• Detailed code updates later this week: MediaWiki

In depth

• Read more about TextMatch in a Diff post titled, Custom edit suggestions for every wiki: How communities are shaping Suggestion Mode with TextMatch.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 20:53, 31 August 2026 (UTC)

DjVu failing for me for the first time

I began proofreading Index:Anaximander and the Origins of Greek Cosmology (1960).djvu for this month's MC, then suddenly lost the ability to see pages from the scan. Purging / refreshing has not helped. This is the first time this has happened for a DjVu, and (as I say) it was working until a few minutes ago. --EncycloPetey (talk) 00:22, 1 September 2026 (UTC)

• For me, the pages don’t load on first glance, but will load if the page is refreshed. This has also happened with other DjVu files on which I have worked relatively recently, but it is very inconsistent. TE(æ)A,ea. (talk) 01:57, 1 September 2026 (UTC)

  Loads for me fine, but takes 1-2s. MarkLSteadman (talk) MarkLSteadman (talk) 02:02, 1 September 2026 (UTC)

  It's working again for me now. shrug --EncycloPetey (talk) 02:20, 1 September 2026 (UTC)

Wishlist 2027, invitation to share feedback

Hi, I’m Sonja and I lead some of the teams at the Foundation who will be responsible for picking up wish work under the new wishlist process.

As you may know, the Community Wishlist started out as an annual process through which Wikimedia contributors submit and vote on technical improvements they would like the Wikimedia Foundation to work on. The main goal of it is and has been to improve the editing experience by making changes and features the community asks for specifically.

In recent years, the process behind the wishlist has changed, and we’ve heard from many of you that it no longer meets many community members’ needs. So now, the Foundation is designing a new process with the community to improve how wishes are triaged, voted on, and prioritized in a way that is transparent, balanced across project families and language editions, and takes into account what the Foundation can deliver.

I would like to get community input specifically on these three stages of the Wishlist process:

• The triage stage, meaning how wishes are fleshed out, organized and filtered prior to voting
  • We recommend to have a working group, including volunteers from various wikis and Wikimedia Foundation staff to work through this together
• The voting stage, including who may vote and how votes are structured
• The post-vote stage, including how to bring equity into what work is prioritized
  • One way to do this is to rank wishes within 3 categories: Large Wikipedias or covering all wikis, small and medium-sized Wikipedias, and sister projects, so that top-voted wishes from smaller projects also get attention

This message is an abstract of the full proposed process. As you read the proposed ideas on Meta (available in your language), please speak up about whether you think this will work well or if there are ways to make it stronger.

Regarding the timeline, this consultation is open for two weeks. You can post your feedback on Meta (in your preferred language) or in response below.

For this year’s cycle, we plan to have the wish submission period in late October/early November and the triage process completed by late November. To respect the end-of-year holiday season, voting would happen in early to mid January. This first voting cycle is meant as a first step to try out a new process, and there will be more opportunities to provide feedback along the way, so that we can figure out the best process for future years together.

SPerry-WMF, delivered by Trizek (WMF) (talk) 13:52, 1 September 2026 (UTC)

Long lists of copyrighted works on author pages

Do we want long lists of copyrighted works on author pages? See, e.g., Author:Alexandre Christoyannopoulos, which contains external links to works that will remain copyrighted until 70 years after the author's death, while the author is still living and relatively young. I understand if some author pages include works that are going to enter the public domain in the near future, but this seems like too much to me. -- Jan Kameníček (talk) 17:26, 2 September 2026 (UTC)

Keep Listing these works is useful for readers, particularly in cases where we can refer that person to a copy to read now. This is similar to an interlibrary service, where a given institution may not have every piece you are looking for but will try to help you find it. There may be concerns about users trying to pre-emptively add local copies of works that we cannot host for copyright reasons and if so, the solution is to have a template that points out how it can't be hosted here, similarly to how we have {{copyright-until}}. Having a list of works that includes some things and excludes others gives a mistaken impression that the list is exhaustive or at least an attempt to be comprehensive, which is what we do for authors of classic literature. It would be confusing and inconsistent to have some author pages list all works and then some only list a subset and some others still list all works but tag a few with {{copyright-until}}, etc. ―Justin (koavf)❤T☮C☺M☯ 17:43, 2 September 2026 (UTC)

Well the current listing does not distinguish between copyrighted freely-licensed works that have not yet been hosted vs. copyrighted works that have not been released. I certainly don't object to long lists of freely-licensed works that wouldn't enter the public domain until a long time in the future, if that is the question. MarkLSteadman (talk) 17:47, 2 September 2026 (UTC)

I mean copyrighted works that have not been released and will not be hostable for many decades. --Jan Kameníček (talk) 17:53, 2 September 2026 (UTC)

For contemporary authors, I would generally delete. As here, it just promotes confusion between hostable and non-hostable works. For authors where we are looking at renewal / non-renewal, I think it makes more sense to have the lists as they serve to track why clearly, but for a contemporary author, the proper place for sticking such bibliography is on the wikipedia page. It allows linking to other sources, narrative text about the works, context etc. MarkLSteadman (talk) 18:59, 2 September 2026 (UTC)

• I don’t think that one standard policy is a useful solution. My opinion on whether an individual author should have many items listed depends on several factors. For instance, the author in this case I think should not have a list, because most of his works are copyrighted and published recently, and the author is still alive. But I don’t think that such a list would be always inappropriate; for a different example, I think it would be fine to list Donald Trump’s privately published works (especially The Art of the Deal), if only to note that they’re copyrighted. On the other hand, for long-dead authors whose published works are still subject to copyright based on the year of publication, I think it makes more sense to list all of them, with the renewal IDs, as this is helpful for contributors to the project in the future and avoids duplication of work. TE(æ)A,ea. (talk) 19:59, 2 September 2026 (UTC)

  This is roughly my opinion as well. For nearly all modern authors, especially living ones, for whom most of the works are still under copyright and likely to be for decades to come, no list should be maintained. In the past, we have made a few occasional exceptions for very high profile authors whose fans will continually add to the lists, such as Author:Stephen King, which I see has been recently deleted. (I thought we had found a couple of his works now in the public domain, but perhaps not). But for deceased authors, whose works have begun to enter the public domain, the focus should be on listing hostable works (ideally with source links), and tagging listed works that are not hostable with a template to discourage copyvio. --EncycloPetey (talk) 23:26, 2 September 2026 (UTC)

\hline not working in <math>

While working on Spherical Trigonometry, I noticed that \hline no longer renders as a horizontal line in the alignat environment in <math>, instead replaced by the text "HLINE TBD". This can be seen, for example, on this page. Does anyone know why this is happening, and possible solutions or alternatives? Gunjounoame (talk) 23:13, 2 September 2026 (UTC)

Book subtitle

Hi, I added "book subtitle" in MediaWiki:Proofreadpage index data config.json, and it can now be added in indexes. But it doesn't display, e.g. Index:David-Neel - My Journey to Lhasa.pdf or My Journey to Lhasa/Introduction. Any idea? Thanks, Yann (talk) 15:57, 4 September 2026 (UTC)

Guidance requested: supervised AI-assisted transcription and proofreading pilot

I would appreciate guidance before proceeding with a small Proust transcription pilot.

I am working, in a strictly personal capacity, on the 1922 Chatto & Windus edition of Marcel Proust's Swann's Way, translated by C. K. Scott Moncrieff: https://en.wikisource.org/wiki/Index:Swann%27s_Way,_trans_Scott_Moncrieff_(f).pdf. I use an AI assistant in a supervised browser session. The assistant has helped with bibliographic metadata, page-list checking, OCR correction and visual comparison of provisional transcriptions against the scan. Public actions are performed only after my explicit authorisation; there is no unattended process. The assistant has already created Index metadata through the normal web interface, but no Swann's Way Page-namespace transcription has yet been published.

The proposed pilot is deliberately small and continuous: scan views 1–25, comprising nine blank views, six textual front-matter pages and printed pages 1–10. Sixteen textual pages have been visually compared with the scan, with a second AI-assisted comparison, and the page boundaries, running headers and printed folios have been checked. Validation would be left to a different human contributor.

Before making these Page-namespace edits, I would like the community's view on three points:

1. Should AI-prepared and AI-checked page text initially remain at Not proofread until a human has personally compared the complete page with the scan, rather than being marked Proofread?

2. Does supervised browser automation for a small number of explicitly authorised edits require a separate bot account and prior bot approval, even when each page is reviewed and the rate is kept low?

3. Is there any additional disclosure, edit-summary wording or project documentation that the community would like for this pilot?

I will not publish the proposed page batch or change its quality statuses until this discussion has had time to receive guidance. HyakinthosPorphyreos (talk) 04:35, 7 September 2026 (UTC)