@Samwilson About listing participants. Personally, I do not look at such lists in e-book files at all, and skip the title pages when I read them.
Moreover, usually the users who performed OCR, importing and proofreading indicate themselves under meaningless pseudonyms. In this case, a link to the wikipage with its edit history is sufficient.

Thanks, I added class="ws-noexport" in the tag of this image of the page layout, so now its uploader is excluded from the list.

In T275319#6884320, @cscott wrote:

database storage size, database column limits, etc, all scale with bytes not characters. We should be careful before bumping the limit that we're not going to run into problems with database schema, etc.

The database schema do not require modification. The database text column is of type binary MEDIUMBLOB, GZIPed diffs are written there. The MEDIUMBLOB type can store up to 16Mb of data per entry, i.e. this is the diff size limit for any page edit (revision).
The number of page edits is not limited, all diffs are collected together only when the page is rendered. If we recall the words of the documentation "The compression ratio achieved on Wikimedia sites nears 98%." (DB doc), then it can be argued that the current database schema can store pages of infinite size.

Seems, yes. Thank you very much!
I checked the places where the bug could appear. It was massive, if the bug remained somewhere I didn't notice, I'll let you know.

@Ladsgroup, I closed it up there, was 2 weeks of the poll. All administrators, bureaucrat and active users voted. Consensus.

Here is the community consensus.

It seems to me that this option should not cause side problems. All important transclusions are on the users watchlists.

@Tacsipacsi, thanks. But you answered an old example from 2019. At the time, I fixed it, bypassing the problem by moving all inclusions to Template NS. Several times I moved the page through different namespaces, tried patrolling and bouncing back, changed the settings for page stabilization and transclusions in different ways... it didn't help.

We probably have 30% of the entire Wikisource (!!!) with warnings that pages need to be patrolled, or it will appear after any editing of the page. Because our main template for texts in Main NS is dependent with json settings and modules in the Mediawiki NS that can be edited.

Sure, calendar algorithms, like Julian day as well as Unix time are beyond the scope of ISO.
It seems to be correct to keep the date as given in the printed source (let it be Julian "44-03-15" BC), without the Gregorian conversion variations. E. g. Wikidata birthdays: d:Q1048, d:Q5592. Will the date format have a code (like "J") about the calendar being used? Current #time supports codes for multiple calendars, excluding Julian.

Is the date format will has a mark to indicate which the calendar used? As a kind of wiki extension to the EDTF format. Like, Julian date "J44-03-15".
Or will need to keep specifying an additional tag about the date calendar? Like a string description in the text next to the date, an additional parameter in templates, a switch / qualifier in the Wikidata properties.

The community of Python language hasn't heard of EDTF either. stackoverflow, docs.python.org, supported format-codes. The size of this community is almost larger than that of Javascript and Php (on which the Wiki is written). Pywikibot is written in Python.
So, can be sure that the generally programming languages will not adopt the standard in the coming years.

Thanks you.

Was Pwb 3.0.dev0 (this version number did not change until this year for several years, although Pwb itself was regularly updated, probably it was a bug) → 6.0.1
PyMySQL 0.9.3 → 1.0.2
Python 3.7.

I updated pywikibot and pymysql and it worked.
I think, need to add check for the version of pymysql to pywikibot/data/mysql.py, and revert the code for support version <1.0.0. Or at least a notification that bots developers need to update pymysql.

By the whois, the domain was paid until 2023, maybe the hosting too. It is a pity that its admins have not responding for about a year, there is no way to fix the site or find out the situation.

On Wikidata and https://en.wikisource.org/wiki/Help:Wikilivres written that the Wikilivres.org was closed in August 2019.

And this page was created by bureaucrat of ruWikisource today. https://ru.wikisource.org/wiki/%D0%91%D0%A1%D0%AD1/%D0%91%D0%B5%D0%BB%D0%BE%D1%80%D1%83%D1%81%D1%81%D0%B8%D1%8F How you can see, this also have the mark "unreviewed pages" with link to a page in NS Project that which technically can't be reviewed.

@Aklapper, yes this still wanted, But I don't understand why you write to me. Because I am not its developer, I have not even seen its code, and moreover, I have not used PHP for 5 years having switched to Python, and don't write MW-extentions.
The author abandoned support of the extension 3 years ago. This is all the information I can help.

Enabled. Although seems that the extension don't work ... But there is no time for testing and no support, and formally this is another task.

Seems, it's a bug in code. How can resolve or get around this issue?
Which code show the revision requirement for this NS?

@Reedy, could you resolve this bug or disable the revision requirement for these NS?

T226054 The problem is that FlaggedRevs is already included in MediaWiki and you need to confirm revisions on a mass of pages. But this is not possible because the confirmation button is disabled. Can to approve this message from one page, but it will appear again and again, since Mediawiki pages cannot be patrolled.
During the year there was no solution to this problem.

Also with NS MediaWiki.
I am administrator and created the MediaWiki:Encyclopedias_settings.json and MediaWiki:Wikiprojects settings.json pages, which are included in most ruWikisource pages of Main NS. Now, after edits on pages (seems, only new users' edits), appear the requirement to review these MediaWiki pages, but this imposible to do. Can to remove this message from one page, but it will appear again and again, since Mediawiki pages cannot be patrolled.

The hotfix works on broken Russian Wikisource images. https://ru.wikisource.org/wiki/%D0%A1%D1%82%D1%80%D0%B0%D0%BD%D0%B8%D1%86%D0%B0:%D0%95%D0%B2%D1%82%D0%B8%D0%B4%D0%B5%D0%BC_(%D0%9F%D0%BB%D0%B0%D1%82%D0%BE%D0%BD,_1878).pdf/57, https://ru.wikisource.org/w/index.php?title=%D0%A1%D1%82%D1%80%D0%B0%D0%BD%D0%B8%D1%86%D0%B0:%D0%A2%D0%B8%D0%BC%D0%B5%D0%B9_%D0%B8_%D0%9A%D1%80%D0%B8%D1%82%D0%B8%D0%B9_(%D0%9F%D0%BB%D0%B0%D1%82%D0%BE%D0%BD,_%D0%9C%D0%B0%D0%BB%D0%B5%D0%B2%D0%B0%D0%BD%D1%81%D0%BA%D0%B8%D0%B9).pdf/308

As far as I understand, this extension is not active and abandoned, because the author did not saw interest of community. I don't understand why my suggestion to call interest of community to it caused your questions.

@freephile, could you add your extention on https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020/Wikisource?

I removed Wikipedia from the commit, remains only Wikisources there.

It do, I think. This problem was not until was disabled FlaggedRevs for NS "Wikisourse". And there don't using [[{{LOCALDAY}}. {{LOCALMONTHNAME}}]] [[{{LOCALYEAR}}]] {{#time}} unlike T119366.
Also, the unupdated version shows as stabilized: https://ru.wikisource.org/w/index.php?title=Заглавная_страница&stable=1. I tried to disable stabilisation for Main page, but problem still, because a transcludion can' be reviewed, as I wrote in this task.

On the Main page of https://ru.wikisource.org for unlogged readers still showing old News. It doesn't updating. (They placed in NS "Wikisource" and can't be revieved for show.) What to do?

This var_dump($wgFlaggedRevsNamespaces) have #6 (NS File), seems it now work (an example is above in post). Update: hm... I update page and it again shown links to not reviewed NS File: https://ru.wikisource.org/w/index.php?title=ИЭС/Раджа&oldid=3672630&diff=cur

I reopen the task. Unfortantelly, it is not resolved.

How large performance issues can will? Will it a noticeable? From that link it not clear. AFAIU, the webfonts downloads once then caching for alltime.

Thank you!

@Aklapper: why not, Bawolff have status "disabled".

Unfortunately, it don't work again.

I could, but unfortunately the login on Gerrit is broken. T220867

It will be great.
How long to wait for fix of login?

Ok, thank you again!

I did not quite understand. Now fonts will be downloaded automatically for all readers? Or will each reader required to register in WMF, and then manually enable font autodownloading in the ULS interface (by clicking on the gear icon near the list of interwiki)?

This is amazing, thank you!
Will this also works on Wikisource by T219065?

T219065

Glagolitic is in the font 'Menaion', it requested in T219065.

We will try via the extention. Thank you!

Is it possible to download these fonts from https://tools.wmflabs.org/ruwikisource/ with MediaWiki:Common.css?

The rules of ru.Wikisource has a permission to add texts written in Russian Church Slavonic, Old Church Slavonic, and Glagolitic script.
These are fonts for the ability to display them, otherwise they not shows. This site https://sci.ponomar.net/fonts.html is main source of fonts.
Although, seems on ru.Wikisource no texts using these fonts. They are transferred to the common Wikisource, where the text headers there have the link to this site for downloading fonts (example).

I found it there https://meta.wikimedia.org/wiki/Talk:Interwiki_map#Bibliowiki. Thanks.

Sorry for confusing, I updated the task.

Still needs a list of clear steps to reproduce the problem, including links. :( See T203897#4569643

@Vladis13: Gadgets are per-wiki settings and their code is on-wiki. If "obviously some kind of gadget" is enabled on your wiki or broken on your wiki then you need to contact admins on your wiki to fix the broken gadget code on your wiki.

Well, then it is not gadget. :) Thanks @JJMC89 for T203897#4570067, now we know that it is ext. CodeMirror on the button in new edit toolbar. This new edit panel globally replaced the previous one about 1-2 months ago.

Is way to disable it via settings?
Now very hard to work. Each press of a button is like a merry-go-round of glitches, they are different each time. Or the button for turning off the highlighting does not work. Another time when press the text size is reduced by half.
When opening a page in the Page namespace and the button was enabled past time, the scan image is shown not on the right, but below the text, which is very inconvenient.
And if the browser will drop status the button?
The editor should always check whether a button is pressed on it or not?

As term "beta-gadget" I meant that it's obvious that this is some kind of gadget in beta condition. I did not mean it in https://ru.wikisource.org/wiki/Служебная:Настройки#mw-prefsection-betafeatures.
But then it is not clear, why the beta gadget is released into the main space, without test notifications, and is not packaged as a "gadget" or "betafeatures"?