Wikisource:Proposed deletions

From Wikisource
(Redirected from Wikisource:DEL)
Jump to navigation Jump to search
WS:PD redirects here. For help with public domain materials, see Help:Public domain.
Proposed deletions

This page is for proposing deletion of specific articles on Wikisource in accordance with the deletion policy, and appealing previously-deleted works. Please add {{delete}} to pages you have nominated for deletion. What Wikisource includes is the policy used to determine whether or not particular works are acceptable on Wikisource. Articles remaining on this page should be deleted if there is no significant opposition after at least a week.

Possible copyright violations should be listed at Copyright discussions. Pages matching a criterion for speedy deletion should be tagged with {{sdelete}} and not reported here (see category).

SpBot archives all sections tagged with {{section resolved|1=~~~~}} after 7 days. For the archive overview, see /Archives.


This specific index is one of many such indexes; I nominate it as an example, but should the rationale be found sound, I will endeavor to make a list of all such indexes.

This index (and many others) were created by now-absent User:Languageseeker. My main concern is that the pages of these indexes have been added via match-and-split from some source, likely Project Gutenberg, which does not have a defined original copy. Because of this absence of real source, and the similarity of the text to the actual text of any given scanned copy, proofreading efforts would likely have to either not check the text against the original source or scrap the existing text entirely to ensure accuracy to the original on Wikisource. In light of this, I think the easiest approach is to delete the indexes and all pages thereunder; if there is organic desire to scan them at some point in the future, the indexes may be re-created, but I do not see a reason to keep the indexes as they stand. TE(æ)A,ea. (talk) 19:12, 9 December 2023 (UTC)[reply]

  •  Comment Hmm. I don't see the Index: pages as problematic. But the "Not Proofread" Page: pages that were, as you say, created by Match & Split from a secondary transcription (mostly Gutenberg, but also other sources), I do consider problematic. We don't permit secondary transcriptions added directly to mainspace, so to permit them in Page: makes no sense. And in addition to the problems these create for Proofreading that TE(æ)A,ea. outlines, it is also an issue that many contributors are reluctant to work on Index:es with a lot of extant-but-not-Proofread (i.e. "Red") pages.
    We have around a million (IIRC; it may be half a mill.) of these that were bot-created with essentially raw OCR (the contributor vehemently denies they are "raw OCR", so I assume some fixes were applied, but the quality is very definitely not Proofread). Languageseeker's imports are of much higher quality, but are still problematic. I think we should get rid of both these classes of Page: pages. In fact, I think we should prohibit Not Proofread pages from being transcluded to mainspace (except as a temporary measure, and possibly some other common sense exceptions). --Xover (talk) 20:24, 9 December 2023 (UTC)[reply]
    • Xover: Assuming the status of the works to be equal, I would actually consider Languageseeker’s page creations to be worse, because, while it would look better as transcluded, it reduces the overall quality of the transcription. My main problem with the other user’s not-proofread page creations was that he focused a lot on indexes of very technical works, but provided no proofread baseline on which other editors could continue work—that was my main objection at the time, as it is easier to come on and off of work where there is an established style (for a complicated work) as opposed to starting a project and creating those standards yourself. As to the Page:/Index: issue, I ask for index deletion as well because these indexes were created only as a basis for the faulty text import, and I don’t want that to overlook any future transcription of those works. Again, I have no problem to work (or re-creation), I just think that these indexes (which are clearly abandoned, and were faulty ab origine) should be deleted. As for transclusion of not-proofread pages, I don’t think that the practice is so widespread that a policy needs to implemented (from my experience, at least); the issue is best dealt with on a case-by-case basis, or rather an user-by-user basis (as users can have different ways of turning raw OCR into not-proofread text, then following transclusion and finally proofread status). But of course, that (and the other user’s works, the indexes for which I think should probably be deleted) are a discussion for another time. (I will probably have more spare time starting soon, so I might start a discussion about the other user’s works after this discussion concludes.) TE(æ)A,ea. (talk) 02:28, 10 December 2023 (UTC)[reply]
      I'm not understanding what fault there is in the Index page. If the Page: pages had not been created, what problem would exist in the Index: page? --EncycloPetey (talk) 02:53, 10 December 2023 (UTC)[reply]
      • EncycloPetey: This isn’t a case where the index page’s existence is inherently bad; but the pages poison the index, in terms of future (potential) proofreading efforts and in terms of abandonment. TE(æ)A,ea. (talk) 03:07, 10 December 2023 (UTC)[reply]
        @TE(æ)A,ea.: Just to be clear, if the outcome here is to delete all the "Not Proofread" Page: pages, would you still consider the Index: pages bad (should be deleted)? So far that seems to be the most controversial part of this discussion, and the part that is a clear departure from established practice. Xover (talk) 07:40, 20 December 2023 (UTC)[reply]
        • Xover: Yes, I think those are also bad. They were created en masse for the purpose of adding this poor match-and-split text, and there is no additional value in keeping around hundreds of unused indexes whose only purpose was to facilitate a project consensus (here) clearly indicates in unwise. The main objection on that ground is that indexes are difficult to make; but that is not really true, and in any case is not a real issue, as a new editor who wishes to edit (but not create an index) can simply ask for one to be created. Another problem with these indexes is that they are not connected with other information (like the Author:-pages) that would help new editors find them. Insofar as they exist like this, the only real connection these indexes have to the project at large is through Languageseeker, who is now no longer editing. I don’t think that every abandoned index is a nuisance, but I do believe that this (substantial) group of mass-created indexes is a problem. TE(æ)A,ea. (talk) 21:10, 20 December 2023 (UTC)[reply]
  • I support deleting the individual pages of the index. As for the Index page itself, I am OK with both deleting it as abandoned or keeping it to wait for somebody to start the work anew. I also support getting rid of other similar secondary transcriptions. If a discussion on prohibiting transclusion of not-proofread pages into main NS is started somewhere, I will probably support it too. --Jan Kameníček (talk) 00:39, 10 December 2023 (UTC)[reply]
 Comment I've always felt uncomfortable with the tendency of some users to want to bulk-add a bunch of Index pages which have the pages correctly labelled, but are left indefinitely with no pages proofread in them. I feel like a "transcription project" (as Index pages are labelled in templates) implies an ongoing, or at least somewhat complete, ordeal, and adding index pages without proofreading anything is really just duplicating data from other places into Wikisource. Not to say there's absolutely no value in adding lots of index pages this way, but the value seems minimal. The fact that index pages mostly rely on duplicate data as it is is already an annoying redundancy on the site, and I think most of what happens on Index pages should just be dealt with in Wikidata, so I think the best place to bulk-add data about works is there, not by mass-creating empty Index pages. I know my comment here is kind of unrelated to the specific issue of the discussion (being, indexes with pages matched and splitted or something), but the same user (Languageseeker) has tended to do that as well. I am struggling to come up with any specific arguments or policies to support my position against those empty index pages... but it just seems unnecessary, seems like it will cause problems in the future, and on a positive note I do applaud Languageseeker's massive effort—it shows something great about their character as an editor—but unfortunately I think their effort should have been more focused on areas other than the creation of as many Index pages as possible. PseudoSkull (talk) 04:15, 10 December 2023 (UTC)[reply]
Bulk-adding anything is probably a bad idea on Wikisource, because so much of what we do here requires a human touch. That being said, so far as I know the Index: pages Languageseeker created were perfectly fine in themselves, including having correct pagelists etc. This step is often complicated for new contributors, so creating the Index: without Proofreading anything is not without merit. It's pointing at an already set up transcription project onsite vs. just (ext)linking to a scan at IA for some users. The latter is an insurmountable effort for quite a lot of contributors. We also have historically permitted things to sit indefinitely in our non-content namespaces if they are merely incomplete rather than actually wrong in some way.
That's not to say that all these Index: pages are necessarily golden, but imo those that are problematic (if any) should be dealt with individually. Xover (talk) 09:08, 10 December 2023 (UTC)[reply]
Oh, also, what we host on Wikidata vs. what's hosted locally in our Index: pages is a huge and complicated discussion (hmu if you want the outline). For the purposes of this discussion it, imo, makes the most sense to just view that as an entirely orthogonal issue. If and when (and how and why and...) we push some or all our Index: page contents somewhere other than our current solution, it'll deal with these Index:es as well as every other. Xover (talk) 07:33, 20 December 2023 (UTC)[reply]
 Comment I do not support creating them, but since they exist, I try to make good use of them. I usually proofread offline for convenience and when I add the text I check the diff. If anything differs, it is an extra check for me as I could be the one who made mistakes. So I would keep them.
BTW, nobody forbids to press the OCR button and restart. Mpaa (talk) 18:35, 10 December 2023 (UTC)[reply]
While that is true, my experience is that the kinds of errors introduced by a mystery text layer is insidious, and most editors are unaware of the issue, or fail to notice small problems such as UK/US spelling differences, changes to punctuation, minor word changed, etc. So, while a person could reset the text, what would alert them to the fact that they should, rather than working from the existing unproofed page?
H. G. Wells' First Men in the Moon is a prime example. A well-meaning editor matched-and-split the text into the scan. Two experienced editors crawled through making multiple corrections to validate the work, yet as recently as this past week we have had editors continue to find small mistakes throughout. Experience shows that match-and-split text is actually worse for Wikisource proofreading than the raw OCR because of these persistent text errors. --EncycloPetey (talk) 18:51, 10 December 2023 (UTC)[reply]
In my workflow, I start from OCR, then compare what I did with what is available. It is an independent reference which I use for quality check. The probability that I did the same error is low (and the error would be anyhow there). It is almost as if someone is validating my text (or vice-versa). For me it is definitely a help. I follow the same process when validating text. I do not look at what is there and then compare. Mpaa (talk) 19:21, 10 December 2023 (UTC)[reply]
Right. You do that, and I work similarly. But experience shows that the vast majority of contributors don't do that; they either don't touch the text due to the red pages, or they try to proofread off the extant text and leave behind subtle errors as EncycloPetey outlines. Xover (talk) 19:35, 10 December 2023 (UTC)[reply]
We could argue forever. I do not know what evidence you have to say that works started from match-and-split are worse than others. I doubt anyone has real numbers to say that. IMHO it all depends on the attitude of contributors. I have seen works reaching a Validated stage and being crappy all the same. If you want to be consistent, you should delete all pages in a NotProofread state and currently not worked on because I doubt a non-experienced user will look where the text is coming from when editing, from a match-and-split or whatever.
Also, then we should shutdown the match-and-split tool or letting only admins to run it, after being 100% sure that the version to split is the same as the version to scan.
I am not advocating it as a process, I am only saying that what is there is there and it could be useful to some. If the community will decide otherwise, fine, I can cope with that. Mpaa (talk) 20:32, 10 December 2023 (UTC)[reply]
I do not know what evidence you have to say that works started from match-and-split are worse than others. Anecdotal evidence only, certainly. But EncycloPetey gave a concrete example (H. G. Wells' First Men in the Moon), and both of us are asserting that we have seen this time and again: when the starting point is Match & Split text, the odds are high that the result will contain subtle errors in punctuation, US/UK spelling differences, words changed between editions, and so forth. All the things that do not jump out at you as "misspelled". Your experience may, obviously, differ, and it's certainly a valid point that we can end up with poor quality results for other reasons too.
Your argumentum ad absurdum arguments are also well taken, but nobody's arguing we go hog-wild and delete everything. Languageseeker, specifically, went on an import-spree from Gutenberg (and managed to piss off the Distributed Proofreaders in the process), snarfing in a whole bunch of texts in a short period of time. All of these are secondary transcriptions, and Languageseeker was never going to proofread these themselves (their idea was almost certainly to either transclude them as is, or to run them in the Monthly Challenge).
For these sorts of bulk actions that create an unmanageable workload to handle, I think deletion (return to the status quo ante) is a reasonable option. The same would go for the other user that bulk-imported something like 500k/1 mill. (I've got to go check that number) Page: pages of effectively uncorrected OCR. For anything else I'd be more hesitant, and certainly wouldn't want to take a position in aggregate. Those would be case-by-case stuff, but that really isn't an option for these bulk actions. Xover (talk) 07:17, 11 December 2023 (UTC)[reply]


 Comment I am agianst deleting the Index. Indexes are one of the most tedious work to do when starting a transcription. Having index pages prepared and checked against the scan will save a lot of work. Mpaa (talk) 21:46, 10 December 2023 (UTC)[reply]
  •  Keep the Index, but  Delete the pages. None of the bot-created pages have the header, which is a pain to add after-the-fact unless you can run a bot. The fact that they were created by match-and-split, instead of proofreading the text layer is poor practice. --EncycloPetey (talk) 19:15, 20 December 2023 (UTC)[reply]
    There are many recently added "new texts" with no headers. Mpaa (talk) 22:00, 23 December 2023 (UTC)[reply]
    • What percent of editors want headers; and what percent do not care? Do you have data? --EncycloPetey (talk) 22:03, 23 December 2023 (UTC)[reply]
      No, I am only stating is not a good argument for deletion in my opinion, unless it is considered mandatory. Mpaa (talk) 22:22, 23 December 2023 (UTC)[reply]
      • It is a good argument if most potential editors want to include the headers, and are put off working on proofreading by the fact that pages were created without the headers in place. There are works I've chosen not to work on for this reason. --EncycloPetey (talk) 23:04, 23 December 2023 (UTC)[reply]
      I agree that on its own the lack of headers is not a good argument for deletion. But I read it here to be intended as one additional factor on the scales that added together favour deletion. Which I do think is a valid argument (one can disagree, of course). Xover (talk) 23:57, 23 December 2023 (UTC)[reply]
    • Mpaa: That is the result of the efforts of one user, who has declared headers superfluous. I was going to start another discussion on that topic after this one (only one big discussion at a time for me, please). I think that, for all editors who want headers (most of them), not having them (because of the match-and-split seen here) is bad. Also, in response to your other comments above about proofreading over existing text, I usually do that as well, but I prefer proofreading on my own, without needing to check against a base—that’s why I focus on proofreading, not validation. For that same reason, I avoid all-not-proofread indexes like those at issue here. TE(æ)A,ea. (talk) 23:22, 23 December 2023 (UTC)[reply]
      I was thinking the same about headers, it would be good to have a consistent approach about works, in all their parts/namespaces. Mpaa (talk) 09:47, 24 December 2023 (UTC)[reply]
 Comment in the future, if anyone feels blocked for the lack of headers, or wants to add headers, please make a bot request.Mpaa (talk) 09:47, 24 December 2023 (UTC)[reply]
 Comment I am proofreading this specific text. This discussion can be as reference for the other indexes, as TE(æ)A,ea. mentioned at the beginning of the discussion. BTW, a list would be useful, so I can fetch before a (possible) deletion. Mpaa (talk) 12:53, 2 January 2024 (UTC)[reply]

Duplicative of Weird Tales/Volume 3/Issue 1/The Picture in the House, starting discussion to decide whether to remove or migrate the librivox recording. MarkLSteadman (talk) 06:43, 29 December 2023 (UTC)[reply]

Gah. Tough call.
The two texts are not the same. Both Weird Tales in 1924 and the 1937 reprint use … the antique and repellent wooden building which blinked with bleared windows from between two huge leafless oaks near the foot of a rocky hill, but the unsourced text uses elms. LibriVox for once actually gives a source, and in the case of File:LibriVox - picture in the house lovecraft sz.ogg that source is The Picture in the House (unknown) (modulo a page move after the fact here), and the audio narration does match (uses "elms"). The change to "elms" seems to be a later innovation, possibly applied by an editor as late as 1982 (Bloodcurdling Tales of Horror and the Macabre, the earliest use of "elms" there I could find right now), and the likely ultimate source of our text. The texts differ in other ways too, but up to this point the difference could be explained by transcription errors, lack of scan-backing and validation, etc.).
So… I don't think we can move the LibriVox file over to our new text (different edition). And because the nominated text is from an indeterminate edition and we have a scan-backed version of this work, we should  Delete The Picture in the House (unknown) too.
But it's really annoying that when LibriVox for once both gives the source text they have used for their reading and actually links back to us, we have to delete the page. I wish they'd coordinate more with us on issues like this so we could get the maximum benefit out of our respective volunteer efforts. Xover (talk) 08:38, 29 December 2023 (UTC)[reply]
I guess that the LibreVox versions dates to when this was the only version available. Can we put the LibreVox link on The Picture in the House ? -- Beardo (talk) 18:33, 29 December 2023 (UTC)[reply]
Hmm, no, I don't think so. We can't start amassing random multimedia versions of texts at the dab pages. Eventually we want spoken-word versions of our texts automatically linked from data on Wikidata, and that requires control over which specific edition the spoken-word version is from. Xover (talk) 10:49, 31 December 2023 (UTC)[reply]
weak  Delete - it would probably be better for us to just start from scratch, although I recognize its value as being linked to from LibriVox, so maybe it could just be redirected to the current scanned version instead of outright deleted. SnowyCinema (talk) 03:30, 8 March 2024 (UTC)[reply]
  • But start from scratch using what? The issue is that our scan-backed copy has a different text from the LibriVox recording. The text of the nominated copy can be attested, but not (yet) from a volume dated before 1945. Ideally, we would find a PD volume with the current text. --EncycloPetey (talk) 04:35, 18 March 2024 (UTC)[reply]

Badly formatted copydump. Could be recreated by proofreading from this "scan". —Beleg Tâl (talk) 02:30, 2 February 2024 (UTC)[reply]

 Comment That scan is posted at gov.uk, which makes it a digital publication of the UK government. This feels like a potential candidate for the MC. --EncycloPetey (talk) 02:46, 2 February 2024 (UTC)[reply]
(what is the MC?) —Beleg Tâl (talk) 15:13, 3 February 2024 (UTC)[reply]
I notice this is marked with a Crown Copyright, which may not be compatible with our licensing. I know Commons would not host the scan, but is it hostable here? --EncycloPetey (talk) 22:49, 10 February 2024 (UTC)[reply]
It is released under the Open Government Licence which is both available here and Commons as {{OGL}}. Is there a particular reason why this work isn't acceptable while the others are? MarkLSteadman (talk) 23:02, 10 February 2024 (UTC)[reply]
Are you looking at the last page of the scan, with the Crown Copyright, or the local license tag that the contributor placed on the work? --EncycloPetey (talk) 23:10, 10 February 2024 (UTC)[reply]
On the last page: "You may re-use this information free of charge in any format or medium, under the terms of the Open Government license". MarkLSteadman (talk) 23:13, 10 February 2024 (UTC)[reply]
 Delete as a copydump. SnowyCinema (talk) 03:27, 8 March 2024 (UTC)[reply]

Supposedly published in Sofia, Bulgaria, in a publication with a Bulgarian title, yet entirely in English. An internet search for the publication turns up nothing, so I do not have access to the claimed source to check. --EncycloPetey (talk) 06:02, 3 February 2024 (UTC)[reply]

 Delete per nom —Beleg Tâl (talk) 15:09, 3 February 2024 (UTC)[reply]
 Comment It looks like a unsourced user-provided translation (several different works by this author were contributed by this IP from a variety of Bulgarian sources). I don't know how we want to apply the grandfathering exceptions for such a translation if so. MarkLSteadman (talk) 16:33, 3 February 2024 (UTC)[reply]
 Delete. We may think this is the Wikisource user's translation, but at the same time we cannot with certainty rule out other possibilities like copying somebody else's work, unless the user states it is their own work and adds a proper licence to it. Without such a statement we should treat it as we treat other licence-lacking texts with dubious sourcing. --Jan Kameníček (talk) 16:56, 3 February 2024 (UTC)[reply]
  • Don’t delete (at least for now) because of the user-translation business. This is, as far as I can tell, a user translation of a few excerpts relating to Delchev. The source definitely exists, however—it is OCLC 831298036. I will try to get ahold of the relevant pages. TE(æ)A,ea. (talk) 19:17, 3 February 2024 (UTC)[reply]

Excerpt of just parts of the title page (a pseudo-toc) of an issue of the journal of record for the EU. Xover (talk) 11:29, 11 February 2024 (UTC)[reply]

Also Official Journal of the European Union, L 078, 17 March 2014 Xover (talk) 11:34, 11 February 2024 (UTC)[reply]
Also Official Journal of the European Union, L 087I, 15 March 2022 Xover (talk) 11:35, 11 February 2024 (UTC)[reply]
Also Official Journal of the European Union, L 110, 8 April 2022 Xover (talk) 11:36, 11 February 2024 (UTC)[reply]
Also Official Journal of the European Union, L 153, 3 June 2022 Xover (talk) 11:37, 11 February 2024 (UTC)[reply]
Also Official Journal of the European Union, L 066, 2 March 2022 Xover (talk) 11:39, 11 February 2024 (UTC)[reply]
Also Official Journal of the European Union, L 116, 13 April 2022 Xover (talk) 11:39, 11 February 2024 (UTC)[reply]
  •  Keep This isn't an excerpt; it matches the Contents page of the on-line journal and links to the same items, which have also been transcribed. The format does not match as closely as it might, but it's not an excerpt. --EncycloPetey (talk) 04:52, 12 February 2024 (UTC)[reply]
    That's not the contents page of the online journal, it's the download page for the journal that happens to display the first page of the PDF (which is the title page, that also happens to list the contents). See here for the published form of this work. What we're hosting is a poorly-formatted de-coupled excerpt of the title page. It's also—regardless of sourcing—just a loose table of contents. Xover (talk) 07:09, 13 February 2024 (UTC)[reply]
    I don't understand. You're saying that it matches the contents of the journal, yet somehow it also doesn't? Yet, if I click on the individual items in the contents, I get the named items on a subpage. How is this different from what we do everywhere else on Wikisource? --EncycloPetey (talk) 16:35, 13 February 2024 (UTC)[reply]
    They are loose tables of contents extracted from the title pages of issues of a journal. They link horizontally (not to subpages) to extracted texts and function like navboxes, not tables of contents on the top level page of a work. That their formatting is arbitrary wikipedia-like just reinforces this.
    The linked texts should strictly speaking also be migrated to a scan of the actual journal, but since those are actual texts (and not a loose navigation aid) I'm more inclined to let them sit there until someone does the work to move them within the containing work and scan-backing them. Xover (talk) 08:35, 20 February 2024 (UTC)[reply]
    So, do I understand then that the articles should be consolidated as subpages, like a journal? In which case, these pages are necessary to have as the base page. Deleting them would disconnect all the component articles. It sounds more as though you're unhappy with the page formatting, rather than anything else. They are certainly not "excerpts", which was the basis for nominating them for deletion, and with that argument removed, there is no remaining basis for deletion. --EncycloPetey (talk) 19:41, 25 February 2024 (UTC)[reply]

Only one user (besides deleting administrator) supported deletion, and those comments were without justification and/or not true. There is a substantial amount of English text in this work, which makes it clearly in scope. TE(æ)A,ea. (talk) 22:38, 20 February 2024 (UTC)[reply]

  •  Oppose In the 13 years this Index was up, the six pages of English introduction were never proofread. The pages that were created included: missing images pages in Latin with English titles; blank pages; and unproofread pages in Latin. Yes, there is substantial English, but only mixed with Latin in the endnotes. It is correct to say that only one person opposed the deletion prior to the deletion occurring. If the Index were proofread first at la.WS or the multi-language WS, we could host the six English pages here, but as a primarily Latin text, it is not in scope for en.WS. --EncycloPetey (talk) 22:42, 20 February 2024 (UTC)[reply]
    Considering the endnotes are about interpreting the latin text it really does feel like this is a good fit for multi-language WS. I could see a potential discussion if the endnotes were themselves meaningful independent texts but I don't understand how a 100 pages of "[Latin] See X. xx." can exist without the text. MarkLSteadman (talk) 00:27, 21 February 2024 (UTC)[reply]
     Abstain: Due to this relevant discussion related to this topic when it was put here a short while ago and I had voted in opposition to keep the work here at that time (since only about 235 scan pages out of the total of 418 scan pages were actually in Latin; the rest being in English). It should perhaps also be noted I made the Commons edit 853982373 (among several others) pointing the Wikisource link at WS.MUL. I agree this work had floundered here previously and that it probably should not be primarily here but I also believe there is substantial English content that can and should be here (provided someone actually proofreads it). —Uzume (talk) 14:18, 14 March 2024 (UTC)[reply]

: Undelete. My interpretation of what makes a text "an English text" or "not an English text" is intended audience. Clearly this book was intended to be read by English speakers, given that the front matter, introduction, etc., were in English. Yes, the bulk of the text is in Latin, but the reason it's in Latin is for English speakers to study it in its (presumably) original form, not because the text needed to be conveyed in Latin for a strictly Latin-speaking audience.

Think of it like this: This version of the work is not strictly "a Latin version of Commentaries" but a book for English readers containing a Latin version of Commentaries to interpret. The point isn't to read the Latin natively (like an ancient Roman text would be), but to read it secondarily to one's academic knowledge of the language. So the crux of the work, while only taking up a small amount of the text, is in the English language, making me believe that this should be hosted at English Wikisource, since this is part of the English-speaking world's compendium of literature. No, I don't think Multilingual or Latin Wikisources are appropriate for this, and including the Introduction alone here (since the Introduction is not a work, but a piece of a work, and not even the only part of it in English), defies our rules on including excerpts. SnowyCinema (talk) 01:02, 21 February 2024 (UTC)[reply]
From WWSI: "The English Wikisource only collects texts written in the English language." I would consider a Latin text aimed at English speakers as not written in the English language (e.g. the untranslated Principia). Re the crux issue, my view is the exact opposite, without the Latin text the introduction / notes have little value, but an edited Latin text could stand on its own. Re excerpts, that is what will happen once we blank out the Latin, that (and the title page) will be all that remain. MarkLSteadman (talk) 02:14, 21 February 2024 (UTC)[reply]
No, no, it's sort of like if you had a plate in a book, and the plate was a picture of a sign in French. But the caption was in English. So what language was the page in? English, not French, and the same logic applies to this book we're discussing... The book contains Latin to study (or whatnot), but the context of it was framed in English, so the book is descriptively an English work. And as I said below, splitting up content by language across interwikis gets complicated fast. SnowyCinema (talk) 16:21, 21 February 2024 (UTC)[reply]
To take the plates example a bit further. Let's say I have a 300 plate facsimile edition of a manuscript edition of this. I would expect that we agree that none of the following would make it a work for here as a preferred relative to Latin WS:
1. There is a title page that says something like "Volume 525 in the British Museum Manuscript Series", a dedication / acknowledgement or each page is captioned as "Page 25, Book 4" instead of "Page Liber 4"
2. Notes are added comparing against other manuscript editions and these say things like "foo in the Parker Library manuscript", again instead of having "in the Parker Library manuscript be English rather than Latin
3. Notes of a highly technical nature such as a discussion of the current thinking of the identification of a particular site, or military specifics.
The experience of a Chinese historian might be different. A classicist would engage archaeologists in English, write in English journals etc., the Chinese historian next door might be presenting a paper written in Chinese based on a similar facsimile from a Chinese publisher in a conference in China. I would expect that we wouldn't consider those differences really significant.
A long series of English essays on topics to accompany the text on the other hand would make sense as a standalone work. To what extent glosses become independent works in themselves is of course up for discussion. I can see an argument, we do have works like An Ainu–English–Japanese Dictionary which are similar to a work like [1] which is similar to the glosses in the endnotes here, but I would hope we agree that [2] or [3] are not English texts per WWSI. MarkLSteadman (talk) 15:08, 22 February 2024 (UTC)[reply]
That opens us to a whole lot of foreign-language texts. Pretty much every major enough work has an edition with English notes and vocabulary for pedagogical use. I've worried about how they fall through the cracks at Wikisource, but I'm not sure supporting huge chunks of Latin/German/Spanish/French/Russian text here is a good idea either.--Prosfilaes (talk) 02:31, 21 February 2024 (UTC)[reply]
Exactly right. If there's an edition (that's a key word) of a foreign-language work with English footnotes or commentary, this is at its core part of the English-language lexicon. So I see absolutely zero issues with including lots of these, since they're just individual editions out of probably hundreds across the globe that exist, and it doesn't corrupt anything at English Wikisource really to include them here. What does corrupt something is for us to automatically exclude certain bits of the English compendium of knowledge from our site. SnowyCinema (talk) 16:21, 21 February 2024 (UTC)[reply]
I'm curious how you came to your conclusion. The first 200 pages of the book are the text in Latin, followed by 150 pages of notes that are keyed to the text by page number. We don't host non-English texts, so we would not host the 200 pages of Caesar's text. Exactly what use are the 150 pages of notes that depend upon knowing the page numbers specific to a work we don't have? --EncycloPetey (talk) 04:00, 21 February 2024 (UTC)[reply]
Text is quite a vague word that can mean different things to different people. So it's unfortunate that we have a policy that doesn't elaborate on a specific definition of a word like text. For example, a poem in a larger poetry collection could be considered a "text" in some contexts. I would certainly consider that poem a work (or properly, a version of a work).
And as it turns out, if you want to use the loose definition of text that I suggested—and I'm assuming that's the one you all are using—we host quite a large number of poems in other languages than English. Why? Because these poems appear in printed works that are at the core English texts: in other words, even the one poem out of 120, that happened to be in French for some narrative or thematic reason, was broadly intended for English speakers to read. And I'm sure that most of you here would at least agree that it would be ludicrous to selectively pick and choose which bits of a poetry collection we want to include based on what language they happen to be written in.
So, I don't like the reverence to a word like "text" as if it's the be and end all, because it can't be. It doesn't capture the necessary nuance here. Let's use the word "scan" instead. That's more appropriate, yes, because that's what was brought up for an undeletion discussion, not the body of the work... And in the context of the broader scan, the intention is clearly for English speakers to read it. It was never for people in Ancient Rome because they were dead long before.
And a big part of the reason I'm making these arguments, by the way, is because of the structural importance of doing the simple thing, having this at enWS instead of making it into a discombobulated mess of interwoven interwikis. Like I said, being picky about which language is in which part of what scans is going to lead us into a kind of hellscape in terms of technical maintenance. Say you wanted to include the Introduction at enWS, but nothing else. How would you do that? How would you ensure no one proofreads the rest of it against your will? Would you use soft redirects to lead people to Latin Wikisource for the rest? Would you do the same at Latin Wikisource, to go back to the Introduction from the body? What if laWS already has 15 other versions of the same work? How would you make sure this one fits their version structure? What if laWS doesn't want this version, because they have some specific rule against some facet of your project? What if Latin Wikisource accepts your project, but doesn't want to let you soft redirect back to enWS, or doesn't have the technology/community consensus/whatever to do so? What if laWS wants the whole entire scan to be transcribed there just like we do, including the English introduction? So now, we have two places where the same transcription exists. Not good for my favorite rule to point to, the DRY rule.
Just one example of how this can get complex... I was gonna write a paragraph for both laWS and mulWS being exclusive keepers of this text, but I'm tired. Just let the platitude that it will also have major problems suffice for the penny I'm giving.
Maybe you'll shrug this off as a mere opinion on my part, that is absolutely nothing compared to the infallible word of Wikisource policy. But I do believe that texts should not be considered based solely on quantity of a certain language, but intent of using a certain language. Our policies are badly written in the first place, probably in need of decades of further reform, and shouldn't ever be someone's blindfold. (And, as far as I understand wiki culture, policies don't matter anyway if the community votes against them in a particular deletion discussion. So my vote, which is hypothetically more powerful than any policy, is still there.) SnowyCinema (talk) 05:08, 21 February 2024 (UTC)[reply]
Opinions and policy are not two different things; they are two forms of the same thing. Policy happens because many people held the same opinion and reached consensus on an issue. So to dismiss policy with a wave of personal opinion is to dismiss the collective opinions of many people. --EncycloPetey (talk) 03:07, 22 February 2024 (UTC)[reply]
I'm not necessarily even dismissing the policy outright. It certainly has merit: we've made it clear we don't want to keep "all works in all languages" (maybe so we don't have to be one letter off from Wiktionary's slogan). But the people who wrote the policy clearly made no consideration about a specific definition of "text", that could apply across the board. Either that, or "text" to the writers specifically meant "scan" or "entire piece of printed matter" (which I think is more useful to consider, and is also a valid definition of "text").
In other words, even with their intent in mind, I could be correct. On that note, this policy was written in the mid-2000s, so I wouldn't even call it "modern consensus", but just the opinions of people in the context of that time 95% of whom are probably long inactive now, so our views on their opinions are really only speculative in nature. But one thing we do know is how they worded it, and they clearly didn't word it with a whole lot of nuance. Literally only one sentence addresses this issue, and it defines what's not allowed with a word that could mean 5 different things to 10 different people. So I'd argue, the policy can't apply to this discussion, since people (not even just me) disagree widely on how to deal with a scan like this. So clearly, the rule can't address these nuances. (And by the way, this is the case with most of WS:WWI. I think lots of detail should be used there, or at least subpages of the policies should be made to address specific nuances. So, reform is needed badly.)
Even if I were to grant that my specific conclusion (that language of context should be considered and not which language is most prevalent) is wrong, it doesn't take away from the fact that a word like "text" is too vague for something like a sitewide policy. If the community is going to cite policy as an absolute arbiter of truth and authority, policy needs to be some of the most well-written and specific and all-encompassing content on the entire site. But it isn't, so I think it's fair to say it doesn't deserve that level of deference. SnowyCinema (talk) 04:11, 22 February 2024 (UTC)[reply]
I am inclined to agree that a work consisting of quite extensive comments in English on a non-English text which includes this non-English text that is being commented could be in our scope, mainly per argument by SnowyCinema above that it was intended for English speaking audience who want to study the Latin text. However, I am not voting to undelete the work, which had been abandoned long time before it was deleted, unless there is somebody who wishes to proofread it. BTW, maybe we should have a specific point about similar cases in our inclusion policy. --Jan Kameníček (talk) 16:55, 22 February 2024 (UTC)[reply]
I have three concerns around the idea of hosting non-English texts with with English glosses / notes.
1. The maintenance burden is increased. This extends from the difficulty of finding additional contributors (e.g. if someone proofreads 120 out of 300 pages of Thai and stops, what do we do?) to verifying copyright and fidelity concerns (are these 300 pages of Arabic what they claim to be? What is the copyright status if it is a modern scan? etc.)
2. Data model concerns. Per practice, we should turn Commentaries on the Gallic War into a {{translations}} page when this is proofread to link to the two different editions. But this isn't a translation. We could make De Bello Gallico a {{versions}} page and link The Commentaries of C. Julius Caesar from that but that breaks our wikidata model of single works with multiple editions, etc.
3. If we do start having large extracts of non-English text, we will eventually start to attract non-English speaking contributors. While that might produce collaborative work, it also brings along its own set of challenges. MarkLSteadman (talk) 22:52, 22 February 2024 (UTC)[reply]
Ad 1: Similarly as I did not agree with undeletion of this abandoned work, I think that we should be strict about completion of all such works, and abandoned works of this type should be deleted after some reasonable time, which can be discussed (e. g. 1 year after the work stopped?).
Ad 2: In fact such a problem may arrise now as well. I can imagine that some English language work we already have includes e. g. some short poem, a letter etc. in a foreign language. Should the poem be added to the translation or version page? There is one specific example, here: Index:A grammar of the Bohemian or Cech language.djvu (currently also abandoned, but on my long list of works I hope to proofread one day). I think that such a kind of work does belong here. At the end of the book there are some works by Czech authors as "Reading lessons" in Czech, see e. g. Page:A grammar of the Bohemian or Cech language.djvu/162. I believe that such a reading lesson should not be omitted from the book, but at the same time it should not be added to any version or translation page.
Ad 3: It is quite possible, but at the same time it may also start attracting foreign contributors who speak English, and I may be considered to be an example of that :-) – after few coincidental attempts between 2011 and 2015 I started seriously contributing in 2016, after my attention was drawn to the above mentioned Grammar of the Bohemian language (although I soon moved to some different publications, as that one was too challenging because of complicated formatting). --Jan Kameníček (talk) 00:23, 23 February 2024 (UTC)[reply]
@Jan.Kamenicek: Your response to point #2 suggests you did not understand the concern. This issue is that, if we host a Latin edition of Caesar's Commentaries then we run into the conundrum of having to possess both a Translations page and a Versions page for certain works. Neither the set-up here nor at Wikidata can currently support this. --EncycloPetey (talk) 00:45, 23 February 2024 (UTC)[reply]
I did understand. And I wrote that we can run into the very same problem if we host an English work that includes just a short poem in a foreign language. And I suggested not to list non-English works either in translation page or a version page. That would eliminate the need to have both in such cases. --Jan Kameníček (talk) 00:53, 23 February 2024 (UTC)[reply]
But we have to list the main page title somewhere. For a work as an appendix and therefore as a subpage we don't necessarily need to build out the link but Commentaries of Caesar will point to what when we have both an English (e.g. [4] and [5]) and a Latin version under that title? Which gets back to the main text distinction (we wouldn't have this issue if it was entitled A Gallic Wars Lexicon. MarkLSteadman (talk) 01:13, 23 February 2024 (UTC)[reply]
The Latin version of the Commentaries will be only a part of Observations upon Caesars Commentaries. It should not be linked to from anywhere, only the whole work called Observations... should be linked from appropriate places, like from the author page of Clement Edmonds. Commentaries of Caesar can either be the translation page containing a list of English translations, or should be a redirect to such a translation page. In this way we can avoid the problem. Or somebody may later come with some other possible solution(s). Let's not forget that it is just a technical problem and thus it is a problem inferior to building up our content. Adding content useful to English language audience should be our main goal and technical means should be adapted to this goal, not vice versa. --Jan Kameníček (talk) 13:49, 23 February 2024 (UTC)[reply]
Except that it's not strictly a technical issue; it's a procedural one. An it's a problem that will be created for every instance we have of hosting a non-English text. Without a plan to deal with this issue, will we just leave it unsolved? The solution cannot be to say that we just won't link it from anywhere. This also goes against SnowyCinema's principle of DRY, since we would be duplicating non-English texts present at other WS projects and potentially duplicating them here as well. Why have just this author's footnotes on Caesar's Commentaries? Why not host all the editions of Caesar's Commentaries that have English footnotes or endnotes? --EncycloPetey (talk) 19:25, 24 February 2024 (UTC)[reply]
Well, playing with words aside, I think what I have written about technical problems applies to procedures too: they serve our goal (hosting proofread texts useful to English readers), we should not adapt our goal to fit the procedures.
Not linking from version/translation pages (containing links to English language works) to non-English text which are incorporated inside an English language publication, and linking only to this English language publication from other proper places, is imo a possible solution. If it is not a good solution for some reason, some other has to be found anyway, no matter whether we accept works like these Commentaries. How should linking e.g. to a fully quoted foreign language poem in an English language publication be solved? I suggest not linking to it.
We can host all editions of Caeasar's Commentaries that have extensive English comments to the original text if somebody were willing to proofread them here. What is extensive and what not can be decided case by case, as no massive adding of such works is likely to happen anytime soon. --Jan Kameníček (talk) 20:10, 24 February 2024 (UTC)[reply]
It is a straw man to compare a critical edition of the Commentaries of Caesar to a poem quoted inside another work. The latter is a work appearing inside another completely different work, but the topic at hand is an edition of Caesar's Commentaries with notes added. The two situations are not equivalent. --EncycloPetey (talk) 19:33, 25 February 2024 (UTC)[reply]
I did not say that the situation is the same, I said that the technical (procedural) problem is the same, because it is the procedure that was above used as an argument. --Jan Kameníček (talk) 19:37, 25 February 2024 (UTC)[reply]
And that is a straw man argument, as I said. The problem is not the same because of the reasons I stated. --EncycloPetey (talk) 19:47, 25 February 2024 (UTC)[reply]
The procedure is absolutely the same, so if you see any other problem, it is not procedural. I really do suggest focusing more on understanding the core of the message before you call somebody's arguments a "straw man". Reading (and thinking) twice may help to avoid some misunderstandings. Now I am going to stop beating the dead horse unless somebody comes with something worthy to think about. --Jan Kameníček (talk) 19:52, 25 February 2024 (UTC)[reply]
I agree. Please read what I wrote initially, because I do not think you've understood, or are instead dodging the issue. The solution will never be to ignore the issue or to prop up some other argument to be battled instead of the actual issue. If we do host this work, we can't connect it at Wikidata, and we have no means for listing it here, so how will anyone find it? It's not the same as a short foreign language work appearing inside another work because we've never included those procedurally in any listing. Not when a quotation appears at the start of a book chapter, not when a biography quotes a letter or poetry, and not when a literary survey of an author's body of works includes numerous quotations either. This is fundamentally different: it's a work not in English, with bits added, and we have no means in place here or at Wikidata to deal with that, in part because no Wikisource has ever done this. --EncycloPetey (talk) 21:46, 25 February 2024 (UTC)[reply]
Re the other points:
1. We can be stricter and enforce additional criteria, but that will need to be reflected in the policy language. And of course if we had a larger community, including more bilingual admins, they could help maintain such works. My point is that maintaining a large collection of works like this [6] is an increased burden relative to the same work in English, and that if concerns are raised (in this case we know it is safe, but e.g. someone uploads a 1980s collection of classical Persian poetry, and claims it is pubic domain it will be hard for me to search.
2. I will note that there is currently no sourced version of the work on la.wikisource. If people are interested proofreading latin shouldn't we concentrate on getting a complete version there? MarkLSteadman (talk) 23:29, 25 February 2024 (UTC)[reply]
@EncycloPetey: My example was a poem that is happenstance in another language, for some reason or another, included in a larger poetry collection of English poems. So I guess our infrastructure "doesn't support this" too you're saying (since poems themselves are works even if included in collections), yet we've been doing this for decades anyway with no contest. I've even seen entire Versions pages that only link to foreign-language poems hosted on English Wikisource, because they were included in collections multiple times. Well, anyway, if the poem in the poetry collection is in French, or in this case if the Caesar's Commentaries is given an introduction in English, in both cases the context is set in English which I've said multiple times, but that point was never addressed anywhere. The Latin body of the text is not holistically and wholesale what the work is as you seem to be suggesting... The body of the work is part of the work. Only part. I don't think of it as a Latin text with English commentary, but as an English work that has a Latin text in it. Sort of like a page in a novel that contains a photograph of a sign in French, but a caption in English. So the page is not a page in French, but a page in English using the French as a display for study by English speakers. Even though the photographed French sign might contain three paragraphs of French words, whereas the English caption is only one sentence long, the page is in English, just like this English work with a Latin text in it for the exact same kind of study. SnowyCinema (talk) 22:11, 25 February 2024 (UTC)[reply]
Please include examples of what you're saying you've seen, because I have only non-examples (quotes and poetry that were not indexed). But the example of a work inside a collection is still not directly analogous to this case. And I understand that you think of it differently, but this is far more like a critical edition of a Shakespeare play than a collection of literature. For a critical edition of any work, it is still an edition of that work, and not something else. All our annotated Shakespeare plays are listed as copies of his plays, because that's what they are. I cannot interpret a Latin-language work with English notes added as a fundamentally English-language work that happens to have Latin text in it. The Latin text is the core of what was published, and everything else in the publication is subservient to the Latin text. That's not an English work with Latin in it. --EncycloPetey (talk) 22:21, 25 February 2024 (UTC)[reply]
And let me pose a very practical question: Who gets credit as the Author for this work? --EncycloPetey (talk) 22:32, 25 February 2024 (UTC)[reply]
Example: Posthumous Poems/Chanson de Février. Should this be deleted too, or relegated to another project? SnowyCinema (talk) 22:34, 25 February 2024 (UTC)[reply]
My point is that such an instance as that is a non-example. It's not indexed here or on Wikidata because it's not the work; it's included inside another collective work that is indexed. We have countless such poems even in English that have not been indexed anywhere at all. With the item currently under discussion, we lack the means entirely for housing the edition both here and at Wikidata because it's a work in Latin written by Caesar with critical commentary added to it. That's how any major library would index it. --EncycloPetey (talk) 22:43, 25 February 2024 (UTC)[reply]
Changing vote to  Abstain—I'm not sure anymore, but EncycloPetey makes an intuitively good point in his rhetorical question about who would be credited as the author, and such like that. I can see there are both pros and cons to including this at English Wikisource, and I've gone into many of the pros. But, this is one of the only examples of a "kind-of-bilingual" gray-area work of this nature that I've even seen on the project, and the fact that it only has an introduction in English of 6 pages' length isn't doing it any favors. If it had much more substantive amounts of English content, I'd probably be more sympathetic.
I will say that I worry about the precedent this work may set for future discussion on far less gray-area bilingual material than this. I still maintain that WS:WWI should be immensely improved and made much more specific so that we're not left up to so much interpretation, and that a single sentence describing "texts" is not sufficient. We should probably investigate many different examples of foreign works with English text in them, to come to some more nuanced and universal conclusion.
I do disagree with EP's idea that poems in collections, i.e. "subworks", should lack indexing on Wikidata "because it's not the work"—see my efforts on any collections I've done like Illinois Verse, The High School Boy and His Problems, or The Way of the Wild, where I have gone above and beyond to connect all subworks to Wikidata and list each one at author and disambiguation pages, since I think they should be treated the same as any other work (and this is not inconsistent with past practices at Wikidata and Wikisource). So I think that the lack of indexing of Posthumous Poems is not a matter of "they shouldn't be indexed", but more that "they should ideally be indexed but aren't because it's hard and no one wants to take the time to do it". But this isn't that relevant to my overall change of perspective on Commentaries. SnowyCinema (talk) 23:22, 25 February 2024 (UTC)[reply]
Note: I am not arguing that "subworks" should lack indexing as a general principle. I was noting that (a) we historically have done a very poor job of indexing them, and that (b) some such works should not be indexed because of what they are and how they are included. If, for example, a novel places a poem at the start of a chapter, or (as noted above) a photograph of a sign in French appears in a book, such "subworks" are not indexed, as per standard library practice. --EncycloPetey (talk) 23:29, 25 February 2024 (UTC)[reply]
I am also much more comfortable being less strict with the metadata around subworks / appenda / etc.: they can rely on the stricter metadata "box" of the main work (putting aside the difference between subwork like an appendix as opposed to breaking up a chapter to wikidata a poem contained in it). MarkLSteadman (talk) 23:42, 25 February 2024 (UTC)[reply]

If you look at the source on Gutenberg, you will see that "Philip Dwight Jones" is listed as both the translator and the ebook producer. I therefore believe that this is a rare instance of a work originally published by Project Gutenberg. Is such a work in scope, or is it doubly out of scope as self-published and second-hand? —Beleg Âlt BT (talk) 20:40, 21 February 2024 (UTC)[reply]

It's a translation of a public domain work. If it's public domain--which it claims to be--I would keep this along the lines of a Wikisource translation.--Prosfilaes (talk) 00:13, 22 February 2024 (UTC)[reply]
 Keep I don't see that counts as self-published, and we accept to keep second-hand works from that time, don't we, until we have a better replacement ? -- Beardo (talk) 03:01, 22 February 2024 (UTC)[reply]
There are many public domain translations of this work: from 1672 [7] to modern [8] [9] [10] [11] MarkLSteadman (talk) 19:21, 24 February 2024 (UTC)[reply]
In terms of copyright: This would be a rare case of an original Project Gutenberg transcription, and despite the work being from 2001 and being impossible to fall into the PD naturally, if I'm correctly reading the very complex legal notice at the bottom of every Gutenberg transcription, the terms comply with wiki standards on licensing, allowing free distribution, derivatives, etc. So it seems freely licensed.
However: Although this is a web transcription from a reputable source like Gutenberg, the transcription itself has no particular notoriety (even though the source work does). Most damningly, I believe Gutenberg works are constantly subject to further updates, which would not be in line with our purposes. The text is from 2001, and was last updated on February 7, 2013, giving it 12 years of potential strings of updates. I.e., it may be impossible to ascertain what the most pure version of this transcription is, so we probably shouldn't include it. So,  Delete. SnowyCinema (talk) 21:20, 22 February 2024 (UTC)[reply]
 Delete per SnowyCinema. --Jan Kameníček (talk) 22:30, 6 March 2024 (UTC)[reply]
 Comment There is no evidence that this work is "expected to constantly change over time". There is speculation that many years of changes might have happened, but no evidence of what has actually changed. No one has compared our copy to the 2013 revision in even a cursory fashion to investigate the actual degree of change. It could be a thorough revision different in many respects; it could be an update to formatting tags with no changes to the text; we don't know because no one has looked. Also, no one has mentioned is that our copy is a copydump without the formatting present in the original, such as centering, italics, font sizes, etc. --EncycloPetey (talk) 01:29, 8 March 2024 (UTC)[reply]

While I understand that there is value to interlinear texts, we generally only host one user translation of a given work, and we already have Translation:Bible. —Beleg Âlt BT (talk) 20:53, 21 February 2024 (UTC)[reply]

@Bobdole2021: I believe this is a project you are involved in —Beleg Âlt BT (talk) 20:54, 21 February 2024 (UTC)[reply]
  •  Comment It depends on the source text, in this case, I would think. Translation:Bible is presumably using the Masoretic text (in Hebrew) for the Old Testament, which is different from the source text for Interlinear Greek Translation:Bible, which is from the Greek Septuagint. This is one reason we want our user-created translations to clearly identify what they are translating, so that we can determine what is happening in cases like this. If one is translating the Masoretic, and another the Septuagint, and another the Latin Vulgate, then that feels like legitimate separate translations. But without having a clearly identified starting point for the translation, we cannot determine that. And even for "the Septuagint", whose edition of the Septuagint is being used? There are whole volumes listing the differences between the various Greek copies of the Septuagint. --EncycloPetey (talk) 21:09, 21 February 2024 (UTC)[reply]
    Translation:Bible is a bit unique, in that every book has (or should have) its own source. So Hebrew works like Translation:Genesis would be translated from Hebrew, while Greek works like Translation:Esther (Greek) would be translated from Greek, Translation:1 Meqabyan from Ge'ez, etc. —Beleg Âlt BT (talk) 21:13, 21 February 2024 (UTC)[reply]
    There would be a good argument to be made, that Translation:Bible should actually be in Portal space, since it is a list of separate works rather than a cohesive work itself. —Beleg Âlt BT (talk) 21:15, 21 February 2024 (UTC)[reply]
    Yes, but also no. The Masoretic text is a cohesive collection, and there are published editions that can be used as a basis for translation. The Vulgate is a cohesive collection, and it has published editions too. But the Dead Sea Scrolls are not; they are a collection by virtue of being discovered in the same location together. And even if you consider Genesis a "book" in its own right, there is still no single source text. There is the Masoretic edition in Hebrew, and the Septuagint editions in Greek, and the Vulgate edition of Jerome in Latin. There is not even an editio princeps as often happens with classical texts. Considering Genesis (and the other "books" of the Bible) to be works in their own right does nothing to help the fundamental issues here. --EncycloPetey (talk) 21:39, 21 February 2024 (UTC)[reply]
    Unfortunately, Translation:Bible is nowhere near as sensible as all that :p
    I wonder if we could approach this by splitting Translation:Bible into component sources?
    • Hebrew OT books based on the Masoretic text, which is what I assume heWS has (he:ביבליה, not scan-backed)
    • Greek OT books based on the Septuagint, which is what I assume elWS has (el:Η Αγία Γραφή, also not scan-backed)
    • Greek NT books based on this scan at elWS
    • The others I'll need to research further but you get the gist.
    We already have separate translations for Esther (Hebrew and Greek) and Psalms (Hebrew, Greek, and Syriac) so we can just extend this to the rest of the works I guess.
    My main concern is the idea of having a separate "regular" translation and "interlinear" translation of the same work; otherwise, I'm open to whatever needs to be done to clean this mess up —Beleg Âlt BT (talk) 14:55, 26 February 2024 (UTC)[reply]
    Perhaps we consider an interlinear translation to be something like the Translation equivalent of an Annotated text, requiring a "clean" copy to exist first? --EncycloPetey (talk) 00:48, 27 February 2024 (UTC)[reply]
    Maybe. I seem to recall that at some point we explicitly disallowed interlinear translations, but I can't find it now.
    [update] I found it: WS:ANN disallows "Comparison pages: Pages from different versions of the same work, whether whole works or extracts, placed alongside each other (whether in series or in parallel) to provide a comparison between the different versions." I'm not sure whether that would apply here though. —Beleg Âlt BT (talk) 14:14, 27 February 2024 (UTC)[reply]

The following discussion is closed and will soon be archived:

Deleted. Unformatted copydump of volume 7 (out of 20). Scans exist for most of the 20 volumes, but they have yet to be transcribed.

Just copypasted raw OCR including headers and pagenumbers breaking the text flow. Besides, it is not the whole text of the The Percy Anecdotes, as the title suggests, but only the 7th volume. There is an index of this volume that can be proofread at Index:The Percy Anecdotes - Volume 7.djvu. I do not think there is a value of keeping this raw OCR, it seems better to start the potential proofreading process from scratch. -- Jan Kameníček (talk) 18:36, 5 March 2024 (UTC)[reply]

 Delete per nom —Beleg Âlt BT (talk) 19:12, 7 March 2024 (UTC)[reply]
 Delete per nom SnowyCinema (talk) 00:50, 8 March 2024 (UTC)[reply]
Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. --EncycloPetey (talk) 17:45, 12 March 2024 (UTC)[reply]

The following discussion is closed and will soon be archived:

Deleted as excerpt.

Just an unsourced excerpt. -- Jan Kameníček (talk) 14:22, 6 March 2024 (UTC)[reply]

 Delete as an excerpt. SnowyCinema (talk) 00:56, 8 March 2024 (UTC)[reply]
Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. --EncycloPetey (talk) 17:46, 12 March 2024 (UTC)[reply]

The following discussion is closed and will soon be archived:

Deleted. Unsourced text, with implication that it it was user compiled and edited.

Unsourced text which cannot be found anywhere. I suspect it was compiled by the anon contributor who added it here, judging by the fact that after they added the text they reworded it and wrote in the summary "hopefully of some use to scholars in future". -- Jan Kameníček (talk) 20:09, 6 March 2024 (UTC)[reply]

 Delete because of dubious sourcing. SnowyCinema (talk) 00:51, 8 March 2024 (UTC)[reply]
Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. --EncycloPetey (talk) 00:00, 14 March 2024 (UTC)[reply]

The following discussion is closed and will soon be archived:

Kept. Contains at least one suitable work.

Has been empty since at least April 2023, we appear to have no texts on the subject. I think there is no need to keep this category. Thanks, Cremastra (talk) 00:09, 7 March 2024 (UTC)[reply]

 Keep This would appear to in fact be a Castilian treaty, so I reinstated the category. SnowyCinema (talk) 00:55, 8 March 2024 (UTC)[reply]
Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. --EncycloPetey (talk) 00:02, 14 March 2024 (UTC)[reply]

A court document allegedly from Lexis Advance, but the source is not available to people who do not have an account of the Multimedia University (from Malaysia). With the source being inaccessible it is impossible to say whether it is a second-hand transcription or a transcription of an original document. The biggest problem is that the text is not available anywhere else either, and so it is absolutely impossible to check whether the transcription is correct and complete, whether it was originally in in English or it is a translation from Malay (which would raise questions about copyright), or even whether such a text really exists (I believe it does, but we have to be able to check it).

Pinging also Ong Kai Jin, who I have already asked to add a proper licence tag but without any reaction. -- Jan Kameníček (talk) 18:09, 7 March 2024 (UTC)[reply]

If indeed this is a document that originated (from legislators) in English it would be in the public domain as an edict of a government, but like you said it is also impossible to tell if that's the case without access to the original source. So,  Delete until evidence of source is provided. SnowyCinema (talk) 00:49, 8 March 2024 (UTC)[reply]
I have trimmed the source link to become not dependent to the institution's account, but subscription is still required for access, I am sorry if this is also not accepted. I would say this is the only authentic and original source, since this is a 'unreported' case law which it was not included into the journal for print, and LexisNexis is the publisher of this journal. The issue is no direct way for other user to validate the text, but I could not help.
In regarding the copyright, literary work, which is a copyrightable work, does not include judicial decisions. This is stated in Section 3 of Copyright Act 1987. The license tag Template:PD-Malaysia have been prepared. I assume there is no copyright issue here. Ong Kai Jin (talk) 16:34, 8 March 2024 (UTC)[reply]
@Ong Kai Jin - to be hosted here, a work needs to be in public domain under US copyright law. I am still unclear - was the actual judgement in English ? -- Beardo (talk) 17:46, 8 March 2024 (UTC)[reply]
I think it is reasonable to be under the public domain in both countries? Yes, the actual judgement was written in English. Why is it suspected to be in Malay language? Ong Kai Jin (talk) 19:52, 8 March 2024 (UTC)[reply]
 Keep a court judgement issued in English is solidly in scope as {{PD-EdictGov}}. That said, @Ong Kai Jin: is there any way this work can be exported from LexisNexus in PDF format so that it can be properly proofread? —Beleg Tâl (talk) 23:14, 8 March 2024 (UTC)[reply]
The website provides two versions of PDF download, the user-customizable and the court-ready, but the court-ready version is not available for 'unreported' cases such as this work. I feel that it serves no authentic value for using that custom PDF. Ong Kai Jin (talk) 20:23, 9 March 2024 (UTC)[reply]

The song Arise O Compatriots, Nigeria's Call Obey was recently deleted as copyvio (see WS:CV#Arise O Compatriots, Nigeria's Call Obey). Its authors, who are not notable for any other work, should be deleted also.

Beleg Âlt BT (talk) 13:49, 13 March 2024 (UTC) —Beleg Âlt BT (talk) 13:49, 13 March 2024 (UTC)[reply]

-  Delete - indeed. -- Beardo (talk) 18:21, 13 March 2024 (UTC)[reply]
Though per w:Babatunde Ogunnaike, he has published various works and has a US patent, which I think would be a work eligible for wikisource - no ? -- Beardo (talk) 18:03, 14 March 2024 (UTC)[reply]
Yeah, if US patents are in the public domain, and someone wants to upload his patent to enWS, then we can definitely keep his author page —Beleg Âlt BT (talk) 18:21, 14 March 2024 (UTC)[reply]
 Delete. It is not really probable somebody will add the patent. If so, the page can be recreated easily. --Jan Kameníček (talk) 15:58, 17 March 2024 (UTC)[reply]

Poems by Emily Dickinson - Second Series[edit]

The following unsourced poems by Emily Dickinson, which now have scan-backed versions in Poems: Second Series (Dickinson) and another in progress in The Complete Poems of Emily Dickinson, should be deleted to make way for {{versions}} pages:

Beleg Âlt BT (talk) 15:36, 13 March 2024 (UTC)[reply]

The following discussion is closed and will soon be archived:

Speedied as redundant to a scanbacked version.

Checkmark This section is considered resolved, for the purposes of archiving. If you disagree, replace this template with your comment. --Jan Kameníček (talk) 23:13, 16 March 2024 (UTC)[reply]

Compilation. -- Jan Kameníček (talk) 23:04, 16 March 2024 (UTC)[reply]

Probably should be converted into a portal linking the various pieces. If that seems like an acceptable resolution to you I can work on moving them this week. MarkLSteadman (talk) 15:10, 17 March 2024 (UTC)[reply]
@MarkLSteadman: Thanks, that is a preferred solution, of course. Only the red text is not available in any sources and was added there nobody knows where from, so unless its source is found, the red text should probably be deleted anyway. --Jan Kameníček (talk) 15:54, 17 March 2024 (UTC)[reply]

Multiple other versions under Ozymandias (Shelley), this particularly unsourced version is entirely redundant with Poems That Every Child Should Know/Ozymandias of Egypt, including the notes. MarkLSteadman (talk) 15:04, 17 March 2024 (UTC)[reply]

I believe this is a translation performed either by an anonymous/IP Wikisource editor in 2009, or else a translation of unknown provenance with no reason to believe it complies with Wikisource's copyright policy. I believe this is a different translation of the Petrarch poem Wyatt translated, here: "The long love that in my thought doth harbor"

It should be deleted as being either out of scope or else a copyright violation; I don't think it's worth the effort to do further research to determine which is the case, if either would likely result in deletion. Please note, there are several such "prose translations" of Petrarch poems; while I have not found as much information about these others, I believe this logic would apply to all of them. See some prior discussion at Author talk:Thomas Wyatt. These full list of such sonnets:

(All are labeled "modern prose translation" on their respective pages.) -Pete (talk) 17:50, 18 March 2024 (UTC)[reply]