Wikisource:Scriptorium

From Wikisource
(Redirected from Scriptorium)
Jump to: navigation, search
Important project pages: What is Wikisource? • Wikisource and Wikibooks • Votes • Copyright • Possible copyright violations • Proposed deletions • 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


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

ar : هذا الموقع الرئيسي لنقاش ويكي مصدر ومكان طلب المساعدة. استخدم اللغات التي تعرف، وترجم ما ترغب.
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.
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 : Jen la centra diskutloko por ĉio, kio rilatas al la Wikisource kiel vikio. Uzu la lingvo(j)n kiu(j)n vi konas kaj traduku laŭplaĉe tion, kion aliaj redaktis.
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.
he : זה הדף המיועד לדיונים העוסקים בויקיטקסט, והמקום לפנות לעזרה. השתמשו בשפות שאתם מכירים, ותרגמו את מה שאתם רוצים.
hy : Սա Վիքիդարանի հետ կապված հարցերի քննարկման կենտրոնական վայրն է, որտեղ դուք կարող եք նաև դիմել հարցերով։ Օգտագործեք ձեր իմացած լեզուն(երը) և թարգմանե՛ք ի՜նչ կամենում եք։
it : Questo è il luogo principale dove discutere di Wikisource, e il posto dove chiedere aiuto.Scrivi nella lingua che vuoi, puoi anche tradurre quello che vuoi.
ja : ここはプロジェクトについて議論したり、質問がある時に尋ねたりするための場所です。お望みの言語を使って書き込んで下さい。他の人の書き込みを翻訳して下さる方も歓迎です。
ko : 여기는 위키소스와 관련된 문제들에 관한 논의를 주로 하는 곳입니다, 그리고 도움을 요청할 수 있는 곳입니다. 당신이 알고 있는 언어를 사용해서 당신이 원하는데로 번역해 주세요.
nl : Dit is de centrale plek om elk onderwerp in Wikisource te bediscussiëren en de plaats om hulp te vragen. Gebruik de taal die je kent en vertaal wat en wanneer je wilt.
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.
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.
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 : 這裡是討論與維基資源有關話題和尋求幫助的頁面。使用您所了解的語言留言。您也可以在任何時候把他人的留言翻譯成您熟悉的語言。
(edit)

Archives
Note: all archives are made by copy&paste, so that the whole history is here except the pre-launch discussions, which are at meta.



Contents


[edit] Open Call for 2012 Wikimedia Fellowship Applicants

Wikimedia Foundation RGB logo with text.svg

I apologize that you are receiving this message in English. Please help translate it.

  • Do you want to help attract new contributors to Wikimedia projects?
  • Do you want to improve retention of our existing editors?
  • Do you want to strengthen our community by diversifying its base and increasing the overall number of excellent participants around the world?

The Wikimedia Foundation is seeking Community Fellows and project ideas for the Community Fellowship Program. A Fellowship is a temporary position at the Wikimedia Foundation in order to work on a specific project or set of projects. Submissions for 2012 are encouraged to focus on the theme of improving editor retention and increasing participation in Wikimedia projects. If interested, please submit a project idea or apply to be a fellow by January 15, 2012. Please visit https://meta.wikimedia.org/wiki/Wikimedia_Fellowships for more information.

Thanks!

--Siko Bouterse, Head of Community Fellowships, Wikimedia Foundation 03:10, 22 December 2011 (UTC)

Distributed via Global message delivery. (Wrong page? Fix here.)

[edit] etherpad + bugzilla + weblog Downtime again tonight

The maintenace for db9 was successfully completed but some followup maintenace is needed. As a result, you might have trouble with Wikimedia's Etherpad or Bugzilla or CiviCRM sites/services tonight. If interruption continues after 1820 PST please tell us in #wikimedia-tech (webchat link). — ☠MarkAHershberger☢(talk)☣ 15:28, 22 December 2011 (UTC)


[edit] Wsexport : an automatic export tool for Wikisource fr

French Wikisource is working on an export tool in epub, odt and others formats. He is join to a website that automatically provide list of books from a category that mark that books are good for export. He works now only for the French Wikisource but we can imagine that he can be used for the others one. You are invited to test it here. The book metadatas harvesting in Wikisource is possible with this microformat implemented in most of French Wikisource templates. We will be glad if people of the others Wikisource works with us to provide a very good export of books ! The source-code of the tool and the website is available here. All help is welcome ! Tpt 21:13, 28 December 2011 (UTC)

WOW!!! We surely want to try it for Italian Wikisource! What do we need to do and how can we help you? Candalua 22:19, 28 December 2011 (UTC)

This is awesome! As Candalua, I'm definetely interested in this. How we (Italian Wikisource, and maybe Wikimedia Italia) can help you? How could we start testing our books (do you think we could use your code to run our site as well?) Aubrey 00:04, 29 December 2011 (UTC)
The stand alone export tool is now available on the toolserver. You can try it for books of non-French Wikisources but it won't work fine until you implement the microformat in the book templates like Intestazione or Prooferead_pages_header_template. When it will be done the export tool can include many metadata on books and remove navigation templates that were "ws-export" html class. We can imagine also provide italian books in a website, the same like the French one or an other one from the same source. We are waiting you on github ! Tpt 11:14, 29 December 2011 (UTC)
To implement the microformat, get a look a the end of fr:Modèle:Proofreadpage header template at the end of the template, the whole block of code <div id="ws-data" class="ws-noexport" style="display:none; speak:none;">..........</div> export the necessary data used by the export tool. — Phe 11:26, 29 December 2011 (UTC)

Great! I added some microformat info on it.source (title, author, translator, year for the moment) and it seems to get them. I also added class="ws-noexport" in MediaWiki:Proofreadpage pagenum template, to hide unnecessary page links. There's just a small annoyance because in our Pages we have a <span class="SAL" that contains the page quality (useful to show it in the pagelinks), is it possible to hide it from the ePub?

Also, is it possibile to call the toolserver page passing along the language, the page title, and the file format? So that we can generate a link "Export in ePub" directly from the Header template?

Thanks very much to all of you for this amazing work! Candalua 14:25, 29 December 2011 (UTC)

For the <span class="SAL" the ws-noexport is maybe your help. Call the toolserver is of course possible with the "lang", "page" and "format" url params. Tpt 15:24, 29 December 2011 (UTC)
Yes, more generally I was thinking about the possibility of including a stylesheet on the ePub, so that every wikisource can create a page like Mediawiki:EPub.css with the styles they need to be included. It's true that we can simply add the necessary styles inline, but the page's html becomes heavier, and not all styles fit well both in the browser and in the ePub, sometimes you can have the need to render an element differently in the ePub and in the regular html page. What do you think? Candalua 16:07, 29 December 2011 (UTC)
It' not a bad idea. I will work on that tomorrow. Tpt 16:42, 29 December 2011 (UTC)
It's done. You can now use MediaWiki:Epub.css to provide css to epub files. Tpt 20:55, 29 December 2011 (UTC)
Thanks for the nice tool, i have added a css to de.ws and will try the css, if the tool is online again. Greetings --Michail 23:23, 29 December 2011 (UTC)
The tool is online again. I have make a mistake. Tpt 08:53, 30 December 2011 (UTC)
marvellous tool!
here a small bug: some of the original links into the text of pages lack of http: string, they appear as --src="//it.wikisource.org" instead of src="http://it.wikisource.org". Easy to fix I presume. I found it into the ePub from it:Georgiche.djvu. --Alex brollo 12:24, 30 December 2011 (UTC)
It's fixed. Tpt 16:25, 30 December 2011 (UTC)

Hello Tpt, is anywhere another place to post bugs? I have found small issues, and i think this thread here is not the perfect place for posting issues. But until we have a any bugfixing reporting tool (or whatever) i post the bugs that i found, also here. First: I think your bugfix for the issue one befor was not perfect, because links to the same page, anchor links like this <a href="#cite_note-33">, shows now a little bit strange ;-) <a href="http:#cite_note-33">. Here is now a http: what should not there. Second: It's a problem with german umlauts. You create the names of epub-file and included xhtml files a little bit wrong. You replace the german umlauts ü with eu, ä with ea and ö with eo. The correct replacement will be ue, ae and oe. It would be nice if you could fix these two small issues. And i have to say, it's a very cool tool. Greetings and i wish you and everyone a happy new year --Michail 00:52, 1 January 2012 (UTC)

What about adding epub files to the list of uploadable ones here? :-) --Alex brollo 06:56, 1 January 2012 (UTC)
For bugs, I've created a page on fr Wikisource. The bug with footnote is corrected. It's working again. For umlauts, it's strange,my regular expression only remove accentuation from letters, by exemple ü give u. But I think it's not important : nobody unzip the file. Happy new year ! Tpt 15:18, 1 January 2012 (UTC)
By the way, uploading EPub files is not allowed to commons because a EPUB sanitizer has to be writen first as indicated in this bug. Would you dare to write one? --Micru 21:12, 8 January 2012 (UTC)

Hi Tpt, congratulations on your work! By the way, have you considered merging your efforts with Extension:EPubExport, or reusing some of their code? There were some comments about this extension in Bugzilla --Micru 16:18, 1 January 2012 (UTC)

Upload of epub files is already possible here, just register (Alex, you're already registered). Nemo 14:08, 2 January 2012 (UTC)

LjL-2012 on IRC said he found this: https://code.google.com/p/wikipediaconv/ . Doesn't seem very useful (full dump to ePub??) nor able to generate good output, but seems worth testing if someone has Windows, just to try. Nemo 18:04, 4 January 2012 (UTC)

Interesting. I'll test it and read the source code. Tpt 17:14, 9 January 2012 (UTC)

An other thing : is someone volunteer to create a logo for the export tool and website(s) ? It will be a grate improvement. Tpt 20:11, 10 January 2012 (UTC)

Export tool integrate now a internationalisation system that works with a MediaWiki:Wsexport i18n.ini file. The reference file is here. An exemple in fr Wikisource Tpt 22:15, 13 January 2012 (UTC)

Can't you use translatewiki:? It's much better than spreading translation and documentation on dozens of websites where translators can't even edit it. Thanks, Nemo 22:37, 13 January 2012 (UTC)


I've started Wikisource:WSexport, to gather all informations about the necessary configuration. Candalua 15:09, 15 January 2012 (UTC)

Shouldn't WSexport become a Mediawiki extension the same way as Extension:Proofread Page did?--Micru 16:32, 30 January 2012 (UTC)
Maybe. But the integration will be an hard work. I'll work on that when I've more time. Tpt 17:34, 31 January 2012 (UTC)

[edit] माझगाव - पूर्वीच्या मुंबईच्या सात बेटांपैकी एक बेट

पूर्वीच्या मुंबईच्या सात बेटांपैकी एक बेट माझगाव : माझगाव हा शब्द माझं गाव आणि माझागोन (माझगाव वर पोर्तुगीज राज्य करीत होते) तर केथेलिक ह्याला माझगोन असेही म्हणत होते. हे सात बेटांपैकी एक बेट होय. माझगाव हा दक्षिण मुंबईचा विभाग असून रेल्वेच्या भायखला स्टेशन व हार्बरच्या डॉकयार्ड व सेंडहर्स्ट रोड स्टेशनने जोडले गेले आहे. माझगाव मध्ये केंद्र सरकारी संस्था जशा, मुंबई पोर्ट ट्रस्ट आणि माझगाव डॉक लिमिटेड असून, माझगाव कोर्ट किंवा न्यायालय देखील येथे आहे. इतकेच नव्हे तर येथे अेन्गलो इंडिअन शाळा असून त्यामध्ये सेंट पीटर आणि सेंट मेरी यांचा समावेश आहे.

माझगाव हा शब्द संस्कृत शब्द मत्स्य ग्राम या शब्दापासून तयार झाला आहे असे म्हणतात. याचा अर्थ माशांचा गाव असा होतो. येथील मूळ रहिवाशी हे आगरी आणि कोळी समाजाचे होते. याचबरोबर असेही मानण्यात येते कि माझगाव हा शब्द मराठी माझं गाव ह्या शब्दापासून तयार झाला आहे असे म्हणतात. माझगाव हा शब्द पोर्तुगीजान्पासून सुद्धा तयार झाला असावा असे म्हटले जाते. पूर्वीच्या काळी माझगाव हा विभाग आंब्याच्या झाडांसाठी फार प्रसिद्द होता. २० व्या शतकात देखील यांतील काही जाती दिसून आल्यात. हे छोटेसे बेट उत्तरेकडे वाढना-या छोट्या छोट्या डोंगरानि आणि बंदराकडील बाजूकडे किना-यांनी वेढलेले असून कोंकणाची आठवण करून देते. —unsigned comment by ‎ Mayurteem (talk) 16:32, 30 December 2011.

Sorry, I don't understand Marathi. Can a wikisourcian translate? --Zyephyrus 17:50, 30 December 2011 (UTC)
This seems to be encyclopedic information about w:Mazagaon in Marathi that would be better suited to Marathi Wikipedia. Shall I move it there? Shivashree 05:22, 31 December 2011 (UTC)
Yes, please. Thank you Shivashree! --Zyephyrus 13:25, 31 December 2011 (UTC)
I checked, the article already exists on Marathi Wikipedia with about the same information. I am going to leave as it is without any merge. Mayurteem can add any further encyclopedic information on Marathi Wikipedia. He can certainly add original free source documents here. Shivashree 14:11, 31 December 2011 (UTC)

[edit] Comparaison des sites Wikisoure

Bonjour et Bonne Année à tous, je ne sais plus où trouver le tableau de comparaison de différents Wikisource et leurs politiques respectives (scan, annotations, etc.) - Quelqu'un pourrait-il me redonner l'adresse, svp ? Merci d'avance,

Hello, and Happy New Year (a day late) : I lost the adress of the page which lists all wikisources and compares their policy (scan, notes, etc.) - Could someone point me again to it, please ? Thank you in advance…

--Hsarrazin 11:25, 2 January 2012 (UTC)

Wikisource:Subdomain coordination. --Milda 11:42, 2 January 2012 (UTC)
Merci, Thank you so much !! --Hsarrazin 11:49, 2 January 2012 (UTC)

[edit] Aggiungere il supporto al formato epub in "carica un file"

Chiedo gentilmente a chi se ne occupa di aggiungere il supporto al formato epub in quanto esso è uno standard di fatto ed inoltre è un formato aperto e molto diffuso fra gli e-book reader. Scusate se ho commesso errori ma non conosco molto bene il sito (come utente registrato). GRAZIE PER L'ATTENZIONE

ps. I dont know english very well.

—unsigned comment by Jpalex (talk) 12:08, 4 January 2012‎.

Per quale scopo di preciso? Il problema non è tanto caricare file epub quanto esportarne a partire dal contenuto di Wikisource, i documenti nei wiki devono essere modificabili e quindi a livello HTML si continuerà sempre a lavorare sulle pagine wiki. Comunque se serve caricare file epub temporanei per qualche motivo è già possibile farlo in Biblioteca di Wikimedia Italia. Nemo 17:49, 4 January 2012 (UTC)

[edit] Announcing Wikipedia 1.19 beta

Wikimedia Foundation is getting ready to push out 1.19 to all the WMF-hosted wikis. As we finish wrapping up our code review, you can test the new version right now on beta.wmflabs.org. For more information, please read the release notes or the start of the final announcement.

The following are the areas that you will probably be most interested in:

  • Faster loading of javascript files makes dependency tracking more important.
  • New common*.css files usable by skins instead of having to copy piles of generic styles from MonoBook or Vector's css.
  • The default user signature now contains a talk link in addition to the user link.
  • Searching blocked usernames in block log is now clearer.
  • Better timezone recognition in user preferences.
  • Improved diff readability for colorblind people.
  • The interwiki links table can now be accessed also when the interwiki cache is used (used in the API and the Interwiki extension).
  • More gender support (for instance in logs and user lists).
  • Language converter improved, e.g. it now works depending on the page content language.
  • Time and number-formatting magic words also now depend on the page content language.
  • Bidirectional support further improved after 1.18.

Report any problems on the labs beta wiki and we'll work to address them before they software is released to the production wikis.

Note that this cluster does have SUL but it is not integrated with SUL in production, so you'll need to create another account. You should avoid using the same password as you use here. — Global message delivery 16:40, 15 January 2012 (UTC)

[edit] Wsexport: an automatic export tool for Wikisource

Hello, and first sorry for this automatic delivery message.

An export tool for Wikisource books, Wsexport, is currently in active development. It is a tool for exporting Wikisource's texts in EPUB, ODT and other file formats. It was created for French Wikisource, but it's also available for the other Wikisource subdomains. It can be used directly from its page on Toolserver.org (for texts in all languages, use "www" for oldwikisource), or browsing http://wsexport.fr.nf (currently only for French Wikisource's texts).

In order to work, the tool need some configuration from your Wikisource subdomain, This page explains how to do it. Currently French, Italian, English, and German Wikisource does it.

You will find more information on The global Scriptorium. Ask here for all question.

This message was distributed to all Wikisources using the Global message delivery system. If you want to use it to send your messages, ask for permission here. Tpt (d) 21:19, 15 January 2012 (UTC)

[edit] Yesterday: Dies ater for the PUBLIC DOMAIN

Please discuss here: http://commons.wikimedia.org/wiki/Commons:Deletion_requests/All_files_copyrighted_in_the_US_under_the_URAA --Historiograf 21:07, 19 January 2012 (UTC)

[edit] Vector interface customization

I'm dragging into vector interface customization, (adding/removing buttons and popups into toolbar [1]; adding/removing tools into sidebar; adding "tattoos"; adding to toolbar draggable() feature; and so on). Don't presume any special js skill by me; I only put into practice the pedia principle "be bold". :-(

Now, I've a bad (but rewarding) attitude to "rediscover the wheel", as my patient it.source fellows know very well; so I'm asking here: is some of you working about similar goal and tricks? Is there a page to discuss this kind of topics to share "just rediscovered wheels"? ;-) --Alex brollo 07:42, 26 January 2012 (UTC)

I’m not working on it (I haven’t any skill in JS !), but I have a little remark : is it for it.ws only or for all the ws ? (or all the wikis ?) In both case, it could maybe be better to work on oldws (or on Translatewiki).
Cdlt, VIGNERON 21:28, 29 January 2012 (UTC)

[edit] Marathi WS

Hi, I imported the Marathi pages to the newly created mr.wikisource.org subdomain (see mr:special:log/import or my userpage there for a list). These can probably be deleted here now. --MF-Warburg 17:17, 7 February 2012 (UTC)

Please enter information as known at Wikisource:Subdomain coordination, so we know the policies and guidelines of the new subdomain.--Jusjih 14:26, 8 February 2012 (UTC)

[edit] MediaWiki 1.19

(Apologies if this message isn't in your language.) The Wikimedia Foundation is planning to upgrade MediaWiki (the software powering this wiki) to its latest version this month. You can help to test it before it is enabled, to avoid disruption and breakage. More information is available in the full announcement. Thank you for your understanding.

Guillaume Paumier, via the Global message delivery system (wrong page? You can fix it.). 15:23, 12 February 2012 (UTC)

[edit] Import Upload - revisited

I requested Import Upload privileges back in October (since archived, see this thread). Candalua and Ooswesthoesbes supported, there were no opposes. This action requires a local decision, probably by a crat and a request at the Steward request page on meta. We currently still have the problem that Transwiki import is enabled but broken due to some local settings (I submitted a bugzilla back in November, no action yet Bugzilla:32411). I have been waiting since October to be able to import a template from de.ws that is holding up work on a project but more importantly, we should have a few people around who can do this (Jusjih can, both as a steward and as a local import uploader but 1 person is clearly not enough as they aren't around day-to-day). Additionally, for large imports import upload is more useful. I re-post my request for further consideration or closure.--Doug.(talk • contribs) 02:26, 21 February 2012 (UTC)

[edit] Stale bots and sysops discussion from last year

In October I started a thread on accounts with privileges that they don't seem to need: Wikisource:Scriptorium/Archives/Jan_2011_-_Dec_2011#Stale_bots_and_sysops. The thread included at least 4 comments in favor of deflagging Wolfbot and CSNbot and at least 2, maybe 3 for desysopping User:ThomasBot (no comments in favor of the bot remaining a sysop, just questions about whether he's coming back from others). I think we have enough to deflag to the two bots. Can we get that done? I will start a separate thread on the Sysop flag because there are other inactive sysops that we should discuss.--Doug.(talk • contribs) 03:26, 21 February 2012 (UTC)


+1 for deflagging all 3 (Wolfbot, CNSbot, ThomasBot). We have currently 4 bureaucrats: excluding -jkb-, the other 3 have been active recently, we can directly ask to one of them. Candalua 13:56, 21 February 2012 (UTC)

[edit] Stale Sysops

Reference the discussion above and the one it references last October, I have started a pro forma desysop discussion on three sysops (ThomasBot, LadyInGrey, and Maximillion Pegasus) at Wikisource:Administrators#Vote_for_removal_of_administrator_privileges. The reasons are entirely for inactivity. I was going to include User:Dungodung but I noticed they have about a dozen recent log actions after some very long periods of inactivity, so I left them out. Please discuss at the Administrators page, not here.--Doug.(talk • contribs) 04:08, 21 February 2012 (UTC)

I personally feel that inactivity is not a real valid reason to desysop an admin, so I'm going to abstain from voting. --Ooswesthoesbes 09:54, 23 February 2012 (UTC)
Perdón por el español, es mi lengua nativa y me cuesta expesarme en inglés, aunque lo leo perfectamente. Todas las semanas entro a esta wiki en busca de vandalismos pero hay muchos administradores atentos y cumpliendo bien sus labores. No he editado desde hace mucho pero si consideran mejor que yo deje de ser admin, aceptaré la decisión de la comunidad. Un saludo, --LadyInGrey 03:10, 24 February 2012 (UTC)

[edit] Wikisources' software application updated to 1.19wmf1

Hi to all. Just saw one of the techs pop into the Wikisource IRC channel, and that was a good indication that they have updated our mediawiki software. Please report errors or discrepancies that you see. I am not sure whether you would like to keep a record here of identified issues, or whether you would like to add them at en:WS:S#Issues log for mediawiki update to 1.19wmf1 billinghurst sDrewth 12:29, 24 February 2012 (UTC)

Yep, from what I can tell they did the update on all Wikisources, except here on oldwikisource (see Special:Version). They will probably do this site in the next days.
BTW, we have some problem on it.wikisource: we have some gadgets that add custom buttons to the ProofreadPage toolbar. But after the update they seem to load before the ProofreadPage extension, so they don't work because the toolbar is not loaded. Do you know a solution for this? Candalua 14:19, 24 February 2012 (UTC)
I found the same error: es:Las mujeres de la independencia: 02, 03, 04, 05; 06, 07 ::¿¿(E2.80.94)??. --LadyInGrey 14:46, 24 February 2012 (UTC)
The problem was in MediaWiki:PageNumbers.js, the string "E2.80.94" probably has some special meaning that I don't know. Tell me if you find other pages with this error. Candalua 16:34, 24 February 2012 (UTC)
Thank you, Candalua, --LadyInGrey 17:38, 24 February 2012 (UTC)
Do you know if this problem is related to the upgrade? --Zyephyrus 08:55, 25 February 2012 (UTC)
Special:AbuseFilter/1 is the reason, whether the update has activated your abuse filter or not is unknown. The filter shows that it has been there since the middle of last year. Three ways to tackle it. 1) turn it off (yuck would be my thought); 2) if you think that it is harsh to disallow, then you could change it to Warn; 3) either to disallow or warn, you can create custom message rather than the default which sounds a little melodramatic. billinghurst sDrewth 09:16, 25 February 2012 (UTC)
Thank you sDrewth, this is more understandable for me now. --Zyephyrus 15:55, 25 February 2012 (UTC)

[edit] new tool

There's a new tool for namespace Page, that shows one or more tabs with a link to the texts that trasclude the current page. You can see it in action on Page:Fluors_alpinas.djvu/20 and the following pages (the tab "Text" near the up arrow). It was developed for it.source by it:User:Alex brollo, and it's now available for all subdomains (instructions on MediaWiki:TranscludedIn.js). Candalua (talk) 16:23, 5 March 2012 (UTC)

It doesn't seem to work when the ns0 page title includes a non-letter symbol. Page:Fluors alpinas.djvu/85, a poem with a question mark in the title, ommits the question mark in the link. In "What links here" it works normally, however. This could especially cause issues on pages and subdomains with non-latin script, e.g. our Hindi pages or the Japanese subdomain. --Kazu89 (talk) 17:13, 9 March 2012 (UTC)

Fixed, now it uses the native mediawiki function to get the encoded url. Thank you very much. Candalua (talk) 18:05, 9 March 2012 (UTC)

Changes like this one needs a centralized roll-out. The most active languages have volunteers that can update local templates (MediaWiki:TranscludedIn.js), but this will not happen in the smaller languages, and so we end up with very different levels of functionality. --LA2 (talk) 18:05, 13 March 2012 (UTC)

[edit] Help for creating a Wikisource in a new language

I was trying to find a guide for creating a Wikisource in a new language and couldn't find one. I can write one myself, but i'm just making sure that there isn't one already... Is there? --Amir E. Aharoni (talk) 22:38, 8 March 2012 (UTC)

All can be found here. For Wikisource the process is fairly simple: add a request on the Request for new languages page on meta and start working. --Ooswesthoesbes (talk) 09:40, 9 March 2012 (UTC)
I'm a langcom member, so i know that page fairly well :)
I'm talking more about a detailed technical guide for people who are not experienced with MediaWiki, but want to start a Wikisource in their language, something that would explain how to add your language to the list, how to create a category for it, how to start adding texts, how to sort them to groups, how to makes books and chapters etc. --Amir E. Aharoni (talk) 09:47, 9 March 2012 (UTC)

[edit] Problem on Bugzilla

Take a look at bug 18861 on Bugzilla. In short - at the moment, any content generated by templates is ignored by the search engine, i.e. pages transcluded in proofread extension. That means that over 50% of content on multiple Wikisource projects (i.e. French, Polish or Norvegian) is inaccessible to search engine. However, with recent developments on Bugzilla it seems that the problem will not be resolved in the foreseeable future. --Teukros (talk) 18:44, 9 March 2012 (UTC)

[edit] Request for Adminship

I have the project to rewrite and improve some of the Wikisource:Shared Scripts with the new mediawiki JS libs and create new ones using our new amazing microformat system, so I request adminship in this wiki in order to work without asking each hours. Tpt (talk) 18:22, 12 March 2012 (UTC)

[edit] Punjabi (pa)

Hello, I was wondering why there isn't a punjabi wikisourceNo community, no wonder. I know atleast one author (w:en:Bulleh Shah) whose works are in punjabi and in the public domain. Plus, I happen to have some of the works. I can type punjabi. I cannot get a scan of the works. I do not know panjabi enough to start a wikisource on my own.nor is one person community enough Panjabi wikipedia has very little or no community to ask for help (haven't tried to ask there yet).

Any suggestions on how to proceed?

PS: This website seems to have works too, although in a non-unicode font.--Siddhartha Ghai (talk) 02:44, 17 March 2012 (UTC)

Modifications in superscript.--Siddhartha Ghai (talk) 02:56, 17 March 2012 (UTC)

Hello Siddharta,

this is the right place to start adding Punjabi texts. I see from the 2 texts in Category:Punjabi that you already guessed which templates to use (Header + Textinfo). If you want, you can also create a copy of those templates and translate/adapt them for Punjabi. Many languages have the habit of placing Textinfo in the talk page, but I find it very disturbing, I worry that many readers will probably not found it; my advice is to put textinfo in the same page of the text. Best solution I think is to create a new template using the content of both Header and Textinfo; but feel free to do what you prefer. You can also create a Main page/pa (or whatever you prefer to name it) on the example of these ones. It would be better to have works with scans, but if you can't find any, no problem. Good work! :-) And ask if you need anything else :-) Candalua (talk) 21:22, 18 March 2012 (UTC)

The template use is courtesy the helpful people at IRC #wikisource. I'd rather just add texts for now. As I'm not a regular contributor, I won't be getting into where to place which template. Doesn't oldWS have a policy for this?
When there is a sufficient number of pages in pa, then maybe I'd work on a mainpage (and name it whatever pa-wp uses).
The problem with getting scans is that its just too costly.
Just one question, the website I linked to above contains works of other authors too, which I do not have physically. However, the site isn't very reliable for texts (I've found variations in the site and my physical source in the two texts I've added). Should it be used for the other authors' texts then? Or should we wait for someone to find a physical source and eventually add the texts?
Thanks :) Siddhartha Ghai (talk) 19:02, 19 March 2012 (UTC)
For consistency with other languages, the Punjabi main page should be called Main Page/ਪੰਜਾਬੀ. —Angr 22:14, 20 March 2012 (UTC)
Actually, I thought we discussed this last year and decided that we would actually use Main Page/ਪੰਜਾਬੀ and Main page/pa as redirects to the name with the local language word for "Main Page" as the target - this would make it easier to later migrate the project without changing all navigational links.--Doug.(talk • contribs) 17:11, 21 March 2012 (UTC)
We did? I thought we decided all the Main Pages should be subpages of Main Page and would thus be called Main Page/something, where "something" is replaced by the native name of the language in the native script. —Angr 21:04, 21 March 2012 (UTC)
Hmmm, maybe; I need to look again, it may not have been clear or at least not clear the way I thought. I know we did discuss the practical problem that most of us don't know most of the languages that are involved, so at a minimum a redirect from Main Page/language code should be required. Beyond that, they just need to all be the same in my opinion.--Doug.(talk • contribs) 22:25, 21 March 2012 (UTC)
Here is the discussion I was thinking of Wikisource:Scriptorium/Archives/Jan_2011_-_Dec_2011#Main_page_variants, not really as definitive as I thought and not much participation. There may have been others that I missed.--Doug.(talk • contribs) 08:11, 22 March 2012 (UTC)
The discussion I was think of is at Wikisource:Scriptorium/Archives/Jan 2011 - Dec 2011#Main Pages, which also didn't have a lot of participation, but where "Main Page/Native name" seemed to have the most support or at least the least opposition. And just a couple of days ago, that's the format I moved a whole lot of Main Pages to (because I thought that format had consensus). Because I did that, all the local Main Pages listed on Template:AllLanguages now use the "Main Page/Native name" format, though there are still some members of Category:Main Pages that don't (and they're not in Template:AllLanguages either). —Angr 23:25, 22 March 2012 (UTC)
Well now, if you've actually gone and organized things a bit then I certainly wouldn't suggest we should change what you did. It's about time we started organizing it. I wanted to but never seemed to get around to it. Thanks!--Doug.(talk • contribs) 11:46, 23 March 2012 (UTC)
Good; if no one objects, I'll continue organizing the Main Pages so they all have the same format. (I can't guarantee I'll get around to making all relevant redirects, though.) The next thing to organize is the language categories. Some are called "Category:English name" and some are called "Category:Native name", and some languages have both (e.g. we have both Category:हिन्दी and Category:Hindi). The new Template:Langinfo assumes that the category is called "Category:Native name", so we should probably standardize on that. The problem is that some of the "Category:English name" categories have hundreds of pages in them (Category:Georgian has almost 800!), and I can't imagine anyone wants to change the categories on all these pages by hand. (I certainly don't!) A bot could recategorize the pages quickly, but we don't seem to have any active bots at Multilingual Wikisource at the moment. —Angr 13:44, 23 March 2012 (UTC)
I don't have a bot flag here but if given the category names I can do this using my bot(CentralAuth).--Siddhartha Ghai (talk) 23:12, 8 April 2012 (UTC)

[edit] Main page

Just a note. The mainpage should state that the X+ ones are the subdomains, the wikisource.org part is the oldWS list and A-Z contains both of them.

I just spent the past few hours trying to dig up how to add the oldWS langs into the X+ parts and writing up comments for that correction (which I didn't post) before finding out that the X+'s are only subdomains.

The interwiki link color isn't different enough from the wikilink color to suffice as differentiation in itself. Without a heading or statement giving this fact, there's no way for non-WSians to differentiate between the two types.--Siddhartha Ghai (talk) 08:57, 20 March 2012 (UTC)

You're absolutely right but I can't help you with this. On the contrary, I see another problem with this list: it's completely outdated. My language and many others don't even exist in it. What is more... what to do with languages that have a subdomain but have parked some texts (or text parts) here due to copyright issues (German and Polish are two examples)? --Kazu89 (talk) 10:50, 20 March 2012 (UTC)

If some of you wants to add languages:

I changed protection so that autoconfirmed users can edit them. Candalua (talk) 18:17, 20 March 2012 (UTC)

Another point is that the Main Page links to all the individual languages' own Main Pages; if your language doesn't have a Main Page (Romansh doesn't, for example), it's going to get overlooked and left off the main Main Page. So, Kazu89, you need to create Main Page/Rumantsch and put it into Category:Main Pages so it doesn't get forgotten! —Angr 20:06, 20 March 2012 (UTC)

I absolutely agree that the colours are too similar, but to change them we should discuss at a higher level than here :-) Anyway, non-Wikisourcians readers probably do not bother to know if the link points to a subdomain or not. They just want to go to the main page for a given language, wherever it is. It's also right, in my opinion, that for German and Polish there's only the link to the subdomain; the texts hosted here should be pointed from there. (By the way, I will never understand why a text cannot be hosted on de.source due to copyright, but it can be hosted on oldwikisource... we are the same site! we share the same servers! what's the difference?) Candalua (talk) 21:36, 20 March 2012 (UTC)

Local policy. Even though all the servers are in the U.S., the local policy of German Wikisource is to host only content that is public domain in Germany. (Presumably the Polish Wikisource has a similar policy.) But the local policy of Multilingual Wikisource is to host content that is public domain in the U.S. So, for example, works by Thomas Mann that were published before 1923, or published after 1923 but without a copyright notice or without proper renewal, can be hosted here (because they're PD in the U.S.) but not at de-ws (because they won't be PD in Germany until 2026). —Angr 22:11, 20 March 2012 (UTC)
That's actually the default policy per WMF rules for every project that has a country from which it is primarily accessed so the Polish Wikisource (assuming it is primarily accessed from Poland) must have that rule unless they have affirmatively adopted a different rule - that's not exactly what the policy says but that's what I understand it is intended to mean. mul.ws is excepted from the rule since we don't have a primary language of readership (as also with meta, mw.org, and commons - which has a local rule that conflicts which is why Mann's (and Hesse's - I'm working on one of his) have to be uploaded here as well.) The only languages which don't have an issue are English and (mostly) dead languages like Latin or synthetic languages. All other languages could, at least theoretically, have works here and the Main page needs to accommodate that. How to best do that, I don't know. --Doug.(talk • contribs) 16:33, 21 March 2012 (UTC)

[edit] Another request for adminship

I just added a request for adminship for me. Figured it was about time and started to ask someone to nom me but realized we don't seem to do that here. Also, while you're about it, please take note of my request above for import upload rights, above, it's really getting stale; I had to bring it forward as it had gotten archived. I think we should avoid archiving matters that aren't actioned, especially those from late in the year. Thanks.--Doug.(talk • contribs) 13:45, 20 March 2012 (UTC)

[edit] Gujarati Wikisource

Hi, the whole content of Category:Gujarati has now been imported to the newly created http://gu.wikisource.org subdomain. So they can probably deleted here now. In case any pages are missing, please tell me and I'll import them too. --MF-Warburg (talk) 21:55, 27 March 2012 (UTC)

The same for Belarussian (be:). --MF-Warburg (talk) 22:29, 27 March 2012 (UTC)
Did you get Category:ગુજરાતી for Gujarati too? It's one of the languages that wound up with two categories somehow. —Angr 23:15, 27 March 2012 (UTC)
I'll check that, though it seems to be that all pages are in both categories (equal number of pages in them). --MF-Warburg (talk) 23:28, 27 March 2012 (UTC)
Is Belarusian OK, at least? -- Liliana-60 (talk) 18:34, 4 April 2012 (UTC)
I think so. However, I just saw this, but I actually, all pages from that category should be imported. --MF-Warburg (talk) 14:42, 6 April 2012 (UTC)

This still hasn't been done... why? -- Liliana-60 (talk) 18:52, 20 May 2012 (UTC)

[edit] author namespace

Currently some author pages use the "Author:" prefix, other do not. I propose this rule: all author pages must have the "Author:" prefix, so that they are correctly counted to be in the author namespace, and not in the main namespace. Pages that use a different prefix or no prefix should be moved. Redirects can stay. Candalua (talk) 07:39, 30 March 2012 (UTC)

Is Author: activated as a real namespace here, or is it just a pseudo-namespace? I ask because the Author pages on my watchlist are listed under "(Main)" when I click "View and edit watchlist". (They're also shown as redlinks there, even though the pages exist, which I don't understand.) —Angr 09:11, 30 March 2012 (UTC)

Author is a real namespace, it was created with bug30724 and pages starting with Author: were moved from ns0 to the new namespace. Maybe it's just the watchlist that's broken. Candalua (talk) 12:19, 30 March 2012 (UTC)

Well, whatever it was, it's fixed now, because now, the author pages are listed in Author: namespace and they're blue. Anyway, back to the original question, I support moving all author pages to the Author: namespace. Should an author also be listed in the category of the language in which he wrote? Using Irish as an example, Author:Peadar Ua Laoghaire is currently in Category:Gaeilge; is that desirable? Should there be an intermediate category (like Category:Údair or something, údair being Irish for "authors") to gather all Irish-language authors together, or is it preferable to have all authors grouped together in Category:Authors as well as in the various languages? The {{Author}} template automatically puts all authors into Category:Authors without regard for language; if we want to group them by language we'll need to tinker with that template. —Angr 13:22, 30 March 2012 (UTC)
To tell the truth, I'm opposed to your proposal. Actually, I'd like to keep the language projects separate from one another. My arguments, regarding the author namespace, are as follows:
  • If an author was active in different languages or if translations exist, they would all be listed on the same page (language of introduction?)
  • If a given project is moved to its own subdomain, this will facilitate several things, I think, including that mentioned above
I would prefer to use pseudo-namespaces for all types of page, save for categories, as they are not edited by individual user but by the system. Another possibility would be to use the system Incubator uses, but many people seem to be overcharged with the prefixes used there. I hope you get my point and, if you don't agree, can come up with a solution for the flaws mentioned. Kazu89 (talk) 22:49, 7 April 2012 (UTC)
It is important to keep something for "author" namespace in the language of the work for current use and possible later migration. However, we must face the fact that many languages will never migrate and even if they eventually do the admins and others here need to be able to track them. There is nothing to prevent creation of many aliases for "author", it's a simple bugzilla request that can be executed in a few seconds by anyone with the required access. I believe this is actually the decision that was made last year when we implemented the author namespace and we may have even started compiling a list of aliases, I'd have to look back - a problem with archiving automatically at year end. I am less concerned with categories and since you can't have meaningful redirects or aliases in categories, it's best to just put them all in Category:Author and Category:<lang> in my opinion.
As for the point about an author being active in different languages, well, I think that's the sort of thing that we should track here and a very valid use for mul.ws beyond simply and incubator. Multilingual pages are possible and desirable. If a language is on the verge of going live and wants to create this infrastructure we can always create a pseudo namespace or request a new one.--Doug.(talk • contribs) 06:36, 8 April 2012 (UTC)

[edit] De-crat

I have nominated -jkb- for removal of crat privileges. I don't find any evidence of a vote or discussion and the user has never logged an action as a crat since they were promoted in March 2011; they actually haven't logged an admin action since before that, so I've nominated them separately for removal of that privilege as well - to be consistent with others and because there is a 6 mos inactivity practice here. Please take notice of the discussion at Wikisource:Administrators#-jkb-_2. I placed the discussion there because the Crat page has only been used for crat requests not for nominations and decrat actions.--Doug.(talk • contribs) 12:32, 6 April 2012 (UTC)

[edit] Desop votes - closing?

Historically it hasn't taken much to desysop for inactivity. I understand that Ooswesthoesbes doesn't support the practice in general as noted above; however, it's been going on for several years and was discussed in the past so I won't address that here. In several cases, inactive users have been desysopped with only two votes, including the nom. While low, we aren't a very active site for such discussions and the general premise is that the user obviously doesn't need the bit right now and can ask for it back anytime, so it's low cost. Some of the users may have permanently retired (in ThomasV's case it's at least semi-permanent, unfortunately).

Does anyone object to summarily closing discussions with a result of removal of the bit if the discussion stays open for 30 days with no support for retention? Currently that would affect ThomasBot and Maximillion Pegasus.

How about where there is one or more supports for retention, a close by an uninvolved user or after no less than 30 days?

I've noticed some discussions historically have stayed open for more than a year, which is silly.--Doug.(talk • contribs) 09:13, 9 April 2012 (UTC)

[edit] Tracking Bug for Wikisource

I have created a tracking bug at bugzilla:35925, this bug is intended to list all bugs that are of special interest to wikisource. Just add any relevant bug to the "Depends on" field. Do not remove bugs when they are resolved, they'll simply be crossed out on the list when they are closed as resolved or dups or whatever.--Doug.(talk • contribs) 16:50, 15 April 2012 (UTC)

[edit] Bug 32189 and the mul.ws question



This discussion is transcluded from Wikisource:Scriptorium/Bug 32189 on wikisource.org aka sourceswiki aka multilingual wikisource (fka "old wikisource")

  • Bugzilla:32189 is the bug requesting our interwiki languages links to be fixed so that subdomains can have correct sidebar links to works and other pages on this project. The bug, however, also touches on issues of whether mul.wikisource.org needs to exist. A discussion of this bug started on en.ws but I have moved it to a subpage on mul and transcluded this discussion on both mul and en.ws.

[edit] Bugzilla:32189 oldwikisource language id bug

I don't fully understand this issue...

Isn't http://www.wikisource.org suppose to be the multilingual portal(i.e www.wikiwhatever.org )?

The wikipedia family has one and the language code is correctly set to mul & which is overridden as needed by every other language that needs to be listed or linked on a per div or span basis. See

See http://meta.wikimedia.org/wiki/Talk:Www.wikipedia.org_template for the basics.


... but we don't have the typical multilingual portal for the Wikisource family..

See http://meta.wikimedia.org/wiki/Talk:Www.wikisource.org_template for leftovers.

...the WWW url redirects to the oldwikisource's Main Page instead because this Meta template is missing/invalid/dead.

The way I see it, creating mul.wikisource.org or mul:s won't solve the interwiki/interlanguage/translation issues - everything will still need to be hacked or scripted to function as some workaround, No?

I think we need to separate the missing mul/www-prefixed multilingual portal from the rest of oldwikisource proper and use one of the other two (special) ids for site/lang ID dedication (mis.wikisource.org or und.wikisource.org)

  • {{language|mul}} → Multilingual
  • {{language|mis}} → mis misc. - needs to be added
  • {{language|und}} → und undefined - needs to be added

Not sure what happens to all the current pages based on English but all the other languages that are present will probably no longer need to override English via scripts/templates for starters. Am I missing some key fact or something here? -- George Orwell III (talk) 06:35, 13 April 2012 (UTC)

  • I'm not sure but I think you may be right that multiple solutions are required here for distinct problems and that is contributing to some of the confusion on that bug. I will note though that this really needs to be discussed on wikisource.org. The problems I see are:
    1. Works that are in a language that has no subdomain (and may never have one for some very obscure or historical languages), works that are in a language that has a subdomain but the subdomain has a stricter copyright policy than US law, and possibly works that are truly multilingual (i.e. they have no base language) such as treaties, need a home. Currently they are maintained on wikisource.org.
    2. Interwiki language links to works noted in 1, above, should function the same as other interwiki language links that is [[xxx:Some page]] should create a sidebar link to "Some page" on the appropriate wikisource. Currently, this fails with wikisource.org. This is the reason for the bug you reference, which was filed by Candalua. As noted by Candalua, the ISO 639-2 language code for multiple languages is "mul", so the link should ordinarily be styled [[mul:Some page]] irrespective of whether mul.wikisource.org is a subdomain.
    3. Matters of general interest to all wikisourcerers (to use Dominic's term for us) need a place to be addressed; particularly development issues and documentation, as well as shared scripts. Currently that place is wikisource.org. If works and templates were removed from there, it probably wouldn't need linking except maybe from Scriptorium, which could be managed with my js workaround currently in use here. There is probably no good reason to keep this at the same location as works.
    Did I miss some things or misstate some things? Very likely. On a related note I'm going to be writing up a page on wikisource.org to discuss all of the many issues involved in any multilingual work, both technical and stylistic. The current system creates many problems. All known alternatives create other problems - though not necessarily of the same quality or quantity. Again, all of this should be discussed over at wikisource.org as we can't really resolve it here - though obviously this location gets more day-to-day traffic.--Doug.(talk • contribs) 11:13, 13 April 2012 (UTC)
Points all well taken here & agree its complicated, but I don't see how you are accomplishing anything by applying the MUL id. If a work is in Russian, you are currently overriding the default HTML language designation (English - but not us here on en.WS English) and subsequent skin generated mw-content-ltr/rtl div class(es) for manually added Russian. Making the default language MUL still means you need to overide it to be able to get to editing in Russian (not phoney script hacked, font induced Russian over English). What you want is to override an undefined default - making your manually added language id and direction the default by fallback (hopefully).
All MUL indicates is that multiple languages appear on one page - not multiple pages with differing languages for each page throughout a site. In short MUL is not meant to be a site wide default but a per page default (typically overridden by multiple div or spans with their own language ids as needed). UND, however, makes the user added language the Default for any particular page consistently site wide. Of course, The MW & WS namespaces among others will need to be overidden by English if a 1st fallback is unassignable at the skin level (the level where the HTML & BODY tags are actually assigned a language).
Plus -- it is kind of unfair to usurp the standard multilingual portal for oldwikisource's main page. I understand feelings run deep and over a long time concerning oldwikisource but to pidgeon hole hundreds of thousands pages found in established language sub-domains for the sake of 10K on life-support seems counter-productive to put it mildly. -- George Orwell III (talk) 15:34, 13 April 2012 (UTC)
Hmm, I need to think about this some. I'm really not stuck on "mul", just need something. If you don't object, I'd like to do something we don't normally do here and move this discussion to it's own subpage and transcluded it both here and at wikisource.org's Scriptorium. Probably the subpage should actually be over there. I'll make the move and you can revert if you strongly object.--Doug.(talk • contribs) 15:08, 15 April 2012 (UTC)
You'd be the only one who can do that. Just noticed Mobile View (wayyyy down at the bottom of most pages) doesn't work on OldWikisource either. Look -- if we don't have enough traffic issues as it is -- I personally don't want to miss out on the mobile content revolution so I move resolving this sooner rather than later be a priority over most of the other "neat-o" editing bells & whistle Bugzillas if at all possible (and that www.wikisource.org multi-language portal page has to come back to the wiki-wide standard over the current redirect as OlsWikisource's mainpage. We don't want folks landing on sub-standard pages with sub-par transcriptions as part of our guiding principles so it only makes sense the same apply to (sub)domains that don't carry the same basic functionality as the other wiki foundation sites do. -- George Orwell III (talk) 22:18, 15 April 2012 (UTC)
Mobile on multilingual is now Bugzilla:36002, thanks.  :\ --Doug.(talk • contribs) 04:56, 16 April 2012 (UTC)
Well, just to be clear, what I meant there was resolving the domain-name question as laid out in Bugzilla 32189 before addressing all the other bugs/wishes out there. If making "noise" on the mobile question gets us there faster; all the better. If they fix the mobile view issue without resolving the domain name questions; we might have made things more complicated in the long run. -- George Orwell III (talk) 10:42, 16 April 2012 (UTC)
I agree, I tend to think it's best to list all bugs as we find them and we can always note that it depends on the other bug if we think that's the case or simply request that they defer the solution until the other matter is resolved.--Doug.(talk • contribs) 12:08, 16 April 2012 (UTC)
With help from enomil, we have determined the problem is in the MobileFrontend, it's looking for a three-part domain name and can't handle a two-part domain name like http://wikisource.org--Doug.(talk • contribs) 08:25, 17 April 2012 (UTC)
Getting back to this, I don't see setting the interwiki language link to "mul" as requiring us to apply "mul" as its "site wide default" language. On the other hand, your point about the main page is well taken - we should have multiple language content based mainpages, especially if we concede that some languages may never have their own subdomain. Possibly, we should even have a content based mainpage with multilingual content, that is to say, it would display works in multiple languages and maybe work as a portal to the works on the subdomains rather than the current system, which seems to give more of a "For French go here" than a "For works in French go here" flavor; I truly hope the latter is what we want our main page to project.--Doug.(talk • contribs) 09:38, 20 April 2012 (UTC)
The order of language determination goes → sitewide setting → sitewide fallback(s) → user preferences setting → user preferences fallback(s) → per page setting → per block(s) on a page (core JS, CSS and a handful of MediaWiki / Special pages are always in English). You can set whatever 2 or 3 letter domain name prefix you like as part of a recognized interwiki "id" as you like as long as the real language identifiers for site, user and page are set according to what outcomes are desired when clicked-in /clicked-on independently.

Life would be somewhat easier if the 2 or 3 letter domain name prefix "matched" at least the site id assignment but that betrays the desired outcome of a true single language environment for both editing and viewing. This is why I believe ( and stress believe only ) that in order to achieve the desired outcome in old wikisource's case, one where multiple languages will be hosted under one umbrella site domain name & not so much a site with a batch of individual multi-lingual pages, the best possible option is to have an undefined site id; letting the appropriate language fallbacks dictate where folks land and in what medium they will be able to view and/or edit any give page in.

What exists now is nothing more than a ["broken"] English language based site and folks are merely hacking it so that some other language overrides that default English language code when it comes to editing / viewing. So sure, using MUL will solve your cherished interwiki linking in the sidebar and such, but it won't mean the site is really multi-language capable nor truly MediaWiki interwiki / translation enabled. -- George Orwell III (talk) 14:49, 23 April 2012 (UTC)

[edit] New features in ProofreadPage

The new version of Mediawiki that will be deployed the April 28th (more info) will bring new features to ProofreadPage : The tag <pages> get new options in order to improve transclusion system of multi-pages books (with .djvu or .pdf file). Here they are:

step
Transclude only one page on n. By example : <pages from=1 to=10 step=2 /> show the 1st, 3rd, 5th,7r and 9th pages.
exclude
Don't include following pages. By example : <pages from=1 to=10 exclude="2-5,9" /> show the 1st, 6th, 7th, 8th and 10th pages.
include
Include following pages. By example : <pages include="2-5,9" /> show the 2th, 3th, 4th, 5th and 9th pages.

We can, of course, use all the attributes on the same tag. By example <pages from=1 to=10 include="31" exclude="2-4" step="2" /> will show 1st, 5th, 7th, 9th and 31th pages. —unsigned comment by Tpt (talk) 09:30, 17 April 2012 (UTC).

For Tpt and for all the workers in such successful and useful additions: Thanks !Thanks! Splendid news!  :) --Zyephyrus (talk) 09:16, 20 April 2012 (UTC)
Can we get an update to Wikisource:ProofreadPage? billinghurst sDrewth 13:16, 20 April 2012 (UTC)
Yes check.svg Done I have pasted it: is it correct? --Zyephyrus (talk) 22:21, 20 April 2012 (UTC)
Yes thanks a lot ! Tpt (talk) 08:09, 21 April 2012 (UTC)

[edit] Notice of a css class discussion on EN that affects all subdomains

Please take note of en:Wikisource:Scriptorium#Other_issues and particularly en:Wikisource:Scriptorium#Proposal. This discussion appears to be resolving now in favor of activating the class for all namespaces. The discussion really should've taken place here but as it's nearly resolved in favor of the less restrictive use I'm not moving or transcluding it. Please note though that this will require local changes to CSS to either enable or disable the colors, depending on which is the default.--Doug.(talk • contribs) 10:49, 23 April 2012 (UTC)

[edit] Wikisource and Project Gutenberg

Redundancy? I took a look at PG's site and searched here, but all I could find is a brief and old discussion at en.ws about the overlapping nature of WS and PG. Have either of these communities had a serious discussion about what appear to be redundant mission statements? Is it possible to integrate one into the other? Koavf (talk) 02:24, 27 April 2012 (UTC)

I don't see how. They're not a wiki and they don't provide scans of the original works. —Angr 09:03, 27 April 2012 (UTC)
It would be possible for them to bring all their works here to join us. There output is the same, however, the approach is somewhat different …
  1. We are using wiki as the tool, online, and wikilinks
  2. We are doing a holisitic approach to being a library, not just reproduction of text
  3. We have images
  4. We encourage casual transcription
  5. We are part of a bigger scheme of wiki that looks to interlink (between encyclopaedia/dictionary/images/languages/...)
plus presumably other things. billinghurst sDrewth 03:31, 6 May 2012 (UTC)
Scope Clearly, the two communities aren't identical, but it just seems silly for someone to be typing up and spot-checking the same text in two separate places. Because of licensing issues, it's (apparently) not possible to just port over all of their content, but that also seems silly to me as well. If they could simply relicense, wouldn't WS have a huge new source of texts that won't require our users to reinvent the wheel? Koavf (talk) 23:06, 8 May 2012 (UTC)
The public domain part of their content can already be copied over here, and indeed a lot of it has been. —Angr 22:18, 9 May 2012 (UTC)

[edit] New version of ProofreadPage

Hi! New version of ProofreadPage extension is available for testing on test2. List of some changes:

  • 34732 The scan does not appear on Opera.
  • 35757 Add 'onlysection' parameter to <pages/>.
  • 36070 <pagelist/> should show localized page numbers
  • 36115 Anonymous users cannot change page status
  • 36125 Position of quality buttons should not change
  • 36158 <pages> transclusions allow for infinite loop - This change disables nested <pages> transclusion completely.

If you find any errors please file a bug on bugzilla, so we can fix the issues before the upcoming deployment. Beau (talk) 07:29, 1 May 2012 (UTC)

[edit] Trial of thumbnail regenerator — volunteer testers?

I have asked one of the gadget developers at Commons to assist adapt a tool for our use.

The current problem is that when in transcription mode with Proofread Page, there are occasions when the image is not generated properly, and it is difficult to purge the thumbnail. This application adds a PURGE tab to the top right in vector/monobook skins, which should then purges stubborn image file. To identify where and when is needed is a little sporadic as we don't know when the thumbnail generators for commons will play up, hence the call for vols, and to request your feedback. [Note: Only tested in monobook and vector skins]

To trial the application, add the following text to your file Special:MyPage/common.js

// test of thumbnail regenerator [[File:User:Rillke/forWikisource.js]]
mw.loader.load('//commons.wikimedia.org/w/index.php?title=User:Rillke/forWikisource.js&action=raw&ctype=text/javascript');

Please provide your feedback (preferably at enWS), so I can look to how we can update, preserve and manage the gadget. Thanks. billinghurst sDrewth 03:25, 6 May 2012 (UTC)

[edit] Bot flag for GedawyBot

The bot mades the same function at many wikis & Commons & Meta and Wikispecies. I'm sorry for doing many test edits. Thank you.--M.Gedawy 22:29, 7 May 2012 (UTC)

Thanks to you! Test edits are ok. I support this request. Candalua (talk) 09:37, 8 May 2012 (UTC)

[edit] Special:Statistics

Hello, what has happened to Special:Statistics. For instance, on Croatian Wikisource, the count dropped from +7.900 to 5.003 (see: hr:Posebno:Statistika). On Serbian Wikisource the count dropped for about 1.000 (see: sr:Посебно:Статистике). Did the OldWikisource experience a simmilar drop? -- Bugoslav (talk) 17:24, 13. V. 2012. (CEST)

Phe’s statistics give this. Is it different from figures given by other sources? --Zyephyrus (talk) 07:11, 14 May 2012 (UTC)
I see that it is only the ProofreadPage Statistics, it doesn't include Serbian. Strangely enough it shows only 1062 (as total count of all pages) for Croatian. If you have any info, please do write on hr:Wikizvor:Pisarnica#Brojidba. Thanks. :) -- Bugoslav (talk) 13:03, 14. V. 2012. (CEST)

These changes in the stats are the result of bug33253. The original goal was actually to fix the page count, but it looks like the new numbers are just as inaccurate and wrong as the old ones... Candalua (talk) 19:21, 17 May 2012 (UTC)

[edit] interwiki links pointing to wikipedia instead of wikisource

It looks like our interwiki links are now pointing by default to Wikipedia, instead of Wikisource. This is a regression because this was fixed just some months ago. I'm reopening bug29591. Candalua (talk) 09:23, 18 May 2012 (UTC)

Retrieved from "http://wikisource.org/w/index.php?title=Wikisource:Scriptorium&oldid=333593"
Personal tools

Variants
Actions
Navigation
Print/export
Toolbox
In other languages