Wikisource:Scriptorium/Help

How to download a whole work

Hello all. I have just finished proofreading The Chronicles of Early Melbourne (if anyone felt like validating, please be my guest...) I now wish to download the entire work in pdf format so that I can do some more efficient searching within the work than is possible on Wikisource. However, when I attempt to download - whether the button in the top right hand corner in mainspace or the sidebar link, I just get 77KB of the title page, whereas I want the whole work, please! There are some cryptic remarks from @Billinghurst 7 years ago which seems to be exactly what I am experiencing, but they don't allow me to work out what I should do to rectify my situation. Alternatively, is the slightly worrying remark from @EncycloPetey back in 2019 the answer? If so, in order to have a full work epub, we have to graft the TOC into the first page? I suppose I could do this temporarily, download and revert - otherwise it's going to look awful! Thanks. CharlesSpencer (talk) 10:13, 3 March 2025 (UTC)

Having a TOC on the main page has been relatively common practice, and the {{AuxTOC}} template is there for when the chapters are not listed in the source. If the subpages are not listed on that page, I don't know how the tool is supposed to find them. — Alien  3
3 3 12:29, 3 March 2025 (UTC)

Thank you for this - I have successfully downloaded the whole work in pdf with your help, having put the ToC in the first page. If that is common practice (which I was not aware of) I will happily leave it there.

As an aside, may I say that - as a not stupid person, and a Wikisource editor of 15 years' standing with several complex templates to his name - I do think it is hugely important to be helpful to the purpose of a question rather than express surprise at someone's ignorance - sometimes, frankly, in order to demonstrate one's own superior knowledge. It is neither helpful, nor pleasant to be on the receiving end of. This was not a question born out of idleness - I had spent some time researching the Scriptorium archives, whence I cited two examples which really didn't answer my question, but were instead slightly cryptic or oblique, or based on a supposition of knowledge which the question plainly didn't support. Yet Alien's passive aggressive response is "how [else is] the tool...supposed to find them". If I knew that, why on earth would I have asked the question? A simple "Do this and this will happen", or "Sticking the ToC on the title page will give the tool the info it needs" in this case - is what this context called for. Researching further in Help:Preparing for export, I find absolutely no trace of "Put the ToC in the first page so the Tool knows what to include". Instead I find

☐ Do make sure that either:

1. ☐ Every page you want in the export is linked from the root page, or
2. ☐ Every page you want in the export is linked from a page that is linked from the root page and is inside a container with the class ws-summary (see {{AuxTOC}} or {{export TOC}})

which makes a lot of sense to someone who already knows the answer, but very little/zero to someone seeking the answer. This is unfortunate, since the title of the namespace is Help: not Oxymoron: (there - a little touch of passive aggressive intellectual superiority (considerably more in sorrow than in anger) to illustrate my point.) I shall now edit Help:Preparing for export to be more practically helpful.

Please do not think that I am not grateful for all the help that numerous people have freely given me over the decade and a half that I have been an editor - I am, and my contribution to Wikisource would be nowhere without them and their help. However, may I make a heartfelt plea to the most experienced editors who make the whole undertaking function not to be casually cutting in their responses but instead to attempt helpfully to answer all questions? It will take an extra 1% of effort, yet I believe will compound considerably to the benefit of all Wikisource participants - and crucially, will aid in the recruitment of new editors. If I were a noob and saw the cutting sort of response that my most basic of questions - "How do I download it?" - received, I would probably have given up and gone home long since. Thank you. CharlesSpencer (talk) 15:22, 14 March 2025 (UTC)

CharlesSpencer there is a similar question, due greatly to the long "helpful" speel that appears when you do this thing. That thing is to follow a link from a commons upload of djvu or whatever that has the s:Index:{{PAGENAME}} link in the proper place in the book template.

The answer to that question is to use the "Create" link at the uppermost right of the page. That answer is terse and when I typed it, full of happiness because I figured it out without help and felt on this occasion a bit superior (which was a feeling I did not often have then).

I mention that here because for those who do not read documentation, terse is so good. Lack of terse in documentation is the reason I don't read it. Terse is like pulling a bandaid off quickly, while reading documentation is like soaking it in water, slowly curling the edge up, taking an aspirin or something to kill pain, soaking it again until you forget what you wanted to do that required that bandaid to be removed.

That documentation you get by following the link from the djvu file to here is the enemy of actually making the Index page and accomplishing proof-reading. I'm going to defend User:Billinghurst the wikisourcerer (I am not defending Billinghurst the escalation bot, R.I.P.!) because I learned a lot, a very lot, from that terse sourcer. One thing being the endpaper hack (see User:RaboKarbakian/The Other Style Guide/Endpapers; I think I used {{bc}} in Main or something equally against the rules. That hack was Billinghursts solution to the argument that ensued (which is not what an escalation bot does at all).

Anyone doing anything of a collaborative nature anywhere, needs to be aware that there are a lot of different kinds of people and to put personal offense on a back burner until it is clear that there is really good reason to have that offense.--RaboKarbakian (talk) 15:47, 14 March 2025 (UTC)

Hi RaboKarbakian - thank you for your helpful contribution. If I may make an observation with respect to your final - and very valid - point, I have not taken personal offense at all. I have finally - after many years of feeling this - spoken up about a cultural behaviour which has, in my experience of 15 years on the site, been growing slowly over time. Interestingly, Alien333 appears to have been a WS editor since only 1st December 2023, yet has seemingly picked up on, and adopted, this cultural vibe in only 15 months. This cannot be of benefit to the WS project long-term as it risks alienating future editors (unintentional alien pun there!). I don't think there's anything unique to WS about this, BTW. It is (quite) a common behaviour in technical/technocratic circles where technical knowledge is assumed. That works fine on the wiki of the Institute of Electrical Engineers (assuming such a thing exists), where a base load (intentional pun this time!) of knowledge can reasonably be assumed, but much less so on a public project.

May I try to illustrate my point in another way? IRL, I belong to a mutual which has existed since 1874. If it still behaved today as it did in 1874 - without any cultural adjustment since then - it would be dead, buried and forgotten. As it is, it is in vibrant good health. In the last five years alone - just 3% of its lifespan to date - it has consciously changed its corporate "tone" to a less formal mode after canvassing members, it has updated its logo to be fresher and more browser friendly, and it has generally updated itself, I would say more rapidly than it ever has before (my father has been a member since before I was born, so I have a longer view than some other members might) - all to stay relevant to the modern world, and crucially to be able to continue to recruit new members. WS will always need new members, but it may need to change itself culturally in order to accommodate them. If it doesn't, it risks withering on the vine as retirees are not replaced by new participants.

You are - again! - absolutely right that terseness is the natural mode of expression of some people, and can often be a highly efficient form of communication. Absolutely nothing wrong with that. And Billinghurst is both a master of succinct expression and very probably one of the main reasons I am still on the site at all after a decade and a half. Some terseness can also be due to very reasonable frustration with the TLDR; crowd. I absolutely do not subscribe to the TLDR; vibe (in fact it really annoys me), whereby idleness and lack of intellectual curiosity can be effectively excused by using somebody else's goodwill, time and energy instead. Also, TLDR;ers tend not to learn from their initial exploitation of others' knowledge, and so come again and again to the trough, selfishly repaying those who help them only with further demands on their time. However, when I, as an experienced user, and after meaningful research cannot find the answer to a fairly basic question, something is surely empirically wrong, would you not agree?

Today, I came across another unintentionally unhelpful "answer": Template:Anchor link has the cryptic optional parameter 3, "subpage = name of different subpage of the work, where the anchor is on a different subpage". This is illustrated without any context at all by reference to two complex index-like pages, Page:A Compendium of Irish Biography.djvu/617 and A Compendium of Irish Biography/Authorities. I have literally no more awareness of the purpose of parameter 3 than I had before I went to the documentation!

I think I have taken more than enough of your time with my reply, so I will end there. Thanks again for contributing to the conversation. CharlesSpencer (talk) 13:42, 15 March 2025 (UTC)

I am deeply sorry for what I said. There was no intent on my part, in any way, to express surprise at someone's ignorance - sometimes, frankly, in order to demonstrate one's own superior knowledge. What I was trying to say, and I visibly failed quite badly at it, and sorry for that, is that, from a technical standpoint, I don't know a reliable way of answering the question "what is part of this work?" that does not rely on a user giving the list (it would be nice if we could find one, but I don't know of any), so, yes, there has to be a ToC on the main page (this to answer your question: If so, in order to have a full work epub, we have to graft the TOC into the first page?). The intended meaning was essentially:

• Put an auxtoc on the main page if the works are not listed
• Yes, I do think we don't have an alternative

On what Help:Preparing for export says: Every page you want in the export is linked from the root page, in saying that the rest has to be linked from the first page, is trying to imply that it should have a table of contents (to contain the links). And, you're right, it does it badly. We have a chronic issue with documentation.

The irony is, that I wholeheartedly agree on the importance of a welcoming environment, without the sort of biting I have just contributed to. As you say yourself, I was not two years ago in the position of new user coming along and getting bitten occasionally (and getting discouraged by that), and have noticed other instances of biting here and there (and tried to—well not prevent, that's not the right word, but indicate to the biter that it was suboptimal behaviour). I think that it is one of the key problems of a wiki community.

I have previously noticed I have difficulties communicating with others, especially figuring out what subtext people read in what, since essentially forever. This predates, by a lot, my involvement with WS. I had previously assumed that it wasn't that bad, and that it would not be much of an issue to my contributing. It does not give me an excuse to be rude, and so as I am unintentionally rude and I fail to compensate, perhaps I should just shut up; keep proofreading and avoid discussions. — Alien  3
3 3 18:32, 15 March 2025 (UTC)

Honestly, I cannot see anything that looks like some demontration of superior knowledge or whatever... The original answer was brief, but absolutely neutral and polite. --Jan Kameníček (talk) 10:46, 16 March 2025 (UTC)

Thanks all - appreciate you taking the time to address my points. We are all agreed - our documentation needs work! And Jan, this lovely article from the BBC [1] openend my eyes to the amazing variety of socio-cultural interpretations that we all (mostly unknowingly) apply when hearing or reading something. There's another article I can't now find which says that only Japanese uses more phatic langauge than Anglo-English, and that, for example, Bulgarian uses the least among European languages. CharlesSpencer (talk) 17:48, 24 March 2025 (UTC)

True. We all, myself included, have to bear in mind that we are from different socio-cultural environments, and so the more we have to try to assume good faith. Besides, many of us also often struggle with time constraints because we have to save the time for our online activities from our offline life, and so we just try to be brief and efficient. --Jan Kameníček (talk) 18:50, 24 March 2025 (UTC)

Line break issue

On Facts, Observations, and Conjectures Relative to the Generation of the Opossum of North-America, there are some pages with unwanted paragraph breaks, I believe from me using Hyphenated Word Start/End in footnotes. SnakesOfWest (talk) 18:40, 11 March 2025 (UTC)

No, it's not that. The problem is that when you add a <ref follow="...">...</ref>, you leave a paragraph break between the end of the page and the ref, like so:

... and this is the end of this page's last paragraph

<ref follow="...">...</ref>

You shouldn't do that, because when it is transcluded, although the ref follow="..." gets moved somewhere else, the empty paragraph stays, so you get something like this:

... and this is the end of this page's last paragraph

[empty paragraph where the ref used to be]

and this is the start of the next page

Which is what create the break. So, to fix, just remove the break before the ref=follows at the end of pages, e.g. like this. (note: when linking to templates, I believe you will find {{tl}} useful.) — Alien  3
3 3 18:53, 11 March 2025 (UTC)

Thank you. SnakesOfWest (talk) 19:04, 11 March 2025 (UTC)

Index "broken"?

For the book: The Country of the Pointed Firs, the source .djvu is fine, but the Wikisource index seems to be broken. When I click on "Source" at the top of the title page of the book, it displays this error: Lua error in Module:Proofreadpage_index_template at line 516: data for mw.loadData contains unsupported data type 'function'. Oddly, this apparently occurs only with the most recent edit to the index of this book in August 2022 (here) which simply added a Monthly Challenge category template; previous versions seem to display the index ok. I didn't want to just blindly revert this last edit, since I don't understand how it would cause this error. Harris7 (talk) 22:05, 11 March 2025 (UTC)

I do not see any errors at Index:The Country of Pointed Firs - Jewett - 1896.djvu. —Justin (koavf)❤T☮C☺M☯ 22:09, 11 March 2025 (UTC)

Presumably because I made a "null edit" moments before you visited the page. --EncycloPetey (talk) 22:11, 11 March 2025 (UTC)

See the discussion at Wikisource:Scriptorium#Index lua issue. --EncycloPetey (talk) 22:09, 11 March 2025 (UTC)

Replacing unsourced texts

I'm currently proofreading Index:The Ball and the Cross.djvu. At some point I'll need to start transcluding it into the main namespace. The Ball and the Cross is currently occupied by an unsourced version of the same novel. Would it be appropriate to simply replace the unsourced text by transclusions, or should the unsourced version be preserved? Bloated Dummy (talk) 23:43, 14 March 2025 (UTC)

If the edition is the same, then yes. If the scan edition differs from the existing copy, then the answer becomes more complicated. --EncycloPetey (talk) 01:13, 15 March 2025 (UTC)

PG, as they are wont to, do not give a source or date, but from comparing it appears to be the same edition. The only differences I can see are exactly the sort of stuff PG would take the freedom of changing. (Plus, this is a PG ebook, but not from DP. The DP ones are the only ones that are close to being faithful to something.) So, I think this is the same edition, in which case, yes, you can just replace it, and many thanks for doing so! — Alien  3
3 3 09:20, 15 March 2025 (UTC)

Alright, thanks for checking! Bloated Dummy (talk) 13:41, 15 March 2025 (UTC)

Guidance for an open license work work that contains some images that aren't open licensed

I recently managed to obtain a copy of The collapse of NATM tunnels at Heathrow Airport a report published in 2000, by the UK's Health and Safety Executive into an industrial accident in 1994, intending to scan it and upload it to Wikisource. The document is a work of the Health and Safety Executive, however contains at least three photographs that are noted as being "Reprinted with permission from...(Non-UK government entity)", so I do not believe those photos would are covered by Open Government License or Crown Copyright.

I feel like there was guidance for dealing with this situation, but I can't locate it.-- The Navigators (talk) 19:51, 23 March 2025 (UTC)

I think the procedure for that is removing these images in the file before you upload it, by putting a black rectangle over them for example, and then use {{image removed}} in the transcription. — Alien  3
3 3 20:08, 23 March 2025 (UTC)

Thanks, that looks like what I was looking for, and how to approach handling it.

(Now I just need to make some time to get to the library for their nice scanner. Life has decided to get very busy lately....)-- The Navigators (talk) 05:52, 30 March 2025 (UTC)

Transclusion error

Hello,

I’m trying to transclude a text for the first time and keep getting a “No such index” error. The index page is here: https://en.wikisource.org/wiki/Index:Family_Portrait.pdf

The code that I’m trying to use is: <pages index=“Family Portrait.pdf” from=“1” to=“3” header=“1” />

I’d like to transclude the text to the page at: The_Menorah_Journal/Volume_17/November_1929/Family-Portrait

Does anyone know what my mistake is here? Thanks for your help! Nvss132 (talk) 09:34, 24 March 2025 (UTC)

It's the curly quotes (” and “). For technical stuff, always use the straight quotes ("). Here it was looking for an index named “Family, as the curly quote was not interpreted as delimiting the index name. — Alien  3
3 3 11:22, 24 March 2025 (UTC)

Thanks, that solved it. Nvss132 (talk) 16:00, 24 March 2025 (UTC)

Errata glitch found

See Orlando Furioso (Rose)/Canto 27#109, in the final line of Canto XIX., where a correction from the errata has been applied, but is displayed incorrectly by the template, causing the overlapping of text. At first I thought this is caused by the fact that the original text is being used to determine the display, but the correction is wider than the original text, however the original text and correction are the same width. --EncycloPetey (talk) 19:46, 27 March 2025 (UTC)

• See another instance here. TE(æ)A,ea. (talk) 00:14, 28 March 2025 (UTC)

The span is inheriting a text-indent: -1em style from its parent, so to fix it a text-indent: 0 style should be inserted in the errata template, which I have just done. Arcorann (talk) 00:18, 28 March 2025 (UTC)

Thanks! --EncycloPetey (talk) 01:55, 28 March 2025 (UTC)

transcribing maps?

does wikisource transcribe maps like the one in Page:Pentagon-Papers-Part IV. A. 5.djvu/103 or leave them be? if maps are transcribed, how are they transcribed? ltbdl (talk) 03:47, 28 March 2025 (UTC)

It's an image with text on it; we can't really transcribe image, so I'd say either just leave the image, or, if you really want to transcribe it, blank the labels and use {{overfloat image}}, but I think no one'll hold it against you if you just put the image. — Alien  3
3 3 07:01, 28 March 2025 (UTC)

ok, thank you! ltbdl (talk) 07:47, 28 March 2025 (UTC)

example of 2-1 column TOC?

Newbie tables of contents question - Increasing spacing between rows to match scanned TOC page.

TOC proofread: https://en.wikisource.org/w/index.php?title=Page:Code_And_Other_Laws_of_Cyberspace_Version_2_0.pdf/5

Questions:

Is it important to duplicate the additional empty row spacing according to scan page layout (as I've been attempting to do)?

If it is, how do I either

a) add additional empty rows *and* get them to show up in the published page or

b) increase the space in the subcaption/"book part X" rows above and below the text?

(or c) is there a better way to increase spacing?)

What I've tried:

"TOC l | 3 |||"

"TOC 3|"

"TOC 2-1| |"

empty lines/additional line breaks

Results: I either get red text errors in the preview, or the additional rows simply don't show up in the preview.

Thanks for any suggestions/pointers on formatting TOC row height, adding blank but visible rows, or other more appropriate formatting.

Grayautumnday (talk) 22:54, 28 March 2025 (UTC)

Hello. When you add a line into the TOC, it has to contain something. So to add an empty line I suggest {{TOC row l|3| }}. --Jan Kameníček (talk) 23:33, 28 March 2025 (UTC)

additional question regarding title/TOC/blank pages - should I be putting "invisible" page numbers in the page headers? What's the template for that? Grayautumnday (talk) 23:12, 28 March 2025 (UTC)

We usually write page numbers only to the headers of the pages which contain such numbers. However it is not really important, as the headers are not transcluded to the mainspace anyway. I can see that you are using the {{rh}} template, you can also try {{rvh}}. --Jan Kameníček (talk) 23:33, 28 March 2025 (UTC)

further question: on this book, pages 3 to 9 are created and most are validated, but they're not listed when I search for subpages of the original PDF - is this a function of these pages needing to have a template added to show them as subpages of the scanned book? Grayautumnday (talk) 23:25, 28 March 2025 (UTC)

line breaks + basic accessibility request?

Help need 1: Line Breaks -- are there any tools or methods to remove all line breaks from an OCR transcription, or to find-replace line breaks?

What I tried: I tried doing find for all variations of newline HTML entities as well as attempting to cut and paste a line break into the find box in Firefox. I also went and explored the other OCR engines and tried setting OCRs to "treat the page as a single line of text" and "treat the page as a single block of text" but neither kept line breaks from being included.

Help need 2: Accessibility/usability issues for newer editors/proofreaders

It is extremely difficult for me to find relevant template or styleguide info to very specific use cases by re-reading every "newbie" page and searching "help"/"template" pages. (I've run into accessibility issues in FOSS communities before, but wikisource resources for newbies, in a few notable areas, it's quite remarkably something else wrt gaps in info accessibility for neurodivergent newbies!)

What I tried: - searches for basic phrases such as "ask for help" or "post a request for help" in Help/Help:Talk/Template/Template:Talk pages - no results. Zero user-friendly/disabled-accessible links to ask for help from Scriptorium page or from ANY of the "new proofreader/editor" help pages. Additionally, there's a Scriptorium/Help/Archive but no Scriptorium/Help.

Pretty pretty pretty please can there be added some easy-to-find -very obvious- links to where post help requests when all proofreading/formatting guides and all relevant searches are thoroughly scoured and no answer found?

Especially since basically every reference page/reference section on "finding and using templates" throughout all the help pages have been deleted/removed???

I have a significant amount of time and energy to dedicate to proofing and validating, and it's important to me to conform to accepted standards. But the roadblocks to learning and finding answers to difficult questions here are incredibly steep and just seem to be getting more intense as I keep learning.

I'm happy to research and fill in information if more experienced editors create and put up skeleton outlines for help pages that have been removed, but without them it's feeling particularly unwelcome here (despite the very warm welcome when I manage to actually find this page again to post new questions!)

Sorry for the long winded message.

Please help? Grayautumnday (talk) 09:56, 29 March 2025 (UTC)

On 1:

• multiple users made scripts to do that. My own iteration of that is at User:Alien333/nobr.js. If you add importScript("User:Alien333/nobr.js") to User:Grayautumnday/common.js, a link should appear in the sidebar that unwraps paragraph.
• else, if you've got the editing toolbar activated, you can use find-and-replace with the search icon on the right, put \n in the search field, enable Treat search string as a regular expression, and then press Replace all, and it'll remove all line breaks.

On 2:

We have do have an issue with documentation, especially on templates.

However, on mentions of this page, I must say there aren't none. First on the welcome message everyone has received: Have questions? Then please ask them at either Wikisource:Scriptorium; or Wikisource:Scriptorium/Help. Also, if you look at WS:Community portal, linked in the menu on every page, the second link in the tab "community" pages at the top left is Requests for help, linking to here. And the bottom of Help:Contents, also linked to in the menu on every page, has:

Do you need assistance? Post a request!

which also links to here. So, there are already quite a lot of references to this page.

But yes, besides that, we have a problem with template documentation, and user-friendliness could be better. — Alien  3
3 3 10:32, 29 March 2025 (UTC)

this is a lifesaver. I've got a strong tendency to go straight to searching docs (aka rtfm :0>) and clicking through relevant links. I almost never end up getting down to the bottom of a page -- well, like if the section I've clicked through to doesn't have the answer I need, I tend to back up or start over with a new set of "template: __" search terms or "" quoted literal strings of basic phrases I'd expect to see in the text (eg "blank pages" or "no text") and then just limit searches to Help/Templates or sometimes turn on a talk page for a relevant category to see if I find something there.

So it sounds like I got far enough to not need the super-duper-basic stuff, and that's what was catching me up and biting me in the foot, so to speak.

But d00d, seriously, thanks for the tips. Maybe it'd help if I hadn't gotten sucked into editing wikisource by a super-technical legal text on cyberlaw (where the endnotes pages has endnotes of its own - doh! I've switched to creating/proofing pages at the end, so I can create the links to all the refs and then go back to the beginning to properly link all the endnote refs. )

It's an adventure! Grayautumnday (talk) 12:58, 29 March 2025 (UTC)

sheesh, hey - does this add itself to the "User" editing menu? If so, can you recommend any other daily-driver general-purpose scripts you use for yours? Grayautumnday (talk) 13:02, 29 March 2025 (UTC)

It adds itself in the "Tools" menu, in the "General" section, somewhere next to the "Page information" button.

There's the gadgets (in Preferences): if you haven't already, I strongly recommend the {{nop}} inserter, the {{running header}} inserter (these two save time), and the "preload next page image" thing (makes pages load faster).

I am what I think could be called a prolific script writer, and more or less everytime I come across something that looks like it could be automatised, I make a script for it. Some of mine you could find useful (it's also a question of preferences):

• User:Alien333/clean.js to do some basic formatting when creating a Page: (it includes my preference for straight quotes, but I could make that customisable if someone wants me to)
• User:Alien333/cuts.js for many more shortcuts, including to the other scripts (feel free to suggest more)

Also a few very minor tweaks:

• User:Alien333/pagenum.js just adds the display page number in parenthesis to the page title, e.g. if you go to Page:Passion-Flowers (Howe).djvu/119 it adds a (109) after, because in the index it's listed as page 109
• User:Alien333/nts.js just automatises the summary for new texts, with "+ [link to work]"
• User:Alien333/sandbox.js removes the trouble of having to care about the WS:SAND header (the "Please do not remove this line" thing)

I would also have recommended User:Alien333/transclude.js for transclusion, though sadly I haven't made an interface for that yet, User:Alien333/mtv.js if you ever want to do movies, and User:Alien333/poemise.js for poetry (a lot of my scripts aim to optimise poetry proofreading, as it's the main thing I do).

The complete list is on my user page.

I also use User:Inductiveload/popups reloaded (popups when you hover over a link) and mul:MediaWiki:TranscludedIn.js (giving links, when in Page: namespace, to the pages that transclude the current page). — Alien  3
3 3 13:50, 29 March 2025 (UTC)

well, again, thank you.

I'm also drawn to poetry in addition to reference works, and - related to our discussion elsewhere - have added a few additional PD poetry projects to my user:talk page if you're ever looking for more works to upload (before I get around to it) - if you do, please add a note so I can include the books in my proofing/validating project rotation Grayautumnday (talk) 20:02, 29 March 2025 (UTC)