Wikisource:Scriptorium/Help

From Wikisource
Jump to navigation Jump to 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).

Have you seen our help pages and FAQs?



Footnotes at the bottom of a chapter in Main, at the bottom of the page in Page:

[edit]

Hi. Looking at Page:ChroniclesofEarlyMelbournevol.1.pdf/41 I have a footnote, which displays correctly, but is completely wrongly placed at The_Chronicles_of_Early_Melbourne/Volume_1/Chapter_3. How can I make these footnotes - or rather their positioning - namespace aware? Thanks. CharlesSpencer (talk) 15:23, 4 September 2024 (UTC)Reply

@CharlesSpencer: By following our guidance for footnotes at H:REF. Short version: use <ref>...</ref> and {{smallrefs}}. Xover (talk) 15:36, 4 September 2024 (UTC)Reply
Thank you! All very clear... CharlesSpencer (talk) 15:55, 4 September 2024 (UTC)Reply

Sharing CSS between volumes

[edit]

In Help:Page styles I see this:

You can redirect a `/styles.css` to another CSS page (for example if a set of volumes share the same styles) but the redirect page may need to have the "content model" changed to "wikitext" (from "sanitized-css"), which currently requires an admin.

Well, I'd like to share the CSS between volumes of EB456S... how can I get an admin to do the thing? Bloated Dummy (talk) 21:09, 7 September 2024 (UTC)Reply

For admin requests in general, make them at WS:AN.
In this specific case, though, there's a way to do it without admins, though it's a bit hacky, with @import, with something like:
@import "https://en.wikisource.org/w/index.php?title=[insert page name]&action=raw&type=text/css";
Alien333 ( what I did
why I did it wrong
) 23:08, 7 September 2024 (UTC)Reply
Thanks, I'll give it a go. Bloated Dummy (talk) 00:06, 8 September 2024 (UTC)Reply
Despite the annoyance of having to ask an admin, it is generally preferable to use redirects for this purpose. @import has security implications that may conceivably lead to limiting that use of it in the future, and with redirects we can use the normal on-wiki tools for this (e.g. Special:WhatLinksHere) that do not work with @import.
PS. cf. Class naming conventions, use the _ prefix for class names in per-work styles to avoid collisions with classes from other sources. Xover (talk) 07:25, 8 September 2024 (UTC)Reply
I created a redirect at vol. 2, but not the others since they do not exist yet. Please feel free to grab me, or post at WS:AN, when you create the index for subsequent volumes. Xover (talk) 07:29, 8 September 2024 (UTC)Reply
Okay, thanks.
Re: the naming conventions, I'll try to rename the classes I already added. Bloated Dummy (talk) 12:17, 8 September 2024 (UTC)Reply
There's also another trick where if you create a page in a certain content model, it keeps it when you move it.
We can in this case create a page which will by default be wikitext, such as a userspace page, and then move it to an Index:/styles.css, and it'll still be wikitext. — Alien333 ( what I did
why I did it wrong
) 08:34, 8 September 2024 (UTC)Reply
Hmm. It'd probably also work to create the stylesheet in one of the subordinate indexes, then move it by turns through all of them until it finally ends up in volume 1 / its permanent location, and then manually update all the redirects thus created. But those are all hyper-complicated technical approaches that we can't subject our contributors in general to. Thus the guidance to just request it at WS:AN and let an admin sort it out. Xover (talk) 10:21, 8 September 2024 (UTC)Reply
{{REDIRECT|Index:title/styles.css}} would do the same thing as moving the page would. Hmm. Maybe three curly brackets on each side. But "Move" just deposits one of these wiki directives and displays a suggestion for how to handle things after the move which should be ignored for this case.--RaboKarbakian (talk) 13:54, 9 September 2024 (UTC)Reply

Requesting assistance researching authors

[edit]

We have three author pages for people named Duncan Campbell, and very limited information about any of them. If anyone would like to assist with researching biographical information for them, it would be appreciated.

Beleg Tâl (talk) 14:59, 10 September 2024 (UTC)Reply

I found:
but I'm not sure whether it actually refers to the first Duncan Campbell listed, or is a fourth one. --EncycloPetey (talk) 15:45, 10 September 2024 (UTC)Reply
@EncycloPetey@Beleg Tâl Assuming the fl. 1756 date is correct, based on the dates quoted in the DNB he's a fourth one. Chrisguise (talk) 12:41, 12 September 2024 (UTC)Reply
Correct, but only if the fl. date is correct, and it may not be. That date assumes the one publication we have was not published posthumously, or that it was not published under the name solely to capitalize on someone's fame. Hence, I am not sure whether it is the same person or not. --EncycloPetey (talk) 16:15, 12 September 2024 (UTC)Reply
Allibone has a record for the first one with some additional works. MarkLSteadman (talk) 18:38, 12 September 2024 (UTC)Reply
Huh, interesting. He seems to think that Campbell (d. 1730) and Campbell (fl. 1756) are the same person, as EP suggested above. I'm skeptical, but maybe I'll take a page from Wikipedia and aim for verifiability rather than truth (shrug) —Beleg Tâl (talk) 19:45, 12 September 2024 (UTC)Reply
Actually, no—The Earth's Groans, &c. describes the 1750 London earthquakes, and was available for sale by the author in 1756, so I'm not accepting that it was written by a guy who died in 1730 regardless of what Allibone says. —Beleg Tâl (talk) 23:20, 12 September 2024 (UTC)Reply
The British Museum Catalogue lists the two as separate, as Duncan Campbell of Holbourne, with three works (Time's Telescope, Earth's Groans and the Poem upon Tea). MarkLSteadman (talk) MarkLSteadman (talk) 23:49, 12 September 2024 (UTC)Reply
@MarkLSteadman could you send me a link to this catalogue entry? I haven't been able to find it. Their search engines are a labyrinth lol —Beleg Tâl (talk) 17:27, 17 September 2024 (UTC)Reply
https://www.google.com/books/edition/British_Museum_Catalogue_of_printed_Book/c9cQ4B2JBBsC pg. 206. MarkLSteadman (talk) 17:30, 17 September 2024 (UTC)Reply
Awesome ty :) I was looking here lol —Beleg Tâl (talk) 17:32, 17 September 2024 (UTC)Reply
[edit]

I have 'page links displayed' set on and 'page links beside text'. In Firefox 130.0 (64 bit) they are no longer displayed. I've checked Edge (128.0.2739.67 (Official build)) and they display and work fine there. Chrisguise (talk) 12:36, 12 September 2024 (UTC)Reply

Apologies - they seem to have started working again.
Chrisguise (talk) 12:49, 12 September 2024 (UTC)Reply

Request for admin assistance for an image deletion

[edit]

Could an admin please delete https://en.wikisource.org/wiki/File:Fawkner.jpg ? I have now (correctly) uploaded it to commons. Thanks and apologies. CharlesSpencer (talk) 15:15, 13 September 2024 (UTC)Reply

For such images, tag then with {{sdelete|A1}} (more info at WS:CSD) (and for admin requests, post them at WS:AN). Cheers, — Alien  3
3 3
15:48, 13 September 2024 (UTC)Reply
DoneBeleg Tâl (talk) 16:04, 13 September 2024 (UTC)Reply

corrections

[edit]

There are many misspellings in the pdf format of this page one is on page 176 item 63 and it's written Lime and I believe it should be time. 24.189.233.205 23:42, 15 September 2024 (UTC)Reply

Which page are you talking about here? —Justin (koavf)TCM 23:43, 15 September 2024 (UTC)Reply
The page is that the PDF was downloaded was this one: https://en.wikisource.org/wiki/Pocket_Manual_of_Rules_of_Order_for_Deliberative_Assemblies 24.189.233.205 00:09, 16 September 2024 (UTC)Reply
Fixed it, it was indeed an OCR error at Page:Pocket Manual of Rules of Order for Deliberative Assemblies (1876).djvu/168. You can also help fixing pages, we're constantly looking for volunteers. (readding this section, as it's not usually done to delete sections that quickly, and it keeps other people from answering). — Alien  3
3 3
05:37, 16 September 2024 (UTC)Reply

Replace the Source File

[edit]

Hello. I created the "Comparative Vocabularies of Barma, Maláyu and Thai" index yesterday, but today I found that the quality is quite bad and the source file was already deleted from Internet Archive. I found a better quality source file from Google Books. How to replace the existing source file with the better one? Thank you. Mbee-wiki (talk) 05:40, 16 September 2024 (UTC)Reply

Weird syntax issue?

[edit]

Could someone please help me figure out why the following text is being displayed on a single line?

{{lang block|la|
{{xxx-larger|APOLOGIA}}

{{x-larger|Confessionis Augustanae.}}
}}

APOLOGIA

Confessionis Augustanae.

Beleg Tâl (talk) 17:22, 17 September 2024 (UTC)Reply

{{Lang block}} is a div and {{xxx-larger}} and {{x-larger}} and spans. A div is a block-level element, like a paragraph and a span is an inline element. If you want to make a line break in the middle, you can use {{br}}. —Justin (koavf)TCM 17:25, 17 September 2024 (UTC)Reply
To clarify, I am trying to figure out why the empty line (\n\n) is not being parsed as a paragraph break. As you say, I could put a <br> for a line break, but that doesn't answer the question of why the double line isn't being parsed as expected. If I use {{lang block/s}} and {{lang block/e}} instead of {{lang block}}, it works as expected. —Beleg Tâl (talk) 17:30, 17 September 2024 (UTC)Reply
Near as I can tell, this is a product of how Module:Lang has the feature local inline = yesno(args.inline or "yes") and the default value is no to strip out or suppress certain elements. Compare:
{{lang block|inline=yes|la|
{{xxx-larger|APOLOGIA}}
{{x-larger|Confessionis Augustanae.}}
}}
Which results in:
APOLOGIA
Confessionis Augustanae.
Which I believe is the outcome you want. —Justin (koavf)TCM 17:43, 17 September 2024 (UTC)Reply
Huh, that seems to be it, though I find it very unintuitive that the feature allowing it to behave as expected for a block element is to specify inline=yes lol. Thanks! —Beleg Tâl (talk) 17:48, 17 September 2024 (UTC)Reply
This is a bug in the way the template is coded. I recently fixed {{asc block}}, which had the same issue. Templates of the form
<div ... >...</div>
Have an issue with paragraph breaks.
However, templates like
<div ... >
...
</div>
Do not have this issue.
In this case, I added \n's in two places, and now it works. — Alien  3
3 3
18:07, 17 September 2024 (UTC)Reply
You didn't fix it. The side effects of your change have broken over 2000 pages!.. Next time ask someone to check your code FIRST!. ShakespeareFan00 (talk) 18:31, 17 September 2024 (UTC)Reply
Could you please be more specific and explain which calls adding whitespace broke, and how? Thanks, — Alien  3
3 3
18:35, 17 September 2024 (UTC)Reply
By adding in the "\n" for both DIV and SPAN varaints of lang, you put whitespace inside a SPAN which the parser really really doesn't like. You should be checking for the block variant of the template/module call and only applying the "\n" on the block variant. ShakespeareFan00 (talk) 18:38, 17 September 2024 (UTC)Reply
Ooo, forgot that, sorry. will do right away. — Alien  3
3 3
18:41, 17 September 2024 (UTC)Reply
@ShakespeareFan00: Forgot to add text if inline. In sandbox, what do you think now? — Alien  3
3 3
18:50, 17 September 2024 (UTC)Reply
Looks good. But I'd seek an administrator to review your code first.. ShakespeareFan00 (talk) 18:52, 17 September 2024 (UTC)Reply
A side note, but to avoid future reckless editing, maybe also request protection of module? Looks high-traffic enough to me. — Alien  3
3 3
18:54, 17 September 2024 (UTC)Reply
 Support Protection. ShakespeareFan00 (talk) 18:55, 17 September 2024 (UTC)Reply
As @Alien333 said, this seems to be a general issue with line spaces within div elements. I have reproduced it outside of any template, at User:Beleg Tâl/Sandbox#Div bug?. I think it should be reported to Phabricator, and I'll open a bug later if I don't see one already. —Beleg Tâl (talk) 18:50, 17 September 2024 (UTC)Reply

Help:Index page status colors changed

[edit]

My index page status colors of red and yellow changed to beige and pink, and I have no idea what I touched/changed to cause this. This is on en.wikisource but is normal on fr.wikisource. — ineuw (talk) 04:44, 19 September 2024 (UTC)Reply

See Wikisource:Scriptorium#Proofread_Page_colors_have_faded... —Justin (koavf)TCM 04:46, 19 September 2024 (UTC)Reply
Much thanks. Is there a current solution? — ineuw (talk) 04:57, 19 September 2024 (UTC)Reply
  1. Go to User:Ineuw/common.css
  2. Copy User:Duckmather/common.css
  3. Save and maybe hard refresh
Justin (koavf)TCM 05:02, 19 September 2024 (UTC)Reply
Thanks. It's working now. — ineuw (talk) 05:21, 19 September 2024 (UTC)Reply