Jump to content

Wikisource:Scriptorium

Add topic
From Wikisource
Latest comment: 48 minutes ago by Beleg Tâl in topic Portal naming
Scriptorium

The Scriptorium is Wikisource's community discussion page. Feel free to ask questions or leave comments. You may join any current discussion or start a new one; please see Wikisource:Scriptorium/Help.

The Administrators' noticeboard can be used where appropriate. Some announcements and newsletters are subscribed to Announcements.

Project members can often be found in the #wikisource IRC channel webclient. For discussion related to the entire project (not just the English chapter), please discuss at the multilingual Wikisource. There are currently 603 active users here.

Announcements

[edit]

Wikimedia Education Program - National Education Policy Pilot Project at Fergusson College, Pune

[edit]

The Open Knowledge Initiatives (OKI) at International Institute of Information Technology, Hyderabad is a strategic initiative with the aim to foster language diversity and promote equitable access to knowledge across the Indian subcontinent. Through community-led and multilingual efforts across Wikimedia projects like Wikipedia, Wikimedia Commons, Wikisource, Wikidata in research, partnerships, technology development, and outreach, the initiative seeks to strengthen and expand the open knowledge and technology ecosystem.
Under the Wikimedia Education Program - National Education Policy Pilot Project, OKI aims to develop a strategic framework for integrating open knowledge ecosystems into the Indian education landscape, directly responding to the mandates of the National Education Policy (NEP) 2020 and integrating the findings of the 2024 CIS-A2K study. OKI is facilitating and mentoring the community collaborations with different educational institutions to design the scalable process modules.
In collaboration with Fergusson College, Pune and Wikimedians, we have started Wikisource:Wikimedia Education Program - National Education Policy Pilot Project at Fergusson College, Pune. We kindly request for the community support in this endeavor.
Regards, Subodh (OKI) (talk) 12:50, 28 January 2026 (UTC)Reply

Proposals

[edit]

Proposal: Add option for Wikidata item in Index namespace

[edit]

In some wikisources, basic data about a work in Index namespace comes from Wikidata, compare here. This new trend is implemented by inserting the option in MediaWiki:Proofreadpage index template and MediaWiki:Proofreadpage index data config.json. This makes the data centralised, and also readable by search engines that rely on Wikidata. I am proposing the addition here. This will be open to choice of individual editors, so that editors may fill up the Index page data as per current style or opt for importing from Wikidata. Hrishikes (talk) 13:58, 30 January 2026 (UTC)Reply

 Comment Since a lot of editors here are linking scans and Index pages into data items for the work instead of the data item for the edition, I foresee a lot of mismatched information using this approach. On smaller Wikisources, this is less of an issue, but for a large project like en.WS, there will be a lot more potential for mismatched information. At the very least, we would need to agree on what values to use in certain locations: For example, Wikidata tracks editions and not always separate print runs, but here we will often make a distinction between impressions of the same edition issued in different years. --EncycloPetey (talk) 20:18, 30 January 2026 (UTC)Reply
The edition versus print issue is a problem, but that has been sorted out by treating prints as editions. The item linked in my proposal is a reprint treated as edition in Wikidata. Every index requires a separate Wikidata item for this scheme to work, be it edition or print. Currently, index page data can be fetched from the Commons file; those who wish can do so. This Wikidata scheme will just create another option, to fetch data from Wikidata, like what is done in Author pages. Hrishikes (talk) 04:29, 31 January 2026 (UTC)Reply
I wonder if this change might actually make it easier to automatically track and fix Wikidata items that aren't modelling works properly? Certainly, I think if we were to proceed with this, it would be wise to start small and iron out any issues before making it a regular practice. —Beleg Tâl (talk) 22:03, 31 January 2026 (UTC)Reply
@Beleg Tâl: — Yes, of course. But I believe adding just an extra option is starting small. Big things are not now proposed. This option will motivate proper Wikidata entries at edition level (as opposed to work). Later, it will be possible to make appropriate queries using Wikidata tools to find various patterns and statistics. It will be possible to make entries in Author pages using a bot, instead of manually (the system exists elsewhere; in this set-up no vandalism is possible because the bot will correct those during next update). With proper Wikidata entries, works can be made available in the Wikisource android app (made available in PlayStore) for ease of readers. A work recently completed by me, Some Notes on Indian Artistic Anatomy, is available in the app. But I fully agree that we should start small. Hrishikes (talk) 16:57, 1 February 2026 (UTC)Reply

Bot approval requests

[edit]

Repairs (and moves)

[edit]

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

See also Wikisource:Scan lab

Index:File:When Peoples Meet.pdf

[edit]

wrong title, should be Index:When Peoples Meet.pdf Duckmather (talk) 02:51, 26 January 2026 (UTC)Reply

Moved. -- Beardo (talk) 05:26, 26 January 2026 (UTC)Reply
Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. ToxicPea (talk) 01:00, 31 January 2026 (UTC)Reply

Should be moved to Index:When knighthood was in flower or, The love story of Charles Brandon and Mary Tudor, the king's sister, and happening in the reign of...Henry VIII; (IA cu31924022498913).pdf (i.e. to change "bor" to "or"). However, I had already started proofreading it a long while ago, so this'll need an admin Duckmather (talk) 02:53, 26 January 2026 (UTC)Reply

I think it is best to get the file on Commons moved first. -- Beardo (talk) 01:08, 4 February 2026 (UTC)Reply
@Beardo: just requested the move on Commons! Duckmather (talk) 05:06, 4 February 2026 (UTC)Reply
@Beardo: move is done on Commons, you can do the move here now Duckmather (talk) 19:50, 4 February 2026 (UTC)Reply

File:Superseding Indictment, United States of America v. Robert Sylvester Kelly, also known as "R. Kelly".pdf is a redirect file to File:Superseding Indictment, United States of America v. Robert Sylvester Kelly, also known as R. Kelly.pdf. So this index will have to be moved to Index:Superseding Indictment, United States of America v. Robert Sylvester Kelly, also known as R. Kelly.pdf. SnowyCinema (talk) 19:29, 26 January 2026 (UTC)Reply

Hello, I tried to follow the instructions at Help:Beginner's guide to adding texts and (for uploading) Help:Internet_Archive#ia-upload, which resulted in commons:File:The_Ten_Princes_-_Ryder_-_Dandin's_Dasha-Kumara-Charita.djvu. Then I created Index:The ten princes ryder dandin 27s dasha kumar charita.djvu (clearly a mistake, needs to be deleted) and Index:The Ten Princes - Ryder - Dandin's Dasha-Kumara-Charita.djvu. There are a couple of (possibly related) problems:

  • For some reason, the set of pages in the uploaded file here (on Wikisource / Wikimedia Commons) does not match the set of pages shown at the Internet Archive.
  • In the page scans, the OCR-ed text is off by one page from the corresponding page.

Could someone help fix this mess? Not sure what I did wrong. Shreevatsa (talk) 07:07, 29 January 2026 (UTC)Reply

@Shreevatsa: this problem sometimes occurs with scans from IA; for each invalid view the text if off by 1 page. The file should be fixed now. • M-le-mot-dit (talk) 09:46, 29 January 2026 (UTC)Reply
Thank you. I see you uploaded a new version of the DJVU file. What was the fix? Shreevatsa (talk) 16:47, 29 January 2026 (UTC)Reply
@Shreevatsa: DjVuLibre tools (djvm, djvused) allow some operations on DjVu files (delete a page, get or set hidden text). • M-le-mot-dit (talk) 19:12, 29 January 2026 (UTC)Reply

Something happened (I think a while ago) that broke many of the tooltips I have set up for abbreviations that contain superscripts and are throwing up errors, as can be seen in the link above. The problem will be somewhere in Template:Nornabr, Module:Nornabr or Module:Nornabr/data. Would anybody with more template knowledge be able to fix this?— 🐗 Griceylipper (✉️) 19:25, 1 February 2026 (UTC)Reply

I had a look, and while I'm not super familiar with wiki templates, it might have something to do with the fact that {{sup}} now uses TemplatesStyles instead of inline CSS (i.e. line 2 of Module:Nornabr/data). You might get more responses if you ask at Scriptorium/Help. —Tosca-the-engineer 09:19, 14 February 2026 (UTC)Reply

Other discussions

[edit]

Template:Featured download

[edit]

I don't think that this template should be included within mainspace pages outside of Main Page, like it has sometimes before. Here's a complete list of all 5 pages that use this template that way:

  1. Some Mistakes of Moses
  2. Love and Freindship and other early works
  3. The Princess Pourquoi (collection)
  4. A Puritan Bohemia
  5. The story of saiva saints

It seems a bit redundant since the Download button at the top of every page is already there. SnowyCinema (talk) 08:12, 8 January 2026 (UTC)Reply

I agree. I don't recall any of these five being a featured work (they're certainly not in the category), so using this template on them is misleading at best. Beeswaxcandle (talk) 07:32, 9 January 2026 (UTC)Reply
Since a bit of time has passed, Done—removed these instances, as that template is really supposed to only be used on {{Featured text}}, for the Main Page, not on work front matters. SnowyCinema (talk) 00:17, 20 January 2026 (UTC)Reply

Physique magazines

[edit]

Hello, I'd like to ask for guidance regarding the suitability of certain historical US magazines for Wikisource. Magazines such as Physique Pictorial, Young Adonis, and Grecian Guild Pictorial were published in the United States in the 1950s–1960s and are considered to be in the public domain under PD-US-no notice. Scans of many issues are already available on Wikimedia Commons (e.g. File:Young Adonis.pdf, File:Physique Pictorial Vol 12 No 1.djvu).
Are the contents of such magazines acceptable for transcription on English Wikisource? Are there any specific policies or community guidelines on en.Wikisource regarding erotic/adult (18+) material? PolskiChłopak (talk) 21:05, 18 January 2026 (UTC)Reply

@PolskiChłopak: Hi, and welcome to Wikisource. To answer your question, there is no rule against NSFW or 18+ material being hosted at Wikisource. We have for example pornographic films and erotica here already. The only concern would be copyright and the nature of publication, etc., which magazines like these should pass as you noted. SnowyCinema (talk) 21:07, 18 January 2026 (UTC)Reply

Tech News: 2026-04

[edit]

MediaWiki message delivery 20:29, 19 January 2026 (UTC)Reply

Annual review of the Universal Code of Conduct and Enforcement Guidelines

[edit]

I am writing to you to let you know the annual review period for the Universal Code of Conduct and Enforcement Guidelines is open now. You can make suggestions for changes through 9 February 2026. This is the first step of several to be taken for the annual review. Read more information and find a conversation to join on the UCoC page on Meta.

The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. This annual review was planned and implemented by the U4C. For more information and the responsibilities of the U4C, you may review the U4C Charter.

Please share this information with other members in your community wherever else might be appropriate.

-- In cooperation with the U4C, Keegan (WMF) (talk)

21:02, 19 January 2026 (UTC)

Template:Engine usages

[edit]

When do we want and not want {{Engine}} to be used? Are there any cases where it's definitely inappropriate? The template docs don't really say anything specifically, but I found one example of an Index page that uses it for only the page namespace, but not the actual transcluded work: Index:Darby O'Gill and the Good People by Herminie Templeton Kavanagh (1903).djvu. And all the work is anyway is a collection of short stories, average in page structure.

I also put {{Engine}} on a work I did called Southern Antiques (1931) years ago, but now that I think about it, it is a short nonfiction book with an average Introduction + numbered chapters structure, so I don't know that this was the right call. My understanding is that {{Engine}} is best for works like encyclopedias or dictionaries or copyright records, where there's loads of material within a multi-volume nonfiction work with logical topical separations.

(And the search engine doesn't actually seem to work that well, but we can get to that another day.) SnowyCinema (talk) 00:07, 20 January 2026 (UTC)Reply

Where does the "Cast and Crew" section from

[edit]

Hi, I want to transcribe a film in my home wikisource, and I'm using Blackmail (film) as an example. I couldn't find where the data of Cast and Crew section came from. I tried to copy to Sandbox [7], but it doesn't appear to have the Cast and Crew section. Anybody could shed a light on this? Thanks. Bennylin (talk) 06:05, 24 January 2026 (UTC)Reply

@Bennylin: Hi, and thanks for taking interest in our film projects here. I looked and saw you're working on at the Indonesian Wikisource. The Cast and Crew section is generated by the template {{Cast and crew}} which is internal to {{Film}}. And the logic is in several Lua modules: Module:Cast and crew and Module:Film. Here's an example invocation: {{cast and crew|Q816038}} This can produce some code by itself. Hopefully that helps. If you need more help with it, I can try to take some time out this week or so to work on stuff over at idws with you. SnowyCinema (talk) 06:36, 24 January 2026 (UTC)Reply
Thanks for the fast response. I will try it. Bennylin (talk) 07:21, 24 January 2026 (UTC)Reply
It works now (id:Darah dan Doa (film)) even before I linked it to the Wikidata item. I wonder where it got its Wikidata ID from. Bennylin (talk) 06:19, 28 January 2026 (UTC)Reply

Best choice for this editorial?

[edit]

So I came across Chicago Press and Tribune/Editorial on Harper's Ferry and wanted to switch it to a scan-backed source (as well as transcribe the rest of that particular issue), so I transcribed Page 2 of Index:Chicago Press and Tribune 1859-10-20.pdf and transcluded it to Chicago Tribune/1859/October/20/Where the responsibility belongs. The question I have now is this -- what should I do with the old version? Should I just blank the page and redirect to the scan-backed version? Make an edition page and include links to both? Leave it how it is right now? Let me know what you think. Mathmitch7 (talk) 19:23, 24 January 2026 (UTC)Reply

I would say to redirect the non-scan-backed copy to the scan-backed one, making sure that the edit history is preserved. CitationsFreak (talk) 13:42, 25 January 2026 (UTC)Reply
Deleted per WS:Deletion policy#G4. @CitationsFreak: We do not keep such unnecessary redirects. Unlike Wikipedia, where contributors create their own texts—often building upon the work of others—we only transcribe texts, and therefore the page history is not as important here. --Jan Kameníček (talk) 14:07, 25 January 2026 (UTC)Reply
Thanks! Helpful clarification of policy Mathmitch7 (talk) 15:40, 25 January 2026 (UTC)Reply

Poems, by S. T. Coleridge. Second Edition, To Which Are Now Added Poems by Charles Lamb and Charles Lloyd

[edit]

can this be transcribed? i believe the link has a scan

https://archive.org/details/bim_eighteenth-century_poems-by-s-t-coleridg_coleridge-samuel-taylor_1797 Skittythetranscat (talk) 10:55, 26 January 2026 (UTC)Reply

The 1803 edition is currently being transcribed, but has not had many volunteers working on it. --EncycloPetey (talk) 15:08, 26 January 2026 (UTC)Reply
When I searched for it nothing came up, how weird.
Thanks for linking! Skittythetranscat (talk) 10:35, 27 January 2026 (UTC)Reply
It's listed and linked at Author:Samuel Taylor Coleridge. It's often worth checking the author's page in addition to making a general search. --EncycloPetey (talk) 14:56, 27 January 2026 (UTC)Reply
Yes, it can. Do you need help with uploading the scan or creating the index page? -- Jan Kameníček (talk) 15:09, 26 January 2026 (UTC)Reply
Once the 1803 edition is done I might look into it. Thanks for the offer. Skittythetranscat (talk) 10:35, 27 January 2026 (UTC)Reply

Tech News: 2026-05

[edit]

MediaWiki message delivery 21:17, 26 January 2026 (UTC)Reply

Double-click errors in Proofread Page

[edit]

Last night I noticed odd behavior while editing in the Page namespace. The behavior is still occurring today. When I double-click a word, I now get the front half of a word selected instead of the entire word. It selects the word only up to the point where my cursor is positioned, instead of the entire word.

This behavior does not occur outside of the Proofreading in Page space, nor in other applications where I've tested for it. Although it does not occur 100% of the time, it is occurring frequently enough that I noticed it causing errors in proofreading, as I expect normal double-click behavior to select all of word, so that I can replace it, rather then retaining the end of the existing word.

Are other people experiencing this behavior in Page proofreading? --EncycloPetey (talk) 20:29, 28 January 2026 (UTC)Reply

I believe that double-click-to-select is a browser-based function; have you experienced this in other browsers? I can confirm that I do NOT have this issue, and I am using Chrome on Windows. —Beleg Tâl (talk) 20:35, 28 January 2026 (UTC)Reply
I am not experiencing it either. Tried Chrome, Firefox and Opera on Windows. --Jan Kameníček (talk) 20:45, 28 January 2026 (UTC)Reply
If it is a browser-based function, then I would expect the same behavior in my browser regardless of the site / page. I considered this possibility and checked other sites, both in and out of Wikimedia. I am only experiencing the issue when editing in the Page namespace. --EncycloPetey (talk) 22:07, 28 January 2026 (UTC)Reply
  • That doesn’t change anything. I’ve had a long-running issue which only occurs in Page: and appears to an issue specific to me (not your issue, though); in other Web-sites, including other Wikimedia sites, there is no problem. For the record, I also don’t have your issue (I checked Chrome and Edge). TE(æ)A,ea. (talk) 00:43, 29 January 2026 (UTC)Reply

Issues with editing window height in ProofreadPage

[edit]

Has anyone encountered that recently? I've been having issues with the editing layout being compressed to a very small height, making it kind of unusable. I can reproduce on another account, so I'm a bit surprised it'd affect only me. (For details, see my report at phab:T393231#11570707.) — Alien  3
3 3
21:22, 30 January 2026 (UTC)Reply

Yes for past two days, I've been experiencing the second version you reported "the edit boxes overflowing onto the form buttons". No scroll bars on the edit window any more—instead the edit window expands to take in the entirety of the content, and the "form buttons" (Proofread status buttons, Publish buttons etc.) are floating in the middle of the edit box.
Edit: I've checked which feature was causing this extreme version of the problem in my case. It went away when I turned off "Improved Syntax Highlighting" in Beta Features. Pasicles (talk) 21:43, 30 January 2026 (UTC)Reply
@Alien333: as a turnover you can use the grey handle above the Summary to expand the edit area. • M-le-mot-dit (talk) 22:19, 30 January 2026 (UTC)Reply
My edit window suddenly reduced in height about the same time. I corrected the problem by dragging the edge of the editing window down, and it has stayed at the new height. I'm guessing that some sort of data was accidentally overwritten, or some change altered the default. The [OCR] button no longer appears at the top of my edit window; I have only the new drop-down OCR menu instead. And there in now an intrusive "Insert" drop-down menu at the top that was not there previously. The menu duplicates functions of the options below it, but also offers items that are completely useless in the Page namespace, like category and redirect insertion options, and the ability to sign my posts (in the Page namespace ??). This looks like Wikipedia-specific editing content misapplied to the Page namespace. --EncycloPetey (talk) 22:54, 30 January 2026 (UTC)Reply
And for those of us who don't have the editing toolbar turned on, there is no grey handle to drag. I've got one line of text visible in header and footer, and four lines in the Page body box. The page image is a piece from the middle and can't be scrolled, so the Page: namespace is unusable for me, unless I turn the toolbar back on. It has no useful functionality for me, other than the occasional need to do OCR and it just wastes space on a smaller screen <grumble>. N.B. The "Insert" drop-down menu is the CharInsert gadget and is supposed to appear at the bottom of the Edit window between the footer box and the Summary. Beeswaxcandle (talk) 07:45, 31 January 2026 (UTC)Reply
Addendum: It seems the page height value is now made uniform across all namespaces. So, when I enlarged the Page namespace editing window, it meant that I also made the Module and Author namespace windows larger, but the calibration is off. What is a good size in the page namespace is too tall in other namespaces; and a height that is good for Author and Module namespaces is too small for the Page namespace. The result is that I'm constantly having to adjust by edit window height every time I shift to working in a new namespace. --EncycloPetey (talk) 16:22, 31 January 2026 (UTC)Reply
If you don't use the editing toolbar, you may add a style to the class wikiEditor-ui-view in your common.css, e.g.
.wikiEditor-ui-view { height: 600px; }
until a fix is found. • M-le-mot-dit (talk) 11:43, 1 February 2026 (UTC)Reply
Thanks, but it didn't work. It starts up okay at normal height, but then shrinks down to the four lines etc. as the page completes loading. So, there's something in the patch that is overriding. Beeswaxcandle (talk) 07:31, 3 February 2026 (UTC)Reply
.wikiEditor-ui-text { height: 600px !important; } might do better. — Alien  3
3 3
09:14, 3 February 2026 (UTC)Reply
No, still collapses down. Will see what happens when this week's release propagates. Beeswaxcandle (talk) 07:26, 4 February 2026 (UTC)Reply
I seem to be back to "normal" currently. Will see what happens as I move through some pages. Beeswaxcandle (talk) 06:02, 6 February 2026 (UTC)Reply
Something new has just lost my ability to resize the edit window in the Page namespace. I will have to stop editing until this is fixed, since I cannot see enough of the text at one time to be able to proofread. I had a properly sized window until a few minutes ago, when I started a new page without window resizing. This problem exists on other Wikisource projects in their Page namespace equivalent as well, not just here. --EncycloPetey (talk) 01:12, 5 February 2026 (UTC)Reply
They tried as far as I understand to revert last week's issues. Normally we should be back where we were. Is the window still too vertically small? I can't reproduce anymore. — Alien  3
3 3
07:29, 5 February 2026 (UTC)Reply
It is no longer too small, but I have still lost the option to resize the window. There are times when I would rather run the scan page and edit window above each other, such as when proofreading footnotes that contain Greek. Without the option to alter the size of the edit window, this is still impossible. --EncycloPetey (talk) 14:38, 5 February 2026 (UTC)Reply
Not being able to resize the edit window feels like an accessibility issue. --EncycloPetey (talk) 14:49, 5 February 2026 (UTC)Reply
I have as well. I have found that resizing the optical window in a certain work carries over from page to page. —Justin (koavf)TCM 01:14, 5 February 2026 (UTC)Reply

How do I start adding sources?

[edit]

There are several primary source documents that I know are public domain (hundreds of years ago) that I'd like to add to Wikisource, but I am a bit confused; how do I start the new page? Is there a template? How does copyright apply to translations? VidanaliK (talk) 01:06, 31 January 2026 (UTC)Reply

Have you read Help:Beginner's guide to adding texts? You should start by uploading a scan of the work to Commons, then create an Index here based on that scan.
Translations have their own separate copyright status. For a translation to be acceptable here, both the original and the translation need to be in public domain. -- Beardo (talk) 02:11, 31 January 2026 (UTC)Reply
@VidanaliK: You can also start with proofreading or validating indexes that have already been uploaded by somebody else, e. g. within the Monthly Challenge collaboration, which might be easier for a beginner. Or if you have some specific scan that you want to transcribe here and need some help, we can help you with the technical stuff like uploading and creating the Index page. --Jan Kameníček (talk) 21:40, 31 January 2026 (UTC)Reply

National anthems

[edit]

I just wanted to note, since many national anthems have been put up for deletion as of late, that doing an actual transcription project of National Anthems of the World (1960), a text which was not renewed, might be a worthwhile endeavor so that we can have pages for specific countries' national anthems. I checked, and most of our national anthems that were considered for deletion did not originate from this collection. We've already more or less proven the Latvian and Portuguese anthems in this text are in the public domain, and many or most of the others likely are also. But the tricky thing is we will have to assess each of the anthems' copyrights individually, since for various reasons some originals or translations that appear in this book may have some way they were URAA'd or otherwise still under copyright, as has been noted before in the CV discussion threads. Pinging @MarkLSteadman, @TE(æ)A,ea.: as users who might be interested in this. Consider this somewhat of a request, as I can't work on sheet music and LilyPond myself (yet). I can help on the copyright parts if needed. SnowyCinema (talk) 12:56, 31 January 2026 (UTC)Reply

I requested a different collection of National Anthems from 1943, hoping that it again would be non-renewed, alas it was renewed. MarkLSteadman (talk) 11:30, 1 February 2026 (UTC)Reply

Vast free space at the bottom of a page

[edit]

Does anybody have any idea why there is so much free space at the bottom of Manifesto of the Communist Party, below the disclaimers and everything? -- Jan Kameníček (talk) 01:17, 2 February 2026 (UTC)Reply

On the left hand side it has links to the advertisement pages, so it seems to be something to do with that. -- Beardo (talk) 02:51, 2 February 2026 (UTC)Reply
It's an issue with the advertisement template [11], introduces the extra space. GhostOrchid35 (talk) 04:04, 2 February 2026 (UTC)Reply
I note that Fantastic Universe/Volume 08/Number 3 also has a lot of blank space - I guess for the same reason. -- Beardo (talk) 23:01, 3 February 2026 (UTC)Reply
From what I've seen it appears to be every page that uses that template where more than one page is transcluded within the template. ToxicPea (talk) 00:44, 4 February 2026 (UTC)Reply
While this error does seem to only occur with multi-page transculsions. The Merry Men and Other Tales and Fables, The Dawn of Canadian History and Dreams of a Spirit-Seer, transclude multiple pages without this error. GhostOrchid35 (talk) 13:48, 8 February 2026 (UTC)Reply
Does the problem only arise when the adverts are at the end ? -- Beardo (talk) 16:22, 8 February 2026 (UTC)Reply
Nope. See The Famous Speeches of the Eight Chicago Anarchists in Court for example. ToxicPea (talk) 16:26, 8 February 2026 (UTC)Reply
And I tried moving the ads in the Fantastic Universe and that did not help. -- Beardo (talk) 16:31, 8 February 2026 (UTC)Reply
Revise Template:Advertisements?--TunnelESON (talk) 06:22, 15 February 2026 (UTC)Reply
If I try replacing {{advertisements}} with {{front matter}} the extra space still appears. The issue is likely with {{collapsed section}}. ToxicPea (talk) 16:35, 15 February 2026 (UTC)Reply

Tech News: 2026-06

[edit]

MediaWiki message delivery 17:43, 2 February 2026 (UTC)Reply

Problem with the editing interface

[edit]

Hello. For the last few days I've been having a strange issue with the editing interface. The left box (where I can actually edit the text) doesn't have a roll bar, and the text just keeps going, with parts of it behind other elements, which makes it not viable to edit. It has something to do with my account, since it works after I log off it goes back to normal. It affects only Wikisource in several languages. I tried changing the appearance and disabling all gadgets, and the problem persists. Any one else dealt with this? HendrikWBK (talk) 18:08, 2 February 2026 (UTC)Reply

See #Issues with editing window height in ProofreadPage above. There seem to be several connected issues with editing the Page namespace right now. --EncycloPetey (talk) 18:35, 2 February 2026 (UTC)Reply
Thank you, I must have missed this. HendrikWBK (talk) 18:39, 2 February 2026 (UTC)Reply

Handling an entire chunk of misplaced text

[edit]

In one of the works I've been proofreading, Page:The reference shelf v4 no5 1926.djvu/45 there is an obvious error in the paragraphs of text currently marked using the SIC template. The chapter is a reprint from the Educational Record, and based on a check of the original it seems that the line "appropriations. Most students of government, however," has been accidentally swapped with "appropriations totaling two hundred million dollars.". What would be the best way of handling this? Arcorann (talk) 00:21, 3 February 2026 (UTC)Reply

I would put a note in the page header when it gets transcluded, something like
{{header|...|notes=Note: the source text contains errors, which have been reproduced faithfully. The errors are: The lines "[Line A]" and "[Line B]" at [insert location] have been accidentally swapped. The passage should read: "[The original passage]". The original passage can be read here: [link] }}
Tosca-the-engineer 08:25, 3 February 2026 (UTC)Reply
You're going to get a conflict here between the people who think the purpose of WS is to be an exact transcription of pages, and nothing more, and those who think the purpose is to create a work that someone might actually want to read. Personally, I'd either just swap the lines back (with a note in the source page), or use SIC. qq1122qq 09:31, 4 Feb 2026 (UTC).

Best practice and accessibility for eye spellings

[edit]

I searched and found no previous discussion. I'm inclined to think that eye spellings should have {{SIC}} applied for 1.) intelligibility and 2.) accessibility. Is there any reason to not do this? —Justin (koavf)TCM 20:15, 3 February 2026 (UTC)Reply

Throwing out a few reasons to not put tooltips:
  • Because texts which use such spellings usually use them extensively, and we'd end up with a sea of tooltips.
  • Because it means assumptions from our part and decisions on how it "should" look that would be integrated into the text about everywhere.
  • (Specific to using {{SIC}} Because it implies that such spellings are errors: to quote the doc, This template should only be used for words that are actually typos. It is not for indicating a different or obsolete spelling.)
  • (Because it could be largely vain endeavour knowing tooltips are not supported by a wide range of devices.)
More specifically, I at any rate strongly oppose requiring tooltips because that would mean tons of unneeded work.
And then on reasons to do so:
  • intelligibility: we host published editions, not modernisations. What we offer is supposed to be the work as it was.
  • accessibility: erm, why? I don't see the link with the topic at hand. As I said above tooltips are very inaccessible so it wouldn't change much accessibility-wise.
Alien  3
3 3
20:45, 3 February 2026 (UTC)Reply
I'm not concerned about tooltips as such, I'm concerned about a screen reader coming across a bunch of wonky spelling nonsense that a blind person will hear as a string of gibberish or a deaf person who can read standard English will see as a bunch of gibberish. If we can make this intelligible to a person who is using assistive technology or who is literate but has never heard English, why wouldn't we? —Justin (koavf)TCM 20:47, 3 February 2026 (UTC)Reply
This sounds to me like a good use case for creating an annotated version tbh —Beleg Tâl (talk) 21:14, 3 February 2026 (UTC)Reply
I did consider that for cases that have a lot of eye dialect spellings for a certain character, but there are also works where there are very occasional deliberate misspellings like this and it seems a little much to create an entire secondary edition just for a handful of words. —Justin (koavf)TCM 21:16, 3 February 2026 (UTC)Reply
Because screen readers have the option of "go back and spell that word for me", and the English language already has objectively absurd spelling rules, and idiosyncratic spelling is not that difficult to understand. It might take a few pages to get your bearings, but tbh, sometimes that's part of the appeal. Phonetic spelling is often indistinguishable from the "correct" spelling when read aloud anyway (e.g. skool vs school), and considering that a large proportion of wikisource texts are 100+ years old, if a reader can't handle the idea that language and spelling change over time, they're probably in the wrong place anyway. —Tosca-the-engineer 18:33, 4 February 2026 (UTC)Reply
Okay, but did you see what I wrote above about deaf readers? —Justin (koavf)TCM 20:40, 4 February 2026 (UTC)Reply
For TV programs, they will subtitle the speaker if they believe the dialect is going to interfere with the ability of a viewer to understand what is being said. That's a form of annotation, and we already have a process in place of creating annotated editions, as previously mentioned. --EncycloPetey (talk) 14:45, 5 February 2026 (UTC)Reply
And how does that answer the question I asked to a different person? Do you know if Tosca-the-engineer read what I wrote about the deaf? —Justin (koavf)TCM 14:50, 5 February 2026 (UTC)Reply
  • This would be inappropriate use of {{SIC}}, which should only be used for errors, not intentional differences; the use of eye dialect is obviously an intentional choice, so marking it as incorrect (using {{SIC}}) would be misleading. For intelligibility, an annotated version is more appropriate; (although I haven’t finished it,) some years ago I was working on transcribing a text with much in the way of nonstandard English. My solution was to keep the text as is, with no adjustments, in the standard transclusion, and use many instances of {{asw}} to create a “modern” English rendition. This could also be applied to a work with eye dialect, to create a “clean” version. However, in both cases, the modified version is more appropriately placed as an annotation. As for accessibility, well, eye dialect is also fairly inaccessible to people who don’t use screen readers, so I don’t think that there is a major difference in this respect. For comparison, if somebody wanted to listen to an audiobook of a novel which uses eye dialect, it would be strange if all dialogue was pronounced “correctly,” without any indication of the eye dialect in the text. Thus, there’s no reason for it, and as for reasons against it, it is the goal of Wikisource to create an accurate transcription of the text. TE(æ)A,ea. (talk) 15:10, 5 February 2026 (UTC)Reply
    This adds up, especially re: {{SIC}}. I suppose the problem may be with the template itself: using "sic" in a text does not only apply to actual typos or errors, but any usage of language that could reasonably be perceived as an error. So we have restricted this template to one of the two main uses of the word, which means that I have proposed a non-solution based on the scope of the template. It seems like an annotated version is the only solution based on the existing templates and best practices. —Justin (koavf)TCM 15:19, 5 February 2026 (UTC)Reply

FYI: Spotlighting the World Factbook as We Bid a Fond Farewell

[edit]

https://www.cia.gov/stories/story/spotlighting-the-world-factbook-as-we-bid-a-fond-farewell/Justin (koavf)TCM 22:50, 4 February 2026 (UTC)Reply

I am working on rounding up folks to help put up current editions of the The_World_Factbook text - the most current years just lead to a field of red links. I think this is just a copy paste job from the internet archive, unless anyone has a more bot-directed idea. -- Phoebe (talk) 22:41, 11 February 2026 (UTC)Reply
ps this page may be helpful; and the archive has now made a collections page. -- 22:47, 11 February 2026 (UTC)

Watchlist pop-ups

[edit]

Is anyone else bothered by pop-ups on the Watchlist. I keep getting them, over and over, on every project where I am active, which is about seven projects right now. I know some folks are active on even more projects. Is there a way to opt out of the pop-ups across all projects without having to visit every project one by one and click through them each time on each project? --EncycloPetey (talk) 14:48, 5 February 2026 (UTC)Reply

Do translations done only for the Marxist Internet Archive meet inclusion criteria?

[edit]

For example, the translation at "What is an Anarchist?" appears to have been done only for the Marxist Internet Archive, sourced to this page. Many others by the same translator appear to be a similar situation. As this is an online source, where these translations seem to be self-published without editorial controls, how do we feel about these? Do they meet our inclusion criteria? SnowyCinema (talk) 15:38, 5 February 2026 (UTC)Reply

It is just a web page which can disappear any time. We should host transcriptions of texts published in a fixed stable format, we should not be doing a mirror to the Internet. --Jan Kameníček (talk) 16:23, 5 February 2026 (UTC)Reply
No one is suggesting "mirroring the Internet": that's completely insane. There are plenty of very valuable educational and cultural documents that originate online and there's no reason why a digital-first or digital-only work that is otherwise in our scope ceases to be. —Justin (koavf)TCM 18:04, 5 February 2026 (UTC)Reply
Of course. That is why I was not talking about digital-first (or -only) but about non-fixed web pages. Nothing against fixed electronic documents (e.g. pdfs), which can be easily uploaded to Commons. unsigned comment by Jan.Kamenicek (talk) .
There's no reason why a filetype should change whether or not something fits our criteria as an acceptable text. —Justin (koavf)TCM 19:31, 5 February 2026 (UTC)Reply
Again: Of course. That is why I gave .pdf just as an example. It can be any kind of a fixed electronic document. --Jan Kameníček (talk) 19:39, 5 February 2026 (UTC)Reply
HTML is a document. A PDF online has a URI, just like an HTML document has a URI. —Justin (koavf)TCM 21:21, 5 February 2026 (UTC)Reply
On the topic of these translations being "otherwise in our scope", I'm going to check that. So, when reading through the relevant policy at WS:Translations, it says (emphasis mine):

Published translations (public domain or open-licensed) have been created and released by an external translator and publisher. They allow the project to fill Wikisource with peer-reviewed, edited content and verifiable translations into English.

This seems to at best imply, and at worst outright rule, that peer-reviewed translations are the only thing we want at enWS, besides user translations at the Translation: namespace. And this is an official Wikisource policy. So, were MIA translations peer-reviewed? They don't appear to me to have been, so unless I'm mistaken about either the meaning of the policy or the situation behind marxists.org works, I think a number of these should be considered for deletion. SnowyCinema (talk) 18:22, 5 February 2026 (UTC)Reply
They were published by AK Press: https://www.akpress.org/down-with-the-law.html. MarkLSteadman (talk) 18:25, 5 February 2026 (UTC)Reply
Ah, on inspecting that book, there's a problem. The book does not internally state that any of it has a free license. Here's the copyright notice in full, as can be seen here:
Down with the Law: Anarchist Individualist Writings from
Early Twentieth-Century France
© 2019 Mitchell Abidor
ISBN: 978-1-84935-344-1
E-ISBN: 978-1-84935-345-8
Library of Congress Control Number: 2019933776
AK Press
370 Ryan Ave. #100
Chico, CA 95973
www.akpress.org
[email protected]
AK Press
33 Tower St.
Edinburgh EH6 7BN
Scotland
www.akuk.com
[email protected]
[...]
Cover and interior design by Margaret Killjoy
Cover illustration by Flavio Costantini, Les Travailleurs de la nuit I. Parigi, 1 ottobre 1901, 1964. Courtesy Archivio Flavio Costantini, Genova
@MarkLSteadman: I was going to say maybe we could bring a scan of it here to enWS, but this makes that a bit of an issue. The copyright status of the introduction and the cover, and possibly some of the other work within it, seems up in the air. Any ideas? SnowyCinema (talk) 18:55, 5 February 2026 (UTC)Reply
Abidor certainly has recognition: https://www.nyrb.com/collections/mitchell-abidor. Example: https://www.google.com/books/edition/Notebooks_1936_1947 and https://www.marxists.org/archive/serge/1944/notebooks.htm . NYRB certainly meets our editorial standards, so how to handle the Copyleft MIA version and the Copyright NYRB version. MarkLSteadman (talk) 20:19, 5 February 2026 (UTC)Reply
There is one more issue: Marxist org. copied the text from Brochure Mensuelle no 26, February 1925. That makes it a second-hand transcription, which is disallowed here per WS:WWI#Second-hand transcriptions. --Jan Kameníček (talk) 19:52, 5 February 2026 (UTC)Reply
Surely Brochure Mensuelle had a French original ? Not an English translation. -- Beardo (talk) 19:59, 5 February 2026 (UTC)Reply
Ah, so in that case it was probably transcribed from the AK press publication (issued 2019), which is the same problem. --Jan Kameníček (talk) 20:15, 5 February 2026 (UTC)Reply
It wasn't, unless the Marxist Internet Archive has a time machine. Or how else did they transcribe in 2011 a book published in 2019? MarkLSteadman (talk) 20:20, 5 February 2026 (UTC)Reply
Oh, now I can see my fault: I misread 1925 for 2025. Apologies for the confusion, I am taking all this back. -- Jan Kameníček (talk) 20:43, 5 February 2026 (UTC)Reply

Little Bitty Pretty One

[edit]

I noticed that the Wikipedia article references a 1992 Billboard article (this one) which notes that the song lapsed out of copyright. Nighfidelity (talk) 17:56, 6 February 2026 (UTC)Reply

Given the date, I'd assume that it would have been published on paper to be copyrighted. HathiTrust theoretically has a source, but a school newspaper sans copyright notice that has a list of the lyrics for popular hits is a questionable source.--Prosfilaes (talk) 00:31, 11 February 2026 (UTC)Reply

Tech News: 2026-07

[edit]

MediaWiki message delivery 23:30, 9 February 2026 (UTC)Reply

Proofread of the Month is missing pages

[edit]

Hello, I just noted this on the work's talk page, but I've noticed that February's (first) Proofread of the Month, Index:Modern Tendencies in Sculpture.djvu, is missing at least two pages. I haven't gone through every single page to verify those are the only two missing pages, but this seems to be a major problem. Advice is appreciated -- In the meantime, I'll double check the other pages in the scan; and try to find a scan that includes the missing pages, so the file can be fixed ASAP. -- Mathmitch7 (talk) 00:19, 10 February 2026 (UTC)Reply

@Mathmitch7: Repaired. 2 pages were missing (American VII and VIII). • M-le-mot-dit (talk) 14:15, 10 February 2026 (UTC)Reply
Missing pages retrieveed from Internet Archive identifier: moderntendencies00taft--• M-le-mot-dit (talk) 14:19, 10 February 2026 (UTC)Reply
Thank you!!! Mathmitch7 (talk) 23:48, 10 February 2026 (UTC)Reply

Make file from images

[edit]

Is there anyone whom I could trouble, please, to make a PDF/ DjVu file from the 11 images in c:Category:The Dweller In The Darkness, splitting the double-page spreads where needed?

Or is there a tool that I can throw them at that will do the job to a sufficiently high quality? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:59, 11 February 2026 (UTC)Reply

Someone may respond here, but we have Wikisource:Scan Lab for requests like that. --EncycloPetey (talk) 20:27, 11 February 2026 (UTC)Reply
I can do it. And EP is correct that the other board is better for these requests in the future. —Justin (koavf)TCM 20:55, 11 February 2026 (UTC)Reply
@Pigsonthewing: File:Reginald Berkeley - The Dweller in the Darkness.pdfJustin (koavf)TCM 21:10, 11 February 2026 (UTC)Reply
Thank you. Now transcribed at The Dweller in the Darkness. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:51, 12 February 2026 (UTC)Reply

authority control template in Author pages

[edit]

I've just been informed that I've been missing off {{authority control}} from the Author: pages I create. If it's a requirement to put it on Author: pages, can we not add it to the default template for Author pages? Otherwise I'm sure I'll start forgetting again at some point. Qq1122qq (talk) 20:12, 13 February 2026 (UTC)Reply

On a related note, can someone with the ability to run scripts on the sites add the template to any Author: pages I've created that don't have them? Qq1122qq (talk) 20:14, 13 February 2026 (UTC)Reply
Automatically having it added to author, main/works, and portal pages is a good idea. —Justin (koavf)TCM 20:16, 13 February 2026 (UTC)Reply
It was included on all the author pages that I have created using the default template, at the bottom, after the note about license. I don't know why Qq did not get those. -- Beardo (talk) 20:57, 13 February 2026 (UTC)Reply
When I go to Author:foo, there is no authority control added. Also, it should be on all content pages. —Justin (koavf)TCM 20:59, 13 February 2026 (UTC)Reply
If you use {{Author/preload}} it appears. I assumed that was what was meant by "default template". -- Beardo (talk) 21:02, 13 February 2026 (UTC)Reply
When I create a blank author page (e.g. for Author:Banana) this is what I get:
{{author
| firstname =
| lastname = Banana
| last_initial = Ba
| birthyear =
| deathyear =
| description =
}}
==Works==
I have no idea when/where I would use {{Author/preload}} - if there are settings I need to change in order to get better defaults, let me know and I'll change them. (edit: line breaks not displaying properly there but I don't want to mess with the threading markup) Qq1122qq (talk) 21:05, 13 February 2026 (UTC)Reply
When I create an author page it has nothing in the box, but within the text above, there is a line which says "Click to preload this page with an author template" - when I click that, it gives the header, the works subheading and then below those:
"<!-- please add author license here; see [[Help:Copyright tags]] -->
{{authority control}}"
How do you get the heading and "Works" line ? -- Beardo (talk) 21:38, 13 February 2026 (UTC)Reply
What happens when you click on Author:Beardo? —Justin (koavf)TCM 21:40, 13 February 2026 (UTC)Reply
A edit box with nothing in it. Above it, the following text:
"This page does not exist yet; you can create it by typing in the box below and publishing the page. If you are new to Wikisource, please see Help:Adding texts.
You are editing in the author namespace. This page should include an {{author}} template. Please review its documentation and Help:Author pages.
Click to preload this page with an author template
As an alternative, English Wikisource has a gadget to preload this and other namespace-relevant templates.
Note: Birthyear and deathyear parameters are deprecated in favour of pairing the author page with Wikidata and extracting the requisite data. Search for this person on Wikidata: Beardo" -- Beardo (talk) 21:45, 13 February 2026 (UTC)Reply
There is a gadget the Editing section: "Preload useful templates such as header, textinfo and author in respective namespaces." So, looks like there's more than one way at present. Beeswaxcandle (talk) 21:45, 13 February 2026 (UTC)Reply

Is there a name for the use of a semicolon when it connects two complete, independent thoughts?

[edit]

Is there a name for the use of a semicolon when it connects two complete, independent thoughts, replacing a period in headlines? For example: "McDowell Homestead Razed by Blaze; Origin Unknown" Some newspapers do not use periods in headlines, so use that style, it must have a name. RAN (talk) 17:53, 15 February 2026 (UTC)Reply

Isn't that what semicolons are usually used for? —Beleg Tâl (talk) 14:20, 16 February 2026 (UTC)Reply

Portal naming

[edit]

Looking for suggestions about what to name a portal for books about exercise and fitness. Eievie (talk) 06:00, 16 February 2026 (UTC)Reply

Portal:Fitness ? —Beleg Tâl (talk) 14:20, 16 February 2026 (UTC)Reply

There's a woman name to fix

[edit]

Here: A Cyclopaedia of Female Biography the wrong name "Scacrati-Romagnli, Orintia" should be fixed into the right one "Sacrati-Romagnoli, Orintia". I don't know details of your policy about moving pages/fixing links... Here the original warning into itwikisource scriptorium. Alex brollo (talk) 09:42, 16 February 2026 (UTC)Reply

I find that's an original mistake into the source book. Here her wikidata id: Q126367424. Alex brollo (talk) 12:11, 16 February 2026 (UTC)Reply