[Wikisource-l] Re: MediaWiki, Wikisource extensions, and new implementations deployment
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. assuming 2k-width scan (which is quite standard, now) that you will need to download and handle about 4^2 + 2^2 = 20 times larger network trafic (100% max-width + 200% max-width images). This might SIGNIFICANTLY affect users who pay for network transfer. And I wonder how was this accepted without wide discussion while earlier implementing prev/next image preload/prefetch discussion met an oposition from some developers who suggested that 10-100% (1.1-2x) larger network trafic could be a problem for some users. Unfortunately, I am out of time resources today, so I would welcome if anybody fills a bug (or bugs) concerning this. Ankry PS. Setting scan width in index pages (likely to half of the required width) would probably be a temporary workaround for affected users. W dniu 22.11.2021 o 04:44, Sam Wilson pisze: 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 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) However, I doubt if any technical comments from communities expressed here will reach developers. And which wiki pages would be more appropriate for such comments. Ankry W dniu 20.11.2021 o 14:33, Ruthven pisze: Hi all, as usual, I get surprised every time there are major changes on the MediaWiki software that are deployed without providing advance warning to the community. Every time it's the same story: something stops working on the project. A gadget, a toolbar or some personalised JS. This time it was T288141 (see https://phabricator.wikimedia.org/T288141), that was deployed in all the Wikisources (then rolled back because WikiMedia computer scientists are the best) completely disrupting redesigning the image side of the Page namespace. This affected the toolbars (see https://phabricator.wikimedia.org/T296033) and several gadgets around all the Wikisources. I am not saying that MediaWiki software shouldn't be improved: it's normal that we're trying to get all we can from this outdated software. I am just asking that major changes that affect all the Wikisources should be announced in every single Village Pump waaay before deploying them on the projects. Is it possible, as a Usergroup, to do a little pressure to be considered as a community and not as guinea pigs on which to deploy new, partially-tested features? Alex *Ruthven*on Wikipedia ___ Wikisource-l mailing list --wikisource-l@lists.wikimedia.org To unsubscribe send an email towikisource-l-le...@lists.wikimedia.org ___ Wikisource-l mailing list --wikisource-l@lists.wikimedia.org To unsubscribe send an email towikisource-l-le...@lists.wikimedia.org ___ Wikisource-l mailing list --wikisource-l@lists.wikimedia.org To unsubscribe send an email towikisource-l-le...@lists.wikimedia.org___ Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
[Wikisource-l] Re: MediaWiki, Wikisource extensions, and new implementations deployment
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) However, I doubt if any technical comments from communities expressed here will reach developers. And which wiki pages would be more appropriate for such comments. Ankry W dniu 20.11.2021 o 14:33, Ruthven pisze: Hi all, as usual, I get surprised every time there are major changes on the MediaWiki software that are deployed without providing advance warning to the community. Every time it's the same story: something stops working on the project. A gadget, a toolbar or some personalised JS. This time it was T288141 (see https://phabricator.wikimedia.org/T288141), that was deployed in all the Wikisources (then rolled back because WikiMedia computer scientists are the best) completely disrupting redesigning the image side of the Page namespace. This affected the toolbars (see https://phabricator.wikimedia.org/T296033) and several gadgets around all the Wikisources. I am not saying that MediaWiki software shouldn't be improved: it's normal that we're trying to get all we can from this outdated software. I am just asking that major changes that affect all the Wikisources should be announced in every single Village Pump waaay before deploying them on the projects. Is it possible, as a Usergroup, to do a little pressure to be considered as a community and not as guinea pigs on which to deploy new, partially-tested features? Alex *Ruthven*on Wikipedia ___ Wikisource-l mailing list --wikisource-l@lists.wikimedia.org To unsubscribe send an email towikisource-l-le...@lists.wikimedia.org___ Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
[Wikisource-l] Re: 2021 report
I think that information like "WCUG member X presented a session on Y at
event Z" would be hard to manage in this form as (1) we have no formally
managed membership at the moment (maybe we should change this and ask
interested people for formal declarations at regular intervals? - the
list on meta is unmaintained and contains initial declarations only) and
(2) most of us are also members of other formal affiliates and while our
activity in specific fields can be separated internally, this separation
would be not verifiable without clear declarations of these members
(should we ask them for such declarations concerning any Wikisource
related activity?)
For example, while I am a member of WMPL and participated in the
organization committee of Źródłosłów 2021, I clearly declared to WMPL
that I represent the community, not WMPL during the organizational
process. But neither information about roles of the conference
organizing committee members, nor this declaration is anywhere in
public. Only the results of this activity are public.
And I am active in WMPL in non-Wikisource related fields and also in
some Wikisource-related fields.
Ankry
W dniu 13.11.2021 o 20:12, Asaf Bartov pisze:
Thank you for starting the report, Ankry!
I think it should be clear what the user group is claiming as an
activity. For instance, was the usergroup involved in the creation of
the Balinese and Javanese Wikisource projects, mentioned under
"Milestones"? If so, the report should explain how the group was
involved; if it is just a mention of a milestone for Wikisource (as
distinct from a milestone for the Wikisource Community User Group), it
should be clearly separated from the main section of the report, which
should be devoted to activities and communications of the WCUG.
Likewise, was the user group involved in planning or organizing the
events mentioned? If so, it should be stated explicitly. (And if the
involvement was only that a member of the user group presented at the
event, then *that* should be stated explicitly (e.g. "WCUG member X
presented a session on Y at event Z"), avoiding the impression the
event itself is [co-]organized by the user group.)
Cheers,
A.
Asaf Bartov (he/him/his)
Senior Program Officer, Emerging Wikimedia Communities
Wikimedia Foundation <https://wikimediafoundation.org/>
Imagine a world in which every single human being can freely share
in the sum of all knowledge. Help us make it a reality!
https://donate.wikimedia.org
On Sat, Nov 13, 2021 at 7:11 PM Satdeep Gill
wrote:
Here is the link to the report:
https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/2021_Report
Best
Satdeep
On Sat, Nov 13, 2021, 7:57 PM Ankry wrote:
Hi everyone,
As we are close to the end of this year, I started preparing
the 2021
WCUG annual report. Formally, it is due end of November.
If anyone participated or organized some Wikisource events,
please add
appropriate sections.
Cheers,
Ankry
___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to
wikisource-l-le...@lists.wikimedia.org
___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
___
Wikisource-l mailing list --wikisource-l@lists.wikimedia.org
To unsubscribe send an email towikisource-l-le...@lists.wikimedia.org___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
[Wikisource-l] 2021 report
Hi everyone, As we are close to the end of this year, I started preparing the 2021 WCUG annual report. Formally, it is due end of November. If anyone participated or organized some Wikisource events, please add appropriate sections. Cheers, Ankry ___ Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
[Wikisource-l] Re: can't create account-- want to help validate a text
This would be not helpful as a local range blocks prevent local account creation even for users having a global account. Local administrator action is needed in such cases. And, by default, a single account for another user can be created by any autoconfirmed user; no special rights is needed. I have already created an account for this user per private communication, so, I hope, his problem is solved. Ankry W dniu 27.10.2021 o 13:23, Andy Mabbett pisze: On Tue, 26 Oct 2021 at 20:35, Casper Oswald wrote: I know this is a little like reply-all-ing, but I can’t figure out to create an account— all IP addresses available to me are blocked, including IP address of my home service without a VPN. Can anyone help me sign up. Assuming you're caught up in IP range blocks and not personally blocked; have you tried creating an account on another project, such as one of the Wikipedias? ___ Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
[Wikisource-l] Re: Help wanted: local labels for Wikisources on Wikidata
I just wonder which lamguage description is missing for Multilingual Wikisource. :) Ankry On 02.08.2021 09:44, Sam Wilson wrote: Hi everyone, I noticed the other day that there are a bunch of Wikisources whose Wikidata items don't have labels in the languages of those Wikisources. So if anyone knows how to write "Welsh Wikisource" in Welsh, it'd be great if you could go to Q24577651 <https://www.wikidata.org/wiki/Q24577651> and add the Welsh label. Similarly for the rest of these: [...] wd:Q18198097 <http://www.wikidata.org/entity/Q18198097> Multilingual Wikisource [...] ___ Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
[Wikisource-l] Re: Wikisource Satisfaction Survey 2021
Any deadline for filling the survey? Or is it time-unlimitted? Some tolls are used by most wikisource users occasionally only. So new opinion by the same users may appear over time. Ankry On 01.07.2021 16:28, Satdeep Gill wrote: Hello everyone! We hope you are all doing well. There has been a lot of Wikisource infrastructure related development in the past year. A lot of which was done by the Community Tech team at the WMF, Grantees funded by the WMF or through projects like Google Summer of Code. We would like to understand what you feel about all of these different features and tools, be it the Wikisource Pagelist Widget or the new Ebook Export tool? We would like to take a little time to fill in this not so long survey. You can take the survey in English <https://docs.google.com/forms/d/1DOM1bMB2eFAz_Wfh8k6WT903NWWKIzHBbY6S-yoq-QI/edit>, Spanish <https://forms.gle/n91HW6W3C8D1z1T8A>, Polish <https://forms.gle/DEntVxSvoZx3n6Yt8>, Hindi <https://docs.google.com/forms/d/1XwkNV4FIMOvFm7aKQKDVdX_dtCITHINSVuPH67tefCs/edit>or Punjabi <https://docs.google.com/forms/d/1eSV0taEMJ9WTFUdcXFwXRYAgzMD72bkAuiJfk3nhSkI/edit>. (In an ideal world, the survey would be available in all the Wikisource languages, sadly we couldn't do it for this survey. We will try to be more inclusive in the future.) P.S. This survey will be conducted via a third-party service, which may subject it to additional terms. For more information on privacy and data-handling, see the survey privacy statement (English <https://foundation.wikimedia.org/wiki/Wikisource_Community_Tech_Survey_Privacy_Statement>, Spanish <https://foundation.wikimedia.org/wiki/Wikisource_Community_Tech_Survey_Privacy_Statement/es>, Polish <https://foundation.wikimedia.org/wiki/Wikisource_Community_Tech_Survey_Privacy_Statement/pl>, Hindi <https://foundation.wikimedia.org/wiki/Wikisource_Community_Tech_Survey_Privacy_Statement/hi>and Punjabi <https://foundation.wikimedia.org/wiki/Wikisource_Community_Tech_Survey_Privacy_Statement/pa>) P.P.S. If you have any questions or feedback about the survey, feel free to reach out to me at sg...@wikimedia.org <mailto:sg...@wikimedia.org>. Best Satdeep -- Satdeep Gill (pronouns - he, him) Program Officer GLAM and Underrepresented Knowledge Wikimedia Foundation <https://wikimediafoundation.org/> ___ Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org ___ Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
Re: [Wikisource-l] Various news
I wonder if the non-working score extension would be a good candidate here. Few thousand pages in many Wikisources are hit by this problem. And AFAIK nobody is actively working to fix it. Ankry On 13.11.2020 16:54, Nicolas VIGNERON wrote: Hi everyone, I hope you're all well. I'm sorry I didn't post for a long time, so here is some news (not exhaustive, feel free to answer with your own news): - first and foremost, the Wishlist is back and it starts next Monday: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021 let's gather our best idea again this year! - as usual, if you did something related to Wikisource, don't hesitate to add it on https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/2020_Report (especially in this strange year, if you did some online activities, I'd love to hear about it!) - an "Affiliates Data Survey" run by mail and by the Foundation is coming; I'll get in touch with you soon, if you are interested to share your experience with the Wikisource community, feel free to contact me in private. - here is a very interesting and promising project to improve Wikidata-Wikisource Integration : https://meta.wikimedia.org/wiki/Wikicite/grant/Improving_Wikidata-Wikisource_Integration Finally, as an official user group, the Foundation requires 2 primary contacts, for now (and since a long time), I'm the only contact, which is problematic. Also, for me, I'd be happy to have some help ;) Are there any candidates? Cheers, For the WCUG, Nicolas ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Memorandum of Understanding with NDLI, CIS and WMF
I don't think there is a problem here.
From the copyright point of view, the content we want to copy from them
is PD (expired copyright).
The problem was their ToU that did not allow commercial republishing.
If we republished without permission, then they would accuse us a
violation of ToU and eg. suspend users' accounts. I doubt they would be
able to sue a republisher for anything as they are not the copyright holder.
Once we get their permission to publish in Wikimedia, we can publish
there under the correct copyright status (PD) and anybody can download
therefrom for any purpose. Reusers are not bound by their ToU. The
permission is to be not bound by their ToU limits, and is unrelated to
copyright.
Ankry
On 14.03.2020 20:12, Asaf Bartov wrote:
On Sat, Mar 14, 2020, 20:03 Bodhisattwa Mandal
mailto:bodhisattwa.rg...@gmail.com>> wrote:
Hi Ankry,
As part of the understanding, NDLI is giving permission to use
their contents to be used on Wikimedia sites as needed.
This is of course not enough. Permission must be given to the entire
world, not to Wikimedia sites only. I know you know this, but it is
important NDLI understand this, too.
A.
Also, anything not compatible with Wikimedia sites and licensing
will not be uploaded in any way.
Regards,
Bodhisattwa
On Sat, 14 Mar 2020 at 19:55, Ankry mailto:ankry.w...@onet.pl>> wrote:
I'm just looking at them.
They have restriction for non-commercial use of their content
in their ToU.
So uploading anything to Commons without their explicit
permission may be against their ToU (even if consistent with
copyright law).
Do we care?
Ankry
On 14.03.2020 11:18, Nicolas VIGNERON wrote:
Hi,
That's a really great news! Thanks for sharing it.
I browse quickly the content they have and wow, this is
really multilingual. I even found some bilingual books with
Breton (mislabelled as French) and I saw a lot of other
minority languages!
Do you already know what the next steps will be? Do you need
help?
Cheers, ~nicolas
Le sam. 14 mars 2020 à 09:52, Bodhisattwa Mandal
mailto:bodhisattwa.rg...@gmail.com>> a écrit :
Hi all,
It gives us immense pleasure to announce to the Wikimedia
community that National Digital Library of India
<https://en.wikipedia.org/wiki/National_Digital_Library_of_India>
(NDLI), Centre for Internet and Society (CIS) and
Wikimedia Foundation (WMF) have signed a tripartite
non-binding Memorandum of Understanding (MoU) for a
2-years partnership. National Digital Library of India is
a Ministry of Human Resource Development
<https://en.wikipedia.org/wiki/Ministry_of_Human_Resource_Development>
project, developed at IIT Kharagpur
<https://en.wikipedia.org/wiki/Indian_Institute_of_Technology_Kharagpur>
which aims to build a virtual repository of learning
resources and literature metadata.
Through this understanding, we will work together on:
* integrating Wikisource and Wikidata contents on NDLI
website. <https://ndl.iitkgp.ac.in/>
* building up technical infrastructure on NDLI website
to crowdsource
metadata curation on Wikidata and proofreading on
Wikisource websites.
* importing relevant contents and data from NDLI
website to Wikidata and Wikisource.
* identifying and pursuing collaboration opportunities
around other Wikimedia projects, such as Wikibooks.
After months of discussion among the three parties, the
understanding was finalized during International
Symposium on Knowledge Engineering for Digital Library
Design 2019, <http://kedl2019.ndl.gov.in/> an
international conference organized collaboratively by
NDLI and UNESCO at IIT Delhi
<https://en.wikipedia.org/wiki/Indian_Institute_of_Technology_Delhi>,
where WMF was a technical partner.
Many apologies for cross-posting the announcement in
different relevant mailing lists.
Regards,
Jayanta and Bodhisattwa
CIS-A2K
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
<mailto:Wikisource-l@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
<mailto:Wikiso
Re: [Wikisource-l] Memorandum of Understanding with NDLI, CIS and WMF
I'm just looking at them. They have restriction for non-commercial use of their content in their ToU. So uploading anything to Commons without their explicit permission may be against their ToU (even if consistent with copyright law). Do we care? Ankry On 14.03.2020 11:18, Nicolas VIGNERON wrote: Hi, That's a really great news! Thanks for sharing it. I browse quickly the content they have and wow, this is really multilingual. I even found some bilingual books with Breton (mislabelled as French) and I saw a lot of other minority languages! Do you already know what the next steps will be? Do you need help? Cheers, ~nicolas Le sam. 14 mars 2020 à 09:52, Bodhisattwa Mandal mailto:bodhisattwa.rg...@gmail.com>> a écrit : Hi all, It gives us immense pleasure to announce to the Wikimedia community that National Digital Library of India <https://en.wikipedia.org/wiki/National_Digital_Library_of_India> (NDLI), Centre for Internet and Society (CIS) and Wikimedia Foundation (WMF) have signed a tripartite non-binding Memorandum of Understanding (MoU) for a 2-years partnership. National Digital Library of India is a Ministry of Human Resource Development <https://en.wikipedia.org/wiki/Ministry_of_Human_Resource_Development> project, developed at IIT Kharagpur <https://en.wikipedia.org/wiki/Indian_Institute_of_Technology_Kharagpur> which aims to build a virtual repository of learning resources and literature metadata. Through this understanding, we will work together on: * integrating Wikisource and Wikidata contents on NDLI website. <https://ndl.iitkgp.ac.in/> * building up technical infrastructure on NDLI website to crowdsource metadata curation on Wikidata and proofreading on Wikisource websites. * importing relevant contents and data from NDLI website to Wikidata and Wikisource. * identifying and pursuing collaboration opportunities around other Wikimedia projects, such as Wikibooks. After months of discussion among the three parties, the understanding was finalized during International Symposium on Knowledge Engineering for Digital Library Design 2019, <http://kedl2019.ndl.gov.in/> an international conference organized collaboratively by NDLI and UNESCO at IIT Delhi <https://en.wikipedia.org/wiki/Indian_Institute_of_Technology_Delhi>, where WMF was a technical partner. Many apologies for cross-posting the announcement in different relevant mailing lists. Regards, Jayanta and Bodhisattwa CIS-A2K ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org <mailto:Wikisource-l@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
[Wikisource-l] Wikisource Community User Group 2019 report
Dear subscribers, the 2019 report of Wikisource Community User Group is ready: https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/2019_Report Thank you very much to all who helped with the work on it. Best regards, Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Wikisource Conference in Warsaw
Our conference grant application is ready. We can now ask people / chapters to endorse the idea: https://meta.wikimedia.org/wiki/Grants:Conference/WCUG_Wikisource/Wikisource_Conference_2020#Endorsements And keep our fingers crossed! Regards, Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Wikisource Conference in Warsaw
Well, I forgot to mention: the deadline for this grant application is on Sunday, so if you wish to add something, please do this before this date. Ankry On 31.01.2020 16:45, Ankry wrote: Dear Wikisource Community, we are in the final stage of preparing the conference grant application: https://meta.wikimedia.org/wiki/Grants:Conference/WCUG_Wikisource/Wikisource_Conference_2020 At the moment, we are defining the conference goals. Would you like to add something here? Do you think about other important points that we should focus on? Maybe, the 2015 Wikisource Mission Statement: https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/Wikisource_Mission_Statement needs to be revised? Any comments are appreciated. If you have any comments or questions, feel free to contact any member of the Organizing Committee (contact info on the application page). We believe that all Wikisource Communities, the large ones as well as the small ones will benefit from the Conference. On behalf of the Organizing Committee, Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Wikisource Conference in Warsaw
Dear Wikisource Community, we are in the final stage of preparing the conference grant application: https://meta.wikimedia.org/wiki/Grants:Conference/WCUG_Wikisource/Wikisource_Conference_2020 At the moment, we are defining the conference goals. Would you like to add something here? Do you think about other important points that we should focus on? Maybe, the 2015 Wikisource Mission Statement: https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/Wikisource_Mission_Statement needs to be revised? Any comments are appreciated. If you have any comments or questions, feel free to contact any member of the Organizing Committee (contact info on the application page). We believe that all Wikisource Communities, the large ones as well as the small ones will benefit from the Conference. On behalf of the Organizing Committee, Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
[Wikisource-l] Wikisource Conference in Warsaw
Dear Wikisource Community, Meeting the Wikisource community expectations, we are working with Wikimedia Polska and Wikimedia Foundation on organiziing the 2nd Wikisource Conference in Warsaw. We already had a survey that showed high interest in the Conference within the community. We also had recently a meeting on the conference organization process and its requirements. However, we are still at a very early stage of the Conference organization process. But we are hoping this event will happen in September this year. In order to apply for Wikimedia Foundation support, we need some input from the community about the Conference goals and the community expectations. If you are a wikisourcian, you wish to participate the conference or you wish to help the Wikisource community that the conference take place, please fill the short survey linked below before January 29 (due to short deadline for grant applications). Please, also share this request among Your communities. Here is the link to the survey https://docs.google.com/forms/d/e/1FAIpQLSf7FnFgMLPHeyWtBqjgXwLDYvh5vxeTnsZ0OIjTdSDrZlX0PA/viewform Feel free to contact us, if you have any questions, suggestions, proposals, or if you wish to help us in any other way. On behalf of the Organizing Commitee, Nicolas Vigneron Satdeep Gill Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Fwd: rozliczenie grantów
Sorry, wrong list :) Ankry On 07.01.2020 21:05, Ankry wrote: Na poniższą, wysłaną tydzień temu wiadomość Biuro niestety, wbrew zapowiedzi zawartej w autoresponderze, że odpowie dziś, nie [...] ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
[Wikisource-l] Fwd: rozliczenie grantów
Na poniższą, wysłaną tydzień temu wiadomość Biuro niestety, wbrew zapowiedzi zawartej w autoresponderze, że odpowie dziś, nie odpowiedziało. Dyrektor i skarbnik również zignorowali temat. Przekazuję zatem do wiadomożci KW, że prawdopodobnie Huston ma problem, z którym sobie nie potrafi poradzić i do któregp być może, jako KW, powinniśmy się odnieść. Proponuję to przedyskutować na jutrzejszym spotkaniu. Ankry PS: właściwy problem jest opisany w postscriptum maila. Forwarded Message Subject:rozliczenie grantów Date: Tue, 31 Dec 2019 02:22:19 +0100 From: Ankry To: Biuro Wikimedia Polska CC: masti , Łukasz Garczewski Cześć Aniu. Mam kilka pytań doczyczących sprzecznych informacji / nieścisłości w rozliczeniu grantów: 1. WG 2019-27 - na stronie grantu figuruje jako rozliczony, a na zbiorczej jako oczekujący na fakturę; mogłabyś to uzgodnić? 2. WG 2019-16 - czy rzeczywiście nadal jest nierozliczony? Z korespondencji e-mail, która do mnie dotarła wynika, że Nostrix dostarczył dokumentację zgodnie z wymaganiami podanymi przez Stowarzyszenie na stronie https://pl.wikimedia.org/wiki/Wikigranty/zasady_refundacji i zostało to zaakceptowane przez księgowość. 3. WG 2019-25 i WG 2019-26 jakoś dugo są nierozliczone; wiesz może coś o przyczynach? Czy Jacek Halicki tak długo zwleka z przysłaniem rozliczenia? Zwykle mu się to nie zdarzało. Czy mam go pogonić? Ankry PS. Zauważyłem, że pomimo zastrzeżeń księgowości w korespondencji skierowanej do Nostriksa, na stronie https://pl.wikimedia.org/wiki/Wikigranty/zasady_refundacji nadal figuruje informacja dla grantobiorców, że wymagane jest podawanie jedynie stanu licznika na początku i końcu podróży (bez jakichkolwiek stanów pośrednich). Muszę więc zakładać, że te informacje są aktualne i rozbiezności wymagań zostały z księgowością wyjaśnione. Jako, ze nie wiem kto z ramienia Stowarzyszenia zajmuje się uzgodnieniami z księgowością dotyczącymi rodzaju i formy dostarczanej dokumentacji, nie wiem do kogo kierować ewentualne prośby o wyjaśnienie. Bo chyba nie do całego zarządu? ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
[Wikisource-l] Wikisource Conference in Warsaw 2020/2021
Hi all, As some of you already noticed, we were talking on Saturday not only about Wikimedia Summit, but also about plans concerning Wikisource Conference sequel. The first Wikisource Conference took place in Vienna in 2015. Maybe, five years later, it is good time to organize the next event? The only way for this to happen is to receive a grant from WMF. Recently, I have got a confirmation from my chapter that Wikimedia Polska is willing to help us to apply for the grant and to organize Wikimedia Conference in Warsaw as a fiscal sponsor <https://meta.wikimedia.org/wiki/Grants:Fiscal_sponsorships>. (AFAIK this is the same procedure that was applied to the conference in Vienna). What they need from us? We need: * to organize various commitees (Organizing Commitee, Program Commitee, Grant Comission, etc); the discussion on Saturday showed that there are people among us who want help in theese. Of course the more people, the better * to decide *when we want the Conference*. There are two possible dates: Autumn 2020 (likely September) and Spring 2021 (likely May); we need to decide which one is preferred and the decision is a bit urgent as for the near term the deadline for grant application is 10 February (however it is a realistic plan). At the moment this question is crucial * to estimate how many people wish to participate in the Conference The person supporting us from WMPL is Natalia. We have prepared a short survey that should help us to find response to the above questions. The survey is here: https://docs.google.com/forms/d/e/1FAIpQLSe-0WGvjrt1UcHhAl-CMtNps85m28R22a6CFkai_cH86k44rw/viewform Please, fill it if you are interested in participating the Conference. Best, Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Wikimedia Summit report
Has the report appeared finally? I cannot find it on meta. I noticed that User:Gurlal Maan was quite active in mid-September, so hoping his busy time ended finally and we can see the report. While, after six months, the topics may be a bit outdated, IMO they are still interesting for us to understand the importance of such events for Wikisources and for our community group and to consider how to take good decisions concerning delegate selection for such events in future. Ankry On 15.06.2019 12:18, Gurlal Maan wrote: I feel really very sorry for that. I am very busy in serious family matters since 3 months. It is in my notice. I will do it after some relaxation. On Sat 15 Jun, 2019, 2:23 PM Bodhisattwa Mandal, mailto:bodhisattwa.rg...@gmail.com>> wrote: Sorry *almost 3 months On Sat, 15 Jun 2019, 14:20 Bodhisattwa Mandal, mailto:bodhisattwa.rg...@gmail.com>> wrote: Hi, It has been more than 3 months and there is no report or any update. Shall we get any? Regards, Bodhisattwa On Wed, 8 May 2019, 20:02 Bodhisattwa Mandal, mailto:bodhisattwa.rg...@gmail.com>> wrote: Any update ? Regards, Bodhisattwa On Thu, 4 Apr 2019, 11:41 Nicolas VIGNERON, mailto:vigneron.nico...@gmail.com>> wrote: Hi, Yes, it is already planned (I remind it to him just yesterday), please wait a little bit ;) Cheers, ~nicolas Le mer. 3 avr. 2019 à 22:11, Mardetanha mailto:mardetanha.w...@gmail.com>> a écrit : Agreed On Wed, Apr 3, 2019 at 11:57 PM Bodhisattwa Mandal mailto:bodhisattwa.rg...@gmail.com>> wrote: Hi, As the Wikimedia Summit 2019 ended recently, it would be great if the representative from Wikisource User Group can share his experience and submit a report. Regards Bodhisattwa ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org <mailto:Wikisource-l@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikisource-l -- Sent from iphone using Gmail mobile ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org <mailto:Wikisource-l@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org <mailto:Wikisource-l@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org <mailto:Wikisource-l@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] PDF preview missing (429 Error generating thumbnail)
Problems with rendering PDF files appear quite often. This is the reason why I prefer to process PDF files through pdf2djvu program before uploading. Ankry On 26.09.2019 10:56, Lars Aronsson wrote: On September 16, ten days ago, I got a relapse and started to contribute to Wikisource again. I found some nice PDF files and uploaded them to Commons, a total of 81 issues of the official gazette of Finland from the winter 1878. I have since then been proofreading several pages from the first week of March (when the peace at San Stefano was signed), e.g. https://sv.wikisource.org/wiki/Finlands_Allmänna_Tidning_1878-03-05 But previews (thumbnails) have been generated for none of these 81 PDF files. I am able to proofread the text (embedded in the PDF) only because I keep local copies of the PDFs that I can view. https://commons.wikimedia.org/wiki/Category:Finlands_Allmänna_Tidning_1878 On September 17, I asked about this problem on the Help desk, https://commons.wikimedia.org/wiki/Commons:Help_desk#PDF_previews_missing and a kind person registered the problem in Phabricator, https://phabricator.wikimedia.org/T151202 but then nothing has happened in more than a week. So there is not only a problem in generating thumbnails, but also in responding to a reported problem. I don't even know if there is a technical problem with the PDF files I uploaded or if this is a temporary technical problem on Commons. (But since I can view the local files, I assume the files are okay.) ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Affiliate-selected Board seats
I can assist you if you need. However, it seems to me that this mailing list is (almost) dead (correct me if I am wrong). So voting announcements via mailing list go nowhere. Ankry On 12.05.2019 20:28, Nicolas VIGNERON wrote: Hi all, The voting period is now open. Do we want to want to vote as a group? (I'm a bit concerned no-one even aswered my previous email :/ ) and if so, how should we procede? I was thinking about an internal vote, and take the results but I fear there will be too few votes to be representative of the group. I need you, /we /and /you /need you! So the big question is: should I launch the internal vote and is anyone interrested? (for obvious reasons, it would be good that someone assist me to make sure everything is going fine). For information, there is 12 candidates (listed with statements on https://meta.wikimedia.org/wiki/Affiliate-selected_Board_seats/2019/Nominations, including the two seats whose terms have expired) and as remarked, none « mentioned Wikisource specifically in their candidate statement » (source: https://en.wikisource.org/wiki/Wikisource:News/2019-05 ). Cheers, Nicolas Vigneron Le mer. 17 avr. 2019 à 13:57, Nicolas VIGNERON mailto:vigneron.nico...@gmail.com>> a écrit : Hi all, As you may know, the election of the Affiliate-selected Board seats (ASBS) has begun. We, as the Wikisource Community User Group, can take part in this election and elected two person to the Board of Trustees of the Wikimedia Foundation. The meta page https://meta.wikimedia.org/wiki/Affiliate-selected_Board_seats/2019 give some lengthy informations, here is a quick summary: - since April 15 and until April 30, people will candidate to seat at the board, at this step we can ask question to candidates and *endorse* two candidates. - between May 8 and May 31, we can vote. For this whole process, I am the primary contact but we *all* make the decision, I'm merely the messenger of the group here. Here is how I suggest to proceed: - right now, write together questions and criteria for candidate we want to endorse (WMNL shared this table to help https://meta.wikimedia.org/wiki/File:Assessing_candidates_for_the_Affiliate-selected_Board_seats_of_the_Board_of_Trustees.pdf but it's very general, we should adapt it to this usergroup needs ; here is copy of this table https://lite.framacalc.org/asbs2019-wcug we can work on). You can also ask question in your own name. - in May, we vote for the candidates inside the user group (not sure how to best handle this part, I would prefer it to be public but we can do it in private too) and then, I will take the results and vote in the name of the user group. - is anyone interested to be the secondary contact? (I'm a bit busy so I could use some help ;) ) - if you feel the need, we can do an online meeting to talk about it, but as we are scattered all around the globe, finding a good timeslot is challenging. Would anyone be interested? (or is this mailing list enough?) - obviously, any question, idea, remark, suggestion are welcome! Cheers, ~nicolas ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
[Wikisource-l] Multiple interwiki
Of course, this is about interwiki, not about toolbar. I am sorry for wrong subject in my previous email.. Ankry W dniu 11.03.2019 o 16:15, Ankry pisze: Just FYI. As ETA for this work: https://phabricator.wikimedia.org/T128173 cannot be even estimated, we have utilized in pl.wikisource the old Swedish solution (by Innocent bystander) for providing interwikis based on the work/edition Wikidata model. This is a modified sv.ws solution with an anti-loop protection. This solution also (unlike the original) merges iw links from the "work" item if there is no "edition" item from the specific wiki. (Such pages seem to be "old" interwikis in most cases.) Of course, this sulution works only if there are already appropriate data in Wikidata; and moving the data there seems to be the main problem. The pages utilizing this feature can be found in the category: https://pl.wikisource.org/wiki/Kategoria:Strony_z_interwiki_utworzonymi_za_pomoc%C4%85_arbitralnego_dost%C4%99pu_do_Wikidata New feature is visible in works of: Byron, Lagerlöf, Moliere, Shakespeare, Sienkiewicz, Verne and of few others. If anybody interested, I can provide more technical details. Regards Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] old toolbar is back
Just FYI. As ETA for this work: https://phabricator.wikimedia.org/T128173 cannot be even estimated, we have utilized in pl.wikisource the old Swedish solution (by Innocent bystander) for providing interwikis based on the work/edition Wikidata model. This is a modified sv.ws solution with an anti-loop protection. This solution also (unlike the original) merges iw links from the "work" item if there is no "edition" item from the specific wiki. (Such pages seem to be "old" interwikis in most cases.) Of course, this sulution works only if there are already appropriate data in Wikidata; and moving the data there seems to be the main problem. The pages utilizing this feature can be found in the category: https://pl.wikisource.org/wiki/Kategoria:Strony_z_interwiki_utworzonymi_za_pomoc%C4%85_arbitralnego_dost%C4%99pu_do_Wikidata New feature is visible in works of: Byron, Lagerlöf, Moliere, Shakespeare, Sienkiewicz, Verne and of few others. If anybody interested, I can provide more technical details. Regards Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Upload/import wizard
> Very interesting. > > About djvu files on IA, they can be built simply by pdf2djvu from pdf > files > of IA, but quality is very poor; [...] Did you try to set the -d parameter to something higher than the default 300? While converting PDF files from Polish digital libraries, I often use -d 450 or -d 600 with good results. Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Indic Wikisource Update November 2016
> Thanks Mathieu. > What really strikes me is that challenge is doable in fr.wikisource: in > many others would be complete madness ;-) > Also, Polish Wikisource is doing great. > > What interest me is understanding how they are building their community of > active and super-active proofreaders: are they doing something that other > wikisource aren't? > > Aubrey I think I will nor betray any secret If I tell about that. At the moment our community is based on few active users and we are trying to support newcommers actively. We noticed that many new users do not like classic on-wiki communication (through talk pages or Scriptorium) so we support them also through other channels (email, IRC). They are always welcome to ask. I think we have no two users that come to the project in the same way. Our users are often active in many fields. We have a Facebook page, sometimes we mention our project on various fan sites (eg few years ago a short note about plwikisource on an ebook fan site brought over 100 new users; a few of them is still active). We also appreciate occasional actions of our fellow colleagues from Polish Wikipedia and Wikimedia PL (interviews, blog articles, workshops). We notice that our community originates from different societies than Wikipedia community (in Wikipedia some level of creativity is required, in Wikisource other skills are preferred) and as Polish orthography and grammar did change significantly since XIX c. and even since 1920-ties and 1930-ties, we do not look for new users among teenagers (we do not want to break their fresh orthography-related skills; we look for users rather among retired :) ). Also I think, OCR tools progress (thanks to Wieralee), a short techical guide for newcommers (also thanks to Wieralee) and a lot of automation (thanks to Zdzislaw) made plwikisource more familiar for new users, even if they have no earlier wiki experience. (When I really came to plws in 2010, almost all books were re-written manually) We also noticed that various near goals when announced (eg. reaching 90% ProofreadPage-based pages in main, 300.000 pages in Page namespace, 150.000 proofread pages or prepare the full set of Sienkiewicz's texts onto 100th anniversary of his death) make our community more active. Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Index page move with corresponding Page: move
> Hi all, > > Are there ant tool / bot to Index page move with corresponding Page: move. > We need to rename/move some index page. How could we do? > > Regards, > Jayanta Nath AFAIK, no. And there is very little interest in creating one as index pages moves are rare, and unlikely to happen. However, I sometimes make such renames on plwikisource half-manually with my bot support. All pages in Page namespace need to be moved and transcuding pages need to be fixed. This is slow and unefficient. However, if you describe which index and why you need to be moved I can look at it. Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Template help needed
See footnotes 15 & 16: footnote 15 starts on page 16 and continues on 17 footnote 16 is referenced at page 16, so it starts as empty footnote on page 16 also and continues on 17 (full footnote text there) If you can suggest another solution, I will be intrigued. Ankry > I don't see *two* footnotes start and continue from the one page, I > just see one footnote start on 18 to19, and another start on 19 to 20. > I don't see see two footnotes continue start on 18 or 19 and both > continue to subsequent pages. > > -- billinghurst > > On Tue, Jan 19, 2016 at 12:42 AM, Ankry <an...@mif.pg.gda.pl> wrote: >> Billinghurst wrote: >>> To note that you can use multiple versions of if the >>> reference carries on. Also to note that you cannot use numbers in the >>> ref name, the extension doesn't play, so at enWS we would usually do >>> something like where it is the initial page and >>> continue it. I have never seen two footnotes start and continue from >>> the same page, so it is pretty safe. >> >> It happens. See >> >> https://pl.wikisource.org/wiki/Strona:Cesarz_Juljan_Apostata_i_jego_satyra_Symposion.djvu/16 >> >> https://pl.wikisource.org/wiki/Strona:Cesarz_Juljan_Apostata_i_jego_satyra_Symposion.djvu/17 >> >> Ankry >> >> >> ___ >> Wikisource-l mailing list >> Wikisource-l@lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikisource-l > > ___ > Wikisource-l mailing list > Wikisource-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikisource-l > ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Template help needed
Billinghurst wrote: > To note that you can use multiple versions of if the > reference carries on. Also to note that you cannot use numbers in the > ref name, the extension doesn't play, so at enWS we would usually do > something like where it is the initial page and > continue it. I have never seen two footnotes start and continue from > the same page, so it is pretty safe. It happens. See https://pl.wikisource.org/wiki/Strona:Cesarz_Juljan_Apostata_i_jego_satyra_Symposion.djvu/16 https://pl.wikisource.org/wiki/Strona:Cesarz_Juljan_Apostata_i_jego_satyra_Symposion.djvu/17 Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Template help needed
> Hi, > > I need a template solution for the following proof-reading problem I faced > in Bengali Wikisource. > > There is a reference in Page 1 which is continued in Page 2. I have used > the following code in Page 1:- > > Text of Page 1 reference and text of Page 2 > reference > > It was okay while proof-reading, but when it was transcluded in mainspace, > its not working. There the text of Page 2 reference is not shown. > > Can anyone help me with a solution? Do we need some more templates? > Thanks. This is supported by cite extention internally. Just use: ... on the following page(s), as described here: https://www.mediawiki.org/wiki/Extension:Cite#Merging_two_texts_into_a_single_reference Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Errare humanum est, perseverare diabolicum
> Mathieu Stumpf Guntz, 29/11/2015 18:57: >> What about having both central and local versions? I mean, for community >> stuffs localization is clearly a big pro, and those who are more >> interesting to get extra-localized works could go to the central >> repository which would gather all localized mainspaces. > > Do oldwikisource admins currently force people to go away if their > language is supported elsewhere? Yes they do. Unless there are non-US copyright problems ot the text is really multilingual. Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Errare humanum est, perseverare diabolicum
> On Sun, Nov 29, 2015 at 3:39 PM, Andrea Zanni <zanni.andre...@gmail.com> > wrote: > >> (...) >> >> Unfortunately, for the time being, we hare scattered communities with no >> software support whatsoever: we don't have a Proofread page for >> Right-to-left languages, just imagine how much time it would take to >> redesign a MediaWiki for being a multilanguage, unique digital library, >> in >> which anyone can contribute. >> (...) >> > > What about two multilanguage Wikisources? One for RTL languages, another > for LTR languages. ... and the third for some Asian scripts: https://phabricator.wikimedia.org/T60729 ? And maybe a separate one for French: https://phabricator.wikimedia.org/T14752 ? If you dig deeper then more such issues. Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Errare humanum est, perseverare diabolicum
Maybe it is "fine" but I am afraid it is only "fine" for majority (that speaks English or at least one major European language). As an example, note, that there is very few discussion in Chinese in Village pump despite there is a lot Chinese users there and many of them do not speak English. It is very difficult to operate on Commons for users that speak only Thai, Urdu, Bashkir, Hindi or another not highly populated language. Also there are attempts to discriminate users who do not speak / do not understand English. IMO, there is high risk that merging all wikisources would marginalize minorities or people who are not multilingual. The other issue is (I noticed it in plwikisoure) that few users come to wikisource because they feel bad in large wiki communities (plwiki in our case). (I don't know if there are similar cases in otner wikisources, but likely.) In case, we decide to merge projects they will leave. So disadvantage here is the risk of losing users that we do not have too many. However, there are also advantages of unification and closer cooperation. Question is: will they predominate? Ankry > As to the communication problems well WD and Commons are doing just > fine, it's no problem really. I am actually not an active contributor to > WS but I always had a feeling that I'd perhaps be one if it was not > split. It's easier to work in big project with all infrastructure ready > and big community to help you, in small on the other hand you have to > face the same 1 or 2 people or the time and personal issues may come in > the way of participation. > > I am not a person to have enough energy to run a major RfC in order to > have the WSs joined (as you can see I even failed to show my points in a > structured way) but if such a person shows up I'd gladly support such an > initiative. > > --Base > > On 27.11.2015 17:03, Alex Brollo wrote: >> I'm deeply convinced that splitting wikisource projects into variuos >> languages has been a mistake. >> >> Is anyone so bold to imagine that it is possible to revert that mistake? >> >> Or, are we forced to travel along the/ diabolicum/ trail? >> >> Alex >> >> >> >> >> >> ___ >> Wikisource-l mailing list >> Wikisource-l@lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikisource-l > > ___ > Wikisource-l mailing list > Wikisource-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikisource-l > ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Template Wikipedia
In many cases this relation may be not of 1-1 type. Unless you connect disambig pages to Wikipedia in case of text variants. Or if you have no text with variants in your wiki... Ankry > Hi all! > > As is typical for smaller communities, connecting all the pages to > Wikidata > items can be a major undertaking. Luckily many users have already used > Template:Wikipdia (https://www.wikidata.org/wiki/Q15632185) to connect > Wikisource pages to Wikipedia pages. Because Wikipedia pages are already > connected quite well to Wikidata, it is easy to find the common item. > > I ran a bot on ar-wikisource and found ~400 inclusions of the template. > The > bot set ~170 sitelinks. The rest of the pages either already had a > sitelink > or the corresponding Wikipedia page did not have a Wikidata-item yet. > > Having also checked around 30 items by hand I couldn't find any mistakes, > which shows that the template is well curated. If anyone would like me to > run the bot on another language of Wikisource or share the code just send > me a message. > > -Tobias > ___ > Wikisource-l mailing list > Wikisource-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikisource-l > ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Import 80mb+ file size to commons through ia-upload
Just FYI.
As this bug:
https://phabricator.wikimedia.org/T94562
seems to be fixed, hopefully, the problems with uploading big DjVu files
using upload wizard should diappear. I have tested it today with few
60-70MB DjVus and everything seems to be fine.
I think, the url2commons tool also uses stash upload, so it was also hit
by this bug. Starting from today, I would expect less number of problem
reports related to uploads from IA.
However, we still have the misleading message on
https://commons.wikimedia.org/wiki/Special:Upload
suggesting that any user can upload files up to 1GB in size.
In fact, the limit here is 100MB. And only stewards/Commons admins/license
reviewers can omit it using direct URL upload.
Other users should be able to upload >100MB files using UploaadWizard with
chunked upload enabled.
Ankry
> Done. Thanks you Billinghurst.
>
> On Wed, Oct 28, 2015 at 1:37 AM, billinghurst <billinghurstw...@gmail.com>
> wrote:
>
>> Try using url2commons on toollabs; it is OAuth too. You will need to
>> create a filled-in {{book}} manually.
>>
>> If that fails take the template and let me know where you have poked it
>> and I will import the file directly.
>>
>> On Wed, 28 Oct 2015 04:55 Jayanta Nath <jayanta...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> How do I import 80mb+ file size to commons through ia-upload? During
>>> import , the tool got error gar-beg, Can anyone try to import
>>> https://archive.org/details/UpendraKishoreRachanaSamagra to common
>>> through ia-upload?
>>>
>>> Regards,
>>> Jayanatanth
>>> BNWS
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Virtual Transcription Laboratory
There's another contact address here: http://wlt.synat.pcss.pl/wlt-web/contact.xhtml It seems the project is no longer in development phase. Ankry > I swapped a few tweets with the developer, Adam Dudczak (maneo on Twitter) > back in 2013. Looking at his LinkedIn profile, it seems he left that job > in early 2014. > > If you find out more about the status of VTL, I'd love to hear about it. > > Ben Brumfield > http://fromthepage.com/ > http://manuscripttranscription.blogspot.com/ > > On Thu, Oct 8, 2015 at 11:35 AM, Federico Leva (Nemo) <nemow...@gmail.com> > wrote: > >> Apparently, this rather mysterious project allows some select libraries >> to >> import a special flavour of DjVu into a system for manual transcription >> (and OCR training?). >> >> https://confluence.man.poznan.pl/community/display/WLT/Introduction+to+Virtual+Transcription+Laboratory >> Found via http://succeed-project.eu/wiki/index.php/Cutouts >> >> Nemo >> >> ___ >> Wikisource-l mailing list >> Wikisource-l@lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikisource-l >> > ___ > Wikisource-l mailing list > Wikisource-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikisource-l > ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Tech issues
Maybe an effect of no longer supported document.write() in scripts that we were warned some time ago? Just guessing... Ankry > I didin't find anything similar. Do you find the same issue with the same > PC with different connections, or with different PC under the same > connection? What happens if you log out? > > Alex > > 2015-09-11 15:19 GMT+02:00 Federico Leva (Nemo) <nemow...@gmail.com>: > >> What error do you see? Something like "connection refused"? How does >> your >> computer connect to the internet? Do things improve if you delete your >> cookies for the domains which don't work? >> >> Do you manage to perform some basic networking diagnostic e.g. with >> http://winmtr.net/ ? >> >> Nemo >> >> ___ >> Wikisource-l mailing list >> Wikisource-l@lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikisource-l >> > ___ > Wikisource-l mailing list > Wikisource-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikisource-l > ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] ia-upload error
> When I am trying to upload by > https://tools.wmflabs.org/ia-upload/commons/init from > https://archive.org/details/KoranSharifBhaiGirishchandraSen, I am > getting the error, > > "The upload to WikimediaCommons failed: Client error response [status > code] 413 [reason phrase] Request Entity Too Large [url] > https://commons.wikimedia.org/w/api.php?action=upload=Koran_Sharif-Bhai_Girish_chandra_Sen.djvu=json; Uploaded their djvu (55MB) manually here: https://commons.wikimedia.org/wiki/File:Koran-Sharif-Bhai-Girishchandra-Sen.djvu Maybe the generated djvu exceeded 100MB filesize limit? Ankry ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Better way to validate pages
If you wish to add the Big Validate Button in a specific Wikisource, it is your choice. But the Polish language Wikisource will definitely refuse to use such a tool. So it should never become a general tool. We have VERY BAD experience with new users making the final validation process. Noticing an OCR error omited in previous stages is often a problem for a user unexperienced in work with OCR-based texts. In general, they just read both texts, do not compare them word-by-word so they often cannot notice mistakes like: missing paragraph, missing line of text, wrong word and also aften miss a typo (eg. missing letter). Our OCR tetxs are full of OCR-specific typos, like m instead of in rn instead of m 1 instead of l l instead of 1 l instead of ł ą instead of ę i instead of ! , instead of . . instead of , wrong capitalization missing or extra diacritic marks In most cases such typos are impossible to eliminate using dictionary-based tests as both words (OCR-created and the correct one) exist in the OCR dictionary. Another disadvantage of directing new users to the validation process (especially without even viewing the code) is that they might NEVER learn how to format texts (or even fix broken formatting) as they might never need to use it! It does not matter whether it is low-level template-based formatting process or using VE (however, it is likely that wrong formatting enetered using VE might be difficult to fix while also using VE). In plwikisource we prefer to direct new users to start work with simple texts, when little formatting is required (eg. short stories, novels, simple poetry) entering them (basing on pre-formatted OCR) or to do the first Proofread stage (red - yellow) than direct them to final validation. Maybe OCR in other languages is much better or you do not care for final text quality - but it definitely should be a choice. Ankry Date: Mon, 10 Aug 2015 18:14:20 +0200 Andrea Zanni wrote: The Big Validate Button is a good idea, but I also would like a better navigation experience, as it is pretty slow and cumbersome to got on the top of the page to click a tiny arrow, wait for the new page, click edit, etc. Aubrey On Mon, Aug 10, 2015 at 4:29 PM, Alex Brollo alex.bro...@gmail.com wrote: If this is true, then to add a big button Validate to edit by ajax the code of the page (the header section only needs to be changed if there's no error to fix into the txt) should be a banal task for a good programmer. Perhaps Andrea is asking for much more, but this could be a first step. Alex 2015-08-10 14:47 GMT+01:00 Nicolas VIGNERON vigneron.nico...@gmail.com: 2015-08-10 15:37 GMT+02:00 Alex Brollo alex.bro...@gmail.com: First point is: is it a safe practice to validate a page without reviewing its raw code? Probably yes. Obviously, it's safer to check the raw code but it's unrealistic to expect the raw code to be review for all page. Anyway, the pages doesn't contain a lot of code (and most pages does'nt contain code at all), so it doesn't seems to be crucial to me. Plus : when VisualEditor will be on WS, less and less people will actually see the raw wikicode. A second point: is it a safe practice to validate a page without carefully reviewing its transclusion into ns0? Definitively yes. When can a transclusion can go wrong? In all cases I can think of, the problem come from templates, css classes or general stuff like that. It should be fixed generally and it shouldn't block the page validation since it have nothing to do the the page itself (but maybe I'm missing an obvious example here). Alex Cdlt, ~nicolas ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Better way to validate pages
That's a very good idea. NO! NO! NO! It is suggesting new users to behave like bots! Just click and go on? Why to read the small-lettering texts? Just click the GGB (Great Green Button). In Polish language Wikisource we have VERY BAD experience with directing new users to the final validation process: they can't carefully compare the text in both windows word-by-word. They just read both texts (and maybe one only?) and click validate next. Later we found a lot of unnoticed OCR-related mistakes like: - missing last paragraph - missing a line - typos like m-rn, in-m, ę-ą, o-n, etc. Even 5-10 mistakes per a GREEN page (whan it was based on poor scans/poor OCR). In our opinion people need to LEARN how to compare texts. And it is easier to learn when there are more mistakes to notice when there is only a few of them. If you want to decrease quality or you believe you have perfect OCR software, plese do it for specified Wikisource subdomains, not as general tool. plwikisource highly discourage such a tool. Ankry A big green button validate at the end of the displayed wikitext content of the page may fit the need. It would open a confirmation popup with an explanation message the first k times the user click on it in order to make sure new contributors use it well (with k something like 3 or 5). What do you think about it? I'll have some free time in a few weeks to implement a such thing directly into the ProofreadPage extension. Thomas Le 10 ao?t 2015 ? 14:31, Alex Brollo alex.bro...@gmail.com a écrit : Ok; imagine that while opening a level 3 page, an ajax query uploads quietly the raw code of the page; as soon as you click the Big Green Button the script could edit the code and send it to the server - in milliseconds - and immediately could click the next page button. If a review of page in view mode is all what is needed to validate it, there's no reason to enter in edit mode when there's nothing to fix. Alex 2015-08-10 18:14 GMT+02:00 Andrea Zanni zanni.andre...@gmail.com: The Big Validate Button is a good idea, but I also would like a better navigation experience, as it is pretty slow and cumbersome to got on the top of the page to click a tiny arrow, wait for the new page, click edit, etc. Aubrey On Mon, Aug 10, 2015 at 4:29 PM, Alex Brollo alex.bro...@gmail.com wrote: If this is true, then to add a big button Validate to edit by ajax the code of the page (the header section only needs to be changed if there's no error to fix into the txt) should be a banal task for a good programmer. Perhaps Andrea is asking for much more, but this could be a first step. Alex 2015-08-10 14:47 GMT+01:00 Nicolas VIGNERON vigneron.nico...@gmail.com: 2015-08-10 15:37 GMT+02:00 Alex Brollo alex.bro...@gmail.com: First point is: is it a safe practice to validate a page without reviewing its raw code? Probably yes. Obviously, it's safer to check the raw code but it's unrealistic to expect the raw code to be review for all page. Anyway, the pages doesn't contain a lot of code (and most pages does'nt contain code at all), so it doesn't seems to be crucial to me. Plus : when VisualEditor will be on WS, less and less people will actually see the raw wikicode. A second point: is it a safe practice to validate a page without carefully reviewing its transclusion into ns0? Definitively yes. When can a transclusion can go wrong? In all cases I can think of, the problem come from templates, css classes or general stuff like that. It should be fixed generally and it shouldn't block the page validation since it have nothing to do the the page itself (but maybe I'm missing an obvious example here). Alex Cdlt, ~nicolas ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l ___ Wikisource-l mailing list Wikisource-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Re: [Wikisource-l] Better way to validate pages
Ankry, there's no need to shout :-) We are just *talking*, nobody is coming to Polish Wikisource and make you use a tool you don't want. You do what the Polish community wants to do. I'm sorry, maybe I misunderstood. I thought you want to include it into ProofreadPage extension as the default behaviour for the last step of validation process. That is what I oppose to. And only that. Ankry Still, it's 10 years I'm on Wikisource projects (it.ws) and worries me the most is that the community grows slwly. It's too slow, and the web changes rapidly, and our infrastructure becomes rapidly obsolete. I think (but I do not have hard data) that we would have many ways to make users active and teach them how to format things. But a big green button like if you see an error fix it could be useful. Maybe we don't need to link it to the validation process, and let users understand that by themself. But I still think that we need to low the complexity of wikisource if we want our communities to grow and thrive. I repeat, there can be many ways to achieve this goal, but for me it's a crucial goal. Aubrey On Tue, Aug 11, 2015 at 11:45 AM, an...@mif.pg.gda.pl wrote: That's a very good idea. NO! NO! NO! It is suggesting new users to behave like bots! Just click and go on? Why to read the small-lettering texts? Just click the GGB (Great Green Button). In Polish language Wikisource we have VERY BAD experience with directing new users to the final validation process: they can't carefully compare the text in both windows word-by-word. They just read both texts (and maybe one only?) and click validate next. Later we found a lot of unnoticed OCR-related mistakes like: - missing last paragraph - missing a line - typos like m-rn, in-m, ę-ą, o-n, etc. Even 5-10 mistakes per a GREEN page (whan it was based on poor scans/poor OCR). In our opinion people need to LEARN how to compare texts. And it is easier to learn when there are more mistakes to notice when there is only a few of them. If you want to decrease quality or you believe you have perfect OCR software, plese do it for specified Wikisource subdomains, not as general tool. plwikisource highly discourage such a tool. Ankry A big green button validate at the end of the displayed wikitext content of the page may fit the need. It would open a confirmation popup with an explanation message the first k times the user click on it in order to make sure new contributors use it well (with k something like 3 or 5). What do you think about it? I'll have some free time in a few weeks to implement a such thing directly into the ProofreadPage extension. Thomas Le 10 ao?t 2015 ? 14:31, Alex Brollo alex.bro...@gmail.com a écrit : Ok; imagine that while opening a level 3 page, an ajax query uploads quietly the raw code of the page; as soon as you click the Big Green Button the script could edit the code and send it to the server - in milliseconds - and immediately could click the next page button. If a review of page in view mode is all what is needed to validate it, there's no reason to enter in edit mode when there's nothing to fix. Alex 2015-08-10 18:14 GMT+02:00 Andrea Zanni zanni.andre...@gmail.com: The Big Validate Button is a good idea, but I also would like a better navigation experience, as it is pretty slow and cumbersome to got on the top of the page to click a tiny arrow, wait for the new page, click edit, etc. Aubrey On Mon, Aug 10, 2015 at 4:29 PM, Alex Brollo alex.bro...@gmail.com wrote: If this is true, then to add a big button Validate to edit by ajax the code of the page (the header section only needs to be changed if there's no error to fix into the txt) should be a banal task for a good programmer. Perhaps Andrea is asking for much more, but this could be a first step. Alex 2015-08-10 14:47 GMT+01:00 Nicolas VIGNERON vigneron.nico...@gmail.com: 2015-08-10 15:37 GMT+02:00 Alex Brollo alex.bro...@gmail.com: First point is: is it a safe practice to validate a page without reviewing its raw code? Probably yes. Obviously, it's safer to check the raw code but it's unrealistic to expect the raw code to be review for all page. Anyway, the pages doesn't contain a lot of code (and most pages does'nt contain code at all), so it doesn't seems to be crucial to me. Plus : when VisualEditor will be on WS, less and less people will actually see the raw wikicode. A second point: is it a safe practice to validate a page without carefully reviewing its transclusion into ns0? Definitively yes. When can a transclusion can go wrong? In all cases I can think of, the problem come from templates, css classes or general stuff like that. It should be fixed generally and it shouldn't block the page validation since it have nothing to do the the page itself (but maybe I'm missing
