Wikisource:Scriptorium

From Wikisource
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: Αυτή είναι η κεντρική τοποθεσία για να συζητήσετε θέματα για τη Βικιθήκη, αλλά και το μέρος για να ζητήσετε βοήθεια. Χρησιμοποιήστε τη γλώσσα (ή τις γλώσσες) που γνωρίζετε και μεταφράστε αυτά που θέλετε.
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: זה הדף המיועד לדיונים העוסקים בויקיטקסט, והמקום לפנות לעזרה. השתמשו בשפות שאתם מכירים, ותרגמו את מה שאתם רוצים.
hr: Ovo je središnje mjesto za raspravljanje o temama u svezi s Wikizvorom, kao i mjesto za pitati za pomoć. Rabite jezik(e) koje znate, te prevodite što želite.
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: 이곳은 주로 위키문헌과 관련된 문제들에 관한 논의를 하는 곳이며 도움을 구할 수 있는 곳입니다. 당신이 구사할 수 있는 언어를 사용해서 마음껏 번역해 주시길 바랍니다.
nb: Dette er det sentrale stedet å diskutere saker som angår Wikisource, og stedet for å be om hjelp. Bruk de språka du kan, og oversett det du vil.
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.
pl: To główne miejsce dyskusji o sprawach związanych z Wikiźródłami i miejsce uzyskiwania pomocy. Używaj języków, które znasz i tłumacz co i kiedy chcesz.
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.
ro: Acesta este locul central de discutare a problemelor legate de Wikisursă și locul unde se poate solicita ajutor. Folosiți limbile pe care le stăpâniți, și când doriți, traduceți ceea ce vă place
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.
uk: Це центральне місце для обговорень, пов'язаних з Вікіджерелами в цілому, а також місце, де можна попросити про допомогу. Використовуйте мову, яку ви знаєте і перекладайте те, що вам подобається.
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: 这里是讨论与维基文库有关话题和寻求帮助的页面。使用您所了解的语言留言。您也可以在任何时候把他人的留言翻译成您熟悉的语言。
(edit)


Important project pages: What is Wikisource? • Wikisource and Wikibooks • Votes • Copyright • Possible copyright violations • Proposed deletions • Wikisource:Protection requests • Cataloging • Wikisource and Project Gutenberg

Languages: Language policy • Language domain requests • Language domain requests/Rules for voting • List of Wikisource Languages

Coordination: Statistics • ProofreadPage Statistics • Subdomain coordination • News

Pre-launch discussions

Archives

The whole history is here.


Licensing[edit]

Was trying to import the Template:PD-KG-exempt template from Commons to identify the licensing of our sparse Kyrgyz works..even sure if it should be here or we somehow link to off-wiki licensing templates? Lemuritus (talk) 19:45, 1 January 2020 (UTC)

It would be OK, however, non-US copyright templates are redundant here. Per policy, this project requires that works uploaded here are free in US only. Ankry (talk) 19:50, 1 January 2020 (UTC)
Would it not require a non-US template for the mythical day when the files are moved to their own ky.wikisource subdomain? Perhaps I misunderstand. (unrelated matter, Special:Preferences has two typos, "Preloading next page scan in background. When edining(sic) in the Page: namespace, this gadżet(sic) preloads scan of the next page to speed up its future loading." Lemuritus (talk) 19:55, 1 January 2020 (UTC)

Tech News: 2020-02[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

  • When trying to move a page, if the target title already exists then a warning message is shown. The warning message will now include a link to the target title. [1]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 7 January. It will be on non-Wikipedia wikis and some Wikipedias from 8 January. It will be on all wikis from 9 January (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:18, 6 January 2020 (UTC)

A personal essay from a kindred site[edit]

https://blog.pgdp.net/2020/01/01/ten-eleven-years-at-dp/ —Justin (koavf)❤T☮C☺M☯ 07:28, 13 January 2020 (UTC)

Tech News: 2020-03[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • You can no longer read Wikimedia wikis if your browser use very old TLS. This is because it is a security problem for everyone. It can lead to downgrade attacks. Since 9 December you just see a warning. Soon the browser will not connect to the wikis at all. Most are users on Android systems older than 4.4. You can read the browser recommendations. [2]
  • Special:LinkSearch has been moved from the "Redirecting special pages" section on Special:SpecialPages to the "Lists of pages" section. [3]

Changes later this week

  • Advanced item Wikis can protect pages so that only some users can edit them. The standard protection levels are Allow only autoconfirmed users and Allow only administrators. If your wiki use more protection levels the technical name might be renamed for standardisation. This doesn't affect what users see. [4]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 14 January. It will be on non-Wikipedia wikis and some Wikipedias from 15 January. It will be on all wikis from 16 January (calendar).

Future changes

  • Deepcat and Catgraph will stop working. This will happen at the end of January. This is because you can now use the normal search function instead. [5]
  • You can use <ref follow="…"> to merge footnotes that follow each other. It is meant to be used for digitised books on Wikisource. If the order of the footnotes is wrong no error was shown but the bad <ref> was shown outside the <references /> list. This will change and you will see an error message instead. [6]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery (talk) 18:39, 13 January 2020 (UTC)

Tech News: 2020-04[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 21 January. It will be on non-Wikipedia wikis and some Wikipedias from 22 January. It will be on all wikis from 23 January (calendar).

Future changes

  • There is a new suggestion for what to show when someone edits without registering an account. This is to give unregistered editors better privacy and make some anti-vandalism work go faster. You can give feedback.
  • Advanced item Pywikibot is a Python library to automate work on wikis. It will no longer support Python 2. Use the python2 tag if you need to continue running Python 2 scripts. The Pywikibot team strongly recommends to migrate to Python 3. You can get help to do so. [7]
  • Advanced item The weekly MediaWiki branch cut will soon become automated. The timing for this cut may change. You can discuss in Phabricator if this affects you. [8]
  • Advanced item You can read about coming technical events and mentoring interns.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:41, 20 January 2020 (UTC)

Movement Learning and Leadership Development Project[edit]

Hello

The Wikimedia Foundation’s Community Development team is seeking to learn more about the way volunteers learn and develop into the many different roles that exist in the movement. Our goal is to build a movement informed framework that provides shared clarity and outlines accessible pathways on how to grow and develop skills within the movement. To this end, we are looking to speak with you, our community to learn about your journey as a Wikimedia volunteer. Whether you joined yesterday or have been here from the very start, we want to hear about the many ways volunteers join and contribute to our movement.

To learn more about the project, please visit the Meta page. If you are interested in participating in the project, please complete this simple Google form. Although we may not be able to speak to everyone who expresses interest, we encourage you to complete this short form if you are interested in participating!

-- LMiranda (WMF) (talk) 19:01, 22 January 2020 (UTC)

Wikisource Conference in Warsaw[edit]

Dear Wikisource Community,

Meeting the Wikisource community expectations, we are working with Wikimedia Polska and Wikimedia Foundation on organiziing the 2nd Wikisource Conference in Warsaw. We already had a survey that showed high interest in the Conference within the community. We also had recently a meeting on the conference organization process and its requirements. However, we are still at a very early stage of the Conference organization process. But we are hoping this event will happen in September this year.

In order to apply for Wikimedia Foundation support, we need some input from the community about the Conference goals and the community expectations. If you are a wikisourcian, you wish to participate the conference or you wish to help the Wikisource community that the conference take place, please fill the short survey linked below before January 29 (due to short deadline for grant applications). Please, also share this request among Your communities. Here is the link to the survey

https://docs.google.com/forms/d/e/1FAIpQLSf7FnFgMLPHeyWtBqjgXwLDYvh5vxeTnsZ0OIjTdSDrZlX0PA/viewform

Feel free to contact us, if you have any questions, suggestions, proposals, or if you wish to help us in any other way.

On behalf of the Organizing Commitee,

Nicolas Vigneron

Satdeep Gill

Ankry

Tech News: 2020-05[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • Some mobile diffs have problems. A couple of buttons are not shown. Structured data diffs on Commons are confusing. The developers are working on fixing it. [9][10]
  • Administrators on wikis that use Structured Discussions can't move discussion pages. This is a bug. The developers are working on fixing it. [11]

Changes later this week

  • There is no new MediaWiki version this week.

Future changes

  • There is JavaScript code on Special:Undelete for administrators that makes it possible to automatically select multiple checkboxes by holding the "Shift" key and clicking. This code is also loaded by accident on other special pages and on articles. This makes pages slower to load. This will be fixed. If you know of other special pages where this is useful please tell the developers at phab:T232688.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:52, 27 January 2020 (UTC)

Tech News: 2020-06[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 4 February. It will be on non-Wikipedia wikis and some Wikipedias from 5 February. It will be on all wikis from 6 February (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:04, 3 February 2020 (UTC)

New error messages for the attribute “follow”[edit]

There are new error messages for some edge cases when the follow attribute is used incorrectly.
The follow attribute allows users to merge source material which spans over multiple pages. It only exists on Wikisource and works like this: You can merge the contents of two references into one footnote, e.g. <ref name="a">Text for source 1</ref> […] <ref follow="a">Text for source 2</ref> . In the reference section, this shows the footnote like this: Text for source 1 Text for source 2. More information about this attribute can be found here.

Error message for follow attribute.

For the follow-attribute to work it is important that the name of the reference is defined in the text before the follow attribute is called. Unfortunately, if this is not the case, the follow reference is shown on top of the reference list, with no footnote marker and unattached to the predecessor which it's supposed to follow. In the past, there was no error message for this edge case. This will change soon: In order to align this error behavior with error behavior in the rest of the Cite extension, an error message will be shown (see picture) for this edge case. If you want to find all pages in your wiki using the follow attribute, you can use this query.
This change was done in the context of developing the extends attribute, which caused the WMDE’s Technical Wishes team to rework big parts of the Cite extension. It’s planned to be deployed on February 5.
If you’d like to know more about this change, you can find more detailed information on this Phabricator ticket: T240858. If you have any feedback on this change, please let us know on this central feedback page. - For WMDE’s Technical Wishes Team: Max Klemm (WMDE) (talk) 08:33, 4 February 2020 (UTC)

Update: There will be no new error messages after all.[edit]

Contrary to what was previously announced, the above change will not take place. There is a risk that as a result of the change, error messages would be displayed on many Wikisource pages, even when there is no error. More information can be found on Phabricator (T240858). Many thanks to everyone who pointed this out!
At this time it is not clear if the announced change can be removed from the general software update (scheduled for tonight) or if the Technical Wishes team will remove it promptly afterwards. -- For the Technical Wishes Team: Max Klemm (WMDE) (talk) 10:49, 5 February 2020 (UTC)

Nice to see this info. Ankry (talk) 22:40, 6 February 2020 (UTC)
Max Klemm (WMDE), On the French Wikisource, it works as before. Thank you for the prompt fix. Cantons-de-l'Est (talk)
Thank you Max Klemm (WMDE): this repair was quickly done! --Zyephyrus (talk) 15:22, 9 February 2020 (UTC)

Importing articles from a free online journal[edit]

Hi,

For information, @Eavqwiki: (full disclosure: she is working for WMFR right now) had the idea to import articles from Jornalet, a free online journal in Occitan. See a first test example here: Peró: la primèra tèsi doctorala presentada en lenga shipibo defend lo desvolopament de las femnas indigènas.

I admit it's a bit unusual but I still think it's a great idea. What do you think?

Cheers, VIGNERON (talk) 09:46, 10 February 2020 (UTC)

Love it. I don't see why not. —Justin (koavf)❤T☮C☺M☯ 10:09, 10 February 2020 (UTC)
Great idea, I support. And the fact that the journal is purely online should not be a problem (though some wikisources accepted a strange rule that only work having been printed on paper are allowed in Wikisource — I don't share their opinion). And if such (or similar) a journal existed for those languages on which I work here then I would not only supported the idea but also personally and eagerly participated in importing articles into those Wikisources. Therefore, as I think, the Occitan Wikisource should also benefit from this import, since at least it would expand the amount of works presented in the Wikisource. --Nigmont (talk) 20:47, 10 February 2020 (UTC)
Hi everyone, Thank you @VIGNERON: for the post. Indeed, we are importing articles from the Jornalet to feed the Occitan wikisource with some quality modern content that is usable for young readers and learners amongst others. Doing it automatically will have to wait for a bit unless someone with the technical skills wants to give us a hand in this which we would be very grateful for :) --Eavqwiki 17:42, 17 February 2020 (UTC)

Tech News: 2020-07[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

Problems

  • There was a problem with the new MediaWiki version last week. It deleted some messages by accident. The new version was late because it was stopped to fix things. [13]

Changes later this week

  • Advanced item The MediaWiki action API is used by various tools like bots and gadgets. Some error codes will change. Some parameter values that do not follow the standard will no longer work. [14]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 11 February. It will be on non-Wikipedia wikis and some Wikipedias from 12 February. It will be on all wikis from 13 February (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:09, 10 February 2020 (UTC)

Balinese Wikisource[edit]

There was some discussion on IRC (#wikimedia and #wikimedia-tech [15] [16] [17]) about a possible Balinese Wikisource to host transcriptions of palm leafs, with the person who runs https://palmleaf.org/ . I'm not sure there's a summary yet, but there are some discussions around:

In our discussion on February 11th I've suggested to start by hosting some of their files on Wikimedia Commons and creating some pages on Wikisource.org, to see how they can be formatted and to experiment with any potential issue in MediaWiki. I don't expect any major i18n issue in hosting and showing the content (even adding their existing transliteration to LanguageConverter should not be a big deal). Integrating their workflows may be more challenging, so it's useful for some palmleaf.org contributors to first try and see what we have in terms of extensions, gadgets and tools which may be of use for them as well. Nemo 08:47, 16 February 2020 (UTC)

Lautgesetz, you probably want to add something. However, feel free to start experimenting here on Wikisource.org (the multilingual Wikisource). Nemo 08:58, 16 February 2020 (UTC)
@Nemo bis: Exciting. Would this be an XML-download-to-upload situation where we do it all in bulk and import the pages here? —Justin (koavf)❤T☮C☺M☯ 09:41, 16 February 2020 (UTC)
It could be, but I wouldn't do that immediately: if it's a little more than a hundred pages, it's no problem to copy them here, but to test whether our infrastructure works well enough you don't need all of them from the beginning. I understand that palmleaf.org is not in danger of shutting down tomorrow, they're just thinking how to sustain it longer term.
Thanks for the go-ahead, @Nemo bis:. Experimenting on multilingual Wikisource will let us move everything carefully piece by piece and make sure it's solid. I don't think we'll want to do a bulk export/import because I need to consider the best way to make the content live in Wikisource, which will require some changes or reformatting. I'm going to start with one or two pages and see how it goes. And yes, palmleaf.org will keep going indefinitely until we can figure out how to do this. Lautgesetz (talk) 19:15, 16 February 2020 (UTC)
Tracked in Phabricator
Bug T245357
Tracked in Phabricator
Bug T245359
Tracked in Phabricator
Bug T245360

Anyway, first problem (thanks Aldnonymous for pointing it out): translatewiki:Portal:Ban is formally in Bali script, but in reality it's in Latin. On the Bali Wikipedia both scripts are found, on separate pages connected by a manual link, like w:ban:Kalimantan Barat and w:ban:ᬓᬮᬶᬫᬦ᭄ᬢᬦ᭄​ᬓᭁᬄ (if you can't read the font, it's easy to find it on your software repository: in Fedora it's called google-noto-serif-balinese-fonts ). We probably need to split the locale, so that we have a Bali script locale. Then pages on ban.wiki and here can have their page content language report the actual script they're using, and the language converter would know what to do if installed. Also, palmleaf users would be able to start experimenting with writing in Bali script in our wikis: we may add a new input method, I'm told we're still accepting new ones and it's not too hard. We can then enable it right away on translatewiki.net for translators, then when the community wants it can also come here and on the Bali Wikipedia.

It seems that most users don't have a Bali font installed on their devices, so we'll need to add the Noto font to web fonts. Nemo 09:58, 16 February 2020 (UTC)
In the meantime I've contacted some active BAN speaker and the original script contributors, once the specific on translatewiki is fixed, they will translate it to the script instead into the latin.Aldnonymous (talk) 14:45, 16 February 2020 (UTC)
Noto Balinese is a good start, but the current version is incomplete and cannot render many character combinations needed for palmleaf.org. That's why PanLex has worked with Aditya Bayu Perdana to develop new Balinese fonts. I believe the NC license is an issue for Wikimedia, though? If so I can see if he is willing to change that. PanLex has also created an on-screen keyboard for Balinese (deployed on palmleaf.org currently) and a Keyman keyboard layout. We could try to port the Keyman layout as an input method, but the rules are pretty complex and context-sensitive. I can look into whether it would be possible. By the way, Google has hired Bayu to fix Noto Balinese, so eventually Noto will be fine, but I don't know when the new font will be available. Lautgesetz (talk) 19:15, 16 February 2020 (UTC)

This has now been submitted as a project grant. PanLex would much appreciate any community comments or support. Thanks! Lautgesetz (talk) 23:05, 24 February 2020 (UTC)

@Lautgesetz: Why don't you also create m:Requests for new languages/Wikisource Balinese? --Liuxinyu970226 (talk) 23:51, 10 March 2020 (UTC)

Tech News: 2020-08[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 18 February. It will be on non-Wikipedia wikis and some Wikipedias from 19 February. It will be on all wikis from 20 February (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:16, 17 February 2020 (UTC)

Tech News: 2020-09[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 25 February. It will be on non-Wikipedia wikis and some Wikipedias from 26 February. It will be on all wikis from 27 February (calendar).

Future changes

  • There will be a reply button after each post on a talk page if you want one. This will soon be a beta feature on the Arabic, French, Dutch and Hungarian Wikipedias. You will have to turn it on if you want to use it. It will come to more wikis later. You can test the reply button. It was briefly shown earlier than planned by mistake on the four first wikis last week.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:59, 24 February 2020 (UTC)

Additional interface for edit conflicts on talk pages[edit]

Sorry, for writing this text in English. If you could help to translate it, it would be appreciated.

You might know the new interface for edit conflicts (currently a beta feature). Now, Wikimedia Germany is designing an additional interface to solve edit conflicts on talk pages. This interface is shown to you when you write on a discussion page and another person writes a discussion post in the same line and saves it before you do. With this additional editing conflict interface you can adjust the order of the comments and edit your comment. We are inviting everyone to have a look at the planned feature. Let us know what you think on our central feedback page! -- For the Technical Wishes Team: Max Klemm (WMDE) 14:15, 26 February 2020 (UTC)

Tech News: 2020-10[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • Readers who were not logged in briefly saw the interface in a language decided by their browser. It should normally be in the language of the wiki. This happened for a short period of time last week. This was because of a bug. [20]

Changes later this week

  • If you forget your password you can ask for a new one to be sent to your email address. You need to know your email address or your username. You will now be able to choose that you need to enter both your email address and your username. This will be a preference. This is to get fewer password reset emails someone else asked for. [21]
  • When you asked for a new password you could see if the username didn't exist on Special:PasswordReset. Now the page will show the username you entered and tell you an email has been sent if the username exists. This is for better security. [22]
  • On Special:WhatLinksHere you can see what other pages link to a page. You can see if the link is from a redirect. You can now see which section the redirect links to. [23]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 3 March. It will be on non-Wikipedia wikis and some Wikipedias from 4 March. It will be on all wikis from 5 March (calendar).

Future changes

  • The developers are working on a new interface to solve edit conflicts on talk pages. You can give feedback. [24]
  • There is a vote on the creation of a new user group called abuse filter manager. The vote runs from March 1 to March 31 on Meta.
  • Advanced item wgMFSpecialCaseMainPage was used for the mobile site. It was deprecated in 2017. It will stop working in April. Wikis should see if they use it. If they do they should fix it. You can read more and ask for help. This affects 183 wikis. There is a list. [25]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

00:35, 3 March 2020 (UTC)

Tech News: 2020-11[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • There is a new search word called articletopic. You can use it to search for articles on a specific topic. It is available on the Arabic, Czech, English and Vietnamese Wikipedias. It will come to more Wikipedias soon. [26][27][28]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 10 March. It will be on non-Wikipedia wikis and some Wikipedias from 11 March. It will be on all wikis from 12 March (calendar).

Future changes

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

17:14, 9 March 2020 (UTC)

A bold try: Index:Vocabolardlladinleterar.pdf[edit]

Just to let you know about a running test into Index:Vocabolardlladinleterar.pdf. Both text and formatting come from extraction by pdf file itself (see Index talk:Vocabolardlladinleterar.pdf for a fast and rough hint); the book also uses templatestyles. --Alex brollo (talk) 08:21, 15 March 2020 (UTC)

What in the world am I looking at here? —Justin (koavf)❤T☮C☺M☯ 08:58, 15 March 2020 (UTC)
@Koavf: Please be patient, and consider that tools & tricks, unluckely, are far from being user-friendly by now.... and, being hardly work-specific, perhaps they will never be useful again. Nevertheless I'll publish python code as soon as I will fix a couple of persisting, unexpected bugs. --Alex brollo (talk) 16:32, 15 March 2020 (UTC)
@Alex brollo: I'm patient I just have no clue what this resource is. What is it? —Justin (koavf)❤T☮C☺M☯ 17:41, 15 March 2020 (UTC)
Are you interested about book contents or about extraction tools? About the latter: there are some excellent free command line tools to manipulate pdf contents, they are collected into xpdf utilites; it's relatively easy to use them by a python script. --Alex brollo (talk) 19:34, 15 March 2020 (UTC)
Both actually but I specifically meant the content of the book. Grazie. —Justin (koavf)❤T☮C☺M☯ 19:40, 15 March 2020 (UTC)
OK! The best I can do is to give you a wikipedia link: en:w:Ladin_language and to ping the Italian friend that asked me for some tecnhical help: @Mizardellorsa:. This book is a dictionary of Ladin language. --Alex brollo (talk) 20:17, 15 March 2020 (UTC)
Scusa l'italiano: L'Università di Bolzano ha pubblicato e rilasciato con licenza libera il primo dei volumi di un grande Vocabolario in cui ciascun lemma della lingua ladina dolomitica porta l'inficazione di tutti i passi in cui è contenuta nelle opere della letteratura. Il primo volume riguarda i testi dall'inizio della letteratura fino al 1879. I testi sono già quasi tutti caricati su Wikisource. Alex brollo sta curando sistemi automatici per per estrarre i testi e formattarli.--Mizardellorsa (talk) 20:21, 15 March 2020 (UTC)
@Mizardellorsa: L'italiano ist buono. Grazie! —Justin (koavf)❤T☮C☺M☯ 01:33, 16 March 2020 (UTC)

Tech News: 2020-12[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • Advanced item There is a new API module for changing the content model of existing pages. Use action=changecontentmodel to specify the new model. You can read the documentation on mediawiki.org. [30]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 17 March. It will be on non-Wikipedia wikis and some Wikipedias from 18 March. It will be on all wikis from 19 March (calendar).

Future changes

  • If you edit a page at the same time as someone else you can get an edit conflict. There is a new two-column interface to make it easier to solve this. It will soon be active by default on the German, Arabic, and Farsi Wikipedias. It will be on by default on more wikis within the next months. You will be able to opt out of the new interface. [31][32]
  • You can see a proposed design for replying to comments in an easier way.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:18, 16 March 2020 (UTC)

Tech News: 2020-13[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • Some development will be slower than planned. This is because of the current pandemic. You can see the new deployment guidelines. This is to avoid risks when some persons could be unavailable.
  • There was a problem when adding interwiki links. The tool you use to add interwiki links could suggest the wrong project to link to. This has now been fixed. [33][34]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 24 March. It will be on non-Wikipedia wikis and some Wikipedias from 25 March. It will be on all wikis from 26 March (calendar).

Future changes

  • There is a project to make editing easier for newcomers. The developers are trying to understand what initiatives different Wikipedias have to welcome newcomers. They also want to know which templates are often used for maintenance activities. You can help this project by checking if your wiki's pages are listed on Wikidata.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

17:05, 23 March 2020 (UTC)

Hindi Translation of The Rose And The Ring[edit]

As I proofread The Rose And The Ring, one of the best translators (in their language) I know of happens to be working on a Hindi translation for it.

These as well as any artistic works must have been published in a medium that includes peer review or editorial controls; this excludes self-publication.

  • I can provide scans of their handwritten translation if it would help the proofreading process.
  • The translator is not averse to it being published online under the terms of either CC0, CC-BY, or CC-BY-SA
  • The original is underrated; a Hindi translation of such quality (given this translator's past record) unlikely to come again.

Given these circumstances, what would be the best way for me to help Wikisource and the commons benefit from this translation? -- Contrapunctus-1 (talk) 18:20, 25 March 2020 (UTC)

Tech News: 2020-14[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 31 March. It will be on non-Wikipedia wikis and some Wikipedias from 1 April. It will be on all wikis from 2 April (calendar).

Future changes

  • The video player will change to be simpler and more modern. The current beta feature will become the video player for everyone. The old player will be removed. [36]
  • There is a project to make templates easier to use. The next few weeks the developers will present ideas on the project page. You can watch that page if you are interested in giving feedback. [37]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

17:24, 30 March 2020 (UTC)

Tech News: 2020-15[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • There was a problem with user pages not being shown properly on desktop. This was because of a bug. It will soon be fixed. [38]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 7 April. It will be on non-Wikipedia wikis and some Wikipedias from 8 April. It will be on all wikis from 9 April (calendar).

Future changes

  • MediaWiki will use a newer version of Unicode. Some characters that did not have an upper case equivalent before do now. Titles beginning with one of these characters will be moved. A list of these titles can be seen on Phabricator. The titles will be renamed by the user Maintenance script. This will start on 13 April 2020. You can rename them before this if you wish and the new title can be different from the one the script would rename it to. [39]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:01, 6 April 2020 (UTC)

Tech News: 2020-16[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

Problems

  • There was a problem with the Wikidata database last week. Some wikis went down for twenty minutes. Wikidata and other projects showed error messages. Interwiki links were not shown, some tools did not work and other problems. Some of this was fixed quickly. The developers are working on fixing the rest. [44][45][46]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from April 14. It will be on non-Wikipedia wikis and some Wikipedias from April 15. It will be on all wikis from April 16 (calendar).

Future changes

  • Some graphs have not worked on mobile. This will soon be fixed. [47]
  • The article tab on talk pages of redirects links to the target of the redirect. It could link to the redirect page itself instead. You can leave feedback on this.
  • For pages using syntax highlighting, the use of the deprecated <source> tag, as well as the use of the deprecated enclose parameter, will add tracking categories.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:30, 13 April 2020 (UTC)

Tech News: 2020-17[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Tech News

  • The next issue of Tech News will be sent out on 4 May 2020.

Recent changes

  • Advanced item The small wiki toolkits is to help smaller wikis that need technical skills. They can learn and share technical skills. [48]
  • Advanced item Over-qualified CSS selectors in Wikimedia skins have been removed. div#content is now .mw-body. div.portal is now .portal. div#footer is now #footer. This is so the skins can use HTML5 elements. If your gadgets or user styles used them you will have to update them. [49]

Changes later this week

  • There is no new MediaWiki version this week.

Future changes

  • Some things on the wikis might look weird or not work in Internet Explorer 8 in the future. Internet Explorer 8 was replaced in 2011. [50]
  • The font in the diffs will change. [51]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 28 April next week. It will be on non-Wikipedia wikis and some Wikipedias from 29 April next week. It will be on all wikis from 30 April next week (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:44, 20 April 2020 (UTC)

Copyright permissions[edit]

These past two months I have been working on translating a German excavation report about the House of the Prince of Naples in Pompeii. I requested permission from the original copyright holder, Professor Volker Michael Strocka and received his permission via email. One of the executive directors of Italian Wikipedia has asked if I could upload my translation to WikiSource in epub format. Is the permission email I received from Professor Stroka in which I explained that I wished to make the now out-of-print text freely available on the internet enough documentation? I also have an email from the German Archaeological Institute (the original publisher) saying they have no copyright claim and only the editor (Professor Strocka) now holds any copyright (the work was published in 1984). I have been contributing to Wikipedia and Wikimedia Commons since 2007. Mharrsch (talk) 23:07, 21 April 2020 (UTC)

@Mharrsch: Since files are uploaded at c:, I would refer you there and your the OTRS system. —Justin (koavf)❤T☮C☺M☯ 05:40, 22 April 2020 (UTC)

Template:Langinfo and Meta-Wiki requests[edit]

Should we consider adding a parameter to this template, to let users add a link with Meta-Wiki language requests? --Liuxinyu970226 (talk) 10:54, 23 April 2020 (UTC)

Technical maintenance planned[edit]

(Sorry for using English. Please help translate to your language.)

A maintenance operation will be performed on Thursday 30th April at 05:00 AM UTC.

It impacts all wikis and is supposed to last a few minutes.

During this time, new translations may fail, and Notifications may not be delivered. 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 making your community aware of this maintenance operation.

Trizek (WMF), 18:01, 27 April 2020 (UTC)

Reminder: Technical maintenance planed[edit]

Sorry to use English. Please help translate to your language.

This is a reminder of the message sent on Monday 27th April.

A maintenance operation will be performed on Thursday 30th April at 05:00 AM UTC.

It impacts all wikis and is supposed to last a few minutes.

During this time, new translations may fail, and Notifications may not be delivered. 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 making your community aware of this maintenance operation.

Trizek (WMF) 15:13, 29 April 2020 (UTC)

Tech News: 2020-19[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • Some wikis will be on read-only for a few minutes on 5 May. This will happen around 05:00 UTC. This is for database maintenance. [52]
  • Some wikis will be on read-only for a few minutes on 7 May. This will also affect CentralAuth. This can for example affect global renames, password changes, changing or confirming your email address and logging in to new wikis. This will happen around 05:00 UTC. This is for database maintenance. [53]

Changes later this week

  • You can get a notification when someone links to a page you created. You can soon turn these notifications off for individual pages. [54]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 May. It will be on non-Wikipedia wikis and some Wikipedias from 6 May. It will be on all wikis from 7 May (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:59, 4 May 2020 (UTC)

Tech News: 2020-20[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • Everyone can now import photos from Flickr to Commons with the UploadWizard. Before this only autopatrollers on Commons could import photos from Flickr. [55]

Problems

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 May. It will be on non-Wikipedia wikis and some Wikipedias from 13 May. It will be on all wikis from 14 May (calendar).

Future changes

  • Advanced item JavaScript scripts and gadgets can no longer check multiple keys at once via mw.config.exists() or mw.user.tokens.exists(). You can use exists() or get() to check one at a time instead. [59]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:40, 11 May 2020 (UTC)

Need help to update[edit]

Hi...!

Kindly help us to update Template:ALL TEXTS on Punjabi Wikisource. It's pending for a long time. We need your help to automatically update this page.

Click here for the link at local wiki

- Satpal Dandiwal (talk) 06:31, 13 May 2020 (UTC)

Context for those of us like me who were going to try to emulate en.ws. I, unfortunately, am too ignorant to help. —Justin (koavf)❤T☮C☺M☯ 08:04, 13 May 2020 (UTC)

Tech News: 2020-21[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • If you forget your password you can ask for a new one to be sent to your email address. You need to know your email address or your username. You can choose that you need to enter both your email address and your username. This is a preference. This is to get fewer password reset emails someone else asked for. This is now available on all Wikimedia wikis. [60][61]

Problems

Changes later this week

Future changes

  • Graphs will be rendered in the reader's browser. This will use Javascript. Graphs will hopefully work better for everyone who uses Javascript. It will not work for users who don't use Javascript. This will not affect diagrams in image files. [66]
  • Advanced item Some CSS for the skins has been simplified. This affects div#p-personal, div#p-navigation, div#p-interaction, div#p-tb, div#p-lang, div#p-namespaces, div#p-variants and div#footer. They will have to remove div. You will have to update your gadgets, scripts or user styles. This is so we can use HTML5. [67]
  • Advanced item Some CSS for the Vector skin has been changed. This affects #p-variants, #p-namespaces, #p-personal, #p-views and #p-cactions. They can no longer use > ul. You might need to update your gadgets, scripts or user styles. See how.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

17:18, 18 May 2020 (UTC)

Tech News: 2020-22[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

  • The visual editor will now work in the Modern skin. The changes that needed to happen for this to work could cause problems for some scripts or gadgets. [68]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from May 26. It will be on non-Wikipedia wikis and some Wikipedias from May 27. It will be on all wikis from May 28 (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

14:17, 25 May 2020 (UTC)

Tech News: 2020-23[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • There is a new beta version of the Wikimedia Commons app for Android. It has a new zoom function when you look at images. It can also suggest places when you upload geotagged photos. [69]

Problems

  • There was a problem with the Commons database on 27 May. Commons could not be edited for eight minutes. Because of this problem the database was moved. This caused another short read-only time on 29 May. [70][71][72]
  • The Vector skin had a problem where you couldn't add links to the article in other languages. You couldn't see the section if there were no links to other languages already. It also removed content translation links and links to language settings. This has now been fixed. [73]

Changes later this week

  • You can get a notification when someone links to a page you created. You can turn these notifications off for individual pages. You can soon turn them off also in the notifications you get. [74]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 2 June. It will be on non-Wikipedia wikis and some Wikipedias from 3 June. It will be on all wikis from 4 June (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

22:30, 1 June 2020 (UTC)

Tech News: 2020-24[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • Some articles have tables that can be sorted in different ways. For example a list of countries can be sorted alphabetically but you can click on the size column to sort them by size. If you clicked on the column a second time it would sort the countries from the bottom to the top instead. A third click will now take you back to the original sorting. [75]
  • Self-closed tags now work as in the HTML5 specifications. This means you should stop using some of them. <b/> is an example of a self-closed tag that won't work. area, base, br, col, embed, hr, img, input, keygen, link, meta, param, source, track, wbr can be self-closed. Pages with tags that should not be self-closed have been listed in a tracking category since 2016. They will be listed in Special:LintErrors/self-closed-tag. This doesn't affect <references /> or <ref />. [76]
  • There is a banner called WikidataPageBanner. It is for example used by the Wikivoyages, Wikimedia Russia and the Catalan, Basque, Galician and Turkish Wikipedias. It will now been seen by mobile visitors too. Before this it was only seen on desktop. The wikis should update instructions on MediaWiki:Sitenotice so that editors know to test and style for mobile too. [77][78]

Changes later this week

  • Advanced item You can now edit MassMessage descriptions through the API. This is useful for tools and gadgets. [79]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 9 June. It will be on non-Wikipedia wikis and some Wikipedias from 10 June. It will be on all wikis from 11 June (calendar).

Future changes

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:11, 8 June 2020 (UTC)

Tech News: 2020-25[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • Advanced item Toolforge hosts several tools created by the Wikimedia community like edit counters or enhanced editors. It is changing the domain from tools.wmflabs.org to toolforge.org. The routing scheme is moving from tools.wmflabs.org/toolname to toolname.toolforge.org. You can read the details. Tools that use OAuth will have to be updated to keep working. You can ask for help.

Problems

  • There is a Wikidata item link in the sidebar on many pages. This disappeared for a couple of days for users who have the Monobook skin. This was because of a bug. It has now been fixed. [81]
  • Editing, logging in and logging out didn't work properly for a short period of time last week. It was soon fixed. [82]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 16 June. It will be on non-Wikipedia wikis and some Wikipedias from 17 June. It will be on all wikis from 18 June (calendar).

Future changes

  • Advanced item Pywikibot is a Python library to automate work on wikis. It will not support Python 2 after the new version in July. Support for Python 3.4 and MediaWiki below 1.19 will also be dropped. You should migrate to Python 3. You can ask for help. [83]
  • The selectors .menu and .vectorMenu will no longer work in the Vector skin. This can affect gadgets and user scripts. .menu should be replaced by ul. .vectorMenu should be replaced by .vector-menu. [84]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:37, 15 June 2020 (UTC)

Could an administrator ban this IP address[edit]

Hello everyone,

An IP address uses to modify Walloon pages and this IP address adds useless characters. Unfortunately, I'm not an administrator on this Wiki, so it would be difficult for me to ban it by myself. Here it is.

Sincerely yours,

Èl-Gueuye-Noere (talk) 14:32, 19 June 2020 (UTC)

Yes check.svg Done --Zyephyrus (talk) 15:02, 19 June 2020 (UTC)

Ambiguous copyright status of translation of PD-US-1923-abroad work[edit]

Hi to all! I would like to propose to the community to consider and discuss how to deal with following copyright case. During the course of my work on Moksha-language magazine "Kolkhozon eryaf" (Колхозонь эряф), I found, in the issue 1 of 1936 of that magazine, an article of authorship by Soviet leader Joseph Stalin. The article was originally a speech about Vladimir Lenin spoken by Stalin in 1924 shortly after the Lenin's death, and shortly after that the speech was printed (in Russian) in the form of an an article in the Soviet newspaper "Pravda" ("Truth") in the same 1924 year; and in the 1936 year that article was translated to the Moksha language and printed in the 1936's issue No. 1 of "Kolkhozon eryaf". Original Russian article by Stalin is PD in the US because it was published in 1924 — more than 95 years ago, and the copyright of the work has expired in the US. Several days ago (16.06.2020) I created local Stalin's author's page here: Author:Иосиф Виссарионович Сталин, and also published here that Russian work created by him: О Ленине: Речь на вечере кремлевских курсантов 28 января 1924 г. (Сталин). But the Moksha translation of that work has seemingly ambiguous copyright status. From the first hand, this translation should be copyrighted in the US and would go in PD only in the 1936 + 95 + 1 = 2032 year; from the other hand, it should be in PD in the US already. I asked for help on the English Wikisource, and there I tried to provide verbose explanation what the problem is, so I suppose it would be okay not to repeat the same information here but just to give link to that topic: en:Wikisource:Scriptorium/Help/Archives/2020#Question_on_US_copyrights_regarding_foreign_translated_works_and_URAA (changed the link. — Nigmont (talk) 10:30, 4 July 2020 (UTC)). You may read my explanation there, and also comments done by User:Xover and User:Prosfilaes (great thanks to both of them, expecially to Xover).

And, as it is seen from that discussion, there is no clear answer whether this translation is copyrighted in the US or not, though it seems that, much likely (per convincing arguments provided by Xover), it should be in PD in the US already. Though, Xover and Prosfilaes have not evidences on that case, and I guess, based on silence of others in that topic, other En-WS users have not such evidences too.

Now, I would like to ask for opinions from the community, especially from admins: whether publishing of that Moksha translation is allowed, or might be allowed?

First: may be, anybody of the users here, on the mul-WS, has fully convincing information which doubtlessly proves one of those two options, or real example of treatment of similar case in any US court? If yes, I would greatly appreciate if you share that information here. English Wikisource users seemingly have not such information or example, but may be someone here has such knowledge?

Second: if it occurs that nevertheless nobody knows any proofs regarding the case: then I propose to consider / assume that the work is in PD in US, and to allow me to publish it here, amongst other "Kolkhozon eryaf" articles. Reasons why I ask for that:

1. It is much likely, as seen from that discussion and opinion of Xover, that both copyrights (original's and translation's) should be treated separately and run concurrently, and now both of them are invalid in the US. But, of course, we are not yet sure altogether that it is really so.

2. The second reason is that this particular translation has zero commercial value in the US, so publishing it here does not infringe any commercial interests in US. There is no, I suppose, any persons amongst common US inhabitants, who can read and understand this (Moksha) language, and even if such people really exist in US then they are very few, and it is very doubtful that they would be ready to pay anything for this text. The only people in the US who might be interested in this text are linguist scholars who study Finno-Ugric languages (to which the Moksha language belongs), but those scholars can easily obtain any amount of Finno-Ugric texts without any payment just by contacting to institutions of Finno-Ugric regions of Russia, or to Finno-Ugric countries outside Russia — that is, Hungary, Finland, Estonia. So, for those scholars there is no need to buy this text for money. Also, this text is not suitable for translation to English, because it is much easier to make translation to English from the original Russian work than from a translation made to other language (especially from a translation to this language which is obviously much less known in America in comparison to Russian).

Now, I would be glad to see any opinions from the community on this issue. Regards, Nigmont (talk) 14:24, 20 June 2020 (UTC)

Update. I now change the link to the topic in En-WS Scriptorium/Help provided in my post above above, because that topic has already gone to the archive there. --Nigmont (talk) 10:30, 4 July 2020 (UTC)

I am personally convinced this must be PD per the reasoning I gave on enWS, but I cannot assert this with any certainty. To the best of my understanding this is not a question that can really be conclusively decided absent case law addressing the question directly. But an alternate way of looking at it—given uncertainty regarding its actual copyright status—is risk: what risk of liability would hosting this work impose on our contributors, readers, and re-users? As Nigmont adduces above, there seems exceedingly little commercial potential (probably the most common driver for legal action) for this work in the US and very little risk of getting sued, even iff it should turn out to be still in copyright. That would not be a valid argument for something known or likely to be in copyright, but I think it just might be the sensible approach for this particular case. --Xover (talk) 15:27, 20 June 2020 (UTC)
For such texts, zhwikisource currently allow them following m:United_States_non-acceptance_of_the_rule_of_the_shorter_term#Statement_from_Wikimedia_Foundation (unless if in the Office action cases, then we will temporary grant administrator right to *a T&S member*, and let them delete), not sure if ruwikisource allow them or not. --Liuxinyu970226 (talk) 00:04, 10 July 2020 (UTC)

Tech News: 2020-26[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • There are some new tools to make it easier for newcomers to start editing. They are available on some wikis. These wikis had a problem with the visual editor for a short period of time last week. This was because of a bug in the new tools. It was soon fixed. [85]
  • Advanced item Some user scripts and gadgets stopped working because of a change to CSS selectors. .vectorTabs should be replaced with .vector-menu-tabs to fix this. [86]

Changes later this week

  • The developers are working on a new interface to solve edit conflicts on talk pages. This will be released on 24 June. You can give feedback. [87]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 23 June. It will be on non-Wikipedia wikis and some Wikipedias from 24 June. It will be on all wikis from 25 June (calendar).

Future changes

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:48, 22 June 2020 (UTC)

Something about Wikisource:Subdomain coordination[edit]

In the "Ways to handle United States non-acceptance of the rule of the shorter term" column, there's only one wiki (the zhwikisource) that allow limited tolerance, while several projects still say "Wikilivres", which is unfortunately a dead site. Should there have updates for them?

  • bnwikisource: ?
  • cswikisource: ?
  • dewikisource: ?
  • enwikisource: ?
  • eswikisource: ?
  • frwikisource: ?
  • lawikisource: ?
  • ruwikisource: ?

--Liuxinyu970226 (talk) 11:57, 23 June 2020 (UTC)

Yes, there should but I don't immediately know what those updates would be and the only languages out of that list that I understand are English and Spanish. —Justin (koavf)❤T☮C☺M☯ 01:41, 25 June 2020 (UTC)
As I know, English Wikisource does not tolerate as much as Chinese Wikisource about the United States non-acceptance of the rule of the shorter term, while https://wikilivres.ru still works. Yet Chinese Wikisource users are not convinced to use a Russian site while upset about the death of Wikilivres. "Pre-1925 works still copyrighted in source country allowed" should be better filled in.--Jusjih (talk) 04:33, 21 August 2020 (UTC)

Ginrsig[edit]

Please revert & revdel Special:Contributions/Ginrsig. A lock has been requested at m:srg. Cabayi (talk) 07:24, 28 June 2020 (UTC)

...also Special:Contributions/Dunkintoilet. Cabayi (talk) 08:35, 28 June 2020 (UTC)

Tech News: 2020-27[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • Everyone was logged out. This was because a few users saw the wikis as if they were logged in to someone else's account. The problem should be fixed now. [89]
  • Some readers didn't see new edits to pages. If the page had been recently changed they saw an older version of the page instead. This only affected readers who were logged out. It lasted for ten days. It has been fixed. [90]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 30 June. It will be on non-Wikipedia wikis and some Wikipedias from 1 July. It will be on all wikis from 1 July (calendar).

Future changes

  • Octicons-tools.svg The Modern and Monobook skins use the ID searchGoButton for the go button. This is searchButton for Vector. To have the same ID for all skins it will change to searchButton in Monobook and Modern too. This will affect gadgets and user scripts. It will happen on 23 July. They should be updated to use searchButton. You can read more and see a list of affected scripts.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:30, 29 June 2020 (UTC)

Feedback on movement names[edit]

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

There are a lot of conversations happening about the future of our movement names. We hope that you are part of these discussions and that your community is represented.

Since 16 June, the Foundation Brand Team has been running a survey in 7 languages about 3 naming options. There are also community members sharing concerns about renaming in a Community Open Letter.

Our goal in this call for feedback is to hear from across the community, so we encourage you to participate in the survey, the open letter, or both. The survey will go through 7 July in all timezones. Input from the survey and discussions will be analyzed and published on Meta-Wiki.

Thanks for thinking about the future of the movement, --The Brand Project team, 19:39, 2 July 2020 (UTC)

Note: The survey is conducted via a third-party service, which may subject it to additional terms. For more information on privacy and data-handling, see the survey privacy statement.

Equals sign parser function template conflicts[edit]

See m:Equals sign parser function template conflicts. This wiki is affected by this issue. Alexis Jazz (talk) 15:27, 4 July 2020 (UTC)

@Shruggy, Jimregan: I suggest renaming {{=}} to {{V=}} (v as Volapük) and substitute current use through a bot action. Other proposals? Objections? Ankry (talk) 16:14, 7 July 2020 (UTC)
@Ankry: No objections from me (though I just wanted a regular '=', and didn't want to cause a fuss) -- Jimregan (talk) 19:19, 7 July 2020 (UTC)
Actually... if you do, please skip Page:Jimín Mháire Thaidhg.djvu/123, Jimín Mháire Thaidhg/Gluais, Page:Jimín Mháire Thaidhg.djvu/118, Page:Jimín Mháire Thaidhg.djvu/120, Page:Jimín Mháire Thaidhg.djvu/121, Page:Irisleabhar na Gaedhilge vols 5+6.djvu/129, Page:Catilína - Ua Laoghaire.djvu/79, Page:Catilína - Ua Laoghaire.djvu/80, Page:Catilína - Ua Laoghaire.djvu/98, and Page:Irisleabhar na Gaedhilge vols 5+6.djvu/20, as {{=}} is what was intended there. TIA. -- Jimregan (talk) 19:26, 7 July 2020 (UTC)
@Ankry, Jimregan: I would suggest {{Doh}} as the character is a Double Oblique Hyphen, not an equals sign and not restricted to Volapük. Any apparent connection to Homer Simpson is entirely coincidental. Alexis Jazz (talk) 21:01, 11 July 2020 (UTC)
@Alexis Jazz: I am not sure if an English abbreviation is useful if the template is used basically in Volapük texts. We may create as many redirects as we wish or rename the template in future. Ankry (talk) 07:36, 12 July 2020 (UTC)
@Ankry, Shruggy, Jimregan: well I won't stand in your way. If you want a name that references Volapük, I think {{Tlml}} with a redirect at {{Teilamalül}} would be more appropriate than v=, as it's not a Volapük equals sign. Also just having an actual equals sign in a template name looks confusing. But again, I won't stand stand in your way. Alexis Jazz (talk) 16:35, 13 July 2020 (UTC)
@Ankry, Shruggy, Jimregan: On hiwikisource (the admins didn't respond to pings) I moved it to Teilamalül. (d:Q97143249) Alexis Jazz (talk) 14:32, 17 July 2020 (UTC)
@Ankry, Shruggy, Jimregan: Time is running out. I suggest you move the template. If you don't, I'll move it to {{Teilamalül}} which I believe is better than {{V=}}, but I won't revert if you pick that instead. Alexis Jazz (talk) 16:47, 14 August 2020 (UTC)
I agree with Alexis's suggestion. --Liuxinyu970226 (talk) 10:49, 28 August 2020 (UTC)
Moved to {{Tm}}. @Jimregan: Consider using {{==}} then. Shruggy (talk) 21:59, 16 September 2020 (UTC)

Tech News: 2020-28[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • The Score extension has been disabled for now. This is because of a security issue. It will work again as soon as the security issue has been fixed. [91]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 7 July. It will be on non-Wikipedia wikis and some Wikipedias from 8 July. It will be on all wikis from 9 July (calendar).

Future changes

  • Abstract Wikipedia is a new Wikimedia project. It will collect language-independent information that can be easily read in different languages. It builds on Wikidata. The name is preliminary. You can read more. [92]
  • The iOS Wikipedia app developers are thinking about new experimental tools. If you use an iPhone you can help them by answering the survey.
  • Some rules for user signatures will soon be enforced. Lint errors and invalid HTML will no longer be allowed in user signatures. Nested substitution will not be allowed. A link to your user page, user talk page or user contributions will be required. You can check if your signature works with the new rules. This is because the signatures can cause problems for tools or other text on the page.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:18, 6 July 2020 (UTC)

Announcing a new wiki project! Welcome, Abstract Wikipedia[edit]

Hi all,

It is my honor to introduce Abstract Wikipedia, a new project that has been unanimously approved by the Wikimedia Foundation Board of Trustees. Abstract Wikipedia proposes a new way to generate baseline encyclopedic content in a multilingual fashion, allowing more contributors and more readers to share more knowledge in more languages. It is an approach that aims to make cross-lingual cooperation easier on our projects, increase the sustainability of our movement through expanding access to participation, improve the user experience for readers of all languages, and innovate in free knowledge by connecting some of the strengths of our movement to create something new.

This is our first new project in over seven years. Abstract Wikipedia was submitted as a project proposal by Denny Vrandečić in May 2020 [1] after years of preparation and research, leading to a detailed plan and lively discussions in the Wikimedia communities. We know that the energy and the creativity of the community often runs up against language barriers, and information that is available in one language may not make it to other language Wikipedias. Abstract Wikipedia intends to look and feel like a Wikipedia, but build on the powerful, language-independent conceptual models of Wikidata, with the goal of letting volunteers create and maintain Wikipedia articles across our polyglot Wikimedia world.

The project will allow volunteers to assemble the fundamentals of an article using words and entities from Wikidata. Because Wikidata uses conceptual models that are meant to be universal across languages, it should be possible to use and extend these building blocks of knowledge to create models for articles that also have universal value. Using code, volunteers will be able to translate these abstract “articles” into their own languages. If successful, this could eventually allow everyone to read about any topic in Wikidata in their own language.

As you can imagine, this work will require a lot of software development, and a lot of cooperation among Wikimedians. In order to make this effort possible, Denny will join the Foundation as a staff member in July and lead this initiative. You may know Denny as the creator of Wikidata, a long-time community member, a former staff member at Wikimedia Deutschland, and a former Trustee at the Wikimedia Foundation [2]. We are very excited that Denny will bring his skills and expertise to work on this project alongside the Foundation’s product, technology, and community liaison teams.

It is important to acknowledge that this is an experimental project, and that every Wikipedia community has different needs. This project may offer some communities great advantages. Other communities may engage less. Every language Wikipedia community will be free to choose and moderate whether or how they would use content from this project.

We are excited that this new wiki-project has the possibility to advance knowledge equity through increased access to knowledge. It also invites us to consider and engage with critical questions about how and by whom knowledge is constructed. We look forward to working in cooperation with the communities to think through these important questions.

There is much to do as we begin designing a plan for Abstract Wikipedia in close collaboration with our communities. I encourage you to get involved by going to the project page and joining the new mailing list [3]. We recognize that Abstract Wikipedia is ambitious, but we also recognize its potential. We invite you all to join us on a new, unexplored path.

Yours,

Katherine Maher (Executive Director, Wikimedia Foundation)

  1. ↑ Abstract Wikipedia
  2. ↑ User:Denny
  3. ↑ Abstract Wikipedia mailing list

Sent by m:User:Elitre (WMF) 20:10, 9 July 2020 (UTC) - m:Special:MyLanguage/Abstract Wikipedia/July 2020 announcement

Tech News: 2020-30[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • A temporary fix helped wikis make their main pages more mobile friendly. This was in 2012. It has not been recommended since 2017. The mobile main page special casing stopped working 14 July. 60 wikis now have main pages that don't work well on mobile. You can see which ones, how to fix it and how to get help in Phabricator. This is the same problem that was reported in Tech News 2020/24 and 2020/26.

Problems

  • There is a problem with the interlanguage links. The interlanguage links are the links that help you find a specific page in a different language. The sorting is broken. The developers are working on a solution. [93]
  • Some users keep getting the notifications for the same event. Some of these are old events. [94]
  • Some users have trouble logging in. This is probably a browser cookie problem. The developers are working on understanding the problem. If you have trouble logging in you can see the details on Phabricator. [95]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 21 July. It will be on non-Wikipedia wikis and some Wikipedias from 22 July. It will be on all wikis from 23 July (calendar).

Future changes

  • There is a Printable version link. This will disappear. That is because web browsers today can create a printable version or show how it will look in print anyway. [96]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:13, 20 July 2020 (UTC)

Wikisource Ligurian exists[edit]

See lij:. Thanks to User:MF-Warburg for importing. —Justin (koavf)❤T☮C☺M☯ 23:19, 20 July 2020 (UTC)

Bringing order to how language categories are named[edit]

Currently, the subcategories of Category:Languages are all over the place: some are named after their native name (e.g. Category:Plattdüütsch), others are named after their English name and have a local redirect (e.g. Category:Albanian and Category:Shqip), and still others use another form (e.g. Category:Mìng-dĕ̤ng-ngṳ̄/閩東語). Since some categories cannot have a localized form (Category:Multilingual, Category:Unknown Languages, Category:No linguistic content), I propose renaming all of these to start with ISO codes, followed by local names, and then defaulting to English in parenthesis. E.g. we would now have Category:sq Shqip (Albanian) and Category:mul (Multiple languages). This will help impose a uniform scheme to categorization, make it easier to actually find a language, and make it clear to new users how to name languages that are added. I'm happy to get feedback for the next two weeks. —Justin (koavf)❤T☮C☺M☯ 13:42, 24 July 2020 (UTC)

Additionally, all content pages should be in a subcategory of Category:Languages, even if they are in a subcategory of that. E.g. Category:Language has the subcategory Category:Magazine published in that language: all those pages should also be in Category:Language so that the total page counts on Wikisource:Languages and on the various Main Pages are accurate. I think I'll do a couple of subcategories today just so others can see what I mean and if there's some pushback, I can revert. —Justin (koavf)❤T☮C☺M☯ 20:07, 24 July 2020 (UTC)
Just posting again to make sure others see my edits: I had a pseudobot flag turned on for awhile as I did maintenance work. —Justin (koavf)❤T☮C☺M☯ 23:04, 24 July 2020 (UTC)
I have already done this with Category:Mis (Uncoded languages), Category:Mul (Multiple languages), Category:Und (Undetermined), and Category:Zxx (No linguistic content) for starters. —Justin (koavf)❤T☮C☺M☯ 03:00, 25 July 2020 (UTC)
I encourage everyone to take a look at Wikisource:Languages to see some of the changes that I've made. I have updated the table with some semantics and new category names. It should be pretty clear which ones have been moved. —Justin (koavf)❤T☮C☺M☯ 05:19, 27 July 2020 (UTC)
Strongly Symbol oppose vote.svg Oppose. Proposed names are intricate and uncomfortable (too many letters, brackets etc). Let every language community itself will determine name for their category. At least do not move categories with English names. --Wadorgurt (talk) 09:25, 27 July 2020 (UTC)

Hello, @Koavf:

Regarding your initial proposal: "I propose renaming all of these to start with ISO codes, followed by local names, and then defaulting to English in parenthesis". As of me personally, such renaming does not seem to me something bad, but nevertheless, as I think, it would be better to arrange some voting first — whether active users of local wikisources here support such change in categorizing, or they oppose it. It seems to me that most users have accustomed to the current naming and some of them might reject such change.

But regarding your second statement: "Additionally, all content pages should be in a subcategory of Category:Languages, even if they are in a subcategory of that" — sorry, but I strongly disagree with that. As I understand, the purpose which you mean to achieve with that recategorizing — to get "accurate numbers", as yourselves said: "so that the total page counts on Wikisource:Languages and on the various Main Pages are accurate". Firstly, which page counts you want to obtain this way? Counts of normal content pages only, without proofread pages; or counts of content pages together with proofread pages (that is, together with items in the "Page" namespace)? You should know, that currently some local wikisources include in their categories not only content pages but also proofread pages; but other wikisources do not include proofread pages — only content pages are collected in those ones. So, regardless which kind of numbers you want to gain — you are not able to get precisely any of those by this way: for part of Wikisources you get the first kind of statistics, and for others — the second, but you never get any of them for all wikisources at once. Secondly: such moving may cause troublesome mess in the form of mixture of main pages, subpages and proofread pages, which would occur after proposed actions. For example, let's look on category Category:Мокшень which content is completely created by me. Currently it has well-organized structure, in which each content page is represented in the main category by its "entry point", which may be in a form of: a redirection which leads to its associated content page (for example, Критик-революционер leads to subpage Колхозонь эряф/1936/01/Критик-революционер), or a version page — for different versions of the same work (for example, Ульхть ударник), or a disambiguation page (for example Тунда) — for same-name works which are really different. And if you do as you are intending now, then that your action would cause in that category, at first, a duplication of counts of works (because their entry points will be in the same category as the content pages themselves, and the same work is counted twice), and at second, it would fill the Moksha category with hundreds of various subpages (of Kolkhozon eryaf and Valda yan magazines, as well as chapters of multi-chaptered books) and thousands of proofread pages. And it would be then a total trouble to navigate through such mess of various items, and it would be very hard for a reader to find there something to read. So I urgently ask you not to do such "categorizing" — at least to my categories Category:Мокшень and Category:Эрзянь — the content of them both was created all (or almost all) by me, and I spent a lot of time of efforts to fill them, so I hope my work here will be respected and you would not do such an abuse to the look of those categories. Regarding all other local Wikisources here: though I am not sure of course, but I am inclined to think that your such actions also can make the same trouble to other users as well as it does to me.

And if counts of pages are so urgently needed, that I propose to consider another ways to get them. 1-st option available: to implement a gadget or module (Lua script) which would take given language category and pass through it and get all desired counts; and if different kinds of stats are needed — then it may be implemented by different fuctions of that gadget / script; and in the table with local WS languages, those functions may be invoked and report correct statistics and display them in the cells of the table. 2-nd option: to arrange a bot's algorithm which will do needed calculations of stats, and this bot may be lauched, for example, on daily basis, and it will update counts in the table with actual values. I think, any of these options is much more preferable then forced recategorizing of items in language categories which can annoy, frustrate and irritate users. I think, you should let local Wikisources go as their users want to go, and avoid to impose any forced and violent changes in the inner structure of their categories, as well as to other kinds of formatting accepted on the pages of those Wikisources. --Nigmont (talk) 07:04, 27 July 2020 (UTC)

@Nigmont: Thanks for this thorough response. I don't see any viable means to create any kind of vote, so posting to the Scriptorium seemed like the best way to get others' attention. Do you have a better venue where I could post? —Justin (koavf)❤T☮C☺M☯ 07:08, 27 July 2020 (UTC)
@Koavf: No, I don't mean that you necessarily must do that in other place — the Scriptorium seems to be well suitable for that (though, page Wikisource:Votes does exist — may be, it would be more proper to arrange some voting there?). But the form of your proposal seems to me to be not quite appropriate. Look as you did: your informed about your intentions, but without awaiting any reactions, you already started all those mass changes, notwithstanding that for some users more time may be required to realize your ideas and how they could come in touch with their Wikisources and their work (and notwithstanding that you yourself said that "I'm happy to get feedback for the next two weeks" which for me personally also has a meaning of "I will wait for next two weeks, and if nobody is disagree — I start the changes", but you really started changes without awaiting for those two weeks). Many users might miss your topic at first (not everybody regularly visits the Scriptorium), and many come to Wikisource not on evereyday basis. I think a more correct way to settle an agreement would be:
For first point (renaming the categories): I think you had to create a vote, invite (ping) there main contributors (you may look for example Wikisource:Active tests — there active contributors may be seen), as well as other admins, and put the possible renaming, proposed by you, for voting: Yes or No, or Neutral. Because your proposed renaming is a mass change and it would touch all the Wikisources here, so a more broad approval, I believe, is required here than just create a topic and, on just seeing that in couple days nobody had commented and answered, to start changes without further awaiting. The change is broad and massive, so any haste here is not necessary and even may be harmful (anyway, the wikisources existed in that state for many years and nobody attempted to change that, so the broad changes must be cautious because they may be sensitive).
For the second point (re-categorizing): as I said above, I actively oppose such change, but nevertheless I agree for voting (separately from previous vote, since this is quite a different quiestion) for this point as well: and if majority of users accept your change — then so be it, I'll subdue if such is the consensus. Anyway, such change is also a mass change, and more broad acceptance is required on this point as well. --Nigmont (talk) 07:58, 27 July 2020 (UTC)

Tech News: 2020-31[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • The Starter kit is now available for wiki communities. This page lists technical resources, tools, and recommendations. These are essential to operate a wiki project. This is mostly useful for smaller wikis where the community has limited experience with this. [97]
  • The first features of the Desktop Improvements project are available for logged-in users on all wikis. In order to use them, uncheck Use Legacy Vector in your local or global preferences in section Skin preferences. More improvements are planned. Feedback is welcome.
  • Advanced item On multiple wikis, a UTCLiveClock gadget is available. For wikis that import the gadget directly from mediawiki.org, end users can now choose a different timezone to show instead of UTC.

Problems

  • Advanced item The deployment train for MediaWiki has been blocked this week. [98][99]
  • Translation Notification Bot was sending the same message multiple times to every translator. This has been fixed. [100]
  • Some users were receiving the same notification multiple times. This has been fixed. [101]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from July 28. It will be on non-Wikipedia wikis and some Wikipedias from July 29. It will be on all wikis from JUly 30 (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

13:51, 27 July 2020 (UTC)

Interwikis and Wikidata on authors' pages are broken[edit]

I would like to inform the community that currently interwikis and Wikidata links are broken on authors' pages: even if the Wikidata item exists for an author page and is correctly referenced in the corresponding parameter of the Template:Author, then whatever — in the "Plain sister" pane at the right top corner the message "Search wikidata" is displayed (as if Wikidata had not been normally found), and interwikis on the left are absent. Examples: Author:Максим Горький in the Moksha WS, or else Author:Peadar Ua Laoghaire in the Irish (Gaeilge) WS. I am not sure but maybe this issue is related to recent (27.07.2020) changes of Template:Author done by User:Koavf (see revisions' history). Could anyone try to fix this problem and restore normal displaying of interwikis and Wikidata? --Nigmont (talk) 22:33, 2 August 2020 (UTC)

I don't see how this would cause interwiki links to break. —Justin (koavf)❤T☮C☺M☯ 00:32, 3 August 2020 (UTC)
Still not sure what you're talking about as the sister links appear before and after my most recent revision. —Justin (koavf)❤T☮C☺M☯ 00:35, 3 August 2020 (UTC)
I didn't assuredly assert that the reason is the change in Template:Author made by you — I just did a guess (which might be wrong, of course), a hypothesis. Meanwhile, you also did an edit in template Plain sister: (54 revisions imported from en:Template:Plain_sister: Highly-linked page, important), as I understand, this template is invoked from Template:Author: maybe you forgot to import something which also needed in connection with that template? Though, it is also just a guess, please don't think that I affirm this supposition as an absolute truth. All this topic should be considered just as a proposal to solve the problem, which obviously exists for now. The only thing in which I am sure — that earlier in July interwikis were OK and recently they disappeared for some reason, still unknown. And I just want that somebody would help with that. --Nigmont (talk) 01:10, 3 August 2020 (UTC)
A good guess but reverting that didn't seem to do anything. —Justin (koavf)❤T☮C☺M☯ 02:04, 3 August 2020 (UTC)
Also, Module:Interwiki is working on this page. —Justin (koavf)❤T☮C☺M☯ 02:07, 3 August 2020 (UTC)

Tech News: 2020-32[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • All queries to the Wikidata Query Service failed between 17:50 and 17:59 UTC on Thursday 23 July. Some queries failed during a longer period. [102]
  • Interlanguage links were ordered incorrectly for the past few weeks. This problem was also mentioned in Tech News two weeks ago. The problem is now fixed. [103]
  • There is a problem with the global preferences for the "Use Legacy Vector" option. Developers are working on fixing it. [104]
  • A bug in the Wikibase extension had disabled the "move" and "create" types of protection in the main (Gallery) namespace on Wikimedia Commons. New protections could not be added, and existing protections were not enforced, allowing some page moves and page creations that should not have been possible. This has now been fixed. [105]

Changes later this week

  • The video player will change to be simpler and more modern. This week, the current beta feature will become the video player for everyone on most non-Wikipedia wikis. The old player will be removed. [106]
  • Users' global.js and global.css pages will now also be loaded on the mobile site. You can read documentation for how to avoid applying styles to the mobile skin. [107]
  • Advanced item In the MonoBook skin, the searchGoButton identifier is now searchButton. This may affect CSS and JS gadgets. Migration instructions can be found in T255953. This was previously mentioned in issue 27.
  • Advanced item Bot operators can use Pywikibot to regularly archive discussions. The behavior when the bot uses counter to prevent large archives was changed. [108]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from August 4. It will be on non-Wikipedia wikis and some Wikipedias from August 5. It will be on all wikis from August 6 (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:43, 3 August 2020 (UTC)

Bot request: Palmleaf Bot[edit]

This bot will create Index pages for files from the ongoing batch upload on Commons relating to the active Balinese palm-leaf manuscript project grant. I've created a few of these pages already, which you can see here. Creating index pages in advance simplifies the workflow for Balinese contributors moving from Palmleaf.org and ensures uniformity across the project work. The index page creation will run as a simple python script using the mwclient module and will pause 30 seconds between pages.

Note that it is not possible to fill in most metadata (author, publisher, etc.) because most works are anonymous manuscripts. In some cases additional metadata (e.g. year) may become available once Balinese contributors are able to transcribe the work, but that requires creating the index page first so they can work on it.

--Lautgesetz (talk) 20:37, 3 August 2020 (UTC)

@-jkb-, Ooswesthoesbes, Zyephyrus: ^^^ Ankry (talk) 16:47, 10 August 2020 (UTC)
@Lautgesetz: Could you please create a user page for the bot acount, so we know who is the owner and we can easily contact him in case of a malfunction? --Ooswesthoesbes (talk) 17:28, 10 August 2020 (UTC)
Done. The user page is here. --Lautgesetz (talk) 18:19, 10 August 2020 (UTC)
Indications too on Commons and your bot has been approved there. --Zyephyrus (talk) 19:16, 10 August 2020 (UTC)
Correct. For the user page here I just put the tasks it will be doing on this wiki. --Lautgesetz (talk) 19:22, 10 August 2020 (UTC)
How many edits a day will your bot - appoximately - do? -jkb- (talk) 21:09, 10 August 2020 (UTC)
Right now all it will do is create the index pages (2,854 pages, one every 30 seconds = about 24 hours total). If any batch updates are needed to those pages in the future, then I will run it again for that. It will not run permanently in the background. In the future it will be used to copy existing content from Palmleaf.org into corresponding pages in the Page: namespace. For any given task it will always be a single run. I can modify the pause between edits if necessary. --Lautgesetz (talk) 21:24, 10 August 2020 (UTC)

Yes check.svg Done The waiting period for a week has expired and it looks good. Please make sure any new pages are categorized in a language category or a subcategory of a language category (you have done this already up until now). --Ooswesthoesbes (talk) 15:54, 11 August 2020 (UTC)

Comment: It seems to me that something is wrong with that bot: it is working now, but its edits are currently not marked with "bot" (b) tag, so they are not filtered from "Recent changes" page. As I understand, one of the goals of acquiring the "bot" flag for an account is tagging bot routine edits with bot flag and filter them out from Recent changes. But it has been not done for this bot, and it is not a good thing. @Lautgesetz: could you please set up your bot, in order its edits were tagged with b mark? --Nigmont (talk) 20:46, 19 August 2020 (UTC)

OK, I'll try to fix that. On Commons the instructions suggested I shouldn't use the bot flag for the batch upload, but I can see how the recent edits are different. --Lautgesetz (talk) 22:55, 19 August 2020 (UTC)
I'm having it make all edits with the bot flag now, but not sure if it's working. --Lautgesetz (talk) 23:32, 19 August 2020 (UTC)
This is very remarkable.. As far as I can see, the bot flag is on the account; as such it should be filtered out. Any of the other admins know what's happening here? @Ankry/-jkb-/Zyephyrus. --Ooswesthoesbes (talk) 06:27, 21 August 2020 (UTC)
Unsure which exactly pywikibot script is used and with which parameters. Maybe the bot should logout/login after it got the flag? AFAIR, pywikibot gives a warning when doing edits not marked as bot edits. Or, maybe ask at #wikimedia-tech if still unresolved? Ankry (talk) 07:13, 21 August 2020 (UTC)
Sorry, but problems with bots is not something I can judge :-) -jkb- (talk) 20:03, 21 August 2020 (UTC)

comics[edit]

what is en-ws' policy on transcribing comics, and if it is allowed, any advice on doing so? Arlo Barnes (talk) 05:54, 6 August 2020 (UTC)

apologies, thought I was on en-ws, which I see now has a category:comics. Still, the question stands for those existing in mul's purview; I particular, I have my eye on the many languages of w:en:Pepper&Carrot. Arlo Barnes (talk) 12:05, 6 August 2020 (UTC)
@Arlo Barnes: I think there is no special policy about comics here, so the general ones apply: it has to be PD-US (or CC-BY-SA 3.0 licensed), published, and not suitable for a separate domain Wikisource. Ankry (talk) 16:37, 10 August 2020 (UTC)

Technical Wishes: FileExporter and FileImporter become default features on all Wikis[edit]

The FileExporter and FileImporter will become a default features on all wikis until August 7, 2020. They are planned to help you to move files from your local wiki to Wikimedia Commons easier while keeping all original file information (Description, Source, Date, Author, View History) intact. Additionally, the move is documented in the files view history. How does it work?

Step 1: If you are an auto-confirmed user, you will see a link "Move file to Wikimedia Commons" on the local file page.

Step 2: When you click on this link, the FileImporter checks if the file can in fact be moved to Wikimedia Commons. These checks are performed based on the wiki's configuration file which is created and maintained by each local wiki community.

Step 3: If the file is compatible with Wikimedia Commons, you will be taken to an import page, at which you can update or add information regarding the file, such as the description. You can also add the 'Now Commons' template to the file on the local wiki by clicking the corresponding check box in the import form. Admins can delete the file from the local wiki by enabling the corresponding checkbox. By clicking on the 'Import' button at the end of the page, the file is imported to Wikimedia Commons.

If you want to know more about the FileImporter extension or the Technical Wishes Project, follow the links. --For the Technical Wishes Team:

Max Klemm (WMDE) 09:14, 6 August 2020 (UTC)

Tech News: 2020-33[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • FileImporter and FileExporter became standard features on all Wikis during the first week of August. They help you transfer files from local wikis to Wikimedia Commons with the original file information and history intact. [109]

Problems

  • The mobile skin displays a message at the bottom of the page about who edited last. This message showed raw wikitext. This has now been fixed. Some messages in Structured Discussions and content translation may still appear as raw wikitext. Developers are working on it. [110]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from August 11. It will be on non-Wikipedia wikis and some Wikipedias from August 12. It will be on all wikis from August 13 (calendar).

Future changes

  • All wikis will be read-only for a few minutes on September 1. This is planned between 13:30 and 15:30 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [111][112]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:06, 10 August 2020 (UTC)

Tech News: 2020-34[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • If you revert an edit using the undo link your edit is marked with an undo tag. This will now only happen if you don't change anything in the edit window before publishing the undo. This is to keep users from marking edits as undos when they actually do something else. [113]
  • The new OOUI version will not work with Internet Explorer 8. This means the wikis will look strange and not work well in Internet Explorer 8. This was reported in Tech/News/2020/17. This is because keeping the wikis working with very old browsers creates other problems. [114]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 18 August. It will be on non-Wikipedia wikis and some Wikipedias from 19 August. It will be on all wikis from 20 August (calendar).

Future changes

  • All wikis will be read-only for a few minutes on September 1. This is planned between 13:30 and 15:30 UTC. More information will be published in Tech News and will also be posted on individual wikis next week. This is a reminder. You can help by translating the announcement message. [115][116]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:41, 17 August 2020 (UTC)

Tech News: 2020-35[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 25 August. It will be on non-Wikipedia wikis and some Wikipedias from 26 August. It will be on all wikis from 27 August (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

17:59, 24 August 2020 (UTC)

Important: maintenance operation on September 1st[edit]

Read this message in another language • Please help translate to your language

The Wikimedia Foundation will be testing its secondary data centre. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

They will switch all traffic to the secondary data centre on Tuesday, September 1st 2020.

Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

  • You will not be able to edit for up to an hour on Tuesday, September 1st. The test will start at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 19:30 IST, 07:00 PDT, 23:00 JST, and in New Zealand at 02:00 NZST on Wednesday September 2).
  • If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

  • Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
  • There will be code freezes for the week of September 1st, 2020. Non-essential code deployments will not happen.

This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. Please share this information with your community.

Trizek (WMF) (talk) 13:49, 26 August 2020 (UTC)

Tech News: 2020-36[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • This is a reminder. All wikis will be read-only for a few minutes on September 1. This is planned between 14:00 and 15:00 UTC. Please check on the details on the announcement message. [117][118]

Changes later this week

  • There is no new MediaWiki version this week.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

20:11, 31 August 2020 (UTC)

Tech News: 2020-37[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes later this week

  • Normally pages can be moved to a title that has no existing page yet or to a page that has only one revision, which is a redirect to the page to be moved. A new user right allows editors to move pages over one-revision pages that redirect to anywhere. [119]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 8 September. It will be on non-Wikipedia wikis and some Wikipedias from 9 September. It will be on all wikis from 10 September (calendar).
  • Advanced item All MediaWiki API modules will now use watchlist instead of watch. This was inconsistent before. [120]

Future changes

  • The Wikipedia Android app team might work on patrolling tools in the future. You can let them know what tools would be useful for you or for less experienced patrollers. See the page on mediawiki.org.
  • OTRS will be updated to a new version. This will probably take around two days. OTRS agents will not have access to the system during these days. Emails that come in during the update will be delivered when the update is done. The plan is to start around 08:00 UTC on 14 September. This could change. [121]
  • The Wikipedia Android app will send push notifications if users want them. This could help you see for example when someone wrote on your talk page or your edit was reverted. This will need Google Play Services to work. It will also be possible to get the app without Google Play Services but push notifications will not work. Google Play Services is also used to make the app work for Android 4.4 users. [122][123]
  • Advanced item Wikimedia code review could move to GitLab. It would be hosted on Wikimedia servers. You can take part in the consultation.
  • Advanced item Dropdown menus in the Vector skin use a .menu class. This will not work in the future. Scripts can use nav ul instead. .vectorTabs and .vectorMenu will also not work. Some scripts need to be updated. You can read more in Phabricator.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:59, 7 September 2020 (UTC)

Invitation to participate in the conversation[edit]

Hello. Apologies for cross-posting, and that you may not be reading this message in your native language: translations of the following announcement may be available on Meta. Please help translate to your language. Thank you!

We are excited to share a draft of the Universal Code of Conduct, which the Wikimedia Foundation Board of Trustees called for earlier this year, for your review and feedback. The discussion will be open until October 6, 2020.

The UCoC Drafting Committee wants to learn which parts of the draft would present challenges for you or your work. What is missing from this draft? What do you like, and what could be improved?

Please join the conversation and share this invitation with others who may be interested to join, too.

To reduce language barriers during the process, you are welcomed to translate this message and the Universal Code of Conduct/Draft review. You and your community may choose to provide your opinions/feedback using your local languages.

To learn more about the UCoC project, see the Universal Code of Conduct page, and the FAQ, on Meta.

Thanks in advance for your attention and contributions, The Trust and Safety team at Wikimedia Foundation, 17:55, 10 September 2020 (UTC) 

Tech News: 2020-38[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • The Wikipedia apps briefly showed pages without CSS last week. This meant they looked wrong. It was quickly fixed but cached pages without CSS were shown for a few hours. [124][125]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 15 September. It will be on non-Wikipedia wikis and some Wikipedias from 16 September. It will be on all wikis from 17 September (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:19, 14 September 2020 (UTC)

Retrieved from "https://wikisource.org/w/index.php?title=Wikisource:Scriptorium&oldid=847448"