User talk:JesseW

From Wikisource
Jump to navigation Jump to search

Welcome :-)

I notice you mention that you are a contributor to groklaw as well; I have in the past raised the possibility of working with groklaw; see Wikisource:Scriptorium/Archives/2007-10#How Wikisource helps US legal professionals. Perhaps you have idea's on how to establish a bridge between the two communities. John Vandenberg (chat) 09:16, 26 January 2008 (UTC)Reply[reply]

GFDL switch to CC-by-shareAlike[edit]

Oh, this switch will be a problem to wikimedia projects, thanks man, Shooke (talk) 20:15, 20 January 2009 (UTC)Reply[reply]

Gday. We have the template {{textinfo}} which we add to the Talk page of a work where we record the information about source and other miscellaneous detail. To point to the talk page we use the template {{edition}} which is added into the Notes = field with the header. If you are using Firefox or Chrome, you can utilise the preload header gadget it will automagically add the respective header (header (Main), textinfo (Talk), author (Author:)) to the respective namespace. — billinghurst sDrewth 09:31, 14 February 2010 (UTC)Reply[reply]

WP:LAW[edit]

I just saw your topic on WS:BR from a few months ago, so I thought you may be interested in Wikisource:Wikiproject Law. We are currently importing Supreme Court cases from bulk.resource.org (see the status here), and we have plenty of federal cases and statutes ahead of us. We would be glad to have your help proof reading, importing content, or working on tools (such as automated categorization or citation linking—I see you have some experience with python!). Cheers, stephen (talk) 08:33, 3 March 2011 (UTC)Reply[reply]

... link and ... lkpl templates[edit]

To flag that we have internal link templates for our regularly referenced works for use on author/portal pages, and similarly intra-work articles. — billinghurst sDrewth 22:46, 26 July 2020 (UTC)Reply[reply]

@Billinghurst: -- wait, what? I think I'm lacking sufficient context here. JesseW (talk) 23:43, 26 July 2020 (UTC)Reply[reply]
Author:Thomas Frewenbillinghurst sDrewth 06:44, 27 July 2020 (UTC)Reply[reply]
Ah, I see that you added {{DNB link|Frewen, Thomas}} there -- thank you. And I am familiar with Category:internal link templates (I actually tried to subdivide it, but ran into problems updating the categories). I'm not sure what you mean about {{link}} and {{lkpl}}, though, which don't seem to exist? JesseW (talk) 16:49, 27 July 2020 (UTC)Reply[reply]

I've restored the above index, but I don't know how to link it to Page:Desert News Mona Lisa article.png/1. You would have to ask User:Billinghurst what to do as he knows how to deal with images. --kathleen wright5 (talk) 14:49, 6 August 2020 (UTC)Reply[reply]

All looks resolved to me. mul:Wikisource:ProofreadPage is where the information resides for non-(djvu|pdf) images. — billinghurst sDrewth 20:46, 6 August 2020 (UTC)Reply[reply]
Thanks! I don't see any mention about non-(djvu|pdf) images on that page -- can you point it out? JesseW (talk) 20:52, 6 August 2020 (UTC)Reply[reply]
The above index has now been validated. --kathleen wright5 (talk) 01:20, 7 August 2020 (UTC)Reply[reply]

Chapters and use of roman numerals in subpage title[edit]

Hi. The community has a long-formed consensus that all added works should added in the page title with arabic numerals rather than with roman numerals, per the guidance for subpages. Whilst long-standing works have not been moved and there is currently a discussion at WS:S, all newly added works should be following the guidance. At a later tine today, I will move the subpages and update the links. — billinghurst sDrewth 01:54, 17 September 2022 (UTC)Reply[reply]

Sounds good, I'm happy with either way. I was just following the existing pattern with the other stories from that volume. JesseW (talk) 01:58, 17 September 2022 (UTC)Reply[reply]
@Billinghurst: I've moved the pages and updated the links on the ToC. Not having admin rights on WS, I of course can't delete the redirects. Thanks for the ping about the guideline! JesseW (talk) 02:04, 17 September 2022 (UTC)Reply[reply]
Oh, I haven't updated prev/next links on each chapter yet. I'll get to it in a few days if you don't do it first (maybe you have a convenient bot to fix it up?). JesseW (talk) 02:08, 17 September 2022 (UTC)Reply[reply]
I have a bot, though it isn't many, and I am also making the title links to be relative links, which is our preference with subpages, just makes everything easier if ever we have to move/disambiguate. — billinghurst sDrewth 06:38, 17 September 2022 (UTC)Reply[reply]
Oh, and please do not force formatting <div style="text-align:justify">, the purpose of the layouts is to allow people to choose their formatting, or people can do that through their CSS skins. Hence why we have so many relative templates to give the reader their own control. — billinghurst sDrewth 06:45, 17 September 2022 (UTC)Reply[reply]
Yeah, the text-align justify was also a leftover copy from older ones, thanks for catching that. I thought all the links I made already were relative links -- did I miss some? JesseW (talk) 13:04, 17 September 2022 (UTC)Reply[reply]

Question re validation diff[edit]

Hi. Thanks for starting the work of validating pages in Star Lore of all Ages. I had on question in relation to this change though.

I thought the policy was to keep the linebreaks of the proofread text aligned with that of the facsimile, so as to make proofreading and validation easier. But in the linked diff you twice joined two lines. Mainly wondering if there are specific exceptions to the rule or if I somehow misunderstood it. /Lokal Profil (talk) 08:11, 23 September 2022 (UTC)Reply[reply]

My understanding of the guideline is that either way is fine; I've sometimes noticed if the last paragraph on a page has extra linebreaks, it looks wrong, so I have a habit of removing them -- but I'll avoid doing so for Star Lore. Thanks for asking, and for bringing these astronomy books to Wikisource -- they're fun to proofread! JesseW (talk) 18:24, 23 September 2022 (UTC)Reply[reply]
@Lokal Profil: Help:Beginner's_guide_to_proofreading says: "Line breaks can cause problems ... but removing them is a matter for the individual proofreader." and H:LINEBREAKS says: "Remove end-of-line hyphens and line breaks." so I think the current guidance leans more towards removing them. JesseW (talk) 18:32, 23 September 2022 (UTC)Reply[reply]
I think H:LINEBREAKS refers to linebreak characters, but anyhow the approach seems to be more liberal than I thought. No worries, just wanted to make sure I wasn't somehow misformatting the text during proofreading. Thanks for the links! /Lokal Profil (talk) 09:09, 24 September 2022 (UTC)Reply[reply]

WD statement!![edit]

First: Thank you! (for fixing my mistake) This is only a little more than pushing a button, but really meant.

I have yet to use it, but I am a big fan of the WD statement! I read in its history about "unknown value", that is something that should be in the module(s) where it checks for the "object named as" (used to be "stated as"). It would be dreary to have write an if then for every template.

Here "Author string" is, while well-meaning, a pain. When the author is found enough to make the data, "author string" just sits there. And, there is no illustrator string or translator string.

Later in my day, I am going to look to see what you did to make the second quid optional. I looked for it, but clearly not enough. I remember resolving to go back and look for it also....--RaboKarbakian (talk) 15:53, 24 September 2022 (UTC)Reply[reply]

@RaboKarbakian: Delighted to help! Sadly, I couldn't get the unknown value logic to work, as the value doesn't get included until too late for the #ifeq function to be used with it. It may require a Lua module, which I didn't feel like bothering with. I don't understand what you mean about "Author string"? Regarding making the second argument optional -- I just added a default value of empty string (rather than the default default of "{{{2}}}"), which causes the #if to treat it as false. Hope that makes sense! JesseW (talk) 00:51, 25 September 2022 (UTC)Reply[reply]
"Author name string" d:Property:P2093 there is a rule about not using both, one being a searchable replacement for the other. There are a lot of authors there now, but even just a few years ago, not so much. Also, no "translator string", etc. Pulling in the d:Property:P1932 qualifier if it is there might really be a module thing, but it would be nice for it to use "H. G. Wells" and not the full name, for instance.
Another person was complaining that when several names are given, all the names get pulled in but lack the final ", and " grammer. I was just overjoyed that it pulled in all of the names! The other problem with that is when there are more than one author (or illustrator, etc.), it would be nice to exclude the namespace author, avoiding the self linking. As it is, it will not link to the other authors when they exist and that might be a template level thing.
For now, that is all I can remember of wishing it would do and wanting it to be better. And, that is some trick with the blank space! Had there been a more officious way, it would have been documented, I think. My favorite character (where you need it but don't want it to do much} is the &zwj; Zero Width Joiner. The kitchen sink of the entities! --RaboKarbakian (talk) 01:26, 25 September 2022 (UTC)Reply[reply]
Heh, that makes sense. Likely for improvements like that, we'll need a Lua module. JesseW (talk) 01:41, 25 September 2022 (UTC)Reply[reply]

Wikidata templates[edit]

FYI, I think we figured out what the problem is, over on my talk page... it's a "bug" (we'll call it a missing feature) in Module:Wikidata_link. It basically doesn't do the exact inverse of what I thought the problem was, assuming that a sitelink doesn't exist without checking to see if it exists on a linked "Wikimedia category" or "Wikimedia list article" entity.

Like I said over there, this needs someone who knows Lua needs to fix. Since {{wdl}} is used by {{header}}, it's actually a kind of major bug.... I'm sure it's escaped notice this long simply because of the 'lifecycle' of most books that end up here (if someone just uploaded a single copy of a single edition, and brought it over here, the simple way is just 'what works', and not 'wrong'), but when the goal is actually to flesh out and correct the bibliographic stuff on Wikidata..... irony, lol. Anyhow, thanks for commenting over there, I ...how to put it... appreciated the outside feedback. Hopefully I don't need to try to harass people over here to have someone fix it sometime soonish. Since there is no way to see these usages from WD, and I really don't want to go on a rampage of breaking shit here by fixing stuff over there, it's not good.

Just in case you are curious, History of New York State, 1523–1927 (Q114067501) is a good example (IMO) of what I'm trying to do, what books should look like on WD, in terms of fully describing them (including the not-renewed copyright clearance on that one, which I'm currently shoving 100+ plates from onto Commons). I'm not just mangling library catalogs together, I'm actually looking at the damn things, the mangled library catalog stuff is what needs to go away. :) Jarnsax (talk) 04:45, 25 September 2022 (UTC)Reply[reply]
https://en.wikisource.org/wiki/User_talk:JesseW
en.wikisource.org
CC-MAIN-2023-14
99793
application/http; msgtype=response
sha1:CHTCHFCRVRPSOP3X2W7WRSYAGZBSC77N
<urn:uuid:545ab86f-da92-4916-862f-268b48ff6610>
2023-03-31T00:27:32Z
208.80.154.224
text/html
sha1:WV3FZEJCN35BF3IAJP3IKOAZ2HZ2PXPM
<urn:uuid:0975d98a-6aa2-473a-88f3-3c697c04c869>
https://en.wikisource.org/wiki/User_talk:JesseW
response
<urn:uuid:e66d4857-ac01-4b2d-9b8b-148208b76509>
isPartOf: CC-MAIN-2023-14
publisher: Common Crawl
description: Wide crawl of the web for March/April 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-142
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/