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 December 2021, although the comments contained were likely posted before and after this date.
See current discussion or the archives index.

Filter preventing good-will contributions?[edit]

The following discussion is closed:
No actionable points at Wikisource; complaints about the effects of global filters not felt at Wikisource may go to meta:Babel and about any other project's filters to the project in question

Absolutely any filter which prevents the good-will contribution of any potential contributor is counter the wikipedia ethos. It will be highly indicative if this comment is censored. 23:48, 17 December 2021 (UTC)[reply]

given how opaque filters are, you need to provide a screenshot or filter number to understand what you are talking about. we have global filters of proxy ip's and tor nodes, that are not under the control of admins here. i agree this is a major pain point where functionaries are betraying "anyone can edit" --Slowking4Farmbrough's revenge 00:45, 19 December 2021 (UTC)[reply]
Given the context of the original location of the comment, I assume "filter" here is meant in a barriers not blocking sense. (i.e. hurdles or difficulties that make it hard for people to contribute, even if relatively small, "filter out" people who are interested in making good-will contributions). MarkLSteadman (talk) 02:55, 19 December 2021 (UTC)[reply]
My only comment is that given the scope and long-term vision many people desire, expanding the size of the contributing community here would really help. I am not sure what analysis has been done either by looking at historical user behavior or via usability testing and to what extent changes there might help get more visitors to become contributors. MarkLSteadman (talk) 03:03, 19 December 2021 (UTC)[reply]
filters are the backend used by functionaries to fight abuse, and prevent a save. normally seen on some proxy ip's, or exceeding rate limit with quick statements in backround. normally accompanied by a big red screen, for example File:Abuse filter warnings, removal of information template, OTRS by non-OTRS member and unconstructive edit.png. --Slowking4Farmbrough's revenge 00:33, 22 December 2021 (UTC)[reply]
If you're hitting any filters at Wikidata or Commons, something is working as intended because you are not supposed to be editing there, since you are indef blocked. Inductiveloadtalk/contribs 07:17, 22 December 2021 (UTC)[reply]
funny, i have never hit a filter at commons or wikidata, so i guess they are not working. --Slowking4Farmbrough's revenge 00:18, 23 December 2021 (UTC)[reply]

Pictogram voting comment.svg Comment Seems a spurious complaint, and approaches trolling with its kicker. This IP address has not had abuse filters prevent them from editing nor spam abuselog, nor any deleted edits. Reviewing the DISALLOW edit filter log shows nothing that we would say is an unreasonable action in recent times. We deal with reasonable complaints, especially where our system inhibits good-will editing. That said there needs to be systems in place to prevent spam and bad-will editing, and perfect differentiation is non-existent. — billinghurst sDrewth 08:40, 19 December 2021 (UTC)[reply]

i agree it is too vague to be actionable. but veteran editors continue to get caught up, and are astonished. (be it filtering Amtrak, or African country phone networks) we need an improved filter standard of practice to simplify explaination and feedback. the unaccountability is not a good look, and you should expect periodic venting until filter use is improved. --Slowking4Farmbrough's revenge 02:52, 20 December 2021 (UTC)[reply]
We are not having veteran editors continue to get caught in abusefilters, and when we have a false positive, they are typically updated. — billinghurst sDrewth 12:40, 20 December 2021 (UTC)[reply]
i'm sure it is just a misunderstanding: When you try to get something done on @wikidata --Slowking4Farmbrough's revenge 00:39, 22 December 2021 (UTC)[reply]
There are no rate limited filters at Wikisource. What's your point? Inductiveloadtalk/contribs 06:42, 22 December 2021 (UTC)[reply]
I won't speak for WD abuse filters, well not here, so please limit local commentary to what we can address locally.

And MM is a big boy and knows wikis well enough to know the best way to resolve abusefilter issues. I would argue that whining about it on twitter while maybe comforting is not the best way to get an AF issue addressed. — billinghurst sDrewth 12:09, 22 December 2021 (UTC)[reply]

well, apparantly when you are running quick statements in the backround, and try to edit, you get this filter. or if you are editing at an editathon with lots of new editors (which i saw). MM dunking on wikidata is all very amusing, and clearly communication channels are strained. it would be very difficult to trip a rate limit here, but it is theoretically possible. thankfully, we do not have filter problems here, but the principle remains, that veterans trip them up from time to time, and work stops - the permission work arounds are so obtuse as to be non-existent. i would not say spurious, but rather "did not stick around long enough to find out" --Slowking4Farmbrough's revenge 00:16, 23 December 2021 (UTC)[reply]
This section was archived on a request by: Inductiveloadtalk/contribs 12:29, 23 December 2021 (UTC)[reply]

November Monthly Challenge[edit]

Wikisource laurier.svg

Hear ye! Hear ye! This November, the Monthly Challenge has smashed though all previous records! 6079 pages proofread, validated, or marked "no text", completely eclipsing the target of 2000 by a factor of three, and claiming a new monthly record by a margin of over two thousand pages! This represents over 25% of all the ~22000 pages processed in all of English Wikisource in November. More excitingly, the number of pages validated, 2275, accounts for over 50% of all validation undertaken this month, meaning that the Monthly Challenge is roughly twice as effective at validations-per-page than the site average. We also had over 100 pages processed every day of the month, except the 29th, which fell short by only 2 pages. We also broke the record for most pages proofread and processed in a day (286 and 416 respectively, on the 1st) and pages validated in a day (205, on the 2nd). In fact, we saw so much work being done that a server performance hot-spot was discovered (don't worry, it was fixed).

This amazing result appears to support the idea that a broad range of works in the challenge attracts more interest throughout the month. Thank you to everyone who has contributed, and special thanks to Languageseeker for again marshalling the challenge as works were completed.

Works proofread in November include:

Validated works:

Several works, previously completed but never transcluded, were also transcluded and rounded out:

Only one work expired without being completed:

Coming up in December are some very interesting new works, as well as continuations of series from last month:

An early precursor to the familiar maps fantasty worlds well as many more. There's something for everyone, so please come on in and help us smash more records! You can see the works included here. Nothing can chase away the wintry blues and ghosts of Christmas-almost-there like a nice, mince-pie-fuelled proofreading session!

Finally, as we are now a month away from Public Domain Day 2022 (a.k.a. New Year's day to those strange "normal" people), we are starting to collect works that will fall into the public domain for a special-edition challenge in January. Please submit ideas for 1926 works (and any other works entering the PD) on the nominations page.

Ho ho ho and merry proofreading, one and all! Inductiveloadtalk/contribs 14:54, 1 December 2021 (UTC)[reply]

How to name images without captions?[edit]

About half of the 120+ images in Index:The_Count_of_Monte-Cristo_(1887_Volume_1).djvu are without captions and are waiting to be uploaded. In my previous commons uploads, the text surrounding a captionless image provided context for the title and the caption.

These, with few exceptions, depict possibilities of situations from the illustrator's imagination. They are so irrelevant that they should be considered page decorations. I want to name and categorize these as such. e.g: COMC V1 D125 Page decoration.jpg.— Ineuw (talk) 05:41, 7 December 2021 (UTC)[reply]

@Ineuw: I would name these File:The Count of Monte-Cristo (1887 Volume 1), p. 49 illustration.jpg. That is, 1) use the same base name as the DjVu with which they are associated, 2) human readable without parsing "COMC", and 3) descriptive of what they are. On that last point, they are illustrations not "decoration" (decorations would be flourishes and fleurons and so forth) and spelling out distinguishes it from a possible image representing the whole scanned page (which may well be added on a collaborative / multi-project media repository). This naming schema can be extended to unnumbered plates as well:File:The Count of Monte-Cristo (1887 Volume 1), facing p. 49.jpg. Alternately, you can use each illustration's title from the list of illustrations. Xover (talk) 06:41, 7 December 2021 (UTC)[reply]
@Xover: I cannot accommodate your suggestion for several reasons. The first is that I don't want to create 100+ character titles. Especially, in an acronym driven universe such as Wikimedia and the web. Because this wasn't my upload and only focused on the images, I missed the list of illustrations. Much thanks for bringing it to my attention and will add them.
My use of book titles as acronyms goes back to my first uploads. At that time, I was warned on the commons that sufficient info is required in the title and the description, so I combined the two.
Every work I upload is properly categorized on the commons. This is the main category and this is the subcategory. I always use DjVu numbers because page numbers are not accurate. Every so often, they are duplicated or omitted. Also, Publishers/printers use divergent page numbering rules when it comes to blank pages and images.— Ineuw (talk) 22:43, 7 December 2021 (UTC)[reply]
crop tool automatically renames copies of image pages, commons tends not to engage in rename drama of the semi-automatic. --Slowking4Farmbrough's revenge 23:31, 7 December 2021 (UTC)[reply]
User:Ineuw I name mine the same number as the ia file has (or hathi, with the addition of some zeros), something like Count of Monte-Cristo 1887 Vol. 1-0049.jpg if there are multiple images on one page, then Count of Monte-Cristo 1887 Vol. 1-0049-3.jpg and Count of Monte-Cristo 1887 Vol. 1-0049-4.jpg. It is only awkward in that the scan number often does not match the djvu page, but, it keeps them sequential in the Category at commons, and it is easy to determine if one is missing and where it is at and, it is pretty easy to script a mass name change, if that is something that is needed. Also, at commons, consider using Category:The_Count_of_Monte-Cristo_1887_(books)/Volume 1, etc.--RaboKarbakian (talk) 23:50, 7 December 2021 (UTC)[reply]
As an aside and a plug: will attempt to construct some kind of useful title based on the work title, the page number if any and the image type (e.g. illustration, initial, etc), as well as a token effort at categorisation based on the image type. The user can then tweak the auto-generated name and cats.
It doesn't use the caption for anything other than dumping into the info template, but One Fine Day, it will add the right SDC fields at least. Inductiveloadtalk/contribs 23:59, 7 December 2021 (UTC)[reply]

Tech News: 2021-49[edit]

21:59, 6 December 2021 (UTC)

WS changes[edit]

As far as I know, there are no major Wikisource-relevant changes due this week on top of these those listed last week #Relevant_changes_to_Wikisource_due_in_wmf.11 that never got deployed.

I know of no further comments that have been received about the OSD viewer and thoughts on improving the UI beyond its current "initial" implementation. The patch demo here is still a place you may try the proposed interface options. As always, Beta Wikisource represents the current "master" branch of the software at a given moment. Everything you see there is normally expected to be deployed within a week or so (changed merged on a Tuesday or Wednesday will normally be delayed to the next week since they miss the cut-off early on Tues mornings UTC). Inductiveloadtalk/contribs 22:47, 6 December 2021 (UTC)[reply]

Since yesterday (8 December, in my AM), while editing in Index:Some file.djvu/page#, the djvu page shows itself briefly and then disappears. After it disappears, the enclosing area remains and is not clickable. The new and the old zoom do not work and the area is pretty much void of any response to any interaction. Toggling the edit tools "on" brings everything back. I have not tried Beta yet.--RaboKarbakian (talk) 13:41, 9 December 2021 (UTC)[reply]

Marking what's wrong with files[edit]

I've been using a PETSCAN query - to disperse the category of "File to Fix" into more specfic subcats, and re-evaluating files placed in that category.

Much appreciated if other experienced contributors could aid this effort, especially as @Inductiveload: wrote a tool for generating pagelists recently. ShakespeareFan00 (talk) 16:17, 11 December 2021 (UTC)[reply]

Barbados becoming a republic[edit]

How about collecting Constitution (Amendment) (No. 2) Act (Barbados) here? – Kaihsu (talk) 20:53, 7 December 2021 (UTC)[reply]

it seems they are asserting all rights reserved --Slowking4Farmbrough's revenge 15:27, 12 December 2021 (UTC)[reply]

New features in Page namespace editing?[edit]

Is there a way to turn off the coloring of wiki codes?— Ineuw (talk) 12:56, 11 December 2021 (UTC)[reply]

@Ineuw: -- I don't get any such coloring. You may have activated the relevant gadget. See under editing tools of gadgets menu of your preferences. Hrishikes (talk) 13:47, 11 December 2021 (UTC)[reply]
@Hrishikes: I looked before posting. There is no mention of highlighting the code on the edit, gadget of beta. Besides I use very few features, most are the default or disabled.— Ineuw (talk) 14:01, 11 December 2021 (UTC)[reply]
@Ineuw: You have most likely clicked the OOjs UI icon highlight.svg button in the toolbar, which turns on syntax highlighting for wikicode using the CodeMirror extension. Just click it again to toggle it off (it doesn't work all that well). Xover (talk) 14:31, 11 December 2021 (UTC)[reply]
@Xover: Many thanks, another supernatural event resolved. Now, if I can only get back the page image scrolling, but then, that is up to the gods on Mount Phabricator. — Ineuw (talk) 01:28, 12 December 2021 (UTC)[reply]
yeah, i agree the image zoom, rather than scrolling up and down, is a major UX unimprovement. clearly no testing done there. --Slowking4Farmbrough's revenge 22:29, 12 December 2021 (UTC)[reply]

Tech News: 2021-50[edit]

22:27, 13 December 2021 (UTC)

Public Domain Day 2022[edit]

here are some works to plan on:

  • 13th edition of Encyclopædia Britannica
  • Agatha Christie, The Murder of Roger Ackroyd
  • Arthur Conan Doyle, The Land of Mist
  • Ernest Hemingway, The Sun Also Rises
  • Franz Kafka, The Castle
  • T. E. Lawrence, Seven Pillars of Wisdom
  • A. A. Milne, Winnie-the-Pooh
  • Dorothy L. Sayers, Clouds of Witness
  • Ruth Plumly Thompson, The Hungry Tiger of Oz [4]
  • Gorton James et al., Profit Sharing and Stock Ownership for Employees,
  • Willa Cather, My Mortal Enemy
  • Christopher Vecsey, Adventurous Religion and Other Essays
  • Seán O'Casey, The Plough and the Stars
  • Katharine Brush, Glitter
  • Isabel Cotton Smith, Blue Book of Cookery and Manual of House Management
  • Felix Salten, Bambi
  • Florence Armstrong Grondal, The Music of the Spheres: A Nature Lover's Astronomy --Slowking4Farmbrough's revenge 03:07, 1 December 2021 (UTC)[reply]
There is already a page for coordination at Wikisource:Requested texts/1926 which lists some of these. --EncycloPetey (talk) 20:47, 1 December 2021 (UTC)[reply]
So much to do, so little time. Can these lists be merged into one? — Ineuw (talk) 01:42, 12 December 2021 (UTC)[reply]
You can certainly add to that but these lists are pretty arbitrary because not all works are going to end up Wikisource any time soon. This should really be a list of what we anticipate someone will actually work on adding. —Justin (koavf)TCM 23:28, 15 December 2021 (UTC)[reply]

Help: Half of edit screen is no longer accessible[edit]

I use over/under page editing and that is broken. How can I fix it?— Ineuw (talk) 09:41, 14 December 2021 (UTC)[reply]

i'm afraid i have gone to side by side with timeless skin for small screen, as the image zoom, rather than scroll up / down, has deprecated over / under for me. (i suspect you have a zoom issue) since UX is not done, we are left to do trial and error, for the combination of skins and toolbars that work best. --Slowking4Farmbrough's revenge 15:18, 14 December 2021 (UTC)[reply]
I find it interesting that everyone involved with this update is silent. Is this going to be the permanent layout, My current options are for over/under editing in Vector:
  • CSS settings to improve my view no longer work.
  • Half screen editing with an empty half right screen.
  • No scrolling of the image.
  • Overhead preview is the width of the screen, as opposed to the page width, which was controlled by CSS.
  • Previously existing editing controls in Preferences are gone.
These changes are not acceptable to me.Ineuw (talk) 01:39, 16 December 2021 (UTC)[reply]
@Ineuw: Are you using the Timeless skin? I'm not familiar with it but you can maybe reach out to who maintains it for help. —Justin (koavf)TCM 02:30, 16 December 2021 (UTC)[reply]
@Koavf: I always used Vector. Then I tried Timeless today, which made no difference. So, I returned to Vector.

Title Page Not Exported[edit]

In The Works of H. G. Wells (Atlantic Edition)/Anticipations, the Title Page is not exported because it is not part of the TOC. What is the best way to allow for the export of the Title Page? Languageseeker (talk) 02:43, 15 December 2021 (UTC)[reply]

There are three main main ways I can think of:
1. Just transclude it on that page like a "normal" book, above the TOC
2. Use an AuxTOC (if the main TOC sets ws-summary, e.g. if it uses {{TOC begin}}, you also need to wrap everything in an {{export TOC}}, or only the ws-summary element will be used.

Example: Separate Aux TOC

{{export TOC|
* [[/Title page/]]
...The usual TOC
 (not listed in original)

...The usual TOC

3. Use the class "wst-toc-aux" with the {{TOC begin}} templates. This does not need {{export TOC}} as it's all in one table. Clearly not popular as when I tried it I got reverted because "it wasn't in the original". For things like Prefaces and so on, it seems much neater (to me) than tacking on AuxTOCs.

Example: {{TOC begin}} and wst-toc-aux

{{TOC begin|width=35em}}
{{TOC row 2-1|class=wst-toc-aux|Title {{Smaller|(not in original TOC)}}}}
{{TOC row 2-1|Chapter 1 | 1}}
{{TOC row 2-1|...}}
{{TOC end}}
Title (not in original TOC)
Chapter 1 1
Inductiveloadtalk/contribs 06:56, 15 December 2021 (UTC)[reply]
@Inductiveload Thanks for the help. I'm wondering if it's possible to add a hidden parameter so that it will export the Title Page, but will not actually show up. Languageseeker (talk) 01:59, 16 December 2021 (UTC)[reply]

Last Chapter of Southern Historical Society Papers, Volume 3[edit]

First of all, sorry for my grammar. So, basically at Index:Southern Historical Society Papers volume 03.djvu there is the last chapter. The pages for the last chapter itself at the Index is declared as problematic and without text, already transcluded on the other scan. My question is if I want to transclude it, what should I do? Thanks. Mnafisalmukhdi1 (talk) 12:02, 17 December 2021 (UTC)[reply]

@Mnafisalmukhdi1 The roster was already transcluded at A Roster of General Officers. I updated the TOC to reflect this. Languageseeker (talk) 12:42, 17 December 2021 (UTC)[reply]
Then I don't have to transclude it again for the last chapter? Thanks. Mnafisalmukhdi1 (talk) 12:50, 17 December 2021 (UTC)[reply]

Missing page placeholders[edit]

"The following pages in this file are missing: 5,6.

"Placeholders should be inserted so that when the pages are inserted, existing content will not become misaligned."

How is that done, please? The index in question is Index:Aerial travel for Business or Pleasure - Thos Cook & Son - 1919.pdf. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:14, 17 December 2021 (UTC)[reply]

@Pigsonthewing the short answer is using some kind of PDF editor (I think PdfSam is supposed to be good, I use a command line tool called stapler) and inserting some kind of placeholder page, for example File:Generic placeholder page.pdf at the appropriate point. Inductiveloadtalk/contribs 23:28, 17 December 2021 (UTC)[reply]

In Windows you can also use the djvm command line tools from DjVu for replacing a page using the -d (delete) and -i (insert) switches.

@echo off
: location of the app
: C:\Program Files (x86)\DjVuLibre\djvm.exe

: if you wish to add the location to the path
: path=%path%;C:\Program Files (x86)\DjVuLibre

echo on
:"C:\Program Files (x86)\DjVuLibre\djvm" -d "I:\0_djvu\A_Chapter_on_Slavery.djvu" 166
: check result
"C:\Program Files (x86)\DjVuLibre\djvm.exe" -i "I:\0_djvu\A_Chapter_on_Slavery.djvu" "Replace_it_with_page152.djvu" 166

:see any error messages


Ineuw (talk) 07:15, 18 December 2021 (UTC)[reply]

Tech News: 2021-51[edit]

22:05, 20 December 2021 (UTC)

Help with columns spanning page breaks[edit]

For the text Index:Axiochus (Spenser, 1592).pdf, I have implemented two columns for the purpose of presenting both the original and a modernized version (without archaic spellings) of the source text. In the Transcluded text however, Axiochus (Spenser)/Axiochus, page breaks are causing new lines between pages. How would I go about fixing this, such that transitions are seamless between pages. On Help:Page breaks I saw templates relating to lists and tables, so might it be advised to use the "Column list" template as opposed to "columns" to fix this? Oryang7 (talk) 05:09, 17 December 2021 (UTC)[reply]

I hate to say this, but I personally don't think you should try to do any such thing. Wikisource is about presenting (relatively) faithful digitized versions of the source document, even when that source uses archaic spellings or may be otherwise difficult to read/comprehend by modern readers. I can see you've put a fair bit of effort into this, so I don't say this lightly, but I think you should just be presenting the text as written, rather than trying to modernize it. — Dcsohl (talk)
18:43, 17 December 2021 (UTC)[reply]
Do you know if it's possible to someway preserve the modernized version on wikisource? If I removed the modernized version from the transcluded text might it be possible to create another page, unsourced, of the modernized version? Or, if it needs to be sourced, may uploading a pdf of the modernized version, which I assume could be done as the original is out of copyright, and transcluding it to a seperate page suffice? Or, and I don't know if this is already present on wikisource, is there a way to implement a feature allowing readers to toggle between the original and modernized versions on the single transcluded page? Oryang7 (talk) 23:49, 17 December 2021 (UTC)[reply]
I'm not entirely sure whether to point you to Wikisource:Annotations or Wikisource:Translations, but I would think reviewing those two pages might be helpful to you. — Dcsohl (talk)
19:51, 22 December 2021 (UTC)[reply]


The documentation to the template {{Lang}} says that the code for the language being displayed should be provided using ISO 639. However, there many languages have different codes in ISO 639-1, ISO 639-2 and ISO 639-3. Which of these should be used? --Jan Kameníček (talk) 18:57, 22 December 2021 (UTC)[reply]

@Jan.Kamenicek as far as I know, they HTML lang attribute can use either two or three-letter language codes (so ISO 639-1 or -2), as well as a two-letter country code suffix. According to, this is RFC 3066, and you can also have other IANA "subtags" for "variants", the example given is "en-scouse", but there are lots.
Generally, just the two letter one will do in most cases unless you really need to drill down into the language variant. Inductiveloadtalk/contribs 19:11, 22 December 2021 (UTC)[reply]
According to this document from W3C, the standard is IETF BCP 47, which is something of a catchall that "combine[s] subtags from other standards such as ISO 639, ISO 15924, ISO 3166-1 and UN M.49." — Dcsohl (talk)
19:12, 23 December 2021 (UTC)[reply]

Naming convention[edit]

I have a question that is not yet governed by Wikisource:Naming conventions & Help:Disambiguation.

A work has two different editions published in the same year. How should we name these editions, such as

  1. "aaa (2021a)" and "aaa (2021b)",
  2. "aaa (1st edition)" and "aaa (2nd edition)",
or otherwise?

Thank you.

--Miwako Sato (talk) 11:41, 23 December 2021 (UTC)[reply]

@Miwako Sato: What actually distinguishes the editions? The usual go-to for disambiguation are publisher and place of publication. If neither is sufficient we have to get more creative. "1st edition" and "2nd edition" may be reasonable options for some cases. For laws and similar it may make sense to use both month and year, or even a full date. It's a bit of an edge case, so we don't really have firm guidance or practice on it, and the details of your particular case will be necessary to suggest anything sensible. Xover (talk) 11:50, 23 December 2021 (UTC)[reply]
The editions in question were published in the same year, by the same publisher, and at the same place. The only thing that distinguishes them is their contents (the subsequent edition contains revised & additional contents). So, in this case, I think "1st edition" and "2nd edition" would be appropriate (because it's a book). Thank you so much, and special kudos for a very quick response! --Miwako Sato (talk) 12:04, 23 December 2021 (UTC)[reply]

Page image vanishes after loading[edit]

Whenever I try to edit in Page: namespace, the page image loads, and then immediately vanishes. I am proofreading against an empty box. I have blanked my .js and .css files, tried another djvu file, tried changing skins, tried changing browsers. Am I the only person experiencing this? This is a total blocker for me -- I might as well quit Wikisource if I can't get this fixed. Hesperian 23:24, 16 December 2021 (UTC)[reply]

After noticing RaboKarbakian's comment above, I discovered that the problem goes away if I "Enable the editing toolbar" in my preferences. I'm not exactly happy at being forced to turn on a toolbar that I don't want, but at least there is a workaround. Hesperian 23:31, 16 December 2021 (UTC)[reply]
Yeah, I tried it without the toolbar today and nothing has changed. Even with the toolbar, today I had to reload every other page to get the djimage to load. To the best of my knowledge, the only complaints have been about the changes in zoom and not being able to change the orientation and I wonder if people actually use the tools or just have them enabled....--RaboKarbakian (talk) 23:38, 16 December 2021 (UTC)[reply]
yeah, i have the new OCR button enabled but do not use it. no improvement to require the learning curve. this is visual editor redux, where the devs make their "improvements" without UX. it was hard enough getting the devs to put their button on the toolbar, rather than hovering over the image in the way. --Slowking4Farmbrough's revenge 01:14, 17 December 2021 (UTC)[reply]
This was fixed within hours over a week ago, but wasn't merged until today: Since today is Friday, there are now no backport windows until Monday. I'm personally not available today at the normal window times of 1200, 1900 and 0000 UTC anyway; if anyone wants to request an emergency backport, they'll have to do it themselves or find someone who can. I have, however, done a backport patch for that person to use:
The whole torture of actually getting OSD deployed properly (there have been a lot of compounding issues, including the main developer going AWOL, the usual lack of review capacity/interes, a near total lack of engagement on outstanding UX questions and, unrelated to WS, missed MW releases for weeks at a time) is why Wikisource needs a proper Code Steward to take point and make sure important fixes don't just rot on Gerrit and, when fixed, get backported promptly. Inductiveloadtalk/contribs 11:28, 17 December 2021 (UTC)[reply]
huzzah, and beware, you may have self-nominated. i would support a individual grant, or set up the go fund me / patreon. --Slowking4Farmbrough's revenge 03:49, 18 December 2021 (UTC)[reply]

So, that magical Monday has come and gone, and the problem still persists.--RaboKarbakian (talk) 15:39, 24 December 2021 (UTC)[reply]

There are actually no Release Engineering backports (or deploys) this week or next because of the holidays. I didn't realise there wasn't even a window on Monday when I wrote that. This will not, therefore, be resolved until the 5th Jan at the earliest. Inductiveloadtalk/contribs 16:01, 24 December 2021 (UTC)[reply]
Please excuse me for whining on a holiday. Thank you for the information, and eh, Seasons Greetings!--RaboKarbakian (talk) 17:02, 24 December 2021 (UTC)[reply]

Wikipedia @ 20 (published by MIT Press)[edit]

I am starting to translate individual essays from Wikipedia @ 20 (published by MIT Press) to Croatian and I wonder if it would be good to import the whole book (licence), as well as to advance with translations here on Wikisource? --Zblace (talk) 15:27, 26 December 2021 (UTC)[reply]