Wikisource:Scriptorium

From Wikisource
(Redirected from Scriptorium)
Jump to navigation Jump to search

Welkom · أهلا و سهلا · Xoş gəlmişsiniz · Вiтаем · Добре дошъл · স্বাগতম · Degemer mat · Dobrodošli · Benvinguts · Ⲛⲟϥⲣⲓ · Croeso · Velkommen · Willkommen · Şıma xeyr ameyê · Κκαλώς ήρθες · Welcome · Bonvenon · Bienvenidos · Tere tulemast · Ongietorri · خوش آمدید · Tervetuloa · Tervettulemaa · Bienvenue · Wolkom · Fáilte · भळु-औणु · સુસ્વાગત · ברוכים הבאים · स्वागतम · Dobrodoš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ö · კუჩხი ბედინერი ჸოფედას თქვანი მოზოჯუა · װילקום · 欢迎 · 歡迎 · (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.
gbm: इ च मझळु अड्डा विकीसोतु दगड़ मुद्दा बारा म छुंई लगाणु खुणी, अर ठाणु मदद मंगण खुणी. इस्तेमाल कारा उ भाखा ज्व तुमु बिंगुदौ, अर बदलाखरा जू च पसंद​।
he: זה הדף המיועד לדיונים העוסקים בויקיטקסט, והמקום לפנות לעזרה. השתמשו בשפות שאתם מכירים, ותרגמו את מה שאתם רוצים.
hy: Սա Վիքիդարանի հետ կապված հարցերի քննարկման կենտրոնական վայրն է, որտեղ դուք կարող եք նաև դիմել հարցերով։ Օգտագործեք ձեր իմացած լեզուն(երը) և թարգմանե՛ք ի՜նչ կամենում եք։
io: Ita esas la centrala loko por diskutar problemi pri Wikifonto, e la loko por serchar helpo. Uzez la linguo/i quan vu parolas, e tradukar quon/in vu volas.
it: Questo è il luogo principale dove discutere di Wikisource, e il posto dove chiedere aiuto.Scrivi nella lingua che vuoi, puoi anche tradurre quello che vuoi.
ja: ここはプロジェクトについて議論したり、質問がある時に尋ねたりするための場所です。お望みの言語を使って書き込んで下さい。他の人の書き込みを翻訳して下さる方も歓迎です。
ko: 이곳은 주로 위키문헌과 관련된 문제들에 관한 논의를 하는 곳이며 도움을 구할 수 있는 곳입니다. 당신이 구사할 수 있는 언어를 사용해서 마음껏 번역해 주시길 바랍니다.
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.


New user group for editing sitewide CSS / JS[edit]

My idea is that we need one or two admins / non admins at least in this group here, which starts now. Any suggestions? (As far as I know the admin rights are not nessesary for it; just users who know what it is.) -jkb- (talk) 20:31, 14 August 2018 (UTC)

I think this flag may be assigned to admins by 'crats just on request, when they need it per 'crats discretion (like in many other wikis). Do you wish to suggest some non-admin candidates? Or do you think we should assign it to some users in advance for the case when no `crat is active? Ankry (talk) 08:01, 16 August 2018 (UTC)
I agree, as this was something any admin could do prior to this - in my opinion - superfluous user group. --Ooswesthoesbes (talk) 08:30, 28 August 2018 (UTC)
@Ooswesthoesbes: I don't agree with that… The point of separating these rights into another group is so that there are fewer people able to edit JS and CSS files. By editing those, people could insert malicious scripts, off-site tools (which could violate user privacy), and so on. The entire idea is to make it so that fewer people have those rights, so if a hacker is able to take over an admin account, they can't do as much damage as they could if they were able to edit those JS/CSS pages. Also, out of the current 14 admins, only 5 have edited pages in the MediaWiki namespace within the last year, so the majority of admins have shown no need for the ability to edit those. If they should get the need to do it regularly, they can request interface admin rights, if they only need it for one-off things, they can request an edit by an interface administrator just like any other user. Jon Harald Søby (talk) 11:00, 28 August 2018 (UTC)
As far as I'm concerned, any admin who has edited MediaWiki pages regularly in the past should just be given this flag once requested. --Ooswesthoesbes (talk) 12:00, 28 August 2018 (UTC)

Enable translate extension?[edit]

Hi folks, I would like to suggest enabling the translate extension here on oldwikisource. It would make it much easier to translate pages in the Wikisource namespace, like policies and guidelines. It is already in use on many major Wikimedia projects, like Wikidata, Meta and Wikimedia Commons, and is a well-tested and stable piece of software that I think would have the potential to improve this project. What do you think? Jon Harald Søby (talk) 22:58, 5 August 2018 (UTC)

Symbol support vote.svg Support I think it may be a good idea. However, two problems: (1) we may have not many users able to manage translations and (2) some languages used here may be not supported by wiki software (eg. gbm on this page). Ankry (talk) 05:46, 6 August 2018 (UTC)
@Ankry: (1) It's not very difficult after a bit of practice, and for a small project like this the workload wouldn't be unbearable for even one or two people. (2) That should be adressed, but it is quite an easy fix. Do you know if there is a comprehensive list of languages used here somewhere? Jon Harald Søby (talk) 12:23, 6 August 2018 (UTC)
@Jon Harald Søby: I am afraid most users here edit accidentally only, so no chance for practice :( And I think most languages used here are languages without subdomain (eh. Khmer, Hindi, Mingrelian, Urdu). I am afraid it will be hard to find translators. I also think of possibility tu use this extension to translate some common templates ({{header}}.{{Author}}, {{disambig}}) as I encoutered needs for multilingual pages that use them. And also documentation for basic templates like eg. {{rh}} or {{gesperrt}}. Ankry (talk) 13:16, 6 August 2018 (UTC)
@Ankry: I was thinking more of the "translation admin" side, that's what can be a bit confusing at first. Translation itself is easy-peasy, anyone can do it with minimal prerequisites (the only thing being that you need to know basic wiki syntax, but that goes for pretty much anything around here). When there is a call for translation on page, it's very easy to get started – I myself have translated many pages that I wouldn't have thought to do otherwise just because it was possible (and easy!). And yes, the extension can indeed be used for those cases you mention! Jon Harald Søby (talk) 13:32, 6 August 2018 (UTC)
Neutral. I have no valid reason to oppose this, but I also believe it isn't going to be used that much. --Ooswesthoesbes (talk) 09:52, 6 August 2018 (UTC)
@Ooswesthoesbes: Aye, but that's not necessarily a problem. I'm thinking it would be useful for meta pages, the ones that tell users how to get started. And since this is sort of the Incubator for languages that don't have Wikisources yet, I believe it would be useful to have that information in more languages than just English. Jon Harald Søby (talk) 12:23, 6 August 2018 (UTC)
Support Altho I agree that in fact, there will be very little translating actually done, this is an ideal wiki for the extension. Good thinking, Jon. —Justin (koavf)TCM 07:30, 8 August 2018 (UTC)
Symbol support vote.svg Support --Zyephyrus (talk) 07:59, 8 August 2018 (UTC)
Symbol support vote.svg Support though I don't know whether it is needed right now, but in future seems to be useful. --Nigmont (talk) 00:16, 12 August 2018 (UTC)
Thanks folks! Since it has been a week since the suggestion and no objections, I've created a task and a patch to add the Translate extension here. :-) Jon Harald Søby (talk) 09:46, 13 August 2018 (UTC)
Very good! :) --Ooswesthoesbes (talk) 11:24, 13 August 2018 (UTC)
And now it has been deployed. :-) For it to be used though, we need some translation administrators who can mark pages for translation (bureaucrats can assign that right). I'll fill out a request for it for myself on Wikisource:Administrators. :-) Jon Harald Søby (talk) 12:19, 13 August 2018 (UTC)

Tech News: 2018-32[edit]

19:39, 6 August 2018 (UTC)

Tech News: 2018-33[edit]

17:53, 13 August 2018 (UTC)

Tech News: 2018-34[edit]

16:46, 20 August 2018 (UTC)

Enable arbitrary Wikidata access for oldwikisource[edit]

Hi again, folks! I think it would be a good idea to enable what's called arbitrary Wikidata access for this wiki. This means that one can build modules that pull information from Wikidata to be used here. I am working on Module:Interwiki, which would let you put {{Interwiki|qid=Q16503}} on this very page to get the interlanguage list on the left. However, since arbitrary access isn't enabled here yet, the module doesn't work. I think this could also be useful for many other uses as well (for example infoboxes on author pages), so therefore I would like to ask you to support this proposal. Jon Harald Søby (talk) 14:28, 22 August 2018 (UTC)

Symbol support vote.svg Support Absolutely! Candalua (talk) 14:48, 22 August 2018 (UTC)
Symbol support vote.svg Support --Ooswesthoesbes (talk) 18:43, 22 August 2018 (UTC)
Symbol support vote.svg Support If mul.ws links can't be included in d: yet, at the very least we can include them locally thru the module. Good thinking again, Jon. —Justin (koavf)TCM 00:06, 23 August 2018 (UTC)
Symbol support vote.svg Support, looks very good for me too. --Nigmont (talk) 21:02, 23 August 2018 (UTC)
Symbol support vote.svg Support Ankry (talk) 15:41, 27 August 2018 (UTC)
Symbol support vote.svg Support--Jusjih (talk) 00:14, 28 August 2018 (UTC)

This change has now been put in place (thanks, Amir!), and I got the Interwiki module working and have put it on this page. This change also enables us to create automatic infoboxes for authors, for instance, using data from Wikidata. Jon Harald Søby (talk) 12:50, 8 November 2018 (UTC)

New Phab task for mul.ws subdomain[edit]

Please see and comment there. —Justin (koavf)TCM 00:13, 23 August 2018 (UTC)

And this, too. —Justin (koavf)TCM 03:32, 25 August 2018 (UTC)

Editing of sitewide CSS/JS is only possible for interface administrators from now[edit]

(Please help translate to your language)

Hi all,

as announced previously, permission handling for CSS/JS pages has changed: only members of the interface-admin (Interface administrators) group, and a few highly privileged global groups such as stewards, can edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage). This is done to improve the security of readers and editors of Wikimedia projects. More information is available at Creation of separate user group for editing sitewide CSS/JS. If you encounter any unexpected problems, please contact me or file a bug.

Thanks!
Tgr (talk) 12:40, 27 August 2018 (UTC) (via global message delivery)

Tech News: 2018-35[edit]

16:16, 27 August 2018 (UTC)

Setting languages of pages[edit]

Since we now have mw:Extension:Translate, I've changed the page information for several pages to correspond to the correct language. On my talk, another user suggested that setting author pages to a particular language may not be a good idea. In retrospect, I think maybe setting them to mul may be best since the interface on an author page should be multilingual. What do others think? —Justin (koavf)TCM 17:18, 2 September 2018 (UTC)

Symbol support vote.svg Support the idea.--Jusjih (talk) 04:37, 9 September 2018 (UTC)

Tech News: 2018-36[edit]

16:47, 3 September 2018 (UTC)

Read-only mode for up to an hour on 12 September and 10 October[edit]

13:33, 6 September 2018 (UTC)

Tech News: 2018-37[edit]

22:35, 10 September 2018 (UTC)

Vandalism[edit]

For admins: please take care and keep watching at least for the main pages of the Wikisource, since in the recent time some vandal: User:185.232.31.100, has vandalized some main pages. I reverted those vandal edits, but the vandal should be prevented from doing the same. --Nigmont (talk) 02:47, 15 September 2018 (UTC)

Semi-protected Main Page/Bahasa Melayu, Main Page/Afrikaans and Wikisource:Armâneascâ. Please go to Wikisource:Protection requests for any follow up.--Jusjih (talk) 02:42, 18 September 2018 (UTC)

Tech News: 2018-38[edit]

21:58, 17 September 2018 (UTC)

IP vandal creating bad user and talk pages[edit]

Could an admin deal with 2607:FB90:54A9:200A:A13D:D345:383E:EFB5 and delete all their page creations? Thanks! Graham87 (talk) 07:37, 23 September 2018 (UTC)

@Graham87: Blocked, nucked, reported to stewards. Thanks for the report and sorry for delay. Ankry (talk) 09:21, 23 September 2018 (UTC)

Tech News: 2018-39[edit]

15:23, 24 September 2018 (UTC)

Tech News: 2018-40[edit]

17:35, 1 October 2018 (UTC)

Words hyphenated across pages in Wikisource are now joined[edit]

Hi everybody. I forgot to include this site in the mass-message that was sent about this change, so I'm now copy-pasting it here:

The ProofreadPage extension can now join together a word that is split between a page and the next.

In the past, when a page was ending with "concat-" and the next page was beginning with "enation", the resulting transclusion would have been "concat- enation", and a special template like d:Q15630535 had to be used to obtain the word "concatenation".

Now the default behavior has changed: the hyphen at the end of a page is suppressed and in this case no space is inserted, so the result of the transclusion will be: "concatenation", without the need of a template. The "joiner" character is defined by default as "-" (the regular hyphen), but it is possible to change this. A template may still be needed to deal with particular cases when the hyphen needs to be preserved. --Candalua (talk) 08:10, 2 October 2018 (UTC)

I would propose to use ­ as the joiner character instead of a normal hyphen – that is called a "soft hyphen", and is used as a marker for where words should be split in case they are too long to fit on a line. Semantically I think that would be a bit more correct than just the normal hyphen. Jon Harald Søby (talk) 14:36, 19 October 2018 (UTC)
I think that using ­ here is unnecessary complication, especially for users entering the text:
  • The character is finally removed in main namespace, so at this point it is technically irrelevant what character is used
  • Entering binary version of ­ (not the &-s-h-y-; 5-character HTML entity) may be a bit complicated
  • I am not sure whether the ­ 5-character HTML entity can be even used as joiner, technically
  • Even if the above is possible, I do not think that both versions: binary and the HTML entity ­ could be used interchangeably here (note: - cannot be used here instead of - now)
  • This is not a big difference for displaying at the end of page in the Page namespace. However, only at this point the above note concerning correctness is indeed valid. The disappearing-in-the-middle-of-line function of the ­ will not be used here as the joiner will appear only at the end of last page line.
Summarizing, I think disadvantages predominate here. Ankry (talk) 07:11, 21 October 2018 (UTC)

Bot status for JhsBot[edit]

Hi, I'd like to request bot status for my bot, JhsBot. It uses the normal Pywikibot framework, and I will use it to fix various things in "my areas". However, I have ben running the bot for more than 10 years, so if there are other bot tasks that need doing, I'm more than willing to help in other areas too (as long as I know how). Jon Harald Søby (talk) 10:57, 2 October 2018 (UTC)

Yes check.svg Done --Ooswesthoesbes (talk) 15:29, 19 October 2018 (UTC)

Tech News: 2018-41[edit]

23:38, 8 October 2018 (UTC)

Tech News: 2018-42[edit]

22:40, 15 October 2018 (UTC)

Tech News: 2018-43[edit]

23:11, 22 October 2018 (UTC)

Tech News: 2018-44[edit]

20:09, 29 October 2018 (UTC)

Tech News: 2018-45[edit]

17:29, 5 November 2018 (UTC)

mul.ws is confusing[edit]

See this thread on the en.ws Scriptorium: "I see, thanks for the explanation very much, now I understand it better. The biggest problem I see with this site is that it was necessary to explain it at all, as the reader does not get this information on the main page and in fact I did not find it even after quite a long time of searching. I was not able to find any page explaining the system of the site, its rules, anything. As a reader I am directed to various single-language sites and do not get the information that multi-lingual works can be found there and how/where I can find them. So I got the impression that adding there some work is like throwing it into a black hole :-( --Jan Kameníček (talk) 07:20, 20 October 2018 (UTC)" We should really fix this via revamping the main page. Thoughts? —Justin (koavf)TCM 23:18, 7 November 2018 (UTC)

We can't do an awful lot to the main page as it has to be in sync with the portals of www.wikipedia.org, www.wiktionary.org etc.
Instead, we could make sure the help pages are actually helpful. --Ooswesthoesbes (talk) 09:48, 8 November 2018 (UTC)
Please note, that if a multilingual book can be split into separate single-language parts, publishing appropriate parts in various single-language wikisources is an alternative and commonly utilized way to present such books. It is likely that readers do not know that the book is multilingual why searching for the texts and making the content easier to find for readers is a strong argument. Few examples of books that are done this way:
Ankry (talk) 11:08, 8 November 2018 (UTC)

Tech News: 2018-46[edit]

19:22, 12 November 2018 (UTC)

Change coming to how certain templates will appear on the mobile web[edit]

CKoerner (WMF) (talk) 19:35, 13 November 2018 (UTC)

For boldest users...[edit]

While working again a little bit in nap pages, I'm updating a personal "maxi-gadget", that emulates many of itwikisource editing tools. Consider that is a tool designed mainly to help and fasten nsPage edits, and that it is poorly documented, being mainly for personal use; it doesn't manages but latin languages; but if any of you would like to test it.... simply add importScript("User:Alex_brollo/common.js"); into your User:UserName/common.js and (prudently!) go. --Alex brollo (talk) 18:11, 14 November 2018 (UTC)

Grazie! —Justin (koavf)TCM 22:56, 14 November 2018 (UTC)
Some doc about that tool (in Italian) here: User:Alex brollo/BAT man. By now, it implements too "eis", the Edit In Sequence itwikisource environment (briefly quoted into Community Wishlist Survey 2019). Alex brollo (talk) 06:57, 15 November 2018 (UTC)
@Koavf, Ruthven: Update I'm very frustrated, I found that "add importScript("User:Alex_brollo/common.js");" doen't run for some users (while it runs into my secondary test user User:Alex brollo bis). I'm trying to fix the bug. --Alex brollo (talk) 17:38, 17 November 2018 (UTC)
Hm. Not sure why that is/isn't working myself. Does copy/paste of the raw code work? —Justin (koavf)TCM 17:41, 17 November 2018 (UTC)
I logged in with my bot account User:BrolloBot; the trick "add importScript("User:Alex_brollo/common.js");" didn't run; copying the whole page User:Alex brollo/common.js into User:BrolloBot/common.js runs! I don't understand why, but it runs. So, try too to copy the whole User:Alex brollo/common.js into your personal common.js subpage; if it runs, you'll see a long list of small buttons at the bottom of the page. They are edit buttons, but their appearance in view mode too isn't a mistake :-) --BrolloBot (talk) 17:50, 17 November 2018 (UTC)
@Alex brollo: unsure if this is the case, but maybe related: while testing some gadgets I noticed that user/common.js changes sometimes take effect after many hours. Probably due to some caching issues, probably unrelated to local browser cache. I did not observe such issues with gadgets. Maybe it is worth to convert your code to a gadget, or a set of gadgets? Ankry (talk) 02:23, 18 November 2018 (UTC)
@Alex brollo: I think that I've solved. In my case, the issue was with the way I'd written my PersonalButtons. I do upload the the javascript with mw.loader.load('/w/index.php?title=User:Alex_brollo/common.js&action=raw&ctype=text/javascript' );. Cheers, Ruthven (talk) 10:55, 18 November 2018 (UTC)
@Ankry, Ruthven: First, thanks for your interest and help. I'll try to convert deprecated importScript() into mw.loader.load; presently I haven't admin nor interface admin privileges here, so I can't create or edit gadgets. The recent implementation of User:Alex brollo/eis.js is just a test, and needs to be rethought by scratch. It's a little bit frustrating to document an "alpha tool", things change fastly into it, but I'll try. --Alex brollo (talk) 08:30, 19 November 2018 (UTC)
@Alex brollo: I am not bureaucrat here, but I think this would not a problem to receive interface-admin rights if you need that. Ankry (talk) 09:41, 19 November 2018 (UTC)
 : @Ankry: Thanks but... I feel myself more and more dissatisfied about the quality of my developer skills, so I will not ask for interface-admin rights; I prefer to edit my personal js pages. Alex brollo (talk) 21:33, 19 November 2018 (UTC)

Vandal 2001:56a:76ec:e800:e0ae:62c5:d3ce:6c10[edit]

I don't know how to report vandalism. Could an administrator please review possible vandalism by 2001:56a:76ec:e800:e0ae:62c5:d3ce:6c10 Link to contributions

  • editing existing page in bad faith to link to the same creations [61]
  • deleting I placed on one of the nonsense pages [62]

Apt-ark (talk) 04:39, 16 November 2018 (UTC)

Yes check.svg Done Reviewed. Deleted. Blocked. Ankry (talk) 06:30, 16 November 2018 (UTC)

Tech News: 2018-47[edit]

23:28, 19 November 2018 (UTC)

Adding Cosmoglotta[edit]

Hello,

I am looking for some feedback before importing a magazine written from the 1920s to around 1950. It's called Cosmoglotta and is written mostly in the planned language Occidental (Interlingue), but includes a number of other languages as well from time to time. The Austrian National Library hosts it here:

http://anno.onb.ac.at/cgi-content/anno-plus?aid=e0g

http://anno.onb.ac.at/cgi-content/anno-plus?aid=e0m&size=45

Each year is around 100 pages. Cosmoglotta at its height was 12 pages per issue, one issue per month, so many years have exactly 144 images. Also for a number of years it published two versions of the magazine, which is why there are two links.

Image quality varies from very good to fairly blurry such as this one:

http://anno.onb.ac.at/cgi-content/anno-plus?aid=e0m&datum=1945&page=26&size=45

Since it's multilingual that should solve where to put it (here on the multilingual WIkisource). I have two questions:

1) Importing the images: is one at a time best? The closest thing the library site has to displaying all pages on one screen is this: http://anno.onb.ac.at/cgi-content/anno-plus?aid=e0g&datum=1922&pos=1&size=45 But I don't think that'll be enough. I have no problem with doing them one at a time though.

2) Two orthographies. The orthography and vocabulary changed somewhat between the years 1922 and 1947, the latter date when it took on its current form. Also for a number of years, especially during WWII, it was put together on a pretty shoestring budget with a typewriter and so has a number of typos here and there. I would ideally like to type up two versions: 1) the way it was originally printed, and 2) the cleaned up, modernized version. The difference is not great, but since nobody speaks Occidental as a native language it's important to not confuse anyone wanting to learn it or trying to decipher it (e.g. if the spelling is off it may not show up in a dictionary).

All in all it's about 3000 to 3500 pages. I would start with Cosmoglotta B which goes from 1935 to 1947, as that is when the most work was put into cleaning up the language, and also due to the period's historical importance (Cosmoglotta A did not publish during the war).

Mithridates (talk) 03:34, 22 November 2018 (UTC)

Hi @Mithridates:, I see that lots of Cosmoglotta fascicles have already been uploaded into archive.org, here the results of a first search: https://archive.org using creator:"Societé Kosmoglott" into search field.
I think that mulwikisource is the best project to upload multilingual works, please try the tool https://tools.wmflabs.org/ia-upload/ that often runs even if IA item haven't a djvu file.
The project is a hard one, so my suggestion is to begin with a "diplomatic" (as it has been printed) version; there are possible tricks to write an alternative modernized version into the same nsPage page, but I feel that a simple diplomatic version is the best strategy to begin such a large work. Alex brollo (talk) 09:26, 22 November 2018 (UTC)
Thank you, that tool is exactly what I was looking for. I see on Archive.org they have Cosmoglottas up to 1939, after which only very few changes were made. So I can just type out the 'diplomatic' version as you said and in the end it will be at least 99% the same as the modern version. I'll start with the 1939 issues, and even that one year will take a very long time. The tool seems to have worked well: https://wikisource.org/wiki/Index:Cosmoglotta_A_128_(Sep-Dec_1939).djvu Mithridates (talk) 11:47, 22 November 2018 (UTC)
@Mithridates: I took the opportunity to import here an itwikisource successful gadget using CropTool. While editing nsPage, it adds a "CropTool" link to Tools list into sidebar, and a button Pulsante img.png into Advanced section of toolbox. The former opens CropTool for current page, the latter inserts a draft code for cropped image using the default file name suggested by CropTool. I tested the script into page 1 of your new Index. If you like, the code for that script is into User:Alex brollo/vector.js, you can test it simply copying the code into yours User:Mithridates/common.js. I hope that it will run for you too. :-) Alex brollo (talk) 13:20, 22 November 2018 (UTC)
@Alex brollo: Ah, took me about five minutes to see what exactly you were referring to but I see it now. Cosmoglotta is full of those hand-drawn images and diagrams so that should help a lot. Thanks again! Mithridates (talk) 14:21, 22 November 2018 (UTC)
@Alex brollo: So today I noticed somebody has added a few pages and also included a SIC tag to indicate where the spelling has changed. I gave that a try on page 8 and it seems to be a good solution to indicate where the spelling has changed. In a single page I ended up using it five times, which is not too much: Illa-ella, antiqualya-antiquallia, femina-fémina, ley-lege, analysat-analisat. Mithridates (talk) 01:12, 23 November 2018 (UTC)
@Mithridates: Maybe this is a stupid question, but why do you think that the magazines are PD (in US in case of this project)? It is clear that 1922 volumes are PD and 1923 ones will be PD in January. But others? is there a specific exclusion in Swiss copyright law that made them PD in Switzerland in 1996? Being available in a digital library does not automatically mean that they are PD. They may be available under Fair Use or some limited permission (like non-commercial ones). Ankry (talk) 22:19, 22 November 2018 (UTC)
@Ankry: Not a dumb question. I wonder if the tool automatically selected PD? Either that or I did without looking closely when doing the upload. Let's see...anything by Edgar de Wahl (the creator of the language) will definitely be PD as he has been dead for exactly 70 years now (died in Tallinn in 1948), but Cosmoglotta was mostly written by others, some of whom like Berger and Matejka died in the 1980s and 1990s. The Interlingue-Union (previously the Occidental-Union) exists today though I think it might have been dissolved at once point when so many Occidentalists made the exodus to Interlingua...also the magazine often used letters to the editor and translated content from other languages that came from who knows where. The library itself has the standard disclaimer that (paraphrasing) "we are making this content available for historical reasons but that doesn't mean we are asserting them to be PD". So I think we both agree that full PD isn't claimable here. Should I just change it to CC BY-SA 3.0? Mithridates (talk) 00:40, 23 November 2018 (UTC)
@Mithridates:I see no evidence for CC BY-SA 3.0 license (this has to be explicitely declared by copyright owners to be valid). 70 pma may be also irrelevant here, as in US, for pre-1978 published works copytight is based on publication date, and lasts 95 years unless it falls under some special cases. One of the cases may be, that the work was PD in 1996 in the initial publication country (Switzerland, I assume). So the question is, when did Swiss copyright to these publications expire? (50 years after publication? 50/70 pma?) Ankry (talk) 02:10, 23 November 2018 (UTC)
@Ankry: I see. The library itself (should mention this is the Austrian library - Cosmoglotta was based in Vienna, although Cosmoglotta B was published in Switzerland) seems have kind of been winging it on copyright since the project started over 10 years ago: http://anno.onb.ac.at/faq.htm They say they are not asserting that any of the newspapers there are free of copyright, and that they choose to scan works that are in particularly bad condition, so journals that are on the verge of outright disappearing anyway. I remember an Occidentalist back in 2007 or so before they were scanned who had managed to get his hands on a few issues, and that was big news at the time. What sort of copyright applies here when we are in a "some is definitely PD, some may not be, and in the meantime the copyright owners have more or less let their material rot" situation? Some sort of fair use claim for the sake of preservation? Mithridates (talk) 02:31, 23 November 2018 (UTC)
@Mithridates, Ankry: What's a pity, this licence-related issue! It's a very complex and critical one and I can't help you. Our itwikisource policy is, to discuss it into Commons, and to accept Commons's decision. Nevertheless, thanks for opportunity of importing here too the CropTool stuff, I hope it will turn out useful for other users/other works. Alex brollo (talk) 07:19, 23 November 2018 (UTC)
@Mithridates: I think, you can safely upload the 1922 volumes, and in few weeks the 1923 volumes. The rest should wait for subsequent years or till their Swiss copyright status is resolved. As I do not know German/French/Italian/Rumansch I cannot help you in the latter. Their Swiss copyright may be based on publication date (50 yers) and may be not extended by newer copyright law. But we need an explicit clause either from Swiss copyright law or from some legal opinion by Swiss lawyers for that. Also, as the Swiss copyright is unclear, I suggest to upload the volumes here, and not to Commons (Commons require files to be PD in US and in the country of origin; Wikisource accepts works that are PD in US regardless of their copyright status in the country of origin). Everything published more than 95 years ago (before 1.1.1923 now, and before 1.1.1924 in Jan 2019) is PD in US. Ankry (talk) 08:31, 23 November 2018 (UTC)
@Ankry: Just to clarify, this is mostly Austrian copyright law as that's where most of them were published. (Swiss is involved too, but mostly Austria) I just sent an email to the library to get an opinion on this and will let you know if I get a reply. If it's only 1922 and 1923 that would be a shame, as that's when the magazine was a real hodge-podge of languages and the Occidental is a bit dated, so much less value to the community there. I was planning to do those years right at the end. Mithridates (talk) 08:41, 23 November 2018 (UTC)

User talk page[edit]

I need someone to indefinitely semi-protect my user talk page on this project, please. Thank you. Drmies (talk) 23:40, 25 November 2018 (UTC)

Yes check.svg Done Ankry (talk) 00:21, 26 November 2018 (UTC)

Advanced Search[edit]

Johanna Strodt (WMDE) (talk) 11:03, 26 November 2018 (UTC)

Tech News: 2018-48[edit]

22:22, 26 November 2018 (UTC)

Congratulazioni to Napulitano[edit]

Main Page/Napulitano has been approved to graduate to its own domain. See phab:T210752. —Justin (koavf)TCM 17:15, 29 November 2018 (UTC)

That is great news! :) --Ooswesthoesbes (talk) 13:38, 1 December 2018 (UTC)
It's by far our largest collection here and very active. —Justin (koavf)TCM 21:48, 1 December 2018 (UTC)
Congrats from me as well! -jkb- (talk) 16:51, 8 December 2018 (UTC)
Congratulations from me too! (I'm sorry that I saw this topic only recently and hadn't noticed it before, thus I hadn't respond quickly and I am commenting only just now). And I feel some pity that the Neapolitan project hadn't been approved much earlier, since, in my opinion, it for a long time had already deserved that approvement. As well I wish good luck to all the contributors to Napulitano! --Nigmont (talk) 01:28, 9 December 2018 (UTC)

Tech News: 2018-49[edit]

16:12, 3 December 2018 (UTC)

Selection of the Wikisource Community User Group representative to the Wikimedia Summit[edit]

Dear all,

Sorry for writing in English and cross-posting this message.

The Wikisource Community User Group could send one representative to the Wikimedia Summit 2019 (formerly "Wikimedia Conference"). The Wikimedia Summit is a yearly conference of all organizations affiliated to the Wikimedia Movement (including our Wikisource Community User Group). It is a great place to talk about Wikisource needs to the chapters and other user groups that compose the Wikimedia movement. For context, there is a short report on what happened last year. The deadline is short and to avoid the confusing vote on the Wikisource-I mailing list of last year, we created a page on meta to decide who will be the representative of the user group to the Wikimedia Summit.

The vote will be in two parts:

  1. until December 7th, people can add their name and a short explanation on who they are and why they want to go to the summit. Nomination of other people is allowed, the nominated person should accept their nomination.
  2. starting December 7th, and for a week, the community vote to designate the representative.

Please feel free to ask any question on the wikisource-I mailing list or on the talk page.

For the Wikisource Community User Group, Tpt (talk) 15:15, 5 December 2018 (UTC)

New Wikimedia password policy and requirements[edit]

CKoerner (WMF) (talk) 20:03, 6 December 2018 (UTC)

Wikisource Community User Group representative vote[edit]

Dear all,

Sorry for writing in English and cross-posting this message.

Following the previous message, the vote for the representative of the Wikisource Community User Group to the Wikimedia Summit 2019 is now open.

There is two great candidates on page on meta to decide who will be the representative of the user group to the Wikimedia Summit. You can support a candidate now. All active Wikisource users can vote. The vote is ending on December 14, 2018.

Feel free to ask any question on the wikisource-I mailing list or on the talk page.

Thank you!

For the Wikisource Community User Group, Tpt (talk) December 8, 2018 at 18:53 (UTC)

Tech News: 2018-50[edit]

17:33, 10 December 2018 (UTC)