Jump to content

Wikisource:Scriptorium/Archives/2023

From Wikisource

Tech News: 2023-02

[edit]

MediaWiki message delivery 01:07, 10 January 2023 (UTC)[reply]

Tech News: 2023-03

[edit]

MediaWiki message delivery 01:10, 17 January 2023 (UTC)[reply]

Tech News: 2023-04

[edit]

MediaWiki message delivery 23:46, 23 January 2023 (UTC)[reply]

Tech News: 2023-05

[edit]

MediaWiki message delivery 00:05, 31 January 2023 (UTC)[reply]

Tech News: 2023-06

[edit]

MediaWiki message delivery 10:21, 6 February 2023 (UTC)[reply]

Trolling all around

[edit]

So this well known LTA troll (either Wikinger or What's-his-name) found one obscure WMF project where he is not yet banned and defaced my (thitherto non-existing) talk page to insult me: Apparently for the crime of not sharing this troll’s wrong views on pre-Classic Greek letters a few years ago (!), it’s cool to accuse me of c.p. while pinging Jimbo about it (unsuccessfully pinging, that is, for lack of the necessary brackets). So, I want to replace this nonsense with a blank page.

But the really clever system in place here in Wikisource, the system that just allowed an IP account to create anew someone’s talk page and let it be added explicit mentions of c.p., has this to say when a user tries to blank their own talk page:

This action has been automatically identified as harmful, and therefore disallowed. If you believe your action was constructive, please inform an administrator of what you were trying to do. A brief description of the abuse rule which your action matched is: don't create empty pages

And to this I have a few choice words myself, but better not add them here, for that too may be harmful. Tuvalkin (talk) 09:38, 8 February 2023 (UTC)[reply]

@Tropicalkitty: Thanks for reverting this sad, sad troll in my talk page. Is there a way of protecting it and/or blocking these IPs? And more generally, shouldn’t there be in place some sort of policy or filter to be triggered when someone, especially an unlogged user, add a mention to c.p. in a new edit? Tuvalkin (talk) 09:28, 13 February 2023 (UTC)[reply]
Maybe Koavf or another Wikisource administrator could fulfill this request at their discretion. I don’t have sufficient permissions on Wikisource to perform blocks or protections in your user space, sorry. Tropicalkitty (talk) 20:35, 13 February 2023 (UTC)[reply]
Deleted and protected. Sorry that I didn't see this earlier: I've been very active on en.wp lately and have ignored responsibilities on other WMF wikis. —Justin (koavf)TCM 20:45, 13 February 2023 (UTC)[reply]

Edit disallowed as spam

[edit]

Hello,

I just attempted to create a new topic in Talk:Rolls Series but my edit was automatically disallowed as spam. I have fifteen years of activity and hundreds of edits on various Wikimedia projects, mainly English Wikipedia. My edit isn't spam. (Nor is it self-promotion, as I have nothing to do with "Links Galore" or its author.) Please permit the edit. RW Dutton (talk) 20:32, 11 February 2023 (UTC)[reply]

Thanks for allowing this. RW Dutton (talk) 21:44, 11 February 2023 (UTC)[reply]

Tech News: 2023-07

[edit]

MediaWiki message delivery 01:48, 14 February 2023 (UTC)[reply]

Semi-protection request

[edit]

Hi. Please semi-protect my user talk page User talk:Jeff G., as the IP vandalism has gotten out of hand. Thanks in advance! Jeff G. (talk) 11:39, 14 February 2023 (UTC)[reply]

DoneJustin (koavf)TCM 23:49, 14 February 2023 (UTC)[reply]

Weird categorizing in "Pages transcluding nonexistent sections"

[edit]

I have noticed that recently some pages are added into category (auxiliary I guess) Category:Pages transcluding nonexistent sections (not created yet). For example, articles and main pages of newspaper "Yakstere teshte" created by me: Якстере теште/1924/05, Якстере теште/1924/05/Газета тест аэряви. I think there is something wrong with this categorising because actually these pages don't use transcluding nonexistent sections. Moreover, some other pages of the same newspaper are not included in that category: e.g. page Якстере теште/1924/05/Лия масторга and others. Can someone comment on this categorization?

The English Wikisource seemingly also encountered this event, and it has recently created. @Tpt:: you created this category in the English WS — maybe you know: is something broken with that? Will it be fixed soon? --Nigmont (talk) 12:21, 18 February 2023 (UTC)[reply]

This is a tracking category, which collects pages that use LabeledSectionTransclusion is used incorrectly – but it currently collects also pages where it’s used correctly (see phab:T329432). Since the category itself will probably remain, I think it can be created, even if no pages it currently contains are indeed broken, and therefore it may get empty when the bug is fixed – it just needs an {{empty category}} tag. —Tacsipacsi (talk) 22:27, 18 February 2023 (UTC)[reply]
Yes, there is currently a bug adding correct usages to the category. A change that should fix this problem will be deployed on Wednesday. Sorry for that. Tpt (talk) 09:01, 20 February 2023 (UTC)[reply]

Tech News: 2023-08

[edit]

MediaWiki message delivery 01:57, 21 February 2023 (UTC)[reply]

Community feedback-cycle about updating the Wikimedia Terms of Use starts

[edit]
You can find this message translated into additional languages on Meta-wiki.

Hello everyone,

Wikimedia Foundation Legal Department is organizing a feedback-cycle with community members to discuss updating the Wikimedia Terms of Use.

The Terms of Use (ToU) are the legal terms that govern the use of websites hosted by the Wikimedia Foundation. We will be gathering your feedback on a draft proposal from February through April. The draft will be translated into several languages, with written feedback accepted in any language.

This update comes in response to several things:

  • Implementing the Universal Code of Conduct
  • Updating project text to the Creative Commons BY-SA 4.0 license
  • Proposal for better addressing undisclosed paid editing
  • Bringing our terms in line with current and recently passed laws affecting the Foundation, including the European Digital Services Act

As part of the feedback cycle two office hours will be held, the first on March 2, the second on April 4.

For further information, please consult:

On behalf of the Wikimedia Foundation Legal Team, --AAkhmedova (WMF) (talk) 12:59, 22 February 2023 (UTC)[reply]

Pseudonym

[edit]

How should I deal with works published under a pseudonym? See Author:Л._Савельев and Koht_jemne_mil̦t_vьjet. --Rießler (talk) 09:10, 27 February 2023 (UTC)[reply]

To use an example from en.ws, if someone exclusively wrote under a penname and we know that person's actual identity (e.g. Eric Arthur Blair was "George Orwell" and Samuel Clemens published as "Mark Twain"), we use the penname. If someone wrote under a variety of pseudonyms or used one-off names (e.g. Søren Kierkegaard published under a half-dozen pseudonyms), then we use that person's proper name. So, if this is a one-off, I'd use his real/legal name and make a redirect from the pseudonym. —Justin (koavf)TCM 19:13, 27 February 2023 (UTC)[reply]
Thank you very much! --Rießler (talk) 15:08, 3 March 2023 (UTC)[reply]
Also check w:List of countries' copyright lengths while pseudonymous works tend to get regular copyright terms if the identity of the pseudonym is well known.--Jusjih (talk) 03:01, 4 December 2023 (UTC)[reply]

DjVu

[edit]

http://urn.fi/URN:NBN:fi-fe2016050411419 includes a PD work, partly in Kildin Sami language and partly in Akkala Sami, which I would like to transcribe in Wikisource. The OCR done on this document is already very accurate. I'm afraid that this accurate OCR is destroyed if I convert to DjVu. --Rießler (talk) 12:07, 27 February 2023 (UTC)[reply]

Or perhaps someone can help me to create the relevant pages here, for me to proofread? --Rießler (talk) 12:18, 27 February 2023 (UTC)[reply]

Here the PDF: https://commons.wikimedia.org/wiki/File:Махьтвеест_Пась-Евангели_–_Самас.pdf --Rießler (talk) 14:09, 27 February 2023 (UTC)[reply]

Hello, @Rießler: It is not required to convert a PDF scan file to DjVu, you can use a PDF for proofreading if you want, there is no problem with that. You may use any of those formats as you prefer. Also, I created an index for that file from the Commons: Index:Махьтвеест Пась-Евангели – Самас.pdf, is that what do you need? I myself work here on adding text in Mordvinic languages (Moksha and Erzya), which are of Finno-Ugric family too, so probably I could do some help to you if you need. --Nigmont (talk) 19:30, 27 February 2023 (UTC)[reply]
Огромное спасибо! Это страница: Page:Махьтвеест_Пась-Евангели_–_Самас.pdf/3 does it look alright? --Rießler (talk) 20:06, 27 February 2023 (UTC)[reply]
I checked the page and found two OCR errors, and fixed; also added {{nop}} at the end of the page, because it is needed when paragraph terminates the page, as explained on the template's documentation page: Template:Nop. The proofread page (Page:Махьтвеест Пась-Евангели – Самас.pdf/3) now looks good, so I marked it as 'Proofread' while saving the edit. --Nigmont (talk) 21:13, 27 February 2023 (UTC)[reply]
Thank you very much for your help! I'll transcribe this work soon, but for testing how this works I've uploaded another work, which is already transcribed locally on my computer and can be added here easily. Look here: Index:Men_antij_Okțaвr_Revolucia_roвtus̷dɘdь_saamit.pdf. However, the original scan from the library had the backcover as frontcover. I noticed this first after creating the project in Wikisource. It is corrected in Commons, but how do I fix this here? --Rießler (talk) 15:08, 3 March 2023 (UTC)[reply]
Sorry, but I don't understand what you mean... Do you mean — that the pages in the file are ordered somewhat wrongly: the back cover page (must be at the end of the file) is currently placed as the 1-st page, and the front cover goes as the 2-nd page? If you mean this, then if you fix the file and change pages' order, and upload a new version (it should be noticed that it hasn't been done yet — the file on the Commons still has that wrong order), then you need to change the pages which you have created here already: page "Page:Men antij Okțaвr Revolucia roвtus̷dɘdь saamit.pdf/2" should become as page "/1", the page "/3" would go as "/2" etc. But if you don't want to upload new version — then you can proofread pages as they are now, without changing their current order. It's rather a question of convenience — is it needed to fix the pages order, would it be easy, or maybe it would be easier to leave them as they are ordered now. --Nigmont (talk) 11:44, 5 March 2023 (UTC)[reply]
Commons has the corrected order, but in Index:Men antij Okțaвr Revolucia roвtus̷dɘdь saamit.pdf I defined page 2 as the cover. I think fixing the pages would be most convenient. Are you admin and can delete current Page:Men antij Okțaвr Revolucia roвtus̷dɘdь saamit.pdf/1? (Don't worry about loosing the transcription, I have it locally.) After this I can move the other pages and insert current page one at the end. --Rießler (talk) 14:15, 5 March 2023 (UTC)I understand this now, sorry for bothering you. --Rießler (talk) 14:54, 5 March 2023 (UTC)[reply]
No, I am not an admin, so I cannot help with moving the pages, sorry. I can move only pages' content by copy-pasting from page to page, but seemingly you have already done that yourselves, so the problem should be solved now. But if there were a lot of pages (hundred or more) to move, then, of course, it would be better to ask admins to run a script to move them automatically, and to wait when some of them does that. --Nigmont (talk) 15:45, 5 March 2023 (UTC)[reply]

Your wiki will be in read only soon

[edit]

Trizek (WMF) (Discussion) 21:21, 27 February 2023 (UTC)[reply]

Tech News: 2023-09

[edit]

MediaWiki message delivery 23:47, 27 February 2023 (UTC)[reply]

Tech News: 2023-10

[edit]

MediaWiki message delivery 23:49, 6 March 2023 (UTC)[reply]

Remove one vandalism

[edit]

Hello,

I tried to remove this vandalism: [30], but a filter (Operator873's Filter) does not allow me to do it. Could a sysop remove the vandalism?

Regards NicoScribe (talk) 11:20, 13 March 2023 (UTC)[reply]

Done by Operator873. Thanks! --NicoScribe (talk) 14:51, 14 March 2023 (UTC)[reply]

Wikimania 2023 Welcoming Program Submissions

[edit]

Do you want to host an in-person or virtual session at Wikimania 2023? Maybe a hands-on workshop, a lively discussion, a fun performance, a catchy poster, or a memorable lightning talk? Submissions are open until March 28. The event will have dedicated hybrid blocks, so virtual submissions and pre-recorded content are also welcome. If you have any questions, please join us at an upcoming conversation on March 12 or 19, or reach out by email at wikimania@wikimedia.org or on Telegram. More information on-wiki.

Tech News: 2023-11

[edit]

MediaWiki message delivery 23:20, 13 March 2023 (UTC)[reply]

Tech News: 2023-12

[edit]

MediaWiki message delivery 01:25, 21 March 2023 (UTC)[reply]

Tech News: 2023-13

[edit]

MediaWiki message delivery 01:13, 28 March 2023 (UTC)[reply]

Tech News: 2023-14

[edit]

MediaWiki message delivery 23:39, 3 April 2023 (UTC)[reply]

Tech News: 2023-15

[edit]

MediaWiki message delivery 20:05, 10 April 2023 (UTC)[reply]

Tech News: 2023-16

[edit]

MediaWiki message delivery 01:54, 18 April 2023 (UTC)[reply]

Your wiki will be in read-only soon

[edit]

MediaWiki message delivery 00:42, 21 April 2023 (UTC)[reply]

Tech News: 2023-17

[edit]

MediaWiki message delivery 22:03, 24 April 2023 (UTC)[reply]

Seeking volunteers for the next step in the Universal Code of Conduct process

[edit]

Hello,

As follow-up to the message about the Universal Code of Conduct Enforcement Guidelines by Wikimedia Foundation Board of Trustees Vice Chair, Shani Evenstein Sigalov, I am reaching out about the next steps. I want to bring your attention to the next stage of the Universal Code of Conduct process, which is forming a building committee for the Universal Code of Conduct Coordinating Committee (U4C). I invite community members with experience and deep interest in community health and governance to nominate themselves to be part of the U4C building committee, which needs people who are:

  • Community members in good standing
  • Knowledgeable about movement community processes, such as, but not limited to, policy drafting, participatory decision making, and application of existing rules and policies on Wikimedia projects
  • Aware and appreciative of the diversity of the movement, such as, but not limited to, languages spoken, identity, geography, and project type
  • Committed to participate for the entire U4C Building Committee period from mid-May - December 2023
  • Comfortable with engaging in difficult, but productive conversations
  • Confidently able to communicate in English

The Building Committee shall consist of volunteer community members, affiliate board or staff, and Wikimedia Foundation staff.

The Universal Code of Conduct has been a process strengthened by the skills and knowledge of the community and I look forward to what the U4C Building Committee creates. If you are interested in joining the Building Committee, please either sign up on the Meta-Wiki page, or contact ucocproject(_AT_)wikimedia.org by May 12, 2023. Read more on Meta-Wiki.

Best regards,

Xeno (WMF) 19:01, 26 April 2023 (UTC)[reply]

Trying to fix typos on Interlingua Wikisource

[edit]

Hello, I am trying to fix some typos on the Interlingua Wikisource, but my edits are considered spam. The message suggests contacting an administrator, and I asked on the Discord channel, and was told to ask here. Eowug (talk) 22:50, 29 April 2023 (UTC)[reply]

Ok, I can edit the page now. Eowug (talk) 23:18, 29 April 2023 (UTC)[reply]

Tech News: 2023-18

[edit]

MediaWiki message delivery 01:45, 2 May 2023 (UTC)[reply]

Global ban proposal for Piermark/House of Yahweh/HoY

[edit]

There is an on-going discussion about a proposal that Piermark/House of Yahweh/HoY be globally banned from editing all Wikimedia projects. You are invited to participate at Requests for comment/Global ban for Piermark on Meta-Wiki. Thank you! U.T. (talk) 12:36, 4 May 2023 (UTC)[reply]

Tech News: 2023-19

[edit]

MediaWiki message delivery 00:36, 9 May 2023 (UTC)[reply]

Is there pdf browser for wikisource

[edit]

When openning pdf in wikisource there are in the screen many things other than the pdf page. is there a Gadget or template to view only pdf pages like Internet Archive? حبيشان (talk) 11:52, 15 May 2023 (UTC)[reply]

You can open PDFs. Most if not all desktop and some mobile browsers (e.g. Firefox for Android) natively support displaying PDFs. Isn’t that sufficient? —Tacsipacsi (talk) 23:05, 16 May 2023 (UTC)[reply]
@Tacsipacsi they are slow when opening a page in the middle of a book or at the end of a book. حبيشان (talk) 08:29, 18 May 2023 (UTC)[reply]

Tech News: 2023-20

[edit]

MediaWiki message delivery 21:45, 15 May 2023 (UTC)[reply]

Request for the Bot-flag

[edit]

I would like to apply for the bot-flag for User:DracoBot. I have to move some pages in the index. suppress-redirect is essential for this task. I run already the bot on the PL-Wikisource (pl:User:DracoBot. Regards Draco flavus (talk) 09:04, 16 May 2023 (UTC)[reply]

If there are any other tasks I can happily help. Draco flavus (talk) 08:17, 18 May 2023 (UTC)[reply]
Support: trusted and technically skilled user; this bot already has a bot flag at plwikisource. Ankry (talk) 17:03, 7 June 2023 (UTC)[reply]
Sorry for the late reaction. Looks good to me :) --Ooswesthoesbes (talk) 17:30, 7 June 2023 (UTC)[reply]

Done -jkb- (talk) 08:17, 10 June 2023 (UTC)[reply]

Tech News: 2023-21

[edit]

16:55, 22 May 2023 (UTC)

Selection of the U4C Building Committee

[edit]

The next stage in the Universal Code of Conduct process is establishing a Building Committee to create the charter for the Universal Code of Conduct Coordinating Committee (U4C). The Building Committee has been selected. Read about the members and the work ahead on Meta-wiki.

-- UCoC Project Team, 04:21, 27 May 2023 (UTC)

This LTA (also known as GRP) is now active at Njet, Molotoff - please protect the page as vandalism, and please revdel the absurd libels. Thanks. --Quangdat201 (talk) 04:41, 28 May 2023 (UTC)[reply]

Done by Koavf --Quangdat201 (talk) 15:15, 29 May 2023 (UTC)[reply]

Vandal

[edit]

See Special:Contribs/KEMONO PANTSU Z. Thanks. Styyx (talk) 21:24, 28 May 2023 (UTC)[reply]

Tech News: 2023-22

[edit]

MediaWiki message delivery 22:03, 29 May 2023 (UTC)[reply]

2001:448A:2022:B44C:D4DB:171A:F24:2080 (talkcontribsglobal contribs): Vandalism --Ameisenigel (talk) 14:51, 31 May 2023 (UTC)[reply]

Vandal 2

[edit]

Hi, see FortressBuilder... Draco flavus (talk) 17:29, 2 June 2023 (UTC)[reply]

Tech News: 2023-23

[edit]

MediaWiki message delivery 22:52, 5 June 2023 (UTC)[reply]

Tech News: 2023-24

[edit]

MediaWiki message delivery 14:51, 12 June 2023 (UTC)[reply]

Tech News: 2023-25

[edit]

MediaWiki message delivery 20:08, 19 June 2023 (UTC)[reply]

Tech News: 2023-26

[edit]

MediaWiki message delivery 16:18, 26 June 2023 (UTC)[reply]

Announcing the new Elections Committee members

[edit]
You can find this message translated into additional languages on Meta-wiki.

Hello there,

We are glad to announce the new members and advisors of the Elections Committee. The Elections Committee assists with the design and implementation of the process to select Community- and Affiliate-Selected trustees for the Wikimedia Foundation Board of Trustees. After an open nomination process, the strongest candidates spoke with the Board and four candidates were asked to join the Elections Committee. Four other candidates were asked to participate as advisors.

Thank you to all the community members who submitted their names for consideration. We look forward to working with the Elections Committee in the near future.

On behalf of the Wikimedia Foundation Board of Trustees,

RamzyM (WMF) 18:00, 28 June 2023 (UTC)[reply]

Tech News: 2023-27

[edit]

MediaWiki message delivery 22:51, 3 July 2023 (UTC)[reply]

Tech News: 2023-28

[edit]

MediaWiki message delivery 19:54, 10 July 2023 (UTC)[reply]

Tech News: 2023-29

[edit]

MediaWiki message delivery 23:08, 17 July 2023 (UTC)[reply]

Tech News: 2023-30

[edit]

MediaWiki message delivery 02:20, 25 July 2023 (UTC)[reply]

Deploying the Phonos in-line audio player to your Wiki

[edit]

Hello!

Apologies if this message is not in your language, ⧼Please help translate⧽ to your language.

This wiki will soon be able to use the inline audio player implemented by the Phonos extension. This is part of fulfilling a wishlist proposal of providing audio links that play on click.

With the inline audio player, you can add text-to-speech audio snippets to wiki pages by simply using a tag:

<phonos file="audio file" label="Listen"/>

The above tag will show the text next to a speaker icon, and clicking on it will play the audio instantly without taking you to another page. A common example where you can use this feature is in adding pronunciation to words as illustrated on the English Wiktionary below.

{{audio|en|En-uk-English.oga|Audio (UK)}}

Could become:

<phonos file="En-uk-English.oga" label="Audio (UK)"/>

The inline audio player will be available in your wiki in 2 weeks time; in the meantime, we would like you to read about the features and give us feedback or ask questions about it in this talk page.

Thank you!

UOzurumba (WMF), on behalf of the Foundation's Language team

02:26, 27 July 2023 (UTC)

Tech News: 2023-31

[edit]

MediaWiki message delivery 23:54, 31 July 2023 (UTC)[reply]

Tech News: 2023-32

[edit]

MediaWiki message delivery 21:20, 7 August 2023 (UTC)[reply]

Tech News: 2023-33

[edit]

MediaWiki message delivery 05:59, 15 August 2023 (UTC)[reply]

Tech News: 2023-34

[edit]

15:25, 21 August 2023 (UTC)

Tech News: 2023-35

[edit]

MediaWiki message delivery 14:00, 28 August 2023 (UTC)[reply]

Review the Charter for the Universal Code of Conduct Coordinating Committee

[edit]

Hello all,

I am pleased to share the next step in the Universal Code of Conduct work. The Universal Code of Conduct Coordinating Committee (U4C) draft charter is now ready for your review.

The Enforcement Guidelines require a Building Committee form to draft a charter that outlines procedures and details for a global committee to be called the Universal Code of Conduct Coordinating Committee (U4C). Over the past few months, the U4C Building Committee worked together as a group to discuss and draft the U4C charter. The U4C Building Committee welcomes feedback about the draft charter now through 22 September 2023. After that date, the U4C Building Committee will revise the charter as needed and a community vote will open shortly afterward.

Join the conversation during the conversation hours or on Meta-wiki.

Best,

RamzyM (WMF), on behalf of the U4C Building Committee, 15:35, 28 August 2023 (UTC)[reply]

Tech News: 2023-36

[edit]

MediaWiki message delivery 23:33, 4 September 2023 (UTC)[reply]

Tech News: 2023-37

[edit]

MediaWiki message delivery 21:07, 11 September 2023 (UTC)[reply]

Your wiki will be in read-only soon

[edit]

Trizek_(WMF) (talk) 09:24, 15 September 2023 (UTC)[reply]

Tech News: 2023-38

[edit]

MediaWiki message delivery 19:19, 18 September 2023 (UTC)[reply]

Tech News: 2023-39

[edit]

MediaWiki message delivery 16:51, 26 September 2023 (UTC)[reply]

IP Masking is comming :-(

[edit]

Some Infos see IP Editing: Privacy Enhancement and Abuse Mitigation (in different languages) with some more pages... -jkb- (talk) 19:08, 2 October 2023 (UTC)[reply]

Tech News: 2023-40

[edit]

MediaWiki message delivery 01:26, 3 October 2023 (UTC)[reply]

A lot of unsourced texts being added on the multilingual Wikisource

[edit]

Currently the multilingual Wikisource has not specific rule(s) which require tagging texts added to the Wikisource with information when and where the text being added was published first (or at least, information about when the current version of the work represented on the page was actually published). I have noticed (long ago) that some users do additions of texts without providing publication data for the works they create and save here. For example, User:Quangdat201 who adds many texts for languages of Russia, but doesn't provide publication information on any texts added by him/her. In my opinion, the multilingual Wikisource should create a rule requiring providing information about publication of the text. At least, it is necessary for texts which are not scan-backed (for text profread from scans it is less needed because publication information can be taken from the scan, though putting publication data on the page in the mainspace would be useful for the scan-backed pages too).

The reasons for such a rule - I tried to describe them on the talk page of User:Quangdat201, anyone can read and know them. Unfortunately, Quangdat201 ignored that my message and even didn't respected me so much to give any answer. And this user still continues adding texts for languages of Russia, recently the user started adding texts for Finno-Ugric languaages, for which I am pretty sure that where exist some works which were published much later than their claimed creating year, so calculating copyright status based on the creation year only (as Quangdat201 does) is wrong and can cause adding works which are actually not out of copyright - that is, the works' pages which are actually copyvios.

In addition to that explanation on the Quangdat201's talk page, I can tell one more consideration. When a user adds a text here, he/she has a book or other source of information from which he/she actually has got the text, and that book must have the needed iformation when and where the work (or the current version of the work represented there) was published, so for the user it shouldn't be a problem to put that information in the header of the page being added, because he/she already has (should have) that information. In the case when user doesn't have that information - in that case he/she cannot be sure that the text is out of copyright, and cannot be sure that he doesn't do a copyvio while publishing the text.

One more point: the publication data is also needed not only for avoiding copyright violation, but also for cataloging of versions of works presented in the Wikisource. It is known that significant and pupular works are usually published many times and have many versions, so when a user puts a page with a work and doesn't provide from which book (or other source) this version of work was acquired, it would be hard for future contributors of the Wikisource to find out where the current version of the work has come from, so enforcing the rule - to add the publication data immediately when the page is created, - would save time for future users to find the origin of the version of the work represented on the page.

So I would like to create opinion poll - to know whether users (especially experienced users and admins) agree that the multilingual Wikisource must have a rule requiring providing publication data for newly-added content pages in the mainspace of the Wikisource. As far as I know many (or all) big Wikisources (like English and other ones) have such rules, and I don't see any reason why the multilingual Wikisource should not have such a rule too.

Any comments and opinions are welcomed. --Nigmont (talk) 09:30, 8 October 2023 (UTC)[reply]

Yep, that is a huge problem. Unsourced, not categorized, fake texts... -jkb- (talk) 10:36, 8 October 2023 (UTC)[reply]
I fully agree with the suggested rule. Just one more or less stylistic clarification : "...the main namespace (except maybe scan-backed pages...". I do not see the point in repeating this data. Draco flavus (talk) 11:01, 8 October 2023 (UTC)[reply]
Good point, though I always put publication data even on scan-backed pages while adding them in the Moksha and Erzya categories (the languages I am working on), I agree - other language Wikisources may have other preferences and their contributors may decide that repeating that data is not desired. I corrected the wording accordingly (removing the word "maybe"), let's leave scan-backed pages on full discretion of the contributors. --Nigmont (talk) 13:02, 8 October 2023 (UTC)[reply]
The Polish texts (scan-backed) translude usually the template {{Dane tekstu}}, the publication date is there explicitly given. So the information is still there. Draco flavus (talk) 14:31, 8 October 2023 (UTC)[reply]

Vote

Do you support the idea that the mutilingual Wikisource needs to have a rule - requiring to provide with publication data all the content pages in the main namespace (except maybe scan-backed pages with scans/files having the reqired publication data)?

Results

Enough time have elapsed from the start of the vote, and all users who voted here supported that the rule should be added. Therefore we have to create the rule and add it somewhere on a Wikisource policy page. I will open a new topic soon -- to discuss what should the rule look like. --Nigmont (talk) 11:39, 4 November 2023 (UTC)[reply]

Tech News: 2023-41

[edit]

MediaWiki message delivery 14:39, 9 October 2023 (UTC)[reply]

Opportunities open for the Affiliations Committee, Ombuds commission, and the Case Review Committee

[edit]

Hi everyone! The Affiliations Committee (AffCom), Ombuds commission (OC), and the Case Review Committee (CRC) are looking for new members. These volunteer groups provide important structural and oversight support for the community and movement. People are encouraged to nominate themselves or encourage others they feel would contribute to these groups to apply. There is more information about the roles of the groups, the skills needed, and the opportunity to apply on the Meta-wiki page.

On behalf of the Committee Support team,

Translated text

[edit]

Hello, new here. I was reading on Wikisource an original text in English and clicked on the equivalent page in another language. It is obvious that the translation was done by users who knew little about the topic and little about literary English, most probably used a translation app. I poked around a little bit more and found a translated version of the text published by a well-respected editor, however still copy-righted. What is the policy of Wikisource in that case? Delete with a note and add a link to the published translation? Best, --2tirets4tildes (talk) 09:23, 15 October 2023 (UTC)[reply]

Tech News: 2023-42

[edit]

MediaWiki message delivery 23:47, 16 October 2023 (UTC)[reply]

Review and comment on the 2024 Wikimedia Foundation Board of Trustees selection rules package

[edit]
You can find this message translated into additional languages on Meta-wiki.

Dear all,

Please review and comment on the Wikimedia Foundation Board of Trustees selection rules package from now until 29 October 2023. The selection rules package was based on older versions by the Elections Committee and will be used in the 2024 Board of Trustees selection. Providing your comments now will help them provide a smoother, better Board selection process. More on the Meta-wiki page.

Best,

Katie Chan
Chair of the Elections Committee

01:13, 17 October 2023 (UTC)

Tech News: 2023-43

[edit]

MediaWiki message delivery 23:16, 23 October 2023 (UTC)[reply]

Tech News: 2023-44

[edit]

MediaWiki message delivery 23:21, 30 October 2023 (UTC)[reply]

The rule for providing texts with their sources

[edit]

According to the voting in the topic above (A_lot_of_unsourced_texts_being_added_on_the_multilingual_Wikisource), we need to create the rule and add it somewhere in policy page(s).

First, we need to describe the rule itself. I can propose such text:

All content pages of the main space of the Wikisource, except pages of user-created translations, must be provided with publication data of where and when the work represented on the page was published. This information should be added in the header or beginning of the page.
If the work was published in a book, then the information must contain the book's name and year when the book was published; also (not mandatory) information about the author's, publishing house, city and ISBN if they are known (may be omitted if they are unknown or absent).
If the work was published in a periodical issue, then the information must contain the periodical's name and year when the issue was published; also (not mandatory) the number of the issue in the year (or volume if the periodical is published in volume-based format) and month and day of the periodical issue if any of those are known, also publishing house, city if they are known.

Since I am not a native English speaker, I propose to somebody with native or very good knowledge of English to fix the text given above to make it looking good from the point of English grammar and English sense.

Also a question: should we make some exceptions for this rule -- to point out some cases when giving publication data is not mandatory? I think we need to add some:

  • As it was remarked during the voting (User:Draco flavus pointed out), to put publication data for scan-backed pages should not be mandatory if all required information provided on the proofread index and/or a file from which the work has been proofread.
  • Also in my opinion, in the case when a work was published as a part of collection or as a part of a periodical issue, and the work's page was created as a subpage of the main page representing the entire book or the periodical issue, then duplication of the information from the root page (given the root page already has publication data for the entire book or periodical issue) on the subpage is not required (but may be done if the contributors want to add it).
  • Also, publication data IMHO is not required for government works -- such as constitutions of countries, legislative acts and others, that is, works licensed like PD-USGov or PD-RU-exempt. Freedom from copyright for such acts are not connected with publication year or death year of author's, they are released into Public Domain unconditionally; also in some cases it is not easy to find the first edition where the act was originally published (for example, for acts in Russia there could be some government newspapers where such acts are usually published first). For those reasons, publication data for government acts released into PD by force of laws of the country, is not required, IMHO, we can omit it on those pages.
  • And one more case that can be an issue: the Wikisource contains specimens of short but well-known works translated in many languages, for example Pater noster. Many translations of such works presented here in the multilingual Wikirource are not provided with publication data too. Should we require publication data for such pages too? I am not sure...

And the last point: we should also decide -- where to add the rule after we create it's precise statements, on which page? I would propose to add it to the page Wikisource:Copyright policy, because possible copyright violation is the major issue originating from the absence of publishing data on the work's page. Or maybe we should add the rule on some other page?

So, let's discuss all of that. Pinging all who voted: @-jkb-, Draco flavus, Koavf, Ankry, Jusjih: other users are welcomed to the discussion too, of course. --Nigmont (talk) 11:53, 4 November 2023 (UTC)[reply]

This all seems sensible. We should require publication data for non-original translations, such as those Pater noster pages as well. —Justin (koavf)TCM 17:42, 4 November 2023 (UTC)[reply]
Source is important not only to determine whether the copyright expired on the work, but also to determine whether the work is out of copyright (or freely licensed) for other reasons, and to determine whether the work is real in the first place. For this reason, I’d require a source for every work, including Pater noster translations and law text. (In case of ProofreadPage scans or individual chapters of works on subpages, the source field on Commons / the source provided at the main page of the work counts as a source, so those cases aren’t exempted either, just we allow not duplicating the same pieces of information all over the place.) On the other hand, not all works were first published in books or periodicals (or maybe the first publication is not known, but the copyright status can be determined without that), so we should say something about works whose known publication is a web page, a flyer, or even a house wall. —Tacsipacsi (talk) 10:58, 5 November 2023 (UTC)[reply]

Tech News: 2023-45

[edit]

MediaWiki message delivery 21:05, 6 November 2023 (UTC)[reply]

Move request, revert a previous one

[edit]

Move page اومارمیدڭ؟ towards Wikisource:How does one edit a page. --ZandDev (talk) 17:04, 8 November 2023 (UTC)[reply]

Done How odd. —Justin (koavf)TCM 18:37, 8 November 2023 (UTC)[reply]

Change content model

[edit]

Use Special:ChangeContentModel to change content model of Help:Font_size_templates/styles.css to sanitized-css. --ZandDev (talk) 01:18, 9 November 2023 (UTC)[reply]

DoneJustin (koavf)TCM 02:36, 9 November 2023 (UTC)[reply]

Tech News: 2023-46

[edit]

MediaWiki message delivery 23:52, 13 November 2023 (UTC)[reply]

Tech News: 2023-47

[edit]

MediaWiki message delivery 00:55, 21 November 2023 (UTC)[reply]

FYI: Celebrating 20 years of Wikisource and 3,000+ years of history

[edit]

https://diff.wikimedia.org/2023/11/23/celebrating-20-years-of-wikisource-and-3000-years-of-history/Justin (koavf)TCM 10:11, 23 November 2023 (UTC)[reply]

Tech News: 2023-48

[edit]

MediaWiki message delivery 23:08, 27 November 2023 (UTC)[reply]

Tech News: 2023-49

[edit]

MediaWiki message delivery 23:50, 4 December 2023 (UTC)[reply]

Tech News: 2023-50

[edit]

MediaWiki message delivery 02:12, 12 December 2023 (UTC)[reply]

(New) Feature on Kartographer: Adding geopoints via QID

[edit]

Since September 2022, it is possible to create geopoints using a QID. Many wiki contributors have asked for this feature, but it is not being used much. Therefore, we would like to remind you about it. More information can be found on the project page. If you have any comments, please let us know on the talk page. – Best regards, the team of Technical Wishes at Wikimedia Deutschland


Thereza Mengs (WMDE) 12:31, 13 December 2023 (UTC)[reply]

Tech News: 2023-51

[edit]

MediaWiki message delivery 16:17, 18 December 2023 (UTC)[reply]