Wikisource:Scriptorium/Archives/2021

From Wikisource
Jump to navigation Jump to search

About long poems[edit]

Hello everyone and happy new year. This is my first time coming to Wikisource. Wanna say, it's really nice here.

If I do edit, I'll be editing Georgian entries/poems, so I have a few questions on formatting and especially on long poems. Right now დავითიანი exists as a page written in Latin script. Itself, it's a long poem consisting of different chapters and one of the chapters is ALREADY separated as another page სწავლა მოსწავლეთა, which I just recently filled. So, uhm, what would be the best:

  1. delete სწავლა მოსწავლეთა and keep დავითიანი to renew it
  2. delete დავითიანი and add all chapters separately.

Another question is, if we choose the second option, should we like create a category called დავითიანი under დავით გურამიშვილის პოემები (poems of davit guramishvili) and have all chapters there?

Thank you in advance :D -Solarkoid (talk) 15:56, 3 January 2021 (UTC)[reply]

As far as I can see we have a georgian section here, see Category:Georgian. Try to find somebody there and discuss this problem with him/her. If there is something to be deleted so mark the page with {{delete}} + reason, no problem for me or for my colleagues to do so. Cheers -jkb- (talk) 21:57, 3 January 2021 (UTC)[reply]

Advanced Search "Pages in this language" is not working as described[edit]

Hi, I tried a simple Advanced Search of "automobile" and then selected "English" from the drop down on Pages in this language. But the search results still show source texts in other languages that are not English. I noticed the Info icon next to the Pages in this language that describes how it should work, but it doesn't work as described. --Thadguidry (talk) 20:07, 9 January 2021 (UTC)[reply]

@Thadguidry: This is a great point. There is a problem here with data integrity and I've fixed a few hundred pages but there are tens of thousands left to go. The problem is, if you go to any page (e.g. Page:Ag séideadh agus ag ithe - Ua Laoghaire.djvu/24), you can see page information (in this case: https://wikisource.org/w/index.php?title=Page:Ag_s%C3%A9ideadh_agus_ag_ithe_-_Ua_Laoghaire.djvu/24&action=info) and one of the pieces of info stored here is the language (in this case, it's correct: "ga - Irish"). So when you are using the search by language feature, the MediaWiki software should only be searching pages that have the correct language. Unfortunately, since the default is English, unless someone deliberately changes a given page's information to another language, then many English-language pages will show up flooding results. E.g. Әкеміз was in "en - English" until just now, when I changed it to "kk - Kazakh".Justin (koavf)TCM 23:58, 9 January 2021 (UTC)[reply]
To be more clear, I initiated the Advanced Search from the regular domain Wikisource URL. I did not initiate the search from the English subdomain Wikisource URL. By the way, I keep getting an error when I try to include URL's in my posting and replies here. It keeps saying I'm a new user or something and is treating them as external URL's and SPAM so I cannot give you the URL's I'm using to help. (Help Admin?) --Thadguidry (talk) 01:38, 10 January 2021 (UTC)[reply]
@Thadguidry: Yes, I understood that you were searching this edition of Wikisource and not en:. Unfortunately, admins can't unilaterally make you able to be able to post links (without editing the edit filter itself): you'll have to make [x] edits and be a member here for [y] days in order for that restriction to be lifted. —Justin (koavf)TCM 01:46, 10 January 2021 (UTC)[reply]
So what are your next steps to resolve the search filtering problem? Or is this some mass corrections that need to be made to tens of thousands of pages and is really the only proper way to fix it? I.E. is it simply a problem because some users made pages in some wrong language category? --Thadguidry (talk) 02:00, 10 January 2021 (UTC)[reply]
Mass corrections. The problem is that persons made pages not in the wrong language as such but that the new pages weren't marked with a language and that default is English. Search in a non-English language and you are liable to get better results but they will be incomplete and missing all of the pages that aren't properly marked. —Justin (koavf)TCM 02:40, 10 January 2021 (UTC)[reply]

15:42, 11 January 2021 (UTC)

MediaWiki:Sp-contributions-footer[edit]

Can somebody tell me why the MediaWiki:Sp-contributions-footer (and MediaWiki:Sp-contributions-footer-anon) do not work? We have both since years. -jkb- (talk) 20:45, 12 January 2021 (UTC)[reply]

@-jkb-: Not sure what you mean. When I go to Special:Contributions/-jkb-, I see that footer displayed. —Justin (koavf)TCM 08:19, 14 January 2021 (UTC)[reply]
I wonder what is wrong. When I see the contribution pages (both registered user and IPs) I don't see it. When I go to other projects (either wikisource or wikipedie) everything is OK. As far as I can see I have no sdcripts here that could influence this... -jkb- (talk) 15:05, 14 January 2021 (UTC)[reply]
@-jkb-: Maybe it's your skin? Shows up fine in Monobook. —Justin (koavf)TCM 01:13, 15 January 2021 (UTC)[reply]
I`m sure not. I use vector since years, and as I said, I have no problems with vector in other projects :-( -jkb- (talk) 17:32, 15 January 2021 (UTC)[reply]

16:10, 18 January 2021 (UTC)

Hi! The MediaWiki Wikisource extension is installed on all language-based Wikisources but not on old Wikisource. This extension now contains code to link to Wsexport in the MediaWiki navigation sidebar. So, it might make sense to install it here too in order to replace the current wsexport gadget. Is there anyone who has concerns about it? Tpt (talk) 20:31, 20 January 2021 (UTC)[reply]

While silence is approval, I don't like it when no one responds to good faith questions like this. So to chime in: I don't have concerns and I don't see any reason why this edition of Wikisource would be exempt. —Justin (koavf)TCM 22:14, 20 January 2021 (UTC)[reply]
Honestly, I have no Idea what the extension could be :-); if people, who can judge it, have no objections, so do I. -jkb- (talk) 23:04, 20 January 2021 (UTC)[reply]
+1 from me. —Sam Wilson 00:46, 21 January 2021 (UTC)[reply]
It's now done. Tpt (talk) 13:58, 23 January 2021 (UTC)[reply]

Importer ma thèse de doctorat depuis Wikiversité - Import my PhD thesis from Wikiversity[edit]

Hello !

Juste un petit message pour savoir s’il est envisageable d'importer ma thèse de doctorat en provenance de Wikiversité dans le but de la publier sur Wikisource dès qu'elle sera terminée ?

Just a little message to know if it's possible to import my PhD thesis from Wikiversity in order to publish it on Wikisource as soon as it's finished?

Lionel Scheepmans (talk) 09:10, 22 January 2021 (UTC)[reply]

@Lionel Scheepmans: You should ask at s:fr:. —Justin (koavf)TCM 11:59, 22 January 2021 (UTC)[reply]
Done Lionel Scheepmans (talk) 13:16, 22 January 2021 (UTC)[reply]

18:31, 25 January 2021 (UTC)

Share your feedback on the OCR improvements![edit]

Hello, everyone! We (the team responsible for the Community Wishlist Survey) have just launched the project for OCR improvements! With this project, we aim to improve the experience of using OCR tools on Wikisource. Please refer to our project page, which provides a full summary of the project and the main problem areas that we have identified.

We would then love if you could answer the questions below. Your feedback is incredibly important to us and it will directly impact the choices we make. Thank you in advance, and we look forward to reading your feedback! SGrabarczuk (WMF) (talk) 20:08, 26 January 2021 (UTC)[reply]

Moving Wikimania 2021 to a Virtual Event[edit]

Wikimania's logo.

Hello. Apologies if you are not reading this message in your native language. Please help translate to your language. Thank you!

Wikimania will be a virtual event this year, and hosted by a wide group of community members. Whenever the next in-person large gathering is possible again, the ESEAP Core Organizing Team will be in charge of it. Stay tuned for more information about how you can get involved in the planning process and other aspects of the event. Please read the longer version of this announcement on wikimedia-l.

ESEAP Core Organizing Team, Wikimania Steering Committee, Wikimedia Foundation Events Team, 15:16, 27 January 2021 (UTC)

Project Grant Open Call[edit]

This is the announcement for the Project Grants program open call that started on January 11, with the submission deadline of February 10, 2021.
This first open call will be focussed on Community Organizing proposals. A second open call focused on research and software proposals is scheduled from February 15 with a submission deadline of March 16, 2021.

For the Round 1 open call, we invite you to propose grant applications that fall under community development and organizing (offline and online) categories. Project Grant funds are available to support individuals, groups, and organizations to implement new experiments and proven ideas, from organizing a better process on your wiki, coordinating a campaign or editathon series to providing other support for community building. We offer the following resources to help you plan your project and complete a grant proposal:

Program officers are also available to offer individualized proposal support upon request. Contact us if you would like feedback or more information.

We are excited to see your grant ideas that will support our community and make an impact on the future of Wikimedia projects. Put your idea into motion, and submit your proposal by February 10, 2021!

Please feel free to get in touch with questions about getting started with your grant application, or about serving on the Project Grants Committee. Contact us at projectgrantsTemplate:Atwikimedia.org. Please help us translate this message to your local language. MediaWiki message delivery (talk) 08:01, 28 January 2021 (UTC)[reply]

22:38, 1 February 2021 (UTC)

On WIkidata links[edit]

Heads up that they got delayed but for those who don't know, soon, d: will support linking to this edition of Wikisource. Follow phab:T138332 for more. —Justin (koavf)TCM 08:33, 2 February 2021 (UTC)[reply]

That's good to know. Thanks for keeping us informed :) --Ooswesthoesbes (talk) 15:35, 2 February 2021 (UTC)[reply]

17:42, 8 February 2021 (UTC)

17:56, 15 February 2021 (UTC)


00:17, 23 February 2021 (UTC)

Wikidata links are here![edit]

Following from #On WIkidata links, it is now possibile to link Wikidata items to pages on this site, finally! Many thanks to the people who made this possible.

Links can be added in the "Multilingual sites" box (not the "Wikisource" box), by typing "s" for "sources" or "m" for "multilingual wikisource" (example).

Previously, we used Template:Interwiki to simulate a link; this template should no longer be used. On pages that use it, we need to add the link on Wikidata and then remove the template, I will start doing it but help is welcome. Candalua (talk) 08:30, 24 February 2021 (UTC)[reply]

  • Actually it looks like no one asked for interlanguage links, so everything works except for interlanguage links, and now the developers ask for community consensus to enable interlanguage links as well. I obviously  Support enabling interlanguage links pointing to other Wikisources (not Wikipediæ, as on other multilingual wikis), and hope that many other people will express their opinion. —Tacsipacsi (talk) 10:51, 27 February 2021 (UTC)[reply]
 Support Candalua (talk) 20:04, 28 February 2021 (UTC)[reply]
 Support --Ooswesthoesbes (talk) 20:28, 28 February 2021 (UTC)[reply]
 Support yep -jkb- (talk) 21:20, 28 February 2021 (UTC)[reply]

See the new phab T275958 as well - -jkb- (talk) 18:46, 27 February 2021 (UTC)[reply]

Two main pages?[edit]

When creating items for main pages, I came across the following pairs:

Maybe they can be merged, maybe not. Jura1 (talk) 10:43, 28 February 2021 (UTC)[reply]

I merged them. Each one of the two had one page with more contents as well as more edits, so I made the guess that that would be the best one. The other redirects to it. --Ooswesthoesbes (talk) 08:22, 1 March 2021 (UTC)[reply]

19:08, 1 March 2021 (UTC)

Wikifunctions logo contest[edit]

01:49, 2 March 2021 (UTC)

17:51, 8 March 2021 (UTC)

23:22, 15 March 2021 (UTC)

Import Fantasia original from enWS[edit]

Hi,

Fantasia original has been determined to be out of scope for English Wikisource since it contains no English text (it is mainly musical notation in LilyPond with some Italian text), but provided I've understood correctly it should be within scope for mulWS. Could someone with +sysop please import it here? --Xover (talk) 14:26, 18 March 2021 (UTC)[reply]

Well, I see no text there at all. Do we allow such musical notations here? Just a question. -jkb- (talk) 13:02, 19 March 2021 (UTC)[reply]
@-jkb-: There is arguably some Italian there (the counter would be that it's strictly speaking musical notation that happens to use terms borrowed from Italian rather than Italian as such). But my assumption was that music-as-a-sort-of-language was within scope for mulWS, cf. Category:Zxx (No linguistic content). --Xover (talk) 08:06, 20 March 2021 (UTC)[reply]
Here are musical categories on multi.ws. Does it belong to one of them? --Zyephyrus (talk) 22:06, 20 March 2021 (UTC)[reply]
Yep, I know those categories. But: all pages in them are articles (i.e. text articles) about music. The page that should be importet has no text. I'm no musician, but the text are the common "instructions" how the music should be played. No text. If we would agree to import it we should first make an exemption on the page about the scope of this project - in ...This site is a repository of source texts .... Difficult. More oppinions? -jkb- (talk) 22:55, 20 March 2021 (UTC)[reply]
N. B. Well, yes we have such pages in Category:Zxx (No linguistic content), that is right. My question is if it is right. That's all. -jkb- (talk) 22:58, 20 March 2021 (UTC)[reply]
There is some italian instructions not for Italian locutors but for musicians from all languages, so I think these musical notations have their place on multi-ws. Don't you think so? --Zyephyrus (talk) 21:40, 23 March 2021 (UTC)[reply]
Correctly: it is a musical notation with (short) instructions, mostly in italian, but not every time; more over, and this is important for me, it is no text in the meaning of what is the scope of Wikisource. If somebody will to keep such pages he should better apply for a new WMF project for musical notations. My 2 cents. -jkb- (talk) 22:56, 23 March 2021 (UTC)[reply]
And, it is unsourced and unlicensed; by the way, the notation is by José Viñas, a spanish componist, so if, the it could be kept in the es.wikisource as well (I don't think so...). -jkb- (talk) 23:05, 23 March 2021 (UTC)[reply]
FWIW, I agree with -jkb- that the textual content there is negligible. In my opinion, the only sensible thing to do is to treat it as primarily music notation and then ask the question: "Is music notation within scope for mulWS?"

Incidentally, it is definitely out of scope for enWS and the minimum discussion period for the proposed deletion there expired long ago (IOW, it could get deleted there at any time). If there is any reasonable chance it could end up as being determined to be within scope here it would be good to import it temporarily and then rather delete it if it is determined to be outside scope. If it doesn't fit at mulWS there is no other Wikimedia project that will have it. --Xover (talk) 20:49, 25 March 2021 (UTC)[reply]

Non-linguistic texts belong here and we already have musical texts. I'll import it. —Justin (koavf)TCM 07:18, 26 March 2021 (UTC)[reply]

16:53, 22 March 2021 (UTC)

Interwiki link to this web site[edit]

Hello, I would like to know what can I use as syntax for a link pointing to this wikisource international project. If I use s: or [[wikisource:]] I iteratively go to a linguistic version... Lionel Scheepmans (talk) 13:46, 26 March 2021 (UTC)[reply]

@Lionel Scheepmans:: Use s:mul:. —Justin (koavf)TCM 19:36, 26 March 2021 (UTC)[reply]
Perfet @Koavf Thanks ! Lionel Scheepmans (talk) 13:53, 27 March 2021 (UTC)[reply]

17:30, 29 March 2021 (UTC)

19:41, 5 April 2021 (UTC)

Universal Code of Conduct – 2021 consultations[edit]

Universal Code of Conduct Phase 2[edit]

Please help translate to your language

The Universal Code of Conduct (UCoC) provides a universal baseline of acceptable behavior for the entire Wikimedia movement and all its projects. The project is currently in Phase 2, outlining clear enforcement pathways. You can read more about the whole project on its project page.

Drafting Committee: Call for applications[edit]

The Wikimedia Foundation is recruiting volunteers to join a committee to draft how to make the code enforceable. Volunteers on the committee will commit between 2 and 6 hours per week from late April through July and again in October and November. It is important that the committee be diverse and inclusive, and have a range of experiences, including both experienced users and newcomers, and those who have received or responded to, as well as those who have been falsely accused of harassment.

To apply and learn more about the process, see Universal Code of Conduct/Drafting committee.

2021 community consultations: Notice and call for volunteers / translators[edit]

From 5 April – 5 May 2021 there will be conversations on many Wikimedia projects about how to enforce the UCoC. We are looking for volunteers to translate key material, as well as to help host consultations on their own languages or projects using suggested key questions. If you are interested in volunteering for either of these roles, please contact us in whatever language you are most comfortable.

To learn more about this work and other conversations taking place, see Universal Code of Conduct/2021 consultations.

-- Xeno (WMF) (talk) 22:15, 5 April 2021 (UTC)[reply]

Invitation to m:Talk:Universal Code of Conduct/2021 consultations/Discussion[edit]

I am interested in hearing the input of Wikisource users about the application of the Universal Code of Conduct, especially from the perspective of interactions on Wikisource. Xeno (WMF) (talk) 23:54, 17 April 2021 (UTC)[reply]

Line numbering coming soon to all wikis[edit]

-- Johanna Strodt (WMDE) 15:09, 12 April 2021 (UTC)[reply]

16:48, 19 April 2021 (UTC)

Suggested Values[edit]

Timur Vorkul (WMDE) 14:09, 22 April 2021 (UTC)[reply]

Looking for (ancient) Armenian speakers to help transcribe a text on Wikisource[edit]

Recently the French Wikisource community started to work on the transcription of Grammaire de Denys de Thrace. So far you might wonder what the relation with Armenian speakers? Have a look to the full title instead:

GRAMMAIRE de DENIS DE THRACE, tirée de deux manuscrits arméniens de la bibliothèque du roi. Publiée en Grec, en Arménien et en Français, et précédée de considérations générales sur la formation progressive de la Science glossologique chez les anciens, et de quelques détails historiques sur Denis, sur son ouvrage et sur ses commentateurs ; PAR M. CIRBIED, membre de la société royale des antiquaires de france, professeur d’arménien à la bibliothèque du roi. extrait des mémoires de la dite société.

That's a bombastic title if you want my opinion. 😂 However it gives a good overview of what it contains. Especially, it make transparent that the book includes a huge load of material in Armenian. So the text is basically translation and comments of a text in Armenian, itself a translation of an ancient Greek text - also provided in the book. As the French Wikisource community has limited skills on Armenian, it makes the work of transcription far more complicated. Thus this call.

We are looking for people able to make transcriptions of text in Armenian alphabet. It would be even better if we could find people with ancient Armenian, since it is expectable that the text will likely contain oddity of the past. And if we can find someone who can moreover speak French or English to interact in discussions with the community, it would be perfect. Note that the main requirement is simply being able to read Armenian alphabet and to write it in simple Unicode transcription. In particular, there is no expectation that the potential helpers would make any work on the formatting that often require to deal with locale templates.

Please be bold in spreading the word wherever you think that could reach potentially interested Armenian speakers.

With all my warm love, Psychoslave (talk) 07:27, 26 April 2021 (UTC)[reply]

Hello, @Psychoslave: I think, if you really want to find Armenian speakers (either for modern or for ancient Armenian) who might help you and your comrades on this task, then you should also create analogous topic in those Wikimedia projects where to find native Armenian speakers is expected to be more likely than here, that is — on Armenian-language projects. I think, you should consider creating similar topics on those projects:
Good luck, and best regards, Nigmont (talk) 17:07, 27 April 2021 (UTC)[reply]

21:24, 26 April 2021 (UTC)

Japanese vandalism[edit]

Since about march 2021 there are some IPs vandaling this site by creating pages with nonsense and not appropriate content (might be some 200 pages up to now). An overview see User:-jkb-/check. I'm not sure how to proceed this. Global block is a nonsense as it would effect other japanese projects as well. A range block here at oldwikisource: I'm afraid the range is too big, otherwise as there is a japanese wikisource it wouldn't be such a great problem. Otherwise we can block the IPs one by one just like I did up to now. What is your opinion? -jkb- (talk) 16:17, 30 April 2021 (UTC)[reply]

See how these IPs behave after the blocks expire. We have no more administrator natively speaking Japanese. I would like to remind that pre-1926 publication does not automatically expire Japanese copyright, so limited Japanese texts belong here.--Jusjih (talk) 04:08, 9 June 2021 (UTC) (with extremely basic Japanese skill)[reply]
Yes, that's right. But you surely had a look at the stupid nonsense the IPs created and inserted here. That were no texts / documents for PD-US-1923-abroad/JA, but some tweets and spam for some discos, DJs and similar nonsense. By the way, the same range has been blocked global by Tegel, see https://wikisource.org/wiki/Special:Contributions/2400:4052:2C80:4600:0:0:0:0/64 , -jkb- (talk) 09:11, 9 June 2021 (UTC)[reply]

Logo stolen?[edit]

Where ist the Wikisource logo (bottom left) ?? -jkb- (talk) 18:21, 30 April 2021 (UTC)[reply]

15:43, 3 May 2021 (UTC)

15:10, 10 May 2021 (UTC)

13:49, 17 May 2021 (UTC)

17:07, 24 May 2021 (UTC)

17:05, 31 May 2021 (UTC)

20:02, 7 June 2021 (UTC)

Universal Code of Conduct News – Issue 1[edit]

Universal Code of Conduct News
Issue 1, June 2021Read the full newsletter


Welcome to the first issue of Universal Code of Conduct News! This newsletter will help Wikimedians stay involved with the development of the new code, and will distribute relevant news, research, and upcoming events related to the UCoC.

Please note, this is the first issue of UCoC Newsletter which is delivered to all subscribers and projects as an announcement of the initiative. If you want the future issues delivered to your talk page, village pumps, or any specific pages you find appropriate, you need to subscribe here.

You can help us by translating the newsletter issues in your languages to spread the news and create awareness of the new conduct to keep our beloved community safe for all of us. Please add your name here if you want to be informed of the draft issue to translate beforehand. Your participation is valued and appreciated.

  • Affiliate consultations – Wikimedia affiliates of all sizes and types were invited to participate in the UCoC affiliate consultation throughout March and April 2021. (continue reading)
  • 2021 key consultations – The Wikimedia Foundation held enforcement key questions consultations in April and May 2021 to request input about UCoC enforcement from the broader Wikimedia community. (continue reading)
  • Roundtable discussions – The UCoC facilitation team hosted two 90-minute-long public roundtable discussions in May 2021 to discuss UCoC key enforcement questions. More conversations are scheduled. (continue reading)
  • Phase 2 drafting committee – The drafting committee for the phase 2 of the UCoC started their work on 12 May 2021. Read more about their work. (continue reading)
  • Diff blogs – The UCoC facilitators wrote several blog posts based on interesting findings and insights from each community during local project consultation that took place in the 1st quarter of 2021. (continue reading)

--MediaWiki message delivery (talk) 23:06, 11 June 2021 (UTC)[reply]

20:26, 14 June 2021 (UTC)

Please provide input for a Global Conversation on 26-27 June 2021 about the Movement Charter drafting committee[edit]

Hello, I'm one of the Movement Strategy and Governance facilitators working on community engagement for the Movement Charter initiative. I'd like to invite users to participate in an upcoming Global Conversation on 26-27 June 2021 about the Movement Charter drafting committee. Feel free to comment here in any language and see the above links for details (a longer message can be viewed here, delivery was prevented by an edit filter here). Xeno (WMF) (talk) 17:04, 19 June 2021 (UTC)[reply]

phabricator T275958[edit]

The phabricator T275958 (https://phabricator.wikimedia.org/T2759589 = Enable interlanguage links from multilingual Wikisource to other Wikisources) has been moved to the phase testing. -jkb- (talk) 13:46, 21 June 2021 (UTC)[reply]

15:49, 21 June 2021 (UTC)

Today's changes have broken my editor - please help[edit]

This applies to the Page namespace only. The edit box is now much larger than my screen size and there is now (as of today) no way that I can see of altering the size. I need frequent access to the Special characters feature, and there is no way that I can see of getting that feature and the edited text on the screen at the same time, especially when the text is near the bottom of the page. Please help. Jan1nad (talk) 22:59, 24 June 2021 (UTC)[reply]

@Jan1nad: So far as I know there has not been any software changes today. New versions of MediaWiki will usually be deployed on Tuesday or Wednesday, and never normally on a weekend (unless it's a critical bugfix or something like that). Have you tried different web browsers? Or tested when logged out (to make sure it's not something caused by your user scripts and things like that)? Are all page elements otherwise the right size? In case you have turned on your web browser's page zoom function, I mean. Xover (talk) 17:22, 27 June 2021 (UTC)[reply]
@Xover: The flex attribute has been added few days ago to some parts of the interface resulting with stretching of the edit area. @Jan1nad: Maybe adding these changes to your personal commons.css would help you? Ankry (talk) 18:42, 27 June 2021 (UTC)[reply]
@Ankry: Crap. Did that patch go out already? I thought it was still pending for the next deployment. @Jan1nad: If it’s the change Ankry mentioned, I’m sure the developers would appreciate information about your web browser including version number, as well as a description of what exactly changed and what stayed the same (for example, did the scan image change size or just the text field. How did that look before?) Do you use any special settings in your web browser or user scripts, like very small or very large font size, page zoom, custom font face, or anything like that? Xover (talk) 18:54, 27 June 2021 (UTC)[reply]
@Xover: I use a bit ancient FF, but it does not matter: I have made tests on the newest Opera and Chrome and the result is the same. With non-zero flex the edit areas (header+main+footer) are streched to the full scan height. And as the scan height almost always exceeds the window size, the header and the footer cannot be seen together on the screen (also the bottom part of the main textarea is out of the screen is the toolbar area is visible). Switching between them scrolls the whole screen which is very annoying. I use the vertical scan position where the scan width is always the same fraction of the screen width, so the result is independent on font size and/or page zoom. In most standard cases about 70-80% of the scan is visible, and it can be scrolled using a mouse/touchpad when needed. However, there are edge cases like this or this. People using horizontal scan position also report problems. I think, that the size of the edit area should remain configurable as people has various monitors and they use various screen sizes. Editing on an old 1024x768 laptop is different than on a 4k TV-set. And there is a lot in between. Some screenshots: standard interface after recent changes and my interface with the CSS changes applied (note: I am using monobook & the old toolbar, but they do not matter here - the effect is independent on toolbar & skin). Ankry (talk) 21:28, 27 June 2021 (UTC)[reply]
@Ankry: Ah, thanks. That's an excellent description that should let them understand what the issue is. In terms of a solution… if the separators between the header/main/footer text fields were made into drag handles that could be resized in the vertical (only vertical) direction, and the size you set is remembered between pages, would that solve the issue for you? I ask because I believe that's already planned as the next step for this. Xover (talk) 06:17, 28 June 2021 (UTC)[reply]
Do you mean that the total height of all fields will be constant, equal to the full scan height, and I can move the separators only? I think this would be OK for me. But it may be still a problem for users who do not use header/footer view or who use horizontal view. Unless the total height of the edit fields can also be changed. And what about cases when scan height changes significantly between pages? We are sometimes proofreading novels basing on their newspaper editions (eg. if no book edition exists). And the newspaper clippings vary in size (well, proofreading whole newspapers is often pointless and proofreading 4-6 column newspaper pages is very hard, so we use clippings). Ankry (talk) 08:25, 28 June 2021 (UTC)[reply]
I could be wrong, but I believe the current plan is to allow resizing the entire PRP container, including the image. With Flexbox layout the header and footer fields, if visible, should then grow or shrink proportional to the size of the main text field (the ratio is currently 1:6 I believe). The problem with horizontal layout reported on plWS is, I believe, a different one that won't be solved (I don't think) by the patch to allow resizing. Xover (talk) 08:58, 28 June 2021 (UTC)[reply]
@Xover: It's informations that you asked me: web browser - Chrome 90.0.4430.210, MediaWiki skin is Vector. Hitherto I didn't use any scripts and styles that could affect the edit area. I use horizontal scan position. Hitherto a page, edit area and scan area were autonomous and I might scrool all areas autonomous. Earlier when it was possible, I set up an edit area for 80 columns and 15 rows. Now an edit area is bigger and rigid. If you scroll just text area you'll scroll whole page. Today I use user's style and I force size of edit area using #wpTextbox1 {max-height:10em !important;} and it helped. I use Ankry's changes too, just in case. My experiences on both pl and enWS are the same. Tommy Jantarek (talk) 17:23, 28 June 2021 (UTC)[reply]
@Tommy Jantarek: Thanks! The ability to resize the text field vertically (not horizontally) is coming. I think it's still being tested but hasn't been merged yet, so exact timing for when we can expect it to be deployed is unclear as yet. As it currently stands you will not be able to resize it horizontally (make the text field narrower, to for example 80 columns). Will that be sufficient to resolve your issue or is the ability to set a specific width critical to your workflow?
Regarding the scrolling issue… Could it be that the larger size of the text field meant that it could now fit all the text in it without needing to scroll? If a text field has no overflowing text, and thus no scroll bars, and you initiate a scroll with the mouse pointer over it, the web browser will usually infer that you meant to scroll the whole page and not the text field. I was able to reproduce that behaviour with Chrome 91, but so long as the text fields had scroll bars they scrolled independently for me. Would it be possible for you to test that out by simply pasting a lot of text into a text field (so there's more text than can fit its current size) and see if that makes it scroll independently? If this is the explanation for the scrolling issue you experienced I would be hopeful the upcoming changes to enable resizing will alleviate it. Xover (talk) 05:59, 29 June 2021 (UTC)[reply]
@Xover: is the ability to set a specific width critical to your workflow? - No, I use only horizontaly view and height of textarea is important to my work.
Could it be that the larger size of the text field meant that it could now fit all the text in it without needing to scroll? - Exactly, and I tested it in the way you adviced me. I pasted a lot of text and all scrolled indepedently on beginning. Whole page scrolls just in the end of text. It seems that this height of text area is too big just for me and because of it textbox height set on 10em helped me. Tommy Jantarek (talk) 10:55, 29 June 2021 (UTC)[reply]
@Tommy Jantarek: Thanks. The scrolling stuff is web browser behaviour that we can't really control, but the good news is that it sounds like the ability to adjust the height of the text field should solve your problems and make the scrolling thing much less likely to occur. Xover (talk) 12:52, 29 June 2021 (UTC)[reply]
@Ankry Thank you for the suggestion, I tried the CSS - it seemed to make no difference to me. For info, I'm using Windows 10 Firefox on a laptop (no mouse) with zoom set to 110%. All I'm looking for is for the behaviour of the edit box to revert so that it can be resized vertically by dragging (again). Other namespaces (including this one) continue to behave as before. Jan1nad (talk) 18:51, 28 June 2021 (UTC)[reply]
@Jan1nad: The developers are working on a patch to enable vertical resizing. It is still in testing and not merged yet, so the timing for when it will be deployed is not yet clear. But provided I've understood your problem correctly, that change should address it when it lands. Xover (talk) 06:05, 29 June 2021 (UTC)[reply]
Thank you. Jan1nad (talk) 11:23, 30 June 2021 (UTC)[reply]
Is there any expected date for this change yet? Jan1nad (talk) 12:22, 23 April 2022 (UTC)[reply]

Server switch[edit]

SGrabarczuk (WMF) 01:19, 27 June 2021 (UTC)[reply]

16:32, 28 June 2021 (UTC)

Batch uploads of Bodleian scans of the Red Book of Hergest[edit]

Hi all! (Also posted on Commons) I've uploaded a couple of test images in Commons:Category:Red Book of Hergest: scans by the Bodleian Library, using Pattypan. This is a 14th c. Welsh language manuscript. Can someone verify and ok the batch uploading of a further 720 images pls; I welcome any suggestions! I know they could be done on CC0, but the Bodleian Library, Oxford have requested CC-BY for these and I think we should respect that. I'll then create a DjVu of all the images on cy-wikisource; but I also need them as individual pages/images too, so that the resolution isn't compromised on individual WP articles. The text is already done, and good to go. Thanks! Llywelyn2000 (talk) 05:49, 2 July 2021 (UTC)[reply]

Update - I've now uploaded the scans here, with categories. Does any one have a contact email at the Internet Archives pls, so they can pdf them? Any other suggestions? Thanks! PS The Red Book of Hergest is the most important manuscript in the Welsh Language. Llywelyn2000 (talk) 06:49, 13 July 2021 (UTC)[reply]

17:33, 5 July 2021 (UTC)

Some Muscogee-language texts to be transcribed and uploaded[edit]

I have come across http://muskogee.blogs.wm.edu/bookshelf a collection of public domain texts in the Muscogee language, but they are in PDF format and require transcription and uploading. Could someone help out with this? --Sailor Ceres (talk) 00:54, 13 July 2021 (UTC)[reply]

If you want to transfer it into text so you need an OCR application. I guess I saw an OCR for Muscogee, you can google it. But anyway, using it you need somebod who speaks the language well. Then it ould be easy. -jkb- (talk) 09:20, 16 July 2021 (UTC)[reply]
Converting to text can be well done on Wikisource—this is what ProofreadPage is for. —Tacsipacsi (talk) 22:53, 16 July 2021 (UTC)[reply]

Transwiki[edit]

Could anyone do this request for pages which should be imported to Multilingual Wikisource⸮ 217.117.125.83 09:12, 13 July 2021 (UTC)[reply]

Done. I did not assign edits to local users where the named user exists locally as I was unsure if any conflict. Should Wp/yrk/Нюдя ӈэдаханд and Wp/yrk/Сава нум мальӈгана be renamed by dropping "Wp/yrk/"?--Jusjih (talk) 03:54, 18 July 2021 (UTC)[reply]
I categorized these pages to the proper language category, their language is Nenets languages (code yrk). Regarding dropping "Wp/yrk/": in my opinion, it should be done, because this prefix has sence for the Incubator but has no sence for the multilingual Wikisource: there is no policy and common practice here to prefix language pages with language codes, to categorize in the proper language category or its sub-category is well enough. --Nigmont (talk) 09:58, 18 July 2021 (UTC)[reply]
Done moving Wp/yrk/Нюдя ӈэдаханд and Wp/yrk/Сава нум мальӈгана to Нюдя ӈэдаханд and Сава нум мальӈгана. Yet who, when, and where were both works they made?--Jusjih (talk) 23:52, 19 July 2021 (UTC)[reply]

Multilingual Wikisource?[edit]

Hello, why do we have multilingual Wikisource when we have separate language Wikisources? Lightbluerain (talk) 08:07, 19 July 2021 (UTC)[reply]

@Lightbluerain: Multilingual Wikisource is for languages that don’t have separate language Wikisources; it’s similar to Incubator but for Wikisources. —Tacsipacsi (talk) 15:35, 19 July 2021 (UTC)[reply]
Template:PD-US-1923-abroad also explains why separate language Wikisources cannot host some works.--Jusjih (talk) 23:55, 19 July 2021 (UTC)[reply]
Alright, thanks. Lightbluerain (talk) 06:52, 20 July 2021 (UTC)[reply]
In addition to the above, there are also some works which are themselves multilingual. —Justin (koavf)TCM 17:55, 24 July 2021 (UTC)[reply]

15:31, 19 July 2021 (UTC)

21:11, 26 July 2021 (UTC)

Export to hewikisource or not? --Liuxinyu970226 (talk) 05:58, 31 July 2021 (UTC)[reply]

Only the users there may decide.--Jusjih (talk) 01:22, 9 September 2021 (UTC)[reply]

Movement Charter Drafting Committee candidates needed[edit]

Read in other languages
See full announcement (available in other languages)

Movement Strategy announces the Call for Candidates for the Movement Charter Drafting Committee. The Call opens August 2, 2021 and closes September 1, 2021.

This Committee will have around 15 members. It is expected to represent diversity in the Movement. Diversity includes gender, language, geography, and experience. This comprises participation in projects, affiliates, and the Wikimedia Foundation.

Will you help move Wikimedia forward in this important role? Submit your candidacy here. Please contact strategy2030 at wikimedia.org with questions.

Thank you, Xeno (WMF) (talk) 14:45, 2 August 2021 (UTC)[reply]

20:47, 2 August 2021 (UTC)

16:21, 9 August 2021 (UTC)

19:27, 16 August 2021 (UTC)

Universal Code of Conduct - Enforcement draft guidelines review[edit]

The Universal Code of Conduct Phase 2 drafting committee would like comments about the enforcement draft guidelines for the Universal Code of Conduct (UCoC). This review period is planned to begin 17 August 2021.

Community and staff members collaborated to develop these draft guidelines based on consultations, discussions, and research. These guidelines are not final but you can help move the progress forward. Provide comments about these guidelines by 17 October 2021. The committee will be revising the guidelines based upon community input.

Everyone may share comments in a number of places. Facilitators welcome comments in any language on the draft review talk page or by email. Comments can also be shared on talk pages of translations, at local discussions, or during round-table discussions and conversation hours.

There are planned live discussions about the UCoC enforcement draft guidelines:

The facilitation team supporting this review period hopes to reach a large number of communities. Having a shared understanding is important. If you do not see a conversation happening in your community, please organize a discussion. Facilitators can assist you in setting up the conversations.

Discussions will be summarized and presented to the drafting committee every two weeks. The summaries will be published here.

Please let me know if you have any questions about the draft, the community consultation or the UCoC.
Many thanks! --Civvi (WMF) (talk) 20:24, 17 August 2021 (UTC)[reply]

Update on the OCR Improvements[edit]

Hello! The OCR Improvements are complete. We, the Community Tech team, are grateful for your feedback from the beginning to the last stage when we were finalizing the interface.

Engine improvements[edit]

OCR menu in toolbar
OCR menu in toolbar
Reliability

Prior to our work, the OCR tools were separate gadgets. We have added "Wikimedia OCR." It is available under one icon inside the toolbar on all Wikisource wikis. This tool supports two other OCR tools, Tesseract and Google OCR. We expect these tools to be more stable. We will maintain Wikimedia OCR.

The gadgets will remain available. The communities will have sovereignty over when to enable or disable these.

Speed

Prior to this work, transcription would take upwards of 40 seconds. Our improvements average a transcription time under 4 seconds.

Advanced Tools improvements[edit]

Multiple-language support

Documents with multiple languages can be transcribed in a new way.

  1. Open the Advanced Options
  2. Select the Languages (optional) field
  3. Search for and enter the languages in order of prevalence in the document.
UI Crop tool in Advanced tools
Cropping tool / Multi-column support

We have included a Cropper tool. It allows to select regions to transcribe on pages with complicated layouts.

Discoverability and accessibility of OCR

We have added an interface for new users. It is pulsating blue dots over the new icon in the toolbar. The new interface explains what OCR means and what transcription means in Wikisource.

We believe that you will do even more great things because of these changes. We also hope to see you at the 2022 Community Wishlist Survey. Thanks you again for all your opinions and support.

Please share your opinions on the project talk page!

NRodriguez (WMF) and SGrabarczuk (WMF) 01:57, 19 August 2021 (UTC)[reply]

21:58, 23 August 2021 (UTC)

Read-only reminder[edit]

A maintenance operation will be performed on Wednesday August 25 06:00 UTC. It should only last for a few minutes.

This will affect your wiki as well as 11 other wikis. During this time, publishing edits will not be possible.

Also during this time, operations on the CentralAuth will not be possible (GlobalRenames, changing/confirming e-mail addresses, logging into new wikis, password changes).

For more details about the operation and on all impacted services, please check on Phabricator.

A banner will be displayed 30 minutes before the operation.

Please help your community to be aware of this maintenance operation. Thank you!

20:35, 24 August 2021 (UTC)

16:01, 30 August 2021 (UTC)

15:20, 6 September 2021 (UTC)

The 2022 Community Wishlist Survey will happen in January[edit]

SGrabarczuk (WMF) (talk) 00:23, 7 September 2021 (UTC)[reply]

Results for the 2021 Wikimedia Foundation Board of Trustees election[edit]

Read in other languages

Thank you to everyone who participated in the 2021 Board election. The Elections Committee has reviewed the votes of the 2021 Wikimedia Foundation Board of Trustees election, organized to select four new trustees. A record 6,873 people from across 214 projects cast their valid votes. The following four candidates received the most support:

  1. Rosie Stephenson-Goodknight
  2. Victoria Doronina
  3. Dariusz Jemielniak
  4. Lorenzo Losa

While these candidates have been ranked through the community vote, they are not yet appointed to the Board of Trustees. They still need to pass a successful background check and meet the qualifications outlined in the Bylaws. The Board has set a tentative date to appoint new trustees at the end of this month.

Read the full announcement here. Xeno (WMF) (talk) 01:56, 9 September 2021 (UTC)[reply]

Proposal: discontinue Tech News to this board[edit]

I propose to delete the Tech News here without archiving it and also support the unsubscription of this to this board. It is overwhelming this board with frequency and amount of content. It is also not on-topic, as this is a Wikisource general discussion board.

This board is one of hundreds of targets for these news announcements, so people have other options for getting news. Mostly two kinds of users are at this board: experienced Wikimedia editors who know how to access news elsewhere, and less experienced Wikimedia editors who are not looking for archives of news updates.

Support Bluerasberry (talk) 20:32, 9 September 2021 (UTC)[reply]

  • Comment, Why not just have separate places for these news? Tech News contains things like announcements of server switches and technical features that can be beneficial for Wikisource, an example of a better alternative to deleting would be creating something like "Wikisource:Scriptorium/Announcements" which is linked prominently above and only contains this month's (or only six months or a year, depending on how much news / automated messages are actually placed here) announcements and newsletters, while the main Scriptorium could then be exclusively used for community discussions and urgent announcements (exclusively related to Wikisource) free from all the clutter. Note: I am not a frequent contributor here, I just read this website. -- Donald Trung/徵國單  (討論 🀄) (方孔錢 💴) 12:46, 12 September 2021 (UTC)[reply]

I would say No. It should be found by the users. What we can do is to archive the tech news more frequently, might be in a special archive like Tech Archive or something like this. -jkb- (talk) 17:59, 12 September 2021 (UTC)[reply]

Once more: what shall we do wit this? Both alternatives are possible. -jkb- (talk) 21:42, 21 September 2021 (UTC)[reply]

Advice for multilingual text - Popul Vul - Mayan language[edit]

I have this text in various forms including scanned images and digital text.

The original text is in both en:Kʼicheʼ language and Spanish, but I may also have access to translations with Wikimedia compatible copyright.

Here are my questions:

  1. Which language version Wikisource is the right place for central management of this? The original publication contains the full text in K'iche and Spanish.
  2. Can someone point me to a good example of a text in Wikisource which also has translations? I want to see how Wikisource links translations of texts across languages.
  3. K'iche script is unique and has an ISO code. Can anyone tell me if Wikisource can already handle text in that script?
  4. If K'iche is not already set up...
    1. How complicated is it to import an ISO code?
    2. Can I start engaging with the text before setting up the script, or is there some reason why I should sort the script import in Wikisource first?
  5. Can someone else check to confirm that this text is either not already in Wikisource, or otherwise, confirm that I can just start playing around with an upload?
    1. I found es:Popol Vuh but I am not sure which version of text this is or what the source is.

Thanks. Please no one put too much effort into answering these questions. I am still exploring options, and just want casual thoughts at this time. Bluerasberry (talk) 20:47, 9 September 2021 (UTC)[reply]

It is not common here, but we have Hail Mary here for example. -jkb- (talk) 09:39, 10 September 2021 (UTC)[reply]
Thanks, that is helpful. Bluerasberry (talk) 16:24, 10 September 2021 (UTC)[reply]
my pleasure :-) -jkb- (talk) 16:34, 10 September 2021 (UTC)[reply]
As far as I know, MediaWiki can handle any Unicode text, so adding text in K'iche script should be no problem as long as it uses Unicode (but what else would it use in 2021?). This doesn’t ensure that readers will be able to read it, though, but it depends on fonts installed on their computers, for which you/we can only add advice. —Tacsipacsi (talk) 17:26, 10 September 2021 (UTC)[reply]

Call for Candidates for the Movement Charter Drafting Committee ending 14 September 2021[edit]

Movement Strategy announces the Call for Candidates for the Movement Charter Drafting Committee. The Call opens August 2, 2021 and closes September 14, 2021.

The Committee is expected to represent diversity in the Movement. Diversity includes gender, language, geography, and experience. This comprises participation in projects, affiliates, and the Wikimedia Foundation.

English fluency is not required to become a member. If needed, translation and interpretation support is provided. Members will receive an allowance to offset participation costs. It is US$100 every two months.

We are looking for people who have some of the following skills:

  • Know how to write collaboratively. (demonstrated experience is a plus)
  • Are ready to find compromises.
  • Focus on inclusion and diversity.
  • Have knowledge of community consultations.
  • Have intercultural communication experience.
  • Have governance or organization experience in non-profits or communities.
  • Have experience negotiating with different parties.

The Committee is expected to start with 15 people. If there are 20 or more candidates, a mixed election and selection process will happen. If there are 19 or fewer candidates, then the process of selection without election takes place.

Will you help move Wikimedia forward in this important role? Submit your candidacy here. Please contact strategy2030(_AT_)wikimedia.org with questions.

Xeno (WMF) 16:50, 10 September 2021 (UTC)[reply]

Server switch[edit]

SGrabarczuk (WMF) (talk) 00:46, 11 September 2021 (UTC)[reply]

Talk to the Community Tech[edit]

Read this message in another languagePlease help translate to your language

Hello!

As we have recently announced, we, the team working on the Community Wishlist Survey, would like to invite you to an online meeting with us. It will take place on September 15th, 23:00 UTC on Zoom, and will last an hour. Click here to join.

Agenda

Format

The meeting will not be recorded or streamed. Notes without attribution will be taken and published on Meta-Wiki. The presentation (first three points in the agenda) will be given in English.

We can answer questions asked in English, French, Polish, and Spanish. If you would like to ask questions in advance, add them on the Community Wishlist Survey talk page or send to sgrabarczuk@wikimedia.org.

Natalia Rodriguez (the Community Tech manager) will be hosting this meeting.

Invitation link

See you! SGrabarczuk (WMF) (talk) 03:04, 11 September 2021 (UTC)[reply]

Working with other websites (an online library of religious texts)[edit]

While I frequent Wikisource as a reader I don't edit here, so I am quite curious if there are any efforts to reach out to entire websites to import them. While researching religion in South Vietnam I recently found a website called Sacret-Texts.com, they seem to know a lot about US copyright and try to make sure that as much as possible on their website is in the public domain. This website seems like "a perfect match" for Wikisource, is it already being used as a source? Is it useful or do the actual texts need to be available and not just online transcriptions? --Donald Trung (talk) 12:41, 12 September 2021 (UTC)[reply]

I'm afraid you must ask at the vietnamese Wikisource. Cheers, -jkb- (talk) 17:05, 12 September 2021 (UTC)[reply]
These are all in English though. -- Donald Trung/徵國單  (討論 🀄) (方孔錢 💴) 07:58, 14 October 2021 (UTC)[reply]
@Donald Trung: English texts should go to English Wikisource. Here is primarily a place for texts without their own linguistic domain (or free in US, but not free in the country of origin if not accepted in their linguistic domain). Ankry (talk) 17:07, 7 November 2021 (UTC)[reply]

15:35, 13 September 2021 (UTC)

Asking for delete[edit]

The book I currently working Index:ရွှေဘုံနိဒါန်း.pdf is same as ရွှေဘုံနိဒါန်း. Can I make a request to delete ရွှေဘုံနိဒါန်း ? P0rnytail (talk) 15:00, 18 September 2021 (UTC)[reply]

@P0rnytail: Why would we? The goal of proofreading is to eventually transclude the proofread text in the main namespace; the Index and Page namespaces are behind-the-scenes stuff. Instead of deleting, just overwrite the content with the <pages/> tag transcluding the proofread text when you’re done with the proofreading. —Tacsipacsi (talk) 16:41, 18 September 2021 (UTC)[reply]
So, I should move my text to that page after completed. Is that right? If so, what is the role of PDF file on WikiCommons? Should I request to delete that after all the previous stuff done? P0rnytail (talk) 16:48, 18 September 2021 (UTC)[reply]
No, you should transclude it with the wikicode <pages index="ရွှေဘုံနိဒါန်း.pdf" from="3" to="119" /> (assuming that Page:ရွှေဘုံနိဒါန်း.pdf/3 is the first and Page:ရွှေဘုံနိဒါန်း.pdf/119 is the last page containing actual content); obviously this requires that you don’t request deleting any content. There are two purposes of uploading PDFs to Commons: first, it helps the digitization of the book (people without access to a physical copy can help, and you can more easily work in smaller chunks, e.g. digitize one page at a time); second, they serve as a source, anyone can check if the Wikisource text matches the original work. —Tacsipacsi (talk) 18:40, 18 September 2021 (UTC)[reply]

18:32, 20 September 2021 (UTC)

Movement Charter Drafting Committee - Community Elections to take place October 11 - 24[edit]

Dear fellow Wikimedians,

This is an update from the Movement Charter process. We have closed the call for candidates on September 14 for the Drafting Committee and now have a pool of candidates with diverse backgrounds to choose from. As the number of candidates is quite large and thus informing yourself about them might be a bit more complicated, we want to try something different this time: an “Election Compass", more about it in this page.

The 15 member committee will be selected with a 3-step process:

  • Election process for project communities to elect 7 members of the committee.
  • Selection process for affiliates to select 6 members of the committee.
  • Wikimedia Foundation process to appoint 2 members of the committee.
Communities elect 7 members
This announcement is related to the community elections, which will take place in a time period of 2 weeks from October 11 to October 24. We look forward to a wide participation across the communities to create the committee to curate the writing of the Movement Charter. The Election Results will be published on November 1.
Affiliates select 6 members
Parallel to the election process, all affiliates asked to contribute as well: All affiliates were divided into eight geographic and one ‘thematic’ region (check the list), and each region chooses one person who will act as a selector for that region. These 9 selectors will come together to select 6 of the committee (from the same pool of candidates). The selection results will be published on November 1.
Wikimedia Foundation appoints 2 members
Finally, the Wikimedia Foundation will appoint two members to the committee by November 1.

All three processes will be concluded by November 1, 2021, so that the Movement Charter Drafting Committee can start working by then.

For the full context of the Movement Charter, its role, as well the process for its creation, please have a look at Meta. You can also contact us at any time on Telegram or via email (wikimedia2030@wikimedia.org).

Best regards, --Civvi (WMF) (talk) 10:28, 23 September 2021 (UTC)[reply]

Author Pages[edit]

Can anybody provide me with a list of "template" etc pages I need to download / translate in order to create "Author Pages" to Cy-Wikisource, at the moment I'm using the "category pages" to include author details, which is where the author line in transclusion pages goes. But I would prefer dedicated pages, but can't work out how to create them or link to them to them AlwynapHuw (talk) 02:09, 27 September 2021 (UTC)[reply]

22:23, 27 September 2021 (UTC)

Let's talk about the Desktop Improvements[edit]

Hello!

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

Join an online meeting with the team working on the Desktop Improvements! It will take place on October 12th, 16:00 UTC on Zoom. It will last an hour. Click here to join.

Agenda

  • Update on the recent developments
  • Sticky header - presentation of the demo version
  • Questions and answers, discussion

Format

The meeting will not be recorded or streamed. Notes will be taken in a Google Docs file. The presentation part (first two points in the agenda) will be given in English.

We can answer questions asked in English, French, Polish, and Spanish. If you would like to ask questions in advance, add them on the talk page or send them to sgrabarczuk@wikimedia.org.

Olga Vasileva (the team manager) will be hosting this meeting.

Invitation link

We hope to see you! SGrabarczuk (WMF) 15:09, 4 October 2021 (UTC)[reply]

Hello! I'd like to remind that the meeting will happen today. You are welcome to join! SGrabarczuk (WMF) (talk) 15:13, 12 October 2021 (UTC)[reply]

16:31, 4 October 2021 (UTC)

Remove main namespace from wgExtraSignatureNamespaces[edit]

I am planning to remove the main namespace from the wgExtraSignatureNamespaces configuration setting on this wiki. I think this will have very little impact, but letting you know just in case. For more context, see task T291630 (although I'm happy to reply here if you have any questions).

Currently, that configuration setting affects:

It was configured that way in 2014 for all "special" wikis (basically, anything other than the Wikimedia projects with multiple language versions), on the assumption that they often have discussions, including their "village pump" equivalent, in [main namespace]. This doesn't seem correct for this wiki. We're planning to use that config setting for future discussion-related features, and it would probably be unexpected if they showed up in the main namespace here.

Please let me know if there's any problem with this. Thanks. Matma Rex (talk) 18:36, 4 October 2021 (UTC)[reply]

The change has been applied now. Matma Rex (talk) 11:38, 12 October 2021 (UTC)[reply]

15:30, 11 October 2021 (UTC)

Voting for the MCDC Election[edit]

Voting for the election of the members for the Movement Charter drafting committee is now open. In total, 70 Wikimedians from around the world are running for 7 seats in this election.

Voting is open from October 12 to October 24, 2021.

The Movement Charter committee will consist of 15 members in total: The online communities will vote for 7 members, 6 members will be selected by the Wikimedia affiliates through a parallel process, and 2 members will be appointed by the Wikimedia Foundation. The plan is to assemble the committee by November 1, 2021.

You can learn more about each candidate to inform your vote here

You can also learn more about the Drafting Committee here

We are piloting a voting advice application for this election. Click through the tool and you will see which candidate is closest to you! To try out this tool, visit: App

Go vote at SecurePoll: Vote

Read the full announcement: here

Best, --Civvi (WMF) (talk) 15:14, 14 October 2021 (UTC)[reply]

20:53, 18 October 2021 (UTC)

Learn how Movement Strategy Implementation Grants can support your Movement Strategy plans[edit]

Movement Strategy Implementation grants now provide more than $2,000 USD to put Movement Strategy plans into action. Find out more about Movement Strategy Implementation grants, the criteria, and how to apply here.

Also, the Movement Charter Drafting Committee election is still ongoing. It would be great to increase community participation. If you haven't voted now is the time. Please vote here before October 24. Regards, --Civvi (WMF) (talk) 12:43, 21 October 2021 (UTC)[reply]

Talk to the Community Tech[edit]

Read this message in another language

Hello!

We, the team working on the Community Wishlist Survey, would like to invite you to an online meeting with us. It will begin on 27 October (Wednesday) at 14:30 UTC on Zoom, and will last an hour. Click here to join.

Agenda

  • Become a Community Wishlist Survey Ambassador. Help us spread the word about the CWS in your community.
  • Update on the disambiguation and the real-time preview wishes
  • Questions and answers

Format

The meeting will not be recorded or streamed. Notes without attribution will be taken and published on Meta-Wiki. The presentation (all points in the agenda except for the questions and answers) will be given in English.

We can answer questions asked in English, French, Polish, Spanish, German, and Italian. If you would like to ask questions in advance, add them on the Community Wishlist Survey talk page or send to sgrabarczuk@wikimedia.org.

Natalia Rodriguez (the Community Tech manager) will be hosting this meeting.

Invitation link

We hope to see you! SGrabarczuk (WMF) (talk) 23:00, 22 October 2021 (UTC)[reply]

20:08, 25 October 2021 (UTC)

Inactive admins[edit]

There seem to be a number of inactive admins per [140].

Has the community attempted to contacted these users or alternatively, considered removing rights? --Rschen7754 00:46, 1 November 2021 (UTC)[reply]

Voting for desysoping[edit]

I think we should discuss this point - desysoping for long inactivity has happened here some more times, see Wikisource:Administrators#Desysoped for long inactivity. The five names users has not been active since end of 2019. This week I will try to contact them, but apart from this please do give your votes here. -jkb- (talk) 11:19, 1 November 2021 (UTC)[reply]

OK, I didn't see this, you are right, but the other four users are more than two years inactive. -jkb- (talk) 21:18, 8 November 2021 (UTC)[reply]
Any update? --Rschen7754 22:25, 5 December 2021 (UTC)[reply]
@-jkb-, Ooswesthoesbes, Rschen7754: I have started the desysop voting procedure. Ankry (talk) 02:57, 16 January 2022 (UTC)[reply]
Thank you. Usually I wait a few days for them to respond. --Ooswesthoesbes (talk) 07:18, 16 January 2022 (UTC)[reply]

Meet the new Movement Charter Drafting Committee members[edit]

The Movement Charter Drafting Committee election and selection processes are complete.

The committee will convene soon to start its work. The committee can appoint up to three more members to bridge diversity and expertise gaps.

If you are interested in engaging with Movement Charter drafting process, follow the updates on Meta and join the Telegram group.

With thanks from the Movement Strategy and Governance team. --Civvi (WMF) (talk) 15:10, 1 November 2021 (UTC)[reply]

20:28, 1 November 2021 (UTC)

Proposal: discontinue Tech News to this board 2[edit]

New beginning, see above #Proposal: discontinue Tech News to this board. I'm like to change my mind. The different WMF staff, first of all Tech News etc., are really becoming "overwhelming this board with frequency and amount of content." It is not easy to get hier an answer and to discuss our problems. O propose to order WMF staff to something like "Wikisource:Scriptorium/Tech news" or better "Wikisource:Scriptorium/Announcements".

Let us discuss it, then we can reorder the announcements to the new place. Invited are all, and the users who started the first part above especiaslly - @Bluerasberry, Donald Trung:. Thanks, -jkb- (talk) 20:54, 1 November 2021 (UTC)[reply]

Thanks for the reping
I made the original proposal, and I see there are other counter proposals. Here are the options proposed as I understand them:
  1. Do nothing, status quo
  2. Discontinue tech news entirely
  3. Set up new board, send tech news there
  4. status quo for tech news coming to this board, but archive it separately to a new board
I favor some change being made and still think the problem is serious enough to merit a response. This board should be a place for humans to have peer to peer interactions. Because these announcements are from outsiders rather than peers, and because they are off-topic for what humans on this board typically discuss, I feel that this board is not the place for those announcements. I support the messages going anywhere else where people can watch the board and access the messages as they like. It is not my intent to block access to the messages, but these are mass mailings and they do outnumber human posts which I see as much more valuable. Another aspect of solution that I want is something which is zero labor to maintain. If someone volunteers to keep up with archiving after a month then that might help, but I prefer a solution which does not require a human to commit to labor.
Thoughts from others? Bluerasberry (talk) 21:12, 1 November 2021 (UTC)[reply]
It can be helpful messages, but I do see the problem of this page being cluttered up. Therefore, my preference goes out to a separate (sub)page for those messages to be posted on. --Ooswesthoesbes (talk) 17:47, 8 November 2021 (UTC)[reply]
I doubt anyone would read the Tech News messages if they weren't here on at least linked here. Ankry (talk) 22:03, 9 November 2021 (UTC)[reply]

20:36, 8 November 2021 (UTC)

Mensusa accounts[edit]

See User talk:-jkb-#ping ping :-), abuse filter 14, Meta CU request, regards -jkb- (talk) 18:02, 13 November 2021 (UTC)[reply]

Own Checkuser on Oldwikisource - a proposal[edit]

See pls the previous topic #Mensusa accounts and the links to the abuse filter and the CU request at meta. Such request is quite simple (I was CU at Wikilivres for some time) but it costs the stewards a lot of time I guess. Something like this happens here not very often, but however, I think we could have our own checkuser. As far as I know there must be at least two persons (just to control each other, in some projects three etc.), might be we can vote for three. I can gladly apply for it as I know the CU procedure, but that's a matter of choice if we want it. Info: As far as I know, all check users at WMF must announce and confirm their real life identity. 1) do you think we can arrange this and 2) has somebody the interest to apply for it? -jkb- (talk) 20:09, 13 November 2021 (UTC)[reply]

Please carefully read m:CheckUser_policy#Access_to_CheckUser that any wiki must have >= 2 CheckUsers or zero. Thus do not vote until getting at least 2 qualified candidates.--Jusjih (talk) 05:31, 2 December 2021 (UTC) (former CheckUser on English Wikiquote and former steward with no more interest in CheckUser)[reply]
I think, we are discussing on whether we need not about candidates at this point. Ankry (talk) 16:37, 3 December 2021 (UTC)[reply]
Regardless of policy, I do not think that checkuser tools would be helpful here. If an account was not created or it has made no action after creating, there is no logged action for a checkuser. Stewards may do checks in loginwiki, but see no job for a checkuser here. Ankry (talk) 16:37, 3 December 2021 (UTC)[reply]

Pragmatically - I don't think you could get the needed 25 support votes in a timeframe that would be acceptable to stewards. --Rschen7754 22:22, 5 December 2021 (UTC)[reply]

Oh "see no job for a checkuser here" - ehm? See #Mensusa accounts, see [talk:-jkb-#Mensusa_2], see abuse log 14 and CU meta (rejected by Urbanec, wo has some problems with cs.wiki/cs.Source and people from there, my experience). -jkb- (talk) 21:12, 6 December 2021 (UTC)[reply]

Voting for new CheckUsers does not have a definite time frame. Yet getting 25 supports seems hard here.--Jusjih (talk) 06:06, 3 January 2022 (UTC) (admin on 13 wikis, too busy)[reply]

Where can I find nepali language community to talk on wikisource?[edit]

Please redirect me to there.unsigned comment by Kushal Dev Wiki (talk) 14 November 2021 13:50.

I'm afraid there is no one. But try to find some similar languages on Category:Languages or Category:Babel or Category:Main Pages; however there exist the nepali main page where you could fine the authors who were editing it. -jkb- (talk) 13:13, 14 November 2021 (UTC)[reply]
But I'm not sure if they still edit here, might be in this case you should try to reach them on their wikipedias. -jkb- (talk) 13:27, 14 November 2021 (UTC)[reply]

Why different languages have different kind of domains?[edit]

English wikisource opens in different format than nepali. While opening nepali wikisource, it is redirected from somewhere else. How to turn nepali wikisource into standard subdomain? unsigned comment by Kushal Dev Wiki (talk) 14 November 2021 13:55.

@Kushal Dev Wiki: A language domain can be created if it gathers enoth active contributors. According to this page you need at least 5 active controbutors editing the project each month. Ankry (talk) 02:14, 16 January 2022 (UTC)[reply]

22:06, 15 November 2021 (UTC)

20:02, 22 November 2021 (UTC)

Talk to the Community Tech: The future of the Community Wishlist Survey[edit]

Hello!

We, the team working on the Community Wishlist Survey, would like to invite you to an online meeting with us. It will take place on 30 November (Tuesday), 17:00 UTC on Zoom, and will last an hour. Click here to join.

Agenda

  • Changes to the Community Wishlist Survey 2022. Help us decide.
  • Become a Community Wishlist Survey Ambassador. Help us spread the word about the CWS in your community.
  • Questions and answers

Format

The meeting will not be recorded or streamed. Notes without attribution will be taken and published on Meta-Wiki. The presentation (all points in the agenda except for the questions and answers) will be given in English.

We can answer questions asked in English, French, Polish, Spanish, German, and Italian. If you would like to ask questions in advance, add them on the Community Wishlist Survey talk page or send to sgrabarczuk@wikimedia.org.

Natalia Rodriguez (the Community Tech manager) will be hosting this meeting.

Invitation link

We hope to see you! SGrabarczuk (WMF) (talk) 20:03, 26 November 2021 (UTC)[reply]

21:15, 29 November 2021 (UTC)

21:59, 6 December 2021 (UTC)

22:27, 13 December 2021 (UTC)

Pali using Thai script[edit]

At Thai Wikisource, we found a Pali Tripiṭaka written in Thai script, and according to the policy, we cannot proofread the text there, so I'm wondering if multilingual Wikisource accepts Pali works using Thai script? Here's one of the 45 books of the text. --Bebiezaza (talk) 02:14, 16 December 2021 (UTC)[reply]

And as it is published in Thailand, and the copyright had expired in Thailand, can we use our copyright expired law to proofread the text here? --Bebiezaza (talk) 02:21, 16 December 2021 (UTC)[reply]

@Bebiezaza This sounds like it can be hosted here at Multilingual Wikisource (see also Main_Page/Pāḷi): since they were published in up to 1930, and went in the Thai PD after 1930 + 50 = 1980, it was in the PD in its home country of Thailand in 1996. Therefore, it was not restored by URAA and it's in the public domain also in the US per {{PD-1996}}. Inductiveload (talk) 12:19, 16 December 2021 (UTC)[reply]

Requesting admin help - proofread transclusion[edit]

Transcluding proofread page to mainspace does not move the text out of the way of the page number, see สฺยามรฏฺฐสฺส_เตปิฏกํ/Volume_1/Chapter_1. What should happen is the text moves out of the way for the page number to not stack on top of the text, like as seen in en:The_Return_of_Tarzan/Chapter_2.

I think some other elements might need fixing too, but I have not noticed them yet (except {{nop}}). --Bebiezaza (talk) 14:42, 18 December 2021 (UTC)[reply]

@Zyephyrus, Ankry, Ooswesthoesbes : can you pls have a look at it? thx, -jkb- (talk) 16:04, 18 December 2021 (UTC)[reply]
Probably we need some default CSS settings, but I am not familiar with them; I can only suggest a Mdiv>-based workaround at the moment. Ankry (talk) 16:13, 18 December 2021 (UTC)[reply]
It seems like text highlighting when hovering on page number is also broken --Bebiezaza (talk) 17:40, 18 December 2021 (UTC)[reply]
Unfortunately, I am of no help here :( --Ooswesthoesbes (talk) 07:30, 19 December 2021 (UTC)[reply]
Explicit page numbers like [ ๒ ] in สฺยามรฏฺฐสฺส_เตปิฏกํ/Volume_1/Chapter_1 are explicitly added to the wikitext of the page: pages like Page:สฺยามรฏฺฐสฺส_เตปิฏกํ_-_วินยปิฏเก_มหาวิภฺงคสฺส_ปฐโม_ภาโค.pdf/17. It's why they are not moved to the side because they are considered by ProofreadPage as content.
About text highlighting when hovering on page number, this feature is managed by a custom script/gadget in a lot of Wikisource but nothing has been added to the oldWikisource about it yet. Tpt (talk) 12:57, 24 December 2021 (UTC)[reply]

22:05, 20 December 2021 (UTC)

Upcoming Call for Feedback about the Board of Trustees elections[edit]

You can find this message translated into additional languages on Meta-wiki.

The Board of Trustees is preparing a call for feedback about the upcoming Board Elections, from January 7 - February 10, 2022.

While details will be finalized the week before the call, we have confirmed at least two questions that will be asked during this call for feedback:

  • What is the best way to ensure fair representation of emerging communities among the Board?
  • What involvement should candidates have during the election?

While additional questions may be added, the Movement Strategy and Governance team wants to provide time for community members and affiliates to consider and prepare ideas on the confirmed questions before the call opens. We apologize for not having a complete list of questions at this time. The list of questions should only grow by one or two questions. The intention is to not overwhelm the community with requests, but provide notice and welcome feedback on these important questions.

Do you want to help organize local conversation during this Call?

Contact the Movement Strategy and Governance team on Meta, on Telegram, or via email at msg(_AT_)wikimedia.org.

Reach out if you have any questions or concerns. The Movement Strategy and Governance team will be minimally staffed until January 3. Please excuse any delayed response during this time. We also recognize some community members and affiliates are offline during the December holidays. We apologize if our message has reached you while you are on holiday.

Best,

Movement Strategy and Governance--Civvi (WMF) (talk) 11:00, 27 December 2021 (UTC)[reply]