Wikisource:Scriptorium/Help

How to delete a page created by mistake?

I have created Weird_Tales/Volume_2/Issue_1/ by mistake. Since then I have created the correct page Weird_Tales/Volume_2/Issue_1 with the same content. How can I correct my mistake and remove Weird_Tales/Volume_2/Issue_1/? Klaufir216 (talk) 17:44, 14 May 2024 (UTC)

Put {{sdelete|G7}} at the top (for more info about this, see WS:CSD and Template:Sdelete). Note: When you create a page at the wrong place, instead of deleting the old one and creating a new one, you can move (rename) it by going in the "Page" menu at the top right. — Alien333 (what I did & why I did it wrong) 18:39, 14 May 2024 (UTC)

If you do move a page like this (i.e. quickly after creation), please mark the old title as {{sdelete|M2}}. That way we can delete the wrong title. This criterion only applies within a week of creation. Beeswaxcandle (talk) 10:12, 15 May 2024 (UTC)

Will keep in mind, thanks a lot! Klaufir216 (talk) 20:17, 15 May 2024 (UTC)

Failing page parser when creating index

I wanted to create an index of a file in Hebrew Wikisource, but the server fails to parse the file for the list of pages. It seems that there's the same error in English: Index:Ketav Sofer al haTorah.pdf. What is my mistake? Drkazmer (talk) 17:36, 21 May 2024 (UTC)

The pagelist is a tag and must therefore be opened with < and closed with />. In your case, there was </ pagelist >, which doesn't work (technically, it'd be a closing tag, and then you're missing the opening tag). I fixed it, normally, though you still need to put a pagelist (as of now, it's empty). — Alien333 (what I did & why I did it wrong) 18:24, 21 May 2024 (UTC)

Thanks for fixing it! It may be a bug due to the right-to-left nature of Hebrew, because in case of my previous upload I didn't have such problem at all. Drkazmer (talk) 18:43, 21 May 2024 (UTC)

Huh, so much for me. I also, as a matter of routine after that discussion, purged the file on commons, and it might be that, though it didn't appear to have immediate effect. EDIT: Could you translate me the error message? (I don't speak Hebrew). If it's that whole purging thing, the error should be "Invalid Interval" — Alien333 (what I did & why I did it wrong) 18:45, 21 May 2024 (UTC)

Looks like the Index at Hebrew Wikisource is working fine, and proofreading has started. Cremastra (talk) 23:07, 21 May 2024 (UTC)

Some piece of the voodooing I did to it fixed the pagelist. — Alien333 (what I did & why I did it wrong) 05:23, 22 May 2024 (UTC)

DOI help

The DOI links for Monthly Weather Review, Volume 1, Issue 1 are weird and are not actually linking properly on Talk:Monthly Weather Review, Volume 1, Issue 1 or Index:Monthly Weather Review, Volume 1, Issue 1.png. Can I have some assistance with fixing that? Also, I'm still newer to the whole page/index aspect on Wikisource, so can someone check over Page:Monthly Weather Review, Volume 1, Issue 1.png to see if I did it properly? WeatherWriter (talk) 21:01, 23 May 2024 (UTC)

As far as the index: You've transcribed library annotations from the bottom. Typically, we don't transcribe writing added after the work was printed, whether library markings, stamps, book plates, etc. --EncycloPetey (talk) 21:17, 23 May 2024 (UTC)

I fixed the first and second link on the page (missing the l in xml and escaping the [ and ]). MarkLSteadman (talk) 23:41, 23 May 2024 (UTC)

Triggering quality change

I've been trying to find an event to trigger from JS to change the radio buttons for quality. $("input[value=3]").trigger("click") and $(".quality3").trigger("click") are the only two that appear to work, but they do not really, as the proofread button gets checked but the other buttons not unchecked and on saving the page is still red (or whatever it was before). $("div[aria-activedescendant][tabindex=5]").attr("aria-activedescendant", "14") didn't help either, so that's not what actually changes something. The relevant file appears to be there, and it even looks (from the comments ~l.5400) that it is plainly impossible to .trigger() it. Maybe there's a way to bypass the radio buttons, and directly call some underlying function. — Alien333 (what I did & why I did it wrong) 19:25, 28 May 2024 (UTC)

@Alien333: What is it you're trying to do?

In any case, those radio buttons are not plain HTML radio selects, they are an OOUI RadioSelectWidget. You're probably looking for something like

const pageQualityWidget = OO.ui.infuse($('.prp-pageQualityInputWidget'));
pageQualityWidget.radioSelectWidget.selectItemByData("3");

For normal HTML radio selects you should use jQuery's .prop() method. --Xover (talk) 17:00, 30 May 2024 (UTC)

I was trying to find a shortcut to mark the page as proofread, instead of having to scroll down.

Since clicking changed it, I figured faking a click would do it.

Thank you for your solution! — Alien333 (what I did & why I did it wrong) 17:04, 30 May 2024 (UTC)

.trigger("click") isn't the same as interactively clicking the UI with a mouse, it's the event that gets triggered under the hood by that UI interaction. Sometimes these are the same thing, but often they are not. To actually simulate a mouse click you would have to use accessibility APIs and it'd be pretty hacky, probably.

But if you're in edit mode the quality buttons are right next to the save button anyway. Are you trying to replace both perhaps? Xover (talk) 17:28, 30 May 2024 (UTC)

For save, there is already the alt-shift-S shortcut, that is sort of useless if you have to scroll anyway to change the quality, so I thought I might as well make another shortcut for that. — Alien333 (what I did & why I did it wrong) 17:33, 30 May 2024 (UTC)

You can probably just $("#wpSave").trigger("click") (not tested, may be more OOUI weirdness involved) and assign your own accesskey to kill both birds with one stone. Xover (talk) 18:24, 30 May 2024 (UTC)

Fair enough (no OOUI weirdness). Thanks. — Alien333 (what I did & why I did it wrong) 18:47, 30 May 2024 (UTC)

add 1939 report of the commission on the palestine distrubances of august 1929

i was wondering how to best start putting https://commons.wikimedia.org/w/index.php?title=File:Report_of_the_Commission_on_the_Palestine_Disturbances_of_August_1929_cmd_3530.djvu&page=2 , resp https://unispal.un.org/pdfs/Cmd5479.pdf here. in 2 aspects, first how to put at all, and second, how to handle the rather comlex formatting. ThurnerRupert (talk) 00:55, 5 June 2024 (UTC)

To add the text here, begin by creating the Index:Report of the Commission on the Palestine Disturbances of August 1929 cmd 3530.djvu. Then proofread each page to match the original. If the formatting is complex, then this might not be a good choice for creating your first work here. You might try some of the community collaboration works listed through the main page before starting a challenging work. --EncycloPetey (talk) 00:59, 5 June 2024 (UTC)

Question about updating PDF later

So I am working on scanning a large U.S. government online document into a PDF. I currently have 47 pages. I know the Commons allows you to post a new version of a image/PDF. My question is would that screw up stuff over here on Wikisource? So say I uploaded the PDF as-is right now with 47 pages to work on transcribing those (basically 3 chapters done of it). If I then later go back and scan in more images, should I upload that as an entirely separate thing on the Commons or just upload a new version of the PDF? Basically, what should I do in this circumstance. Note, there is probably 200-ish (or more) pages of the document. WeatherWriter (talk) 20:36, 7 June 2024 (UTC)

It's best to transcribe from a complete PDF. Yes, altering a PDF during transcription can create problems. This is one reason we have a setting option on the Index page to indicate a scan needs to be repaired before proofreading. --EncycloPetey (talk) 20:47, 7 June 2024 (UTC)

• WeatherWriter: If you’re just adding pages at the end of the document, then there shouldn’t be any problem. It is not best practice, however. TE(æ)A,ea. (talk) 21:52, 7 June 2024 (UTC)

Deciphering bl capital

Sort of silly question, but there, I can't manage to understand what the first letter of the title is, it's in a {{bl}} variant I'm not familiar with. (there is no TOC in this book, so can't use that). It's not a common word either, ending in "idigeigi". Google OCR says it's an H, but it doesn't look like that. A G, maybe? — Alien333 (what I did & why I did it wrong) 15:23, 10 June 2024 (UTC)

Ha, that's a tricky one, but there's an identical character on page 26 which confirms that it's an H. —Beleg Tâl (talk) 15:29, 10 June 2024 (UTC)

Good find, thank you. — Alien333 (what I did & why I did it wrong) 15:49, 10 June 2024 (UTC)