# Wikisource:Scriptorium/Help

Jump to: navigation, search
 The Scriptorium is Wikisource's community discussion page. This subpage is especially designated for requests for help from more experienced Wikisourcers. Feel free to ask questions or leave comments. You may join any current discussion or a new one. Project members can often be found in the #wikisource IRC channel (a web client is available). This page is automatically archived by Wikisource-bot Have you seen our help pages and FAQs?

## About proofreading

I'm new to this so - I found a book that I'm really enjoying proofreading but I can't do all the pages because some have illustrations. My question is - how do I let you know when I've finished what I can so you can have someone do the 10 or so pages I can't? Do you automatically get notified when a book is done? I'm working on Aunt Jo's Scrap-bag by Louisa May Alcott and I only have about 20 pages left. Thanks, unsigned comment by Mkjames100 (talk) .

Hi Mkjames100. Welcome to our little site, and great that you are finding somewhere to contribute, thanks for what you are doing. Help:Page status gives some information about your questions, and also Help:Beginner's guide to proofreading which has pointers to Template:missing image. Pages with images that need to be replicated get tagged with {{missing image}} and marked as problematic, if there is text and you have proofread that text, then a comment into summary is helpful. Re completion and notification, who is the "you"? Not exactly certain what you are expecting/wanting.

When an index page has its proofreading status changed, ie. Index:Aunt Jo's Scrap-Bag, Volume 5.djvu there is categorisation that changes. Normally we have good watching on recent changes, so someone generally knows and assists if it is required, or we are pinged here. There are numbers of processes that take place, so depending which it is, will set of triggers, though not announcements. — billinghurst sDrewth 23:57, 19 July 2017 (UTC)

## Your incorrect schedules

Just wondered if these are to be altered so that the columns refer to the data supplied?

Yours, Neil, South Africa.unsigned comment by 203.7.43.45 (talk) .

please provide a link to the page at which you are seeing issues. — billinghurst sDrewth 14:55, 23 July 2017 (UTC)

## My first djvu

Hi,

I've uploaded my first .djvu to Commons yesterday and I've created the Index page for that book today: Index:A literal translation of the Saxon Chronicle.djvu. Can someone have a look and tell me whether I've made mistakes? Ælfgar (talk) 16:56, 25 July 2017 (UTC)

Looks OK to me.— Mpaa (talk) 16:01, 26 July 2017 (UTC)

## The Betrothed (Manzoni) Transclusion boo-boo

Advice please. I have been validating for so long that I've lost sight of transclusion.

This book has Roman numeral chapters, not identified. I used AuxTOC on both main:ns and index:ns as Roman numerals. But then I created Chapter I and Chapter II as Chapter 1 and Chapter 2. My question is: Should I continue as I've started, adjusting the AuxTOC's, or should I move subpages 1 and 2 to subpages I and II? My inclination is to continue as I've started but if that goes against style guidelines, I can try to make the appropriate changes. Any and all comments welcomed. Humbug26 (talk) 22:56, 30 July 2017 (UTC)

I suggest to continue as you started. I know some people would use Arabic numbers instead of Roman regardless of usage within the text, though I don't think it matters either way. —Beleg Tâl (talk) 01:05, 31 July 2017 (UTC)
Thank you, I'll continue on as I started. Humbug26 (talk) 16:32, 31 July 2017 (UTC)

## Page:The_Cutter's_Practical_Guide_1898_Edition_Part_1.djvu/28

Same approach in two locations on this page with DIFFERING results, There should be ONE line between the end of one section and the heading for the next. Can someone suggest an approach that will work CONSISTENTLY?

ShakespeareFan00 (talk) 09:03, 3 August 2017 (UTC)

And whilst that's solved, adding {{nop}} elsewhere produces spurious lines on transclusion! The Cutters' Practical Guide (1898)/Part 1/The System. Please fix the parser so there is ONE CONSISTENT approach used, so I don't have to continually run around playing "hunt the obscure syntax". I am getting very tired of having do this.

ShakespeareFan00 (talk) 13:10, 3 August 2017 (UTC)

I agree that it's pretty annoying that EasyLST adds empty paragraphs when there's a blank line above the section marker. EasyLST is just a JS gadget; it isn't real markup, and it converts to normal LST markup before being saved. That's probably why the behaviour is erratic. I suggest that you bring it up at Phabricator if it's causing you a lot of problems. I usually just leave off the preceding blank line as you have done in your final version of the page. Also: if you put a section tag at the top of the page, the behaviour will at least be consistent.
I also reproduced your problematic version at Page:Sandbox.djvu/6 in case people want to investigate further.
As for your second question, I don't see any problems with {{nop}} on a quick perusal of the linked page; can you be more specific as to where the problem is? —Beleg Tâl (talk) 19:47, 3 August 2017 (UTC)
Please take it back to basics. NOP statement is a sneaky placeholder that stops the collapse of a line where mediawiki tries to collapse multiple terminating lines. It is a cheat by us to retain these linebreaks when we transclude multiple pages. As it is a sneak, its behaviour completely relates to how and where it is used. If it is giving different behaviour it is most likely being used differently. Above links are too inspecific to comment for the reported use.
And we have no means of knowing who is using EasyLST or if it is being used as when the code is saved it is done with tags. So Mediawiki and the LST extension are working perfectly and as expected, though it sounds as if a local gadget is not doing so. are you are able to investigate the gadget, and is using phabricator ticket the best means to do this? I am going to hazard a guess that a change in mediawiki general behaviour has resulted in this quirk. [I don't see an issue, though I use old-fashioned section tags and format assiduously around them.] — billinghurst sDrewth 02:16, 4 August 2017 (UTC)
I don't know it's anything to do with the MediaWiki parser/backend (not my area), but from a quick look at the Sandbox rev, I have a clue. Using EasyLST does make it less obvious, as you don't get to see the <section> markup being sent to the server.
With no section at the start of the page:
lorem ipsum

<section begin="diagram40" />{{c|'''Single space above here'''}}

<section end="diagram40" />
<section begin="diagram41" />{{c|'''Double space above here'''}}

With a "dummy" section at the start of the page (EasyLST or not) and it's consistent:
<section begin="dummy" />
Lorem ipsum

<section end="dummy" />
<section begin="diagram40" />{{c|'''Double space above here'''}}

<section end="diagram40" />
<section begin="diagram41" />{{c|'''Double space above here'''}}

Or, not using EasyLST and doing it manually, without newlines between <section> tags:
Lorem ipsum

<section begin="diagram40" />{{c|'''Single space above here'''}}

<section end="diagram40" /><section begin="diagram41" />{{c|'''Single space above here'''}}

I presume from this that the MW parser is removing the <section> tags and leaving the newlines after them, when they exist. That could well be a parser issue, especially if it's changed recently and suddenly. EasyLST hasn't changed in years, AFAIK, so it isn't that EasyLST is adding newlines where it used to run-on the same line - it's always done that. Now, the problem here is that if you manually remove the newline between begin and end section tags, EasyLST will put it back on the next edit by anyone with it on.
I don't see any commits in the proofreadpage extension in the last year that should have changed this - I am not familiar with the backend code, but I imagine it would have been around here if anywhere.
A solution is to roll with what EasyLST does (newlines after all section tags begin and end) and simply don't but blank lines before the sections, as mentioned by Beleg Tâl above:
lorem ipsum
## diagram40 ##
{{c|'''Single space above here'''}}
## diagram41 ##
{{c|'''Single space above here'''}}

Expanded by EasyLST to:
Lorem ipsum

<section begin="diagram40" />{{c|'''Single space above here'''}}
<section end="diagram40" />
<section begin="diagram41" />{{c|'''Single space above here'''}}

I suppose it could be possible to change EasyLST to not include the newlines after ## section_name ##, but that might be a surprise if it changes suddenly? It might be possible to do it transparently without causing any "null edits" on pages to change the wikitext? Too early in the morning to get my head round that! Inductiveloadtalk/contribs 05:22, 4 August 2017 (UTC)

## Commons djvu and Source pdf

Niger Delta Ecosystems- the ERA Handbook, 1998 Uploaded this as pdf but realised issues, so then uploaded as djvu file. Made index page but can't get it to refer to djvu, only pdf. However, the djvu file is still extant on Commons. Can anyone help this beginner? Susi Susi Arnott (talk) 11:47, 3 August 2017 (UTC)

Looking for this Index:Niger Delta Ecosystems- the ERA Handbook, 1998.pdf? which I'd done a first pass OCR trabscribe on. Can't garuntee all the scan/typing errors removed though. ShakespeareFan00 (talk) 11:50, 3 August 2017 (UTC)

Thanks for replying; but my question was about what to do next. Presumably stick with the pdf, even though images are missing? And a beginner's guide or glossary of 'proofreading' would be great. (What the different commands mean, etc.) What happens if I've tagged a page as being 'proofread' and there are still problems? Thanks for your patience!

Done -- Index:Niger Delta Ecosystems- the ERA Handbook, 1998.djvu. Hrishikes (talk) 16:01, 3 August 2017 (UTC)

Thanks again! Presumably I should now go ahead and start proofreading the djvu file - but what does this box mean: The text of this work needs to be migrated to Index:Niger Delta Ecosystems- the ERA Handbook, 1998.djvu Happy to put the hours in (Sunday is for Wiki now!), but would love to start from the right place :) Thanks everyoneSusi Arnott (talk) 16:45, 3 August 2017 (UTC)

You'll notice that the transcription User:ShakespeareFan00 performed applied to the pages linked to the PDF version of this book, as in Page:Niger Delta Ecosystems- the ERA Handbook, 1998.pdf/3 (note the "pdf" in the title). Since the DjVu version does not have this transcribed text (i.e. Page:Niger Delta Ecosystems- the ERA Handbook, 1998.djvu/3 does not yet exist), the text will need to be moved from the PDF's pages to the DjVu's pages. Mahir256 (talk) 17:05, 3 August 2017 (UTC)
Donebillinghurst sDrewth 22:16, 3 August 2017 (UTC)

Thanks everyone. Could somebody post a link to the page I should start from? Don't want to be an idiot and muddle anything up, but planning to spend much of Sunday on this (learning as I go).Susi Arnott (talk) 08:23, 4 August 2017 (UTC)

Index:Niger Delta Ecosystems- the ERA Handbook, 1998.djvu is the index page. Susi Arnott is the generated file coming from a document that has been directly transformed, or has it been scanned to generate this version? If the former, then obviously not words to check, and it is formatting, and, if any, images to reproduce. — billinghurst sDrewth 08:56, 4 August 2017 (UTC)

The original file was a pdf with several illustrations - took advice to convert online into a djvu fileSusi Arnott (talk) 11:15, 4 August 2017 (UTC)

## Linking to French WS

I am trying to link to a work at the French WS at this page and another, but [[fr:La Cité chinoise|La Cité Chinoise]] does not seem to work. 1) Is my method incorrect? 2) Is it 'permissible' to wikilink to another language WS? Thanks, Londonjackbooks (talk) 09:19, 4 August 2017 (UTC)

Re 1: The code [[fr:La Cité chinoise|La Cité Chinoise]] adds a sidebar interwiki (which is normally done by Wikidata now? Help:Interlanguage links is probably a bit out-of-date in that respect). For an in-line inter-language link in the text, use a prefixed colon: [[:fr:La Cité chinoise|La Cité Chinoise]]. Re 2: Seems like a perfect thing to link to me. Inductiveloadtalk/contribs 09:36, 4 August 2017 (UTC)
Thanks, and welcome back. Londonjackbooks (talk) 10:20, 4 August 2017 (UTC)

##  error cannot be found

There is a  statement which is a duplicate of another on the same page, but there is something wrong with it, and I cannot find the error. Page:Popular Science Monthly Volume 70.djvu/455. Could someone with could take a look at it please? — Ineuw talk 04:48, 8 August 2017 (UTC)

@Ineuw: Done I think... Mahir256 (talk) 05:04, 8 August 2017 (UTC)
@Mahir256: Much thanks. Do you know what was wrong with it? — Ineuw talk 06:14, 8 August 2017 (UTC)
@Ineuw: Looking at the diff, you missed a \right command. Mahir256 (talk) 17:47, 8 August 2017 (UTC)
I never thought of using the diff. I should have quit earlier in the evening or, I should have matched it to the (nearly) identical formula that appeared previously on the same page. Thanks again.

## Work has a wrong title

Could Johnson be moved? As you can see from [1] or [2], the correct title is Johnson v. Pannel's heirs, even though a lot of works (e.g. my first link) wrongly give it merely as Johnson v. as if it were a court case in which Johnson sued nobody. I'm familiar with Special:MovePage, but since I've never had reason to move a page here, I don't know if moving just one page might make a mess with other pages of which I'm unaware. Nyttend backup (talk) 15:24, 8 August 2017 (UTC)

Done with all pages, and left a soft redirect at the root. Feel free to create a hard redirect for your other shortened title if you think it worthwhile. Worthwhile double checking enWP for outbound links to the work. — billinghurst sDrewth 22:54, 9 August 2017 (UTC)

## Running header lookup script problem

I've started working through Hazlitt's Political Essays and it would be very convenient to use the Running header lookup script to create the headers automatically . I have put the script on my common.js, but see nothing in the proofreading edit view. The first page I'd want to start using it is here. Celuici (talk) 20:31, 9 August 2017 (UTC)

Hi @Celuici:, that's interesting, I didn't think my version of that tool would have been listed there still! I have updated it to use the TemplateScript framework like Phe's arabic-only version now does, and fixed a few more issues with it, as it's been rotting there for quite some time! It appears now to be working (look in the sidebar on the left). I tried it on your page - it won't work if you use the "center" and "right" params - the easiest and most common way to write it without a left parameter is {{running header||PREFACE|xi}}. I fixed page 15 and page 17 filled in OK.
Note for anyone using the old edit toolbar - this tool is now in the left sidebar. Shout if you value it very much in the toolbar as well, and I can put it back in the toolbar. Inductiveloadtalk/contribs 00:57, 10 August 2017 (UTC)
It's working perfectly now, so thanks very much for looking into this. It's certainly a very useful tool! Celuici (talk) 06:56, 10 August 2017 (UTC)

## Talk Page Archive

Hey folks -- we have a lot of lengthy discussion going on at Translation: Genesis. So far the talk page has 68 entries, and more are probably coming, and they stretch back about ten years. Is there a way on Wikisource to set up an archive bot like we would have on Wikipedia, to sweep conversations that haven't been touched for, say, a month into a searchable archive? Thanks. Alephb (talk) 00:39, 12 August 2017 (UTC)

You can use User:Wikisource-bot at the top of the talk page.— Mpaa (talk) 10:59, 12 August 2017 (UTC)
Thanks. That should help. Alephb (talk) 13:38, 13 August 2017 (UTC)

## Possibly duplicated text

Is Reconstruction (The Atlantic Monthly) a duplicate of Reconstruction (Douglass)? They seem very similar if not competely identical. What is the process for raising this sort of issue on enWS (I have never really contributed here, so I don't know what the right procedure or forum is...) SJK (talk) 10:41, 15 August 2017 (UTC)

It does appear to be a duplicate text from the same source. One was copy-pasted from a website where the text had been extracted, and the other is transcluded from a scanned copy. --EncycloPetey (talk) 16:36, 15 August 2017 (UTC)
Thanks for raising it, and raising it here is fine. We do allow the same work to appear where they are different editions/sources of the same work. Having a proper source and even better provenance is what we seek, as explained by EncycloPetey. It would seem that both should be moved to be subpages of The Atlantic Monthly with redirects from root. — billinghurst sDrewth 00:06, 16 August 2017 (UTC)

## Unexpected {{Chart}} template errors

On Page:The_Melanesians_Studies_in_their_Anthropology_and_Folklore.djvu/60, what should be quite a simple family tree chart is giving the following template redlinks.

Template:Chart/cellt

Template:Chart/cellb

Does anyone more experienced have any ideas, or have I done something wrong with my {{Chart}} syntax?

Thanks

CharlesSpencer (talk) 05:40, 17 August 2017 (UTC)

Check now. Hrishikes (talk) 06:10, 17 August 2017 (UTC)