User talk:ShakespeareFan00

From Wikisource
Jump to navigation Jump to search

Coral Island

Reverting the chapters to the pre-match and split doesn't help anything. The Match-and-split text is the exact same unsourced text that was present there before. The Match-and-Split process takes the text from the Mainspace pages and inserts it into the Page: namespace pages. So reverting those changes does not fix anything. It's just the same unsourced text whether it's transcluded or not. --EncycloPetey (talk) 20:14, 4 July 2023 (UTC)[reply]

The reason for going back to the pre split version, was that you'd raised concerns that they were not necessarily the same edition. I am well aware that it doesn't 'fix' the text. I also undid a number of other splits I'd done, on the basis that I would not have time to work on them right now. ShakespeareFan00 (talk) 20:17, 4 July 2023 (UTC)[reply]

Alexander and Dindimus (Skeat 1878)

I notice that there are four pages starting from Page:Alexander and Dindimus (Skeat 1878).djvu/151 which are not linked from the index page. Are those pages needed ? -- Beardo (talk) 19:00, 20 July 2023 (UTC)[reply]

No, They are blank "overscans" and should not be transcluded. ShakespeareFan00 (talk) 19:41, 20 July 2023 (UTC)[reply]
Are they needed for anything ? Or should they be deleted ? -- Beardo (talk) 20:35, 20 July 2023 (UTC)[reply]
They can be safely deleted. You my wish to check Special:LonelyPages for other 'overscans' . ShakespeareFan00 (talk) 20:38, 20 July 2023 (UTC)[reply]
Will you put them up for deletion, or shall I ?
Yes, that special was how I came upon these. There are currently only 11 on with "Page" prefix on that list. -- Beardo (talk) 21:21, 20 July 2023 (UTC)[reply]
Feel free to do the cleanup :) ShakespeareFan00 (talk) 21:41, 20 July 2023 (UTC)[reply]

Named vs. unnamed params

What's the reasoning behind this? Xover (talk) 10:02, 3 August 2023 (UTC)[reply]

@Xover:. Parameter 2 was showing up as unrecognised in the TemplateData analysis script I was using, So I updated the wikitext to use the documented, height param. I'll update the TemplateData. ShakespeareFan00 (talk) 10:07, 3 August 2023 (UTC)[reply]


I noticed you removed this template from many images. Should I do the same for the String Figures and How to Make Them images? The Eloquent Peasant (talk) 18:52, 22 August 2023 (UTC)[reply]

If they are not a Djvu file , yes. ShakespeareFan00 (talk) 18:55, 22 August 2023 (UTC)[reply]

please focus your lint activity to the content spaces

Please will you stop flying around people's user and user talk pages just because a page appears on the lint special pages. What makes you think that it is okay for you to just edit people's pages as there is an html/coding error on a page. What is the purpose? Seriously, what are you achieving? We don't typically go and fix red links, grammer, etc., so unless there is a real burning issue, just leave them. Stop being sucked in just because it appears on a list. — billinghurst sDrewth 22:28, 10 September 2023 (UTC)[reply]

Noted. I've already expressed my views about this previously. ShakespeareFan00 (talk) 22:40, 10 September 2023 (UTC)[reply]
If you like I can start undoing every single edit, but that would only create 'noise'.ShakespeareFan00 (talk) 22:41, 10 September 2023 (UTC)[reply]
It would indeed create noise, so please don't start mass undoing your edits unless there is a very good reason to do so. Xover (talk) 05:37, 11 September 2023 (UTC)[reply]
@Xover: I have undone a number of non-content namespace edits already, because I effectively lost confidence in the stability of the repair based on subsequent concerns. As an admin you are welcome to reinstate any "good" fixes, provided that you can personally justify the attempted fix that was being attempted. Priority should of course be given to 'structural' repairs (unclosed tables and unpaired 'block' tags.) ShakespeareFan00 (talk) 05:48, 11 September 2023 (UTC)[reply]
I'd also appreciate someone making sure I don't make a fool of myself due to over-confidence.ShakespeareFan00 (talk) 05:48, 11 September 2023 (UTC)[reply]
One of the current batch of repairs (not reverted) which seems to be contentious when performed outside of content-namespaces, were the attempts to resolve unterminated <p> tags in decades old welcome messages to User talk pages. As I stated on your user talk page in response to a related query regarding misnested tags, I stated I am more than happy to revert any edits I make (or have made). ShakespeareFan00 (talk) 06:00, 11 September 2023 (UTC)[reply]
As attempting non-content namespace "linting" as a non-admin is considered to be controversial currently, I'll go back to 'linting' Content namespaces, effectively doing a plain-text proofread of pages I find. Do you have a list of 'in-progress' items you were working on so I don't conflict with specific focus you had? ShakespeareFan00 (talk) 06:00, 11 September 2023 (UTC)[reply]

@Xover: I need a way forward on this, and won't be reverting any more edits, However I would really appreciate someone (with the authority to do so obviously) reviewing the attempted fixes, and if they were 'sensible' delints reinstating them (with the appropriate authority to do so). I have always tried to act in good faith, and the delinting efforts were done with this in mind, and so as to reduce a backlog that had in some places seen no reduction efforts in at least 5-6 years. Until I started looking at de-linting, I got the distinct impression there had not been a visible systemic effort at all. ShakespeareFan00 (talk) 08:51, 11 September 2023 (UTC)[reply]

DNB errata

As when this issue has come up before, I am doing nothing to interfere actively with the format on the page. It must be my browser, or suchlike. There are actual corrections to be made on the three pages. Since it appears I cannot fix them, I would ask you to look at the diffs and sort them out. Charles Matthews (talk) 13:14, 15 September 2023 (UTC)[reply]

Mpaa had already corrected these. If they are still "wrong" take it to the Scriptorum, as an edit/revert cycle is not the way to reach a soloution for this.ShakespeareFan00 (talk) 13:28, 15 September 2023 (UTC)[reply]

Custom font on The Urantia Book

Hi! I saw you reverted a change here, on The Urantia Book. I'm trying to clean this up, but am still new to Wikisource. Can you help me confirm my interpretation of WS:STYLE? I've been removing the custom font forced by <div style="font-family:georgia,times;"> from all Pages of this book. Here on this one page I think I just missed a closing </div> tag. But if I'm off base on this in my validation, please let me know. Brad606 (talk) 23:07, 30 September 2023 (UTC)[reply]

Ah Okay. if you are stripping the custom formatting Proceed. ShakespeareFan00 (talk) 23:08, 30 September 2023 (UTC)[reply]
Copy that, thanks! BTW, was this detected with a linting check? If so, which one? I 'd gladly check for any mismatched tags I introduce after an proofing/validating session. Brad606 (talk) 23:11, 30 September 2023 (UTC)[reply]
Yes it was found with a lint check. I have some lists of highly specfic lint checks on some page generally if interested in doing some cleanup more generally? (You might need specific experience in certain languages though)ShakespeareFan00 (talk) 23:18, 30 September 2023 (UTC)[reply]
Thanks. For now I'll focus on cleanup of this one work. It's an enjoyable way to gain skill/experience on WS. It's already motivated me to fork typoscan.js to look for some problems specific to this work; hopefully these are improvements and I'm not making the text worse! Brad606 (talk) 23:29, 30 September 2023 (UTC)[reply]

Creating a table with a central border only

Thanks for helping in the "Report of the Commission of Enquiry North Borneo & Sarawak.pdf". I tried to create a wikitable for the data in the report as shown in this page: Page:Report of the Commission of Enquiry North Borneo & Sarawak.pdf/88 but I have to use style="border:none;" multiple times in each cell to remove the right cell border. Is there any simple way to apply this change across the whole table? Any help is very much appreciated. Thank you. Cerevisae (talk) 11:03, 2 October 2023 (UTC)[reply]

You can setup a CSS Style for your table. 11:12, 2 October 2023 (UTC)
Thanks for the info! Cerevisae (talk) 20:49, 2 October 2023 (UTC)[reply]

Hi. I've just spent 2 hours fiddling with tables for the vowel section and now run into a page save conflict. Let's coordinate - I honestly don't mind who goes but it's silly to be stepping on each other's toes. We can split the book by section or I can do the validation stage if you feel strongly about it - I note you were there first, way back. Cheers Helrasincke (talk) 22:59, 6 October 2023 (UTC)[reply]

I hope you don't mind me overwriting your edit though, since I'd already done the formatting. Feel free to improve on it of course. Helrasincke (talk) 23:03, 6 October 2023 (UTC)[reply]
@Helrasincke: Fair enough. I was trying to resolve some pages that seemed out of sequence. If you were already working on this, I can back off. ShakespeareFan00 (talk) 06:34, 7 October 2023 (UTC)[reply]
@ShakespeareFan00 Yeah that's because the old file had a bad page, so I swapped the files. I'm on it, cheers. Helrasincke (talk) 07:53, 7 October 2023 (UTC)[reply]

Using <p> as a single tag.

This is a confusing issue for me, because HTML uses <p> single tags. See a bookmarks.html file, where I learned from. I understand your edits, but the double tag also doubles the space between paragraphs. I must research this again for a definitive answer as it relates to our Wikisource proofread page.

It is just a matter of having the time to do it. The best source would be MDN The Mozilla Development Network web documentation — ineuw (talk) 10:28, 7 October 2023 (UTC)[reply]

There is also {{pbri}}, but you had concerns about my use of that previously for the same reasons. Of course if there was an ability to have proper P wrapping inside references (sigh) ... ShakespeareFan00 (talk) 10:31, 7 October 2023 (UTC)[reply]
Our posts crossed: element p first on their list. — ineuw (talk) 10:33, 7 October 2023 (UTC)[reply]
I would strongly suggest looking at {{pbri}} as I've added a pusedo-class to it just now. This means that you could set-up an Indexstyle, to set inter-paragraph spacing inside references rather quickly, and have that spacing remain fixed, across a whole work. It would only be a medium-term solution until the Mediawiki devs come up with a long-term block level footnotes implementation (as opposed to the current span-based one.) ShakespeareFan00 (talk) 10:37, 7 October 2023 (UTC)[reply]
I will try it, thanks. — ineuw (talk) 10:42, 7 October 2023 (UTC)[reply]
You'd need something like
.reference-text .__pbreak{
line-height: 0.9em /* Set inter-paragrpah spacing here */
Possibly, but I'm open to the pbri template being re-worked at some point, given that the default 1em line height I'm using isn't ideal.
ShakespeareFan00 (talk) 10:47, 7 October 2023 (UTC)[reply]
Thanks, I set it at .5em and it looks good for me|
Cleanup is progressing. I attempted some repairs for other things I noticed at the same time. Pausing for a moment as I need a break, but I will continue later. ShakespeareFan00 (talk) 16:28, 7 October 2023 (UTC)[reply]

Make the list work PROPERLY

Hi, You edited a page I worked [[1]], with your comment being the subject of this message (caps included). You replaced it with tagging I've never seen—not a problem at all, but having been doing this for less than a year, I'm amazed that the tagging you used is not listed anywhere in the instructions for beginning editors, even though it would be easily understood (and this tagging is not the only one; I was told by one editor with quite a bit of time on this site that using the hws/hwe is not necessary; if that is so (and it appears to be so), why do instructions for new users not include this very relevant bit of information?). I realize complete documentation is not your responsibility, but I'm just passing on my experience as a relatively new user—though I AM an very experienced technical writer/editor. Maybe you know the right people to talk to about this.

Back to the page you edited. Your comment that the change was done to 'make the list work PROPERLY' confuses me. What was done in the way I tagged it to prevent it from working correctly? I really hate doing something incorrectly that someone else has to fix, and I don't want to repeat my errors again. Thank you for your time sir/ma'am. snafu22q (talk) 17:47, 27 October 2023 (UTC)[reply]

Nothing you did.. It was a reminder to myself to make sure I'd put the {{ }} braces in. ShakespeareFan00 (talk) 17:51, 27 October 2023 (UTC)[reply]
The list syntax I used is still "experimental" , hence it's not widely used, and thus would not be in the documentation.
ShakespeareFan00 (talk) 17:51, 27 October 2023 (UTC)[reply]
Ah, OK. Just wanted make sure I wasn't creating work rather than doing work.
Is it ok for me to use that syntax? And just to verify, the *!/spage tagging is essentially 'start page at', correct?
Thank you for your time. snafu22q (talk) 18:03, 27 October 2023 (UTC)[reply]
Feel free to use that syntax, but bear in mind it's experiemental nature. and yes *!/spage is start of list on page. for a continued 'item' use *!/c ShakespeareFan00 (talk) 18:23, 27 October 2023 (UTC)[reply]
I hate to bother you with this, but in that same experimental syntax for a bullet—is there a way to change the character used for the standard bullet? I have the need for a circle bullet (same document, page 10) and I'm wondering if there is a way to implement that with this syntax. Thanks. snafu22q (talk) 06:50, 30 October 2023 (UTC)[reply]
Please read - and You will then need to set an appropriate IndexStyle, for wst_ulist.__circlebullet such as:-
list-style-type: circle;
list-style-image: none;

You then use __circlebullet in the class parameter of the opening template for the list concerned. ShakespeareFan00 (talk) 07:32, 30 October 2023 (UTC)[reply]

Me again, in reference to Letter to David S. Ferriero on the topic of January 6. Contacting you directly since I'm using that experimental tagging, though I don't think the problem I'm having has anything to do with it.
Looking at the transcluded text, please note the indenting issues I'm having at [11]. This in itself is odd—where it indicates page 11 starts is actually on page 10 (page 11 starts at the 4th item—where the indent issue is. Regardless of that, I can't figure out why the indents are not the same AND why there's that extra half line between the 2nd & 3rd item.
Also, the indents on [13] are way off from the rest of the lists, even though the tagging seems to be the same on the previous & subsequent pages. A conundrum wrapped in an enigma. snafu22q (talk) 09:02, 25 November 2023 (UTC)[reply]
Thanks—I won't bother you again.
snafu22q (talk) 06:58, 26 November 2023 (UTC)[reply]



Can you please check if {{pbri2}}, which I based on {{pbri}} has any validity using this? <span style="line-height:2lh;"><span>

I want to create vertical space which is double the line height specified (1.2lh), in the {{fs85/s}}{{fs85/e}} enclosing surrounding text.

While {{pbri}} provides a fixed line height based on 100% font size regardless of the font-size it is embedded in?

Progressive reduction of the line height of an empty row is only relevant with font sizes less that 100%. Also, proportionate reduction of the line height, starting from <100% font-size already exists {{ppoem}}. — ineuw (talk) 20:07, 29 October 2023 (UTC)[reply]

Also see , for a slightly tweaked approach. ShakespeareFan00 (talk) 20:48, 29 October 2023 (UTC)[reply]
I will check quickly, but I would suggest paging someone like Xover if you want a full blown technical assesment. You might also need other CSS. If pbri doesn't have a height option, it should be added.

I will also note that lh unit values might not be that widely supported.

ShakespeareFan00 (talk) 20:13, 29 October 2023 (UTC)[reply]
Sorry, but lh units aren't supported on my browser. Your coding approach looks correct though. ShakespeareFan00 (talk) 20:25, 29 October 2023 (UTC)[reply]

Template:RunningHeader/1 revert

Regarding this revert. It would be a lot more useful if you explained somewhere what broke, how it broke, and where you observed the breakage. That way it is possible to fix it and progress. Without such details a revert just becomes a stone wall to further changes. You also reverted within a minute of the change, so if there were related changes that needed to be made (or even just page caches to purge) there would have been no time to do them. Unless the problems you observed were very critical (very visible, high impact, etc.) my suggestion for the future would be to raise the problem on talk first, and discuss the best way to fix it. It could still be reverting, but it also could mean a simple tweak to whatever the desired change was. If what broke was high-impact a revert would of course be appropriate, but then followed up with a talk page message explaining it. As I once wrote to the NLS contributors: a revert is sort of like harsh language in the real world; it might be appropriate in some situations, but then you'd best make sure everyone understands that you're not cussing them out.

PS. {{RunningHeader/1}} currently looks likely to be entirely obsoleted by the main {{rh}} in the migration to a Scribunto module. If you have any specific concerns about that, or there's a good reason for a separate template to exist, now would be a good time to flag those issues so they can be taken into account. I see the purpose of the template was questioned on its talk page back in July, and I am similarly having trouble understanding what the use case for it is. Possibly just because I'm being a dummy of course, but if so I'd appreciate being educated. :) Xover (talk) 07:32, 13 November 2023 (UTC)[reply]

@Xover: - What was happening was that the {{rh/1}} was appearing on the left of pages, rather than centered. What I suspect is that the module isn't applying the same styles. You point out that the use of the template was questioned back in July. I have no objections to {{rh/1}} being deprecated, provided that ALL it's uses get replaced at the same time. The reverts made on individual Page:'s where to do with consistent styling across those specfic works. The original intent was so that for some works single page numbers could be consistently styled, without the need for a 3 param {{rh}} with blank parameters, and if the styling needed changing later, so that one style line in an IndexStyles page could be tweaked, as opposed to 10-20 Page: footers. ShakespeareFan00 (talk) 08:33, 13 November 2023 (UTC)[reply]
The edit summary I'd left on my Page: reverts was "This was rh/1 in line with all the other page numbering in this work. If you are going to deprecate rh/1 please use a talk page to explain what you are doing.". If there's a desire to simplify things, I can fully support that. ShakespeareFan00 (talk) 08:35, 13 November 2023 (UTC)[reply]
Ah, thanks, I just saw the template revert and that just said Please test more robustly. This change broke stuff... If the only purpose of {{rh/1}} is to get a single centered cell (i.e. what {{rh| |42| }} would give you; the typical bottom-of-page page number) then I think either {{rh| |42| }} or {{rh|42}} is the right interface for that rather than a separate sub-template. My working theory is that we can make {{rh|42}} do what rh/1 does and {{rh|42|Chapter 3}} do what rh/2 does, or at least be treated identically to {{rh| |42| }} and {{rh|42| |Chapter 3}}. I just need to be sure I understand what people are using rh/1 and rh/2 for first. Xover (talk) 08:46, 13 November 2023 (UTC)[reply]
That's logical, but someone would need to check for existing 1 param and 2 param {{rh}} usages, because until the recent proposed changes/simplifciations , a 3 or 4 param behaviour was assumed to be the default, and thus params may have been omitted in existing usage. Marking out {{rh/1}} ,{{rh/2}} and to some extent {{rh/5}} and higher values behaviours explicitly, is to me clearer as to the desired header style. I'm all for simplifications, provided that there is eventually ONE consistent way it's done, and that the existing non-conformant uses get updated to ensure that.  :)
ShakespeareFan00 (talk) 09:01, 13 November 2023 (UTC)[reply]
Yes, the rule for this I am thinking of is that the number of parameters passed decides how many cells you get out, and if you want nothing in a cell you pass it as an empty parameter. That's a simple 1:1 rule that can be memorized and applied to all variants of this.
I'll need to check whether there are any uses of {{rh}} that omits empty parameters and relies on a three-cell default, and whether any such can be cleanly migrated. At the moment I am not seeing any use for rh/1 etc. and other such specialized templates for number of cells, but that could of course change as I see cases in the wild. Xover (talk) 09:24, 13 November 2023 (UTC)[reply]
In respect of single param {{rh}} usage -*%29%5C%7D%2F&title=Special%3ASearch&profile=advanced&fulltext=1&ns1=1&ns2=1&ns3=1&ns4=1&ns5=1&ns6=1&ns7=1&ns8=1&ns9=1&ns10=1&ns11=1&ns12=1&ns13=1&ns14=1&ns15=1&ns100=1&ns101=1&ns102=1&ns103=1&ns104=1&ns105=1&ns107=1&ns114=1&ns115=1&ns710=1&ns711=1&ns828=1&ns829=1&ns2300=1&ns2301=1&ns2302=1&ns2303=1 (Around 1700-1800 uses :( ) ShakespeareFan00 (talk) 09:38, 13 November 2023 (UTC)[reply]
Even worse than that, I'm afraid! In the Page namespace, there are at least 2559 results for \{\{[Rr]unning[\s]?[Hh]eader\|([^}|]*)\}, plus 1706 results for \{\{[Rr][HhFf]\|([^}|]*)\}, and both of those searches timed out. —CalendulaAsteraceae (talkcontribs) 15:52, 15 November 2023 (UTC)[reply]
{{Rh/2}} For example here - Page:Moll Flanders (1906 edition).djvu/34 has a different 3rd parameter which is used to determine which 'cell' get's expanded. If there was a straight conversion then you'd end up with :



rather than as shown in the page concerned.

I can appreciate this different param usage is perhaps confusing, and so welcome simpliifciation efforts.ShakespeareFan00 (talk) 09:01, 13 November 2023 (UTC)[reply]
{{rh/2}} has no third parameter and assigns no special meaning to "l" or "r" that I can see. What's happening there is that the third parameter (the "l") is being ignored because there are only two cells. But if {{rh}} was changed such that if it only gets passed two arguments it will output them left and right aligned (possibly with an empty middle cell, possibly without), would that cover your use case? Xover (talk) 09:18, 13 November 2023 (UTC)[reply]
It wouldn't. the usage of {{rh/2}} has recto-verso behaviour currently, compare the headers on
Page:Moll Flanders (1906 edition).djvu/34 and Page:Moll Flanders (1906 edition).djvu/35 , so the third paramater IS being interpreted somewhere. The naming is confusing and should be revised. (See also {{rh/1lr}} and {{rh/1rv}} for simmilar naming cnofusions.. ShakespeareFan00 (talk) 09:26, 13 November 2023 (UTC)[reply]
No, it's just the order of the arguments; /34 has page / title and /35 has title / page. Both output two cells, and the third argument is ignored.
The automated recto—verso variants are a different problem for which I've not looked closely at solutions yet. I'm betting there's a way to generalize them significantly, but perhaps not fully since there are a lot of variations in these. The possibility of using Index CSS for formatting is going to help a lot here I think. Xover (talk) 09:55, 13 November 2023 (UTC)[reply]
That was my view as well, thanks for looking into this. ShakespeareFan00 (talk) 15:55, 15 November 2023 (UTC)[reply]
@Xover: I've done a review of invocations of {{rh/2}}, and as far as I can tell, Index:Moll Flanders (1906 edition).djvu is the only instance of this problem. Could you do a bot run to fix it? —CalendulaAsteraceae (talkcontribs) 16:34, 15 November 2023 (UTC)[reply]
@CalendulaAsteraceae: Remove the "l"/"r" arguments? Or convert it to {{rh}}? If we change {{rh}} as outlined above it would be {{rh|146|THE … FLANDERS}}, but with the current behaviour it would be {{rh|146||THE … FLANDERS}} (with an empty center cell). I think we need to decide the path forward before we start running a bot over it. Xover (talk) 21:28, 15 November 2023 (UTC)[reply]
@Xover: Just remove the "l"/"r" arguments, so we can handle it with the rest of the {{rh/2}} uses later. —CalendulaAsteraceae (talkcontribs) 21:29, 15 November 2023 (UTC)[reply]
@CalendulaAsteraceae: Done Xover (talk) 07:54, 16 November 2023 (UTC)[reply]
That said, I do think that the updated {{rh}} template should, when passed only two arguments, output them left- and right- aligned, without a middle cell (which is what {{rh/2}} does right now), and once the main template has been updated, we'll be able to replace {{rh/2}} with {{rh}}. —CalendulaAsteraceae (talkcontribs) 02:26, 16 November 2023 (UTC)[reply]
Hmm. A recto—verso running header with chapter or work title in the center and the page number on whichever side is the outer edge of the leaf, is conceptually a three-cell running header (the side without the page number is there, it's just empty on that particular page). If that's the base assumption we can free up two-cell running headers to be just left + right aligned. Do we have any edge cases that complicate this? Xover (talk) 08:03, 16 November 2023 (UTC)[reply]
I haven't come across any yet. (Different text alignment can of course be handled with index CSS.) —CalendulaAsteraceae (talkcontribs) 16:45, 16 November 2023 (UTC)[reply]

The Bartered Bride (1908)

Hello. I have revisited this work which I added a long time ago and noticed that the layout of the subpages like The Bartered Bride (1908)/Act first got completely broken after some changes of yours. I do not want to revert it simply, because I suppose you wanted to achieve something, so can you have a look at it and correct it, please? -- Jan Kameníček (talk) 21:09, 20 November 2023 (UTC)[reply]

Feel free to revert. I don't at first glance see WHAT broke. ShakespeareFan00 (talk) 23:14, 20 November 2023 (UTC)[reply]
@Jan Kameníček: Please be more specfic. Exactly what got "completely broken" because I am not seeing it. ShakespeareFan00 (talk) 23:22, 20 November 2023 (UTC)[reply]
Hm, that is strange, after the revert it looks the same, i. e. the headings are not centered in proportion with the left-aligned columns, so something else must have happened. I need to have a look at it in detail, which I will do soon. I will consider dropping the multicol as you suggested. I used it because it is easier to compare the transcribed text with the original, because without the columns the text gets too long, it even gets out of the screen, which makes any checking against the original very difficult. --Jan Kameníček (talk) 23:52, 20 November 2023 (UTC)[reply]
I don't see any obvious layout problems on that page currently (Safari on macOS). In Page: namespace the minor headings are slightly offset due to the pilcrow markers, but in mainspace they appear fine. The multicol stuff doesn't work well with any of the constrained-width layouts, but in any of the full-width ones it looks fine to me. Unless you've already fixed whatever it was it's either at least partially dependent on web browser or it's subtle enough that I don't notice it (which is maybe a low bar :)). Xover (talk) 06:42, 21 November 2023 (UTC)[reply]

Yale Shakespeare

If you run across a similar issue in a Yale Shakespeare volume, you can always ask. Since I'm familiar with the formatting, I can probably spot the issue faster. --EncycloPetey (talk) 20:04, 15 December 2023 (UTC)[reply]

Noted. The subsquent speakers in Italics also look off in the transclusion.. ShakespeareFan00 (talk) 20:05, 15 December 2023 (UTC)[reply]
What looks off? Where? I don't understand. --EncycloPetey (talk) 20:07, 15 December 2023 (UTC)[reply]
The alignment of the speakers in italics looks like it's offset after the extended speech by Trin. ShakespeareFan00 (talk) 20:08, 15 December 2023 (UTC)[reply]
It is, and it's supposed to be. Poetical lines and prose lines are formatted and indented differently from each other in the FF and in the Yale editions. --EncycloPetey (talk) 20:09, 15 December 2023 (UTC)[reply]

{{img float}} template use

Hi and Happy New Year. Just FYI I have fixed Page:EB1911 - Volume 07.djvu/128, your last edit broke the image display. I can see now I didn't terminate the {{small-caps}} properly in my 2021 edit — but at least the image displayed OK :) — DivermanAU (talk) 14:39, 7 January 2024 (UTC) DivermanAU (talk) 14:39, 7 January 2024 (UTC)[reply]

I just fixed another broken {{img float}} edit of yours, Page:EB1911 - Volume 16.djvu/153. — DivermanAU (talk) 15:59, 7 January 2024 (UTC)[reply]
Don't bother listing them indvidually, feel free to fix away. ShakespeareFan00 (talk) 16:08, 7 January 2024 (UTC)[reply]
No worries, thanks. It was just a reminder really (for myself too!) to check things. Thanks, by the way for the fixes you have made to my edits. DivermanAU (talk) 09:04, 8 January 2024 (UTC)[reply]

Thanks for the Bible pagelist!

I was just about to reluctantly drag myself into editing the pagelist for the ASV Bible I just uploaded, but discovered you beat me to it! This is a huge help, thank you so much! I hope the tedium of tackling a 1300-page pagelist didn't give you a headache!

SpikeShroom (talk) 09:14, 12 January 2024 (UTC)[reply]

Nope. - I use the visual page list script, speeds up things no end. I would strongly suggest setting up common styles though. ShakespeareFan00 (talk) 09:16, 12 January 2024 (UTC)[reply]
What exactly do you mean by common styles? I'm still slowly learning how to use the CSS stylesheet; are there any examples you had in mind?
SpikeShroom (talk) 20:11, 12 January 2024 (UTC)[reply]
I meant setup the IndexStyles before you get too deeply into proofreading. ShakespeareFan00 (talk) 20:14, 12 January 2024 (UTC)[reply]
Ah, gotcha. Yeah, that'll make proofreading easier, thanks for the reminder! SpikeShroom (talk) 22:02, 12 January 2024 (UTC)[reply]

I noticed that you added {{?}} to a bunch of pages in this index. In case you are still working on it, you may find it helpful to know that the requisite symbols are listed on page xix, and on the previous pages it also provides the symbols {{blackletter|G}} (G = Greek), {{blackletter|T}} (T = Targum), {{blackletter|S}} (S = Syriac), and {{blackletter|B}} (B = Vulgate for some reason) —Beleg Tâl (talk) 14:46, 18 January 2024 (UTC)[reply]

Thanks. I'd stopped working on this because my browser doesn't have good support for Hebrew, if you want to continue proofreading and cleanup, feel free. ShakespeareFan00 (talk) 14:48, 18 January 2024 (UTC)[reply]
That's valid. I'm probably going to work on clearing it out of the backlog of Category:Pages with missing symbol characters, but that's as far as I care to go on this project (I don't know any Hebrew anyway) —Beleg Tâl (talk) 14:50, 18 January 2024 (UTC)[reply]

Could you please help with little issue in Trees of GB&I

Hi ShakespearFan,

could you please help me with a little thing in the ToC of Trees of GB&I? On this page I can't find a good solution for the first few entries. As you can see, from the real pages, starting with Fagus, it goes alright, but the first pages, in the "roman" section.... I don't know how to handle that. Do you know how I can make this part of the ToC? I'll be happy to hear of you. Many greetings, --Dick Bos (talk) 17:55, 20 January 2024 (UTC)[reply]

Breaks what?

Heya SF! Long time....

It *might* help me to remember not to do this if I know what it breaks.--RaboKarbakian (talk) 10:36, 27 January 2024 (UTC)[reply]

@RaboKarbakian: putting a trailing |- other than in the header causes the generation of 'fostered content' as the parser doesn't apparently pick up the correct context for end of table marker. This has been a long standing concern that's been around for at least a decade! ShakespeareFan00 (talk) 10:40, 27 January 2024 (UTC)[reply]

bold font in header

Hi ShakespearFan,

may I ask you a question, please. Since a couple of days (or perhaps weeks...), when working in the Page-namespace, the central part of the header shows bold. As far as I can remember this was never the case. Is this the same for you? What has changed? And why? Do you perhaps know? Thank you. --Dick Bos (talk) 17:25, 28 January 2024 (UTC)[reply]

Your WS feature requests at January community meeting

FYI, your agenda items were briefly discussed at the January WS community meeting. They said they'd forward them to Sam Wilson, and they might get discussed at the next meeting (which Sam is more likely to attend). I asked if there's a formal process for raising, discussing, voting on, and selecting feature requests, and it seems like there isn't. There certainly is a large backlog, though. Brad606 (talk) 16:53, 30 January 2024 (UTC)[reply]

Yes, that's a known process weakness. There is the community Wishlist, but that generally doesn't involve Wikisource compared to bigger projects. ShakespeareFan00 (talk) 16:54, 30 January 2024 (UTC)[reply]

Alternatives to font-old

CalendulaAsteraceae (talkcontribs) 02:48, 31 January 2024 (UTC)[reply]

I see that you mention that the source file was deleted at Commons. Do you know what can be done about this ? There are now hundreds of orphaned Pages lacking scans. -- Beardo (talk) 20:40, 2 February 2024 (UTC)[reply]

Talk to Commons. I requested it be localised , but it got deleted anyway. ShakespeareFan00 (talk) 22:43, 2 February 2024 (UTC)[reply]
You could upload the djvu from locally. ShakespeareFan00 (talk) 22:45, 2 February 2024 (UTC)[reply]
Thanks for sorting that out. -- Beardo (talk) 00:13, 3 February 2024 (UTC)[reply]

Confusing edit

Why does {{uc}} need an empty second parameter? (koavf)TCM 11:45, 12 February 2024 (UTC)[reply]

Okay it seems that the rgexps I was using to change {{rh}} to current usage failed. I'll have to review everything again. I will be rather busy. Apologies.ShakespeareFan00 (talk) 11:46, 12 February 2024 (UTC)[reply]
Pobody's nerfect. Let me know if I can help (tho I am going to sleep now). —Justin (koavf)TCM 11:55, 12 February 2024 (UTC)[reply]
If you want to check my recent back 'minor' edits feel free. I'm just not feeling very confident about doing reapirs at the moment. Of course if someone wrote a bot that did the migration "properly", without me needing to write the regexp (badly) to do it...
ShakespeareFan00 (talk) 11:59, 12 February 2024 (UTC)[reply]

Recent *!/c template edit

@ShakespeareFan00 Although I can't be 100% certain, your recent edit of Template:*!/c seems to have changed its behavior in the Page namespace when a list spans a page break. See the top of Page:The Urantia Book, 1st Edition.djvu/134 and Page:The Urantia Book, 1st Edition.djvu/75 as two examples. I don't recall seeing numbered items carrying over at the top of this like this when I first published the edits to make these numbered lists.

Also possible I'm using this template incorrectly, or I shouldn't be using it at all. Any advice? Brad606 (talk) 23:51, 14 February 2024 (UTC)[reply]

Award yourself a Proofreading star.. typo found and fixed. ShakespeareFan00 (talk) 00:05, 15 February 2024 (UTC)[reply]
Great, thanks! I'll just pat myself on the back for now; the star will be for when I finish validating this giant first work I've taken on haha Brad606 (talk) 00:12, 15 February 2024 (UTC)[reply]

Thank you

...for showing me by example the {{*!}} family of templates. Super useful! -Pete (talk) 18:03, 15 February 2024 (UTC)[reply]

Page numbers and SCOTUS cases

Hey... noticing you've been reformatting the Supreme Court cases I've been working on and moving the page numbers to the side. The WikiProject page says the page numbers need to be like this [p1] in the text to facilitate more accurate citations. I could be wrong but I'm trying to maintain the standard that was set. Just wanted to let you know, have a good one! JoeSolo22 (talk) 16:04, 18 February 2024 (UTC)[reply]

@JoeSolo: Ah okay. Feel free to revert then. ShakespeareFan00 (talk) 16:06, 18 February 2024 (UTC)[reply]
Thanks! JoeSolo22 (talk) 16:07, 18 February 2024 (UTC)[reply]


Hello, I am just wondering because I saw you changed dhr into dhri in pages in Index:Poems Osgood.djvu. What does it do or change? — Alien333 (what I did and why I did it wrong) 16:42, 7 March 2024 (UTC)[reply]

{{dhr}} cannot be used inside {{Ppoem}} due to HTML structuring rules. I used the SPAN based DHRI I created a few months ago instead. ShakespeareFan00 (talk) 16:55, 7 March 2024 (UTC)[reply]
Ok. It seems to work with dhr, though. (for example here). Alien333 (what I did and why I did it wrong) 17:01, 7 March 2024 (UTC)[reply]

Is this page needed for anything ? -- Beardo (talk) 17:21, 22 March 2024 (UTC)[reply]

This looks like a work specific template that was meant to be subst. I've no objections to it's removal provided it's function is met by other means. If you are doing a cleanup and consolidation, feel free. ShakespeareFan00 (talk) 18:24, 22 March 2024 (UTC)[reply]

Sorry to bother you, I haven't been uploading anything for a while and now I am having a problem I cannot clearly identify, wiith the index of the newly uploaded file in subj. Would you please take a look? BR, ̴Tar-ba-gan (talk) 14:52, 23 March 2024 (UTC)[reply]

@Tar-ba-gan: Invalid interval problem fixed. Unfortunately, Commons is having some problems right now with its files as they translate to other wikis. See Wikisource:Scriptorium/Help#Trouble_with_file_from_commons. SnowyCinema (talk) 03:48, 24 March 2024 (UTC)[reply]
Thanks a lot for fixing itǃ ̴̴̃ Tar-ba-gan (talk) 04:45, 28 March 2024 (UTC)[reply]

Page:2019SouthDakotaConstitution20190107.pdf/46-48 numbered paragraphs

HI, I hope I am doing this right, as I have never "talked" before. I noticed the changes you made after I made changes, rendered it to PDF to see if all was well, and found the numbers of the items were all cut off in the left hand margin using -2em! I changed it to -1em and it lines up perfectly with left hand margin in pdf version, although indentation shows in the index pages. Go figure! ^^ Ta, sacle1 Sacle1 (talk) 22:02, 24 March 2024 (UTC)[reply]

This seems to be a duplicate of Alexander and Dindimus/Endnotes, which is the version linked from the main page. Which should be kept ? -- Beardo (talk) 19:50, 31 March 2024 (UTC)[reply]

Style - vertical align

Will this edit force everything to be vertically aligned to the top? If so, then the edit is incorrect. --EncycloPetey (talk) 00:48, 7 April 2024 (UTC)[reply]

Those style rules would have made the contents of every table cell vertically aligned to the top, iff the table had class="_valign" applied. No table in Index:Sophocles - Seven Plays, 1900.djvu has that class so it had no effect. But you can use that snippet for three-column tables of contents (chapter no + chapter title + page no.) and then combine it with one of the ways to make the last column align to the bottom (align with the end of the possibly-wrapped chapter title). For tables without a lot of exceptions I'd recommend ._toc tr td:last-child {vertical-align: bottom;} (adding a _toc class to the table), but {{ts|vbm}} should work too. Xover (talk) 21:10, 7 April 2024 (UTC)[reply]

Is that edit supposed to do anything? I've tried it myself, but it seems to have no effect on anything. Is it nonfunctional code? --EncycloPetey (talk) 20:07, 7 April 2024 (UTC)[reply]

It was supposed to vertically align all the tables in a cell. I removed it as it didn't seem to be doing aything. ShakespeareFan00 (talk) 20:08, 7 April 2024 (UTC)[reply]

Romance of the Rose: Moving side headers

Hello, I appreciate you monitoring my work and making corrections with some formatting issues, but it will cause a bit of a problem for me if I have to go back and change all of the side headers. It makes more sense to me to put them according to the sense of the text rather that at a top of a "page" where there is no top of page in the transcluded version. This has been my consistent practice and I would prefer to stick with it. Like images, I contend that it sometimes makes better sense to shift the position a bit.

Thank you for considering my point of view in this matter.

11:54, 13 April 2024 (UTC) PWidergren (talk) 11:54, 13 April 2024 (UTC)[reply]