Wikisource:Scriptorium

From Wikisource
(Redirected from WS:S)
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.
zh-hant: 這裡是討論與維基文庫有關話題和尋求幫助的頁面。使用您所了解的語言留言。您也可以在任何時候把他人的留言翻譯成您熟悉的語言。
zh-hans: 这里是讨论与维基文库有关话题和寻求帮助的页面。使用您所了解的语言留言。您也可以在任何时候把他人的留言翻译成您熟悉的语言。
(edit)


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

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

Coordination: StatisticsProofreadPage StatisticsSubdomain coordinationNews


Pre-launch discussions


Archives

The whole history is here.


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]

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)TCM 07:28, 13 January 2020 (UTC)

Tech News: 2020-03[edit]

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

Tech News: 2020-04[edit]

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]

18:52, 27 January 2020 (UTC)

Tech News: 2020-06[edit]

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

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)TCM 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)

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]

16:16, 17 February 2020 (UTC)

Tech News: 2020-09[edit]

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]

00:35, 3 March 2020 (UTC)

Tech News: 2020-11[edit]

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)TCM 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)TCM 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)TCM 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)TCM 01:33, 16 March 2020 (UTC)

Tech News: 2020-12[edit]

21:18, 16 March 2020 (UTC)

Tech News: 2020-13[edit]

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]

17:24, 30 March 2020 (UTC)

Tech News: 2020-15[edit]

19:01, 6 April 2020 (UTC)

Tech News: 2020-16[edit]

15:30, 13 April 2020 (UTC)

Tech News: 2020-17[edit]

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

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

Reminder: Technical maintenance planed[edit]

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

Tech News: 2020-19[edit]

16:59, 4 May 2020 (UTC)

Tech News: 2020-20[edit]

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)TCM 08:04, 13 May 2020 (UTC)

Tech News: 2020-21[edit]

17:18, 18 May 2020 (UTC)

Tech News: 2020-22[edit]

14:17, 25 May 2020 (UTC)

Tech News: 2020-23[edit]

22:30, 1 June 2020 (UTC)

Tech News: 2020-24[edit]

21:11, 8 June 2020 (UTC)

Tech News: 2020-25[edit]

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]

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)TCM 01:41, 25 June 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]

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)

Tech News: 2020-28[edit]

20:18, 6 July 2020 (UTC)

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

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