Jump to content

Wikisource:Scriptorium

Add topic
From Wikisource
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. If a topic seems resolved, please mark with {{subst:section resolved|1=~~~~}}.

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 643 active users here.

▼

Announcements

[edit]

The Score extension has been temporarily disabled

[edit]

More details at Enwiki Village pump (technical).

We do not have a timeline for re-enabling it yet, but a fix is in progress.

we disabled it last night after finding a thorny bug. It'll be disabled at least through the weekend until more people come online in business hours on Monday.

Practically for us at Wikisource, it seems that editing or purging a page that already has a musical score on it, or adding a new musical score, will cause the musical score to be replaced with a "Musical scores are temporarily disabled". Edderiofer (talk) 04:16, 18 October 2026 (UTC)Reply

Just copying over the update from the phabricator ticket: "We (Product Safety and Integrity) are working on the private task mentioned above and hope to have an update soon. I appreciate your patience and am sorry I can’t provide more info right now." MarkLSteadman (talk) 16:05, 28 October 2026 (UTC)Reply

November 2026 Wikimedia Café: the Newcomer homepage & Home experience

[edit]
The logo for the Wikimedia Café

The Wikimedia Foundation's Contributor teams are migrating the Newcomer homepage to a new experience called Home. This page will evolve with users, introducing them to new personalized opportunities based on their interests, and helping them develop into experienced contributors.

In November 21–22 sessions of the Wikimedia Café, Kirsten Stoller (senior product manager, Growth) and Sam Walton (senior product manager, Moderator Tools) will share an overview of this feature, plans for its future, and demos of interactive prototypes which we can explore together.

A quote which I hope will inspire your attendance or at least good wishes, from Grace Hopper: "The most important thing I've accomplished, other than building the compiler, is training young people. They come to me, you know, and say, 'Do you think we can do this?' I say, 'Try it.' And I back 'em up. They need that. I keep track of them as they get older and I stir 'em up at intervals so they don't forget to take chances."

This month's schedule:

  • Session A: 21 November at 16:00 UTC (timestamp converter), at a time friendly to the Americas, Africa, and Europe
  • Session B: 22 November at 04:00 UTC (timestamp converter), at a time friendly to Asia and the Pacific

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

Attendees of the Café are encouraged to bring a favorite beverage. (In the eternal words of Captain Picard, "Tea, Earl Grey, hot.")

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

cropped image of colored pencils

༄ᨒ𖠰 Pine (✉) 23:51, 11 November 2026 (UTC)Reply

Proposals

[edit]

Allowing IP users to mark pages proofread

[edit]

I again find myself thinking it would be useful if IP users could mark pages proofread, problematic and/or without text, in the latter case without automatic page clearing functionality. My main arguments for this change are along the lines of: Wikisource edits are primarily on a good faith basis, enough IP editors provide proofread quality edits for this to change to be valuable (to me at least), and enough users with accounts make edits which are well below proofread quality, but mark the pages proofread anyway, so do not feel the solution is to convince all users to make accounts. P.S. For completeness, I floated this idea a while back Wikisource:Scriptorium/Archives/2024-09 (item 34), I believe with an interim solution of an admin granting temporary proofreading status for individual IP users, but that hasn't happened for a while... [and the solution from 2022-2024ish was bot requests, which were eventually stymied by having to check which pages were without text, and bot requests is very quiet these days]. At any rate, hoping for a more permanent solution. Thanks for your consideration, TeysaKarlov (talk) 20:41, 27 October 2026 (UTC)Reply

IP addresses or temporary accounts ? Are you proposing reverting from temporary accounts back to IP addresses in addition and going back to things like block-based IP bans etc.? MarkLSteadman (talk) 21:43, 27 October 2026 (UTC)Reply
The difference is that temporary accounts (e.g. ~2026-12345-6) are meant to be tied to a device and hide the IP address (which might contain sensitive information, e.g. 123.456.7.8) which gets deleted, so things like communication with the user that exposes their IP address is frowned upon as opposed to communication with their temporary account (so e.g. reaching out with a question or feedback). As indicated, with the creation and rollout of temporary accounts the environment has shifted somewhat as opposed to 2022-2024. MarkLSteadman (talk) 22:35, 27 October 2026 (UTC)Reply
@MarkLSteadman Sorry for any confusion (in my head, IP users and temporary accounts were one and the same, and I am not suggesting any sort of reversion to an IP based system). Thus, consider it a proposal for temporary accounts, or anything covering "users who are not logged in", if things change in the future. Regards, TeysaKarlov (talk) 01:41, 28 October 2026 (UTC)Reply
@TeysaKarlov Understood, just wanted to avoid potential confusion. Per there are four different types of users that in principle could be checked: IP Users, Temporary Users, Permanent Users, Users who have an account, with different code implementations, see also highlighting the differences between IP Users vs. Temporary Users. As said, I think it is definitely worth discussing after the temporary account changes. MarkLSteadman (talk) 01:58, 28 October 2026 (UTC)Reply
One thing I will mention, we have seen that getting works that have been match-and-split or for other reasons are red / not-proofread to proofread is a challenge, even if they are in reasonable good shape. That leaves works contributed by anonymous / temporary lingering around for a long time.... MarkLSteadman (talk) 03:02, 1 November 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

Uploaded as a higher quality replacement for Index:Geometrical considerations and nomenclature for reflectance.pdf

However IA-upload decided to misalign the text layer by one page due to calibration pages being included in the scans, It was not possible to determine this would happen during the upload process via IA-upload.

Can SOMEONE ELSE, build a good version from both files? Thanks . If the tools are going to be un-coperative, I will be making upload requests directly at Scan Requests or here, rather than attempting to work with 'glitching' tools. Thanks. ShakespeareFan00 (talk) 10:01, 20 October 2026 (UTC)Reply

@ShakespeareFan00: Done. The cache is not yet consistent for me (after page 52). • M-le-mot-dit (talk) 12:59, 20 October 2026 (UTC)Reply
Still doesn't look right to me. I'll leave it , and then suggest someone else sits down very carefully and figures out which version is good. ShakespeareFan00 (talk) 13:12, 20 October 2026 (UTC)Reply

Looks good -

Please migrate pages from - Index:Geometrical considerations and nomenclature for reflectance.pdf to Index:Geometrical considerations and nomenclature for reflectance (IA geometricalconsi160nico).djvu and delete the PDF based index. Thanks. ShakespeareFan00 (talk) 16:47, 21 October 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) 08:52, 2 November 2026 (UTC)Reply

Please move to Index:Intelligence Services Act 1994 (UKPGA 1994-13 qp).pdf. I've already request move on commons in order to disambiguate with the south african act with the same name. ToxicPea (talk) 17:38, 25 October 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) 08:52, 2 November 2026 (UTC)Reply

Needs to be moved to Index:Executive Order 13971.pdf to match commons. ToxicPea (talk) 04:17, 29 October 2026 (UTC)Reply

Done MarkLSteadman (talk) 16:02, 29 October 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) 08:52, 2 November 2026 (UTC)Reply

Index:California Digital Library (IA brahmanstheistsm00omaniala).pdf needs to get moved to match its renamed file File:The Brahmans, theists and Muslims of India (IA brahmanstheistsm00omaniala).pdf. Eievie (talk) 17:28, 10 November 2026 (UTC)Reply

Other discussions

[edit]

Chapter titles in The Story of My Experiments With Truth

[edit]

The chapter titles of the two volumes are formatted the same but are transcribed differently Volume 1 uses {{asc}} and Volume 2 uses {{smaller}}. Could we have someone change one of them for consistency? ToxicPea (talk) 06:38, 10 October 2026 (UTC)Reply

Isn't the result exactly the same? If yes, why would it matter? Yann (talk) 15:40, 10 October 2026 (UTC)Reply
{{smaller}} is bigger than {{asc}}. It's {{x-smaller}} that the size of {{asc}} is equivalent to. ToxicPea (talk) 15:44, 10 October 2026 (UTC)Reply
It's not a huge difference, but {{asc}} does also squash the capital letters a bit (a vs. A vs. A), and copies as a lower-case letter, rather than a capital. --YodinT 16:26, 10 October 2026 (UTC)Reply
OK. So what should be chosen: {{asc}} or {{smaller}}? The later is more work, as all titles have to be changed to capitals. Yann (talk) 19:05, 10 October 2026 (UTC)Reply
All the titles are already capitals anyway so it doesn't matter. ToxicPea (talk) 19:12, 10 October 2026 (UTC)Reply
The book looks like it's using small caps to me rather than a smaller font size. --YodinT 11:04, 11 October 2026 (UTC)Reply
OK, I will fix that with {{asc}}. Yann (talk) 18:35, 11 October 2026 (UTC)Reply
Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. Yann (talk) 20:58, 21 October 2026 (UTC)Reply

<ref follow=""></ref> is behaving like a normal footnote in page namespace

[edit]

I'm finding that footnotes within <ref follow="pxxx"></ref> now have inline links in page namespace. See for example this page:

Page:The Dissertations of Maximus Tyrius - Vol I & II.djvu/205

The footnote which is a continuation from the previous page now has a [2] superscript link, and it's listed as footnote 2 on the page. Pasicles (talk) 13:00, 12 October 2026 (UTC)Reply

This is another Parsoid issue (the footnote works as expected if you use the "Switch to legacy parser" link in the Tools menu). TE(æ)A,ea reported this here a couple of days ago, as well as some other Parsoid-related issues a bit over a week ago, but there doesn't seem to be a reply from the Parsoid team yet. --YodinT 13:14, 12 October 2026 (UTC)Reply

Footnote quirk inside Ppoem

[edit]

If you use '+>' at the beginning of a line that immediately follows a line with a footnote in it, the footnote appears twice in Page space (it also does so when the page is transcluded). As an example, if you replace {{hidden text|Him with his legions.}} with '+>' on Page:The Poetical Works of Samuel Rogers (1892, revised Aldine edition).djvu/240, you should hopefully see the effect. It seems to occur regardless of where the footnote is within the line. Chrisguise (talk) 14:38, 12 October 2026 (UTC)Reply

Should be fixed? Normally references are removed now. — Alien  3
3 3
17:32, 18 October 2026 (UTC)Reply
Does seem to be OK. Thanks. Chrisguise (talk) 22:06, 18 October 2026 (UTC)Reply

Tech News: 2026-42

[edit]

MediaWiki message delivery 07:39, 13 October 2026 (UTC)Reply

Possible spammer

[edit]

User:~2026-55430-53 is creating non-transcluded, unsourced pages (Sokoli Tomari Iccha, Bengali Religious Lyrics, Śākta (1923)) and also removing the {{no source}} template when it's rightly added. (). I think this may be a spammer. Eievie (talk) 01:10, 16 October 2026 (UTC)Reply

They don't look like a spammer to me. More like a new user who doesn't understand the way things should be done here. -- Beardo (talk) 02:53, 16 October 2026 (UTC)Reply

Monthly Challenge (no expiry)

[edit]

Hi, I notice that some works have been in this section for ages without change. I wonder what is the point to keep them if nobody seems to be interested. Since January 2026: The Book of the Thousand Nights and a Night (volume 1), History of Greece (Volume 2), National Geographic (Volume 2). Opinions? Yann (talk) 15:05, 17 October 2026 (UTC)Reply

@Yann Technically not nobody, as volume 1's for two of those series were finished. But if there remains no interest at present, then happy to remove them come November. Regards, TeysaKarlov (talk) 20:07, 17 October 2026 (UTC)Reply
OK, I replaced these 3 with other works in the waiting list. Hopefully these will bring more activity. Yann (talk) 19:33, 25 October 2026 (UTC)Reply
@Yann You forgot to replace them in the monthly challenge as well. ToxicPea (talk) 00:39, 1 November 2026 (UTC)Reply
@ToxicPea: Hi, I have followed TeysaKarlov above, suggesting to remove them in November. Yann (talk) 02:18, 1 November 2026 (UTC)Reply
I'm looking at the monthly challenge for November and I'm still seeing the 3 works that were supposedly removed. ToxicPea (talk) 02:24, 1 November 2026 (UTC)Reply
OK, fixed. Yann (talk) 02:47, 1 November 2026 (UTC)Reply
[edit]
The logo for the Wikimedia Café

Hello! There will be two Wikimedia Café discussion opportunities in October. In a change from the usual Café practice, this month's sessions will have different topics. Anyone who meets the Café attendance criteria is welcome to attend either or both sessions.

Session A will happen on Saturday, 24 October 2026 at 15:00 UTC (timestamp converter), at a time friendly to the Americas, Africa, and Europe. This session will feature Wikimedia Foundation lawyer Phil Bradley-Schmieg. We will discuss legal issues on Wikimedia Commons, including complexities of international law. (I am hoping that in a future month, a similar Café session will be offered at a time friendly to Asia and the Pacific.)

Session B will happen on Sunday, 25 October 2026 at 03:00 UTC (timestamp converter), at a time friendly to Asia and the Pacific, we will discuss proposed changes to how Wikimedia Foundation Board candidates are selected. The latest proposals are much different from the earlier July 2026 proposals. The due date for feedback on current proposals is 27 October, and Wikimedians are welcome to participate on the proposal talk page regardless of Café attendance.

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

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

cropped image of colored pencils

༄ᨒ𖠰 Pine (✉) 06:23, 18 October 2026 (UTC)Reply

Musical scores are temporarily disabled

[edit]

Is there some reason that musical scores have been disabled sitewide? See, e.g., "Daisy Bell", "The Entertainer", "Transit of Venus" --EncycloPetey (talk) 13:34, 18 October 2026 (UTC)Reply

See "The Score extension has been temporarily disabled" in the Announcements section above. -- Beardo (talk) 14:07, 18 October 2026 (UTC)Reply
Apparently it is possible to change the Musical scores are temporarily disabled. message to add a link to the Phabricator issue, by editing MediaWiki:Score-exec-disabled (cf. w:MediaWiki:Score-exec-disabled on English Wikipedia). However, it seems that an admin has to do it. Edderiofer (talk) 05:28, 6 November 2026 (UTC)Reply

A discussion was started regarding the name of this page on User talk:Jan.Kamenicek. We have agreed to move this discussion to the Scriptorium. The contents of the discussion up to now are as follows.

I have no idea why you decided to move the ordinance’s title to the long title, especially it contains a citable, official short title. The move is also contrary to the previous practice for other Commonwealth legislation. Can you please explain?廣九直通車 (talk) 05:16, 14 October 2026 (UTC)

@廣九直通車: Hello. I moved it because the actual name of the document used by its authors is An Ordinance to provide enhanced punishments for the offences of abduction and criminal intimidation in certain circumstances, see its first page. In Wikisource we always use the original titles. Will you move it back, please? If you know of any other documents which were not named here by their original titles, and if you point them out, I can rename them too. --Jan Kameníček (talk) 21:02, 14 October 2026 (UTC)
And please also see section 1 of the Ordinance as well! If you don’t know, in most common law jurisdictions, primary legislation has two titles: the long title (e.g. An Ordinance to provide enhanced punishments for the offences of abduction and criminal intimidation in certain circumstances) and short title (e.g. Abduction, and Criminal Intimidation of Witnesses Ordinance, 1947). Both are official titles, though the short title is the title most commonly used. If you look at other legislation, you will also find they are named after their short title.廣九直通車 (talk) 23:37, 14 October 2026 (UTC)
There is two another problems if you use the long title as the title on Wikisource: (1) long titles tend to be very long, and some recent legislation can have over 100 words in the long title (let alone some with extraordinarily long ones like the Criminal Justice Act 1988): remember wikis only allow 255 bytes at page titles; and (2) long titles can be identical, especially for amending legislation; while for short titles, they are meant to be unique identifiers within the jurisdiction.廣九直通車 (talk) 05:34, 15 October 2026 (UTC)
@廣九直通車: I think the misunderstanding is that you are confusing the common name of a work with the title of a specific edition. While a work can be known by various names, an edition has one specific title (sometimes accompanied by a subtitle), which is usually printed on the first page. On Wikisource, we have version pages, which are connected to the work and contain links to its editions, and mainspace pages, which contain the texts of specific editions. The page we are discussing contains the text of a specific edition and should therefore be titled according to the title under which that edition was originally published. The title Abduction, and Criminal Intimidation of Witnesses Ordinance, 1947 does not appear anywhere in this edition. The actual title can be found on its first page. --Jan Kameníček (talk) 09:18, 17 October 2026 (UTC)
The title is Abduction, and Criminal Intimidation of Witnesses Ordinance, 1947 is literally in the first paragraph. It states “This Ordinance may be cited as the Abduction, and Criminal Intimidation of Witnesses, Ordinance, 1947, and shall come into force on the 10th day of June, 1947.” ToxicPea (talk) 07:52, 18 October 2026 (UTC)
Well, it is not really the title of the edition, which is only one. It is a shortened version of the title which "may" be used for citation, it is not the full title. --Jan Kameníček (talk) 10:33, 18 October 2026 (UTC)
From a legal standpoint that’s a distinction without a difference. The short title is not just a nickname, it has legal significance. For all intents and purposes the short title and the long title are both equally valid as titles. ToxicPea (talk) 16:46, 18 October 2026 (UTC)
Quite possibly. That is why it is fine to use it in citations. But it is still a short version of the title, not the full title. --Jan Kameníček (talk) 16:48, 18 October 2026 (UTC)
Legally that’s not a difference. If an act says “This Act may be cited as X” that is legally the same as saying, “X is the title of this Act”. The short title is not just a short version of the long title. It is legally another separate full title that is equally as valid as the long title.
This is not some ordinary book with multiple editions. This is an act with the force of law. Those of us who work on law related works use slightly different conventions on law related works than on regular works because law is different to other works and should be treated differently. No one has had a problem with this until now. ToxicPea (talk) 17:02, 18 October 2026 (UTC)
Is it okay if I move this discussion to WS:S? ToxicPea (talk) 17:17, 18 October 2026 (UTC)
Of course, a good idea. --Jan Kameníček (talk) 17:30, 18 October 2026 (UTC)

I would also like to ping @Penguin1737: and @DraftSaturn15:. They also work on legislation and may want to comment on this. ToxicPea (talk) 17:35, 18 October 2026 (UTC)Reply

Personally having categories full of An Ordinance to provide ... and An Act to ... so all legislation are grouped under A for act makes them less valuable. An Act To authorize appropriations for fiscal year 2012 all grouped under A for Act is instead of looking for it under National Defense Authorization Act for Fiscal Year 2012, nevermind An Act To provide for reconciliation pursuant to title II of S. Con. Res 14. for the Inflation Reduction Act and An Act To provide for reconciliation pursuant to title II of H. Con. Res. 14. for the One Beautiful Bill is even more obscure and unhelpful. MarkLSteadman (talk) 18:06, 18 October 2026 (UTC)Reply
Are page after page of An Act to provide for, An Act to authorize in categories and portals in any situation better than being able to click on N to skip ahead to to National Defense...? MarkLSteadman (talk) 18:11, 18 October 2026 (UTC)Reply
I am of the opinion that the short title should be used as the mainspace page title where it is provided for by the legislation. The short title is the most commonly used form to cite Acts, Ordinances, etc, as 廣九直通車 pointed out in the original talk page. Almost all legislation that has been drafted in the 20th century to present will have short titles. I am going to use a few Australian examples as that is what I am most familiar with but a lot of common law and Commonwealth [of Nations] countries use very similar conventions.
Of course, the Acts Interpretation Act 1901 (Cth) does not apply to us but it can be a guide that we follow when determining procedure such as how to title works. Acts may be cited by the short title, secular year and number, and its Federal Register of Legislation ID (Acts Interpretation Act 1901 (Cth), s 40(1A)(a)). It does not provide for the citing using long titles of Acts. The provision uses the word "may" but that would be to allow for some flexibility but I have not seen any examples of the long title being used in modern legislation. No modern drafter would ever use the long title of an act when drafting legislation. This was not the case in the past before short titles were invented when acts would have been cited in a very long-winded way as "an Act of Council made and passed the 8th day of February in the Year of our Lord one thousand eight hundred and twenty-five intituled 'An Act to regulate of licenses for the Sale of Spirits Ale Beer and other Liquors in New South Wales and Van Diemen's respectively'" (Fines and Penalties Recovery Act 1825 (NSW)) or by the regnal citation.
The Australian Guide to Legal Citation is used by academia (as far as I see, no Australian courts use this style) as the primary referencing style for law. Rule 3.1.1 states that the short title should be used and that the long title should only be used if there is not short title (Australian Guide to Legal Citation 4th ed, p 67). A similar provision appears in Oxford University Standard for Citation of Legal Authorities 5th ed at page 25. In Hong Kong, the short title gives the ordinance its name (Drafting Legislation in Hong Kong, p 11, item 2.2.2). The Federal Court of Australia practice note Lists of Authorities and Citations Practice Note (GPN-AUTH), states in the Annexure that the long title should only be used if there is not sort title; for reference a practice note sets out procedure for lawyers and parties to follow. The only times I have seen judges use long titles are to give further context relating to the Act itself: Hoxton Park Residents Action Group Inc v Liverpool City Council [2016] NSWCA 157 at [27]; Doyle’s Farm Produce Pty Ltd atf Claredale Family Trust v Murray-Darling Basin Authority [2026] NSWSC 1036 at [201]; Australian Securities and Investments Commission v Auto & General Insurance Company Limited [2025] FCAFC 76 at [40]; Davey on behalf of the Gudanji, Yanyuwa and Yanyuwa-Marra Peoples v Northern Territory of Australia (No 5) (McArthur River Project Compensation Claim) [2026] FCA 153 at [163].
Practically, if a person is going to search for legislation, the short title will come to mind. For example if someone wants to search for their workplace rights, that person will search for "Fair Work" or "Fair Work Act", not "An Act relating to workplace relations, and for related purposes". While long titles in other jurisdictions like the United Kingdom might be very long, such as the Criminal Justice Act 1988 (UK), Australian legislation has been using shorter and more generic long titles (Office of Parliamentary Council Drafting Direction 1.1 at [1]). The short title also includes the year the legislation was enacted which is useful to know at an instant.
For example, the following acts all have the same long title of "An Act to amend the Fair Work Act 2009, and for related/other purposes", the short titles are more descriptive, practical, and sortable (as MarkLSteadman said):
  • Fair Work Amendment (State Referrals and Other Measures) Act 2009
  • Fair Work Amendment (Textile, Clothing and Footwear Industry) Act 2012
  • Fair Work Amendment Act 2015
  • Fair Work Amendment (Respect for Emergency Services Volunteers) Act 2016
  • Fair Work Amendment (Protecting Vulnerable Workers) Act 2017
  • Fair Work Amendment (Corrupting Benefits) Act 2017
  • Fair Work Amendment (Supporting Australia’s Jobs and Economic Recovery) Act 2021
  • Fair Work Amendment (Baby Priya’s) Act 2025
  • Fair Work Amendment (Fairer Fuel) Act 2026
I agree that having categories and portals with entries that have "An Act to … and for related purposes" looks cluttered and inelegant.
Wikisource is a library. One of the goals for libraries is quick and intuitive access to resources for everyone. As I have stated earlier, almost no-body uses the long title to search for or to refer to a specific piece of legislation (I do not have data for actual usage but based on the practice of legislative drafters, academia, and the judiciary), so I believe it would be counter-productive for Wikisource as a library to have the long title be the main title. —DraftSaturn15 (talk) 05:14, 19 October 2026 (UTC)Reply
I believe we should prefer full titles to shortened titles whenever possible. This specific edition is titled in some way at the top of the page, and only then inside the text a shortened version of the title is suggested for the purpose of citations, but that is imo no reason why it should be used for the page name. Our common practice is full titles. —unsigned comment by Jan.Kamenicek (talk) 21:53, 18 October 2026.
I don't believe our common practice is full titles: e.g. A General History of the Pyrates, whose full title as used on A General History of the Pyrates/Volume 1 is at the very least "A General History of the Pyrates, from Their first Rise and Settlement in the Island of Providence, to the present Time." (Also cf. A General History of the Pyrates/Volume 2, which just calls itself "A History of the Pyrates, ..." on the title page. In the case of these laws, I see no reason to use the long title.--Prosfilaes (talk) 01:26, 20 October 2026 (UTC)Reply
It's Hamlet (Shakespeare) not The Tragicall Historie of Hamlet Prince of Denmarke, Twelfth Night (Shakespeare) not Twelfe Night, Or what you will it's King James Version not THE HOLY BIBLE, Conteyning the Old Teſtament, AND THE NEW: Newly Tranſlated out of the Originall tongues: & with former Tranſlations diligently compared and reuiſed, by his Majesties ſpeciall Comandement, it's Utopia (More) not A truly golden little book, not less beneficial than enjoyable, about how things should be in a state and about the new island Utopia etc. We certainly aren't consistent currently... MarkLSteadman (talk) 02:05, 20 October 2026 (UTC)Reply
Another example An Essay on the Principle of Population vs. An Essay on the Principle of Population as It Affects the Future Improvement of Society, with Remarks on the Speculations of Mr. Godwin, M. Condorcet, and Other Writers MarkLSteadman (talk) 02:13, 20 October 2026 (UTC)Reply
In almost all of the examples mentioned above, I am afraid version pages for works (where one title must be chosen to encompass multiple editions of different titles) are confused with titles of specific editions. However, it is the titles of editions that we are discussing here. Your point could therefore probably be better illustrated by Hamlet (1917) Yale, which is not titled The Tragedy of Hamlet, Prince of Denmark for some reason, although I believe it should be.
In the last example, “An Essay on the Principle ... M. Condorcet, and Other Writers”, you also included the subtitle, which nobody is suggesting. The full title would simply be An Essay on the Principle of Population as It Affects the Future Improvement of Society, and that is what I consider appropriate.
A General History of the Pyrates is an interesting example, since the continuation “From Their first Rise...” is separated from the main title only by a comma, but is printed in a significantly smaller font. It is therefore somewhere on the borderline between being part of the title and being a subtitle, so leaving it out makes sense.
There will always be special cases that can be dealt with individually when there is a good reason to do so—for example, when a title extends over several screen widths. In general, though, I think we should prefer the full original titles. --Jan Kameníček (talk) 20:52, 20 October 2026 (UTC)Reply
Even if you look at editions: Shakespeare - First Folio facsimile (1910)/The Tragedy of Hamlet, Shakespeare - First Folio facsimile (1910)/Twelfe Night, Bible (King James Version, 1611), even ignoring Utopia which is unsourced. My point still stands that we haven't been consistent about using full titles. MarkLSteadman (talk) 22:45, 20 October 2026 (UTC)Reply
Not only are not consistent about using full titles, I can find no such policy that would imply that full titles are preferred. I also have no idea what benefit there would be to such a policy. ToxicPea (talk) 23:37, 20 October 2026 (UTC)Reply
This moving pages from a short version of a title to the full version has happened before. A user changed the title of Executive Order 13971 to Executive Order on Addressing the Threat Posed by Applications and Other Software Developed or Controlled by Chinese Companies. This was raised and debated in the Scriptorium and the consensus appears to be that Executive Order ##### should be the page title and not the full name. That is reflected in WikiProject United States Executive Orders where the titling is codified as Executive Order #####. —DraftSaturn15 (talk) 00:15, 21 October 2026 (UTC)Reply
Speaking of which, would appreciate if someone could go through all of Joe Biden's orders on Author:Joseph Robinette Biden/Executive orders and move those to Executive Order ##### ToxicPea (talk) 00:24, 21 October 2026 (UTC)Reply

Oppose using long titles, where Short title exists

[edit]
Having set up extensive templates to handle short titles for English Acts (which can run to 5 or more lines if you quote the full title), using the short title i simply more convenient. ShakespeareFan00 (talk) 22:12, 18 October 2026 (UTC)Reply
Not sure why your opposition needs a specific heading Well, some titles can be too long to handle, but this one is within common WS limits (far from "5 or more lines"), there are many much longer titles in Wikisource. That is why I wrote "whenever possible". When the original edition prefers the full title at the top and only somewhere in the text suggests a shortened version for a specific purpose (citation), we should be faithful to the original and prefer the full title. --Jan Kameníček (talk) 22:23, 18 October 2026 (UTC)Reply
As you seem to determined to push for long titles, I'll start removing my templated approach, so you are not obstructed. ShakespeareFan00 (talk) 22:26, 18 October 2026 (UTC)Reply
??? --Jan Kameníček (talk) 22:29, 18 October 2026 (UTC)Reply
Module behind : {{Short-title}} has had link generation removed until there is a clear strategy for linking, and all items transrcribed or linked under their short titles are placed at what you consider to be their "appropriate" titles. It also conveniently solves the template expansion limits that were being hit on a number of items I'd worked on extensively. Reach your decision and I can start manually updating every single table entry in the Short Titles Act 1896, In the tables at the start of Ruffhead, and so on. We want Wikisource to use the "correct" titles of course. ShakespeareFan00 (talk) 22:35, 18 October 2026 (UTC)Reply
Also the module as currently written only works for English/United Kingdom acts, and doesn't take into account other jurisdictions which follow British practice, or develolved assemblies. I am slowly deprecating it to allow for an overhaul. ShakespeareFan00 (talk) 06:56, 19 October 2026 (UTC)Reply

Tech News: 2026-43

[edit]

MediaWiki message delivery 14:38, 19 October 2026 (UTC)Reply

Spammer

[edit]

@~2026-56028-00 is spam editing. Can we get a block? Eievie (talk) 04:15, 21 October 2026 (UTC)Reply

Rollbacked, but only 6 edits and quickly stopped activity so doesn't warrant a block as of now. — Alien  3
3 3
08:58, 21 October 2026 (UTC)Reply
Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. -- Beardo (talk) 18:36, 6 November 2026 (UTC)Reply

Validation request

[edit]

I am asking for a validation of https://en.wikisource.org/wiki/Index:Glaucus,_or,_The_wonders_of_the_shore_(IA_glaucusorwonders00kings).pdf. Pages 1-178 out of roughly 240 pages are ready for validation.

Thank you! QuarrySparrow (talk) 09:19, 21 October 2026 (UTC)Reply

OCR tool not working

[edit]

Don't know if anyone else is having this issue, but the OCR tool hasn't been working for me all day. All three 'engines' return 'No text was returned by the OCR tool'. Chrisguise (talk) 14:52, 21 October 2026 (UTC)Reply

It would not surprise me as there is major security work going on: https://diff.wikimedia.org/2026/10/21/impact-of-php-vulnerabilities-on-wikimedia-tools-and-services/ 15:32, 21 October 2026 (UTC) MarkLSteadman (talk) 15:32, 21 October 2026 (UTC)Reply
See where it lists Cloud VPS as offline. MarkLSteadman (talk) 22:09, 21 October 2026 (UTC)Reply
Thanks. Chrisguise (talk) 04:13, 22 October 2026 (UTC)Reply
Just wanted to mention that services (but not OCR, it uses php) have started to be restored if you look at the page. Thanks to anyone reading this who has been working to keep Wikisource safe and restoring functionality. MarkLSteadman (talk) 05:04, 23 October 2026 (UTC)Reply
Note that there is a ticket here: https://phabricator.wikimedia.org/T442082 to make OCR a production service instead of depending on cloud VPS. MarkLSteadman (talk) 19:51, 23 October 2026 (UTC)Reply

I have created the task T442268. --Jan Kameníček (talk) 11:45, 24 October 2026 (UTC)Reply

Thanks for the work you (Mark and others) have already done. Can we do anything more at this moment, to accelerate the repair process? --Dick Bos (talk) 16:25, 25 October 2026 (UTC)Reply

It's running again! Thanks. --Dick Bos (talk) 19:37, 26 October 2026 (UTC)Reply

It looks like book export and ia upload are up as well. MarkLSteadman (talk) 20:20, 26 October 2026 (UTC)Reply

FYI: How a 139-year-old family document led to my first Wikisource edit

[edit]

https://diff.wikimedia.org/2026/10/22/how-a-139-year-old-family-document-led-to-my-first-wikisource-edit/ ―Justin (koavf)❤T☮C☺M☯ 16:12, 22 October 2026 (UTC)Reply

Server switch - Your wiki will be read-only for a short time soon

[edit]

Trizek_(WMF) 14:00, 26 October 2026 (UTC)Reply

Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. -- Beardo (talk) 18:38, 6 November 2026 (UTC)Reply

Tech News: 2026-44

[edit]

MediaWiki message delivery 18:56, 26 October 2026 (UTC)Reply

Category:Texts with missing images

[edit]

Hi, I have noticed that Category:Texts with missing images doesn't appear too be clearing entries that I have added the missing images for. In some cases I added images a week or so ago. Is this a current known problem? Sp1nd01 (talk) 15:27, 28 October 2026 (UTC)Reply

I was able to fix an example by doing a hard purge on the linked Main space page. I am not sure why the Page --> Main --> Category update didn't propagate. MarkLSteadman (talk) 15:46, 28 October 2026 (UTC)Reply
Thanks, I'd not tried that, I was hard purging at the Category level. They are now clearing when I do that. Sp1nd01 (talk) 17:35, 28 October 2026 (UTC)Reply
If you see continue to seem them not update properly it might be good surfacing, they should fix themselves without intervention too, just might take a bit longer. MarkLSteadman (talk) 21:14, 29 October 2026 (UTC)Reply

Help with images

[edit]

Hi, Index:Three Years in Tibet.djvu has been proofread. There are great many images to be added. Please help. Thanks, Yann (talk) 20:31, 29 October 2026 (UTC)Reply

All the pages are marked as "Proofread". When that happens, people assume that the images are also done, because that's what a "Proofread" status means: that the page is ready for transclusion. Pages where images are missing ought to be marked as "Problematic" so that editors know additional work is needed. See Help:Page status. --EncycloPetey (talk) 13:54, 6 November 2026 (UTC)Reply
Someone did help. Yann (talk) 14:41, 6 November 2026 (UTC)Reply
Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. Yann (talk) 14:41, 6 November 2026 (UTC)Reply

book2scroll - reader

[edit]

I don't think it's been mentioned here yet, but User:Magnus Manske recently updated his "book2scroll" reading tool for Wikisource. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:27, 30 October 2026 (UTC)Reply

It doesn't seem to work currently. Nighfidelity (talk) 23:05, 3 November 2026 (UTC)Reply
Working for me, right now. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:22, 4 November 2026 (UTC)Reply

The Works of Michel de Montaigne

[edit]

Hi, I have uploaded the 10 volumes scan from HathiTrust (Index:Works of Michael de Montaigne, ed. Emerson, E. C. Hill, 1910, vol. 1.pdf), and User:JoanSevier has uploaded one volume of another scan from Internet Archive (Index:The Works of Michel de Montaigne, ed. Emerson, E. C. Hill, 1910, vol. 1.pdf). I think the higher resolution copy should be use. Opinions? Yann (talk) 20:43, 1 November 2026 (UTC)Reply

Hi! My rationale was just consistency with the texts that were uploaded at the time. If the HathiTrust copies were uploaded previously, I did not see them, because they title is misnamed: the 1910 edition uses "Michel de Montaigne," not "Michael de Montaigne," which may be why I missed them. I'm not sure resolution, after a certain point, justifies transferring existing transcriptions of an index page to a new index page, though if there is policy on this I happily defer! JoanSevier (talk) 20:47, 1 November 2026 (UTC)Reply
I don't really see the point, since this is just virtually all text and if there are any graphics, you can just include a crop of the best graphics (or recreate them as vectors). As long as the contents are actually the same, a 58 MB PDF and a 478 MB DJVU are equally sufficient. There's something nice about the consistency of having one set of scans or of having particularly hi quality, but it's really irrelevant ultimately. ―Justin (koavf)❤T☮C☺M☯ 21:38, 1 November 2026 (UTC)Reply
OK, but the indexes should have the same name: now the first is Index:The Works of Michel de Montaigne, ed. Emerson, E. C. Hill, 1910, vol. 1.pdf, and the others are Index:The works of Michel de Montaigne (IA worksofmicheldem02montiala).pdf, etc. Yann (talk) 14:58, 2 November 2026 (UTC)Reply
I don't see that as necessary - as long as the transcluded texts in Main space are consistent. -- Beardo (talk) 15:16, 2 November 2026 (UTC)Reply
No, there isn't any need of that, and the person transcribing uses whatever index they want. — Alien  3
3 3
06:39, 3 November 2026 (UTC)Reply
Thanks for the feedback. Yann (talk) 14:44, 6 November 2026 (UTC)Reply
Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. Yann (talk) 14:44, 6 November 2026 (UTC)Reply

Collaboration on Main Page not visible in mobile

[edit]

It has a enws-hide-on-mobile. (The sister projects box also has one, but that I can understand.)

Anyone know why? Showing potm etc is IMO a good thing to do even in mobile, and {{collaboration}} looks pretty mobile-friendly to me. — Alien  3
3 3
06:41, 3 November 2026 (UTC)Reply

Tech News: 2026-45

[edit]

MediaWiki message delivery 14:23, 3 November 2026 (UTC)Reply

Managing page breaks across "multicol" template

[edit]

I have used the {{Template:Multicol}} for these two pages page 45 and page 46 as the English translation is the left column while the Malay paragraph is on the right column. The first half of the left column and the first half of the right column are on the previous page, while the second half of the left column and the second half of the right column are on the second page. I struggled to stitch both columns together when transcluding the pages as shown here: between page 33 and page 34. Anything else I could do to solve this problem? Cerevisae (talk) 22:49, 4 November 2026 (UTC)Reply

  • The problem of cross-page tables is very difficult to solve. I faced it recently, and came up with the following solution. (See first page, second page, and transclusion.)
    1. The section with the side-by-side columns should be transcluded separately (with a separate <pages /> tag).
    2. Every page in the section, even those without cross-page tables, should begin with ##main##.
    3. The first page, where the paragraph starts to run over the page, should be transcluded mostly as normal. For items in the last row, there should be added <includeonly>{{#lst:[1]|c[2]}}</includeonly>, where “[1]” is the next page and “[2]” is the number of the column.
    4. On the second page, where the paragraph runs over, the formatting is rather complicated; just copy it directly from here.
    5. Finally, when the section is transcluded, add onlysection=main in the code of the transclusion.
  • Feel free to ask me any other questions. TE(æ)A,ea. (talk) 23:37, 4 November 2026 (UTC)Reply

Spammer

[edit]

@~2026-58720-87 is a spammer and needs a ban. Eievie (talk) 01:19, 6 November 2026 (UTC)Reply

Blocked by Prosfilaes. Yann (talk) 14:41, 6 November 2026 (UTC)Reply
Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. Yann (talk) 14:41, 6 November 2026 (UTC)Reply

Sort order on Category:Indexes validated in November 2026

[edit]

I have just noticed that the sort order on this page isn't correct. I presumed it would take notice of the contents of the 'sort order' field on the index page, but the entries under 'A' and 'T' seem to suggest otherwise. Chrisguise (talk) 14:19, 7 November 2026 (UTC)Reply

Bug in footnotes

[edit]

Hello all, I am having an issue with this and a few other footnotes that are in Thelyphthora, Volume 3, Chapter 13 (screenshot included of the one on this page). Is there any reason why it's appearing justified like this, that I can easily fix? Thanks, -- Erblanchard57 (talk) 19:08, 8 November 2026 (UTC)Reply

@Erblanchard57 On my end, in both page and mainspace (all layouts), the footnote isn't justified like that. So not sure what to suggest. Just in case though, I have removed the (unnecessary) line break ahead of each {{pbr}}, in case these were the problem. Regards, TeysaKarlov (talk) 20:11, 8 November 2026 (UTC)Reply
I do not see it justified either. --Jan Kameníček (talk) 20:25, 8 November 2026 (UTC)Reply
Me three. ―Justin (koavf)❤T☮C☺M☯ 20:51, 8 November 2026 (UTC)Reply
I did just check on a different web browser, and it is displaying properly on Firefox. However, it is still showing justified on Safari (I'm running macOS Golden Gate 27.2) Erblanchard57 (talk) 22:02, 8 November 2026 (UTC)Reply
I did try clearing the cache and that didn't work -- Erblanchard57 (talk) 22:03, 8 November 2026 (UTC)Reply
You might try turning off Parsoid (add "&useparsoid=0" to the URL). MarkLSteadman (talk) 01:44, 9 November 2026 (UTC)Reply
Hi, @MarkLSteadman I had to add "?&useparsoid=0" to get the url to load for me without Parsoid—but that did not fix the issue either, unfortunately. -- Erblanchard57 (talk) 03:34, 9 November 2026 (UTC)Reply
So I suspect that is because safari default CSS places a "text-align: match-parent;" on the list items, meaning it inherits a "text-align: justify;" (possibly based on your skin / display settings?). MarkLSteadman (talk) 05:24, 9 November 2026 (UTC)Reply
Hi, @MarkLSteadman, that appears to have been the issue! I added a custom style sheet with
li {
  text-align: start !important;
}
in it to Safari and that seemed to fix it. Thanks! Is this something that could be added to the MediaWiki or Wikisource common.css (I'm not sure exactly how it works) so every Safari user visiting the site doesn't have to adjust their individual browser settings? -- Erblanchard57 (talk) 06:16, 9 November 2026 (UTC)Reply
@MarkLSteadman, This page and this page which transclude at Thelyphthora/Volume 3/Chapter 12 (footnote 19) are also having an issue with the {{ppoem}} template and the "ref=follow" tag (issue happens with both {{refn}} and regular <ref> tags.
And then in the page namespace, the footnotes that have "follow" are appearing with the little number
This one does appear to be an issue with Parsoid.
Thanks -- Erblanchard57 (talk) 17:38, 9 November 2026 (UTC)Reply
The parsoid issue is tracked on phabricator ticket T398402 MarkLSteadman (talk) 17:42, 9 November 2026 (UTC)Reply

Tech News: 2026-46

[edit]

MediaWiki message delivery 10:34, 9 November 2026 (UTC)Reply

Which year for the year parameter?

[edit]

The year parameter in the header template says that it is for the 'year of publication' and it is also used to assign works to subcategories of Category:Works by year. But which 'year of publication' is meant? For example, if we are transcribing a 1921 reprinting of a 1919 edition of a 1901 book, what value goes in the year parameter? Nosferattus (talk) 06:25, 10 November 2026 (UTC)Reply

Assuming that there are no changes in the reprint, then the year of publication for this work is 1919. The 1901 edition would appear separately. Beeswaxcandle (talk) 06:41, 10 November 2026 (UTC)Reply