Wikisource:Scriptorium/Archives/2022-05

From Wikisource
Jump to navigation Jump to search
Warning Please do not post any new comments on this page.
This is a discussion archive first created in , although the comments contained were likely posted before and after this date.
See current discussion or the archives index.

Celebrating One Year of the Monthly Challenge

Today, we’re celebrating the one-year anniversary of the Monthly Challenge. Despite a fair amount of skepticism at the start, the Monthly Challenge has proven itself a roaring success. In one year, we processed 53468 pages with 33340 proofread and 18428 validated. This accounts for about 17% of all the contributions to enWS in the past year. We’ve proofread and transcluded hundreds of works ranging from Old English to the Twentieth Century including all the novels of the Brontë sisters. In addition to proofreading, we’ve reduced the backlog of proofread texts that have not been transcluded from almost 750 to just above 300. None of this would have been possible without the amazing users like you who contributed throughout the year. There are far too many to mention and I’m sure that I’ll miss somebody, but I would like to especially thank Inductiveload for his amazing programming that has made this possible and Chrisguise, Tylopous, TeysaKarlov, MarkLSteadman, MER-C, Stamlou, ‎ ShakespeareFan00, Sp1nd01, Xover, and many more for all their contributions. You are truly what makes enWS work. I’m deeply grateful to every user who contributed to making this Monthly Challenge such a success during its first year.

Of course, much work remains to be done. Some of the titles made little progress despite their overall importance. So, we still have a long way to go. I invite everyone to head over to the Monthly Challenge page and help make the second year even better than the first. Languageseeker (talk) 17:14, 1 May 2022 (UTC)

1.5 million proofread pages

On 25 April, @Notsquaregarden: proofread Page:United States Statutes at Large Volume 5.djvu/555, which was our 1.5 millionth page to be proofread. We achieved 1 million on 19 May 2019, so have proofread half a million pages in a little under 3 years. Over one third of the pages have been validated. Beeswaxcandle (talk) 07:23, 1 May 2022 (UTC)

April Monthly Challenge

The Monthly Challenge continues to deliver! In April, the contributors achieved about 6000 processed pages, which is three times the basic target of 2000. Over 30 indexes achieved status promotion to proofread or validated. That's over one work per day.

Thanks to all who made this excellent result possible: Not only by proofreading, validating, and transcluding, but also by answering requests for help, nominating new works, helping with administration, running bots, supplying missing tables, images, and scores...

This month, the MC enters its second year with a wide range of new texts to work on. Everyone can join and help making it a success!--Tylopous (talk) 06:47, 1 May 2022 (UTC)

Editing news 2022 #1

Read this in another language • Subscription list for this multilingual newsletter

New editors were more successful with this new tool.

The New topic tool helps editors create new ==Sections== on discussion pages. New editors are more successful with this new tool. You can read the report. Soon, the Editing team will offer this to all editors at the 20 Wikipedias that participated in the test. You will be able to turn it off at Special:Preferences#mw-prefsection-editing-discussion.

Whatamidoing (WMF) 18:56, 2 May 2022 (UTC)

Tech News: 2022-18

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • On all remaining wikis (group 2), the software to play videos and audio files on pages has now changed. The old player has been removed. Some audio players will become wider after this change. The new player has been a beta feature for over four years. [1][2]

Changes later this week

  • The new version of MediaWiki will be on test wikis and MediaWiki.org from 3 May. It will be on non-Wikipedia wikis and some Wikipedias from 4 May. It will be on all wikis from 5 May (calendar).

Future changes

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:33, 2 May 2022 (UTC)

New competition on English Wikipedia and related SiteNotice request

A popular article writing competition CEE Spring (about Central and Eastern Europe; now with special subcategory about Esperanto) is happening on the English Wikipedia until the 31st May 2022. I warmly invite you to participate, write some article and win a valuable prize! If you have question, I will happily answer it on the competition page talk.

Also, for more wide outreach, I have just asked for a CentralNotice, which should appear also in this project. If you have a comment on the request, you are welcome to write it on the request page. --KuboF Hromoslav (talk) 18:29, 3 May 2022 (UTC)

Language templates

The template {{Greek}} is broken as of this evening. It is inserting a line return that shouldn't be there. No changes have been made to the template directly, so I assume a Module is the culprit.

You can see the broken template effects on The Suffix -μα in Aristophanes where the entire text is borked. --EncycloPetey (talk) 04:10, 6 May 2022 (UTC)

The problem seems to have been caused by the edit to {{Lang}}, which I have reverted in order to repair all the affected works. --EncycloPetey (talk) 04:13, 6 May 2022 (UTC)
Sorry about that! I'm pretty sure the issue was a newline before the </includeonly>. I've tested that in Template:Sandbox and Wikisource:Sandbox and that should fix it, but given that I didn't catch the last error I'm hesitant to push this change without someone else taking a look. —CalendulaAsteraceae (talk • contribs) 01:01, 8 May 2022 (UTC)

Tech News: 2022-19

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

Problems

  • Last week, there was a problem with Wikidata's search autocomplete. This has now been fixed. [7]
  • Last week, all wikis had slow access or no access for 20 minutes, for logged-in users and non-cached pages. This was caused by a problem with a database change. [8]

Changes later this week

Future meetings

  • The next open meeting with the Web team about Vector (2022) will take place on 17 May. The following meetings are currently planned for: 7 June, 21 June, 5 July, 19 July.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:22, 9 May 2022 (UTC)

Editing interface issue.

I have been experiencing an interface issue for a few weeks when editing pages. I'm not sure if this is an issue with my PC (Win 10 and Latest Firefox) or maybe a setting for my editing interface.

What happens is when I am editing a page the bar containing the dropdown selections (accents etc.) is sometimes above the bar with Bold, Italics etc., and more often than not after the first use appears below the footer editing window at the bottom of the page. It seems to move fairly randomly, its sometimes at the top, sometimes at the bottom of the page. (I don't know the correct terminology for these bars. I have also tried an edit and see the same issue with firefox on an ubuntu pc.)

Is anyone able to suggest a fix for the issue so that the bar remains at the top of the page? Sp1nd01 (talk) 12:11, 9 May 2022 (UTC)

Something I’m facing too. Latest Firefox on Fedora Linux. Ciridae (talk) 12:26, 9 May 2022 (UTC)
It's a gadget called CharInsert and is supposed to be at the bottom of the edit screen. However, there seems to be a conflict with the Editing toolbar. I'm also Win 10 and latest Firefox, and when I've got the Editing Toolbar turned off, CharInsert is in the correct place. When on, it varies in location. Note, that this behaviour only occurs when editing in the Page: namespace, so there's also involvement from ProofreadPage. Beeswaxcandle (talk) 18:39, 9 May 2022 (UTC)
Thanks for the explanation, at least I now know its not an issue with my PC. Sp1nd01 (talk) 05:49, 10 May 2022 (UTC)

Issues with "New Wikitext Editor" Beta

Recently, due to some recent update, whenever the 2017 Wikitext Editor is enabled in beta, in every page but Index and Page namespaces, they become nearly impossible to edit, due to being unable to place my curser and actually have it appear where needed.

For example, I can click in the middle of a word, and the I bar will appear on the next line down, or 3 words back, and characters will appear there.

I tried enabling and disabling all combos of gadgets and other beta features, but everything works fine until that specific one is enabled. Any news on a fix would be appreciated. Reboot01 (talk) 01:13, 11 May 2022 (UTC)

Alternatives to editing in the page namespace?

Is there anyone here who proofreads offline and pastes the results in the page? I have a problem ever since the "new" Proofreading module does not offer this option.

I am working on the four volume "Africa" by Elisèe Reclu. These volumes have images on every 2nd page, over 1,000 images. To see the text below the page is both problematic and time consuming. This now requires sliding and then manipulating to make the text below the image readable.Ineuw (talk) 02:31, 11 May 2022 (UTC)

Strong's Exhaustive Concordance

Why do several of the entries in the Hebrew portion of the dictionary contain "NONE" instead of the actual word? See this search query. I wanted to use this for something simple, but because of these omissions I'm forced to find an alternative.

Other than that (which only affects a minority of entries, to be fair), the transcription seems to be useful, but I haven't compared it for accuracy against the original book. 98.170.164.88 08:46, 13 May 2022 (UTC)

It was probably entered from another website, like a Project Gutenberg or Faded Pages equivalent maybe, with some kind of script. I assume the NONE is perhaps something to do with a None type in a programming language, where perhaps there was a Unicode error with some Hebrew entries, or something similar. Furthermore, the work Strong's Exhaustive Concordance does not meet our modern Wikisource standards because it is not scan-backed and there is no information given on the source, so there is still a huge amount more work to be done anyway. (But it was entered in 2021 so I'm skeptical as to why it was done this way.)
I'm sorry you had this experience, but please keep in mind that Wikisource's content is entered entirely by volunteers and the completion of anything is not mandatory, nor can it always be expected. And there is, unfortunately, a very small contributor base. But those of us who are active here do work very hard and try our best at what we do.
Pinging @Bobdole2021:, the one responsible for the initial transcription. PseudoSkull (talk) 14:32, 13 May 2022 (UTC)
I was not trying to be harsh, just highlighting a low-hanging fruit opportunity for improvement. Sorry if it came across the wrong way. Wikisource is great, and, for my purposes, I even like Wikisource's version of Strong's over most other online versions (ignoring this issue). It does make me wonder whether any manual oversight went into checking the text, though, and if not maybe there are less obvious errors.
I'd be willing to go through and fix these NONEs manually if no one else volunteers. But whoever generated it may be able to fix the issue more efficiently. There are other digitized versions of the book, so you can easily search an H-number and find the original Hebrew word with diacritics. 98.170.164.88 15:59, 13 May 2022 (UTC)
The original text can be found here: https://www.google.com/books/edition/The_Exhaustive_Concordance_of_the_Bible/3TBGAQAAMAAJ?hl=en&gbpv=0 . I'm forgetting how I put together that particular data set. So unfortunately I don't have an easy fix for replacing those NONE values with the correct ones. Bobdole2021 (talk) 16:29, 13 May 2022 (UTC)
Here's a Python script I hacked together to do the job: [10]. It generates the full page text, replacing NONE with the correct Hebrew word. You can change which page it operates on by editing the variable on the second nonempty line. 98.170.164.88 17:27, 13 May 2022 (UTC)
There's a framework called PyWikibot for doing automated edits.. If you know python it might be worth looking at...ShakespeareFan00 (talk) 17:47, 13 May 2022 (UTC)

For now I've gone ahead and made the edits suggested by the script above. (As I was doing so, I looked over the changes to make sure nothing obviously wrong popped out). I think this is resolved. 98.170.164.88 18:52, 13 May 2022 (UTC)

Poll regarding Third Wikisource Triage meeting

Hello fellow Wikisource enthusiasts!

We will be organizing the third Wikisource Triage meeting in the last week of May and we need your help to decide on a time and date that works best for the most number of people. Kindly share your availabilities at the wudele link below by 20th May 2022:

https://wudele.toolforge.org/ctQEP3He1XCNullZ

Meanwhile, feel free to check out the page on Meta-wiki and suggest topics for the agenda.

Regards

Sam Wilson (WMF) and Satdeep Gill (WMF)

Sent via MediaWiki message delivery (talk) 03:38, 14 May 2022 (UTC)

Let's talk about the Desktop Improvements

Hello!

Have you noticed that some wikis have a different desktop interface? Are you curious about the next steps? Maybe you have questions or ideas regarding the design or technical matters?

Join an online meeting with the team working on the Desktop Improvements! It will take place on 17 May 2022 at 12:00 UTC and 19:00 UTC on Zoom. Click here to join. Meeting ID: 86217494304. Dial by your location.

Agenda

  • Update on the recent developments
  • Questions and answers, discussion

Format

The meeting will not be recorded or streamed. Notes will be taken in a Google Docs file. Olga Vasileva (the Product Manager) will be hosting this meeting. The presentation part will be given in English.

We can answer questions asked in English, Italian, Polish; also, only at the first meeting: Farsi, Vietnamese; only at the second meeting: Portuguese, Spanish, Russian. If you would like to ask questions in advance, add them on the talk page or send them to sgrabarczuk@wikimedia.org.

At this meeting, both Friendly space policy and the Code of Conduct for Wikimedia technical spaces apply. Zoom is not subject to the WMF Privacy Policy.

We hope to see you! SGrabarczuk (WMF) (talk) 05:02, 14 May 2022 (UTC)

Tech News: 2022-20

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

  • Some wikis can soon use the add a link feature. This will start on Wednesday. The wikis are Catalan Wikipedia, Hebrew Wikipedia, Hindi Wikipedia, Korean Wikipedia, Norwegian Bokmål Wikipedia, Portuguese Wikipedia, Simple English Wikipedia, Swedish Wikipedia, Ukrainian Wikipedia. This is part of the progressive deployment of this tool to more Wikipedias. The communities can configure how this feature works locally. [11]
  • The Wikimedia Hackathon 2022 will take place online on May 20–22. It will be in English. There are also local hackathon meetups in Germany, Ghana, Greece, India, Nigeria and the United States. Technically interested Wikimedians can work on software projects and learn new skills. You can also host a session or post a project you want to work on.
  • The new version of MediaWiki will be on test wikis and MediaWiki.org from 17 May. It will be on non-Wikipedia wikis and some Wikipedias from 18 May. It will be on all wikis from 19 May (calendar).

Future changes

  • You can soon edit translatable pages in the visual editor. Translatable pages exist on for examples Meta and Commons. [12]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:58, 16 May 2022 (UTC)

Info please on the PDF maker on Commons

Bore da / Good morning! Why does the 'Download as a PDF' tool, on Commons, only download the 1st 200 images, or have I missed something? I need to pdf all images in this category for use on WS. Many thanks! Llywelyn2000 (talk) 08:59, 16 May 2022 (UTC)

@Llywelyn2000 As I understand it, the PDF maker tools are pretty poorly maintained (see mw:Reading/Web/PDF Functionality and w:Help:Books), so I'm unsurprised that it doesn't work for this rather niche use. If you know of a way to mass download the whole category, the images would probably be easy to organize into djvu format with something like DjVuLibre + ScanTailor (but I don't have any experience with that). I just realized that you uploaded the images to Commons in the first place, in which case (if you still have them saved) it might be worthwhile to ask for advice from Scan Lab participants on the matter, if you're curious about making djvu files.
In this instance, though, I think the issue is moot because the source at Digital Bodleian provides a pdf download and a zip file of individual jpeg images (which are apparently higher-resolution than the ones on Commons). Shells-shells (talk) 05:41, 17 May 2022 (UTC)
@Llywelyn2000 Just realized (silly me, I should have checked the existing files more thoroughly) that c:File:Red Book of Hergest - Jesus College MS 111.djvu already exists. Does this work for your purposes? Shells-shells (talk) 06:22, 17 May 2022 (UTC)
Many thanks Shells-shells for such a thorough answer; I'm relatively new to WS. I was searching for a pdf file as I need to create an index page; will a djvu file do the same, or does it need to be converted into pdf? Thanks again! I asked on Commons a week a go, and no reply received. Now I know about Scan Lab! Thanks / Diolch! Llywelyn2000 (talk) 06:43, 17 May 2022 (UTC)
@Llywelyn2000: djvu files work well for Index pages, and are often better than pdf because the OCR layer is better. Converting one to the other is not necessary. Beeswaxcandle (talk) 08:10, 17 May 2022 (UTC)
@Beeswaxcandle: Thanks! Llywelyn2000 (talk) 09:36, 17 May 2022 (UTC)

New transclusion checker tool available (please test!)

A new tool to help check the transclusion status of the pages in an Index: is now available. This is a JavaScript-based tool, so you enable it in the Gadgets section of your Preferences. You activate it with the "Check transclusion" link in the left toolbar, and it works by giving colour indications on each page in the pagelist to tell you its transclusion status. There is documentation available at: Help:Gadget-transclusion-check.

The current transclusion checker tool—toolforge:checker, activated with the little icon in the top right indicator area—was recently broken for several weeks (I think). It's been fixed now, but it's somewhat fragile to changes in Proofread Page and it's maintained on a best effort / volunteer basis (and the maintainers have way more stuff to take care of than hours in the day). And while it works great when it works, it's not the most modern or elegant user interface. The above Gadget is an attempt to address both issues: it's an on-wiki script that anyone with some JavaScript knowledge can maintain, uses the MediaWiki Action API (which is supported by the WMF), and displays the transclusion status in an at least nominally more modern way.

I am therefore requesting that as many people as possible test this tool with a view to eventually replacing the old tool. Feedback, good or bad, here (or on my user talk page if you prefer) would be very appreciated. Particular points of interest: is the visual presentation clear and intuitive? How is it most convenient to activate the tool (left sidebar, the old icon, hooked up to the "Transclusion status" field, etc.).

And credit where credit is due: this is based on Inductiveload's scan transcludes.js. All subsequent bugs and misfeatures are my fault. Xover (talk) 13:05, 12 May 2022 (UTC)

Feedback: the visual presentation is clear, and this is a lot more convenient to use than the old tool! The "Transclusion status" field would be the most convenient way to activate it.
(I'm ambivalent between activating the tool from the left sidebar and activating it from the old icon. The left sidebar link is more clear since it's text, but it's small and doesn't stand out much from the other links. The icon is easier to find on the page but harder to distinguish because the only one of those icons I can remember/identify is the one for purging the file.) —CalendulaAsteraceae (talk • contribs) 01:29, 17 May 2022 (UTC)
@CalendulaAsteraceae: Thanks for the feedback! I've added a small button next to the transclusion status field, which should make it a lot more discoverable. I've also fixed the support for checking pages that are not yet created (but which may still have been transcluded).
I see there are twelve people who have enabled this Gadget now (but I can't see who), and absent negative feedback I'm going to assume they are reasonably happy with it. On that basis I am going to wait a little bit and then make this gadget default (turned on for everyone), and at the same time override the click action on the old indicator icon (the link to the old checker). After a while running like that, if there are no complaints, I'm going to turn off the old checker icon completely. And remove the sidebar link so the button by the transclusion status will be the only way to use it.
In the meantime, I would greatly appreciate all feedback, even if it's just "Looks ok.", or "I have no opinion."; and of course particularly if you are unhappy or have concerns. Xover (talk) 11:52, 21 May 2022 (UTC)
@Xover I only have two (rather petty) UI quibbles with the tool. First, I think I'd prefer the button to be a simple on/off toggle instead of requiring a shift-click to turn the tool off. Second, I'm not so sure about how the red indicator flips from meaning "This page is transcluded" to "This page is not transcluded" between not proofread/without text/problematic pages and proofread/validated pages. It might be better to make it simply indicate the transclusion status of a page, disregarding whether pages "should" or "should not" be transcluded. Shells-shells (talk) 07:10, 22 May 2022 (UTC)
@Shells-shells: Thanks! I'll think about the toggle thing: for (primarily) technical reasons that's not a natural interaction model for this, but I'll mull it over and see if I can come up with something sensible. Regarding recommendation vs. plain transclusion status, I'll test that in a sandbox but I worry that'll be too noisy a way to convey the information. The point is to convey which pages needs checking and potentially some action taken, and consequently also to make all the pages that are fine just fade into the background. If it just indicates status then every page will need some kind of indicator, and the should / should not logic must happen in the brain of the person using it (and making humans do something a computer could do just as well is not a good use of resources). Xover (talk) 07:36, 22 May 2022 (UTC)
@Xover I don't know how the toggle buttons in the sidebar (are those called "portlets"?) do it, but I guess those would probably be the ones worth looking at. For simple toggle logic, here's an idea: 
var checkTransclusion = true; 
$(checkPortlet).click(function (e) {
  ...
  if (checkTransclusion) {
    $('.prp-index-pagelist').addClass('transclusion-check');
  } else {
    $('.prp-index-pagelist').removeClass('transclusion-check');
    checkTransclusion();
  }
  checkTransclusion = !checkTransclusion;
}
On the second point, I just think the only pages which should not be transcluded are those completely without content (at the very least, problematic pages can often be justifiably transcluded), so the only page status that should show red on transclusion is "without text".
Anyway, this is a lovely and completely user-friendly gadget. Again, these are only petty quibbles of mine—I have no real complaints with it. Shells-shells (talk) 08:28, 22 May 2022 (UTC)
@Shells-shells: Ah, that's a different issue. If pages that are "Problematic" or "Not proofread" have been transcluded, the index should not be marked as "Fully transcluded" because it is still missing content. In fact, it is pages marked as "Without text" that can (and often is) transcluded and which do not prevent tagging the index as "Fully transcluded" (the script highlights them, but it's up to the human to decide whether to do anything about these: they should ideally be excluded, but it may be more effort than it's worth).
In any case, the feedback is very much appreciated (and even if I don't agree or it can't be implemented it is still helpful)! Xover (talk) 09:29, 22 May 2022 (UTC)
@Xover Looks great to me! Thanks for your work on this. Languageseeker (talk) 13:14, 22 May 2022 (UTC)

Invitation to join the third Wikisource Triage meeting (28th May 2022)

Hello fellow Wikisource enthusiasts!


We are the hosting the Wikisource Triage meeting on 28th May 2022 at 11 AM UTC / 4:30 PM IST (check your local time) according to the wudele poll. We will be welcoming some developers who contributed to Wikisource related tasks during the recently concluded Indic Hackathon.

As always, you don't have to be a developer to participate in these meetings but the focus of these meetings is to improve the Wikisource infrastructure.

If you are interested in joining the meeting, kindly leave a message on sgill@wikimedia.org and we will add you to the calendar invite.

Meanwhile, feel free to check out the page on Meta-wiki and suggest any other topics for the agenda.

Regards

Sam Wilson (WMF) and Satdeep Gill (WMF)

Sent using MediaWiki message delivery (talk) 03:39, 23 May 2022 (UTC)

Tech News: 2022-21

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • Administrators using the mobile web interface can now access Special:Block directly from user pages. [13]
  • The www.wiktionary.org portal page now uses an automated update system. Other project portals will be updated over the next few months. [14]

Problems

  • The Growth team maintains a mentorship program for newcomers. Previously, newcomers weren't able to opt out from the program. Starting May 19, 2022, newcomers are able to fully opt out from Growth mentorship, in case they do not wish to have any mentor at all. [15]
  • Some editors cannot access the content translation tool if they load it by clicking from the contributions menu. This problem is being worked on. It should still work properly if accessed directly via Special:ContentTranslation. [16]

Changes later this week

  • The new version of MediaWiki will be on test wikis and MediaWiki.org from 24 May. It will be on non-Wikipedia wikis and some Wikipedias from 25 May. It will be on all wikis from 26 May (calendar).

Future changes

  • Gadget and user scripts developers are invited to give feedback on a proposed technical policy aiming to improve support from MediaWiki developers. [17]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

00:21, 24 May 2022 (UTC)

Lint -errors (High priority Misnesting)

Only 8 entries left:- https://en.wikisource.org/wiki/Special:LintErrors/misc-tidy-replacement-issues?namespace=0&titleprefix=

But they seem to be items I didn't feel comfortable making edits to for various reasons. Are there any contributors here able to complete the effort to reduce a backlog that's existed for a few years? ShakespeareFan00 (talk) 09:05, 24 May 2022 (UTC)

@ShakespeareFan00: Done! Tracking down which of the transcluded pages had errors on them was kind of a pain; does anyone know the reasoning behind not having page-namespace pages show up in the linter? —CalendulaAsteraceae (talk • contribs) 04:13, 25 May 2022 (UTC)
I suspect it might be the differences in how references are rendered in page vs. main avoiding a span around the divs... MarkLSteadman (talk) 04:42, 25 May 2022 (UTC)
That would make sense! —CalendulaAsteraceae (talk • contribs) 05:26, 25 May 2022 (UTC)

Template import

I'm working on a report that uses a bunch of tables. Some of the headings at the top have the text rotated 90°. I found Template:Rotate, but I think there's a better option on the English Wikipedia that could be imported and adapted here: w:Template:Vertical header. Any thoughts? Imzadi 1979 → 18:07, 29 May 2022 (UTC)

@Imzadi1979 we don't usually strive to reproduce things like that where there original intent was just to fit onto a fixed-size piece of paper. Firstly, sideways text is harder to read, and secondly, CSS support for it is pretty poor and all the ways people (including me) have tried over the years end up being far more trouble than they are worth. I suggest just to have the text "right-way up". Inductiveload—talk/contribs 18:44, 29 May 2022 (UTC)

The Collected Works of Mahatma Gandhi

Hi, As I am finishing importing the files to Commons (having already done the Gujarati and Hindi versions), I have (again) a question about the best way to handle this. I found 2 different scans of this work. The first ones are 1,239 × 1,906 pixels scans with an intrusive watermark (e.g. [18], the others are 2,025 × 3,043 pixels (e.g. vol. 3), but not really scans, but rather recreation of the books, after removing blank pages. The second set is of better quality and has no watermark, but not exactly a copy of the original work, although the text is the same. Which set do we want for proof reading on WS? Thanks, Yann (talk) 09:58, 26 May 2022 (UTC)

@Yann: I don't understand what you mean by "recreation of the books"? Scans are just a technical representation of a published work, and as such should reflect what was actually published. If the latter scan does not match what was actually published on paper then we can't use it. Xover (talk) 07:16, 28 May 2022 (UTC)
@Xover: I am not sure, as there is no information on the source website. But my deduction after examining the files is that these are the exact same text, but are not technically scans. This set does reflect the text that was actually published, but not the formating of the original books. Thanks, Yann (talk) 12:20, 29 May 2022 (UTC)
@Yann: The scan at gandhiserve.net appears to be a second edition published in June 1979, by the Navjivan Trust in Ahmedabad. I cannot judge its fidelity to Gahndi's original writings, but I see no obvious reason to suspect that the scan doesn't match the physical book as it was then published. The scan at IA looks like the April 1960 first edition of the same work, except scanned by someone even less skilled than your average Google Books scanner, and thus has major problems. Of the two, I would be most inclined to trust the scan at gandhiserve.net for the simple reason that it appears to have been scanned by someone with a modicum of skill and care, which usually means they have tried to be faithful to the work they are preserving. Since it is also, modulo that annoying watermark, the technically superior scan (higher resolution, full colour, consistent page size, etc.) my suggestion would be to focus on that.
PS. I'll assume you have the copyright issue in hand (since we're talking books with a 1960–1979 printed copyright date), so I haven't looked into that at all. Xover (talk) 07:13, 30 May 2022 (UTC)
OK thanks. Then I will use the set from gandhiserve.net to create DjVu files. I will delete the volumes not yet in the public domain after uploading. Yann (talk) 08:00, 30 May 2022 (UTC)
Are you all set for tools to create DjVu with an OCR text layer? Xover (talk) 08:05, 30 May 2022 (UTC)
I am not sure what you mean, but I create DjVu after generating PDF from the online images. Yann (talk) 20:57, 30 May 2022 (UTC)

Template:Advertisements

The template {{Advertisements}} is no longer a collapsed section when a page is loaded, neither can it be collapsed. See (e.g.) Snow-Bound: A Winter Idyl. I do not see any recent changes to the template or to the templates it calls. There may be a Module or update that has changed the functionality. --EncycloPetey (talk) 18:13, 26 May 2022 (UTC)

@EncycloPetey: Fixed, I think. It was using some seriously obsolete code and was only still working because we had some stuff hardcoded in site-specific code. When that got cleaned up this template just fell over. I've updated it to use the current implementation now.
PS. Collapsible content (irrespective of implementation) is not the best practice for several aspects of accessibility, so I recommend against using this template for any new works added. Xover (talk) 18:45, 27 May 2022 (UTC)
There is no "standard" for dealing with large Advertisements that appear among the Front Matter. Recommending against a workable practice isn't helpful if there are not suitable alternatives. --EncycloPetey (talk) 21:50, 29 May 2022 (UTC)
@EncycloPetey: Turn it on its head, rather: the basic state is to include the advertisements as they were published. Granted a lot of them are very large and annoyingly placed, but then, that was the case when they were originally published too. What I'm saying is that {{advertisements}} is not a "suitable alternative". But it's just my recommendation, and not even anywhere near the top of my list of hobby-horses, so you'll need to make up your own mind on that. Xover (talk) 06:44, 30 May 2022 (UTC)
I disagree about the "basic state". Advertisements are not part of the work proper, but are added by the publisher. Unlike ex libris book plates and library stamps, they were present when the book was printed, and there can be useful information about other publications by the same author, so they are more meaningful than marks printed solely for collating pages. But only just. There is a very broad spectrum of what is and isn't transcribed from scans, and not everyone here agrees about what to do for all of those items. --EncycloPetey (talk) 17:18, 30 May 2022 (UTC)

MediaWiki:IndexForm.js

I tried importScript('MediaWiki:IndexForm.js'); on edit page of Index page and it seems like this script is broken because it removes the Type dropdown instead. --Bebiezaza (talk) 13:54, 29 May 2022 (UTC)

@Bebiezaza nearly all the JS in the Mediawiki namespace that does not start with "Gadget-" is probably only for historical interest. If it's currently in use, it'd be a gadget. In this case, the script probably dates back to when the index edit form was generated entirely client side (these days, the form is created server side by the ProofreadPage extension). Inductiveload—talk/contribs 18:47, 29 May 2022 (UTC)
MediaWiki:IndexForm.js is not in use on enWS and hasn't been since 2018 (and is in fact entirely broken). Xover (talk) 06:49, 30 May 2022 (UTC)

Tech News: 2022-22

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • Advanced item In the AbuseFilter extension, an ip_in_ranges() function has been introduced to check if an IP is in any of the ranges. Wikis are advised to combine multiple ip_in_range() expressions joined by | into a single expression for better performance. You can use the search function on Special:AbuseFilter to locate its usage. [19]
  • The IP Info feature which helps abuse fighters access information about IPs, has been deployed to all wikis as a beta feature. This comes after weeks of beta testing on test.wikipedia.org.

Changes later this week

  • The new version of MediaWiki will be on test wikis and MediaWiki.org from 31 May. It will be on non-Wikipedia wikis and some Wikipedias from 1 June. It will be on all wikis from 2 June (calendar).
  • Some wikis will be in read-only for a few minutes because of a switch of their main database. It will be performed on 31 May at 07:00 UTC (targeted wikis).
  • The New Topic Tool will be deployed for all editors at most wikis soon. You will be able to opt out from within the tool and in Preferences. [20][21]
  • Advanced item The list=usercontribs API will support fetching contributions from an IP range soon. API users can set the uciprange parameter to get contributions from any IP range within the limit. [22]
  • A new parser function will be introduced: {{=}}. It will replace existing templates named "=". It will insert an equal sign. This can be used to escape the equal sign in the parameter values of templates. [23]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:28, 30 May 2022 (UTC)

'Transcribe text' script termination

If possible, I request that any person who is authorized to make a change, to add to the end of the Transcribe text script that termination should be in the textbox first row, and not somewhere in the browser window. — ineuw (talk) 02:32, 31 May 2022 (UTC)

Moved to Help. — ineuw (talk) 08:52, 4 June 2022 (UTC)

Categorization of Canadian statutes

I believe it would be best if there were a centralized mainspace umbrella for Canadian Statutes (similar to the one United States Statutes at Large uses). The way statutes are currently listed, there is no structure beyond "next section" and "previous section" links.

Since statutes are listed by reign and chapter in each volume, Wikisource should use the same system. For example, It would be useful if An Act for the organization of the Department of Marine and Fisheries of Canada should be moved to Canadian Statutes/31 Victoria/Chapter 57 while keeping a redirect from the short title of each bill. If anyone has any input, please let me know. I’m mender? :/ (talk) 17:30, 24 May 2022 (UTC)

  • I’m mender? :/: If the intent is to work from the Canadian Statutes out, then I think that would wise. The pattern you have is probably good for how to notate the laws. For this Act, and most others that don’t need to be split, the “Schedule” should be on the same page. For the United States Statutes, there are no redirection pages for the long titles of laws to the formal name; thus, I don’t think it is necessary for the Canadian Statutes, either. Of course, if any law is well-known by a certain title, a redirection should exist, but otherwise, it is not necessary, as a search for the title would reveal the full name anyway. For sidenotes, I would recommend using {{USStatSidenote}}, as it is optomized for use in statutes publications. TE(æ)A,ea. (talk) 18:05, 24 May 2022 (UTC)
    • TE(æ)A,ea.: Thanks for the recommendation. Only mainspace pages with a Short Title as their name will be used as redirect pages, and links to long titles will be adjusted manually. I’m mender? :/ (talk) 18:16, 24 May 2022 (UTC)
      Upon further consideration, pages in Statutes of Canada will be listed by Parliament and Session, as the year of the Gregorian calendar and the year of the reign of the monarch can be ambiguous (e.g. there are two sessions called "5 George V" and two sessions which take place in 1896). I’m mender? :/ (talk) 08:18, 30 May 2022 (UTC)
      Further update: The Statutes of Canada are now classified by year, in the same manner as more recent annual statutes. For instance, the edition titled Acts of the Parliament of the Dominion of Canada passed in the Session held in the Fourth year of the Reign of His Majesty King George VI being the First Session of the Nineteenth Parliament Begun and holden at Ottawa, on the Sixteenth day of May, 1940, and closed by Prorogation on the Fifth day of November, 1940, short title Statutes of Canada, 1940, 4 George VI will be located at Statutes of Canada/1940. I’m mender? :/ (talk) 22:49, 17 June 2022 (UTC)

Index:Memorials of Capt. Hedley Vicars, Ninety-seventh Regiment by Marsh, Catherine, 1818-1912.djvu

This section was archived on a request by CharlesSpencer (talk) 13:36, 13 May 2022 (UTC) Confirmed from two other editions that no text is missing

Apologies - I have not requested one of these before, so I will be a little bit more verbose than more experienced colleagues in an effort to get it right first time! I have two pages missing between /127 and /128, so I hope that my request is correctly formed as follows:

Starting at Page:Memorials_of_Capt._Hedley_Vicars,_Ninety-seventh_Regiment_by_Marsh,_Catherine,_1818-1912.djvu/128 until the end, please move the text by +2. Thank you. CharlesSpencer (talk) 13:14, 3 May 2022 (UTC)

Bizarrely, on consulting another version of the text, it appears that the typesetters may only have skipped two on the page numbers, while the text itself may in fact be complete! Please hold off until I can triangulate from further editions. Thanks. CharlesSpencer (talk) 13:27, 3 May 2022 (UTC)

Index:The future of Africa.djvu

This section was archived on a request by: --Mpaa (talk) 20:06, 12 May 2022 (UTC)

Starting at Page:The future of Africa.djvu/9 until the end, please move the text by +4. Languageseeker (talk) 06:07, 4 February 2022 (UTC)

Done Mpaa (talk) 21:22, 4 February 2022 (UTC)
@Mpaa Thank you!

Index:Incidents in the life of a slave girl.djvu

This section was archived on a request by: --Mpaa (talk) 20:06, 12 May 2022 (UTC)

[[Starting at Page:Incidents in the life of a slave girl.djvu/5 until the end, please move the text by +4. Languageseeker (talk 01:05, 5 February 2022 (UTC)

Done Mpaa (talk) 11:10, 5 February 2022 (UTC)
@Mpaa Thank you!

Index:A history of Hungarian literature.djvu

This section was archived on a request by: --Mpaa (talk) 20:06, 12 May 2022 (UTC)

Starting at Page:A history of Hungarian literature.djvu/3 until the end, please move the text by +4. Languageseeker (talk) 14:44, 16 April 2022 (UTC)

Done Mpaa (talk) 20:06, 12 May 2022 (UTC)
@Mpaa Thank You!

Index:Cambridge by lamplight - 9 woodcuts.djvu

This section was archived on a request by: — ineuw (talk) 02:32, 31 May 2022 (UTC)

Please move the backing file and associated images from commons to wikisource as it is by a UK author who died in 1975. 19:06, 30 May 2022 (UTC)

Done.--Prosfilaes (talk) 19:22, 30 May 2022 (UTC)}}

Clotel

Please move the pages from Index:Clotel, or, The President's daughter - a narrative of slave life in the United States (IA 70979078-9a98-41a4-8db9-1076b6b1186a).pdf to Index:Clotel (1853).djvu. The PDF is basically unreadable. Languageseeker (talk) 23:36, 22 May 2022 (UTC)

@Languageseeker: Thanks for finding more legible scans of this book! I went ahead and transferred the pages manually since there weren't very many of them. Would it be good to do a history fusion? —CalendulaAsteraceae (talk • contribs) 08:42, 29 June 2022 (UTC)
@CalendulaAsteraceae Thank you for transferring the pages and working on this text. I was very happy to find a better version of this book. I don't think that's its necessary to transfer the page history, but I'll mark the pdf for deletion now that the content has been preserved. Languageseeker (talk)
@Languageseeker: Neat, thanks. —CalendulaAsteraceae (talk • contribs) 07:42, 30 June 2022 (UTC)
This section was archived on a request by: Ciridae (talk) 04:54, 26 July 2022 (UTC)
Retrieved from "https://en.wikisource.org/w/index.php?title=Wikisource:Scriptorium/Archives/2022-05&oldid=12516297"