Welcome to Wikisource

Hello, Shenme, and welcome to Wikisource! Thank you for joining the project. I hope you like the place and decide to stay. Here are a few good links for newcomers:

 

You may be interested in participating in

Add the code {{active projects}}, {{PotM}} or {{Collaboration/MC}} to your page for current Wikisource projects.

You can put a brief description of your interests on your user page and contributions to another Wikimedia project, such as Wikipedia and Commons.

Have questions? Then please ask them at either

I hope you enjoy contributing to Wikisource, the library that is free for everyone to use! In discussions, please "sign" your comments using four tildes (~~~~); this will automatically produce your username if you're logged in (or IP address if you are not) and the date. If you need help, ask me on my talk page, or ask your question here (click edit) and place {{helpme}} before your question.

Again, welcome! Beeswaxcandle (talk) 05:55, 21 September 2018 (UTC)Reply

Reference markers, etc. edit

Hi, in answer to your question about replicating the * † etc. reference markers used in some printed works. It was a decision made many years ago here to use only wikirefs and thereby to standardise the presentation of references, footnotes and endnotes. For more info see Help:Footnotes and endnotes.

With respect to your other ponders on Page:Natural History, Fishes.djvu/231, the Style guide gives information on ellipses and dashes. The strong preference is to use the characters.

For typographical errors that require noting to the reader use {{SIC|wrong spelling|correct spelling}}. The wrong spelling will display with a light grey underline. Hovering the mouse will reveal the correct spelling. e.g. leearn

Beeswaxcandle (talk) 18:57, 21 September 2018 (UTC)Reply

Caption formatting edit

Hello. Stumbled across your edit summary question, and I tweaked the formatting for the missing image caption at this page. Hope you are enjoying editing Wikisource. Lots of contributors available to help/give suggestions, etc. Londonjackbooks (talk) 20:00, 23 September 2018 (UTC)Reply

P.S. I noticed you have been formatting using {{smaller|{{smaller in captions. If it is your intention to make the lettering smaller than {{smaller}}, then we have {{x-smaller}} &c. I used {{smaller block}} in my edit to the page linked to above in order to achieve the single line space you were looking for, among other reasons. Londonjackbooks (talk) 20:13, 23 September 2018 (UTC)Reply

Okay, thanks. And thanks for the explanation about block. I had seen something like that done by Jasonanaggie and didn’t know why they’d done that. I’ll look again.
Drat, edit conflict wiped my earlier reply, but that’s exactly what I was asking, about the smaller&smaller. Thanks.
But it’s small bits like this, that make me wish there were suggestions or standards under the index talk page, to allow newbies to conform comfortably. After all, each project/book has its subtle oddities…  :-) Shenme (talk) 20:20, 23 September 2018 (UTC)Reply
Each work certainly does have its own oddities! Good insight. The ideal is to match the original as faithfully as possible, keeping in mind we do not have the same limitations found in physical copies of books (where typesetting, etc. is concerned). Much is learned "on the job" here, but there is good guidance to be found. You are always welcome to begin establishing formatting guidelines yourself at the Index talk page. If others come along to edit, it would be good for them to have such guidance so formatting can be uniform throughout the text. Consistency is key. Often, you will find different ways to format the same text. Sometimes there are good technical justifications for certain methods of formatting, and sometimes the choice is merely a matter of opinion as to what formatting is "best" to use... Look/ask around... Find what works, and works for you. Londonjackbooks (talk) 20:33, 23 September 2018 (UTC)Reply

Validating edit

On Wikisource, we mark pages as "Validated" only when all aspects of the page have been corrected. If a page is missing an image, we mark the page as "Problematic", even though we might make corrections to the text. We work this way so that people who edit images can find those pages the require the addition of an image. If a page is "Validated", we assume the image has already been put into place. --EncycloPetey (talk) 01:09, 24 September 2018 (UTC)Reply

Ahhh… I thought I’d been diverted/elated by finding a separate problem on /37, but I did that goof twice. So, thanks for looking out for mistakes. Shenme (talk) 03:07, 24 September 2018 (UTC)Reply

Index lines with multiple page refs edit

Thanks for pointing this out. It seems that the line breaks (which I introduced) caused problems with the index formatting. I have reverted them to spaces.--Keith Edkins (talk) 16:58, 8 October 2018 (UTC)Reply

DMM edit

Hi, I see you're getting involved in A Dictionary of Music and Musicians. The only style guide I've been following for the past 9 years while slowly working on this is detailed at WS:WikiProject DMM.

To answer some of your questions/ponders on User:Shenme/admmv1:

  • List of contributors is already transcluded at A Dictionary of Music and Musicians/List of Contributors
  • {{larger}} is very rare for me to have used in the Dictionary
  • My intention for populating author pages with the articles is once all article pages are proofread and then transcluded, I will then proofread the last few pages in Vol. 4 (The Catalogue) and then transclude the sections from that into the author pages. The reason for waiting is that I'm still not sure what all the articles will actually be called.
  • We don't use "curly quotes" at enWS by policy
  • For the variations in {{rh}} formatting—this is very minor as these are never seen by the general reader after transclusion. If the same word is at the top of both columns, I haven't bothered typing it twice. However, the option with the page number centred is wrong.
  • Collapse all linebreaks within paragraphs immediately. I use a cleanup script that deals with them in one go.
  • Column breaks are not required to be marked—they are a printer's artefact and aren't reproduced in the electronic medium.
  • Section markers. I see from your notes that you're using the so-called "Easy LST" gadget. I think it's turned on by default. I don't use it because it adds complexities to what Help:Transclude calls Advanced Transclusion. As a result I use the <section begin=XXX />Blah<section end=XXX /> structure rather than strewing double-# markers around.
  • In terms of what to use in a section name, the simple answer is: as much as is necessary to be unique for the page(s) on which an article is found. A more complex answer for DMM is that I've been using enough to make sense for whoever is coming behind me to validate.
  • Smallcaps should be used whenever and only whenever the article prints them. This is pretty much restricted to Christian names and internal references to other articles.
  • On the whole misspellings are rare in the DMM. I have only marked with {{{1}}} those that would change the meaning of a sentence.
  • With respect to scores, I would prefer them all to be Lilypond, but there are a few (in Category:DMM pages with score problems) that are defying me at present and we may have to resort to image files in the end.

When transcluding articles, I've set up a special version of the header template called {{DMM}}. Documentation is there on what the fields mean.

That's probably enough to be going on with. I'm watching this page, so feel free to ask me further questions here (or ask for clarifications where I've been too brief in my comments). Beeswaxcandle (talk) 07:56, 9 October 2018 (UTC)Reply


Thank you for your attention. My motivation comes from wishing others avoid the confused search for simple truths, or worse for the project, the need to repair their wrong assumptions. I took up fun here at another project with no style guidelines, and now I see the post-processors undoing various attempts at fidelity. And they’re even jamming in curlies. Confounding that…
A combined master list of contributors all in one page is exactly the kind of greasing the ways that is appreciated by the passing editor. But then, it should be easily locatable/identifiable by that occasional editor.
As a non-expert in most everything, I bring few biases and, more wonderfully, many confusions. Thus I will come up stupid questions which answers might help others. For instance, in the attributions, should the initials be formatted by their sometimes appearance as "R.H.M.B." or, as I suspect, as "R. H. M. B.", and always the latter, for readability. In fact, I’d want to make it so easy for newcomers/occasionals that I’d want to have a list somewhere for the editors like:
{{right|[ [[Author:Addison_F._Andrews|A. F. A.]] ]}}
{{right|[ [[Author:Carl_Armbruster|C. A.]] ]}}
{{right|[ [[Author:David_Baptie|D. B.]] ]}}
usw. so they could just copy-n-paste. Make it so brains are used little for ’how to’ and more for the text.
Being stupid, insane, and sometimes energetic can be useful to others, if directed well. Let’s hope the energy holds out - the rest is incurable. Shenme (talk) 19:28, 9 October 2018 (UTC)Reply
My intention was to put spaces between all the initials in the contributor attributions, regardless of how any individual article might display them. Consistency is important here. Having said that, it's quite likely that I've missed a few and left them unspaced. And I'm happy for the Esq. to be moved out of the links for E. D. et al.
I'm a firm believer when training/mentoring that the only stupid questions are the ones that aren't asked. Having lived and breathed DMM for 9 years means that at times I'm too close to the details to see the inconsistencies. Beeswaxcandle (talk) 06:04, 10 October 2018 (UTC)Reply

pianoforte edit

Best place is to look elsewhere in the same work to see what the editor has done: A Dictionary of Music and Musicians/Pianoforte --EncycloPetey (talk) 04:36, 15 October 2018 (UTC)Reply

Yes, well in doing that I had found the other variations, "Piano-Forte" and "Piano-forte", though in vol 3, and perhaps in a topic referencing the revolutionary ’new’ instrument. I opted for the much more numerous version minus hyphen. I restrict search to just ’page’ and add intitle:"A Dictionary of …" and the keywords searched for. In another project this was useful as the terminology was rather idiosyncratic. Shenme (talk) 04:58, 15 October 2018 (UTC)Reply

Thank you edit

I thank you for notifying me of the error in the Preface to the bee treatise. I do not know why the {{bl}} does not call correctly in the transclusion; I hope that someone who has more knowledge on the matter would go through the index pages and correct the errors. TE(æ)A,ea. (talk) 18:11, 30 November 2018 (UTC).Reply

@TE(æ)A,ea.: your attempt to use a single {{bl}} template across multiple pages is not going to work. Attempting to use <noinclude> on the closing braces is clever but will not fool the parser. You will need to simply split the text into two sections, ending one instance of {{bl}} at the end of one page and opening a new one at the start of the next page. See my fixes on page 43 and page 44. —Beleg Tâl (talk) 15:41, 3 December 2018 (UTC)Reply

the score edit

You did a nice job, at a quick glance. You should move it into place. If I move it into place, it will give the appearance that I know how to use the software and I don't want to leave a wrong message like that.

One of my biggest fears, since becoming involved with the world of software and its people and culture is that I show up unable to do what I have claimed or even guessed I could do. Asking me to move that is asking me to add fire to the stack of kindling which are my worse fears.--RaboKarbakian (talk) 14:09, 8 December 2018 (UTC)Reply

links that work in some places.... edit

Introduction

I don't know if linking this way is helpful here, but it was really helpful with the Plates in the Botany of the Antarctic where separate publications were linked together.

I can provide a better example if you need it.

You are very thorough, especially compared to me. :) --RaboKarbakian (talk) 18:19, 18 December 2018 (UTC)Reply

Antony and Cleopatra edit

The title should display simply as "Antony and Cleopatra". The additional "(1921) Yale" in the pagename is to distinguish it from other works of the same or similar title, but is not part of the title itself and should not be displayed in the header. --EncycloPetey (talk) 05:03, 8 January 2019 (UTC)Reply


If you can do everything else, it's a simple matter for someone to come in afterwards and set up sections and such.

Both Xover and I are familiar with the series format standards for this work. Just notify one of us when you reach the end of an Act in the play, and we can set up the formatting. --EncycloPetey (talk) 01:22, 16 January 2020 (UTC)Reply

Thank you. I am just dropping in to do basic grunt-work, fleeing the world of people for the world of words. The concentration required here is... diverting. Shenme (talk) 02:12, 16 January 2020 (UTC)Reply

Very nicely done! edit

Thank you for transcribing the table on this page. Something I wanted to do, but I didn't have the patience. Much more valuable in this format, though -- nicely done! (I think the image can be removed now, no?) -Pete (talk) 23:58, 19 March 2020 (UTC)Reply

Also, re: your edit summary here: Yes, a searchable/translatable/generally machine-readable caption is ideal. My process with images is: (1) Upload a high resolution, faithful version, loosely cropped (which permits a reuser to make their own edits if they like); then, (2) upload a tighter crop, eliminating the caption and unnecessary white space, and making other edits (straightening, converting to greyscale, removing moire, adjusting levels etc.) to the same file page. With this work, I'm trying to get step (1) done for all files before I make a dedicated effort to do (2); so in the meantime, I suggest putting the captions in by text at Wikisource, and eventually they will not be redundant when the Commons files have been fixed. -Pete (talk) 00:04, 20 March 2020 (UTC)Reply

Your question edit

In answer to your question The American Cyclopædia (1879)/Goethe, Johann Wolfgang von is an old page which has text transcribed directly into the mainspace. We no longer transcribe text directly into the mainspace, we now transclude text from the page namespace into the mainspace instead. The text now in the mainspace needs to be migrated into the page namespace page Page:The American Cyclopædia (1879) Volume VIII.djvu/73 and the relevant following pages and then transcluded back into the mainspace. In short: first proofread page 73 and the relevant following pages, and then transclude it to The American Cyclopædia (1879)/Goethe, Johann Wolfgang von. (And bear in mind that a lot of articles are still completely missing from the mainspace). James500 (talk) 06:09, 15 April 2020 (UTC)Reply

In answer to your other questions, the page Page:The American Cyclopædia (1879) Volume VIII.djvu/11 is perfectly fine, and just needs to be transcluded into the mainspace. The American Cyclopædia (1879)/Volume VIII: Glasgow - Hortense is a contents page we created ourselves because the volume lacks one. That contents page is presently incomplete, and the missing items (such as the list of contributors on page 11) need to be added as red links or blue links. James500 (talk) 06:24, 15 April 2020 (UTC)Reply

@James500: umm... ?
Is that correct? If so, could this understanding be put someplace others as confused as I could find for enlightenment? Shenme (talk) 06:33, 15 April 2020 (UTC)Reply
If I understand you correctly, that is basically how it works. You might find Help:Transclusion useful. James500 (talk) 06:54, 15 April 2020 (UTC)Reply

I wonder if either of you are aware of the Help:Match and split tools? When we have transcriptions of full works (to whatever degree they have been proofread), this process may be used to spread those transcriptions out, page by page, and permit one-page-at-a-time proofreading. This is the process I used to generate the individual pages, for instance, for The Afro-American Press and Its Editors, and a number of other works. It's imperfect, but it does permit building on past efforts to clean up OCR, rather than starting from scratch. -Pete (talk) 05:07, 16 April 2020 (UTC)Reply

hi, i have taken the liberty to migrate your Goethe article to page space. i added the section tags to each page i.e. [1] and then used the transclusion code to stitch the pages together in article space, i.e. [2] there is more help about sections at Help:Labeled section transclusion and Help:Transclusion#How_to_transclude_a_portion_of_a_page. this is advanced topics, so it's ok to be confused. please leave me a note if you have further questions. cheers. Slowking4Rama's revenge 22:34, 16 April 2020 (UTC)Reply

Memories of Oregon edit

Hi, just wanted to let you know... our efforts at Index:History of Oregon volume 1.djvu have continued, but more slowly without your help. You are missed...though I realize you are doing excellent work elsewhere! -Pete (talk) 20:01, 22 April 2020 (UTC)Reply

@Peteforsyth: Yes, well it got somewhat oppressive/depressing. Getting away for awhile helps one process what it is that bothers. It crystalized later that this was a book somewhat like "Who's Who", but rather "Who was Who". How do you sell a book? Find an audience. Only a generation later, a book about immediate forebears could sell. Hence, along with the 'history' part of the book, we have every list that ever had peoples' names written on it. "Hey, let's get that book cuz it might be about uncle Elias (the old coot)!" "Hey, it says he got gold in California! Let's dig under his old shack and find his hidden gold!"
Then there were the revelations not sweet. The (real) author actually did explain well the infernal combination of abolitionists and slave-state emigrants who wrote into law that there be no slaves, but then no African-Americans either. The abolitionists hated slavery (yay) but had no love for former slaves (?!). The slave-state emigrants wanted no competition with cheap labor. This last showed up repeatedly later regarding Mexicans, Asians, Southern Europeans, etc. Again, the author did quite well laying this out while still not (directly) insulting the buying audience.
Similarly the author ventured to include much material about the ME missionaries that was non-complimentary. Since most (all?) of those individuals were dead, then no worries? There was at least one insight that I will not forget, and that I will be passing on to others. At one point he described an interaction between the upright missionaries and some 'acquaintances' from a few years before. The down-and-out mountaineers came into the promised land starving, but were turned away from the homes of the missionaries. Supposedly because they inadvertently showed up on a Sunday, when homes were 'closed'.
In describing the interactions and conversations, the author in passing explained the unkindly behavior of those Christian men with a phrase that lit me up. The missionaries exhibited "exclusive sentiments". They could be most Christian, but only to those who were part of their group. They who probably knew most of the Bible could not remember the numerous passages that would indite their hearts. But that has been true too much, too long. Hence that one two-word phrase made the book worthwhile for me.
Perhaps in opposition, by checking "Recent Changes" I noticed Index:The Afro-American Press.djvu. After working on that for awhile and hoping for glimpses of a different reality, it became grating also. It really was a "Who's Who" with the focus on a very narrow group. Again, perhaps a focus on a particular audience means book sales? Instead of insights into the times and efforts, rather than quotes from the works themselves, it seemed filled with self-congratulatory back-patting. Almost a book of "who's a real person" lists. And all the honorary degrees!
The repeated "all we need do is be men" statements freaked me out. I did see a few comments that the accumulation of property would be key. When you can't blend in, your community must have 'heft' to be reckoned as a power. So the book does give a small number of reflections, but far too few.
(factoid: In the US the immigrant group whose second-generation has the highest number of advanced degrees is Nigerian-Americans, at around half(!). But that reflects the mother culture, and how they achieved power in that society and then were able to emigrate.)
A friend insists that books of the 1800's were just "like that". I have read too many sciencey books from that period that were mostly opinion, without the underpinnings we take for granted these days. I love the language of those times, but the content sucks often enough.
I'll likely be unwinding and returning to prior projects, after I finish touching up an old project Treaty of Wanghia. Little did I know that this treaty (and at least one other) are also duplicated (twice!) within United States Statutes at Large. So I've been working on the duplications to add more reflections to a bit of stridency at Duplications of texts, USA treaties, between individual projects and within United States Statutes at Large.
All in all, I'd rather work on silly things like Index:Chinese Fairy Book (Richard Wilhelm).djvu, a strange strained oldish translation from some kind of Chinese of that time into an English of that time. And along with problems in publishing. Shenme (talk) 22:02, 22 April 2020 (UTC)Reply

Wow, thank you for the thorough explanation. I'm really interested in both works, and it's rare to get such a carefully thought-out perspective on either one. I am inclined to agree with your perspective for the most part...maybe without exception. "Exclusive sentiments" among Christian missionaries is indeed a vivid turn of phrase, that says a lot about the zeitgeist. But speaking for myself, I have a few other thoughts, and some context (I'm not sure how much of the context you know, so my apologies if I'm telling you stuff that's obvious in some cases).

  • I have a major interest in Frances Fuller Victor, for several reasons. She is considered the "Mother of Oregon History," so much so that her name is inscribed in the Oregon State Capitol. I have an abiding curiosity about the reasons for that, and how well deserved they are.
  • It seems, above all, that she brought from the east coast some ideas that were very current, about the significance of first-person reports in recording history. She worked hard to gather such reports, at a time when others were not doing so. She was diligent in providing and evaluating and contextualizing her sources, at a time when other Oregon historians were not. Much of her work was timely in that way, and if she hadn't done it, it wouldn't have been done.
  • I'm also fascinated by the prominence of the Marcus Whitman controversy, and her role in it. This work is where it all started, though her views evolved after its publication.
  • Another Wikisource editor -- an academic historian -- helped me understand that there are important, then-unsettled historiography questions deeply embedded in they way Victor's work was received at the time, and since. I need to track down that conversation, and I'll link it here when I do.
  • As for social (in)justice, I am often impressed by her perspective, but occasionally disappointed; she could be sensitive to social injustice in some ways, but crass and racist in others. Of course the times were quite different...but reading her work, and contemporaneous responses to it, helps me understand those differences. I find her views on women's rights interesting; she seems to have been a woman unafraid to chart her own course, to have an early marriage annulled, and to pursue her own career rather than chasing her second husband around the world; and with books like The Women's War with Whisky she fully embraced the temperance movement. But she did not strongly align herself with the woman suffrage movement that was strong and active in Portland during her day. My sense is that she had some distaste for, or at least ambivalence about, strong social advocacy, and preferred to choose and fight her own battles rather than join in whatever was popular. I'm sure there's been much written on the subject that I haven't gotten to yet.
  • Regarding the "Who Was Who" issue, I assume you're talking about stuff like the footnote on this page. Yes, there is quite a lot of it, and I agree it's tedious to proofread. (For what it's worth, I have no expectation that you, or anyone, would do more of that than you like...I'm fine with you skipping sections that bore you, and I'd gladly come back and fill them in if necessary.) Surely, your point about marketing fed into her inclusion of the "muster rolls" -- fully a third of the book's contents -- in The Early Indian Wars of Oregon, which was financed by the state. But, in my view it all occurred in a context of doing good intellectual work. Later Oregon histories like those of Joseph Gaston seem even more blatant in that regard. They appear to me to have followed a model of one volume of pretty good history, and then 2-3 volumes full of purple prose about city fathers. I've often wondered if his works were "pay-to-play." But your theory (about book sales) does seem plausible, and might be all the explanation that's necessary.
  • I agree that The Afro-American Press and Its Editors is disappointing in that respect. I was originally attracted to its incredible collection of woodcuts, and I'm hopeful that many can find a home illustrating Wikipedia articles. (More on that below.) But yes, it would be nice if there was a bit more critical thinking, and/or exploration of content, in the text.
  • Even given these flaws in the works, I am motivated to work them to completion (i.e., at least fully "proofread" state, if not "validated") because I would like them to exist in a complete and easy-to-read state online. I'd like to be able to have discussions like this with more people...but that means more people would need to read the books! So, I guess that's the main thing feeding my obsession.

Both of these books, and much of my effort here at Wikisource, have some connection to the Newspapers on Wikipedia campaign, something I've worked on for several years -- an effort to get basic information about local newspapers onto Wikipedia (and thereby, into Google and Bing search result panels). I'm currently seeking funding for another phase of this campaign, and in this phase we will focus on black-owned newspapers...partly because of my discovery of this book, and partly because they seem to be under-represented on Wikipedia. So that's also part of what has motivated my efforts.

Thanks for all your work on them, and thanks for sharing your thoughts. The Chinese Fairy Book looks pretty cool, I'll give that a look too. I had noticed your "duplication" thread at the Scriptorium, but I haven't delved into it. The work here never ends......... -Pete (talk) 03:12, 23 April 2020 (UTC)Reply

Ah, I found the discussion I mentioned above, it was with User:Nizolan, an intellectual history grad student. See here. Fascinating stuff. -Pete (talk) 18:09, 23 April 2020 (UTC)Reply

Matthew Henry edit

Thanks for the work you've done this month on An Exposition of the Old and New Testament (1828). With regard to your comment on "and row the same way as they look" - compare Dictionary of Proverbs (bottom of first column, top of second). --PeterR2 (talk) 23:16, 17 May 2020 (UTC)Reply

Yes, thank you for your help with Matthew Henry. That's really greatǃ Heyzeuss (talk) 12:40, 20 May 2020 (UTC)Reply


The obsolete phrase "to rid ground" or "to rid way" or "to rid space" is defined by the Oxford English Dictionary as "to cover ground, to move ahead, to make progress." They mention this as a specific phrase, but also for the verb on its own they mention a "now rare" meaning of "To accomplish or get through (work of any kind); to clear off or away." Matthew Henry uses the same phrase in Ezekiel 1:9,12, half way down the right column. And no, I wasn't familiar with this phrase either! --PeterR2 (talk) 08:30, 23 May 2020 (UTC)Reply


With regard to damaged type, notably punctuation at the end of a line, I have been using scans at HathiTrust of the First American edition published by Towar and Hogan, from which the Barrington and Haswell edition here on Wikisource was reprinted. The pages containing actual commentary appear to be identical.PeterR2 (talk) 19:20, 7 June 2020 (UTC)Reply


You asked about "v. 20" on Page:An Exposition of the Old and New Testament (1828) vol 3.djvu/210. This refers to John 5:20, which has similar wording to John 3:35. It is confusing because, in Henry's commentary on Psalms, he also uses notation like this to refer to another psalm, whereas in other books he would use "ch.", like this, "ch. v. 20". In Britain we do not refer to the individual psalms as chapters, although some Americans do this (doesn't necessarily mean it's considered correct usage in America, I don't know that).PeterR2 (talk) 12:52, 14 June 2020 (UTC)Reply

@PeterR2: re: "John iii. 35.—v. 20." I had seen elsewhere people refer to 'chapter' as right/wrong. I wouldn't know, and it was new to me that the Psalms can be divided into 5 books (a possibility, as I think this MH section will need to be divided for display).
The thing is that the psalms have always been individual items (and some have been in this order for a very long time - see Acts 13:33) whereas division of the other books into chapters and verses is much more recent (chapters in the mediaeval period and verses in the reformation period), though in some places, e.g. of a poetic nature, for instance Lamentations, and perhaps the verses in Proverbs, some of the divisions are fairly obvious; whereas in others they're very arbitrary.PeterR2 (talk) 22:27, 14 June 2020 (UTC)Reply
What was actually getting me was the "—". I was trying to figure out how "John iii. 35.—v. 20." would work as a range. Later I found places where at least 3 different cites would be mentioned in the form "place.—place.—place." which sort of made it clear these were *not* range references, but 'this' one, 'that' one, and 'another' one. Is this a correct interpretation?
Yes, it looks odd to me too, but that seems to be the only possible interpretation given the way it's used. I've been working mostly in Genesis up to now and don't remember seeing it there, nor what you described as "mid dots". PeterR2 (talk) 22:18, 14 June 2020 (UTC)Reply
With regard to formatting oddities, it would be interesting to see the original 1710 edition, or the 1721 edition (the first edition that covered the whole Bible - which Matthew Henry himself did not complete). According to JISC's Library Hub Discover website, both are on GALE ECCO (Eighteenth Century Collections Online), but one has to belong to an academic institution with a subscription in order to access this. The final volume (Epistles and Revelation) of the 1721 edition is uploaded at Google Books. PeterR2 (talk) 00:10, 15 June 2020 (UTC)Reply
I've trapped myself over at KJV Psalms because, when I was suspicious of a line at MH, and wanted to check against KJV, the Psalms were bare of all comments, like the sidenotes. I'm getting near done with the Psalms, (ex. p. Page:KJV 1769 Oxford Edition, vol. 1.djvu/551, Page:KJV 1769 Oxford Edition, vol. 1.djvu/577) but each page is up to ~60 minutes to do. Bonus is that so far I've found 3 textual errors. Later I'll have to consult experts because marginal note display is weird around here, like on mobile devices. Shenme (talk) 18:43, 14 June 2020 (UTC)Reply
Hehe I'd wondered where you'd gone, but hadn't looked. I've been trying to validate the pages in Psalms that you proofread, but couldn't keep up with how fast you were going (very pleased though!), so you going elsewhere is giving me a chance to start catching up a bit. I've not had to work with margins - my Wikisource skills are very basic.PeterR2 (talk) 22:18, 14 June 2020 (UTC)Reply


Shenme, would you be able to check and validate Page:An_Exposition_of_the_Old_and_New_Testament_(1828)_vol_3.djvu/204, please? It's the only page in a sequence from the beginning of Psalms that I can't validate, because I (rather than you) did the main proofreading on this particular page. --PeterR2 (talk) 09:44, 24 June 2020 (UTC)Reply

Okay, will do 'tomorrow'. Appointments first... Shenme (talk) 10:22, 24 June 2020 (UTC)Reply


Regarding "cael-" versus "coel-", these spellings seem to be interchangeable in different editions of the same passages of Latin authors, but I did a search and discovered that in fact the printer of this edition of Matthew Henry uses a double-storey "a" in "ae" even in italics, so I think we can safely go with "oe" when there is no "handle" on top. As a result I've corrected what I'd already validated on the preface to Proverbs, and when I get to the relevant page in Psalm 8 will put it as "oe" (which was your preference anyway). :) --PeterR2 (talk) 23:08, 28 June 2020 (UTC)Reply


About "to us-ward" - the reference is to the KJV translation of 2 Peter 3:9, one of three places in which the KJV uses this construction, in both NT instances following Tyndale's 1525 NT, though Wycliffe's translation in the 1300s didn't use such wording in these passages. The KJV also has several examples of both "to you-ward" and "to God-ward". --PeterR2 (talk) 13:44, 5 July 2020 (UTC)Reply

Shenme, I think you had some ideas about the splitting of An Exposition of the Old and New Testament (1828) into books of the Bible. However there are already namespaces (at least I think that's the right terminology) such as An_Exposition_of_the_Old_and_New_Testament_(1828)/Genesis and An_Exposition_of_the_Old_and_New_Testament_(1828)/Exodus linked from the main page at An Exposition of the Old and New Testament (1828). Do you have any suggestions for a way of making the beginning and end of these tidier? Because the end of Genesis is on the same page as the beginning of Exodus in the printed book, there is currently a bit of Exodus in the Genesis page and a bit of Genesis in the Exodus page. -- PeterR2 (talk) 09:59, 5 November 2020 (UTC)Reply

Dotted TOC line edit

Hello Shenme! Thanks for all the help with the books I am trying to put on wikisource.

I have two questions:

1. Shall I add entry-width 100% to all the lines? This is in connection to your edit here where you say there is a problem with smaller screens. Or would you recommend more changes? I would love everything to look perfectly on all kinds of screens of course.

Tar-ba-gan, I added that parameter to the one line whose entry text was longest. Only a couple more are 'long' and the rest shouldn't have problems anywhere. I just bugged me that text of long lines wrap around before they need to. When I use {{Dotted TOC line}} I use that parameter and more on all lines, but don't _need_ to, except for the long lines. I'd say just on that one line. Shenme (talk) 04:44, 25 June 2020 (UTC)Reply

2. These refs are really quite confusing. I have the idea that they are best managed once the text of a chapter is done. Will just copy all the refs into the chapter text. Do you think this is a good idea?

I think that it is key that most of the footnote lines have very little information in each. For instance footnote 201 on p. 173, which in the footnotes chapter has (p. 443):
201. IV, 25, p. 267 ff.
Not much there. Volume IV of what? In order to understand it you have to go backwards up the list of footnotes, back to the _previous_ footnotes page (p. 442), back all the way to footnote 184:
157, 184. Al-Chazari I, 1-67, pp. 1-29.
Um, what's "Al-Chazari". Farther up we find:
150, 178. Al-Chazari, I, 67, ed. Hirschfeld, Leipzig, 1887, p. 29, 24.
That's everything in the footnotes, and we still don't know what "Al-Chazari" is.
Footnote 201 says p. 157, initial footnote 178 mentions p. 150. This is the book chapter on Judah Halevi. Turns out "Al-Chazari" is a story(?)[3] by Judah Helevi.
I thought this might have been in the Bibliography, but doesn't seem to be. I did find (though not in the Bibliography or Notes) references to "Kusari" and "Cusari" - could this be, as I suspect, the same book? BTW Project Gutenberg has the whole of A History of Mediaeval Jewish Philosophy in one page, so it's easy to search through the entire book for a particular word. --PeterR2 (talk) 09:33, 25 June 2020 (UTC)Reply
Even if we filled in all the missing information, copying from previous entries into footnote 201, it still wouldn't have enough information for a 'real' footnote ref to insert into page 157? And that would be "altering the source text" that so many frown upon here?
201. Al-Chazari, IV, 25, p. 267 ff., ed. Hirschfeld, Leipzig, 1887.
Few footnotes have information that *explains* the text, that helps the reader. The footnotes are info for researchers and those researchers are going to have to look at the whole footnotes section anyway to make sense of it all.


Proposed solution:
You've created a section for footnotes, p. 439-448: A History of Mediaeval Jewish Philosophy/Notes. I'm thinking that rather than have traditional in-text footnotes - <ref>s - we instead do just what the author wanted: link to the footnotes section! I could make each footnote entry have an anchor, so that one could link to A History of Mediaeval Jewish Philosophy/Notes#201 from p. 157. That would look like [201] (perhaps could be made nicer). The reader could click over to the footnotes section, search backwards if needed, then return to the text using the browser back button.
And we could do that now! That is, finish the pages in the footnotes section, with anchors, then finish creating the /Notes page with the transcluded pages, and poof! each footnote is usable from Page: now or mainspace later. Yay!?
So... not refs - links! Sound interesting? Shenme (talk) 04:44, 25 June 2020 (UTC)Reply
In my enthusiasm, I've created A History of Mediaeval Jewish Philosophy/Notes, filled in one of the footnotes pages with anchors, and made links of the 3 footnote refs on p. 150. Try it out and let me know what you think. Shenme (talk) 05:00, 26 June 2020 (UTC)Reply

TIA, --Tar-ba-gan (talk) 17:27, 24 June 2020 (UTC)Reply

Thanks a lot for your solution! I have never seen that before. I have to try it out elsewhere myself as well. Best regards, --Tar-ba-gan (talk) 14:02, 27 June 2020 (UTC)Reply
@Tar-ba-gan: So... reading documentation I came across Help:Footnotes_and_endnotes#Endnotes_with_anchors, which has been there since 2012! On the one hand, I'm not crazy. On the other hand, I'm not original. Ah well... :-) Shenme (talk) 02:06, 6 July 2020 (UTC)Reply
Thanks @Shenme: It is great you found that piece of instruction. I am glad to see all these contributions you have made to the formatting and linking. I feel humbled. I hope you do not mind if I return to that text next month. --Tar-ba-gan (talk) 15:08, 22 July 2020 (UTC)Reply

TOC spacing edit

I believe I have solved it. Cheers! BD2412 T 01:41, 30 December 2020 (UTC)Reply

@BD2412: Yes! The simpler the tools used, the more likely the solution will last. Adding the line-break between topic sur-title and first entry does what is needed. I _might_ have thought of it eventually... or not. Thanks. There's at least one other place this is needed. I'll go look. (Regarding old tools: heard an expression for "a long time ago" - "when wooden shoes were made out of stone" :-) ) Shenme (talk) 02:25, 30 December 2020 (UTC)Reply
That's a new one for me, too. BD2412 T 02:29, 30 December 2020 (UTC)Reply

Scrollbar edit

Where do you see a scrollbar? —Justin (koavf)TCM 05:24, 16 January 2021 (UTC)Reply

@Koavf: Inside the nice box for "Lyrics from the Pekinese" on Page:The New Yorker 0001 1925-02-21.pdf/23, just to right of the text is a vertical scrollbar. I have to scroll that down to see the "Arthur Guiterman". I tried reducing/expanding the browser display font size with not much change and scrollbar never went away. This with Chrome. Same with MS Edge (but that's now expected) Same with FireFox. On Windows 10. On the off chance, I changed height1 to 1200, but that made the text overflow past bottom of box and out of sight. Haven't investigated more than that. Sorry. Shenme (talk) 06:03, 16 January 2021 (UTC)Reply
Thanks. I figured, but I don't see it on my set up. :\ —Justin (koavf)TCM 06:17, 16 January 2021 (UTC)Reply
@Koavf: Hmm, well the outer image width then determines how much head room there is on the inside. Using 425px instead of 400px gets me (425/661) * 1604 = 1031px height for outer image. We need about 1000px inside so things then fit without the vertical scrollbar. I ended up with
|425px|
| x1 = 80
| y1 = 10
| height1 = 1000
and everything looked nice - no scrollbar and text centered again. Could you try those values and see if they look okay for you? Perhaps your system was using a font that was less 'tall' in pixels, so didn't use more than the ~970px available before? It was that close a difference!
I hate the idea of specifying in pixels, but the {{overfloat image}} barfed when I tried to say things like "height1=50em" because the template forces 'px' so 'empx' boom!
Also, I took out the "text-indent: 1em" because the poem doesn't have that. Shenme (talk) 08:40, 16 January 2021 (UTC)Reply
🤌 (pinched fingers emoji--may not display yet [but you may come back to this talk page in a few months and it renders!]). Grazie. —Justin (koavf)TCM 09:41, 16 January 2021 (UTC)Reply

Templates for special characters. edit

Let me know if there are any more templates that you need me to create. I'm also happy to do so. In general, when I create a template for a special character. I use {{tl|name of the template}}. This will create a link to the template page. Then you can go to the template page, paste in the character, save, and you're done. Great work on the First Folio! Very impressive. Languageseeker (talk) 03:58, 2 May 2021 (UTC)Reply

Index:W. E. B. Du Bois - The Gift of Black Folk.pdf edit

Do you have any interest in collaborating to finish off this work or were you just doing a few one-offs? If it's the former, please ping me and if it's the latter, thanks for all you've done. —Justin (koavf)TCM 00:37, 19 July 2021 (UTC)Reply

@Koavf: I would like to contribute, but can't promise much. I'm kind of taken up with another project. Occasional efforts in plain prose are a vacation from that. And then there's poems I ought to get back to. Too much fun leads to exhaustion? Shenme (talk) 00:53, 19 July 2021 (UTC)Reply

Re: Account of the last words of Christian Kerr edit

The improved text comes from the original scan; some of the earlier NLS imports compressed the PDFs, which ruined some text, and made some hard to discern. As for new-line quotes, they’re ignored, as far as I know. Thanks for the work on the chapbook, by the way. TE(æ)A,ea. (talk) 23:38, 20 July 2021 (UTC)Reply

Index:Russian Fairy Book (N. H. Dole).djvu edit

Hi. What are your intentions with this index? I found it when working on The Russian story book, and would be keen to finish this as well if you have lost interest; I wouldn't ask but it is up in main. CYGNIS INSIGNIS 16:01, 11 August 2021 (UTC)Reply

@Cygnis insignis: In most everything I do my intentions are "wiki-gnomish" - just contributing as I can, peripatetically.
I am rarely invested (or "ownish") about anything, though some projects are different. When fidelity of content and presentation should be paramount, I get a bit huffy.
Regarding TOCs, I'm simply particular about replicating the dots. In that place I used {{Dotted TOC line}} to do so.
As I am captured currently by wanting to do well by User:Stevenliuyi's amazing efforts at Eminent Chinese of the Ch'ing Period (and lately with a side-effort at an input method for entering ancient Greek letters...), please do as looks correct for the Russian tales projects. Shenme (talk) 18:06, 11 August 2021 (UTC)Reply
Okay, thanks for explaining that. I'll finish it off and try to honour your approach, if anything it not to your taste let me know. I'll add or leave the dotted toc, and won't waste your time trying talk you out of using that thing. Your examples are great efforts, Steven's project is sure to be useful to others. CYGNIS INSIGNIS 18:27, 11 August 2021 (UTC)Reply

Re: Boris edit

The confusion here involves two “dictates” of policy, neither of which I have ever seen written down. The first is that whole works in separate languages (like the originals of the Great Charter in French and Latin from A History and Defence of Magna Charta) should be proofread &c. by their respective Wikisources. Because there is no English text, and this is the English Wikisource, the page is thus “without text.” This leads to the second matter of policy: how pages without English text, but with text in other languages, are marked. The standard is to use {{iwpage}}. This more or less transcludes the content as it exists on the relevant non-English Wikisource. However, if there has not been any contact with those projects (as the case is here), those other pages will not be proofread, and will likely remain not proofread for a very long time. The “text” which is received from French Wikisource is Page:A History and Defence of Magna Charta.djvu/250, and that alone; if something was there, the bolded page name would be removed and replaced by that text. I remember working on one volume of around 300 pages, where only six pages were in English; the rest were marked with {{iwpage}}. So, to answer that question, yes, we force the French to stay away from us Brits. For a greater justification, you may want to ask at S or S/H; but this is as much as I have ever known. TE(æ)A,ea. (talk) 12:50, 13 August 2021 (UTC)Reply

  • Of the three works you listed, I would not put any on international Wikisource. The Chinese text in Eminent Chinese is primarily titles—of people, books, or whatnot. The titles themselves are not independent works, and would thus not be subject to {{iwpage}} (which also has a section variety, should than be a concern). The Swatow work is excepted because it is a cross-language dictionary; and Wikisource doesn’t like dictionaries (apparently?). I can’t get much out of the German work, but it appears to placed up there merely because the large quantity of Old Irish text (which is an integral part of the work) has no Wikisource project of its own. The key difference (in my mind) with the works above (and more substantial ones like this) is that the foreign-language sections are both wholly separate and independent works. There aren’t really any gaps on this side, because no one will ever really see the blank French or Latin pages. (For the Eminent Chinese, by the way, I can appreciate how important the work is, but I simply can’t help with the proofreading: my lack of knowledge of Chinese is crippling. It bothered me a lot when I was going through the backlog of pages with illegible text, seeing Swatow and that work, because I couldn’t make heads nor tails of the characters.) TE(æ)A,ea. (talk) 22:47, 13 August 2021 (UTC)Reply
    • Responses:
      1. That is as intended. Because there is nothing on the page (except {{iwpage}}) on this side, there is nothing to transclude. To do so properly, use e.g. {{iwpages|fr|250|250}}.
      2. Yes, this work, though primarily in English, is actually in three languages: English, Latin, and French (appearing in that order).
      3. As for “further inquiry,” go ahead; this work is pretty good on that front, too.
      4. As to how a work is sorted, I will here explain what I think the current procedure is regarding cross-wiki splitting. The English Wikisource gets the title, the introduction, pp. 1–145 and 233–277 (all) and pp. 147–231 on odds of the main text. The Latin Wikisource will get pp. 146–176 on evens. The French Wikisource will get pp. 178–230 on evens. In all three of the projects, pages which they don’t “get” should be marked as without text with {{iwpage}}, so that the other projects can proofread the text in their respective language(s).
      5. “Why did [you] work on [that] page?” For no reason. The content of that page should be moved to wherever, the page as it exists here should be deleted, and recreated with {{iwpage}}.
    • These are the answers, unsatisfactory as they are. I do notice your thoughts; I will respond to them when you bring up the topic before more people. TE(æ)A,ea. (talk) 14:18, 14 August 2021 (UTC)Reply

Index:On the providence of God in the government of the world.pdf edit

Hi there,

I've been doing some work on the National Library of Scotland chapbooks collection on Wikisource, because a large number of them have been transcribed but very few of them have been transcluded, and I've been trying to help reduce the backlog. Unfortunately, it's not just been a case of doing the transclusion. As you have experienced, the quality of the printing is often poor and the binding is often very tight, with words cropped, etc., so doing the best possible transcription can be a bit of challenge. In addition, although pages are at 'proofread' or 'validated' status, it is often the case that they have a number of faults, particularly with formatting, removal of hyphenated words, and sometimes unacknowledged missing images. Because of this I have also had to do a lot of editing, which I tend to do in two stages. First I run the OCR clean-up tool (to collect text into clear paragraphs/remove hyphens, etc,) and, where used, also remove the long s. I do the latter because (i) it's about transcription not reproduction (ii) it makes the resulting text much harder to read, and (iii) it makes spotting errors more difficult (in my opinion anyway). Secondly, I correct any problems.

In the particular case of page 3, I had done the first step but had to break off in the middle of the second without saving my work, and you did your edit before I was able to get back to it. In light of the above, and regarding the comment you added to your edit, hopefully you'll see that it isn't just about the long s.

I think you did a good job on the page, by the way. Your changes mirrored ones I'd picked up. I've made some further changes, principally adding links to the quotes. Unfortunately, the {{reconstruct|}} template and the means of linking don't seem to get along, so I've had to remove the odd instance that you added, but the correctness of the transcription can be seen by checking the linked text against the KJV.

Regards, Chrisguise (talk) 08:13, 18 August 2021 (UTC)Reply

@Chrisguise: Partly it's just that I'm in a snit about a couple conventions here, and also that I'm handicapped (literally) recovering from hand surgery. I did note more than a couple times 'f' and 's' crossed paths in the scan. Did you by any chance see the Google book link I put in the index talk page? There is simply no way else to recover the original text. However do note that the capitalization and a couple words differ in the two copies, e.g. 'to' replaced by 'of' in Google text.
Ack, you mentioned KJV. I really need to get back to that. I'm a stickler for both form and content, and the previous version was a pure copy-n-paste of 'something', and missing footnotes, sidenotes, and much else. I'm willing to work towards better fidelity. Now I just need to get over the carpal tunnel surgery... ;-) Shenme (talk) 17:46, 18 August 2021 (UTC)Reply
I didn't see the link, but have checked it out now. I did try to find a comparator version but failed (because I used the title of the chapbook, not the original title). Chrisguise (talk) 17:58, 18 August 2021 (UTC)Reply
Ahh, great. For some reason I'd been thinking you had to include this on every use within the text. (ick!) Guess I need to work on my reading. Done, thanks. Shenme (talk) 01:49, 19 August 2021 (UTC)Reply

ANCL Volume 5 edit

Hi, I'm obviously not as invested in this volume as I have been in the others in the series. You're finding scannos that I don't usually miss on the first pass. Thank you for picking up what my eye is not seeing and I'll try to be more careful. Beeswaxcandle (talk) 07:54, 9 September 2021 (UTC)Reply

@Beeswaxcandle: Heck, no, I'm quite brainless at the moment, and just using search to find patterns once seen, insource:/mg/, insource:/wdi/, etc. Then once I'm on a page in edit, scanning through looking for browser marking 'misspellings'. And then those can feed me new patterns. Hence my edit summaries, showing the patterns I found. They're all scannos. That I'm clogging up the related changes with minor tweaks is icky, but it's not _exactly_ useless, if not particularly credit-worthy. ;-) Shenme (talk) 08:04, 9 September 2021 (UTC)Reply

enWP imports edit

Regarding this. We usually deliberately do not fix up links or such when we import templates from enWP, because the fixes will just be overwritten the next time we update it; or, alternately, we would have to keep reapplying the fixes every time and MW doesn't actually provide any tools that would make that a sane thing to attempt. There's a long-term desire to support "Global Modules" in MW to alleviate this problem, but it exists pretty much only as an idea at the moment, and no real work on it has happened for the last ~5 years. Xover (talk) 07:38, 18 September 2021 (UTC)Reply

@Xover: Then when templates conflict we have problems. Per "tag" is not "it" ? we have a {{tag}} here that is nothing like the w:template:tag at enWiki. With them using their {{tag}} in documentation there, the documentation when moved here doesn't tell the same story. Which problem to fix? Should we offer to edit out their several usages of a complicating template? :-) Shenme (talk) 07:49, 18 September 2021 (UTC)Reply
In general the problem is not solvable and we'll just have to live with it for now. But for {{tag}} specifically I think we should just replace our local template with the enWP one. Our template is an old one that is barely used and no longer in conformance with current practice, so it should be removed regardless. Xover (talk) 09:14, 18 September 2021 (UTC)Reply
Notes on usages here:
  • [4] (87) all usages of {{tag here
  • [5] (11) remaining {{tag|verb usages in enWiki manner
  • [6] (74) {{tag|[123]}} usages in local enWS manner
  • [7] (3) strange or mixed overlapping usages

Table style edit

Hi, From the comments on Xovers User page, I am hoping you could help me understand templates? I really appreciate efforts to make them function consistently and having clear documentation is a blessing. I am "just" a proofreader; I really struggle to understand how these things work but have muddled along and have tried to correlate Project Gutenberg standard proofreading to Wikisource—this is my Proofreading guide. It’s very much a work in progress—one of the things I have been trying to get my head around is the difference from CSS? and div? templates which I saw you reference in the table style template discussion… If you could help me understand in the context at hand, that would be GREAT-

I’m trying to do vertical text in the table. This used to work. Now it doesn’t. I have vertical text in tables in Das Kapital. Is a shorthand for table style possible to do this? Zoeannl (talk) 20:07, 6 October 2021 (UTC)Reply

@Zoeannl: Ah, just popped in for a second. I see your use of class="rot270" on that page. When I examine the output HTML/CSS in the browser debug, it doesn't know where the definition of that class is. I am interested in this because a few years ago I just couldn't make vertical text work in the browsers of that time.
(I see Page:Das Kapital (Moore, 1906).pdf/749. Did you mean above that you _will_ need to have vertical text in DK or that you have done some already in DK and am wondering why it doesn't work elsewhere? I've checked the DK pages with tables already done and didn't see any vertical text before page /749)
The CSS keywords (remembering and looking at docs) are "writing-mode" and "text-orientation". And they have been very 'magic' for many years, as in working only selectively depending on which browser and which text direction.
Doing one of those horrible expensive searches on "rot270" I see an old conversation Text rotation / vertical text discussing "rot270".
I also see a template using a class similarly? Template:FreedImg No, that's using CSS rotation, even more 'magic' - Template:FreedImg/styles.css.
What needs to be figured out is, where did "rot270" come from long ago, and/or what did that CSS class contain?
The desired CSS setting is "writing-mode: sideways-lr" [10], but that is only supported in Firefox. (I think this is where I say "foo!" years ago)
Let me look into this farther, into people's experiments with "rotation". Shenme (talk) 21:31, 6 October 2021 (UTC)Reply
@Zoeannl: Well that was deflating. Adding " |transform: rotate(270deg) " to the CSS instructions did everything just fine. See current state of Page:The_Gall_Wasp_Genus_Cynips.pdf/48 and the edits I did. This is working in Chrome, new Edge, and Firefox.
What I can't figure out how to do is to "left justify" the text labels at bottom of the heading cells. Compare with scan image. I think it may be impossible to combine rotation and other text manipulations within table cells.   Hmm, maybe "transform: translate(x,y)"... Bwa-ha-ha!
A side note to all this is that the template {{ts}} is just inserting CSS from looking up the alias 'names' like "it1", now using a clearer table lookup from Module:Table style/data after Xover's very nice rewrite. But if the template hits something it doesn't recognize it trusts you know what you are asking for and just copies it straight into the   <td style="..." . So if you have some weird CSS you want to try out, just throw it into the template call, like I did:
| {{ts|bb|br|it1|transform: rotate(270deg)}}
So it is perhaps a nicer way to do needed CSS? Have the appropriate amount of fun... Shenme (talk) 22:22, 6 October 2021 (UTC)Reply
Thanks for looking at this. The vertical effort on the Gall wasp page wasn’t mine-AuFCL did it, but he’s gone now afaik. Your addition works nicely for the Gall wasps table. I’ve had a go at Das Kapital. Can you tell me what you think is best practice re spacing? - I’ve used no break spaces here and I’ve been told off for it before, (and for using {{gap}} in tables) but I would like to know why/why not.
So, for the sake of proofreaders who don’t want to learn to program, can we add rot270 to the ts shorthand list? Cheers, Zoeannl (talk) 01:16, 7 October 2021 (UTC)Reply