>
> While earlier scan image loaded were max 1k px width, now there are two
> images downloaded for each scan: max-width + 2*max-width (scalled up for
> some reason). This means, eg. assuming 2k-width scan (which is quite
> standard, now) that you will need to download and handle about 4^2 + 2^2 =
It seems that current Wikisource scan image handling implementation is
terribly resource consumeng (network, memory):
While earlier scan image loaded were max 1k px width, now there are two
images downloaded for each scan: max-width + 2*max-width (scalled up for
some reason). This means, eg.
I think tackling one thing at a time makes lots of sense, especially if
there's a process around it. I don't know who would run such a process,
especially considering that developers will generally work on whatever
they feel like! Perhaps we need to sketch out (on Meta?) a simple
workflow for
Hey everybody,
I stumbled upon this message by chance, but now I'm curious:
are you implementing IIIF on Wikisource?
That's very interesting!
Aubrey
On Mon, Nov 22, 2021 at 1:13 PM Ruthven wrote:
> Hi all, and thanks for the info.
>
> I get from your messages that there are two major points to
Hi all, and thanks for the info.
I get from your messages that there are two major points to be solved:
1. A clear lack of communication (mass messages are often unread or quickly
read, because there is some abuse of the tool, and what is important gets
lost in the flood of messages). Probably
I think most Wikisource developers are likely to be on this list. Of
course, it's best to make sure there are Phabricator tickets for every
separate bug or feature request.
On 21/11/21 1:36 am, Ankry wrote:
Well, I was notified by techncally skilled users that the ned
OpenSeadragon library
I totally understand this frustration, and I'm not really sure what the
solution is. There's no WMF team responsible for Wikisource (other than
the small amounts of work that my team, CommTech, gets to do; although
I'm writing this email as my volunteer self). So it's up to whoever
wants to do
There's a lot of activity recently on the ProofreadPage extension. It
seems a good thing to me: thanks to all involved!
I didn't see which commit exactly is at fault, but the first step is
usually to note breaking changes on the commit message and add a
user-info tag on the task so that it
Hi Ankry,
on Italian Wikisource and on Neapolitan Wikisource there are "Technical"
village pumps. I suppose that would be the correct place to post it if
there is such a page in other languages.
It would be interesting to see what happens if a whole community writes on
Phabricator in order to
Well, I was notified by techncally skilled users that the ned
OpenSeadragon library is much heavier and more memory consuming than
curreently used tools. So I can only hope that its load into memory can
be disabled if one needs so.
(may be critical while working on multiple pages at once)
10 matches
Mail list logo
