Wikisource:Scriptorium

From Wikisource
(Redirected from Wikisource:Community portal)
Jump to navigation Jump to search

Welkom · أهلا و سهلا · Xoş gəlmişsiniz · Вiтаем · Добре дошъл · স্বাগতম · Degemer mat · Dobrodošli · Benvinguts · Ⲛⲟϥⲣⲓ · Croeso · Velkommen · Willkommen · Sıma xeyr Amey · Κκαλώς ήρθες · Welcome · Bonvenon · Bienvenidos · Tere tulemast · Ongietorri · خوش آمدید · Tervetuloa · Tervettulemaa · Bienvenue · Wolkom · Fáilte · भळु-औणु · સુસ્વાગત · ברוכים הבאים · स्वागतम · Dobro došli · Isten hozott · Aloha · Բարի գալուստ · Benvenite · Selamat datang · Nno̱ · Bonveno · Velkommin · Benvenuti · ᐊᕆᐅᙵᐃᐹ · ようこそ · fi'i · Sugeng rawuh · კეთილი იყოს შენი მობრძანება · Tikilluarit · 환영합니다 · Salve · Wil sha · Bonveni · Wilkóm · Laipni lūdzam · സ്വാഗതം · स्वागत आ · Merħba · Velkommen · Welkom · Velkommen · Bonvenio · Planvengut · Witajcie · Bem-vindo · Allinmi hamusqaykichik · Bun venit · Добро пожаловать · स्वागतम् · Buresboahtin · ආයුබෝවන් · Vitajte · Dobrodošli · Pyereestpuáttim · Soo dhowow · Mirëserdhët · Добро дошли · Wilujeng sumping · Välkommen · Karibu · స్వాగతం · Хуш омадед · ยินดีต้อนรับ · yI'el · Mabuhay · Hoş geldiniz · Räxim itegez · Maeva · Benvenescu · Гажаса ӧтиськом · خۇش كەپسىز · خوش آمديد · Chào mừng đến · Benokömö · კუჩხი ბედინერი ჸოფედას თქვანი მოზოჯუა · װילקום · Angqcoux · 欢迎 · 歡迎 · (edit)


ar: هذا الموقع الرئيسي لنقاش ويكي مصدر ومكان طلب المساعدة. استخدم اللغات التي تعرف، وترجم ما ترغب.
bn: এটি উইকিসংকলনের বিষয়বস্তু ও সমস্যা নিয়ে আলোচনা করার একটি কেন্দ্রীয় আলোচনার স্থান। প্রয়োজন হলে সাহায্য চাইতে পারেন। আপনি যে ভাষা জানেন তাই ব্যবহার করতে পারেন ও অনুবাদ করতে পারেন।
de: Dies ist eine zentrale Stelle, um alle Themen um Wikisource zu diskutieren, und ein Platz, um nach Hilfe zu fragen. Benutzen Sie die Sprache(n), die Sie beherrschen, und übersetzen Sie, was Ihnen gefällt.
diq: No wikiçıme heta merselan war ardış u mınaqeşe kerdış i heta cay peşti waştışiyo.Zıwanê ke şıma zanê ê zımani dı iştıraq bıkerê u açarnayış seni beno bıumısê.
el: Αυτή είναι η κεντρική τοποθεσία για να συζητήσετε θέματα για τη Βικιθήκη, αλλά και το μέρος για να ζητήσετε βοήθεια. Χρησιμοποιήστε τη γλώσσα (ή τις γλώσσες) που γνωρίζετε και μεταφράστε αυτά που θέλετε.
fa: این مکان مرکزی برای بحث در مورد مسائل درباره ویکی‌نبشته و مکانی برای درخواست کمک است. از زبان (هایی) که می‌شناسید استفاده کنید و آنچه را دوست دارید ترجمه کنید.
en: This is the central location for discussing issues with Wikisource, and the place to ask for help. Use the language(s) you know, and translate what you like.
eo: Ĉi tio estas la centra loko por diskuti problemojn pri Vikifontaro, kaj la loko por serĉi helpon. Uzu la lingvo(j)n kiu(j)n vi konas, kaj traduku kion vi volas.
es: Este es el lugar central para discutir cualquier asunto de Wikisource y es el lugar para pedir ayuda. Use los idiomas que conozca, y traduzca lo que crea necesario que otros sepan.
fr: Ceci est la page principale pour discuter de ce qui a trait à Wikisource, et pour demander de l’aide. Utilisez la (ou les) langue(s) que vous connaissez, et traduisez ce qui vous plaît.
ga: Seo an lárnionad chun téamaí a bhaineann le Vicífhoinse a phlé, agus an áit inar féidir leat cabhair a iarraidh. Bain usáid as teanga ar bith dá bhfuil agat agus aistrigh cibé rud is mian leat.
gbm: इ च मझळु अड्डा विकीसोतु दगड़ मुद्दा बारा म छुंई लगाणु खुणी, अर ठाणु मदद मंगण खुणी. इस्तेमाल कारा उ भाखा ज्व तुमु बिंगुदौ, अर बदलाखरा जू च पसंद​।
he: זה הדף המיועד לדיונים העוסקים בויקיטקסט, והמקום לפנות לעזרה. השתמשו בשפות שאתם מכירים, ותרגמו את מה שאתם רוצים.
hy: Սա Վիքիդարանի հետ կապված հարցերի քննարկման կենտրոնական վայրն է, որտեղ դուք կարող եք նաև դիմել հարցերով։ Օգտագործեք ձեր իմացած լեզուն(երը) և թարգմանե՛ք ի՜նչ կամենում եք։
io: Ita esas la centrala loko por diskutar problemi pri Wikifonto, e la loko por serchar helpo. Uzez la linguo/i quan vu parolas, e tradukar quon/in vu volas.
it: Questo è il luogo principale dove discutere di Wikisource, e il posto dove chiedere aiuto.Scrivi nella lingua che vuoi, puoi anche tradurre quello che vuoi.
ja: ここはプロジェクトについて議論したり、質問がある時に尋ねたりするための場所です。お望みの言語を使って書き込んで下さい。他の人の書き込みを翻訳して下さる方も歓迎です。
ko: 이곳은 위키문헌과 관련한 논의를 하는 주된 곳이자 도움을 구할 수 있는 곳입니다. 구사할 수 있는 언어를 사용하여 다른 내용을 마음껏 번역해 주시길 바랍니다.
nl: Dit is de centrale plek om elk onderwerp in Wikisource te bediscussiëren en de plaats om hulp te vragen. Gebruik de taal die je kent en vertaal wat en wanneer je wilt.
nn: Dette er den sentrale staden å diskutere saker som gjeld Wikisource, og staden for å be om hjelp. Bruk dei språka du kan, og set om det du vil.
pt: Esta é a página principal para discutir tudo o que se relaciona com o Wikisource e também o lugar para procurar ajuda. Faça uso da(s) língua(s) que conhece, e traduza os textos que quiser.
ru: Это центральное место для обсуждений, связанных с Викитекой в целом, а также место, где можно спросить о помощи. Используйте язык, который вы знаете и переводите что и когда вам нравится.
su: Ieu mangrupa loka pikeun nyawalakeun hal-hal ngeunaan Wikisource, sarta tempat pikeun ménta pitulung. Pigunakeun basa nu ku anjeun dipikawanoh, tarjamahkeun nu dipikaresep.
sv: Detta är den huvudsakliga platsen där alla typer av frågor rörande Wikisource diskuteras och där nya frågor kan ställas. Använd de språk som du kan och översätt när och vad du vill av andra.
tl: Ito ang sentrong lokasyon para pag-usupan ang mga isyu kasama ng Wikisource, at ang lugar upang humingi ng tulong. Gamitin ang (mga) wika na alam mo, at isalin ang anong gusto mo.
vi: Đây là trung tâm để thảo luận các vấn đề liên quan đến Wikisource. Bạn sử dụng các ngôn ngữ bạn biết, và dịch những gì bạn thích.
vo: Atos binon top cifik, kö mögos ad bespikön valikosi dö Vükifonät, e kö kanoy i begön yufi. Gebolös pükis, kelis sevol, e tradutolös utosi, kelosi vilol.
yue: 呢度係主要討論維基文庫相關問題嘅版面。你可以用你識得嘅語言留言,亦都可以幫手翻譯其他人嘅留言。
zh-hant: 這裡是討論與維基文庫有關話題和尋求幫助的頁面。使用您所了解的語言留言。您也可以在任何時候把他人的留言翻譯成您熟悉的語言。
zh-hans: 这里是讨论与维基文库有关话题和寻求帮助的页面。使用您所了解的语言留言。您也可以在任何时候把他人的留言翻译成您熟悉的语言。
id:Ini adalah lokasi sentral untuk mendiskusikan berbagai masalah dengan Wikisource, dan tempat untuk meminta bantuan. Gunakan bahasa yang Anda ketahui, dan terjemahkan sesuka Anda.
(edit)


Important project pages: What is Wikisource?Wikisource and WikibooksVotesCopyrightPossible copyright violationsProposed deletionsWikisource:Protection requestsCatalogingWikisource and Project Gutenberg

Languages: Language policyLanguage domain requestsLanguage domain requests/Rules for votingList of Wikisource Languages

Coordination: StatisticsProofreadPage StatisticsSubdomain coordinationNews


Pre-launch discussions


Archives

The whole history is here.



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)[]

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)[]

Line numbering coming soon to all wikis[edit]

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

Tech News: 2021-16[edit]

16:48, 19 April 2021 (UTC)

Suggested Values[edit]

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

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)[]

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)[]

Tech News: 2021-17[edit]

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)[]

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)[]
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)[]

Logo stolen?[edit]

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

Tech News: 2021-18[edit]

15:43, 3 May 2021 (UTC)

Tech News: 2021-19[edit]

15:10, 10 May 2021 (UTC)

Tech News: 2021-20[edit]

13:49, 17 May 2021 (UTC)

Tech News: 2021-21[edit]

17:07, 24 May 2021 (UTC)

Tech News: 2021-22[edit]

17:05, 31 May 2021 (UTC)

Tech News: 2021-23[edit]

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)[]

Tech News: 2021-24[edit]

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)[]

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)[]

Tech News: 2021-25[edit]

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)[]

@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)[]
@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)[]
@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)[]
@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)[]
@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)[]
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)[]
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)[]
@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)[]
@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)[]
@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)[]
@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)[]
@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)[]
@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)[]
Thank you. Jan1nad (talk) 11:23, 30 June 2021 (UTC)[]

Server switch[edit]

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

Tech News: 2021-26[edit]

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)[]

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)[]

Tech News: 2021-27[edit]

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)[]

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)[]
Converting to text can be well done on Wikisource—this is what ProofreadPage is for. —Tacsipacsi (talk) 22:53, 16 July 2021 (UTC)[]

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)[]

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)[]
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)[]
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)[]

Multilingual Wikisource?[edit]

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

@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)[]
Template:PD-US-1923-abroad also explains why separate language Wikisources cannot host some works.--Jusjih (talk) 23:55, 19 July 2021 (UTC)[]
Alright, thanks. Lightbluerain (talk) 06:52, 20 July 2021 (UTC)[]
In addition to the above, there are also some works which are themselves multilingual. —Justin (koavf)TCM 17:55, 24 July 2021 (UTC)[]

Tech News: 2021-29[edit]

15:31, 19 July 2021 (UTC)

Tech News: 2021-30[edit]

21:11, 26 July 2021 (UTC)

אבינו[edit]

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

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

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)[]

Tech News: 2021-31[edit]

20:47, 2 August 2021 (UTC)

Tech News: 2021-32[edit]

16:21, 9 August 2021 (UTC)

Tech News: 2021-33[edit]

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)[]

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
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]

Multi-language support in advanced tools.png
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.

OCR onboarding.png
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)[]

Tech News: 2021-34[edit]

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)

Tech News: 2021-35[edit]

16:01, 30 August 2021 (UTC)

Tech News: 2021-36[edit]

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)[]

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

Read in other languages

Wikimedia-logo black.svg

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)[]

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)[]

  • 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)[]

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)[]

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

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)[]

It is not common here, but we have Hail Mary here for example. -jkb- (talk) 09:39, 10 September 2021 (UTC)[]
Thanks, that is helpful. Bluerasberry (talk) 16:24, 10 September 2021 (UTC)[]
my pleasure :-) -jkb- (talk) 16:34, 10 September 2021 (UTC)[]
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)[]

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)[]

Server switch[edit]

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

Talk to the Community Tech[edit]

Magic Wand Icon 229981 Color Flipped.svg

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)[]

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)[]

I'm afraid you must ask at the vietnamese Wikisource. Cheers, -jkb- (talk) 17:05, 12 September 2021 (UTC)[]

Tech News: 2021-37[edit]

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)[]

@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)[]
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)[]
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)[]

Tech News: 2021-38[edit]

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)[]