Wikisource:Scriptorium

From Wikisource
(Redirected from Wikisource:SCRIPTORIUM)
Jump to navigation Jump to search
Scriptorium
The Scriptorium is Wikisource's community discussion page. Feel free to ask questions or leave comments. You may join any current discussion or start a new one; please see Wikisource:Scriptorium/Help. Project members can often be found in the #wikisource IRC channel webclient. For discussion related to the entire project (not just the English chapter), please discuss at the multilingual Wikisource. There are currently 298 active users here.

Contents

Announcements[edit]

Proposals[edit]

Template to mark works ineligible for copyright due to lack of human authorship[edit]

I propose either creating a new template (perhaps {{PD-machine}}), or altering our current {{PD-ineligible}}, to account for works that are in the public domain due to the absence of human creative expression. This template would make clear, for example, that machine translations of non-English works may be freely hosted here (so long as the foreign-language original works are also eligible).

The question whether machine translations may be hosted here has been discussed at meta: Wikilegal/Copyright for Google Translations, which concludes that such Google holds no U.S. copyright in the automatic translations produced by its software.

Guidance from the U.S. Copyright Office also supports this conclusion. Section 306 of the current (2017) Compendium of U.S. Copyright Office Practices states:

The U.S. Copyright Office will register an original work of authorship, provided that the work was created by a human being.

The copyright law only protects “the fruits of intellectual labor” that “are founded in the creative powers of the mind.” Trade-Mark Cases, 100 U.S. 82, 94 (1879). Because copyright law is limited to “original intellectual conceptions of the author,” the Office will refuse to register a claim if it determines that a human being did not create the work. Burrow-Giles Lithographic Co. v. Sarony, 111 U.S. 53, 58 (1884). For representative examples of works that do not satisfy this requirement, see Section 313.2 below.

The cross-referenced Section 313.2 does not expressly mention translations, but it does provide, in part, that “the Office will not register works produced by a machine or mere mechanical process that operates randomly or automatically without any creative input or intervention from a human author.” This further supports the principle that machine translations contain insufficient human expression to qualify for their own copyright protection.

At present, none of our Category:License templates address the human authorship requirement directly. The closest analog is {{PD-ineligible}}, which addresses works that “consist[ ] entirely of information that is common property and contain[ ] no original authorship.” All the works marked with the present version of {{PD-ineligible}}, however, appear to be the product of human authorship (or at least human transcription), and the {{PD-ineligible}} tag does not appear to address the ineligibility of non-human-originated works as discussed in the above-quoted language from the Compendium.

Because {{PD-ineligible}} in its present form does not quite fit the scenario of works created by machine, I suggest creating a new template that would expressly note that the lack of human authorship disqualifies such works from copyright protection in the United States. Tarmstro99 14:45, 8 September 2018 (UTC)

Even if Google holds no U.S. copyright in the automatic translations produced by its software, how about adding quick links from Wikisource? Perhaps machine translations will be improved, thus evolving.--Jusjih (talk) 01:52, 25 September 2018 (UTC)

Bot approval requests[edit]

Repairs (and moves)[edit]

Designated for requests related to the repair of works (and scans of works) presented on Wikisource

Orphée aux Enfers[edit]

Could someone please strip the Google notice from File:Orphée aux Enfers (Chicago 1868).djvu (on Commons) in preparation for hosting the work on Wikisource? --EncycloPetey (talk) 01:54, 14 October 2018 (UTC)

Yes check.svg Done --Mukkakukaku (talk) 18:34, 14 October 2018 (UTC)

Other discussions[edit]

Adapting Template:pd/1996 or a new template[edit]

As per previous conversation started by Prosfilaes, from next year US-published works published in 1923 will be out of copyright, and progressively year by year others will follow. We need to start working on whether we will adapt Template:pd/1996 to have wording that says that the work is out of copyright, and reconfigure that template to set triggers. Or whether we are going to implement a new template for post 1922 works. (Full coverage at copyright tags.) — billinghurst sDrewth 09:34, 5 August 2018 (UTC)

Don't the 1996-series of template primarily apply to works published outside the US? For works inside the US, we've been using the 1923-series of templates, and I would assume that it's the 1923-series that would need to be adapted to accommodate US-published works from 1923. It would be odd to have "published before 1923" to be a reason a work is in PD, if works published before 1924 is the actual set of works in PD. --EncycloPetey (talk) 15:55, 5 August 2018 (UTC)

You are correct that the pd/1996 has been non-US first publications to this point, and there would be complications in updating the template. Template:pd/1923 is set, and incrementing Template:PD/19xx is possible, though becomes a lot of templates. It is why I brought up the issue as we have to get the wording right, and look to the easiest means to progress through the years. As 1977 is the next US copyright milestone, maybe it is something like pd/1978 with both a year of birth AND year of publishing as parameters, where year of publishing flicks between copyright and not copyright.

billinghurst sDrewth 22:46, 5 August 2018 (UTC)

Let us keep watching for the rest of 2018 to be sure that the US copyright term is not extended. Then I may want to introduce "PD-pub-95" to mean "public domain for being published more than 95 years ago. Renaming Pd/1923 will probably be too disruptive, so making a new template may be better.--Jusjih (talk) 04:48, 9 September 2018 (UTC)
It's not going to happen, and part of the reason it's not going to happen is because we are going to rip the hell out of Congress if they try. Being able to say that are already preparing for this change will only help our case. And when the ball drops in New York, I will be uploading 1923 works, and will need an appropriate tag.
I'd like a single PD tag that takes publication year and author death year (if known), and it shouldn't mention in the name the exact rules, just applying all the rules that can be deduced clearly from publication year and author death year. Maybe just naming it PD-old would be too much?--Prosfilaes (talk) 06:35, 10 September 2018 (UTC)
I support the single-PD template idea. While it would be rather an in-depth template, I don't think it would be particularly difficult to implement (just a series of if-elsif-else conditions). Mukkakukaku (talk) 00:56, 13 September 2018 (UTC)
The US Copyright Office already considered the copyright terms too long. Mid-term election will be soon. Template:Pd/1923 is heavily used, so renaming will be harder than adding new template like "PD-pub-95". I will wait for the ball to drop in Times Square.--Jusjih (talk) 03:00, 18 September 2018 (UTC)
  • Pictogram voting comment.svg Comment Looking back at this and thinking again, I think that we should be building a template based on 1978 cutoff, aligning with 1923 and 1996 cutoff usage. We already have our subset of use templates (<1923; 1923<1996) that have a series of #if statements (well #ifexpr) that get implemented. At this stage we need to have some output templates that work in main ns that cover 1923 to 1977 at least
  • published in US between 1923-1963 with notice and renewal
  • published in US between 1964-1977 with notice
  • published outside of US between 1923-1977 (two scenarios)

where we will be incrementing per year. So we just use a #if expression for currentyear - 95 > publicationyear where it shows the PD template when true, and copyright violation when it fails. It is a few years until we need to worry about PD-old for post 1923, so we can work that bit out later. If someone uses this new license for a pre-1923 work, we can simply apply the {{pd/1923}} logic.

We still need a licence to display and the wording to use for US users, bottom half replicates pd/1996.billinghurst sDrewth 10:03, 25 September 2018 (UTC)

List of broken links from Wikipedia to Wikisource[edit]

In my profile: User:Uziel302 I put a list of 340 broken links from Wikipedia to Wikisource, any help fixing those links is much appreciated. Thanks.Uziel302 (talk) 07:58, 22 August 2018 (UTC)

Some examples:
  1. w:Alabama to Wikisource:Alabama
  2. w:Afghanistan to Wikisource:Afghanistan
  3. w:Azerbaijan to Wikisource:Azerbaijan
  4. w:Ancient_Egypt to Wikisource:Ancient_Egypt
  5. w:Aga_Khan_III to 1922_Encyclopædia_Britannica/Aga_Khan_III
  6. w:Antipope to Dictionary_of_Christian_Biography_and_Literature_to_the_End_of_the_Sixth_Century/Dictionary/Z/Zephyrinus
  7. w:Andrew_Carnegie to 1922_Encyclopædia_Britannica/Carnegie,_Andrew
  8. w:Angles to Ecclesiastical_History_of_the_English_People/Book_2
  9. w:Angles to Historia_Ecclesiastica_gentis_Anglorum_-_Liber_Secundus
  10. w:Angles to The_Ecclesiastical_History_of_the_English_Nation
  11. w:Aswan to Dictionary_of_Greek_and_Roman_Geography/Aswan
  12. w:Andalusia to Estatuto_de_Autonomía_de_Andalucía_2007
  13. w:Beryllium to Beryllium

Thanks, Uziel302 (talk) 10:51, 22 August 2018 (UTC)

There may be some broken links to the Folk-Lore Journal at en.wikipedia, the result of a move with suppressed redirects. — CYGNIS INSIGNIS 11:25, 22 August 2018 (UTC)
Anything that was Wikisource: namespace is now Portal: ns. To the others, there looks to be a collection of never/wishful, or moved. — billinghurst sDrewth 12:15, 22 August 2018 (UTC)
Looking through the list itself, one wonders why it was linked in the first place. Can I suggest for people, that you can use {{wikisource author}} as that was redesigned to utilise Wikidata interwiki links so moved pages are automatically updated. One day I am hoping that Wikipedia is better acclimatised to WD and many of their citation templates will be able to utilise a WD-based citation. — billinghurst sDrewth 12:23, 22 August 2018 (UTC)
billinghurst, is there an option to make Wikisource namespace redirected to Portal namespace? Uziel302 (talk) 16:09, 22 August 2018 (UTC)
No, that would be a cross namespace redirect, and wikis don't do it. Portal is a content namespace, and Wikisource is not. — billinghurst sDrewth 22:54, 22 August 2018 (UTC)
Just found a better query for these broken links, updated my page to include over 5,000 broken links. Uziel302 (talk) 08:02, 24 August 2018 (UTC)
Bunch of those aren't actually intentional links to Wikisource. They're trying to link to articles about Swedish tv shows, churches, etc. that are prefixed using the abbreviation S:t -- eg. "S:t Mikael" (a tv show). The "s:" prefix is forcing a WS interwiki.
Also this seems like something that they should be fixing up over the the enWP side. I fixed up a bunch where it was a clear "page moved" situation, but it's a thankless task. Mukkakukaku (talk) 00:32, 25 August 2018 (UTC)
well, i will thank you. a bunch of those are broken DNB links, and missing transcribed articles that were copied there from IA. (i.e. The New International Encyclopædia/Leutze, Emanuel) we did a 12000 article backlog for EB1911 - NIE and Appletons should be easy, not soul crushing at all. Slowking4SvG's revenge 02:55, 29 August 2018 (UTC)
by the way, some of those may be the em dash versus en dash conflict. Slowking4SvG's revenge 02:52, 3 September 2018 (UTC)
fyi, (a lot of links are are malformed template syntax) the english admins are mass reverting my attempts to work this backlog, so i leave it to you. Slowking4SvG's revenge 00:24, 19 September 2018 (UTC)
Hmm. What changes are getting reverted? --Xover (talk) 17:02, 19 September 2018 (UTC)
well, for example, this one here [1] apparantly a bot changed the dashes in title to em dashes breaking the link. an attempt to fix it was mass reverted. Slowking4SvG's revenge 03:47, 17 October 2018 (UTC)

Vulgate[edit]

An editor has proposed at w:Wikipedia:Village pump (miscellaneous)#Vulgate that we need a better and more complete Vulgate here (presumably an English translation). BD2412 T 02:30, 19 September 2018 (UTC)

It wasn't clear to me from the query whether it was a request for the Latin Vulgate or an English translation. The standard English translations of the Vulgate are the Bible (Douay-Rheims) translations. As with many translations into English, there are multiple editions extant. --EncycloPetey (talk) 03:15, 19 September 2018 (UTC)
The main Bible focus here at present is getting the KJV scan-backed. I doubt the current group of enWikisourcerors have the capacity to work on another version/translation right now. Beeswaxcandle (talk) 03:30, 19 September 2018 (UTC)
yeah, if User:Temerarius wants to show up, and get started, i would help him. here is an 1844 edition [2], and a 1852 [3] but i am past patience with the aspirational directive form of collaboration. too many other backlogs on my to do list. Slowking4SvG's revenge 17:29, 19 September 2018 (UTC)
If it is something we should eventually have, then it can't hurt to set up the project. If others want to follow through, that's on them. BD2412 T 22:31, 19 September 2018 (UTC)
Without a lack of clarity of what is needed, I am not certain that we can give specific advice. We can give general advice of 1) Straight transcription belongs at laWS. 2) If scans exist then they can be translated in our Page: ns. 3) If you want it done, it is our experience it will require a team of interested and committed people and a project is the best means to coordinate such. — billinghurst sDrewth 22:36, 19 September 2018 (UTC)
I'm sorry I wasn't clear: I was inquiring about the Latin text. There are a number linked at https://en.wikipedia.org/wiki/Vulgate, to which presumably no copyright restrictions apply. Temerarius (talk) 15:40, 22 September 2018 (UTC)
@Temerarius:The Latin text would need to be uploaded to the Latin Wikisource. And some of the Latin editions do have copyright restrictions. The Latin text is itself a translation from the Greek, attributed to Jerome, but the most recent revision was issued in the middle of the 20th century. That edition would still be protected by copyright. --EncycloPetey (talk) 17:28, 22 September 2018 (UTC)

The GFDL license on Commons[edit]

18:11, 20 September 2018 (UTC)

WEF framework / Wikidata gadget — confirm that it is again working[edit]

The WEF framework gadget has been reconfigured, so it broke here. I have played with the mediawiki configuration, and I believe that it is functional again. I would appreciate if someone can please confirm that it is working. Thanks. — billinghurst sDrewth 23:37, 20 September 2018 (UTC)

Tech News: 2018-39[edit]

15:23, 24 September 2018 (UTC)

Infoboxes on categories?[edit]

At Commons they have infoboxes that pull Wikidata, similarly to how we pull data for our headers; {{wikidata infobox}} and an example of use at c:Category:Alfred Odgers. We have been less than active with our labelling of categories, and while some have the use of {{plain sister}}, others have nothing. In a Commons's conversation it was asked whether it was of interest to us to utilise their schema for infoboxes. I am not adverse to its use

Notes:

  • The modules that are utilised have some similar functionality with some of our existing modules
  • Commons coding fraternity is reasonably active, so there is opportunity for access to more lua coders skilled at pulling Wikidata
  • We are not the best categorisers, and generally don't do people categories

Thoughts? — billinghurst sDrewth 23:15, 24 September 2018 (UTC)

Commons has a preference setting that puts the categories at the top. It is easier to have an opinion if you can see what you are making the opinion on.--RaboKarbakian (talk) 00:26, 25 September 2018 (UTC)
Not sure what to do with that comment. Any preference that Commons has, we have. Any gadget that Commons has, we can have, or individually one can run using a configuration line in your Special:mypage/common.js. — billinghurst sDrewth 02:13, 25 September 2018 (UTC)
Our category naming and structure differ significantly from that used on Commons and the Wikipedias. --EncycloPetey (talk) 00:32, 25 September 2018 (UTC)
As with our author and portal namespace, local naming and structure is not particularly pertinent. All this would do is put the data boxes into place, and display Wikidata with matching data as we do in main, author, and portal nss. Presumably (though we should check) if a category is not connected to Wikidata, then its display would be 'hide'. — billinghurst sDrewth 02:13, 25 September 2018 (UTC)
I disagree. Category naming and structure here is vastly different from other projects, and the names in the infobox will match the Wikipedia/Commons model. With the Author namespace, we are dealing with the name of the author and relevant dates. There is no major disconnect in that case. But pulling the names of Categories from Wikidata will more likely confuse users than help, and will encourage the creation of parallel category structures here to match Wikipedia and Commons. Both are strong negative points for me. --EncycloPetey (talk) 02:33, 25 September 2018 (UTC)
I have copied it (and the required modules and their required modules (ad nauseaum)) on User:Einstein95/sandbox. I particularly find the "Notable Work" field quite interesting, it might lead people to start adding texts that we don't have if they're fans of authors or genres. -Einstein95 (talk) 06:09, 25 September 2018 (UTC)
commons has a structured data on commons, and much work, standardizing metadata in templates.
we could increase links from wikisource to wikidata; could create items: "Wikisource author page" and "wikisource work" page, they have an index page item [5], with status [6], and wikisource links at footer.
we could increase our use of wikidata at author and work header pages. (will have to relax edition specification) we could modify author and header template to pull from wikidata. Slowking4SvG's revenge 20:28, 25 September 2018 (UTC)

Just a couple of brief comments (background: I wrote and maintain the infobox). It doesn't have to be used in categories - it should work equally well in other namespaces. It currently follows d:Property:P301 to go from category to topic items - if it would make sense to follow a different link to fetch the topic information then that should be possible. The infobox is built on modular code (Module:WikidataIB), so pieces of it (row lines, auto-categorisation, etc.) could be reused in e.g. {{Author}} (if that isn't the case already). I'm happy to provide help with using the infobox and WikidataIB if that's useful (on the parser function and bot editing sides - I don't know Lua). Thanks. Mike Peel (talk) 21:08, 25 September 2018 (UTC)

Pictogram voting comment.svg Comment On WP they use infoboxes in articles much like we use headers. Would it perhaps be more in keeping with the rest of WS if instead of category infoboxes we introduce category headers that perform similar function? —Beleg Tâl (talk) 23:38, 25 September 2018 (UTC)
I'd be mildly opposed to making our categories look like Author, Portal, and Work pages. Also, anyone who uses other projects will arrive with a certain expectation of what categories will look like, and doing something to violate that expectation seems a bad idea to me. --EncycloPetey (talk) 00:53, 26 September 2018 (UTC)
I strongly support this proposal, which will add semantic richness to our category pages. The templates work well, with overwhelming popular support, on Commons. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 05:30, 26 September 2018 (UTC)

What is the correct date?[edit]

We have had a contributor newly add:

Declaration of education The announcement of Fifty Industrial Community College on 18 June 1997

which appears to be a Google-translated copy of the same work as

Declaration of education The announcement of Fifty Industrial Community College on 18 June 1996

Can we determine the correct date so as to effect a merger? --EncycloPetey (talk) 01:01, 26 September 2018 (UTC)

According to File:ฯพณฯสุขวิช รังสิตพล รัฐมนตรีว่าการกระทรวงศึกษาธิการประกาศจัดตั้งวิทยาลัยการอาชีพ.jpg, it gives the year as B.E. 2540, which corresponds to 1997 C.E. -Einstein95 (talk) 04:50, 26 September 2018 (UTC)
This is also shown on the Thai Wikipedia article:

พ.ศ. 2540 (ค.ศ.1997) - นายสุขวิช รังสิตพลประกาศจัดตั้งวิทยาลัยการอาชีพ 51 แห่ง

-Einstein95 (talk) 04:54, 26 September 2018 (UTC)
Document itself says 1997. I have moved the first added to the 1997 space, though I think that it needs to be moved to the translation namespace, and we need to correct the case and grammar of the title. — billinghurst sDrewth 06:10, 26 September 2018 (UTC)

New Wikidata templates[edit]

The templates {{Reasonator}} and {{Scholia}} are available, for linking from Wikisource pages to representations of Wikidata items, where no suitable Wikipedia page is available as a target. They are modelled on {{WikiDark}}, with the same low-contrast links. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 05:26, 26 September 2018 (UTC)

Wikiscan Statistics[edit]

For general information. A statistics of this site is available here, maintained by Wikimedia France. Hrishikes (talk) 03:31, 27 September 2018 (UTC)

thank you. here are some old format, continuously updated stats https://tools.wmflabs.org/phetools/stats.html -- Slowking4SvG's revenge 13:37, 27 September 2018 (UTC)

hyphenated words[edit]

Just FYI: Such usage is broken now due to phab:T104566 change in proofreadpage (it was "queen mother" in transclusion before by change). Probably some review of pages ending with hyphen (minus) is needed. Ankry (talk) 22:27, 29 September 2018 (UTC)

Er, you mean a hyphenated word broken at the hyphen at the page break? Like mother-in-law? You can use the {{hyphenated word start}} and {{hyphenated word end}} templates for that. Eg. If mother-in-law is broken like 'mother-' and 'in-law', then you can do: {{hws|mother|mother-in-law}} and {{hwe|in-law|mother-in-law}}.
So for queen-mother it would be {{hws|queen|queen-mother}} and {{hwe|mother|queen-mother}}.
Unless I've misunderstood what you're getting at? --Mukkakukaku (talk) 23:02, 29 September 2018 (UTC)
@Mukkakukaku: I mean, that the hyphen is now removed by software. So if it is intended to remain, its usage is broken. Ankry (talk) 23:06, 29 September 2018 (UTC)
In most cases, the removal makes things working as an editor intended however (as most hyphens at the end are missing {{hws}}/{{hwe}}). Ankry (talk) 23:08, 29 September 2018 (UTC)
I'm still not sure what you're getting at? I've looked and it appears to be working as expected, and as we've described it at Help:Formatting conventions (section "hyphenated end of page words"). Do you have an example where it's not working this way? --Mukkakukaku (talk) 03:16, 30 September 2018 (UTC)
@Mukkakukaku: The change is this: say the word is beautiful. On first page end, you can write beauti- and on next page start, -ful. No template required. On transclusion, it will become beautiful. But for rendering actual hyphenated words like mother-in-law, you'll still need template use (hws/hwe). This is an alternative method. The templates still work. Hrishikes (talk) 03:51, 30 September 2018 (UTC)
Ankry is trying to say that originally there was written "queen -" on one page ane "mother" on the other, which rendered "queen - mother". However after the change in proofreading software it renders "queen mother", which is wrong, and so he changed it using the template hws. His suggestion that all pages ending with a hyphen should be reviewed because of the change and possibly also corrected in the way he did here which should have probably been done immediately after the change) sounds reasonable to me. --Jan Kameníček (talk) 07:12, 30 September 2018 (UTC)
There is also the possibility of trailing hyphens wither within or at the end of dialog. We may need to look for those as well to be certain they are not affected. --EncycloPetey (talk) 15:25, 30 September 2018 (UTC)

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

Hi, this is a message by Can da Lua as discussed here for wikisource communities

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

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

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

Please share this information with your community.

MediaWiki message delivery (talk) 10:28, 30 September 2018 (UTC)

So no more {{hws}} except for special cases maybe. This is great! Maybe we can get something done about the em dashes ending at the end of the page also? Make it default join the words with the em dash intact? Jpez (talk) 11:16, 1 October 2018 (UTC)
Except now apparently we'll need to template the opposite use case, right? So instead of the hyphenated word start/end templates which would collapse the hyphen, we'll now need something to preserve the hyphen? (And, more complicatedly, will now have to go find all the places where we were relying on the old behavior to preserve the hyphen.) --Mukkakukaku (talk) 05:37, 3 October 2018 (UTC)
For preserving the hyphen, writing &#x2010 and semicolon will suffice, if the hyphen is not part of a combined word. Template use in case of combined word with hyphen. Hrishikes (talk) 15:44, 3 October 2018 (UTC)
I suspect even typing &#45; will work to preserve the hyphen too, won't it? —Mahāgaja (formerly Angr) · talk 17:01, 13 October 2018 (UTC)

See Page:Morris-Jones Welsh Grammar 0125.png and Page:Morris-Jones Welsh Grammar 0126.png for what to do if an italicized word is split across a page boundary. The bottom of the first page requires ''gwar- (no closing double apostrophe) and the top of the second page requires <noinclude>''</noinclude>. Then the italicized word appears correctly in both Page: namespace and mainspace. If you close the double apostrophe at the bottom of the first page, the spell is broken and mainspace will show a hyphen followed by a space; see the bottom of Page:Morris-Jones Welsh Grammar 0079.png and its transclusion at A Welsh Grammar, Historical and Comparative/Phonology#80 for an example. —Mahāgaja (formerly Angr) · talk 17:17, 13 October 2018 (UTC)

Breaks around image-pages[edit]

This breaks where there is an intermediate image page, as on The Migration of Birds/Chapter 7. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:17, 9 October 2018 (UTC)

@Pigsonthewing: -- Please check whether it is OK now. Hrishikes (talk) 14:39, 9 October 2018 (UTC)
Thank you. It is, but I was leaving it so others could see the effect. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:47, 10 October 2018 (UTC)

Tech News: 2018-40[edit]

17:35, 1 October 2018 (UTC)

Encrypted PDF of PD book[edit]

The text of this book: [11] is out of copyright (Author:George Bramwell Evens, died 1943) but is only available as an encrypted PDF to "borrow". Does anyone have suggestions for uploading it? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:35, 4 October 2018 (UTC)

Two points:
  • The original work is PD in the UK by the 70 pma rule, but it is PD in the US, as it was first published in 1932?
  • The copy you link to is a 2002 edition, so it's hardly surprised that access is restricted, if it contains copyrighted modern material.
BethNaught (talk) 20:58, 4 October 2018 (UTC)
not renewed here [12]; [13]; [14]; [15]; [16]; [17] and no hits at https://cocatalog.loc.gov/ (after 1978 renewal) = i would say PD-US no renewal - do not see a 1932 scan at Internet Archive; i see there is a copy of 1946 edition at Drew University in New Jersey, and Michigan State University, i can drive down and scan a copy [18] - name your price. Slowking4SvG's revenge 21:44, 4 October 2018 (UTC)
The 2002 edition contains, AFAICT (and I'll check against my paper copy once I can access it), no new material. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:15, 5 October 2018 (UTC)
I see no evidence that it was ever published in the US, so the URAA would have made it publication+95 in the US, or in copyright in the US until 2028.--Prosfilaes (talk) 03:04, 5 October 2018 (UTC)
we can have that discussion on commons. Slowking4SvG's revenge 16:23, 5 October 2018 (UTC)

Problematic PDF: The Migration of Birds - Thomas A Coward - 1912[edit]

There is a problem with File:The Migration of Birds - Thomas A Coward - 1912.pdf; please see c:Commons:Village pump#Problem with PDF, and advise if you can. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:35, 5 October 2018 (UTC)

Some of the PDFs are overly compressed for display in Mediawiki. I think that either @Mukkakukaku, @Hrishikes: has fixed some of these previously, I cannot remember whom. We had one in the past couple of months that should be in the archives. We have a section further up to park broken files, for whatever reason. — billinghurst sDrewth 14:32, 5 October 2018 (UTC)
@Pigsonthewing: -- Yes check.svg Done . OCR is not there, however. If you insist on OCR layer, then I'll do some more experiment. Hrishikes (talk) 15:35, 5 October 2018 (UTC)
@Hrishikes: Working well now, thank you, What did you do to fix it? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:17, 5 October 2018 (UTC)
The file was in pdf 1.5 format with compression. I resaved it in pdf 1.4 format without compression. Hrishikes (talk) 02:48, 6 October 2018 (UTC)
I guess it was a similar problem as https://phabricator.wikimedia.org/T203402. --Jan Kameníček (talk) 09:52, 7 October 2018 (UTC)

Licence check: anonymous 1929 Australian article[edit]

Please can someone advise what licence should apply to this anonymous 1929 article, published in Australia: Examiner (Launceston, Tasmania)/1929/"A Romany in the Fields"? If there's a URAA issue, should it be moved to the Canadian site? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:51, 5 October 2018 (UTC)

{{PD-anon-1996|1929}}billinghurst sDrewth 14:26, 5 October 2018 (UTC)
@Billinghurst: Thank you. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:10, 5 October 2018 (UTC)

Index:Telegraphic Code to Insure Privacy and Secrecy in the Transmission of Telegrams.djvu[edit]

Text OCR cleaned up, anyone want to Proofread? ShakespeareFan00 (talk) 21:46, 5 October 2018 (UTC)

Telegraphic Code to Insure Privacy and Secrecy in the Transmission of Telegrams/Amounts[edit]

Mangled page numbers. It seems someone needs to rethink the module, so it is in fact COMPATIBLE with Proofread page, as currently once you are inside a section generated using {{aligned table}} the automatically generated page numbers aren't displayed correctly (Long term issue). ShakespeareFan00 (talk) 10:01, 7 October 2018 (UTC)

As has been discussed for an extended period, within templates put the table row markers at the beginning, rather than at the end. I have never understood why people close with a row open statement, especially at the end of a table, an extra row marker is like "why?" — billinghurst sDrewth 11:47, 7 October 2018 (UTC)
As an extra comment, the template itself says that this is problematic for page numbering, and it is your choice to continue to use the template. — billinghurst sDrewth 11:52, 7 October 2018 (UTC)
Yes, I know.. Sometimes it would be nice to have long term solutions, (It was me that documented the incompatibility originally). ShakespeareFan00 (talk) 12:38, 7 October 2018 (UTC)
The fix you suggest about row openings would need to be made in Module:Aligned table, All other table handling in the work is based on that template. I'm using it rather than direct table syntax because of concerns about transclude limits for table rows.ShakespeareFan00 (talk) 12:44, 7 October 2018 (UTC)
Yes, which is why I haven't fixed it. I can fix templates, LUA is beyond my capacity, or maybe that is my patience-level. — billinghurst sDrewth 13:07, 7 October 2018 (UTC)
Same here. I'll consider if a different approach might work. The work will need to be split into sections anyway.. ShakespeareFan00 (talk) 13:33, 7 October 2018 (UTC)

RFC: Automating "Wikipedia" link in Header if WD main topic is activated[edit]

I have been tromping through transcluding and WD'ing Dictionary of Indian Biography which has been proofread, though predominantly, not transcluded. Quite a number have Wikipedia articles, and it is pretty tiresome to transclude, then add WD, and identify whether they have a main subject link, then have to go back to the biographic article again. Whereas where I have added "main subject" to d:Q57008414, it would be my preference if the database pulled and automagically added the Wikipedia link, rather than the extra edit.

I am trying to identify any downsides to such an approach, and apart from wrong additions (which can equally happen here. About the only one that I can identify is if someone added more than one main subject, where we would be forced to choose one (if rank preferences where used), or maybe choose none, though mark as problematic and needing resolution. Otherwise, I am unable to identify major stumblings.

@Samwilson, @Mike Peel: from your WD experience, I am guessing that this is a relatively easy data pull. [Mike this happens through {{plain sister}} which is embedded within {{header}}, and in the main ns is an indirect pull as it is a many to one relationship, unlike {{author}} which plain sister does as a straight pull of the interwiki data).

So I am seeking the community opinion on

  1. their thoughts on automating the linking;
  2. any hurdles for implementation; and
  3. the technical aspects for implementation.

Thanks. — billinghurst sDrewth 11:37, 7 October 2018 (UTC)

(comment) I think you mean this property? --Mukkakukaku (talk) 17:51, 7 October 2018 (UTC)

comment[edit]

My first comment is that there already many links in place for Wikipedia, so as we have done for other migrated data, where the the parameter is implemented within the existing header it overrides any WD data pull. This approach allows projects to work out what they wish to do with their data. This allows us to identify where we have overrides in place (current situation for images and dates of life). — billinghurst sDrewth 11:43, 7 October 2018 (UTC)

  • Pictogram voting comment.svg Comment I can't see any issues where the data item will have a single "main subject" for biographical articles, but aren't there situations where we would pull information that isn't suitable, say for non-biographical non-dictionary data items? Some books will have a "main subject", but the WP article of primary interest is actually the WP article about the book, and not the article about the book's subject. --EncycloPetey (talk) 19:12, 7 October 2018 (UTC)
    Fully agree about biographical/people. Maybe that is part of our decision-making process. If it is "edition" d:Q3331189 it should one path, if it is an article, it should follow another path. Let us try mapping these. — billinghurst sDrewth 03:00, 8 October 2018 (UTC)
    This does not account for editions of articles though, nor articles which themselves have wikipedia articles. In my opinion, we should either a) have the article's wp link override the subject's wp link, or b) have two wp links (like how we have two commons links for gallery and category), or c) not use plain sister but perhaps have a special template for such cases. —Beleg Tâl (talk) 11:27, 8 October 2018 (UTC)
    Not just "editions" but also versions pages and translations pages for works, which will have any of several possible values for "instance of" (novel, poem, short story, etc.) --EncycloPetey (talk) 22:04, 9 October 2018 (UTC)
    Further to this, there are some works with multiple "main subjects", and this will need to be accounted for. —Beleg Tâl (talk) 00:15, 8 October 2018 (UTC)
    I am guessing that multiple main subjects is due to there being no single useful subject. To me, if one is given priority (higher ranking) then we show the preferred, if two are equal, maybe we ignore them., or maybe we flag them for review, and again not displayed. — billinghurst sDrewth 03:00, 8 October 2018 (UTC)
    An alternative: create a wikidata item for the group of multiple subjects and link to that from the article. —Beleg Tâl (talk) 11:27, 8 October 2018 (UTC)
    I think that this alternative happens from case 3 of flag as problematic, with an fix eventuating. — billinghurst sDrewth 14:23, 8 October 2018 (UTC)
  • The code for this is demo'd at User:Mike Peel/main topic - for Dictionary of Indian Biography/Aliverdi Khan, {{User:Mike Peel/main topic|qid=Q57008414}} will show Wikipedia, and if used without a QID then it will follow the page's sitelink. It should be straightforward to migrate this to Lua and to embed it into the appropriate templates directly (it's basically a couple of Lua module calls and an if statement - just written in parser functions rather than lua right now). Thanks. Mike Peel (talk) 07:00, 10 October 2018 (UTC)
    But, as noted above, this creates more than a few problems that have yet to be solved. --EncycloPetey (talk) 14:00, 11 October 2018 (UTC)

BHL IDs[edit]

The w:Biodiversity Heritage Library is a rich source of out-of-copyright texts, and a good ally for Wikimedia projects. We store BHL author IDs in Wikidata, as P:4081. Can we add these IDs to {{Authority control}}? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:58, 8 October 2018 (UTC)

Looks like a change to Module:Authority control, which seems rather straight-forward. --Mukkakukaku (talk) 23:56, 8 October 2018 (UTC)
@Pigsonthewing: -- Yes check.svg Done . It needed change in the module, not the template. Hrishikes (talk) 15:22, 9 October 2018 (UTC)
Looks like it's working; thank you. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:15, 10 October 2018 (UTC)

Tech News: 2018-41[edit]

23:38, 8 October 2018 (UTC)

Google Books PDF[edit]

What's the best way to upload the PDF available here - do we have a tool for that, like ia-upload? Note that it includes a Google Books cover sheet. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:48, 9 October 2018 (UTC)

@Pigsonthewing: -- It can be done with url2Commons tool. Hover the cursor over the "Ebook - Free" notice, then right click the pdf option and copy the link address. Use this as the url in the first box of url2Commons. Use the main Google Books address as the source url in the second box. OAuth authorization will be required. OAuth often shows failure in case of this tool. It is false failure. Keep the OAuth screen as it is and go to the tab having the tool window to complete the transfer. If you want to remove the frontsheet, you will need to download, edit and re-upload. Hrishikes (talk) 15:06, 9 October 2018 (UTC)
@Hrishikes: Thank you. The simulation failed, complaining about an invalid URL. I trimmed the "?" and everything after it, and then the simulation worked, but the upload failed with " ERROR: null". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:52, 9 October 2018 (UTC)
@Pigsonthewing: -- c:File:A Discourse on the Emigration of British Birds.pdf -- Hrishikes (talk) 16:19, 9 October 2018 (UTC)

Notable printers[edit]

The plate at Page:The birds of Tierra del Fuego - Richard Crawshay.djvu/180 (like others in the same work) was printed by West Newman & Co. I have created a Wikidata item for that company, d:Q57166684. What's the best way to link them? I've used {{Reasonator}}, for now, but am open to counter suggestions. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:25, 9 October 2018 (UTC)

We have created portals for some publishers, no problem for doing that for printers, though that has usually been for complete works. If it is just the images, then maybe Commons alone is sufficient. No need to replicate what is done better elsewhere. — billinghurst sDrewth 22:05, 10 October 2018 (UTC)

Index:Charlesjarrot nytimesarticle1907.jpg[edit]

I was just attempting to validate this single page article, but have encountered an issue where the source image text is cropped early. I found a link referencing back to the original source page (https://timesmachine.nytimes.com/timesmachine/1907/02/04/106705459.pdf) where the complete text can be found.

I have added in the missing few lines of the article, would somebody be able to recreate the source image for this page using the above link so that it can be completed?

Thanks Sp1nd01 (talk) 14:30, 9 October 2018 (UTC)

Yes check.svg Done -Einstein95 (talk) 22:11, 9 October 2018 (UTC)
Thank you! Sp1nd01 (talk) 07:50, 11 October 2018 (UTC)

Two-page table[edit]

The Migration of Birds - Thomas A Coward - table from pages 92 + 93.jpg

I should be grateful if someone could verify the table on Page:The Migration of Birds - Thomas A Coward - 1912.pdf/114, which also incudes data from Page:The Migration of Birds - Thomas A Coward - 1912.pdf/115, and advise on formatting. I have created a single image, above, to aid this.

Is this the best way to show a table which runs horizontally over two pages? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:45, 9 October 2018 (UTC)

For maps and tables that spread, it does sound best to handle them on one page, and comment on the second. It is one of the adaptations that makes sense to me. — billinghurst sDrewth 22:02, 10 October 2018 (UTC)

Match and Split bot[edit]

As reported by both @Jasonanaggie and @Beleg Tâl on Wikisource:Bot requests, the Match and Split functionality is not currently working. Going to @Phe-bot's page (https://tools.wmflabs.org/phetools/match_and_split.php) says match_and_split robot is not running. Please try again later. @Phe has been pinged at least twice about this. -Einstein95 (talk) 20:45, 9 October 2018 (UTC)

He has been active on another wiki recently, I have asked there if he was no longer supporting the tool whether it is something that we can migrate. — billinghurst sDrewth 22:00, 10 October 2018 (UTC)

Descriptions from Wikidata[edit]

In {{author}}, can we pull |description= from the English-language description in Wikidata, if there is no locally-entered value? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:14, 10 October 2018 (UTC)

It is my understanding (from an earlier time) that we cannot pull the description from the description field. We decided to not pull the occupation alone and continue to add our own description. <shrug> — billinghurst sDrewth 21:59, 10 October 2018 (UTC)
I am sure that's not (or is no longer) the case; no doubt User:Mike Peel can advise. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:29, 11 October 2018 (UTC)
As Mike is busy, @RexxS: for help, please. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:55, 14 October 2018 (UTC)
Try (for George Orwell, Q3335):
  • {{#invoke:WikidataIB |getDescription |qid=Q3335 |wikidata}} -> English author and journalist
Documentation is at Module:WikidataIB #Function getDescription. You could use it in a template something like this:
  • {{#invoke:WikidataIB |getDescription |qid={{{qid|}}} |{{{desc|wikidata}}} }}
That takes optional parameters |qid= and |desc=. If qid is omitted, then it uses the current page; while desc is a local description, which overrides the wikidata. You can supply |desc=none if you want to suppress the description. HTH --RexxS (talk) 17:51, 14 October 2018 (UTC)
I have poked it into template:author/sandbox with an example visible in special:diff/8873313. I haven't done an example where we have no description, and pull from WD. — billinghurst sDrewth 20:29, 14 October 2018 (UTC)
Question, do we wish to track where we have used the WD description? — billinghurst sDrewth 01:53, 15 October 2018 (UTC)
@Pigsonthewing: It is only technically possible, and a fine idea. One of the benefits of having WD fill in blank fields is that the usual names of authors, as given in citations or a user's search, could be spilled out as synonyms of the author page's title here. — CYGNIS INSIGNIS 11:33, 14 October 2018 (UTC)
Additional comment: What would appear in the description field here that is not data or facts, better served at the respective sister sites? Errant content forking across wikimedia is one of the things WD can resolve, and there is no mechanism to address it here if a description or fact is given without references other than bluff. I would prefer that author pages function as a library index card, merely links to sources with all relevant and labelled data providing disambiguating context for the reader. — CYGNIS INSIGNIS 04:22, 15 October 2018 (UTC)
The descriptions at Wikidata are sometimes too brief, sometimes overly verbose. We do often want information in the description such as pseudonyms, pen names, other forms of their names, as well in some cases tha names of close colleagues, family members they might be confused with, or information specific to their status as author rather than whatever else they might be known for. I've seen all of these things and more placed in our descriptions, but they are not generally included in the description field at Wikidata. Neither can we wikilink or bold portions of text pulled from the Wikidata description. --EncycloPetey (talk) 04:27, 15 October 2018 (UTC)
I was not very clear on how I think the pages should be configured, it is very different to the individual creation and maintenance of the information by users here. A key point in my upcoming proposals is that labelled data is the solution to untidy workarounds and verbosity. That information is available in other statements at the the WD item with a reference, each site and reader would be able too choose a preference for what is displayed by default and an opportunity to gather or access further information. This allows any whim to be fulfilled by being able to create a query across wikimedia: are there incomplete books here or at commons, who are the coauthors, who are the notable collaborators, what was their birth name …? I cannot think of an example of an author page I created or modified here that required a unique and unreferenced description, only those that required me to manually copy paste data from other sites, — CYGNIS INSIGNIS 05:52, 15 October 2018 (UTC)
And you will still be able to do all of those things. Using Wikidata descriptions would be a mere fallback, for where none is provided locally. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:00, 15 October 2018 (UTC)
Pictogram voting comment.svg Comment There will be some situations where we want more information than is in the description, and there are some authors for whom the description maintained on Wikidata does not meet our needs, but for the majority of situations, I don't see why we wouldn't want to do so. --EncycloPetey (talk) 15:35, 14 October 2018 (UTC)
Yes, I did specifically say "...if there is no locally-entered value". But where we currently have none, surely something from Wikidata is an improvement. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:54, 14 October 2018 (UTC)

Natural History of the Nightingale[edit]

Natural History of the Nightingale is ready for a second set of eyes, if anyone has time to kindly check it over. There is a gallery of images of the original publication on the talk page.

It's quite complex, being originally spread over two issues; and a lengthy footnote, that includes a subordinate footnote. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:01, 10 October 2018 (UTC)

Is there a reason this wasn't worked as a transcription project using those images in an index? --Mukkakukaku (talk) 03:05, 15 October 2018 (UTC)
There is potential for improvement, I would be proof reading it now if the images were in index, but if a knowledgeable user with access to hathi trust were to bring it over … Is there a reason why that would not be the simple solution? — CYGNIS INSIGNIS 06:26, 15 October 2018 (UTC)
A perhaps not-so-elegant solution(?): Create a single PDF file using the available images, upload to IA, then Commons &c. Unless IA is *still* not generating DjVu files? Londonjackbooks (talk) 06:57, 15 October 2018 (UTC)
Another solution is to check if the file is already hosted IA, but I can't do that and type this message. I'm also limping along on an antique that is allergic to pdf, as am I, limping and allergic. It's a quandary … CYGNIS INSIGNIS 07:25, 15 October 2018 (UTC) P.S. A very enjoyable text, Andy, nicely sourced, transcribed and linked. Any note within a note will resolvable in the Page: namespace, but I'm wondering if another was missed; a dagger † often refers to the second footnote of a page, following the use of an asterisk * — CYGNIS INSIGNIS 07:44, 15 October 2018 (UTC)
Couldn't find it at IA searching text. It would be doubtful anyway (wouldn't it?) for both sections to be pieced together at IA unless someone had taken the pains to do so. I am limping, but my computer is not; and neither of us are (is?) allergic. I can't get to it this minute, but maybe later today, unless/until someone else gets to working out a solution. Londonjackbooks (talk) 07:54, 15 October 2018 (UTC)
Is the watermarking problematic? I can't do anything about that for most images. Londonjackbooks (talk) 08:35, 15 October 2018 (UTC)
Went ahead and uploaded a file to IA. Don't see a 'regular' djvu file derived (forgive my questionable terminology). I have failed in the past to to the pdf to djvu conversion via Commons (or wherever)... If we can get it to Commons, I can set it up here, but confess I have yet to learn how to do match and split (not without an offer to help). Soup sandwich I am :) Londonjackbooks (talk) 17:11, 15 October 2018 (UTC)
DjVu file is now at Commons. Will create an Index here. Londonjackbooks (talk) 05:50, 16 October 2018 (UTC)
What is the point of this, when the work is already proofread and published? I simply asked for someone to "check it over". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:12, 16 October 2018 (UTC)
I don't regard it as obligatory, although I presonally have a strong preference for localised images. The few times I proofread something the old way did not encourage me to do it again (most users cut/paste gutenberberg texts), but I have checked thousands of pages since. This includes a couple of small improvements to this text, that I frankly would not have bothered to do if were not for the scan. Secondly, verifiability, crucial to the work we do here, confirming that the text matches makes it easier for London, for example, to find all the things I miss. — CYGNIS INSIGNIS 17:13, 16 October 2018 (UTC)
Some even {{ls}}eem to be po{{ls}}{{ls}}e{{ls}}{{ls}}ed of a different {{ls}}ong from the re{{ls}}t, and contend with each other with great ardor.
Proof reading is a bit of a challenge, is the preference that the long esses appear in main? — CYGNIS INSIGNIS 12:18, 16 October 2018 (UTC)
  • Generally preferred not to have long s in mainspace, but it's up to you and the other proofreaders of the work. You can post your discussion and decision here. —Beleg Tâl (talk) 12:33, 16 October 2018 (UTC)
    • Er, as I transcribed and proofread the entire work, isn't it up to me? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:12, 16 October 2018 (UTC)
      • That is the practice, but the guidelines say that deviation from whatever is deemed 'standard'—by consensus or otherwise—is liable to be challenged by others. I've only done one work with long esses, just one mind, the argument against their display became even more persuasive. — CYGNIS INSIGNIS 17:21, 16 October 2018 (UTC) P. S. the reason I ask is that I will need to replace the template with the character, which is trivial when compared with your investment in applying them. — CYGNIS INSIGNIS 17:26, 16 October 2018 (UTC)
        • "I will need to replace..." You will? Why? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:22, 16 October 2018 (UTC)
          • The shorter version of the protracted chapter in WS history is that the template does not display in mainspace [!] unless you install a script to show them, although there was an idea to put another option in the sidebar (maybe this has been implemented). In my view the existence of Template:ls is unhelpful, a user is either using it or not; my recommendation is to always check any template documentation. — CYGNIS INSIGNIS 21:03, 16 October 2018 (UTC)
            • So, no "need" to remove it, then. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:27, 16 October 2018 (UTC)
              • If that is your decision. Just to be clear, I was not proposing to remove it: "I will need to replace the template with the character …", that is, replace the template with the character itself. — CYGNIS INSIGNIS 21:48, 16 October 2018 (UTC)

Big untranscluded works[edit]

I am just looking at some of the untranscluded works that we have, and these are some of the biggies that need addressing

Top 5
Migration from text only to image-based

Probably a couple of thousand pages here. — billinghurst sDrewth 04:59, 11 October 2018 (UTC)

The US Statues are a nightmare because of the weird templates and they use in mainspace. Is there a list of untranscluded works somewhere? I've never found one. --Mukkakukaku (talk) 04:53, 12 October 2018 (UTC)
Also, I'll take a stab at A General History... so we don't all go stepping on each other. :) --Mukkakukaku (talk) 04:54, 12 October 2018 (UTC)
We have category:Transclusion check required which is proofread works with something needing to be done. There is also the active list generated at toollabs:phetools, though that a listing of untranscluded pages, irrespective of the status of the work. — billinghurst sDrewth 05:07, 12 October 2018 (UTC)
i see Confederate Military History is missing 2 volumes, and needs some index love for others. i could scan those volumes at LOC, if there is milhist interest. Slowking4SvG's revenge 03:53, 17 October 2018 (UTC)

Narrow no-break space for contractions?[edit]

This is something I've thought about for a long time and would like to hear what people think. In a lot of old books contractions like 'll for will and 's for is are preceded by a narrow space that never breaks for a new line. Until now I've been deleting the space (or following whatever's the trend on projects that are already well advanced, usually an ordinary space), but felt I should really be using u+202f. Anyway, on this page from Oliver Twist there's a good example of why it's important: "Why, a beak 's a madgst'rate; and when you walk by a beak's order, …" where there's a contrast between the possessive "beak's" and the contraction "beak 's". That page I proofed entering the unicode character directly, and the following page I used the entity &#x202f; … Does anyone have advice on which would be better to use? Or should I just use &nbsp; which would be less confusing for validators? — Mudbringer (talk) 01:58, 12 October 2018 (UTC)

I think that any of those options are acceptable so long as it's consistent within a work. I personally would probably use nonbreaking space if I were to use a space at all. I like the idea of narrow nobreaking space if you're willing to put in the effort for it. —Beleg Tâl (talk) 23:22, 12 October 2018 (UTC)
For dialectical speech, I tend to use a full space. I tend to treat such instances of elision differently from contractions. I've come across cases where a half-space is used in the source, but also cases where a full space is inserted. There are also situations where "connecting" the two parts with a non-breaking space would imply a connection not implied in the source text. For example, consider the final paragraph on this page, especially the phrase fellers 'll which is divided between two lines in the final paragraph. Using a non-breaking space when the source text allows for a line break in such a place would not be faithful to the style in which the original was printed. --EncycloPetey (talk) 01:43, 13 October 2018 (UTC)
Thank you both for the comments. The example from Red Badge of Courage is very interesting. In that work I found 'd 'll 'm 'n 're 's 've with elided initial vowel, which all appear both connected with the previous word and with an intervening space, often for the same combination of forms, such as we 're and we're. The only example of one of those appearing following a line break is the case of feller 'll that you pointed out. In Oliver Twist there's also variation between inserting spaces before these forms and joining them to the previous word, but I can find no cases in the three volumes where they appear after linebreak. …… Does anyone directly insert no-break spaces, or is it better to use the html entity? — Mudbringer (talk) 15:29, 13 October 2018 (UTC)
I would look at later editions of the same text for clues to transcription, the fashion for thin spacing to indicate a semantic distinction from a regular space did n't last. I have seen them slipped in and out to aid with the justification of the text block, as if the typesetter was in two minds about the whole business. The trend for justified text (i.e. flush left and right margins), which lasted much longer, was always going to confound the practice; requiring variable width 'full spaces' to be read as distinct from the thinnest space between the type. — CYGNIS INSIGNIS 00:04, 14 October 2018 (UTC)

Portal:Renaissance texts[edit]

We were lacking a Portal for the Renaissance period from our list at Portal:Era, so I began one.

Anyone with an interest in texts from this period (c. 1420-1630) please feel welcome to improve the meagre start that I've made. --EncycloPetey (talk) 00:13, 14 October 2018 (UTC)

Cool image[edit]

Proofread heart.jpg

Kudos to our friends on the Polish Wikisource for creating this image! Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:37, 15 October 2018 (UTC)

Support ends for the 2006 wikitext editor[edit]

This toolbar is being removed from MediaWiki.

The 2006 wikitext editor will be officially removed next week, on the normal deployment train (i.e., Wednesday, 24 October 2018 for the Wikisources). This has been discussed since at least 2011, was planned for three different dates in 2017, and is finally happening.

If you are using this toolbar (and most of you aren't), then you will be given no toolbar at all (the 2003 wikitext editor). This default was chosen so that your editing windows will open even faster, and to avoid cluttering the window with the larger toolbars (a particularly important consideration for Wikisource's PagePreviews). Of course, if you decide that you would prefer the 2010 or 2017 wikitext editors (or a gadget like WikEd), then you are free to change your preferences at any time.

Although it is not a very popular script overall, I know that some editors prefer this particular tool. If you are one of its fans, then you might want to know that some long-time editors are talking about re-implementing its best features as a volunteer-supported user script. I believe that any announcements about that project will be made at mw:Contributors/Projects/Removal of the 2006 wikitext editor. Whatamidoing (WMF) (talk) 17:48, 15 October 2018 (UTC)

Tech News: 2018-42[edit]

22:40, 15 October 2018 (UTC)

Frankenstein, or the Modern Prometheus (Revised Edition, 1831) chapter links[edit]

I changed the fake ToC on the main page to use {{AuxTOC}} and changed the links to point to arabic numeral numbering rather than roman, eg. "Chapter 4" over "Chapter IV". Only issue now is, the old pages are at "Chapter IV" but there are already existing, non-scan-backed pages named with the roman numerals so I am unable to move the page over it (due to lacking permissions). Can someone either move the pages or do a mass edit of the non-scan-backed pages (1-24) to basically contain the content from the recently made pages (I-XXIV) and redirect the roman numeral pages to the arabic numeral ones? -Einstein95 (talk) 03:05, 16 October 2018 (UTC)

Done.— Mpaa (talk) 20:20, 17 October 2018 (UTC)

Patrolling[edit]

Recently I've been noticing IP edits that have been "patrolled" by someone but which included changes to the text so that the Wikisource copy no longer matched the source text.

Wikisource copies must match the source text in matters of spelling. So if someone changes the spellings in a document, and the text no longer matches the source, it is not OK to let that edit stand and mark it as "patrolled". The change should be undone, and a courtesy notice given to the IP (or any editor) regarding Wikisource and fidelity of the text. --EncycloPetey (talk) 02:27, 19 October 2018 (UTC)

I will typically go down the list of unpatrolled recent changes, marking everything I've seen as patrolled and keeping problem pages open in tabs to be dealt with later as a batch, sometimes after a break. I believe I always get around to it if noone beats me to the punch, the case that prompted this was something I came back to look at just now, to find you addressed it, and then found this. I've tried other ways of doing patrolling, like not marking the edit as patrolled until after it's corrected, but I wasn't able to keep up with the volume of edits any other way. If this is more harm than help, I'll stop patrolling, although I would like to be assured that other people will take care of it. Prosody (talk) 05:12, 19 October 2018 (UTC)

Bilingual book[edit]

One of the books I am considering to upload and proofread is Modern Czech Poetry, ed. Paul Selver, 1920. The book contains a collection of poems of Czech writers in original Czech language on one page and the English translation of the opposite page, see https://archive.org/details/modernczechpoetr00selviala/page/12 . The editor probably wanted to present readers both versions and so it seems to me that we should also present here the English translation together with the original poem. What do you think, is it a good idea or should only the English translation be added to the English Wikisource, as original Czech version belongs to the Czech Wikisource?

If both versions could be added, what would be the best way of their transclusion to the main space, so that they stayed next to each other? --Jan Kameníček (talk) 08:07, 19 October 2018 (UTC)

--Jan Kameníček (talk) 08:07, 19 October 2018 (UTC)

@Jan.Kamenicek: Multilingual works belong at mul:. —Justin (koavf)TCM 08:16, 19 October 2018 (UTC)
Thanks for the answer. I have looked at it and it seems to be a strange site to me. The main page is just a disambiguation page referring to various language wikisources including en.ws and many others. After a long time I found a list of languages included at mul and it seems it is intended for some minor languages, but not for English or Czech. I am trying to browse the site but I am completely lost there, unable to find any local rules or whatever. If the work really belongs there, I am afraid it would be completely lost there with a minimal chance to be found by readers (as the main page sends readers somewhere else) and so it seems a loss of time adding it there. So if the Czech text should not be here at en.ws, I will add just the English versions of poems. --Jan Kameníček (talk) 08:40, 19 October 2018 (UTC)
@Jan.Kamenicek: OldWikisource (the multilingual Wikisource) serves several purposes: one is to be the landing page for Wikisource in general, just like how https://wikibooks.org/ introduces Wikibooks and https://wikivoyage.org/ does for Wikivoyage. Another is to hold material for languages with very small literature corpuses (e.g. some dead languages or Papamiento which is generally only spoken and not written). A third is to act like incubator: where a language subdomain can "graduate" to its own site. Finally, it hosts multilingual works, such as s:mul:Index:Festival Romanistica.pdf or s:mul:Hail Mary or s:mul:Index:Boletín RAE VI (1919).djvu or s:mul:Bukvar staroslovenskoga jezika glagolskimi pismeni za čitanje crkvenih knjig. —Justin (koavf)TCM 02:07, 20 October 2018 (UTC)
@Koavf: I see, thanks for the explanation very much, now I understand it better. The biggest problem I see with this site is that it was necessary to explain it at all, as the reader does not get this information on the main page and in fact I did not find it even after quite a long time of searching. I was not able to find any page explaining the system of the site, its rules, anything. As a reader I am directed to various single-language sites and do not get the information that multi-lingual works can be found there and how/where I can find them. So I got the impression that adding there some work is like throwing it into a black hole :-( --Jan Kameníček (talk) 07:20, 20 October 2018 (UTC)
@Jan.Kamenicek: If the work is a collection of single-language works, rather than a single multi-language work, this is frequently handled by splitting the content between enWS and the relevant language WS. For examples, have a look at my laWS user page. — If the text is completely parallel, it may also be acceptable to only transcribe the English content and leave the rest to other editors; see Index:Aida Libretto English.djvu and Index:National anthem act Canada.pdf. — You may also find the templates documented at Template:Iwpage/doc useful. —Beleg Tâl (talk) 12:18, 19 October 2018 (UTC)
@Beleg Tâl: I see, thanks. I just thought that as the editor of the book wanted to present the English readers the English translation of the poems along with the original text, we could keep the original text too. But if you feel it is better to add only the English text as in your examples, it is fine to me as well. --Jan Kameníček (talk) 12:28, 19 October 2018 (UTC)
@Jan.Kamenicek: I think it is (always) better to have both the English text (on enWS) and the Czech text (on czWS). You will see that the examples I gave on my laWS user page (especially The seven great hymns of the mediaeval church where the original and translation are presented in parralel) are like this: the English and Latin texts are both present and accounted for. The last two examples were provided because you said "I will add just the English versions of poems". If you are not comfortable working in multiple wikisources, it is completely acceptable for you to only do the English parts and to leave the Czech part for someone else at a future time. For example, I did this with Aida, because I don't speak Italian and was not comfortable trying to work on itWS. —Beleg Tâl (talk) 12:54, 19 October 2018 (UTC)
@Jan.Kamenicek: You can have a look at this work. Hrishikes (talk) 12:58, 19 October 2018 (UTC)
@Hrishikes: I don't know if this is the best method for this particular collection. I thought we generally discouraged formatting these works in parallel like this, except where it is clearly inappropriate to separate the original from the translation. —Beleg Tâl (talk) 13:16, 19 October 2018 (UTC)
@Beleg Tâl: As for cs.wikisource: the poems are much older than this bilingual publication, so it would be much better to add them to cs.ws from the original Czech sources (in fact some of them are already there). Besides that, there is no clear consensus on cs.wiki as for using proofreading extension and the index and page namespaces. Inf fact conservative local admins oppose it very much and discourage contributors from using it, and I gave up fighting with them. Another problem is technical: cs wikisource uses a lot of templates which are not compatible with en.wikisource environment. Once I tried to transclude something from there to en.ws and failed for this reason.
So I personally do like the solution suggested by @Hrishikes:. --Jan Kameníček (talk) 13:32, 19 October 2018 (UTC)
  • I see no reason to exclude part of the work, and would think that can be duplicated at the Czech wiki source. The attempts to avoid this situation just begets problems, and putting it where it won't be seen is unhelpful. Notwithstanding some questionable interpretation of a rule inferred from the historical split of the wikisource library, the complete text can be welcomed at this site; here is a featured text Le Corbeau that displays both languages (having just restored that version from "experiments" and an undiscussed revert). It is preferable that users concern themselves with solutions to matters that have defined and undesirable consequences, Yet again I ask, what are those consequences in this situation? — CYGNIS INSIGNIS 08:12, 20 October 2018 (UTC)

Hi all, on other Wikisources (at least the French, the Latin, the Breton and the Multilingual - that I know of), we put each parts of a multilingual book in the corresponding Wikisource (with all the templates and tools to make it easy and smooth). Is it not the rules also on the English Wikisource? (if not, it will create problem for bilingual books containing English, like on Le Corbeau where I thought I was applying the usual formatting to only discover afterwards that I was not by Cygnis insignis). Cdlt, VIGNERON (talk) 12:43, 20 October 2018 (UTC)

Pagelist checking...[edit]

Category:Index - File to check

Any chance of this being emptied by the end of the year? I'd done a few more, but the remainder are ones I don't necessarily feel happy about doing the page-listing for various reasons. ShakespeareFan00 (talk) 09:19, 19 October 2018 (UTC)

A Hundred and Seventy Chinese Poems[edit]

This work has already been fully transcribed years ago, but there are still many pages that need to be created for individual poems (see red links in the contents). Isn't there an automated way to do this? Thanks ~ DanielTom (talk) 20:16, 19 October 2018 (UTC)

The automated way to do it is transclude the entire work to that page. The ToC can then link to the page further down, which is easily done by wrapping the page numbers with the wikicode #170|. If someone then wants to make 170 redirects or versions, that full transclusion need not wait and will still return a search result. — CYGNIS INSIGNIS 08:27, 20 October 2018 (UTC)
I have done the single-page ones. I did a few a couple of the multi-pages ones but I stopped as I was unsure how to fix <poem> across pages (you can follow my traces in Page ns to see my fix). If someone more familiar with poems could take a look, I appreciate.— Mpaa (talk) 14:46, 20 October 2018 (UTC)