Wikisource:Scriptorium - Wikisource

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
Pozdravljeni
Pyereestpuáttim
Soo dhowow
Mirëserdhët
Добро дошли
Wilujeng sumping
Välkommen
Karibu
ꠀꠃꠇ꠆ꠇꠣ
స్వాగతం
Хуш омадед
ยินดีต้อนรับ
yI'el
Mabuhay
kama pona
Hoş geldiniz
Räxim itegez
Maeva
Benvenescu
Гажаса ӧтиськом
خۇش كەپسىز
خوش آمديد
Chào mừng đến
Benokömö
კუჩხი ბედინერი ჸოფედას თქვანი მოზოჯუა
װילקום
Angqcoux
欢迎
歡迎
edit
ar
هذا الموقع الرئيسي لنقاش ويكي مصدر ومكان طلب المساعدة. استخدم اللغات التي تعرف، وترجم ما ترغب.
bn
এটি উইকিসংকলনের বিষয়বস্তু ও সমস্যা নিয়ে আলোচনা করার একটি কেন্দ্রীয় আলোচনার স্থান। প্রয়োজন হলে সাহায্য চাইতে পারেন। আপনি যে ভাষা জানেন তাই ব্যবহার করতে পারেন ও অনুবাদ করতে পারেন।
de
Dies ist eine zentrale Stelle, um alle Themen um Wikisource zu diskutieren, und ein Platz, um nach Hilfe zu fragen. Benutzen Sie die Sprache(n), die Sie beherrschen, und übersetzen Sie, was Ihnen gefällt.
diq
No wikiçıme heta merselan war ardış u mınaqeşe kerdış i heta cay peşti waştışiyo.Zıwanê ke şıma zanê ê zımani dı iştıraq bıkerê u açarnayış seni beno bıumısê.
el
Αυτή είναι η κεντρική τοποθεσία για να συζητήσετε θέματα για τη Βικιθήκη, αλλά και το μέρος για να ζητήσετε βοήθεια. Χρησιμοποιήστε τη γλώσσα (ή τις γλώσσες) που γνωρίζετε και μεταφράστε αυτά που θέλετε.
fa
این مکان مرکزی برای بحث در مورد مسائل درباره ویکی‌نبشته و مکانی برای درخواست کمک است. از زبان (هایی) که می‌شناسید استفاده کنید و آنچه را دوست دارید ترجمه کنید.
en
This is the central location for discussing issues with Wikisource, and the place to ask for help. Use the language(s) you know, and translate what you like.
eo
Ĉi tio estas la centra loko por diskuti problemojn pri Vikifontaro, kaj la loko por serĉi helpon. Uzu la lingvo(j)n kiu(j)n vi konas, kaj traduku kion vi volas.
es
Este es el lugar central para discutir cualquier asunto de Wikisource y es el lugar para pedir ayuda. Use los idiomas que conozca, y traduzca lo que crea necesario que otros sepan.
fr
Ceci est la page principale pour discuter de ce qui a trait à Wikisource, et pour demander de l’aide. Utilisez la (ou les) langue(s) que vous connaissez, et traduisez ce qui vous plaît.
ga
Seo an lárnionad chun téamaí a bhaineann le Vicífhoinse a phlé, agus an áit inar féidir leat cabhair a iarraidh. Bain usáid as teanga ar bith dá bhfuil agat agus aistrigh cibé rud is mian leat.
gbm
इ च मझळु अड्डा विकीसोतु दगड़ मुद्दा बारा म छुंई लगाणु खुणी, अर ठाणु मदद मंगण खुणी. इस्तेमाल कारा उ भाखा ज्व तुमु बिंगुदौ, अर बदलाखरा जू च पसंद​।
he
זה הדף המיועד לדיונים העוסקים בוויקיטקסט, והמקום לפנות לעזרה. כתבו בשפות שתכירו, ותרגמו מה שתרצו.
hy
Սա Վիքիդարանի հետ կապված հարցերի քննարկման կենտրոնական վայրն է, որտեղ դուք կարող եք նաև դիմել հարցերով։ Օգտագործեք ձեր իմացած լեզուն(երը) և թարգմանե՛ք ի՜նչ կամենում եք։
io
Ita esas la centrala loko por diskutar problemi pri Wikifonto, e la loko por serchar helpo. Uzez la linguo/i quan vu parolas, e tradukar quon/in vu volas.
it
Questo è il luogo principale dove discutere di Wikisource, e il posto dove chiedere aiuto.Scrivi nella lingua che vuoi, puoi anche tradurre quello che vuoi.
ja
ここはプロジェクトについて議論したり、質問がある時に尋ねたりするための場所です。お望みの言語を使って書き込んで下さい。他の人の書き込みを翻訳して下さる方も歓迎です。
ko
이곳은 위키문헌과 관련한 논의를 하는 주된 곳이자 도움을 구할 수 있는 곳입니다. 구사할 수 있는 언어를 사용하여 다른 내용을 마음껏 번역해 주시길 바랍니다.
my
ဤနေရာသည် ဝီကီရင်းမြစ်နှင့် ပတ်သက်သော ကိစ္စအဝဝအား ဆွေးနွေးရန်နှင့် အကူအညီများအတွက် မေးမြန်းရန် နေရာဖြစ်သည်။ သင်ကျွမ်းကျင်သော ဘာသာစကားကို အသုံးပြုနိုင်ပြီး သင်အလိုရှိရာကို ဘာသာပြန်နိုင်သည်။
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.
pa
ਇਹ ਵਿਕੀਸਰੋਤ ਨਾਲ ਮੁੱਦਿਆਂ 'ਤੇ ਚਰਚਾ ਕਰਨ ਲਈ ਕੇਂਦਰੀ ਸਥਾਨ ਹੈ, ਅਤੇ ਮਦਦ ਮੰਗਣ ਦੀ ਜਗ੍ਹਾ ਹੈ। ਉਹ ਭਾਸ਼ਾ(ਵਾਂ) ਵਰਤੋ ਜੋ ਤੁਸੀਂ ਜਾਣਦੇ ਹੋ, ਅਤੇ ਆਪਣੀ ਪਸੰਦ ਦਾ ਅਨੁਵਾਦ ਕਰੋ।
pt
Esta é a página principal para discutir tudo o que se relaciona com o Wikisource e também o lugar para procurar ajuda. Faça uso da(s) língua(s) que conhece, e traduza os textos que quiser.
ru
Это центральное место для обсуждений, связанных с Викитекой в целом, а также место, где можно спросить о помощи. Используйте язык, который вы знаете и переводите что и когда вам нравится.
sl
To je osrednje mesto za razpravo o zadevah Wikivira in kraj, kjer lahko zaprosite za pomoč. Uporabljajte jezik(e), ki ga (jih) poznate, in prevedite, kar vam je všeč.
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.
syl
ꠁꠈꠣꠘ ꠃꠁꠇꠤꠒꠣꠇꠞ ꠛꠤꠡꠄꠀꠡꠄ ꠀꠞ ꠖꠄꠖꠞꠛꠣꠞ ꠟꠂꠀ ꠝꠣꠔꠣꠞ ꠄꠉꠥ ꠝꠥꠟ ꠎꠦꠉꠣ ⁕ ꠁꠘꠅ ꠖꠄ ꠖꠞꠇꠣꠞꠦ ꠡꠣꠄ ꠡꠣꠁꠎ꠆ꠎꠅ ꠌꠣꠁꠔꠣ ꠙꠣꠞꠂꠘ ⁕ ꠀꠙꠘꠦ ꠎꠦ ꠜꠣꠡꠣ ꠎꠣꠘꠂꠘ ꠅꠐꠣꠃ ꠛꠦꠛꠀꠞ ꠇꠞ꠆ꠔꠣ ꠙꠣꠞꠂꠘ ꠀꠞ ꠅꠘꠥꠛꠣꠖ ꠇꠞ꠆ꠔꠣ ꠙꠣꠞꠂꠘ ⁕
th
ที่แห่งนี้เป็นศูนย์กลางสำหรับการพูดคุยปัญหาต่าง ๆ เกี่ยวกับวิกิซอร์ซ และเป็นที่สำหรับขอความช่วยเหลือ คุณสามารถใช้ภาษาที่รู้จักและแปลสิ่งที่คุณต้องการ
tl
Ito ang sentrong lokasyon para pag-usupan ang mga isyu kasama ng Wikisource, at ang lugar upang humingi ng tulong. Gamitin ang (mga) wika na alam mo, at isalin ang anong gusto mo.
vi
Đây là trung tâm để thảo luận các vấn đề liên quan đến Wikisource. Bạn sử dụng các ngôn ngữ bạn biết, và dịch những gì bạn thích.
vo
Atos binon top cifik, kö mögos ad bespikön valikosi dö Vükifonät, e kö kanoy i begön yufi. Gebolös pükis, kelis sevol, e tradutolös utosi, kelosi vilol.
yue
呢度係主要討論維基文庫相關問題嘅版面。你可以用你識得嘅語言留言，亦都可以幫手翻譯其他人嘅留言。
zh-hant
這裡是討論與維基文庫有關話題和尋求幫助的頁面。使用您所了解的語言留言。您也可以在任何時候把他人的留言翻譯成您熟悉的語言。
zh-hans
这里是讨论与维基文库有关话题和寻求帮助的页面。使用您所了解的语言留言。您也可以在任何时候把他人的留言翻译成您熟悉的语言。
edit
Dear Wikimedia communities,
We hope you are doing well, and we wish you a happy New Year.
Last year, we captured light. This year, we’ll capture legacy.
In 2025, communities around the world shared the glow of Ramadan nights and the warmth of collective iftars. In 2026,
Wiki Loves Ramadan
is expanding, bringing more stories, more cultures, and deeper global connections across Wikimedia projects.
We invite you to explore the
Wiki Loves Ramadan 2026
Meta page
to learn how you can participate and
your community.
Photo campaign on
Wikimedia Commons
If you have questions about the project, please refer to the FAQs:
Early registration for updates is now open via the
Event page
Stay connected and receive updates:
We look forward to collaborating with you and your community.
The Wiki Loves Ramadan 2026 Organizing Team
19:45, 16 January 2026 (UTC)
Hello,
I am working on setting up Bodo Wikisource (language code: brx) on Wikimedia Incubator.
I would like guidance on ProofreadPage, Index creation, and language approval process.
Bodo is an officially recognized language of India and is written in Devanagari script.
Thank you.
Bkbrahma1
talk
07:37, 21 January 2026 (UTC)
Reply
It is possible to change page language from default to Lingua Franca Nova (
lfn
for
Main Page/Lingua Franca Nova
La Prea a Senior
and
Jura de Hipocrate
? Thanks in advance.
Evelino Ucelo
talk
17:10, 5 February 2026 (UTC)
Reply
There are some interesting freely licensed works about librarianship, archiving, and the like. E.g. this recent paper on
Content Authenticity and Provenance
-- which are often in just one language and not well indexed, but bear preserving and translating. Is there a good WS project or collection for such things? Does it make sense to have a language-neutral wikiproject for collecting this type of knowledge across the field?
Sj
talk
18:52, 11 February 2026 (UTC)
Reply
English:
My initial thought is that it makes the most sense to transcribe the original text on
en:
(or whatever the source language is) and then allow the other languages' projects to pursue their own translations in accordance with their own policies. Perhaps coordination could be done via a multilingual wikiproject, like
Wiksource:WikiProject Translations
or similar. I've just started looking around the multilingual wikisource myself so I'm not sure if we have any more infrastructure than the mere
possibility
of organizing such a thing. --
Mathmitch7
talk
22:43, 2 March 2026 (UTC)
Reply
My thinking is that we could create categories like
Category:eng authors
or
Category:zho authors
for all of the languages represented here on multi-language wikisource with ISO-639 codes. Then, either redirect those pages to their respective language-specific Author categories (when they exist); or use them as their own category which would then be categorized into both the language's category and
Category:Authors by language
. For example,
Category:lv authors
would redirect to the Latvian-language
Category:Autori
, while
Category:tpn authors
would serve as the equivalent Tupi-language category. This would help provide some useful infrastructure to support new languages works and authors in the future.
Thoughts? I'm open to suggestions. Don't want to be overly English-oriented, or create too much administrative burden for new users and language content. --
Mathmitch7
talk
18:26, 3 March 2026 (UTC)
Reply
English:
An additional thought: I think it would be helpful if we created category pages for each ISO 639-1 code, possibly -2 or -3 as well for at least the languages included on multilingual wikisource and on their own subdomains. These would generally redirect to the language categories. For example,
Category:en
would redirect to
Category:English
Category:lv
would redirect to
Category:Ladin
Category:Ru
would redirect to
Category:Русский
. This would just be helpful for quickly categorizing works without having to find the specific "correct" category. Again, let me know what you think.
Mathmitch7
talk
23:34, 3 March 2026 (UTC)
Reply
Update to this, I think I really like the solution tried on
Category:Pt Português (Portuguese)
, a combination of ISO-639, emic/native language name, and language name in English. I would propose that we move all language categories (ie in
Category:Languages
) to this scheme. Recognizing of course that it can be tricky to mix rtl and ltr systems, as well as across different scripts. Even so, this seems a fair and usable solution. For example:
Again, let me know what you think. Obviously changing category names can be a huge pain but I think long-term this is as good a plan as any.
Mathmitch7
talk
18:23, 14 April 2026 (UTC)
Reply
Mathmitch7
: That's indeed a point in which I stumbled and wanted to act upon. I have no opposition to your change. :) Anything that brings a strand of consistency in this mess is welcome.
For the record -- and this is not meant to hinder your action, just putting ideas out there, -- I was thinking of making category names something much more mechanical, like
Category:Works:ru
and
Category:Authors:ru
(or equivalent, as you initially suggested), and then have a gadget that could come by on the client-side and alter the displayed category name depending on the selected language of the user, e.g. if one selects Spanish, those would appear as "Obras (ruso)" and "Autores (ruso)" respectively. This has the advantage of fully implementing the internationalisation ideals of this project, a Spanish speaker should be ideally be able to have the entire project's structural text (i.e. any text that isn't a work transcription) in Spanish. Furthermore, while "native name (english name)" may look perfectly fine for things like Polish, as soon as you get to extinct langauges, or minority languages without a standard orthography, things get problematic. For example, taking from your list, "Ἀρχαία ἑλληνική", does not really mean "Ancient Greek" as ancient Greeks would call it, but rather it's the modern name in ancient spelling (again, it would still be the best option available, so feel free to go with your change), and when it comes to languages like Sumerian, Ugaritic or Ancient Egyptian, what do we put in the native name? In many cases there will be something, but who would that be useful for, except mummies coming back from the dead? This ultimately boils down to an important division that was not well taken into consideration in the Wikisource movement in general: the distinction between
content languages
(the language in which the transcribe works are into) and the
working languages
(in which the UI appears, a site operates and a community communicates). This is also why, in my opinion, splitting Wikisources into subdomains was a particularly near-sighted move, why does should reading a Latin text come at the price of having Latin UI? Why should there be an entirely separated set of infrastructure (modules, templates) just on the criterion of the language the transcribed work transcribing is in? The split, driven by technical limitations that we had at the time which can easily be fixed in other ways now (like right-to-left text, which prompted the first subdomain, Hebrew Wikisource, which had this catastrophic domino effect) is showing its failure in almost every aspect, both moral and technical, and those paying the price are the minority languages, whose editors are forced to work in this graveyard of incoherent and unmaintained infrastructure, with the hope of getting their own subdomain, only to be then further alienated from the rest of the community once achieved, helpless to infrastructural bugs and vandalism.
Enough rambling, back to the issue at hand, the proposed gadget idea. Making one is not something impossible, as we have something similar in English Wiktionary,
wikt:en:MediaWiki:Gadget-categoryTreeLanguageNames.js
, by the excellent coder @
Surjection
, where for example if you are on
wikt:en:Category:Cats
, the subcategory
Category:ru:Cats
will display as "Category:ru:Cats
[Russian]
". A while ago, I tried implementing a similar thing here, but I remember running in a number of technical difficulties. A difference in implementation was that on enwikt the scope is much more limited -- the only needed display language is English, -- and since that project employs some non-ISO language codes, the most sensible idea was to have a project-specific JSON to house all the code-to-language correspondences,
wikt:en:Module:languages/code to canonical name.json
, meanwhile here we need to have the name for every language in every language, with all the fallback rules, which is why we are better off relying on the central Wikimedia database that contains all of that. I cannot remember what ultimately stopped me from finishing this gadget, I think the implementation was getting too hacky.
TLDR
: There are some ultimate issues that you will encounter trying to implement this for every language, but anything would be better than what we have now, so feel free to do it. :)
Catonif
talk
13:44, 15 April 2026 (UTC)
Reply
All these points are well-met (Maybe someday we can re-unite the wikisources :') ). I think that ultimately organizing the kind of gadget you describe is a good plan, and my proposal is an adequate in-between step. I'd maybe like to hear at least one other editor's thoughts on the matter before going ahead with that big of a change, though.
Maybe analogous categories would be
Category:En English Authors
and
Category:Co Autori in corsu (Corsican authors)
. I don't know, nothing is perfect.
Do you happen to know if there's a good way to change a category's name other than just moving its page, finding everything that links there, and changing them individually? Do other wikis just use bots?
Mathmitch7
talk
18:50, 15 April 2026 (UTC)
Reply
You are thinking about
commons:Help:Gadget-Cat-a-lot
Ignacio Rodríguez
talk
03:48, 16 April 2026 (UTC)
Reply
Pecha-pema
Abhignkr47
Saaifa
Mathmitch7
: and anyone interested. Greetings, pleasure to meet you and sorry to disturb. Apologies for writing in English. You appear to be the most active on Multilingual Wikisource of the latest days. I'm sorry for whoever interested I did not alert, I did not want to send out too many unwanted pings.
In short, I have written a gadget that can render
TEI XML
-format texts as HTML. (You can turn it on in your preferences and check how it handles
TEI:Fare i ri ëvetar shqip
. A brief explanation is at
Wikisource:TEI Gadget
.) It is a format used for a more scholarly kind of transcription, mainly used for palaeography, manuscripts or thorough critical digital editions. This is not meant as a replacement of the current situation but a way to better digitalise the cases which are not well-handled by Wikitext.
For technical reasons, mostly about security, the solution requires a new namespace (i.e. the thing that comes the colon in a page title, like
Page:
or
Talk:
), so I have to file a technical request for the namespace
TEI:
. As regrettably scatterful as this project is, I assume that such a change would not be carried through without an attempt at a discussion with other editors. For this reason, I ask here whether any of you would oppose such a change.
Thank you for your love of writing, and the work you do to record it. :)
Catonif
talk
16:23, 13 March 2026 (UTC)
Reply
English:
Personally I'm fine with having a TEI: namespace or something similar. Support for this kind of document format would be very helpful and putting TEI documents into their own namespace seems like a good way to integrate it with our existing workflow, using a TEI: page as a source and then transcluding it to a normal "work" namespace using a template/Lua module.
However, I would like to see us think about how we could use TEI or TEI markup alongside the existing Page transcription and transclusion workflow. I think one of the best things about Wikisource is that pages in the mainspace are generally linked back to their source scan in an easily verifiable, traceable, and auditable way. Although TEI is great for transcriptions, I don’t yet see an analogue for that particular type of "backing" to a scan. The example document you link has source information, but some work would need to be done to get to something as granular as what we already have for scan verification and to support proofreading efforts.
That all being said, if the gadget works and TEI-XML is as robust as it appears to be, I’m fine with doing what must be done to implement support for it. If that includes a special namespace, at least here on multilingual ws, I
support
. Cheers! --
Mathmitch7
talk
19:45, 13 March 2026 (UTC)
Reply
Hello, thanks for your thoughts and your support! :) I agree that scan-backed transcription is the strongest point of boast for Wikisource. The thing is that the transformers are very versatile, which isn't well visible by the example I gave, which only shows two almost-identical transformer schemes, with the only difference being script (if it can help get the idea, the green-boxed header is also generated by a transformer of the same structure.) With this in mind, my thought was to have "Original scan" as one of the selectable transformers (i.e. a column), which is fairly easily doable, just requires for the transformer to ignore all tags, except for

("page break"), which would show the images.
I was going to implement this, I didn't because there is an unrelated
ongoing bug
which makes the pages of DJVU files not display. See for example
Page:Veqilharxhi - Ëvetar (1845).djvu/1
(the same work already in wikitext). The page image used to work a while ago. So for now it would have looked like a bunch of error messages in mainspace. But it's definitely doable once the bug is fixed. :)
This to me is also a way to make the scans more immediately accessible to the reader. I find them to be very valuable, especially in cases of manuscripts and other kind of texts in which TEI in particular shines, and having scans into a separate namespace always felt a bit like hiding them to me. The idea of having them user-toggleable seemed quite neat.
Admittedly, it is true that it will never be as easy. TEI is inevitable much more cumbersome, difficult to learn and master, and in many cases harder to read from the source. The main workspace of editors using will most likely never be the Wikisource editor box, but rather VS Code with the "Scholarly XML" extension (AFAIK, most accessible widely used TEI environment), or similar software. For these reason, I emphasise that that TEI is meant for those who particularly have a lot of time and dedication at their disposal, and are willing to go through the hardships that are required to get something of academic quality. The vast majority of texts will be kept in wikitext.
Catonif
talk
20:32, 13 March 2026 (UTC)
Reply
What are the security concerns of having such a namespace enabled and how would you deal with them? Recently there was a mass deletion of random articles in multiple wikis because of a personal JS script gone rogue. PS: (I am well in favor of offering the wide community a sufficiently good for them standard for transcribing. Also I guess there is plenty of text already transcribed this way we could incorporate.)
Ignacio Rodríguez
talk
11:36, 1 April 2026 (UTC)
Reply
Ignacio Rodríguez
: Sorry for the late reply, I didn't see your message, and thank you for your support. Since my post here I have come to a solution, which is to handle the TEI-to-HTML transformation within Lua, and let the gadget only handle the columns display. This has a number of disadvantages: JavaScript is much better at handling XML (it was infact built for that purpose), now a separate
Lua XML parser
is required and we are likely to hit Lua's memory limit with files too large, while a pure JS implementation was much easier to maintain and had no limitations. However we cannot let just any editor write JavaScript that runs on other people's browsers, as the event you mention exemplifies, so the script pages would have needed to be protected under some specific right. But being able to edit and write these scripts is such a central thing for my intended versatile implementation of TEI that I would rather hit the memory limit rather than only allowing very few people to benefit from the infrastructure. As such, the security justification should be gone once I fully implement the Lua solution, and the namespace will be requested only for conceptual reasons.
Catonif
talk
20:24, 12 April 2026 (UTC)
Reply
Catonif
maybe it would be better in the long run to build a TEI MediaWiki extension. The gadget is fine by now, but memory limits are concerning. I am no coder but I can cheer you up. For the record I support the creation of the TEI Namespace.
Ignacio Rodríguez
talk
22:44, 12 April 2026 (UTC)
Reply
Ignacio Rodríguez
: Absolutely agreed. There exist, in fact,
mw:Extension:TEI
and
mw:Extension:CETEIcean
, which I tried testing around, on my own installing of MediaWiki. These are not very well documented projects and it was quite difficult to untangle something out of the code, but to me these seem overly complicated systems with a much more limited outcome, lacking the versatility that TEI was built with in mind, hence not very fit for a project like Wikisource. Furthermore, Extension:TEI, from a quick glance, does not appear to be fully TEI-compliant, allowing for questionable tag names (see
here
), as

instead of

, while CETEIcean is not HTML-compliant, as you can see from your inspector on
this example
, with tag names like

in the HTML fed straight to the browser. I had even tried making my own extension, only to realise that it is much beyond my capabilities, and eventually settled for an awkward Lua implementation. Then I got the idea of a much cleaner JavaScript system, only to come back to Lua in the end for the reasons described. My hope is that my implementation is merely a proof of concept for someone more knowledgeable to notice and make better.
Catonif
talk
22:42, 13 April 2026 (UTC)
Reply
I see. I was hoping it was within your capabilities. You seem to be very skilled as both those implementations are neat. Maybe you should import some more works in that format, so we grow the need and visibility of the project. If I ever stumble upon some interesting TEI-proofread Spanish works, I might give this a try
Ignacio Rodríguez
talk
12:50, 14 April 2026 (UTC)
Reply
When trying to edit
toki soweli tan jan Beatrix Potter
, all of the page images are broken. (Example:
Page 938
, obtained from the "Image" tab at the top of
Page:Toki soweli tan jan Beatrix Potter.pdf/938
It looks like this is because the images are using 872px as the thumbnail size. Setting the size of the thumbnail manually in the URL to 960px (or any of the other sizes listed
here
) fixes the issue (
fixed URL for page 938
).
Is there a way for the default thumbnail size be changed to something other than 872px so the images show up properly in the editor?
Thanks in advance.
Tymewalk
talk
03:47, 19 March 2026 (UTC)
Reply
English:
This strikes me as a weird quirk or possible bug in ProofreadPage. I can confirm that I get the same kind of broken page image, using Firefox 148.0.2 for Windows, and the Monobook skin. I’ll see if I can force a fix by just purging some pages here and on commons, as sometimes that fixes issues with PDFHandler. Otherwise, we can try posting over to
mw:Project:Village Pump
and see if anybody knows if it’s related to a known and tracked issue, or if it needs a new issue reported. --
Mathmitch7
talk
18:23, 23 March 2026 (UTC)
Reply
I think we should:
Move it to
Wikisource:Main Page
and
Include some text introducing that this is a stand-alone wiki, not just a portal. I think we should explain that this wiki hosts:
Multilingual works
Works in a language with too small a corpus
Works that are incubating to a subdomain
Works that are made up of non-linguistic content
Works with languages that have subdomains but that won't accept a particular work for whatever reason
Thoughts on these changes? —
Justin (
ko
vf
06:20, 25 March 2026 (UTC)
Reply
English:
I think about this a lot, and I don’t have a great answer. Honestly, my ideal would be to split multi-lingual WS into mul.wikisource.org, and organize it as its own project, and make this main wikisource.org
just
a portal to those other sites, similar to how Wikipedia works (and by default redirecting all traffic to specific pages to the page on mul.ws). I think that would be clearer to people, including editors. However, that’s a pretty big change, and I wouldn’t move forward with it without substantial discussion both here and at individual language subdomains.
In the meantime, I think your proposal’s points are reasonable. I don’t see a particular reason to move the main page to
Wikisource:Main Page
, but everything else seems fine. I would also add that the main page should specifically say "Welcome to Multilingual Wikisource." --
Mathmitch7
talk
13:01, 30 March 2026 (UTC)
Reply
I agree with Mathmitch7. Moving to mul.wikisource.org seems like a good idea. Like Wikidata and Wikispecies, we should have a centralized and organized Main Page for each language using Extension:Translate --
Namoroka
talk
09:27, 4 April 2026 (UTC)
Reply
I support revising our Main Page. Yet to split multi-lingual WS into mul.wikisource.org sounds excessive for now.--
TunnelESON
talk
03:56, 6 April 2026 (UTC)
Reply
That's fair enough. Even so, multilingual WS has over 61,000 pages in the main namespace, about double the size of
Portuguese Wikisource
. Just saying that splitting it off may be a good idea. But again, it's a bigger discussion. --
Mathmitch7
talk
18:18, 6 April 2026 (UTC)
Reply
Here’s some proposed wording in English. Let me know if that seems adequate:
Welcome to Wikisource
, the free library that anyone can improve.
This is
Multilingual Wikisource
, a site for works in all languages, and for connecting different language-specific Wikisource projects. Works on this site include:
--
Mathmitch7
talk
19:39, 6 April 2026 (UTC)
Reply
That's a nice shot and it finally makes clear on the homepage what this site is. —
Justin (
ko
vf
02:33, 7 April 2026 (UTC)
Reply
Hello! There will be a
Wikimedia Café
meetup on
Saturday, 11 April 2026 at 14:00 UTC
timestamp conversion tool
), focusing on the
the 2026-2027 Wikimedia Foundation Annual Plan
. The featured guests will be
Kelsi Stine-Rowe
(senior manager,
Movement Communications
, Wikimedia Foundation), and
Sam Walton
(senior product manager,
Moderator Tools
, Wikimedia Foundation).
In addition to this Café session,
several additional meetings regarding the Annual Plan are listed on the Collaboration page
, and you may participate on the
talk page
This Café meetup will be approximately two hours long. Attendees may choose to attend only for a part. Please see the Café page for more information, including
how to register
Pine
talk
05:18, 29 March 2026 (UTC)
Reply
Hello everyone,
This is a notice regarding an ongoing data migration on Wikidata that may affect your election-related templates and Lua modules (such as
Module:Itemgroup/list
).
The Change:
Currently, many templates pull electoral maps from Wikidata using the property
P1846
, combined with the qualifier
P180
Q19571328
We are migrating this data (across roughly 4,000 items) to a newly created, dedicated property:
P14226
What You Need To Do:
To ensure your templates and infoboxes do not break or lose their maps, please update your local code to fetch data from
P14226
instead of the old
P1846
P180
structure. A
list of pages
was generated using Wikimedia Global Search.
Deadline:
We are temporarily retaining the old data on
P1846
to allow for a smooth transition. However, to complete the data cleanup on Wikidata, the old
P1846
statements will be removed after
May 1, 2026
. Please update your modules and templates before this date to prevent any disruption to your wiki's election articles.
Let us know if you have any questions or need assistance with the query logic. Thank you for your help!
ZI Jony
using
MediaWiki message delivery
talk
17:11, 3 April 2026 (UTC)
Reply
Hi all, as far as I can tell, multilingual Wikisource is not affected by this change at all. Let me know if you think otherwise. --
Mathmitch7
talk
17:45, 6 April 2026 (UTC)
Reply
Latest
tech news
from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.
Translations
are available.
Updates for editors
The
CampaignEvents extension
now includes a new group goal-setting feature, enabling organizers to set and track event goals such as the number of articles created and participating contributors in real time. Similarly, participants can work toward shared targets and see their collective impact as the event unfolds. The feature is now available on all Wikimedia wikis. Learn more in
the documentation
The new
watchlist labels
feature (announced in
Tech News 2026-07
) is now available via VisualEditor, the source editor, and the 'watchstar' (or watch link, for skins that don't have a star icon). Previously it was only possible to assign labels via
EditWatchlist
. In all three places it is a new field following the expiry field.
View all 23 community-submitted tasks that were
resolved last week
. For example, the issue where talk pages on mobile with Parsoid are unusable after empty section headers, has now been fixed.
[1]
Updates for technical contributors
The
sub-referencing feature
, which lets editors add details to an existing reference without duplicating it, will be gradually rolled out to
more wikis
later this year. Wikis using the
Reference Tooltips
gadget are encouraged to update their version (typically at
MediaWiki:Gadget-ReferenceTooltips.js
as shown
here
) to ensure compatibility. Other reference-related gadgets may also be affected.
[2]
All Wikinews editions will be closed and switched to read-only mode on 4 May 2026. Content will remain accessible, but no new edits or articles can be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions.
The
Action API
has had several formats for requested output. One of them,
format=php
, is being removed soon. Please ensure your scripts or bots use the
JSON format
. This removal should affect very few scripts and bots.
[3]
The
Special:NamespaceInfo
page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia.
[4]
Detailed code updates later this week:
MediaWiki
Tech news
prepared by
Tech News writers
and posted by
bot
Contribute
Translate
Get help
Give feedback
Subscribe or unsubscribe
MediaWiki message delivery
16:19, 6 April 2026 (UTC)
Reply
Appologies for posting in English. Also, I could not locate a dedicated page for bot request in English Wikisource, so I am posting here. Please direct me to the correct page if one exists. Thank you.
Bot name
User:SchlurcherBot
Bot operator
commons:User:Schlurcher
Bot task
: Automatically convert links from
to
(secure protocol migration)
Technical details
: Please see
meta:User:SchlurcherBot
for full details, including the expected number of affected URLs on English Wikisource.
Bot flags on other projects
Global bot status granted
. Also flagged on
English Wikipedia
German Wikipedia
French Wikipedia
Italian Wikipedia
Polish Wikipedia
Portuguese Wikipedia
, and
Commons
. For a full list, see:
sulutil:SchlurcherBot
Comment
: The bot is globally approved and active on the top 10 Wikipedia projects. As this wiki has opted out of the global bot policy, I am requesting permission to perform these link updates on English Wikisource as well. Please let me know if a local bot flag can be granted or if you have any questions. Thank you. --
Schlurcher
talk
07:59, 7 April 2026 (UTC)
Reply
Hi, you can submit this request over to
the en.wikisource Scriptorium
under the "Bot Requests" section, and it will get more targeted en.ws attention. If you'd also like to submit your request to Multilingual Wikisource (this site), let us know. --
Mathmitch7
talk
12:47, 7 April 2026 (UTC)
Reply
Mathmitch7
: This request was made for the project
sourceswiki
so the multilingual wikisource (this site). I also plan to request each individual language like
enwikisource
dewikisource
eventually as well. Hope this helps. --
Schlurcher
talk
08:11, 8 April 2026 (UTC)
Reply
My apologies, I misunderstood! I
support
approving this bot.
Mathmitch7
talk
12:26, 8 April 2026 (UTC)
Reply
-jkb-
, @
Koavf
, @
Ooswesthoesbes
, @
TunnelESON
. Please let me know if Bot status can be granted. --
Schlurcher
talk
06:52, 17 April 2026 (UTC)
Reply
User:Schlurcher
: Looks goed, so granted. --
Ooswesthoesbes
talk
08:07, 17 April 2026 (UTC)
Reply
Latest
tech news
from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.
Translations
are available.
Weekly highlight
Experienced editors are invited to
test
the
Article guidance
feature, designed to help less-experienced editors create well-structured, policy-compliant Wikipedia articles. Testing instructions are
available
. Also, after reviewing
the outlines
, please provide feedback on the
project talk page
. Based on your input, the feature will be refined and transferred to the pilot Wikipedias to translate and adapt. Check out
the video
explaining the feature.
Updates for editors
On most wikis, all autoconfirmed users can now use
Special:ChangeContentModel
page to
create new pages with custom content models
, such as mass message lists, making custom page formats more accessible. Check
Special:ListGroupRights
for the status of your wiki.
[5]
The Growth team has launched an
account creation experiment
to evaluate whether adding an account creation button to the mobile web header increases new account registrations and encourages more mobile users to contribute to the wikis. The experiment is currently live on Hindi, Indonesian, Bengali, Thai, and Hebrew Wikipedia, and targets 10% of logged-out mobile web users.
View all 30 community-submitted tasks that were
resolved last week
. For example, an issue where VisualEditor could get stuck loading on Windows devices with animations turned off, has now been fixed.
[6]
Updates for technical contributors
Starting later this week, Abuse filter editors who have the
Improved Syntax Highlighting
beta feature enabled will have
CodeMirror
instead of
CodeEditor
as the editor at
Special:AbuseFilter
. This is part of the broader effort to make the user experience more consistent across all editors.
[7]
[8]
Tools and bots that access the
Notifications API
action=query&meta=notifications
) will need to update their OAuth or BotPassword grants to also include access to private notifications.
[9]
Due to a library upgrade, listings on category pages may be displayed out of order starting on Monday, 20th April. A migration script will be run to correct this, and will take hours to days depending on the size of the wiki (up to a week for English Wikipedia).
[10]
Detailed code updates later this week:
MediaWiki
Tech news
prepared by
Tech News writers
and posted by
bot
Contribute
Translate
Get help
Give feedback
Subscribe or unsubscribe
MediaWiki message delivery
15:19, 13 April 2026 (UTC)
Reply
Latest
tech news
from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.
Translations
are available.
Weekly highlight
After two years of development,
Improved Syntax Highlighting
, also known as
CodeMirror 6
, is to be promoted out of beta on Tuesday, April 21. It brings better code and wikitext readability, reduction in typing errors, and other
benefits
to all users of the standard syntax highlighter. A huge thank you to volunteer
Bhsd
who developed many of the new features, including
code folding
autocompletion
, and
linting
[11]
A major update to the Wikipedia app for iOS is now rolling out, redesigning the interface to align with Apple's latest "Liquid Glass" visual design.
Download the latest version
and explore the update.
Updates for editors
Reading lists
is a feature which allows readers to save articles to a list for reading later. This feature is now in beta on Arabic, French, Indonesian, Vietnamese, and Chinese Wikipedias and by default for all new accounts on all Wikipedias.
An experiment which explores extending
Page Previews to mobile web
will be launched in the week of April 20 on Arabic, English, French, Italian, Polish, and Vietnamese Wikipedias. Page Previews are pop-ups that display a thumbnail, lead paragraph, and a link to open the full article of a blue link, thereby improving content discovery. The feature is already available on desktop and in the apps.
Read more about this experiment and others
On several wikis, logged-in editors who haven't
confirmed their email addresses
can now see a banner encouraging them to do so. Having the email address confirmed allows a user to restore access to the account if they lose it.
[12]
View all 15 community-submitted tasks that were
resolved last week
. For example, an issue where editing very large wiki pages in the 2017 wikitext editor caused slow loading, preview and scrolling lag, and performance issues when selecting, cutting, or pasting content, has now been fixed.
[13]
Updates for technical contributors
As part of the promotion of
CodeMirror
from a beta feature, all users will use
CodeMirror
instead of
CodeEditor
for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages.
[14]
The
mirrors.wikimedia.org
service for Debian and Ubuntu users will sunset and stop working on May 15. The resources for the service will be replaced with new and better options. Some users may need to switch to a different server which should take about a minute.
You can read more
[15]
The
image
and
oldimage
table will be removed from
wikireplicas
. If your tools or queries access
image
or
oldimage
directly, please update them to use the
file
and
filerevision
table before 28 May.
[16]
Following the recent implementation of global API rate limits on unidentified traffic, the Wikimedia Foundation will continue efforts to ensure
fair use of infrastructure
by applying global limits to identified API traffic beginning the last week of April. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see
Wikimedia APIs/Rate limits
and
Frequently Asked Questions
The
Attribution API
is now available as a
beta
. The API fetches information for crediting Wikimedia articles and media files wherever they are used. Reference documentation is available through the REST Sandbox special page available on all Wikimedia wikis (such as the
REST sandbox on English Wikipedia
). Share your feedback on the
project talk page
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
MediaWiki message delivery
15:00, 20 April 2026 (UTC)
Reply