Wikisource:Scriptorium/Help/Archives/2019

From Wikisource
Jump to navigation Jump to search
Warning Please do not post any new comments on this page.
This is a discussion archive first created on 01 January 2019, although the comments contained were likely posted before and after this date.
See current discussion or the archives index.

Contents

Need to replace 1843 edition with a 1905 edition[edit]

This book was published in 1843 at a time when the first of his letters was not yet found anywhere.

It seems that the missing first letter was found by 1905 and was published in two volumes containing all five letters. These books are named "Letters of Cortes" I don't know what to do with the first one. Personally, I think that it should be deleted.

Your input is most appreciated.— Ineuw talk 03:14, 31 December 2018 (UTC)

Wikisource can accommodate multiple editions of a work. The 1843 could stay, but it would certainly be lower priority if the later edition is the same, just with the extra letter. --EncycloPetey (talk) 04:17, 31 December 2018 (UTC)
Thanks again.— Ineuw talk 04:50, 31 December 2018 (UTC)
Incidentally, I would go further and assert that every edition should be on Wikisource; it's just that given limited resources, only the "best" edition may be a realistic goal. --Xover (talk) 18:42, 1 January 2019 (UTC)

Agatha Christie[edit]

The Agatha books are " copyrighted in the USA till 2019 " . I do not live in the U.S , and 2019 has arrived ; Then why are the links not there ? 182.66.156.165 10:45, 1 January 2019 (UTC)

Because they are not out of copyright outside the US, Christie died in 1976, by current copyright rules, her work will not leave copyright until 2047 at the earliest, (irrespective of the situation in the US). ShakespeareFan00 (talk) 11:11, 1 January 2019 (UTC)
Addendum: Links and texts do not magically appear because of a date change. For a text to be available on Wikisource, a volunteer has to proofread a copy of the text and add it to Wikisource. That process requires someone to volunteer to do the work, and then time to accomplish the task. --EncycloPetey (talk) 15:55, 1 January 2019 (UTC)
Further addendum: after purging the page, the list of works should show up as redlinks now. —Beleg Tâl (talk) 16:29, 1 January 2019 (UTC)

Linking people mentioned in TOC pages - when not in Author: entries here?[edit]

I'm looking at the TOC of a work that includes stories, poems, and illustrations. Handling the 'authors' is straightforward when near all have Author: entries at WS. Handling the 'illustrators' is rather more of a problem, as only one was an author. (Leighton having an author entry is strange to me).

Is it reasonable to link to WP for these non-authors? For instance, w:Robert Anning Bell has a WP article, as does w:Aubrey Beardsley, w:Joseph Pennell, etc. Shenme (talk) 02:18, 31 December 2018 (UTC)

Why would you link to Author pages in the ToC? That would mean making external links from the ToC of a work, which the user will expect to be links internal to the work. The Author pages can be linked from the header pages of the individual items; there is no reason to link the authors from the ToC. A Table of Contents should link to parts of the work, not to external targets. --EncycloPetey (talk) 04:19, 31 December 2018 (UTC)
Introducing a rule implying external links from a work are deprecated constitutes a statement of policy neither supported nor forbidden by our current policy. I am not saying EncycloPetey is "wrong" here but this is a guideline I would generally approve… yet in specific cases ignore as unrealistically restrictive. The matter needs further discussion and subsequent detailed changes to policy. 114.73.65.234 06:01, 31 December 2018 (UTC)
You've misunderstood my comments, and you've also pointed to the wrong policy. The relevant page is at Wikisource:Wikilinks. --EncycloPetey (talk) 15:59, 31 December 2018 (UTC)
@EncycloPetey: You are quite correct. I am still a little concerned that because Wikisource:Wikilinks links to WS:MOS but not the reverse; and the general similarity of the introductory language can lead to ambiguous interpretations. There is a fundamental conflict remaining between "transcription purism" and the risk of lost opportunity for the proof-reader who is closest to the work noting matters of later confusion (an author wring in 1898 referring the the "Prince"…could be referring to Machiavelli's work, their local royalty, current British royalty or a frivolous exaggeration but with a very high degree of certainty almost none of the possibilities listed in w:Prince (disambiguation) (or vastly worse q:Q225225!)… and it seems a shame to miss the chance of offering a clarification. This issue is intractable, yet it seems the community is happy to permit mechanical extraction of wikidata linkage into Author pages. Sad. 114.73.65.234 00:48, 2 January 2019 (UTC)
@Shenme: the relevant documentation is Wikisource:Wikilinks and Wikisource:Annotations. EncycloPetey's recommendations are worth considering, but are not mandatory; links to pages in Author namespace are not considered annotations and can be freely added to the text at the proofreader's discretion. Links to Wikipedia are considered annotations, however, and should follow the annotation guidelines. However, Author pages for illustrators such as Author:Frederic Leighton are totally acceptable, and pages can also be created in Portal namespace for individuals who have never created any content that can be hosted on Wikisource, but for whom relevant related content exists. —Beleg Tâl (talk) 13:20, 31 December 2018 (UTC)
In most situations, I would agree. Linking to Author pages from within a text, especially from footnotes or appendices, or from places where that author's works are being referenced, is a fine thing. But in linking Author pages from the Table of Contents, you are violating a user's expectations. One would normally expect links from the Table of Contents to link to parts of the work itself. --EncycloPetey (talk) 15:59, 31 December 2018 (UTC)
It would reassure me to know that you had looked at the two example pages. Certainly the chapters/articles have links from TOC to in-work individual items. This is as expected. Someone previously had linked the authors' names in the first page. I found this useful. When seeing Leighton's name unlinked in the second page I wanted the same ability to ask "who is this somewhat familiar name? Oh, that guy."
There is minimalism - what are the fewest, absolutely required things to enable reading. Anything else done is an additional benefit to some portion of 'users', or readers. A reader has some expectations against the required minimums. A reader will not be harmed by exceeding the minimums.
As an example, the work in question has a mix of articles from several authors. After A Defence of Cosmetics, I'll be glad to avoid any further works by that author. A quicker link from the TOC obviates having to go the article first, and the author link there, only to back out twice over.
This is a wiki. Wikis were to break conventions/restrictions enforced by physical media, yes? I fail to see the astonishment, much less harm, in linking attributions found in the TOC. Shenme (talk) 19:15, 31 December 2018 (UTC)
I had looked at the two example pages, yes.
Exceeding the minimums can harm the reader when the excess violates expectations. And, no, wikis do not exist solely to break conventions.
The purpose of a Table of Contents is to inform the reader of the contents of that work. When the items in the ToC are linked, the expectation is that there is content in that work to which the link will take the reader. When a link in the Contents links to something other than Contents, that is a violation of expectation.
It would reassure me to know that you read and understood my comments on this issue. --EncycloPetey (talk) 19:25, 31 December 2018 (UTC)
I see there being two issues here. 1) Linking to authors/illustrators from a TOC; and 2) How to link to authors/illustrators who don't currently have a page here.

For the first, I agree with EP that TOC links that go outside of the work should be kept to a minimum. Those links belong where they appear in the text—usually, at the beginning of the subwork (remembering that they should appear in the header on the transclusion, so may not be needed in the Page: namespace).

For the second, based on the long-established policy already in situ at Help:Index pages#Parameters, Illustrators should have an Author: page. Any links required to a wikipedia can happen from that page. Beeswaxcandle (talk) 04:34, 2 January 2019 (UTC)

Template source code[edit]

In the template Helpme, it's given that after helping, I need to insert {{tlf|helpme}}. I would like to know where the source code of that page is present.Adithyak1997 (talk) 06:08, 3 January 2019 (UTC)

@Adithyak1997: All templates' source can be found at [[Template:Template name]] so the source code for the tlf template is at Template:tlf. However, I'm uncertain why Template:helpme recommends using it: it appears to simply be intending to remove the transclusion, presumably to remove it from the category that is automatically added. Simply removing the helpme template will have the same effect, and leaving behind the wikicode "{{helpme}}" seems rather pointless. Maybe it would be better to have a answered=yes parameter for this? --Xover (talk) 09:00, 3 January 2019 (UTC)
It's a suggestion for if you want to indicate that the Helpme template had been used, but no longer need help. {{tlf}} is just one way to do this; you could use {{tl|helpme}} or {{tlf|helpme}} or <nowiki>{{helpme}}</nowiki> or I had a [[Template:Helpme]] notice here but I don't need help any more thanks — I don't think we need to add another method with a parameter. —Beleg Tâl (talk) 13:22, 3 January 2019 (UTC)

Indentation options[edit]

At this page over at the Portuguese Wikisource, I am wondering the best way to indent text without having an available template. I would like indentation to resemble the original. They do not yet have block center over there (nor do they have Gap), so right alignment would be too drastic. I am opting (for now) not to use the poem tag in hopes that I'll get the ball rolling at some point there to add a block center template that behaves like ours here (and spans more than one page). Any suggestions welcome. Londonjackbooks (talk) 16:20, 3 January 2019 (UTC)

I would create a template, but in the absence of that I would probably use raw html to emulate {{gap}} <span style="display:inline-block; width:12em;">​</span> or to emulate {{center block}} <div style="position:relative; margin-right:auto; margin-left:auto;"></div>Beleg Tâl (talk) 16:34, 3 January 2019 (UTC)
Muito obrigada @Beleg Tâl: :) I chose the former. I'll wait until a template is created to apply block center. Londonjackbooks (talk) 16:44, 3 January 2019 (UTC)
@Londonjackbooks: {{gap}} is all of three lines of template code, most of which is boilerplate:
<onlyinclude><span style="display:inline-block; width:{{{1|2em}}};">⁠</span></onlyinclude><noinclude> {{documentation}} </noinclude>
You can easily copy it over to ptws yourself (just drop the <noinclude>{{documentation}}</noinclude> if ptws lacks {{documentation}}; it doesn't affect functionality). {{center block}} is more complex, but still eminently copy and paste'able. --Xover (talk) 17:43, 3 January 2019 (UTC)
@Xover: I am wincing over "easily" ;) I am technically nearly illiterate. But I have to ask... I always use {{block center}} vice center block... What are the main differences in the templates (in layman's terms)? Thanks Londonjackbooks (talk) 17:59, 3 January 2019 (UTC)
P.S. Here's the more honest answer: I can probably figure out how to transfer the template over. I did so some years ago with a template from WS to WB with lots of help and instruction which I have since forgotten, but looking at the history now does not help me much. In the years that have passed, I may have become somewhat lazier in the brain; or at least I may lack the motivation I had then. I would require explicit instruction once again, and if anyone is willing to instruct me with much patience, I may be up to giving it a shot :) Londonjackbooks (talk) 18:13, 3 January 2019 (UTC)
AFAIK the difference is: {{block center}} uses table styles for backwards compatibility, whereas {{center block}} uses block styles per modern web design best practices. It should look the same most of the time but it might display differently if you are playing with margins, indents, or other scenarios. —Beleg Tâl (talk) 18:45, 3 January 2019 (UTC)
@Londonjackbooks: does pt:Predefinição:Bloco centro not do what you are looking for? —Beleg Tâl (talk) 18:36, 3 January 2019 (UTC)
@Beleg Tâl: No, I don't believe it can span several pages, and there are other differences I was told made it not a desirable option. I'll have to look for the discussion. Here is a mention: "bloco centro is <div> block based while block center is table based (different HTML structure is used)." [1] Londonjackbooks (talk) 20:08, 3 January 2019 (UTC)
@Londonjackbooks: I have created pt:Predefinição:Bloco centro/c = {{center block/s}} and pt:Predefinição:Bloco centro/f = {{center block/e}}. Like {{center block}} it is div-block based rather than table based, which is preferable in almost all cases. —Beleg Tâl (talk) 20:27, 3 January 2019 (UTC)
@Beleg Tâl: I tried applying it on this page, but I'm not seeing a desired result. I'm used to block center though... Am I doing something wrong? Londonjackbooks (talk) 20:41, 3 January 2019 (UTC)
@Londonjackbooks: My bad, typo in template, fixed now. (Also I was wrong, bloco centro is table-based like {{block center}}) —Beleg Tâl (talk) 20:46, 3 January 2019 (UTC)
@Beleg Tâl: Great! Thanks! An undesired line space is present before the last line of poetry in each Page:namespace, but it seems to work itself out in the Main. Londonjackbooks (talk) 21:02, 3 January 2019 (UTC)
I don't know anything about that line space, it happens to me on enWS too —Beleg Tâl (talk) 21:12, 3 January 2019 (UTC)
Also pt:Predefinição:Brecha appears to be essentially {{gap}} —Beleg Tâl (talk) 18:46, 3 January 2019 (UTC)
@Beleg Tâl: Thanks for finding that :) Londonjackbooks (talk) 20:16, 3 January 2019 (UTC)
@Londonjackbooks: On {{block center}} vs. {{center block}} I'm not much help. They purport to do the same thing, but the former claims to do it in a technically better way. How that shakes out in practice I don't know. As for copying, I'll use {{gap}} as an example:
  1. Go to Template:gap (the page you're actually referring to when you use {{gap}}).
  2. Hit "Edit" (or, for protected templates, "View source").
  3. Select all the text in the text field and copy it.
  4. Open pt:Predefinição:gap (or replace "gap" with a suitable name in Portugese. "lacuna" perhaps?).
  5. Hit the "Edite esta página" link.
  6. Paste the copied template code into the text field.
  7. Hit the "Pubicar página" button.
  8. Use {{gap}} (or {{lacuna}} or {{hiato}} or whatever you used in #4 above).
The short version: copy the template code from Template:template name in English on enWS to Predefinição:template name in Portugese on ptWS. Use with {{template name in Portugese}}.
This works for all simple templates. Some templates use other templates, or require combinations of templates, or do funny things with namespaces, etc. which make them work poorly or not at all when copying like this. But most simple formatting templates should be doable.
(edit-conflict) Also: what Beleg Tâl said. :) --Xover (talk) 18:56, 3 January 2019 (UTC)
@Xover: Thank you. I will take a look at the instructions above in more detail tomorrow. In addition, it is also desirable to retain the template's history when bringing it to another sister project. Someone linked the history for me [somehow] the time I copied a template from WS to WB. Londonjackbooks (talk) 20:20, 3 January 2019 (UTC)
An edit summary ala "Copied from s:Template:gap." is sufficient for attribution requirements. To actually preserve edit hiistory you need to get an administrator to import, not copy, the template over. It's done using Special:Import by someone who has the "transwiki-import" permission; and import from enWS must be enabled on ptWS (which it isn't currently, I don't think). You'll need to point a friendly admin there at the documentation at m:Import to set it up. (a pain to initially set up, but it makes future imports much easier). --Xover (talk) 20:31, 3 January 2019 (UTC)

/* Problematic */ TOCStyle won't format correctly[edit]

Page:The Outline of History Vol 2.djvu/16

I've typed this logically, and it fails to format per the documentation of that template - Suggestions please? ShakespeareFan00 (talk) 10:39, 4 January 2019 (UTC)

Once again the error proved to be a 'hunt' the obscure indexing error. ShakespeareFan00 (talk) 10:47, 4 January 2019 (UTC)

A newbie's questions: headers and footers in Wikisource pages[edit]

I am an experienced w:Wikipedia:WikiGnome. My favourite WikiProject (w:WP:DPL) has gone from cut down the jungle (before my time) through drain the swamp (about when I joined) to (now) trim the grass. I have started to look for useful WikiGnomish things to do in Wikisource.

I am about halfway through turning a hundred-plus bot-scanned pages like Page:Gedichte Hesse 1919.djvu/99 from gibberish into German. The transcription is easy, and I think I'm beginning to get the hang of Wikisource-specific templates like {{c}}, the {{larger}} family, {{gap}} and {{dhr}}.

My questions are these. Should the published page number be part of the transcribed text or be placed elsewhere? Should the language be included somewhere? Is there anything else I should know before going back to the top of this group and starting to mark the pages as proofread?

(Hermann Hesse won the Nobel Prize for Literature for his prose, most definitely not for his poetry. It's dreadful stuff. Still, that book is out of copyright and has been uploaded; so, we might as well get it right.)

Open offer: if any editor would like someone to review pages originally printed in w:Fraktur, I'd be happy to help. Narky Blert (talk) 00:25, 8 January 2019 (UTC)

Ummm. . . That's in German, and should be hosted at the German Wikisource, not on the multilingual Wikisource. --EncycloPetey (talk) 01:22, 8 January 2019 (UTC)
Hermann Hesse died in 1968; works that are PD-US but not PD-70 are accepted at the Multilingual Wikisource for Wikisources like the German Wikisource that only accept works that are PD-70.--Prosfilaes (talk) 03:14, 9 January 2019 (UTC)
@Narky Blert: The page numbers, as artefacts of the physical medium of a book, as well as the running title/author/otherstuff that's repeated at the top or bottom of every page in the book should be placed in the header and footer text fields. They are also strictly speaking optional, but I think the general de facto consensus behaviour is to transcribe these bits as well. The header/footer text fields will be displayed on each page in the Page: namespace, but are wrapped in <noinclude> and won't be displayed when the pages are transcluded together into the overall work's page in mainspace. Or put another way, in the Page: namespace the focus is somewhat stronger in the direction of preserving the characteristics of the original, while in mainspace the focus is somewhat stronger in the direction of producing a new edition that takes advantage of the modern medium. As an example, page numbers are mostly irrelevant in a web edition; and to the degree they're needed they are generated automatically by software based on the information in the Index: page for the work.
As for the language, as EncycloPetey says, works primarily in German should be transcribed at German Wikisource. Language tagging for the main language is thus not necessary: all works on English Wikisource are presumably in English. However, runs of non-English text in the work should generally be tagged with an appropriate {{lang}} template (for the usual reasons). Practice here seems to be variable, with some guidance and practice running to only tagging those specific instances where the non-English text requires a different font or other special display, but I recommend tagging all such instances for the same reasons they do so over at enwp.
Finally, Wikisource has, by nature, an infinite amount of gnoming type work. Quite apart from the bazillion and one started but never finished transcription projects, there are a great many works that have been transcribed (Proofread) but never Validated. Attacking either of these backlogs would be immensely valuable. There are also a lot of works that are in the public domain and have scans available but where nobody has got around to uploading and transcribing them yet. Organizing work around these, somewhat like EncycloPetey has done for Portal:The Yale Shakespeare (think of Portals as roughly analogous/similar to WikiProjects on enwp) would also be of great value.
I'm a relatively new enwp-expat here myself, so if there're any issues that you think might be a translation issue between the two projects you should feel free to ping me. Not that I can claim any particular expertise on either project, but I've banged my head into at least some of the difference and might be able to point you in the right direction. Or, of course, the village pumps on enWS are a lot lower traffic and more useful than the enwp ones so you probably shouldn't hesitate to ask for any information or assistance you need here. --Xover (talk) 09:00, 8 January 2019 (UTC)
@Xover:. Thanks! (I'm getting up to speed by editing in areas where I can do some good and little damage. I thought it might make a refreshing change faithfully to reproduce the typos in original texts rather than to fix typos introduced by WP editors.)
How do I open the header and footer text fields for editing? On opening a page for editing, I can see the header field for a second or so, but then it disappears.
(Yes, I have seen the numbers in Category:Pages by proofreading status. They won't be easy to dent, but every little helps.) Yrs, Narky Blert (talk) 20:33, 8 January 2019 (UTC)
@Narky Blert: The disappearing headers and footers is (probably) a result of task T209939, which should get rolled back in the deploy scheduled for 7–8 January (ish). I haven't tested myself, but someone said this happens only if you have the horizontal layout enabled in the preferences, so toggling that may be a workaround. It is apparently also just WebKit (Safari) and Chromium (Chrome, etc.) that are affected, so Firefox, IE, or Opera may also work. Personally I've been digging around in Web Inspector to turn off a font-size: 13px rule that applies to those text fields and without which the height becomes juuuust big enough to edit. In any case, it'll hopefully disappear in the next couple of days. --Xover (talk) 20:52, 8 January 2019 (UTC)
@Xover: Ah yes, 'what could possibly go wrong?' I've seen similar at WP with complex Templates and with Wikidata imports.
I can't see the header box for editing in any of PaleMoon, WaterFox, Chrome (which I dislike) or IE (which I wouldn't use if you paid me).
Where does the 'horizontal layout' option hide itself? I haven't tested that, because I can't find it. Yrs, Narky Blert (talk) 21:56, 8 January 2019 (UTC)
@Narky Blert: In Preferences, in the Editing tab, "General options" section (first group of checkboxes). It's labelled "Horizontal layout when editing in the Page: namespace". But when I tried it out just now it had no effect on this problem. --Xover (talk) 06:49, 9 January 2019 (UTC)
Not all works on the English Wikisource are in English (en). They can also be in Scots (sco), Middle English (enm) or Old English (ang), and I suspect various English creoles could also find a home here.--Prosfilaes (talk) 04:36, 9 January 2019 (UTC)

TOCstyle can't cope with inlined styles on page numbering...[edit]

A simple test case

{{TOCstyle|model=D.P
|description:|<span style="font-variant:small-caps;">v</span>
}}
  1. description:
    ................................................................................................................................................................................................................................................................................................................................................................................................

This fails to render correctly. ShakespeareFan00 (talk) 12:50, 9 January 2019 (UTC)

@ShakespeareFan00: The = is confusing MediaWiki's template processor. Replace it with {{=}}. --Xover (talk) 13:22, 9 January 2019 (UTC)
Thanks.. In the end I ended up using a the #tag function which also solved the issue of the equals sign. ShakespeareFan00 (talk) 13:24, 9 January 2019 (UTC)

number before dropped initial[edit]

Could I have a solution for this page, please? The dropped initial goes hard left by default? Cheers, Zoeannl (talk) 03:32, 11 January 2019 (UTC)

Yes check.svg fixed Beeswaxcandle (talk) 03:35, 11 January 2019 (UTC)

The murder on the links[edit]

Agatha Christie's "Murder on the Links" requires proof reading . What does that mean ? 223.191.14.246 12:51, 11 January 2019 (UTC)

Have a look at Help:Beginner's guide to proofreading, it should answer your questions on the subject. —Beleg Tâl (talk) 14:29, 11 January 2019 (UTC)

@Beleg Tâl: The text is there , but I can't see the buttons that are supposed to be there . Can't someone else proofread it ? 005X (talk) 05:21, 12 January 2019 (UTC)

Anyone can proofread it. Wikisource is run by volunteers who donate their time freely. Anyone can volunteer to proofread the text. --EncycloPetey (talk) 05:28, 12 January 2019 (UTC)
@EncycloPetey:Yes , but who will ? As I said before the buttons supposed to mean " proofread" or "validated" aren't there . 005X (talk) 05:31, 12 January 2019 (UTC)
Aren't where? The buttons appear at the bottom of a screen when you are editing a page of the text. --EncycloPetey (talk) 05:36, 12 January 2019 (UTC)
@EncycloPetey:Found the buttons , begun proofreading . Please validate the page once I have proofread it . 005X (talk) 05:41, 12 January 2019 (UTC)
Validation is also done on a volunteer basis. My time right now is divided between a literary criticism of Virgil's poetry and a 1918 edition of Macbeth. But given the popularity of Agatha Christie's works, it is quite likely that someone will notice your work and begin validation before too long. --EncycloPetey (talk) 05:45, 12 January 2019 (UTC)
@EncycloPetey:Do you know any Christie enthusiasists in WS ? If so , then inform then about my work . unsigned comment by 005X (talk) .

Adding layouts and "proposed layouts"[edit]

Hi all. I occasionally contribute to en-wikisource and da-wikisource which is considerably smaller (~2800 mainspace pages). I've noticed that while da-ws has 3 different layouts (the view modes available under "Display Options" in the sidebar) for displaying texts, en-ws has a fourth one as well as one called "proposed layout". What does one have to do to add more layout types as well as the "Proposed Layout", and how does the latter work exactly? I've tried finding information at mw:Extension:Proofread Page, but so far I've come up short. Thanks in advance, --InsaneHacker (💬) 10:58, 12 January 2019 (UTC)

Strictly the layout scheme has nothing whatsoever to do with ProofreadPage apart from the coincidence both schemes were originally the invention of User:ThomasV. I expect the documentation you are looking for might be Help:Layout, particularly sections starting at "How to write dynamic layouts" and below? 114.74.213.158 14:56, 12 January 2019 (UTC)
It helps with how to set up the actual CSS-coding, but I'm still at a loss on what one needs to do to the wiki config files to make new layouts appear for all users. --InsaneHacker (💬) 14:16, 14 January 2019 (UTC)

Page:London - White Fang, 1906.djvu/15[edit]

Would have used {{TOCstyle}} but there isn't an option to set a lead-prefix for the chapter numbering, nor a way to get the page numbering to left align instead.. A suggestion on how to format this would be welcomed, or updates to TOCstyle ShakespeareFan00 (talk) 01:10, 14 January 2019 (UTC)

I've taken a stab at it using a table. --EncycloPetey (talk) 01:21, 14 January 2019 (UTC)
Can also use {{ditto|III|I|r}} or {{0|II}}I in such cases —Beleg Tâl (talk) 01:50, 14 January 2019 (UTC)
Apropos of nothing, I bought and read this new in my teens (a reprint/new edition obviously). Suddenly realising that the book was actually written over a century ago makes me feel old! --Xover (talk) 07:04, 14 January 2019 (UTC)
On this site, over a century old is still pretty new for a book! —Beleg Tâl (talk) 14:57, 14 January 2019 (UTC)
Sure. But most texts here don't register as "New when I was a teenager" in my subjective model of the world. :) --Xover (talk) 17:44, 14 January 2019 (UTC)
Aside: So what's the oldest work we have that's scan backed? ShakespeareFan00 (talk) 17:53, 14 January 2019 (UTC)
Oldest scan I have come across recently is the 13th century manuscript Sumer is icumen in (MS Harley 978)Beleg Tâl (talk) 20:07, 14 January 2019 (UTC)
Of course, if later editions count, we have the 9th century BCE Inscription on the Stele of Méšaʿ as wellBeleg Tâl (talk) 20:10, 14 January 2019 (UTC)
If we're counting translations, then the The Code of Hammurabi dates to 1772 BCE. We have a scan-backed edition with photos of the stone on which the inscriptions were made. --EncycloPetey (talk) 22:43, 14 January 2019 (UTC)

Proofreading EB1911, transclusion and section headings[edit]

I followed a footnote from English Wikipedia to 1911_Encyclopædia_Britannica/Masham,_Abigail,_Lady which (a) at the time was only showing the second half of the article, and (b) wasn't correctly linked from the preceding article 1911_Encyclopædia_Britannica/Maseru. My only edits on Wikisource so far are fixes to this. [2]

I'm raising this in case (A) section headings are being changed while proofreading, without checking 'What links here', as seemed to have happened December last year [3]; (B) Odd encyclopedia entries with two commas like 'Masham, Abigail, Lady' are producing unclear page titles. --Cedders (talk) 11:13, 15 January 2019 (UTC)

Hi Cedders, it was just a case of me forgetting to check for changed section tags when copying the proofed text from Gutenberg. Normally I specifically search for "section begin" when displaying the differences to check for altered tags, but must have forgotten in this case. I don't believe its anything to do with having two commas in the page title. DivermanAU (talk) 11:38, 15 January 2019 (UTC)

Index:A_Son_at_the_Front_(1923)_Wharton.djvu and others...[edit]

This file and others are showing something that someone with the right tools could presumably write a script to resolve.

Namely that the whilst all the scans are present, the OCR text associated with them is apparently offset by a page meaning the OCR text and scan pages do not concur.

Ideally the DJVU files should be rebuilt carefully, as these OCR discrepancies may have resulted from "third-party" page removal in tools that are not necessarily as fully aware of the 'text-layer' capabilities of the djvu format as would be desirable.

Whilst I had been marking these for "Source file needs repairing", On review "Source needs OCR text layer" seems more appropriate.

Alternatively can someone come up with a suitable template tag I can use to categorize affected Index/File combinations appropriately. ShakespeareFan00 (talk) 11:53, 15 January 2019 (UTC)

Ocr is ok here: Index:A Son at the Front, by Edith Wharton.pdf. Hrishikes (talk) 15:04, 15 January 2019 (UTC)
OCR on that second PDF copy may be correctly aligned, but I looked at a few pages and the OCR for that copy is near garbage. --EncycloPetey (talk) 17:50, 15 January 2019 (UTC)
New version of djvu uploaded. It is a bug in IAUpload tool, open in phabricator (I have proposed a fix but maintainer is not fixing it, so I worked out my own script).— Mpaa (talk) 23:13, 15 January 2019 (UTC)
Care to look into other works in the "Source File needs to be repaired" and "Text Layer needed" cateogries? I think MANY files could be rescued quite easily. ShakespeareFan00 (talk) 23:50, 15 January 2019 (UTC)

The Murder on the Links[edit]

I have completed the proofread , now what do I do ? 005X (talk) 07:37, 16 January 2019 (UTC)

@005X: regarding The Murder on the Links, I advise that you leave it alone until the potential copyright issues are resolved. Once that is done, if we are able to keep the scan, the next step will be transclusion: Help:Beginner's guide to transclusionBeleg Tâl (talk) 23:23, 17 January 2019 (UTC)

Text is out of alignment and off by one page[edit]

Starting from this page on to the end of the book ~300 pages are off by one page. Would it be possible to insert a single empty page at Djvu 502 and push all others to the correct alignment? — Ineuw talk 02:23, 18 January 2019 (UTC)

What are you talking about? It seems like there is no problem from the 502nd to 503rd pages of the scan (aligning to pages 482 and 483 of the text). —Justin (koavf)TCM 03:16, 18 January 2019 (UTC)

@Koavf: Please look at the image of what I see on the screen. File:Misaligned text pages.jpgIneuw talk 03:40, 18 January 2019 (UTC)

It took me a while to understand also. You mean the saved text of each page is off by one page. I was looking for a missing page. Maybe an admin can do something about it. Jpez (talk) 06:12, 18 January 2019 (UTC)
@Ineuw: -- Yes check.svg Done -- Hrishikes (talk) 07:31, 18 January 2019 (UTC)
@Hrishikes: Many thanks!

Side by side columns over a page break[edit]

I have a text where there are two columns - effectively an original and a 'translation'. Both are several paragraphs of continuous text which flow over a page break. How can I practically do the layout for this? I can handle the first page using a table but see no obvious way to seamlessly 'join' both columns. See https://en.wikisource.org/wiki/Page:Protestant_Exiles_from_France_Agnew_vol_1.djvu/121 GreyHead (talk) 18:33, 26 December 2018 (UTC)

It's a bit tricky, but you could use sections to divide the separate text regions for transclusion. See Help:Transclusion. I'm using sections for the work I'm currently transcribing as well. --EncycloPetey (talk) 18:36, 26 December 2018 (UTC)
I suggest to ignore the fact that the table is divided into two pages and write the whole table just in one page. I do it with divided pictures (Page:An Anthology of Modern Bohemian Poetry.pdf/12). --Jan Kameníček (talk) 09:05, 20 January 2019 (UTC)

Adding pages to existing scanned book (Once A Week Volume II)[edit]

Hi — what should I do if I am looking through a scanned-and-indexed book and notice that some pages are missing? Would it be possible, if I have to insert two pages after scan number 140, to number them 140a and 140b? Levana Taylor (talk) 21:37, 17 January 2019 (UTC)

It is correct to raise the issue here. Please post the Index page, which page number and where to find the missing pages. Page numbering will be taken care accordingly. Someone will fix it.— Mpaa (talk) 22:05, 17 January 2019 (UTC)
Thanks. The problematic book is Once a Week, Series 1, Volume II Dec 1859 to June 1860. I haven't finished looking through it all yet, but the problems I so-far found are: two pages missing after scan no. 140 [it is pages 128 and 129 of the book that are missing]; scan no. 462 cannot OCR; from scan 218 onward existing OCR'd texts are not matched with the correct page image. As for a source for a scan, there is Google Books. Levana Taylor (talk) 22:19, 17 January 2019 (UTC)
@Levana Taylor: -- I have added the two missing pages. Now if you want a page move, please give specifics: start page number, end page number, increment order. Hrishikes (talk) 08:23, 18 January 2019 (UTC)
@Hrishikes: I had a look at this as well.. The first batch of re-alignment needs to start at Page:Once_a_Week,_Series_1,_Volume_II_Dec_1859_to_June_1860.pdf/141 currently this has the text for page 130, but the scan is for page 128, this misalignment continues to the text currently at Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/240. after which there are a further 2 missing pages that need to be added. I'm still looking into what the misalignment for subsequent pages is. ShakespeareFan00 (talk) 10:08, 18 January 2019 (UTC)
And there are plenty of other problems. The scan of 208 is in the right place, it is correctly followed by 209, but then we wrongly have 208 again, 209 again, and then 210 and so on as it should be. Then, where 225 ought to be, we have an image of 227 (but the same image is also in its correct place). Then, 228 and 229 are missing. 258 is followed by 261 then 260 then 261 again then 262 and 263, then we skip to 266, 267, 266 again, 267 again, then 268 onward are correct until 276 is followed by 279, 278, 281, 282, 281 again, 282 again. 283 and onward are OK, until 420 and 421 are missing and 422 & 423 appear twice. 502 and 503 are missing. Then later pages 512 and 513 appear twice. 602 and 603 are missing.
Let me summarize all that by naming ranges that have problems, starting and ending each range with pages that are correct. 207-210 ; 224-230 ; 258-268 ; 276-283 ; 419-424 ; 501-504 ; 511-514 ; 601-604.
Also the scans of 362 and 579 are bad (edge cut off), and the scan of 453 is crooked. That's all I see for now :-) Levana Taylor (talk) 11:15, 18 January 2019 (UTC)

@ShakespeareFan00, @Levana Taylor: -- Added pages 228 & 229. Replaced page 362. I did not find the other problems mentioned, may be a cache issue. Clearing the cache or opening in another browser should sort it out. Hrishikes (talk) 12:51, 18 January 2019 (UTC)

You are right, rats, well, now I know which browser not to use. The different browser I tried did load the pages without skipping or repeating them.
I still think 579 and 453 need to be replaced, though. After that, all that remains is getting the texts back with the images they belong to. Thanks for your help! Levana Taylor (talk) 13:31, 18 January 2019 (UTC)
Here is a guide to where the OCR'd text of various pages has ended up:
  • From page 128 to 206, the text is two pages before the image. YesY
  • From page 209 to 225, the text is four pages before the image. YesY
  • From page 226 to 227, the text is two pages before the image. YesY
  • From page 230 to 243, the text is four pages before the image. YesY
  • From page 246 to 281, the text is six pages before the image. YesY
  • From page 282 to 299, the text is four pages before the image. YesY
  • From page 306 to 325, the text is six pages before the image. YesY
  • The text of page 340 is four pages before. YesY
  • The text of page 350 is four pages before. YesY
  • From page 406 to 423, the text is six pages before the image. YesY
  • From page 424 to 428, the text is four pages before the image. YesY
  • From page 452 to 456, the text is four pages before the image. YesY
  • From page 506 to 515, the text is four pages before the image. YesY
  • From page 606 to 622, the text is four pages before the image. YesY
  • Pages 619 to 622 are incorrectly marked "without text."
Levana Taylor (talk) 20:18, 18 January 2019 (UTC)
Yes check.svg DoneHrishikes (talk) 05:33, 19 January 2019 (UTC)
Thank you very much! I have checked the repaired areas, they are OK. I have removed the repair templates and the temporary page nubmers ... Levana Taylor (talk) 05:47, 19 January 2019 (UTC)

Wrong page title[edit]

Index:The Book of the Aquarium and Cater Cabinet.djvu is clearly at the wrong page title: It should be at Index:The Book of the Aquarium and Water Cabinet.djvu. The text is also not linked on the author's page. The link that should go to this book is a redlink. How do I fix this? Thanks. Diadophis (talk) 03:38, 20 January 2019 (UTC)

Yes check.svg Done Nice eye, Diadophis! —Justin (koavf)TCM 04:14, 20 January 2019 (UTC)

Update on 1860 Once a Week: pages for special work[edit]

I'm making good progress in putting together this magazine volume, Once a Week Vol II, into a properly constructed form that will then only need proofreading. However, I've seen some pages that have formatting that I don't know how to do: tables, and images that are more complicated than mere full-width insertion (I can and do handle poems, though). I've marked all pages that are complicated as "problematic" in case anyone wants to look at them. Levana Taylor (talk) 14:10, 20 January 2019 (UTC)

references with symbols[edit]

Is there a template that allows us to follow the style of the original document by indicating references with * † ‡ instead of numbers? Levana Taylor (talk) 17:22, 21 January 2019 (UTC)

The "house" style here is to convert them all to numbers—see Help:Footnotes and endnotes. This is because when the text is transcluded the list of references goes to the end rather than displaying at each page. If we to use symbols, then there would multiple references with the same marker and the reader would not know which one applied in a particular case. Beeswaxcandle (talk) 17:29, 21 January 2019 (UTC)
Yep, that makes sense. But I thought maybe someone had programmed a template that would apply to the whole article and display the reference list with custom symbols instead of numbers. Levana Taylor (talk) 17:46, 21 January 2019 (UTC)
That wouldn't solve the problem of multiply repeated symbols. There are more than a few limitations of physical printing-by-page that simply do not transfer well to electronic format. --EncycloPetey (talk) 17:48, 21 January 2019 (UTC)
Why would repeating symbols be a problem? the current system counts up the number of <ref> in the article and displays them in order as 1, 2, 3. Why couldn't it display them as * † ‡? Levana Taylor (talk) 17:59, 21 January 2019 (UTC)
Imagine you have a text with 59 references across 100 pages. Each reference in the original is either * † or ‡. By numbering the footnotes, they can be numbered 1 through 59. If using symbols, there aren't 59 footnote symbols, so you would get two dozen * and a dozen † and a handful of ‡, all on the same page, and it would not be clear which * refers to which footnote. —Beleg Tâl (talk) 18:19, 21 January 2019 (UTC)
I know, it wouldn't be useful for anything but a short piece with not more than 5 references (the number of traditional symbols — though you then go to **, ††, etc.). I will stop beating a dead horse now :-) Levana Taylor (talk) 19:07, 21 January 2019 (UTC)

Index:Field Book of Stars.djvu[edit]

Was looking at this.. Text is good, but the 'diagrams' seem clipped in the scans? Anyone good with SVG to be able to make 'repairable' versions? ShakespeareFan00 (talk) 00:31, 22 January 2019 (UTC)

Looks like they're supposed to be like that —Beleg Tâl (talk) 01:53, 22 January 2019 (UTC)
Images can be taken from the Google-digitized version: https://archive.org/details/afieldbookstars01olcogoog and https://catalog.hathitrust.org/Record/001476074. Example: c:File:A Field Book of Stars 131.jpg (taken from HathiTrust). -- Hrishikes (talk) 02:01, 22 January 2019 (UTC)

Broken links to machine-translated text on an external site[edit]

What should we do about On some controversies regarding origin and nationality of Nezami Ganjavi? The Russian text has been released under a free licence, and a page has also been created here at ENWS, but only the abstract, keywords and contents page are in English. The bulk of the document is in the form of external links to Google Translate which are now broken. Even if the links could be fixed, it seems odd for Wikisource to be directing users to machine-translated text and for something to be "on" ENWS when it's actually on an external site. The research looks interesting, but if almost all of it is in Russian and not English, does it belong on English Wikisource? MartinPoulter (talk) 21:12, 22 January 2019 (UTC)

OCR is off by one page[edit]

In Index:Philosophical Transactions - Volume 053.djvu the OCR is off by one page: OCR for page 2 appears on page 1 and so on. Thanks in advance for any help. MartinPoulter (talk) 21:30, 23 January 2019 (UTC)

I fixed the file (that was wrong), but I think there is more to it. In djview text is aligned with pages but not in Index/Page. I think this is similar to what hapened with an EB199x Volume. Something goes wrong with how text is loaded, but we were not able to explain it (at least so I recall).— Mpaa (talk) 21:04, 24 January 2019 (UTC)
Filed phab:T214729.— Mpaa (talk) 21:17, 25 January 2019 (UTC)

Help with layout positioning[edit]

Can you help me make this page] look a little prettier? I've got two tables of contents positioned next to each other, using "float." I think they would look better with more space between them (that is, in a narrow window they would) and/or maybe a line between --how would I do that? Any other proposals for layout? Levana Taylor (talk) 04:01, 24 January 2019 (UTC)

I'd merge the two lists, maybe something like this:
  • Part I
    • Chapter 1
    • Chapter 2
    • Chapter 3
  • Part II
    • Chapter 4
  • Part III
and so forth. —Beleg Tâl (talk) 13:50, 24 January 2019 (UTC)
I still think parallel columns are preferable, but when you said "combine", I said, "Of course! I can put both lists in one table, and that'll give lots of formatting possibilities." The result was this, which I really like. Thanks for shaking my mind loose! Levana Taylor (talk) 17:35, 24 January 2019 (UTC)

Meat for Thrifty Meals[edit]

Can someone come up with a "better" solution for the images that have left or right captions? {{FIS}} doesn't seem to handle them cleanly...? ShakespeareFan00 (talk) 20:28, 25 January 2019 (UTC)

"Editor's comment" in EB1911 page[edit]

I've been doing some work in the 1911 Encyclopaedia Britannica, and came across this page:

https://en.wikisource.org/wiki/Page:EB1911_-_Volume_11.djvu/403

It includes the following footnote added by a wiki editor: "EDITOR'S COMMENT (FEB. 2015): The date in 1815 given by the original text is wrong and should be the 8th of August."

They may be right about the date being wrong, but my understanding was that we digitise what's there, not correct it when it's wrong. Seems to me like we'd be adding a lot of footnotes to a 100-year-old encyclopedia if we did that. Should this footnote be removed? Chuntuk (talk) 01:07, 26 January 2019 (UTC)

@Chuntuk: you are quite correct. I have replaced the footnote with an HTML comment. You can also use {{SIC}} if desired, but I don't think that's desirable here since this is not a typo —Beleg Tâl (talk) 01:34, 26 January 2019 (UTC)
I would usually move comments like that to the talk page for the article. However, the claim is completely unsupported by any reference at all, which really makes it worthless as an emendation. --EncycloPetey (talk) 01:37, 26 January 2019 (UTC)

Parenthetical can't necessarily appear in a pagelist tag on an Index page..[edit]

I've mentioned this in a phabricator ticket here - https://phabricator.wikimedia.org/T214827 and (https://phabricator.wikimedia.org/T214797 in respect of related issue).

However, the work-around (until the script is repaired), would be to amend the Index pages containing parenthesised page numbering inside a pagelist. So:-

  • Does anyone have a script which could at the very least identify ALL affected Index pages?
  • Could an appropriate edit-filter be implemented to check for this when an attempt is made to save an Index page?

Although it may also be possible to have an automated script 'repair' many of the affected Index pages, I'm not sure it would be able to do this reliably in some contexts. ShakespeareFan00 (talk) 10:01, 28 January 2019 (UTC)

@Billinghurst: Per your closure of those tickets, you stated was this solely a local issue thus here would be the "appropriate" place for further discussions. One of the relevant documentation pages has been updated already. If you would like to outline work-arounds and solutions below, it would be appreciated.

ShakespeareFan00 (talk) 12:22, 28 January 2019 (UTC)

A Preliminary list of Index pages to repair is : https://en.wikisource.org/w/index.php?title=Special:Search&limit=525&offset=0&ns106=1&search=insource%3A%2F%5C%3Cpagelist%28%28.%29%2A%29%5C%3D%28%28.%29%2A%29%5C%28%28%28.%29%2A%29%5C%3E%2F&advancedSearch-current=%7B%22namespaces%22%3A%5B106%5D%7D with apologies for the lengthy escaped portion. Anyone want to go through this assist in resolving the issue? ShakespeareFan00 (talk) 14:50, 28 January 2019 (UTC)
I can’t parse the regex in the above comment to see where exactly the problem lies, but it seems to be producing some false positives. For example, the first item in the “list of Index pages to repair” is Index:United States Statutes at Large Volume 12.djvu, but that page does not use parentheses in any of its <pagelist> calls. Is it possible that the regex is flagging all pages that (1) call <pagelist> and (2) have a parenthesis anywhere on the page, whether or not it is part of the <pagelist> call? Because that would substantially overstate the number of pages that need to be repaired. Tarmstro99 19:30, 28 January 2019 (UTC)
Yes, the regexp isn't perfect. If you want to generate a better regexp, feel free, the current regexp was \<pagelist((.)*)\=((.)*)\(((.)*)\/\> . Thanks.. I estimate about 200 Index pages may be affected, The search generates 500 or so results and many false positives :( ShakespeareFan00 (talk) 21:28, 28 January 2019 (UTC)

vertically-centered asterisk?[edit]

I have been pretty successful so far in finding templates that reproduce the special typographic features used in the 1860 magazine I'm entering, but one I can't find is a largeish asterisk vertically-centered in the line. Levana Taylor (talk) 08:59, 27 January 2019 (UTC)

UPDATE: Problem solved by using Unicode &ff0a;. Levana Taylor (talk) 10:56, 27 January 2019 (UTC)

@Levana Taylor: You could also use {{...|3|*}} --EncycloPetey (talk) 14:46, 27 January 2019 (UTC)
Fullwidth characters are not really for use in English texts; they're designed for use with Eastern Asian scripts that are inherently monospaced, and when Latin characters are stuck in, they are either halfwidth or fullwidth. EncycloPetey's solution is probably best.--Prosfilaes (talk) 03:28, 28 January 2019 (UTC)
OK, then that particular asterisk is not the right one. The main problem with the regular asterisk is that it's too small. Here is a comparison of the original with {{larger}} asterisks—quite good. And Once a Week (magazine)/Series 1/Volume 2/Where is the other?, various uses of enlarged ordinary asterisks in a story. Not bad, as long as I tweak the formatting enough. The pre-made templates are all wrong. Levana Taylor (talk) 05:00, 28 January 2019 (UTC)
It looks to me like the original publication was simply using a font in which the asterisk * is larger than most fonts. For example this page has an unusually large but otherwise unremarkable asterisk for the note in the bottom left. It's not a different character, just a different font. For this reason, an ordinary * would be the best character to use here. —Beleg Tâl (talk) 23:29, 28 January 2019 (UTC)
Thanks. I'm sorry about asking such trivial questions. I haven't even tried the difficult things like tables yet.

Box formatting[edit]

Another question. Is there a help page explaining how to position text inside a box with a border? The documentation for Template:Frame doesn't explain how to change border properties or which other templates you can use inside it for positioning the text, and it looks like Template:Float box doesn't allow for anything very elaborate inside the box (I could be wrong). Levana Taylor (talk) 00:33, 29 January 2019 (UTC)

{{float box}} allows for arbitrary styling; do you have an example of what you're aiming for? —Beleg Tâl (talk) 23:57, 29 January 2019 (UTC)
The pages in question are this and this. Levana Taylor (talk) 00:51, 30 January 2019 (UTC)
Since that's just a border around the text in question, I would use {{border}} and then use regular formatting inside it, like so:

Knocker to Brown.

London—Helmston.

Happy Jones—communication—twins—come off at once. Be here to-day by 8·30 p.m. train. Immediate.

That's all that's needed. —Beleg Tâl (talk) 03:40, 30 January 2019 (UTC)
I tried that on page 288 but something is wrong: why the big white space at the top? Also the text isn't quite horizontally-centered in the box and I couldn't figure out how to add some padding at the left. Levana Taylor (talk) 04:16, 30 January 2019 (UTC)
@Levana Taylor: -- Yes check.svg Done -- Hrishikes (talk) 04:53, 30 January 2019 (UTC)
@Hrishikes: -- Thanks! I translated the width into ems, though; why did you use px? Levana Taylor (talk) 05:26, 30 January 2019 (UTC)
@Levana Taylor: -- That is ok, px or em, whatever you like. But to note that curly quotes are against the house style. Also, the page should not be set to proofread status without the image. Hrishikes (talk) 05:48, 30 January 2019 (UTC)

Page Numbering anomaly part 3[edit]

Acts of the Constituent Assembly and Dominion Legislature of India 1949/Act1 This numbers from 4 because on the index page the last defined page in the previous page list was "3" (rather than 10 which would the DJVU page index), but does it say this is in the documentation? How am I expected to KNOW this is the expected behaviour by intuition or telepathy?

I was testing what happens with multiple page-lists on a single Index page.. The behaviour is not unexpected, but not seemingly clearly documented. ShakespeareFan00 (talk) 21:22, 30 January 2019 (UTC)

A deleted draft[edit]

After a disagreement on the language of a text, where we seemed to be reaching an understanding, I was going to move the text to my sandbox for then moving to the multilingual Wikisource. The text was marked with a template indicating the percieved language issue (part of the book is in English, and a larger part than I initially realised in a constructed language), but it didn't indicate any particular timeframe, or that the text would neccessarely be deleted (moving to a user subpage, as a draft, would otherwise be a possible option), if I remember correctly. I was also going to ask for second opinions, and normal disputed contributions are normally not deleted that fast in the Wikimedia projects I've been active in, so when going for dinner, I didn't expect much to happen this very same day, at least.

The communication from the editor has indicated that 1) he didn't make much effort checking his statements in the discussion on beforehand 2) he didn't make much effort in understanding what me as another editor wrote, which made the communication frustrating. The discussion can be found at my discussion page.

And then the same editor deleted the whole page.

I would be very happy about undeletion and moving to my sandbox or a subpage of the sandbox. Then I could use the edits I did to it. Undeleting, moving with history to user:flinga/sandbox/alteutonish, 1915 would have been excellent, but I would be grateful for any constructive help.

With regards, Flinga (talk) 19:14, 27 January 2019 (UTC)

You were told repeatedly the work couldn't be hosted here because it was not in English. After 40 minutes of back and forth trying to get you to understand this, you finally agreed that only the introduction was in English. Then you say you suddenly went offline the moment you were told it would be deleted. How inconvenient. It seems that you are only here to cause trouble and disrupt the community. You still have access to the scan; it has a DjVu file with a text layer. Use that text layer on multilingual Wikisource. The English Wikisource does not host works written in artificially constructed languages. --EncycloPetey (talk) 21:30, 27 January 2019 (UTC)
@EncycloPetey: Undelete it and I will import it to mul.ws. —Justin (koavf)TCM 21:45, 27 January 2019 (UTC)
@Koavf: done: Alteutonik. --EncycloPetey (talk) 21:52, 27 January 2019 (UTC)
@EncycloPetey: Thanks. @Flinga: Please define the language at mul:Alteutonik. —Justin (koavf)TCM 22:05, 27 January 2019 (UTC)
The language is w:Tutonish, a "constructed language" like Esperanto or Klingon. (see the linked Wikipedia article) --EncycloPetey (talk) 22:10, 27 January 2019 (UTC)
Both of you: Thank you very much! It is greatly appreciated.
EncycloPetey: I appreciate this last help very much. I have to say I don't really understand what's been our problem. I understand that you feel personally attacked in the last messages, but from my viewpoint 1) I was here to contribute 2) I never did or say anything bad or strange 3) I found your dialogue lacking in terms to reach an understanding, and a cooperative outcome - I found a tone in it that I really don't understand the reason for. I've also contributed to Wikimedia projects for well over a decade without big issues or ever being blocked. I did agree on your point in my (next to) last message, then I went for my break, and I can't see what's neccessarely strange with that - in other words, I didn't see your reply before dinner, and I only tried contributing with a text, which is after all the point of this project, isn't it?
The initial topic of our disagreement was whether the book was in English at all or not, and to what extent. From my viewpoint, that's what we were straightening out, we partially disagreed, and as editors we are normally equals, so I disagree with both the premise and the content of "was being repeadetly told".
I do think giving feedback on this is important for this project.
Again, thank you for that helpful action! Flinga (talk) 22:17, 27 January 2019 (UTC)
Assuming that EncycloPetey got the impression early on that my intention was to cause trouble here, which I only realised long after this discussion, I have apologized for any harm potentially caused by my actions, and for essentially making a too big thing out of it. That apology is also directed to anyone else here who might possibly have been affected. Flinga (talk) 03:03, 2 February 2019 (UTC)

No pages numbers displayed ...[edit]

I cannot figure out why the page numbers are not displaying on the later parts of the transclusion here: Provincial_Geographies_of_India/Volume_4, given that I've implemented the workarounds about removing certain characters

There doesn't seem to be a consistency as to where the page numbering script fails, other than it does not seem to like certain non alphanumeric characters in a defined string to be displayed as a page number.

It would be appreciated if those with technical ability, (rather than continuing to suggest work-arounds) documented what page number formats (and charcters) are accepted by the page numbering script because I am getting tired of tracking down technical minutiae, which don't seem to behave consistently. ShakespeareFan00 (talk) 16:07, 30 January 2019 (UTC)

@ShakespeareFan00: The PageNumbers script rather uncritically stuffs the page number value in a HTML ID attribute, so the safe rules (HTML 4 rules) for what you can put in there is something like: A–Z, a–z, 0–9, hyphen (-), underscore (_), colon (:), and period (.). And the first character must be A–Z or a–z.
As of HTML 5 the rules for ID attributes are much laxer (no space characters, must be at least one character, must be unique in the page), but once you exceed the above list you start running into what are special characters in JavaScript, HTML, URLs, and MediaWiki. Some will work, but more by happy accident than design.
This state of affairs is partly due to MediaWiki:PageNumbers.js being effectively a personal half-experimental project of GOIII's (as far as I've been able to tell, but I wasn't around at the time) that was never fully polished or architected, and partially due to the limitations of what such a script can do without being made a part of MediaWiki proper. For example, some of the limitation stems from needing to use the page numbers as identifiers, and it would be… not trivial… for such a script to generate non-pagenumber derived unique identifiers that retain a connection with a page number that is otherwise used only for display. --Xover (talk) 07:03, 31 January 2019 (UTC)
Thank you.. That explains the failure of "("")" bracketed numbers, "'" would conflict with string terminators used in CSS. I am still not sure as to why a terminating period, caused issues though, but will remove those anyway as it's helps solve the problem. Are you willing to look into this in more depth, so there is a definitive list of characters that shouldn't be present, so that the relevant help documentation can be updated?ShakespeareFan00 (talk) 10:47, 31 January 2019 (UTC)
So far I've got that "(" ")" "." and "'" should not appear in pagelist entries ? ShakespeareFan00 (talk) 10:47, 31 January 2019 (UTC)
Well, I'll certainly be happy to help however I can, but there's no actual code that can be parsed to discover the set. The only real way to find the answer is to try various characters and seeing what fails. And we have several different layers of technology interacting here (WikiMarkup and the MediaWiki parser, the ProofreadPage extension, HTML, and JavaScript. It's not impossible CSS is also involved due to selectors for the relevant identifiers. --Xover (talk) 11:10, 31 January 2019 (UTC)

How to update the display of a DJVU file?[edit]

@ShakespeareFan00: discovered that File:Portland, Oregon, its History and Builders volume 1.djvu lacks an image of page 449. I found an alternate scan of the book, extracted the page, inserted it into the DJVU file, removed a neighboring blank page to preserve pagination, and re-uploaded it. But the page previews are not updating. This is true both on Commons and here on Wikisource (but Commons has updated one of the pages, but not the other; Wikisource has updated neither.) I tried refreshing and purging all involved pages, with no effect. It's been more than 24 hours, so I'm not confident it will "fix itself." Does anybody know what's happening, or what to do about it?

Specifically:

Both display properly on my local copy. -Pete (talk) 23:51, 26 January 2019 (UTC)

This took care of itself, a few days after upload. Must have been a cacheing issue. -Pete (talk) 20:42, 29 January 2019 (UTC)
Hmm, I think I must have looked at the wrong pages before. I have checked several times since posting the above comment (now struck), and the problem persists. -Pete (talk) 20:31, 4 February 2019 (UTC)
I noticed, however, that on Commons when I try to purge the file page, I get an error message that says "purge failed" (without further explanation). I don't know why that purge fails, but perhaps it's related to this problem. -Pete (talk) 20:39, 4 February 2019 (UTC)
@EncycloPetey: would you mind taking a look at this one? I saw your comment on WS:Scriptorium on (what I thought was) a similar case; but this one is a DJVU, not a PDF. How can I get the Wikisource interface to display the page images properly? It still (now a couple weeks later) seems to be displaying pages from the previous, deleted file. -Pete (talk) 20:38, 7 February 2019 (UTC)
My best guess is that a cache purge is needed at Commons to made the change show through. I've tried several things at the Wikisource end, including an edit to the Index page, and several forms of purges and cache clearing. Looking at the page itself from the file while at Commons shows the correct image, and using the OCR generates the correct text; it is only the display through the Proofread Page extension that seems to be at fault. So, unless there is a subtle error in the structure of the DjVu file itself, I suspect it will take a purge at Commons or time for the correction to trickle to Wikisource, or else there is a (new?) problem in the Proofread Page extension. --EncycloPetey (talk) 20:48, 7 February 2019 (UTC)
Thanks. I've added a phabricator ticket (see top of this section). I have a screenshot in phabricator of the failed purge, something I haven't seen before -- so I agree, that seems like the most likely cause. -Pete (talk) 21:54, 7 February 2019 (UTC)

Criminal Law of the People's Republic of China[edit]

I have imported Criminal Law of the People's Republic of China from the website of the Chinese National People's Congress. However, I am not sure whether the text fulfills the requirement of English Wikisource. Would any more experienced users proofread the text, as I am not familiar with the formata of English Wikisource, thank you.廣九直通車 (talk) 07:34, 6 February 2019 (UTC)

Tools for building transclusion pages?[edit]

I'm going through the painstaking process of creating a page for each of the many short chapters of The Souvenir of Western Women. It occurs to me that maybe there are tools or scripts that assist in this stuff -- any suggestions out there? -Pete (talk) 21:15, 2 February 2019 (UTC)

Not to my knowledge. I keep three tabs open: the work's table of contents, the page being transcluded, the page being created. Paste the contents of previous chapter page into new chapter page. Update next/section/previous based on TOC in first tab; update pages being transcluded based on info from second tab; copy whole thing to clipboard, save, click the red link to next chapter and paste content, repeat. It's the most efficient process I've got. —Beleg Tâl (talk) 02:13, 3 February 2019 (UTC)
Or you can create a text file with all the needed information for each chapter (e.g.title, prev, next, start, end, section, etc) and we can set up a script to generate pages. If the format of the file is standardized, it could become a library script to be used e.g. for Bot requests.— Mpaa (talk) 09:50, 3 February 2019 (UTC)
That is a great idea—I am about to add another volume of a magazine with several hundred articles, and I would like to be able to submit a text file for you to run through a script (I don't know how to use scripts myself). The data that would be useful for magazine articles are: title, section, contributor, previous, next, index, from, to, fromsection, tosection, defaultsort, category. Title and index are the same for every article. One category would be sufficient. Levana Taylor (talk) 18:56, 3 February 2019 (UTC)
Beleg Tâl, that's more or less the process I've been using. But I agree, an something like Mpaa describes would be ideal, especially for works like this with many chapters. I'd be happy to try creating a text file for the remaining portion of this work, if you want to give it a try. I should be able to do that tomorrow. Thanks! -Pete (talk) 22:19, 3 February 2019 (UTC)

OK @Mpaa: I have created a text file here: User:Peteforsyth/Souvenir I don't know the best format for you, but I think all the information you need is in there. Please let me know if you need me to make changes. A few comments:

  • I started where the bulk of the redlinks begin. There are, however, already some blue links interspersed among the remaining redlinks. If a page already exists, maybe the script could just ignore that line in the text document and move on to the next. (Ideal would be to check, and add in fields for "previous" and "next" if they are missing. But that's probably hard to code, and not so hard to fix manually.)
  • I have no idea what the most convenient delimiter is, so I put three percent symbols between the chapter title and the page number. I figure it should be easy to search-and-replace if there's a more suitable symbol.
  • The page numbers are offset by eight from the DJVU file. (E.g., page 200 in the original book is the 208th page in the DJVU file.)
  • I removed author names, since there is much inconsistency in how they are presented. I don't mind going through and adding "contributor=" items to the headers after the pages are created.
  • There will be a number of cases in which one page contains parts of two chapters. I have no problem fixing those manually.
  • I would suggest including "year=1905" in each page.

Please let me know if this is sufficient, or if you need me to do anything else. Feel free to edit the page in my user space, if that's the easiest way to communicate what format works best for you. -Pete (talk) 23:27, 4 February 2019 (UTC)

@Mpaa: I realized it's better to include the known contributors so I updated the text file. It now includes the name of the contributor at the end of the line, in the cases where it is known. Please let me know if you have questions. -Pete (talk) 19:46, 5 February 2019 (UTC)
I copied a sample of how it should be to your page. Better tab separated. Order of columns is irrelevant, keep for now the header row as is. Pages in 'djvu' values are better (both from/to). I tried to extrapolate the end page but it is wrong, please review it, there are also sections to be added (see the few pages I have created as MpaaBot, there are errors).
This is just a small script, long way to make it up to a standard bot ... but it will do for this work.— Mpaa (talk) 21:25, 5 February 2019 (UTC)
To add sections, add two columns (fromsection/tosection) with corresponding names of sections as applicable.— Mpaa (talk) 22:03, 5 February 2019 (UTC)
Thank you @Mpaa: that all makes sense. I've now updated the text doc, it's accurate with both page numbers and section numbers. -Pete (talk) 23:47, 6 February 2019 (UTC)
p.s. In some cases the section markers do not yet exist in the pages, but I'll be going through to make sure they are included. -Pete (talk) 23:49, 6 February 2019 (UTC)
That all worked great. Thanks @Mpaa:! And thank you @Victuallers: for all your proofreading work too! I just added it to the "new texts" page and will tweet it out too :) -Pete (talk) 22:28, 8 February 2019 (UTC)

Auxiliary TOC for Once a Week[edit]

I have several questions, but will start with the basics. I would like to use the template {{Auxiliary Table of Contents}} to add a table of contents to volumes of Once a Week magazine, because the volumes don't have a TOC, only a subject index (quite a different thing: for instance, in Volume II the article titled "The European Difficulty" is in the index as "Pope Pius IX"). I have here created part of a contents page for Volume III to show what it might look like, with the auxiliary table of contents above the transcluded index. Before I go on with more of this I would like your thoughts on whether this is a reasonable thing to do.

Some notes on the stylistic choices I made for the TOC: It is divided into numbers not just for usefulness and readability, but also because the book is so divided: In small print at the bottom of the first page of every number is "Vol. XNo. Y," and the date is at the top of every page. As for how the entries are formatted, Title. By Author . . . . . Illustrated by Illustrator., that is directly taken from how the magazine displayed their contents in their advertisements. (I can't simply copy over the advertisment, though, because that isn't quite a TOC either.)

Thoughts? Levana Taylor (talk) 20:32, 6 February 2019 (UTC)

OK, I will take the lack of comments to mean that no one has an objection to my implementing this table of contents, and will move on to the actual help question I wanted to ask.
How should I format the lines in the TOC, given that {{Dotted TOC line}} doesn't work inside of {{Auxiliary Table of Contents}}? (And neither do other potentially useful templates like {{block right}} and {{hi}}.) Is there some other combination of templates I could be using? Ideally, the "Illustrated by" column should be a separate column at the right, left-aligned within itself, and with a caption at the top; it's coincidental that the "comment" field of Auxiliary Table of Contents provides a caption for it. And of course the main column should have a line of dots of the correct length and should wrap with a hanging indent. I could do all that by building a table by hand but that would be a bad idea because it would make the page much too hard to edit. The point of templates is to keep complicated stuff under the hood. Levana Taylor (talk) 17:00, 9 February 2019 (UTC)
I think Dotted TOC line works inside Auxiliary TOC, see e. g. Songs of the Slav. --Jan Kameníček (talk) 18:09, 9 February 2019 (UTC)
Actually Songs of the Slav demonstrates that Dotted TOC line breaks Auxilary TOC: notice that the box is only around the first item in the contents, and the content item title creates a white space inside the box Levana Taylor (talk) 18:35, 9 February 2019 (UTC)
@Levana Taylor: Actually, the auxilliary TOC contains only the first item on purpose, the rest is the real table of contents. But you are right about the white space, although this issue is hardly visible (at least on my monitor) and I would not notice, hadn't you told me. --Jan Kameníček (talk) 19:21, 9 February 2019 (UTC)
OK, I see what you were doing adding the preface there. This is what it looks like with more than one line: not too good! there are two problems to fix. The background color of Aux TOC needs to be set to white to match the bgcolor of the lines, and it doesn't have that option (nor do the lines have the option of changing the color to green). Also, I don't know why the left margin of the Dotted lines is different from the undotted ones. (BTW, feel free to edit that TOC experiments page if you have better ideas!) Levana Taylor (talk) 19:57, 9 February 2019 (UTC)
Using the chapter-width parameter may help with adjusting the left margin. --Jan Kameníček (talk) 20:55, 9 February 2019 (UTC)
Yes, that's much better! Thank you very much!
I have posted on the main Scriptorium to see if any programmers want to fix the background color thing. --Levana Taylor (talk) 21:19, 9 February 2019 (UTC)
As for the chapter-width, it seems that the inconsitency is caused by different default values of both templates: it is 2.5em in TOC line and 3.5em in Dotted TOC line. I do not know whether it is a mistake or whether it is set differently on purpose. --Jan Kameníček (talk) 22:33, 9 February 2019 (UTC)

Index:The Peerage, Baronetage and Knightage of the British Empire Part 1.djvu[edit]

I'm seeing an unusual problem with this , namely that in some of the scans, what should be an n is transposed for a u, and vice versa in the images generated from the DJVU file. Whilst I can in context find many of these, I would like an explanation as to why this is occurring, as it's not exactly convenient to have to proofread against 2 sets of scans ShakespeareFan00 (talk) 21:31, 8 February 2019 (UTC)

Can you give a specific example? From time to time I have noticed scans where what should clearly be an "n" looks like a "u" (and vice versa). For some of these works, I have obtained a hard copy of the same edition, and found that the original does not have this issue. My guess is that the dual process of scanning and compression loses some of the visual distinction in 19th century fonts between the two letters. --EncycloPetey (talk) 21:35, 8 February 2019 (UTC)
Page:The Peerage, Baronetage and Knightage of the British Empire Part 1.djvu/77 being a page with a specfic example. The scans on IA is clean, whereas the DJVU on Wikisoruce have the n u switch. This file was recently re-encoded at a higher resoloution, which I would have reasonably expected to resolve this. If a DJVU version can't provide clean scans, it's time to use the PDF, or some other lossless format that doesn't create these issues ShakespeareFan00 (talk) 21:48, 8 February 2019 (UTC)
The problem is likely a reflection of the tiny font size in which the page was printed. I notice the same sort of issues with footnotes and other tiny print. --EncycloPetey (talk) 21:55, 8 February 2019 (UTC)
The original uploader upped the encoding resolution, just how high does it have to be for something like this? ShakespeareFan00 (talk) 22:13, 8 February 2019 (UTC)
Ad as I said, if DJVU can't provide RELIABLE scan images, maybe it's time to use a more reliable format... PDF isn't ideal because of other issues, and there is no current support for using a TAR/TGZ/ZIP archive of JP2 scans in an easily index way at present, ( and of course using direct scans mean no text layer currently) (sigh :( )ShakespeareFan00 (talk) 22:16, 8 February 2019 (UTC)
DjVu has a feature where the pages can be lossly compressed, which means that images of letters are replaced with images of other letters that are close enough. This can cause this type of problem if that feature is turned on.--Prosfilaes (talk) 15:14, 9 February 2019 (UTC)

DropInital and MarginNote are incompatible..[edit]

See the third paragraph here - Page:Ruffhead - The Statutes at Large, 1763.djvu/84.

So far no-one has come up with a 'satisfactory' solution to this, that works consistently. ShakespeareFan00 (talk) 00:26, 11 February 2019 (UTC)

Also - User:ShakespeareFan00/Sandbox/Firstletter using a custom defined style works correctly, when implemented in the page listed, fails entirely. It would be nice if for once Mediawiki behaved CONSISTENTLY, when the SAME markup is used in two different instances.ShakespeareFan00 (talk) 02:35, 11 February 2019 (UTC)
They both use floated blocks, and as far as I can tell they behave entirely consistently with the standard behaviour of floated blocks, which is that the first one goes up against the margin, and any subsequent ones next to it on the inside. You'd have to use fancy positioning in the template to move it from there to the other side of any intervening floated content. —Beleg Tâl (talk) 02:44, 11 February 2019 (UTC)
That answers the first concern, what it doesn't answer is why IDENTICAL markup is rendering in one instance and NOT in another, Perhaps someone else can take a look at the respective markup, and get Mediawiki to give CONSISTENT renderings , rather than forcing me to play hunt the obscurity every single time I actually want to improve something.... (rage noise) ShakespeareFan00 (talk)
It is also well-known that not everything will display well in both the Page: namespace with its narrow pagewidth and the mainspace with a much wider pagewidth. Don't look for solutions for nice display in the Page: namespace if the transcluded text is behaving nicely in the mainspace. The transclusion is the only thing that counts in the end. Beeswaxcandle (talk) 03:12, 11 February 2019 (UTC)
There is another glitch with the margin-note saying "not-in the original" in that it's currently not positioning correctly. It should be right over on the left, not indented as currently. As I said , it would be nice if someone actually overhualed these templates "properly" so that they will play nicely together, instead of creating frustration for contributors. (sigh) 03:27, 11 February 2019 (UTC)
Well lets see User:ShakespeareFan00/Ruffhead - and the drop cap works, but the note-positioning behaviour doesn't. I'm fed up having to play "guess the stable combination" based on templates, namespace, and phase of the moon, &c. Consistency and repeatability are not unreasonable things to expect from a platform like Wikisource... (sigh) 03:36, 11 February 2019 (UTC)
Page:Ruffhead - The Statutes at Large, 1763.djvu/84 and User:ShakespeareFan00/Ruffhead look the same to me —Beleg Tâl (talk) 03:47, 11 February 2019 (UTC)
They should look identical, barring the page header lines, I am puzzled as to why the firstletter behaviour isn't being applied consistently. Maybe a it's a browser issue, which one are you using? ShakespeareFan00 (talk) 13:41, 11 February 2019 (UTC)
They both look the same to me in both Firefox and Chrome on Windows 10, with or without your .sanity rules in my common.css page. —Beleg Tâl (talk) 16:13, 11 February 2019 (UTC)
It also helps if there's a strightforward way to put experimental CSS so everyone can use it (as opposed to a personal common.css) ... TemplateStyles being one possibility, but at present it's not possible to use Userspace CSS files in a templatestyles src field, for various reasonsShakespeareFan00 (talk) 13:43, 11 February 2019 (UTC)


I've updated it with a working solution: wrap all of the margin notes into a single {{float left}}. This means that when the browser places the dropinitial beside the previous floated block, it places it next to the column of notes as a whole, rather than beside the final floated note in the series. —Beleg Tâl (talk) 17:16, 11 February 2019 (UTC)
Thanks that approach may be what I use to update other pages. :) ShakespeareFan00 (talk) 17:47, 11 February 2019 (UTC)

TemplateStyles[edit]

Hi,

I had some experimental CSS I wanted to test and demonstrate more widely.. Is there a way of using TemplateStyles to link experimental CSS from a User space page into a Page: Wikipedia: or Main namespace page? Or are there limitations on what can appear and where? ShakespeareFan00 (talk) 13:45, 11 February 2019 (UTC)

If this message is red, then the answer is yes. You might need an admin to change the content model of the linked CSS file from "CSS" to "Sanitized CSS". I'm not sure if this requires elevated permissions.Beleg Tâl (talk) 15:26, 11 February 2019 (UTC)
BTW be prudent with this. If you have an experimental CSS rule you want to try out, you should put it in your sandbox and link people to it. If it applies to a particular work, you can create a work-specific template and clearly identify it as an attempt to improve that specific work - noting this both on the template documentation, and within the Index talk page. If you start putting user CSS where people don't expect it, and you forget to remove it afterwards, other editors will not take that kindly. —Beleg Tâl (talk) 15:33, 11 February 2019 (UTC)
Okay so what I want to do is thus entirely impossible, because the CSS selector I want to use can;t be used inline... Thanks ShakespeareFan00 (talk) 15:38, 11 February 2019 (UTC)
@ShakespeareFan00: That doesn't sound like it would matter; what specifically are you trying to do? —Beleg Tâl (talk) 15:58, 11 February 2019 (UTC)
Use a selector to implement ::firstletter behaviour, with a view towards the CSS4? style dropcaps styling, (which would make the currrent dropinital approach less of an issue once browsers support the functionality concerned.) ShakespeareFan00 (talk) 16:10, 11 February 2019 (UTC)
@ShakespeareFan00: Like this?Beleg Tâl (talk) 16:25, 11 February 2019 (UTC)
Yes That was it EXACTLY. Now if that could be tested with some exactign test cases... there might be a replacement for the current {{di}} template. The next problem would be how to handle things like drop initals where a normal sized quote preceeds... hmmm... And thanks for the hint ShakespeareFan00 (talk) 16:29, 11 February 2019 (UTC)
@ShakespeareFan00: FYI, implementing drop initials using ::firstletter should result in exactly the same problems that {{di}} has currently, because you still need to float the element in order to have the second line appear beside it rather than below. Given that a solution to this particular issue has been found, I'd suggest saving yourself the headache until the dropinitial feature in CSS is fully implemented across browsers. —Beleg Tâl (talk) 21:31, 11 February 2019 (UTC)

Sidenotes (ongoing)[edit]

https://en.wikisource.org/wiki/The_Statutes_at_Large_(Ruffhead)/Volume_9/Doncaster:_Small_Debts,_Lighting,_etc._Act_1763

This has overlapping sidenotes, which I made an attempt to resolve by adding an optional 'clear:' in the relevant templates {{Outside}} and {{Outside2}} to try and get the sidenotes to auto wrap (the way {{MarginNote}}'s do.,

The relevant diffs being: https://en.wikisource.org/w/index.php?title=Template:Outside&diff=next&oldid=9100920 https://en.wikisource.org/w/index.php?title=Template:Outside2&diff=prev&oldid=9100921 https://en.wikisource.org/w/index.php?title=Template:Outside_RL&diff=prev&oldid=9100923 https://en.wikisource.org/w/index.php?title=Template:Outside_LR&diff=prev&oldid=9100924 https://en.wikisource.org/w/index.php?title=Template:Outside_L&diff=prev&oldid=9100925 https://en.wikisource.org/w/index.php?title=Template:Outside_R&diff=prev&oldid=9100927

and https://en.wikisource.org/w/index.php?title=Page:Ruffhead_-_The_Statutes_at_Large_-_vol_9.djvu/270&diff=prev&oldid=9100932 Where is the coding mistake, because the fix doesn't seem to being implemented? ShakespeareFan00 (talk) 14:39, 11 February 2019 (UTC)

The Statutes at Large (Ruffhead)/Volume 9/Doncaster: Small_Debts, Lighting, etc. Act 1763

This has overlapping sidenotes, which I made an attempt to resolve by adding an optional 'clear:' in the relevant templates {{Outside}} and {{Outside2}} to try and get the sidenotes to auto wrap (the way {{MarginNote}}'s do.,

The relevant diffs being:

and

Where is the coding mistake, because the fix doesn't seem to being implemented?

ShakespeareFan00 (talk) 14:39, 11 February 2019 (UTC)

Sorry, had trouble parsing your comment. I might be able to help, give me a bit and I'll look into it. —Beleg Tâl (talk) 15:37, 11 February 2019 (UTC)
Part of the issue seems to be that {{Outside R}} isn't passing on a parameter "clearfix" when it should be... ShakespeareFan00 (talk) 15:45, 11 February 2019 (UTC)
sounds of insane laughter... It's ALWAYS a misplaced bracket., anyway I've solved the overlapping sidenotes issue that's been an annoyance for over a decade, with one simple clear: in the Sidenotes code. :) (more insane laughter...) ShakespeareFan00 (talk) 15:51, 11 February 2019 (UTC)
Wow, nicely done! —Beleg Tâl (talk) 15:56, 11 February 2019 (UTC)
Now to figure out why using clear makes it harder to use DropInitial's ;) ShakespeareFan00 (talk) 15:59, 11 February 2019 (UTC)
Dropinitials are just ordinary floats, so they will be cleared like any other floats. —Beleg Tâl (talk) 16:26, 11 February 2019 (UTC)
OK, it's time to think laterally. Why does it have to be sidenotes? Just because in print the decision was made to print the references as sidenotes, why do we have to when presenting the text? After all, putting them there makes the work less accessible to some of our readers. Some possibilities (with thanks to the Braille community):
  1. Regular footnotes collected at the end of the piece of legislation;
  2. Regular footnotes collected at the end of the print-page representation (least acceptable here);
  3. Regular footnotes collected at the end of each section/subsection/subsubsection/paragraph—whichever makes the most sense for the piece of legislation; or
  4. Inline notes marked off in some distinguishable way (e.g. [], {}).
An explanation of the variation from print should be placed in the Notes field of the header in the Mainspace: transclusion.
My own preference would be No. 3. Beeswaxcandle (talk) 18:01, 11 February 2019 (UTC)
I do prefer sidenotes, they look much better and work exactly the way the original author intended. Sidenotes are used for a different purpose than footnotes–they should help the reader find the place in the text where a particular topic is dealt with (while footnotes provide extra information and thus can be placed at the end). What is more, footnotes always disturb the readers forcing them to leave the text and go downwards and then return back, which is OK from time to time, but it is not very comfortable at the beginning of every paragraph. (It is possible that some browsers may have problems with sidenotes, but it is a problem of the particular browser, not ours. It is the browser that needs to be improved. I believe that programmers of browsers should serve the needs of internet users, not vice versa, i.e. internet users adapting their behaviour to make the situation easier for browser programmers). --Jan Kameníček (talk) 19:33, 11 February 2019 (UTC)
If the marginal notes were topic-based, then I would not be recommending changing them to footnotes. However, in this particular situation the notes are not topics, but are providing extra information. The print conventions of the period were to use marginal notes rather than footnotes. In this case there are a lot of notes that need to be attached to each paragraph. As a result when done as sidenotes there are frequent overlaps in the wider mainspace: windows. If we want to continue to allow our pages to be viewed at multiple widths on multiple devices, we need a way to manage the overlaps. Thus my series of suggestions to avoid sidenotes for the references. Beeswaxcandle (talk) 20:06, 11 February 2019 (UTC)
@Beeswaxcandle: As far as I see there is e. g. a part mentioning appointed commissioners, next to which there is a sidenote saying "Commissioners appointed". There is a part saying "...the first Meeting of the said Commissioners shall be held on..." which is accompanied by a side note "First meeting". And so on... They are typical sidenotes attracting the reader to the topic, not notes adding extra information. --Jan Kameníček (talk) 21:25, 11 February 2019 (UTC)
Well my preference is to keep the "subect-titles" as sidenotes (per more recent legislation, if not modern ones ), I'm open minded in respect of what are in effect cross referencing
Compare Page:Ruffhead_-_The_Statutes_at_Large,_1763.djvu/82 vs the MarginNote based approach on Page:Ruffhead_-_The_Statutes_at_Large,_1763.djvu/84 or {{cl-act-p}} elsewhere (which is mostly implemented to have anchoring.) 20:12, 11 February 2019 (UTC)
In respect of a complex page like - [[4]] It works, but it's vomit inducingly ugly...

and ends up with far too much white space in the run of text... Maybe some kinds of better hybrid approach is needed... ShakespeareFan00 (talk) 23:21, 11 February 2019 (UTC)

I found a wrong cite - I just to make one edit[edit]

The wrong page in De Vinne, Invention of Printing (1876).djvu/554

the citation is right,

Johnson J. Typographia, or the Printers' Instructor, including an Account of the Origin of Printing. 24mo. 2 vols. London, 1824.

but the wikilink is wrong. There doesn't seem to have a page for John Johnson (1777-1848) (see [5]) - the page is for John Johnson Jr. Editor of the Johns Hopkins University Studies in Historical and Political Science

That hasn't a Wikipedia either.

can someone make it right - it's too hard for me.

Talk about confusing (talk) 10:37, 13 February 2019 (UTC)

@Talk about confusing: fixed. —Beleg Tâl (talk) 12:56, 13 February 2019 (UTC)

Okay why does parameterising line-height completely stop something working?[edit]

https://en.wikisource.org/w/index.php?title=Template:Right_sidenote&action=history

I've attempted MANY times this morning, to get the sidenote to have closer behaviour in the two respective versions... Something was more seriously clearly broken in the relevant template because parameterising ONE component should not have caused the template to cease rendering utterly.

As I've REPEATEDLY asked in the past, WHERE was the coding error, please? ShakespeareFan00 (talk) 14:13, 13 February 2019 (UTC)

It also doesnt't help that someone else seems to have assumed line-height is supported for SPAN ed content, MDN and W3Schools seem to say otherwise, meaning that the parameter concerned is effectively processed but may not have a visual effect. (sigh) ShakespeareFan00 (talk) 14:32, 13 February 2019 (UTC)

Giving an example:-

{{sidenotes begin|35|11}}
{{right sidenote|A.D 686<br />Cures an earl's wife|height=125}}
{{lorem ipsum|2}}
{{-}}
{{right sidenote|A.D 686<br />Cures an earl's wife|height=140}}
{{lorem ipsum|2}}
{{sidenotes end}}


A.D 686
Cures an earl's wife
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Curabitur pretium tincidunt lacus. Nulla gravida orci a odio. Nullam varius, turpis et commodo pharetra, est eros bibendum elit, nec luctus magna felis sollicitudin mauris. Integer in mauris eu nibh euismod gravida. Duis ac tellus et risus vulputate vehicula. Donec lobortis risus a elit. Etiam tempor. Ut ullamcorper, ligula eu tempor congue, eros est euismod turpis, id tincidunt sapien risus a quam. Maecenas fermentum consequat mi. Donec fermentum. Pellentesque malesuada nulla a mi. Duis sapien sem, aliquet nec, commodo eget, consequat quis, neque. Aliquam faucibus, elit ut dictum aliquet, felis nisl adipiscing sapien, sed malesuada diam lacus eget erat. Cras mollis scelerisque nunc. Nullam arcu. Aliquam consequat. Curabitur augue lorem, dapibus quis, laoreet et, pretium ac, nisi. Aenean magna nisl, mollis quis, molestie eu, feugiat in, orci. In hac habitasse platea dictumst.

A.D 686
Cures an earl's wife
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Curabitur pretium tincidunt lacus. Nulla gravida orci a odio. Nullam varius, turpis et commodo pharetra, est eros bibendum elit, nec luctus magna felis sollicitudin mauris. Integer in mauris eu nibh euismod gravida. Duis ac tellus et risus vulputate vehicula. Donec lobortis risus a elit. Etiam tempor. Ut ullamcorper, ligula eu tempor congue, eros est euismod turpis, id tincidunt sapien risus a quam. Maecenas fermentum consequat mi. Donec fermentum. Pellentesque malesuada nulla a mi. Duis sapien sem, aliquet nec, commodo eget, consequat quis, neque. Aliquam faucibus, elit ut dictum aliquet, felis nisl adipiscing sapien, sed malesuada diam lacus eget erat. Cras mollis scelerisque nunc. Nullam arcu. Aliquam consequat. Curabitur augue lorem, dapibus quis, laoreet et, pretium ac, nisi. Aenean magna nisl, mollis quis, molestie eu, feugiat in, orci. In hac habitasse platea dictumst.


Here the sidenotes should have different line spacings, but with the current templates there is no appreciable visual difference. ShakespeareFan00 (talk) 14:39, 13 February 2019 (UTC)


@ShakespeareFan00: Deep breaths :) Yes, it appears to be primarily that line-height is a block-element parameter being used on an inline element. Should you maybe use display:inline-block;? —Beleg Tâl (talk) 16:22, 13 February 2019 (UTC)
PS since sidenotes look different depending on Layout, perhaps some of these changes should be done in Layout.css rather than in the template. —Beleg Tâl (talk) 16:22, 13 February 2019 (UTC)
And whilst the layout options seem to function outside Mainspace. (the option for previewing them doesn't appear), which is not an acceptable long term approach... I'll revert back my changes for now, as this clearly isn't going to work unless someone does some much more fundamental rethinking (Sigh) :( ShakespeareFan00 (talk) 16:54, 13 February 2019 (UTC)

Something like ? Template:Right sidenote/sandbox.css , if you were willing to go test, clearfix is the solution I mentioned in a previous disscussion, Not sure where it should be implemented. Willing to test further? ShakespeareFan00 (talk) 18:33, 13 February 2019 (UTC)

And on testing that didn't behave.. This is now beyond frustrating, and I'm still no closer to figuring out WHY it's not working. Page:The Heimskringla; or, Chronicle of the Kings of Norway Vol 1.djvu/101 2 sidenotes, but doing clear:right doesn't seem to have the desired effect at all. Perhaps someone else here can calmly explain why it's so hard to figure out floats and clears properly? ShakespeareFan00 (talk) 20:14, 13 February 2019 (UTC)

@ShakespeareFan00: the sidenoteRight class is already defined in the sitewide CSS, and is positioned absolutely - so any dynamic positioning will have no effect. —Beleg Tâl (talk) 22:23, 13 February 2019 (UTC)
Hmm.. So How do we do the clearfix like behaviour, if the flr stuff is not going to have any effect. :( ShakespeareFan00 (talk) 22:25, 13 February 2019 (UTC)
Essentialy how in CSS do we tweak the positioning so they don't overlap in situations like ? Page:The Heimskringla; or, Chronicle of the Kings of Norway Vol 1.djvu/103?}ShakespeareFan00 (talk) 22:27, 13 February 2019 (UTC)
It might not actually be possible... If the sidenote is positioned absolutely, it can't be dynamically affected by the position of other sidenotes. However, if the sidenote is positioned relatively, it can only be placed within its parent, and not in its parent's margin... I think this is a place where CSS may have failed us. —Beleg Tâl (talk) 22:29, 13 February 2019 (UTC)
In the case of sidenotes specifically, it could be possible by forcing a fixed-width margin. —Beleg Tâl (talk) 22:31, 13 February 2019 (UTC)
Can you come up with an alternate approach then, like converting them to footnotes instead? 22:33, 13 February 2019 (UTC)
Converting to footnotes is a viable solution. Honestly I would just use sidenotes and let them overlap, and then we can resurrect this discussion when future versions of CSS are released that might give us more options. —Beleg Tâl (talk) 21:06, 15 February 2019 (UTC)

Best placement for an editorial note[edit]

What's the best place to put the editorial note that ran at the bottom of the first page of this magazine article? I'd imagine others have found an elegant way to deal with this sort of thing... McClure's Magazine/Volume 10/A French Critic's Impressions of America -Pete (talk) 06:43, 15 February 2019 (UTC)

I personally would put it at the bottom of the transcluded page, either as a footnote or using LST. —Beleg Tâl (talk) 14:30, 15 February 2019 (UTC)
Thanks. I did the former, and I'm happy with that. I read the LST page, but I'm not sure I understand what you're getting at with that one. I'm curious, if you're inclined to elaborate. -Pete (talk) 15:16, 17 February 2019 (UTC)

Page:Compendium of US Copyright Office Practices, II (1984).pdf/445..[edit]

And others... Can someone else possibly with AWB, assisst in the repair of various tables over multiple pages? I am cleaning up LOT's of pages, but I am about to burn out doing it manually. ShakespeareFan00 (talk) 23:29, 15 February 2019 (UTC)

I can do a quick AWB run, if you tell me precisely what changes need to be made —Beleg Tâl (talk) 00:53, 17 February 2019 (UTC)
Well I did eventually do this one manually, so some validation would be appreciated... but the basic repair needed elswehere is...
{|
|<row data>
|-

needs converting to

{|
|-
|<row data>

and

{{nop}}
|<row data>
|-

to

{{nop}}
|-
|<row data>

And of course any trailing

|<rowdata>
|-

needs converting to

|-
|<rowdata>

All tables need the row marker at the start of the row, fixing this resolves a large number of 'fostered' content warnings. ShakespeareFan00 (talk) 01:07, 17 February 2019 (UTC)

The other cause of a fostered content warning appears to be:

Header

{| <table style>

Body

{{nop}}
|-
|content
...

As there is no row defined at the point at which the {{nop}} occurs there is content outside the table structure which causes the 'fostered' content warning. Using

<!-- -->
|-
|content
...

instead resolves the error in some situations, but the longer term fix would be for the parser ( and wiki-markup) to explicitly recognise it is inside a table and handle the SOL context for the |- correctly, or by providing an unambiguous continuation syntax. There is a unresolved Phabricator ticket concerning this. ShakespeareFan00 (talk) 10:33, 17 February 2019 (UTC)

Please fix redirect for Volume III of OAW[edit]

I moved Once a Week (magazine)/Series 1/Volume 3 to Once a Week (magazine)/Series 1/Volume III and then decided I should instead have made "Volume III" redirect to "Volume 3" because all existing links are to the latter. Could you please do the deletion and recreation needed to reverse the direction of the redirect? Thanks. Levana Taylor (talk) 00:31, 17 February 2019 (UTC)

Yes check.svg DoneBeleg Tâl (talk) 00:52, 17 February 2019 (UTC)

Page:A biographical dictionary of eminent Scotsmen, vol 1.djvu/337[edit]

Enough..

Either I can waste time running around playing hunt the random whitespace rule, or someone can actually care, and get the parser fixed so it has ONE CONSISTENT and REPEATABLE behaviour for how to handle continued tables. This has been unresolved for some time, which doesn't inspire confidence in the platform used for Wikisource. ShakespeareFan00 (talk) 10:45, 17 February 2019 (UTC)

 ? - there is a consistent and repeatable solution, which you are very familiar with - use {{nop}} to separate table syntax from other content so that they don't collapse into each other —Beleg Tâl (talk) 11:55, 17 February 2019 (UTC)
That was what WAS being used on that page... It was STILL generating a "fostered content" warning, apparently due to the <section /> tag, and also possibly due to the reasons I mentioned in the thread above. ShakespeareFan00 (talk) 14:35, 17 February 2019 (UTC)
Another - Page:January 1916 QST.djvu/11 with the section tag being treated as fostered content (which it is not). As I said, I'm getting frustrated in having to play "guess the handling rule". ONE rule please. ShakespeareFan00 (talk) 15:43, 17 February 2019 (UTC)
What I am saying is that I shouldn't have to remember where {{nop}} (or {{nopt}} or <!-- --> works and where it doesn't. There should be ONE syntax that works in all instances and interactions, without me as a contributor having to guess/test on every single instance. It doesen't help that Wikisource is STILL apparently trying to do multipage tables with a syntax designed for single continuous pages. This isn't the first time I've mentioned this, and the sooner certain people overcome their resistance to actually fixing the real problem and provide a working syntax that doesn't depend on template or comment 'work-arounds' the better. ShakespeareFan00 (talk) 16:22, 17 February 2019 (UTC)
I've proposed something on phabricator - https://phabricator.wikimedia.org/T216367 , we can solve this once and for all.ShakespeareFan00 (talk) 18:22, 17 February 2019 (UTC)
I don't know what a "fostered content warning" is, but I have yet to see a scenario where {{nop}} failed to work as expected. As far as I know {{nop}} is the one syntax that works in all instances--that's kind of the point of it —Beleg Tâl (talk) 20:04, 17 February 2019 (UTC)
What fosteref content is , where there is content appearing that doesn't fit with what media wiki thinks the expected table structure is.
{|
Run of text
|-
|Start of row.
|}

Would generate a warning because after the {| the parser is expecting to see either a | or |-. {{nop}} generates a <p></p> which can only appear within a <td> or <th> tag. Mediawiki in an attempt to clean up the output moves the content to the parent container (I.E Outside the table.). Using a <!-- --> instead to effect the line break does not insert content that shouldn't be there as whitespace between a <table> and a <tr> is acceptable..

In some instance the {{nop}} works because it's appended to the end of the row generated in the header portion...

{|
|-
!header1!!header2{{nop}}
|-
|Data 1|| Data 2
|}

Is what's the parser effectively thinks it's seeing.

Where the header only contains an opening {|

What's actually seen is seemingly

{|{{nop}}
|-
|Data 1||Data 2
|}

which breaks the intended stucture as the parser isn't expecting to see a <p></p> immediately after a <table>.

Because figuring these interactions out is tiresome, the proposal was a cleaner method of indicating the ditching of the initial <table>...<tbody> header code, that puts the table generation ENTIRELY within the body text of a page, which is one less set of handling rules to deal with and should be the repeatable and consistent approach desired. ShakespeareFan00 (talk) 20:50, 17 February 2019 (UTC)


In respect of the proposal, what the parser would see is something like
<!-- first page -->
{| nofooter=true 
|+caption
|-
! Header 1 !! Header 2
|-
|Data 1|| Data 2
|}
<!-- next page -->
{| noheader=true 
|-ribbon=true <!-- I.E. Supress display of next row when transcluded. -->
! Header 1 !! Header 2
|-
|Data 1|| Data 2
|}

respectively and this would generate from page

<table>
<caption>caption
</caption>
<tbody><tr>
<th>Header 1</th>
<th>Header 2
</th></tr>
<tr>
<td>Data 1</td>
<td>Data 2
</td></tr></tbody></table>

<table>

<tbody><tr>
<th>Header 1</th>
<th>Header 2
</th></tr>
<tr>
<td>Data 1</td>
<td>Data 2
</td></tr></tbody></table>
</div>

For the two pages in Page namespace

and

<table>
<caption>caption
</caption>
<tbody><tr>
<th>Header 1</th>
<th>Header 2
</th></tr>
<tr>
<td>Data 1</td>
<td>Data 2
</td></tr></tr>
<tr>
<td>Data 1</td>
<td>Data 2
</td></tr></tbody></table>
</div>

on transclusion, which is all within HTML5 structuring rules with no need for <p></p> or other insertions outside of <tr><th> etc.. and entirely linear.

Fixing this for good at parser level avoids the complications and is easier to debug. Spotting a missing noheader/nofooter in the table syntax is easier, then figuring out the absence of various line-feeds and template combinations.ShakespeareFan00 (talk) 21:01, 17 February 2019 (UTC)

Next step would be figuring out how to more precisely define how to handle no-footer/no-header rules work in templates which are transcluded to pages which are transcluded to mainspace., but these could be more tightly and rigidly defined than the current approaches.

ShakespeareFan00 (talk) 21:18, 17 February 2019 (UTC)

The other consideration, is of course where to put a suitable 'gap' so the page numbering script works correctly (Sigh) :(

ShakespeareFan00 (talk) 21:23, 17 February 2019 (UTC)

It would also be NICE if someone documented where precisely the parser expects or inserts whitespace.. ShakespeareFan00 (talk) 21:25, 17 February 2019 (UTC)
As you probably know, headers and footers are simply <noinclude /> tags. You could use this knowledge to your advantage if you liked, for example:
<!-- first page -->
{| 
|+caption
|-
! Header 1 !! Header 2
|-
|Data 1|| Data 2
<noinclude>
|-
|}</noinclude>
<!-- next page -->
## LST ##
<noinclude>
{|
|-
! Header 1 !! Header 2
</noinclude>
|-
|Data 1|| Data 2
|-
|}
Beleg Tâl (talk) 21:39, 17 February 2019 (UTC)
You could also, alternatively, simply ignore the "fostered content" warnings. Where do you even see those anyway? —Beleg Tâl (talk) 21:42, 17 February 2019 (UTC)
Special:LintErrors/fostered , sometimes I'm also seeing them with "Missing end tag" errors for DIV tags. The Missing end tag errors are also useufl for finding unpaired /s /e templates and unclosed italics. :) ShakespeareFan00 (talk) 21:48, 17 February 2019 (UTC)

Delete my account[edit]

Your site is really complicated. Not user friendly

I want to delete my account please. unsigned comment by Christianview (talk) .

@Christianview: it is not possible to delete an account. However, you can go to Wikipedia and request a courtesy vanishing in order to make your contributions harder to find, or to remove your association with your edits. Have a look at w:Wikipedia:Courtesy vanishing for more information. —Beleg Tâl (talk) 23:42, 17 February 2019 (UTC)

Federal Register Template + Proclamation 7463[edit]

It seems that {{USFR}} uses outdated links, see for example at Proclamation_7463: {{USFR|66|48199}} turns to 66 FR 48199. For that matter, is Proclamation_7463 referencing the correct FR item? Because wikipedia:List_of_presidential_proclamations_by_George_W._Bush#cite_ref-66 and govinfo.gov say it’s 66 FR 48197. --Jaquento (talk) 17:46, 19 February 2019 (UTC)

Transclusion difficulty[edit]

I formatted the verse play The secret that can't be kept by copying verbatim the formatting of the Yale 1918 "Macbeth". This works fine except that I would like to add one additional improvement: I would like to confine the entire text column to a width of 32em so that when the screen is wide the right-floated elements are not ridiculously far from the left-aligned elements. In principle, I would do this by placing everything in a block. But I don't understand how to make this work correctly when dealing with multiple transcluded pages. The Yale "Macbeth" uses some tricks I don't understand, involving sections and a dummy header, in order to carry over {{dent}} from page to page. I copied this but don't know how to adapt it to carry over the block also. Levana Taylor (talk) 02:07, 20 February 2019 (UTC)

You can use {{block center}}. Look at the documentation of the template for help and you will see how to use with multiple pages. Jpez (talk) 05:42, 20 February 2019 (UTC)
That worked! Thanks 06:05, 20 February 2019 (UTC)

Float plus blank line[edit]

When formatting articles such as St. Anne's Lake, Transylvania, I use {{float right}} to append the signature to the end of the article text. This article also has footnotes, so for the sake of readability there should be a blank line between the signature and the rule above the footnotes: The problem is that

{{float right}} {{dhr}} {{rule}}

doesn't always produce the desired result because of the way that the float interacts with the elements below it. If I understand correctly, this problem is what the "clear" parameter is used for; but where should I put the "clear"? Levana Taylor (talk) 22:20, 20 February 2019 (UTC)

Hi I've added noninclude tags to the rule on the proofread page. This will make the rule viewable there but won't transclude it to the main namespace. Then I added a blank line and then a rule plus the reference tag to the main namespace which gave the blank line you were asking for. Using the reference tag you can place footnotes wherever you want in the main namespace, whereas if you don't use it they get automatically placed right under the text. Jpez (talk) 05:44, 21 February 2019 (UTC)
Got it, thanks! Levana Taylor (talk) 07:28, 21 February 2019 (UTC)

Shakespeare DjVu help[edit]

Can someone take [6], which is a copy of The Merchant of Venice (1923) and generate a DjVu file and upload it to Commons? It seems IA have not generated a proper DjVu file for this work. The file is needed as part of Portal:The Yale Shakespeare, a current project that is actively generating scan-backed editions of Shakespeare's plays.

For consistency, the Commons file should be named File:Merchant of Venice (1923) Yale.djvu --EncycloPetey (talk) 16:46, 20 February 2019 (UTC)

Aside: The Merchant of Venice, surely? --Xover (talk) 17:44, 20 February 2019 (UTC)
Not for the filename, only for the title of the work. There is a difference. --EncycloPetey (talk) 19:57, 20 February 2019 (UTC)
Sure, but why have a needless diifference between the filename and the title? The "The" never hurt nobody! :) --Xover (talk) 05:15, 21 February 2019 (UTC)
Not true. Including "The" in the filename creates lots of extra work for any derivative files that have to be sorted alphabetically. Modern library databases routinely drop "an", "an", and "the" from the front of titles for this reason. Some of the other titles have been shortened as well, such as "King Lear (1917) Yale.djvu" instead of "The Chronicle History of the Life and Death of King Lear and His Three Daughters (1917) Yale.djvu" --EncycloPetey (talk) 20:58, 23 February 2019 (UTC)
@EncycloPetey: I gotcha. Check in 10 minutes. —Justin (koavf)TCM 19:41, 20 February 2019 (UTC)
Thanks! --EncycloPetey (talk) 20:12, 20 February 2019 (UTC)

suppress space between paragraphs[edit]

What Is the best way to suppress the paragraph-space between two pieces of text that are one above the other? (Not using "float" because I want to position them exactly.) The poem tag is one; are there others? --Levana Taylor (talk) 20:00, 23 February 2019 (UTC)

Can you give an example? It's unclear what you are trying to do, or why "suppression" of the space is needed. --EncycloPetey (talk) 20:02, 23 February 2019 (UTC)
See the letter in this story. I have the signature positioned by means of <br/> and {{gap}}, but I would rather right-align it; {{right}} would cause a paragraph break between the signature and the line above. Levana Taylor (talk) 20:42, 23 February 2019 (UTC)
I've used {{float right}}, although for letters in the middle of text, I might use a {{block center}} with fixed width to help set it off from the body text. Short letters like this suffer from the switch to electronic format by virtue of no longer being constrained to a column of fixed width. --EncycloPetey (talk) 20:54, 23 February 2019 (UTC)

Gadget to add {{nop}} seemingly non functional..[edit]

Has there been a change in mediawiki recently... This used to generate a msg box and doesn't currently...ShakespeareFan00 (talk) 15:07, 24 February 2019 (UTC)

  • It's failing for me too. I'm not quite sure why, but it is using a jQuery ajax call rather than the API, so I'd like to make this change to the gadget code to fix the issue. Sam Wilson 01:17, 25 February 2019 (UTC)
Not working for me still. Has this been reported? Zoeannl (talk) 04:55, 3 March 2019 (UTC)
I've requested a change here: MediaWiki_talk:Gadget-NopInserter.js#Update_wikitext-getting_code (I'm not an interface editor so can't edit the gadget myself). —Sam Wilson 09:42, 3 March 2019 (UTC)

Hanging indent in poems[edit]

When you have a poem with some extremely long lines, it'd be good to allow for wrapping by specifying a hanging indent. But if you add {{hi}} to the start of the poem, it assumes that successive lines of the poem separated by a single line break are the same paragraph and indents every line after the first one. Solution? Levana Taylor (talk) 19:00, 24 February 2019 (UTC)

So what you want to happen is, rather than:

And there, in middle of the path, a leper did appear;
In a deep slough the leper lay; to help would none come near,
Though earnestly he thence did cry, "For God our Saviour's sake,
From out this fearful jeopardy a Christian brother take."

— you would prefer something along the lines of:

And there, in middle of the path, a leper did appear;

In a deep slough the leper lay; to help would none come near,

Though earnestly he thence did cry, "For God our Saviour's sake,

From out this fearful jeopardy a Christian brother take."

? 114.74.213.158 19:46, 24 February 2019 (UTC)

If you don't want a hanging indent, then don't use hanging indent; use a div.

And there, in middle of the path, a leper did appear;
In a deep slough the leper lay; to help would none come near,
Though earnestly he thence did cry, "For God our Saviour's sake,
From out this fearful jeopardy a Christian brother take."

--EncycloPetey (talk) 21:36, 24 February 2019 (UTC)

If I understand it right, what Levana Taylor wants to achieve is something like this:

And there, in middle of the path, a leper did appear;

In a deep slough the leper lay; to help would none come near,

Though earnestly he thence did cry, "For God our Saviour's sake,

From out this fearful jeopardy a Christian brother take."


The solution I have used is not very good and I would be also grateful for being shown some better. The one suggested at the top looks quite complicated to me. --Jan Kameníček (talk) 21:44, 24 February 2019 (UTC)

If the problem is the wrapping of lines, and getting them to wrap in specific places, then that is not usually replicated in Wikisource. The place where a line wraps is fundamentally a function of the page width in the publication. But at this point we're speculating, because we don't know for certain what is being attempted. --EncycloPetey (talk) 22:18, 24 February 2019 (UTC)
I am not sure if we understand each other. The problem as I see it is in making the high indent inside the <poem></poem> tags. (I wrapped the poem in {{block left}} only to make sure that the high indent is visible.) If you watch a poem with long lines on a large monitor, then there is usually enough space and no need to indent it. But when you watch it on a narrow display, part of the verse often gets to another line and needs to be indented similarly, as it is indented in books with narrow pages. The same problem can also appear in the Page namespace, where the right half of the screen is dedicated to the scan and thus the remaining space is much narrower.
Example: I have such problem when displaying e. g. Page:An_Anthology of Modern Bohemian Poetry.pdf/35 on a small monitor. While in the scan it is indented, in the left window all lines (including the parts of verses which have overflown to another line) are unindented. --Jan Kameníček (talk) 23:11, 24 February 2019 (UTC)

The indenting of a single wrapped line within a paragraph is not really supported in HTML/CSS. I strongly recommend that you not try to replicate it, but rather that you allow it to wrap without indenting which is the default wrap behaviour for digital documents. —Beleg Tâl (talk) 00:12, 25 February 2019 (UTC)

@Beleg Tâl: The problem with poems is that you need to distinguish visually a new verse from a verse which has just overflown to another line because of its length. The indent is not only the solution used in printed books, it is probably the only really suitable solution. --Jan Kameníček (talk) 10:12, 25 February 2019 (UTC)
Hmm.

This is a poem.
It is really rather good.
I wrote it myself.
The only trouble is:
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. it has a really long line.

Is this the effect you're going for, Levana? --Xover (talk) 07:14, 25 February 2019 (UTC)
Yep, right on! "Inline block" eh? I take it there isn't a template for that? Levana Taylor (talk) 09:49, 25 February 2019 (UTC)
@Levana Taylor: No existing template, no, but it should be easy enough to create one if there is need and no objections. --Xover (talk) 17:40, 25 February 2019 (UTC)
@Levana Taylor: Absent immediate objections I've created {{hanging indent inline}} (shortcut {{hin}}) that you can try out. I'll look into whether it can be extended to support multi-page use, but for now it'll only work for lines on a single page. --Xover (talk) 07:47, 26 February 2019 (UTC)
Works great. The depth of the indent is right. Levana Taylor (talk) 20:44, 26 February 2019 (UTC)
This solution helps with one particular extremely long line, but it seems too complicated to be used regularly throughout the whole long poems or even anthologies of poems. As I have pointed above, even moderately long lines need to be indented when vied on small displays. For example the Page:An Anthology of Modern Bohemian Poetry.pdf/45 is a real mess on my small monitor, but the suggested solution means that every single line has to be indented in this complicated way separately. It would be great if some simple template wrapping the whole poem could solve it. Jan Kameníček (talk) 10:05, 25 February 2019 (UTC)
Here is what I approximately see on my small monitor in the narrow window in the Page namespace (to achieve it, I limited the width of the block here):

Hidden springs were playing music and my day its song thereto was chanting,
On the melancholy shores.
The grief of bygone life, from whence I came was wafted to me from the fragrance,
And from the converse of the trees and from the heavy drone of insects o'er the waters,
And there lay whole centuries, betwixt my hands, that blossoms plucked, and them
Betwixt my countenance and a mystic world,
That in a thousand questioning glances in my spirit mutely gazed.

However, a new unindented line usually means a new verse, continuing overflown verse needs to be indented, otherwise the poem is difficult to read. Here is what I should see ideally:

Hidden springs were playing music and my day its song thereto was chanting,

On the melancholy shores.

The grief of bygone life, from whence I came was wafted to me from the fragrance,

And from the converse of the trees and from the heavy drone of insects o'er the waters,

And there lay whole centuries, betwixt my hands, that blossoms plucked, and them

Betwixt my countenance and a mystic world,

That in a thousand questioning glances in my spirit mutely gazed.

Is there a better way to achieve it throughout the whole poem or even series of poems?

BTW: Here I used an example when the width of the space for the poem is limited by the page namespace layout, but sometimes it can be limited in the main namespace too, for example by using the template {{Bilingual}}, which divides the screen into two halves. --Jan Kameníček (talk) 10:30, 25 February 2019 (UTC)

@Jan.Kamenicek: Your problem is a separate case, and as Beleg Tâl said above, there is really no good way to achieve that. It's possible of course, but it would probably entail something like wrapping the entire poem in a template with each line a separate parameter, and then doing a lot of moderately complicated and fragile styling. It's not something I would recommend pursuing unless the need was great. --Xover (talk) 17:40, 25 February 2019 (UTC)
@Xover: I do not think it is a separate case, the problem also arises always when you try to read any poem with average-long lines e. g. on a small mobile. It turns into a mess where it is very difficult to find out where a verse ends and a new one begins. --Jan Kameníček (talk) 17:53, 25 February 2019 (UTC)
@Jan.Kamenicek: I agree that it is a problem. What I'm saying is that it is a different problem, and, due to the limitations of HTML/CSS that Beleg Tâl mentioned above, it cannot use the same same solution. Any solution that I can see to the problem you're talking about would be complicated and fragile. Sorry. --Xover (talk) 18:08, 25 February 2019 (UTC)
There is an experimental CSS property text-indent:each-line. When this or an equivalent is published, it will be easy to add this to existing and new poems. —Beleg Tâl (talk) 18:32, 25 February 2019 (UTC)
If you use Xover's solution on any line longer than 35 em (30 em to really be on the safe side) it takes care of any ordinary, rather than narrow, screen width. But I agree with Jan Kameníček that this doesn't address the real problem. Let's hope for improved CSS soon! Levana Taylor (talk) 19:49, 25 February 2019 (UTC)

Contents page numbers don't match the actual page numbers[edit]

I am proofreading Index:The Coronado expedition, 1540-1542.djvu where the some page numbers of the Contents and all of the Illustrations page numbers are incorrect and have no relation to the actual page number and there is no pattern to the offset.

I am asking what is the company policy on what to display? The printed page number, or the actual page number?— Ineuw talk 13:01, 9 March 2019 (UTC)

I suggest using {{SIC}} in combination with {{DJVU page link 2}} linking it to the correct page, see e. g. link to page 136 here. --Jan Kameníček (talk) 13:54, 9 March 2019 (UTC)
I also suggest using {{SIC}}. The displayed number must be the printed number. —Beleg Tâl (talk) 15:09, 9 March 2019 (UTC)
I would just display the number as printed without marking it. On the whole there is no need for links to page numbers as our links are to chapters or sections of a work. If there is a real need to link to a page within a section, then use deep-linking to the appropriate anchor—either the derived one to the page number from the pagelist or a user-created {{anchor}}. Beeswaxcandle (talk) 18:16, 9 March 2019 (UTC)
Thanks to all for the advice. @Beeswaxcandle: I know that it's not necessary to create links from the contents to the page namespace, and I wasn't going to do it, but the images' djvu numbers are all over the place and without access to the pages they are very difficult to find and verify. — Ineuw talk 18:59, 9 March 2019 (UTC)

images not accompanying text in magazines[edit]

Some magazines may publish an image that does not accompany a story or article, like "The Fair Jacobite" on page 249 of Once a Week vol. VI. What is the Wikisource policy about including these when entering a magazine article-by-article? It does have a caption, at least, or there'd be nothing English-language about it. Levana Taylor (talk) 22:03, 10 March 2019 (UTC)

In the magazine the picture is placed between two articles. So I would put it into a separate subpage between the two subpages with those articles. --Jan Kameníček (talk) 22:59, 10 March 2019 (UTC)
It's part of the magazine. We store English language magazines, including their images, captions or no captions. Jan's probably right; just stick it on its own subpage.--Prosfilaes (talk) 04:44, 11 March 2019 (UTC)
Done. I didn't put the artist's name in the "author" space in the header (thereby treating this picture like other pictures). Levana Taylor (talk) 07:18, 11 March 2019 (UTC)
Because this is a rare occurrence, there isn't a set policy for what to do in this case. Putting it on its own subpage is one option. I personally would probably put it at the end of the section preceding it. It's really up to the discretion of the editors who are proofreading the work, whatever makes the most sense within the context of the work as a whole. If there are likely to be more such instances, you should make a note on the index talk page to inform other editors what the convention is if they run into the same question. —Beleg Tâl (talk) 15:01, 11 March 2019 (UTC)
There aren't going to be any more in the issues of OAW I'm working in, but in the later years of the magazine they frequently had a "pull-out" artwork in the issue, and they weren't the only ones to do this. Levana Taylor (talk) 16:01, 11 March 2019 (UTC)

missing greek[edit]

Hi, I've just finished proofreading Munera pulveris by John Ruskin. Just a heads up to whoever can fix Greek, there's 15 pages with only a few words or short phrases per page of missing greek for it to be fully proofread. And transcluded? Cheers, Zoeannl (talk) 10:01, 10 March 2019 (UTC)

All Greek flagged as missing is added. I leave transclusion to someone else. Beeswaxcandle (talk) 09:01, 11 March 2019 (UTC)
Transclusion is complete. —Beleg Tâl (talk) 12:08, 12 March 2019 (UTC)

Wikidata image problem[edit]

On the author page for Abraham Cooper, who has two images in Wikidata, including the image here isn't working properly. But William Wordsworth, who also has two images, is correct. How was this achieved? I don't see anything on Wordsworth's page selecting an image. Levana Taylor (talk) 20:34, 12 March 2019 (UTC)

Look at Wordsworth's Wikidata item, in the image section. Look at the little arrows by the top left of each picture. You can see that one image is ranked higher than the other, but this is not the case for Cooper. Try setting the rank of one of his pictures higher.
Good point though, is there nothing we can do in Template:Author to fix this? BethNaught (talk) 21:13, 12 March 2019 (UTC)
Yes, it should be controlled at this end ... I would want the "Old" image here on Wikisource because it corresponds to the time of writing of that article, but perhaps someone else using Wikidata for a different purpose would have a reason for wanting the "Young" image as their default. Levana Taylor (talk) 21:31, 12 March 2019 (UTC)

Formatting Help[edit]

Hi, I need help in formatting this page. I do not know how to make border boxes. --Abhinav619 (talk) 06:55, 15 March 2019 (UTC)

@Abhinav619: you can use the template {{border}} for border boxes, and {{rule}} for horizontal lines —Beleg Tâl (talk) 12:43, 15 March 2019 (UTC)

Anthology of Modern Slavonic Literature[edit]

I have uploaded File:Anthology of Modern Slavonic Literature in Prose and Verse by Paul Selver.djvu from archive.org, but only then I noticed that there are several pages missing at the end of the book. Hathi has more copies, but they are not available outside the U. S. I tried downloading them with the Hathi Download Helper, but it failed this time for some reason. May I ask somebody from the U. S. to replace the file? Thanks very much! --Jan Kameníček (talk) 10:38, 16 March 2019 (UTC)

I think it will make no harm when I start proofreading, and if the pages don't match after the files are replaced later, they can be moved. But it would be great if somebody were able to get a better copy. --Jan Kameníček (talk) 19:51, 17 March 2019 (UTC)
Yes check.svg Done but the quality isn't the best. Also there is no ocr but you can use the ocr button for that. I'll see if I can create a better copy when I have the time. Jpez (talk) 05:13, 18 March 2019 (UTC)
@Jpez: Thanks very much! --Jan Kameníček (talk) 09:10, 18 March 2019 (UTC)

This page problematic?[edit]

This page was previously deleted on 16 September 2012 by George Orwell III who unfortunately does not seem to be around atm. Is it good to create and proofread? Cheers, Zoeannl (talk) 09:36, 17 March 2019 (UTC)

Yes, was formerly used with a different scan, you can create it again for this new scan. —Beleg Tâl (talk) 11:28, 17 March 2019 (UTC)
Thanks!Zoeannl (talk) 07:26, 18 March 2019 (UTC)

Use of a Government Seal (Question)[edit]

I have almost completed 2015 Philadelphia train derailment NTSB report, but I have a concern about this page. It uses an official government seal (this one). While it is listed as in the public domain, use of a government seal is decently regulated.

At the moment, I have written [Seal Omitted]. Should I leave it as that or add in the seal? Thank you, –MJLTalk 05:26, 21 March 2019 (UTC)

But the seal is in the public domain copyright-wise, and we won't have any copyright problems using it. There's no reason to not use an image that's already on Commons.--Prosfilaes (talk) 07:43, 21 March 2019 (UTC)
@Prosfilaes: Okay, then; thank you! I'll update the page now. :) –MJLTalk 11:22, 21 March 2019 (UTC)
Further to this: regardless of the copyright issues (which there are none), the fact that the government agency themselves placed the seal on this document means that we are not violating any regulations by reproducing the seal when we reproduce the document. —Beleg Tâl (talk) 12:25, 21 March 2019 (UTC)
Actually, that makes a ton of sense in retrospect. I had wanted to be on the safe side with this, but I am glad my to confirm these concerns were unfounded. –MJLTalk 03:53, 23 March 2019 (UTC)

Header, main window and footer temporary resizing issue[edit]

I reported this bug and wondered if anyone else has this problem. Would other editors check this and please reply here indicating the OS and the browser used? Thanks in advance.— Ineuw talk 03:45, 25 March 2019 (UTC)

It works for me (Firefox and Chrome); do you see the same problem when you are not logged in? —Beleg Tâl (talk) 13:16, 25 March 2019 (UTC)
@Beleg Tâl: an excellent idea. Thank you. It works when logged out.— P.S: Deleted all the cookies and logged in and the problem remains.— Ineuw talk 20:26, 25 March 2019 (UTC)
Issue is resolved. There was a code line in the common.css causing all of the above problems. Thanks again. — Ineuw talk 21:21, 25 March 2019 (UTC)

top caption with FIS?[edit]

On this page {{FIS}} allows me to insert the floor plan the way it should be, except that as far as I can tell it doesn't allow for the caption at the top. Can the top caption be added using FIS, or is there another way to get the floor plan right? Levana Taylor (talk) 03:24, 28 March 2019 (UTC)

I would use {{img float}} instead. It's got an option for top captions. Beeswaxcandle (talk) 07:44, 28 March 2019 (UTC)
Problem with that: the "capalign" parameter of {{img float}} aligns both the top and bottom captions the same, whereas in this case the text above should be centered and the text below should be left or justified. Can some HTML expert suggest a way to get the correct result "by hand" instead? (replicating what img float does, but with separate alignments for top and bottom captions)? Likewise I want to put the bottom caption in smaller font than the top one, which means specifying different line heights. Levana Taylor (talk) 14:18, 28 March 2019 (UTC)

Jesus and Satan meeting[edit]

Some where in Ellen Whites writings, there is a reference when Jesus meet Satan some where in space and Satan wanted to return and Jesus turned and cried, where is that found? —Preceding unsigned comment added by 12.246.210.62 (talk)

Have you looked at Author:Ellen Gould White? --EncycloPetey (talk) 13:38, 28 March 2019 (UTC)

Wuthering Heights[edit]

Can this page be fixed? The OCR hasn't worked? Cheers, Zoeannl (talk) 08:40, 28 March 2019 (UTC)

And this one? Zoeannl (talk) 09:40, 28 March 2019 (UTC)
It seems the text layer is either missing or incomplete. I used the WS OCR button to generate text, but this method has several issues, including (1) text rife with scannos, and (b) curly quotes instead of straight.
It may be worth looking for a better scan of the novel instead of proceeding with this particular file.
Also, we already have the 1st (UK) edition, and the 2nd (UK) edition of 1850 is considered the authoritative one. So, is the 1848 US edition worth having? --EncycloPetey (talk) 13:31, 28 March 2019 (UTC)
It must be your browser, it's working fine with Firefox (Mac) and Safari (Mac only). The only thing not working with me is the header - which says - wuraaaxnc acres-rs. 5 --kathleen wright5 (talk) 14:03, 28 March 2019 (UTC)
Not the browser. I created that text layer using the OCR button (see above). --EncycloPetey (talk) 15:31, 28 March 2019 (UTC)

Any consensus? Should this be abandoned? The scan isn't a good one... Zoeannl (talk) 08:23, 29 March 2019 (UTC)

I would say so. It's a poor scan, with a bad text layer, for an unimportant edition, of a work for which we already have the 1st edition. The 2nd UK edition of 1850 would be valuable, but an early US edition of this novel is more a literary footnote. --EncycloPetey (talk) 14:20, 29 March 2019 (UTC)

The name of the main namespace page does not link to the Table of Contents entry[edit]

Can someone please look at these pages and tell me why a link is not made? The text in the Table of Contents was copied from the main namespace page title.

Main namespace page:

Table of Contents 1st entry:

Ineuw talk 08:15, 30 March 2019 (UTC)

I also ran this search and there are two main pages by the same name Page title search.— Ineuw talk 08:38, 30 March 2019 (UTC)

Minuscule "e" in the word "expedition". --Jan Kameníček (talk) 09:08, 30 March 2019 (UTC)
I copy-pasted the link from the address bar that uses underscores instead of spaces, and it's linking now. I have no idea why it didn't work before though. Jpez (talk) 12:51, 30 March 2019 (UTC)
Set this problem aside in the past few hours, But I think it's best to delete all main namespace pages cascading from the two roots, and then delete the root pages. — Ineuw talk 21:44, 30 March 2019 (UTC)

Too long Contents[edit]

It seems that the Contents on the right side of Index:Anthology of Modern Slavonic Literature in Prose and Verse by Paul Selver.djvu is too long and so the last pages are not transcluded. May I ask for advice? --Jan Kameníček (talk) 13:26, 30 March 2019 (UTC)

The same transclusion problem has appeared at Anthology of Modern Slavonic Literature in Prose and Verse. Besides the last Contents pages the license template has not been transcluded either. --Jan Kameníček (talk) 15:50, 30 March 2019 (UTC)
@Jan.Kamenicek: Five pages of Contents are not too long. First, it helps if the pages appearing in the Contents list exist. There is an error somewhere in the list of contents. If you look at the end of transclusion on the index page, there appears three page numbers outside of the Contents structure. — Ineuw talk 16:43, 30 March 2019 (UTC)
@Ineuw:I looked at it again, but there are only existing and proofread pages transcluded. When I try to remove some of the the pages transcluded in the beginning and look at the preview, the pages in the end are transcluded without any problem. That is why I guess the problem is with the length of the pages (maybe they contain too many complicated templates...).--Jan Kameníček (talk) 16:52, 30 March 2019 (UTC)
@Jan.Kamenicek: Tried to find the problem by pasting all five pages into this sandbox. Please look at it if anything is missing. Unfortunately, I never used this template. Isn't there supposed to be end of list template?— Ineuw talk 17:17, 30 March 2019 (UTC)
@Ineuw:It is interesting that direct pasting resulted in more content being displayed in your sandbox, but still the last rows do not work. The documentation to the template {{Dotted TOC line}} does not say anything about ending the list. Anyway, when the list is shorter, it works well, see, e. g. this experiment, when it is longer, transclusion of the last pages stops working. --Jan Kameníček (talk) 19:15, 30 March 2019 (UTC)
@Jan.Kamenicek: You're definitely running into the post-expand include size limit (~2MB). II'm guessing the main culprit to be {{Dotted TOC line}}. Every single invocation of this template will spit out ~10k characters (and assuming all of them are stored as 8 bits, one byte, that's 10kB), meaning you can have a maximum of 200 of these before hitting the limit provided there are no other templates or content involved. Your pages break down like this (post-expand include size in bytes):
  • 19: 284,451
  • 20: 420,260
  • 21: 480,968
  • 22: 443,746 ← hitting limit here due to other content and templates.
  • 23: 457,835
  • 24: 122,368
My immediate advice would be to drop {{Dotted TOC line}}. I'm all for reproducing works visually as close as possible, but this particular template looks downright pathological: the sheer amount of markup it spits out for each single line is just astounding. For a long(ish) ToC it's never going to work reliably and will have a measurable impact on readers' systems (download time, performance). Case in point, replacing it with {{TOC line}} on Ineuw's sandbox reduces its post-expand include size from 2,097,152 bytes (capped by the limit) to 252,726 bytes. That is, something on the order of 90% of it comes from {{Dotted TOC line}}. --Xover (talk) 20:47, 30 March 2019 (UTC)
I was afraid the problem is something of this kind... It is quite bad if the dots have to be left out. The reason is not only the effort to reproduce the original, but dots really make such long lists much easier to read :-( --Jan Kameníček (talk) 21:36, 30 March 2019 (UTC)
@Xover: A sincere thanks for the explanation. For table of Contents I always use tables. I find it to be very flexible. @Jan.Kamenicek: Sorry for the wrong info.— Ineuw talk 21:40, 30 March 2019 (UTC)
@Xover: I have replaced the template with {{Dotted TOC page listing}} which seems less massive and it helped. Thanks very much for pointing out the problem. @Ineuw: No problem, I do appreciate you tried to help me! --Jan Kameníček (talk) 22:05, 30 March 2019 (UTC)

Should be no links to deleted redirect...[edit]

https://en.wikisource.org/wiki/Special:WhatLinksHere/Traffic_Signs_Manual/Chapter_3

Not understanding why this still has entries as I moved/updated all the pages to use the new edition stucture, Explanation? ShakespeareFan00 (talk) 21:36, 1 April 2019 (UTC)

Subpages keep links to parent pages. Beeswaxcandle (talk) 22:00, 1 April 2019 (UTC)
[edit conflict] It is possible that these are automatic backlinks generated because of the forward slashes. I.e. the software assumes that a page named Traffic Signs Manual/Chapter 3/2008/1 will be a subpage of Traffic Signs Manual/Chapter 3, and automatically create a link. --EncycloPetey (talk) 22:02, 1 April 2019 (UTC)
I also see a number of redlinks in those pages that appear to need correcting, such as links to ".../Chapter 3/Chapter 5" in the text --EncycloPetey (talk) 22:02, 1 April 2019 (UTC)

2 columns[edit]

I'm working on this article and there is a page break where 2 columns begin. It is important that what is in the second column is exactly next to the corresponding part of the first, at Page:The Journal of English and Germanic Philology Volume 18.djvu/510. I don't know how to do this. Radioactive Pixie Dust (talk) 23:03, 14 April 2019 (UTC)

It also looks as though the line returns, at least in the left column, are deliberate. It may be easier to match the columns if you replicate these line returns instead of having the text wrap. --EncycloPetey (talk) 00:59, 15 April 2019 (UTC)

Drop initials are incompatible with other formatting...[edit]

See: - Page:Ruffhead - The Statutes at Large - vol 2.djvu/94. Can someone take a sledgehammer to the relevant templates and MAKE them interact in a SANE manner please, there having been considerable efforts made to make the templates used here not screw up the layout?.

If this isn't fixed I will consider nominating the ENTIRE cl-act-p based family for deletion, on the basis that they just seem to be too incompatible, It is not as if they are widely used. ShakespeareFan00 (talk) 09:43, 16 April 2019 (UTC)

What I don't currently understand is why the same approach on Page:Ruffhead - The Statutes at Large - vol 2.djvu/93 does NOT screw up the layout.ShakespeareFan00 (talk) 09:46, 16 April 2019 (UTC)
These templates rely on floating elements. If you familiarize yourself with float positioning you should be able to figure these out. In this case, {{cl-act-p}} depends on {{margin block}} which by default clears floats to the left. This forces each cl-act-p block to appear below other cl-act-p blocks, or any other floated blocks that precede it. The dropinitial is also floated, and is not cleared, so it will be positioned beside the floated block immediately before it - which is the very last cl-act-p block. You can get around this by putting all the cl-act-p blocks inside a container block. The dropinitial will then be positioned next to the top of the container block (which is now the immediately preceding floated block) instead of next to the top of the very last cl-act-p block. —Beleg Tâl (talk) 13:01, 16 April 2019 (UTC)
Right so dropintial is (currently) incompatible with cl-act-p, Perhaps at some indeterminate future date it will be possible for Wikisource to have templates that do not have obscure interactions issues, until then it seems an overly complicated and otherwise uncessary workaround is needed. What a shame :( ShakespeareFan00 (talk) 16:36, 16 April 2019 (UTC)
Perhaps YOU are able to provide a "compatible" drop-initial template that doesn't rely on a contributor knowing precise CSS details and the minutiae of obscure Mediawiki/HTML/CSS interactions? Thanks. ShakespeareFan00 (talk) 17:03, 16 April 2019 (UTC)
lol nope. Templates are just shortcuts for CSS. If you want to format a text with complicated floating blocks of text, it's up to you to understand how complicated floating blocks of text works. Dropinitial needs no further changes to work the vast majority of the time; if you want a version of dropinitial that accounts for the behaviour of whatever cl-act-thingy is, then that's on you. —Beleg Tâl (talk) 17:26, 16 April 2019 (UTC)
Whilst that may be so, there wasn't anything in the documentation for {{di}} or {{intial}} that mentions this issue in any detail. Once again I am supposed to KNOW apparently by intution or telepathy, various miniutiiae of CSS/HTML/Mediawiki markup interactions. This is NOT conducive to positive long term contributions. ShakespeareFan00 (talk) 18:18, 16 April 2019 (UTC)
The documentation for {{di}} explicitly says "This template simply generates a left-floated span (w/style display: block;) containing content with the proper CSS styles applied to it." Floated elements are well documented on MDN, W3Schools, and many many other websites. No intuition or telepathy required. —Beleg Tâl (talk) 20:57, 16 April 2019 (UTC)
The incompatibility of {{di}} with other "floating" templates is NOT howver documented. It seems I'm wasting my time trying to get anywhere with this issue (sigh).ShakespeareFan00 (talk) 21:12, 16 April 2019 (UTC)
See also Page:Test_page#Testing_/s_/e_version_(5d)_with_inline_at_start,_layout_specified_and_a_drop_initial_(I_said_let's_have_some_insanse_test_case!) , The 2 sidenotes/titles should be level with the dropinitial, but that seems to currently be outside the limitations of Mediawiki/CSS/HTML to handle in a SANE and CONSISTENT manner. As I said perhaps SOMONE ELSE can come up with an approach that means that the SAME concerns and arguments do not occur again and again EVERY SIX MONTHS until someone finally gets around to ACTUALLY providing the functionality needed, instead of stalling by saying it's down to me. Either work out a fix the templates or put it in the documentation, that DI and other templates can't be used alongside other 'floated' elements. ShakespeareFan00 (talk) 21:25, 16 April 2019 (UTC)
From some further analysis it seems that what I am trying to do in terms of interactions is NOT currently feasible, due to CSS/HTML limitations. Hopefully when the CSS Text spec, properly supports true drop initials (and browsers do as well) this can be revisted. In the meantime the work around seems to be use a right-hand position for the sidetitles universally. ShakespeareFan00 (talk) 09:39, 17 April 2019 (UTC)

OK, anyone here good with LUA code?[edit]

Page:Ruffhead_-_The_Statutes_at_Large_-_vol_6.djvu/775, a template used on this page was recently updated. I can't figure out WHY the change should have caused something that worked previously to suddenly start generating BAD markup. Can someone else here please provide an explanation, and a repair, so that the templates behave in the SANE and DOCUMENTED way they are supposed to. Thanks. ShakespeareFan00 (talk) 10:49, 16 April 2019 (UTC)

I don't see anything wrong with the linked page. What are you talking about? Which template? What update? Where is the bad markup? —Beleg Tâl (talk) 13:06, 16 April 2019 (UTC)
https://en.wikisource.org/w/index.php?title=Page:Ruffhead_-_The_Statutes_at_Large_-_vol_6.djvu/775&oldid=9201797 and Template:cl-act-p/1, I put in a TEMPORARY fix by explicitly naming the text param. The template should be able to cope with the text being the unamed first parameter.(i.e an implied 1=}} which in the revision shown didn't work as expected. ShakespeareFan00 (talk) 16:17, 16 April 2019 (UTC)

See also Template:Cl-act-p/testcases ShakespeareFan00 (talk) 16:54, 16 April 2019 (UTC)

Which has been solved for the time being by reverting the changes made recently. ShakespeareFan00 (talk) 21:18, 16 April 2019 (UTC)

Tom Swift[edit]

I want to download the whole book Tom Swift and His Motor Cycle as pdf . What do I do? —Preceding unsigned comment added by 223.191.34.87 (talk)

It's my understanding that our PDF export function is still broken. If you need it in PDF format, your best bet may be to download the original book scan from https://ia902705.us.archive.org/20/items/tomswiftandhism00garigoog/tomswiftandhism00garigoog.pdfBeleg Tâl (talk) 12:42, 18 April 2019 (UTC)

Page-spanning table[edit]

Page 8 and Page 9 of The Lucknow Album are currently proofread as two separate tables, which is causing misalignment on transclusion. I have tried formatting as page-spanning table, but for some reason it is not working on transclusion. Can someone make a fresh attempt please? Hrishikes (talk) 08:06, 20 April 2019 (UTC)

Yes check.svg Done , looks like it was because page 8 and page 9 were transcluded separately with two separate <pages /> calls. —Beleg Tâl (talk) 11:38, 20 April 2019 (UTC)
Many thanks. I had overlooked that aspect. Hrishikes (talk) 16:19, 20 April 2019 (UTC)

Book from Google books[edit]

Can somebody from the U.S. check, whether the following book is available in the United States, please? [7]

Thanks very much. --Jan Kameníček (talk) 15:59, 22 April 2019 (UTC)

@Jan.Kamenicek: -- Is the book same as this: https://catalog.hathitrust.org/Record/007853674 ? I can download this one. Hrishikes (talk) 17:00, 22 April 2019 (UTC)
@Hrishikes: That is exactly what I hoped to find out: whether the two books are identical or not :-)
However, I would be really glad if you downloaded at least the one from the Hathi Thrust. Thank you! --Jan Kameníček (talk) 18:12, 22 April 2019 (UTC)
Index:President of the Czecho-Slovak Republic, Thomas G. Masaryk.pdf -- Hrishikes (talk) 01:19, 23 April 2019 (UTC)
Thanks very much! --Jan Kameníček (talk) 07:46, 23 April 2019 (UTC)

Help with braces in a table[edit]

I marked this page "validated," but in retrospect my approach is pretty kludgey. Could somebody with a better understanding of how to handle curly braces in tables offer an alternative?

Page:Alerielorvoyaget00lach.djvu/10

(Note, this is the final page needing validation in this work.) -Pete (talk) 18:46, 23 April 2019 (UTC)

Alignment affecting line spacing[edit]

I uploaded File:Sassoon, Siegfried - Counter-Attack and Other Poems (1918).djvu from the Internet Archive, and have taken a crack at correcting the OCR'd text and formatting it, but I'm having some issues with text alignment. Spefically, when I use {{centre|lorem ipsum}} or {{right|lorem ipsum}}, it seems to add spacing between the lines, as though they were new paragraphs. For example, on this page: Page:Sassoon,_Siegfried_-_Counter-Attack_and_Other_Poems_(1918).djvu/35, the following lines:

"The war'll be over soon."

"What 'opes ?"

"No bloody fear!"

have more spacing between them than ordinary lines do, despite there being no extra line spacing or paragraph breaks applied in the source.

Also, I'm not quite sure how to achieve the indenting style from the original text, as you can see on the same page, when a line runs over, it's a hanging indent, but the second line is right-aligned, but then slightly indented from the right margin. -- I, Podius (talk) 18:11, 25 April 2019 (UTC)

@I, Podius: {{center}}, {{left}}, and {{right}} all wrap their argument in a HTML <div></div>, which is a block element like <p></p>, and so will always have the same vertical whitespace properties. Your best bet is probably to leave the text as such left-aligned but use {{gap}} to indent the relevant lines a suitable amount. I wouldn't worry about that final word on the last line. It doesn't appear to be deliberately wrapped for artistic reasons: it's just wrapped due to the space constraints of physical books. The weird alignment is just to mark such a wrapping point. Just unwrap these lines and you won't need to worry about trying to reproduce it. --Xover (talk) 18:36, 25 April 2019 (UTC)
@Xover: Ah, I see! What annoying behaviour. That's good to know. I wasn't sure how closely I should try to match the original formatting, so that's helpful; I'll just add a standard hanging indent for when the text wraps, in that case. Thank you! I, Podius (talk) 03:29, 26 April 2019 (UTC)
See also Wikisource:Scriptorium#blocks of text w/o blank lines between paragraphs. I have tried the method there, of removing automatic paragraph margins by surrounding every paragraph with {{p|m0}}</p>, and it works fine. Two clarifications: 1. {{p|m0}}</p> should be placed inside all <div> templates such as {{right}} 2. You can specify spacing before and after a block of no-paragraph-break text by using {{dhr}} Levana Taylor (talk) 19:48, 25 April 2019 (UTC)
@Levana Taylor: Very helpful, thank you! It took me a while to figure out how to get it working because I didn't realise I needed to add {{p|m0}}</p> to the preceding and following paragraphs, as well. But now it all looks right. Cheers! I, Podius (talk) 03:29, 26 April 2019 (UTC)

Translator[edit]

I found the English translation from the 2 vol. books Travels in Brazil, in the years 1817-1820 by Carl Friedrich Philipp von Martius and Johann Baptist von Spix and I'm having a problem: I know that, by the date (1824) is Public Domain worldwide, but I'd like to credit the translator (that only goes by the name "H. E. Lloyd") and I cound't find anything about him. Someone here can help? Thanks, Erick Soares3 (talk) 16:17, 26 April 2019 (UTC)

@Erick Soares3: It's Hannibal Evans Lloyd (1771–1847). --Xover (talk) 16:49, 26 April 2019 (UTC)
@Xover: Thanks! Ĩ will soon upload the books! Erick Soares3 (talk) 17:11, 26 April 2019 (UTC)

R.U.R. (Rossum's Universal Robots)[edit]

I would like to proofread the play R.U.R. (Rossum's Universal Robots) by Karel Čapek (the one which introduced the word "robot" for the first time). Unfortunately, the copy at Hathitrust is not very good, e. g. instead of the four sketches of the stage at the end of the book there are only two repeated twice, and some inscriptions in the sketches are illegible. I have found a much better copy at the archive.org, but it seems it can be only borrowed for some reason, although it should have been out of copyright already. Is there any way how to get the book from the archive.org? --Jan Kameníček (talk) 18:40, 28 April 2019 (UTC)

I've got a scan I made many years ago on my hard drive; I'll see if I can get it up to Archive.org tonight.--Prosfilaes (talk) 03:08, 29 April 2019 (UTC)
That would be absolutely perfect! Thanks a lot! --Jan Kameníček (talk) 07:52, 29 April 2019 (UTC)
That was one of my first scans, and the worse for it. It is available on archive.org, but it's not really usable directly. However, Google Books had a better copy of the same edition I scanned, so I uploaded it to File:R U R Rossum s Universal Robots.pdf. It does not have the sketches of the stage, instead having photos of the action, and I'm not sure it's the exact same play text, but there it is.
BTW, we should probably move the Paul Selver books from Commons, since he died in 1970, leaving his translations under copyright in his home nation.--Prosfilaes (talk) 09:14, 29 April 2019 (UTC)
All these linked publications are published in the USA; does that not make USA the source country for this work? —Beleg Tâl (talk) 11:19, 29 April 2019 (UTC)
True, though it was first performed in the UK. The other Paul Selver works in Commons:Category:Paul Selver were all published in the UK, though.--Prosfilaes (talk) 01:00, 30 April 2019 (UTC)
Thanks very much! I will start working on it soon :-)
As for the Commons, their rules seem too complicated to me, so I am really not sure whether the movement is necessary or not. However, the R.U.R. was published directly in the U. S., so I guess it could have been uploaded to Commons. However, I do not care very much if it is uploaded here or there. --Jan Kameníček (talk) 11:43, 29 April 2019 (UTC)
Now I looked at it in more detail and found out that the editions are not the same, comparing e. g. the descriptions of scenes, which are much longer and more detailed in the version published by Samuel French than the description in the uploaded version published by Doubleday (besides the missing sketches). So it would be great if it were possible to get the Samuel French version somewhere too, I would be happy to proofread both of them. --Jan Kameníček (talk) 12:06, 29 April 2019 (UTC)
PS I've converted it to djvu so you can proofread from File:R U R Rossum s Universal Robots.djvuBeleg Tâl (talk) 00:45, 30 April 2019 (UTC)
Thanks, although it seems that the djvu file has lost the OCR layer. Besides that I have to confess I prefer pdf files as they can be also easily viewed outside the proofreading extension directly in a web browser, while djvu files require to download some additional software (I have it but other people who may also want to see the file usually don't). But I thank you for trying to help! --Jan Kameníček (talk) 07:53, 30 April 2019 (UTC)
DJVU works better with the proofreading extension though, so it's good to have both! —Beleg Tâl (talk) 12:26, 30 April 2019 (UTC)

Duplicate pages deleted, but still showing on Index:CAB 129 post war memoranda 73-38.pdf[edit]

I've deleted the duplicate pages from the above, but are still showing. I also deleted them from the Index namespace. What have I done wrong? --kathleen wright5 (talk) 02:01, 6 May 2019 (UTC)

@Kathleen.wright5: The underlying PDF at Commons contains 6 pages, which is what ProofreadPage will show in the Index: for it. You may wish to consider whether duplicated pages are a significant (i.e. worth preserving) feature of the original edition, or whether it is incidental or an error introduced during digitisation. In any case, you can just mark them as not needing proofreading in the pagelist if that is indeed the case. --Xover (talk) 06:19, 6 May 2019 (UTC)
@Kathleen.wright5: Another way to handle it is to blank out the text and mark page as "Without text". Pages with this status will not transclude. — Ineuw talk 06:47, 6 May 2019 (UTC)

Formatting: brace[edit]

After spending two days wrestling with the formatting of an article on cryptography, I have got it all solved, except for one point. On this page, in the paragraph below the cryptic message, one line has a brace under it, and I could not find a way to insert that. Luckily, though, it might not be necessary to include this brace at all, because it isn't part of the text proper, but rather a proof notation indicating "Obviously some error here - query what is intended" which didn't get corrected before the final printing. (This isn't the only muddled sentence in the article either; a pity there wasn't another round of proofreading before press-time.) Thoughts? Levana Taylor (talk) 22:53, 8 May 2019 (UTC)

@Levana Taylor: Absent other examples it is hard to generalise, but in this instance it appears the brace might be marking the repeated "b" (which seems an obvious error, indeed) specifically. If that is the case you might use {{SIC}} to mark that letter. If other instances truly mark a line or sentence fragment of indeterminate length I'm not sure there is any sensible way to replicate those particular markings. If the latter situation obtains it may be best to simply not try to reproduce these at all. --Xover (talk) 04:22, 9 May 2019 (UTC)
@Levana Taylor: I would suggest that we should reproduce the marking; we have a policy of reproducing typos. You can probably replicate it by experimenting with {{dual line}} and {{brace2}}. —Beleg Tâl (talk) 18:16, 9 May 2019 (UTC)
Aha, that {{dual line}} is what was needed. Levana Taylor (talk) 20:12, 9 May 2019 (UTC)

Notes in The Natural History of Selbourne[edit]

Could I have some ideas for dealing with these Notes. For example: this page. Some Letters have multiple Notes referenced, from different pages. Cheers Zoeannl (talk) 06:57, 12 May 2019 (UTC)

The answer partly depends on how the transclusion will happen. Is each letter going to be transcluded separately? Or is it going to be a single section with all the letters together? Beeswaxcandle (talk) 07:14, 12 May 2019 (UTC)
I don't know. There are no descriptive titles, just Letter # so I don't know if there is any advantage to transcluding separately? Hence, looking for ideas... Cheers, Zoeannl (talk) 21:43, 12 May 2019 (UTC)

Multiple columns across pages[edit]

I have a current project which includes a list of names several pages long. Each page is laid out in two columns and the entries are in alphabetical order (of surname) so for example one one page column 1 goes from John Freneau to John Hammel and column 2 continues from John Hibon to James Le Mome and the next page from Isaac Le Doux to Gentien Maret and Paul Maigne to John Picquet.

I started adding these using tables but then it occurred to me that once the pages are linked into a view of the full chapter the entries will be out of sequence as John Hammel from Page 1 col 1 will be followed directly by Isaac le Doux from page 2 col 1.

It looks as though the {{Div col}} template would solve the ordering problem when the pages are combined but the formatting options seem limited. The entries are quite widely spaced, are justified rather than right aligned, there is a large default line space, and the original uses a dividing rule between the columns.

I have been able to use an HTML <div style='column-count:2; column-rule: 1px solid black;'> to give me the rule but so far have not found a way to tighten up the text layout within the columns.

See the 'table' formatting here and the '{{Div col}}' version here

Any suggestions appreciated GreyHead (talk) 13:26, 15 May 2019 (UTC)

Another problem I see is that some entries of the list which should be at the bottom of the left column are at the top of the right column.
I think the solution is in {{multicol}} and {{hin}}, see, e. g. Page:The Spirit of Russia by T G Masaryk, volume 1.pdf/499. --Jan Kameníček (talk) 14:27, 15 May 2019 (UTC)
The standard solution here is to not use columns at all—or rather do it all in a single column. We are aiming to make the text available, not reproduce what the publisher had to do to keep the number of pages down. Beeswaxcandle (talk) 08:08, 16 May 2019 (UTC)
Thank you both. I have opted for the single column solution and have also used the <poem> tags from the pages that Jan linked to so tighten up the formatting. The only niggle there is that it seems they can't be used in the page headers/footers. The section (currently unfinished) is here. GreyHead (talk) 12:41, 16 May 2019 (UTC)
@Beeswaxcandle:: As you can see in the linked page above, the multicol template is used only in the noinclude sections, so the text is divided into the columns only in the page namespace, while there is just a single column in the main namespace.
@GreyHead: Yes, the <poem> tag cannot be put into the header or footer and has to be repeated in the beginning and end of every page. Another option (though not very comfortable one for long lists) is to use <br /> at the end of each line. Do you need any help with the unfinished part? --Jan Kameníček (talk) 13:46, 16 May 2019 (UTC)
@Jan.Kamenicek: Thanks for the offer, I'm fine thank you, it's a lot faster now using the <poem> tags and, all being well, I will finish this section over the weekend. GreyHead (talk) 13:20, 17 May 2019 (UTC)

page numbers in main namespace[edit]

Can anyone please help/explain what is happening here. For instance With axe and rope in the New Zealand Alps/Chapter VIII. The pages up to 86 are given to the left (in different layouts), but after the first image there are no longer page numbers visible. This is also the case in other chapters. What do we do wrong? Help appreciated, --Dick Bos (talk) 11:04, 17 May 2019 (UTC)

Fixed. There were two problems, see [8] and [9]. --Jan Kameníček (talk) 11:35, 17 May 2019 (UTC)
@Jan.Kamenicek: - Thanks a lot! --Dick Bos (talk) 12:12, 17 May 2019 (UTC)
@Dick Bos: You are welcome. The problem partially continues at some other subpages, e. g. at With axe and rope in the New Zealand Alps/Chapter VII, where the page no. 67 is not numbered correctly. It is due to an empty page included among the transcluded pages. The solution is to exclude the empty page, similarly as I have done at [10] . --Jan Kameníček (talk) 15:07, 17 May 2019 (UTC)

Is this the place for a translation?[edit]

I'm looking to develop a new way of publishing translations of historical music theory sources. Could Wikipedia do this? Would another platform be better?

(1) The entire translation should be freely accessible and easily searchable online. (2) All users can comment on specific passages, identify typos, and suggest changes, and this revision history is archivable and viewable (3) A very high volume of foreign language and English text can be viewed in parallel format, with links to images of the original source (or just searchable images of original file on one side) (4) Notation examples and audio files are integrated within the parallel text. (5) Two systems of footnotes (original and editorial) are possible. (6) Integrated bibliographical citations are possible.

Wikipedia would not publish translations, but Wikisource can under certain circumstances. See Wikisource:Translations, specifically the section on "Wikisource original translations". There would need to be a scan-backed copy of the original text at the appropriate language Wikisource (e.g. the Italian Wikisource for a text written originally in Italian.) Then, a translation can be created here based on that original.
Parallel texts are generated dynamically, rather than hosted as a single work. To create a text that is simultaneously in two different languages, you would need to work at the multilingual Wikisource instead. --EncycloPetey (talk) 16:37, 18 May 2019 (UTC)
Wikiversity would publish an original translation or even an original book, Derekremes. If it meets Wikisource's guideline, tho, it's probably better here; Wikiversity is for more general teaching and research resources. HLHJ (talk) 01:56, 20 May 2019 (UTC)

Božena Němcová: The Grandmother[edit]

I would like to proofread Index:The grandmother; a story of country life in Bohemia.pdf, but unfortunately two pages (68 and 69) are missing in this Hathitrust copy. I found the book also at https://books.google.cz/books?id=DA40AQAAMAAJ , but for some reason it is not available from my place, although the copyright should have expired a really long time ago. Can somebody please check its availability from the U. S. (and whether there are the two pages), please? Thanks very much. --Jan Kameníček (talk) 08:41, 26 May 2019 (UTC)

@Jan.Kamenicek: The copy from NWU hosted on HathiTrust is a Google scan, which means Google Books will probably be missing the same pages (it's the same scan). However, HathiTrust also has a ditto scan from a copy at UC which is not missing these pages. As best I can tell, both copies are the same edition. --Xover (talk) 09:15, 26 May 2019 (UTC)
@Xover: Good point! I did not notice it because Hathitrust usually links from an edition's catalogue record to all copies they have, but this time they have separate catalogue records for each copy for some reason. Anyway, I have uploaded the other version now. Thank you very much! --Jan Kameníček (talk) 10:04, 26 May 2019 (UTC)
They rely on the bibliographic records provided by the original institution, and those are in general pretty poor. Almost every time I visit Hathi I find some kind of quirk like that. Thus I wouldn't recommend trusting automatic links through author etc. fields blindly. Always look for title matches or your own search on the author name. --Xover (talk) 10:13, 26 May 2019 (UTC)

About create pages[edit]

Hello! Respected team, i m okay bhargav, i have some questions that which platform we make my wiki info..page past time auto delet my pages and after i don't try agqin so, what can i make page on wiki platforms and if yes , please give me a permission for make my own pages and help me for create pages please and if your answer not, so what is reason for that, also you cqn check my name find on google this name (okay Bhargav) so, i want to page for my information so, please help me. Thank you unsigned comment by Ok bhargav (talk) .

@Ok bhargav: On this website (Wikisource) you can add published, freely licensed, English-language written works. You cannot create a page for self-promotion. I have put some information on your talk page, which should answer your questions. I will try to answer any other questions you might have. —Beleg Tâl (talk) 18:29, 28 May 2019 (UTC)

Need for an Administrator[edit]

Hello - this is a new editor here. Can an administrator help me with my user-page? Multiple times I have tried to create it, but it keeps blocking my action, because the filter thinks that I am a spam-bot. I don't know where else to find help! Thanks in advance! Orlando the Cat (talk) 04:26, 30 May 2019 (UTC)

I've created it; that might let you edit it easier. If not, it would help if you could be very explicit about what error messages you're getting.--Prosfilaes (talk) 05:15, 30 May 2019 (UTC)

How to activate the OCR bot?[edit]

Every once in a while, when attempting to use OCR gadget, I get the following message: ws_ocr_daemon robot is not running..

  • Is this a daily maintenance routine at a particular time of the day?
  • If not, is it possible for me to activate it? and how? — Ineuw (talk) 22:51, 29 May 2019 (UTC)
I also come accross this quite often (for example just now) and it is very unpleasant as it slows down my contributions. Is there anything that could be done to improve the OCR bot's performance? --Jan Kameníček (talk) 07:35, 30 May 2019 (UTC)
Almost 4 hours later, still not running... :-( --Jan Kameníček (talk) 11:18, 30 May 2019 (UTC)
Per Wikisource:Administrators' noticeboard#Requesting the activation of the OCR daemon, the OCR bot does this when it is too busy running other OCR tasks to be able to do yours also. I'd suggest enabling the Google OCR gadget and using that instead when the regular OCR bot is unavailable. —Beleg Tâl (talk) 12:34, 30 May 2019 (UTC)
Ah, thank you, I did not know about the Google gadget. --Jan Kameníček (talk) 14:12, 30 May 2019 (UTC)
@Beleg Tâl: I thank you too.Ineuw (talk) 22:19, 30 May 2019 (UTC)
Just a comment by Phe copied from the phabricator: "...the service was down and not running, those downtime are not related to 'too much request' but there was probably something broken in the past few days in the cluster or one of the numerous downtime for a planned maintenance..." [11]. --Jan Kameníček (talk) 23:02, 30 May 2019 (UTC)
Thanks to Jan Kameníček for the link, and to Peteforsyth for reporting it. Ineuw (talk) 02:45, 31 May 2019 (UTC)
Google's OCR scan is not nearly as good as Phe's. Phe's OCR interprets emdashes {{}} correctly, recreates paragraph breaks and replaces all accented characters with and "é-acute". This last feature is a mixed blessing, even if it's incorrect 50% of the time. At least it identifies where lower case accented characters are missing. Ineuw (talk) 16:11, 1 June 2019 (UTC)
Unfortunately, it is not running again, and this frequent inaccesibility makes it much less useful. Therefore I am trying to get used to the Google gadget, whose main advantage is that it works --Jan Kameníček (talk) 17:11, 1 June 2019 (UTC)

Index:The Naturalisation of the Supernatural.pdf[edit]

Can someone decide on ONE date format on the quoted letters and document that style choice , so I can be consistent in applying it? Thanks.ShakespeareFan00 (talk) 18:35, 6 June 2019 (UTC)

Would you mind providing links to these quoted letters that you want advice regarding? I don't see any indication on the Index page of what you are referring to. —Beleg Tâl (talk) 18:44, 6 June 2019 (UTC)
Also, if you are proofreading this text, why don't you decide on one yourself? Are the dates really weird or something? —Beleg Tâl (talk) 19:23, 6 June 2019 (UTC)
Page:The_Naturalisation_of_the_Supernatural.pdf/156 vs [[12]] , Some are using an additional smaller tag, that looks odd. ShakespeareFan00 (talk) 20:51, 6 June 2019 (UTC)
I also failed to find anything problematic. One of the pages contains the date "July 30th, 1893." and the other March 7th, 1905. Can you please be more specific what sort of special tag you see there and where? --Jan Kameníček (talk) 21:08, 6 June 2019 (UTC)
I guess the date does look even smaller than the smaller quoted text on that particular page. Is it like that in every instance? (If not, there is no need to standardize.) If you nest smaller tags, the date will be really tiny; I'd recommend to use {{fine}} (or similar) instead so that it remains legible. However, the difference in font size is so subtle that I do not think it is necessary to reproduce it, so you can pick whichever convention you prefer, and post your decision at Index talk:The Naturalisation of the Supernatural.pdfBeleg Tâl (talk) 21:13, 6 June 2019 (UTC)
Ah, so if it is the size of font which is being discussed, I suggest using the {{fine}} template. --Jan Kameníček (talk) 22:16, 6 June 2019 (UTC)

Notes at the bottom of articles[edit]

Regarding Wikisource:WikiProject 1911 Encyclopædia Britannica

Are the comments and notes at the bottom of any given article modern? Or were they from the original article? It would seem they are modern. unsigned comment by 144.230.82.246 (talk) .

@144.230.82.246: They should be from the original. —Nizolan (talk) 18:48, 17 June 2019 (UTC)
It would help answer your question if you could be a little more specific -- can you link to a specific page, or quote some of the text you're referring to? If the "note" is a statement about its copyright/public domain status, that is probably modern, and intentionally so. -Pete (talk) 19:20, 17 June 2019 (UTC)

Library_of_Congress_Classification/Class_P,_subclass_PN_--_General_Literature[edit]

Short question is why LintErrors can't be more specfic? I've spent an entire evening trying to find one.

Either tell me precisely where the error is, or Fix LintErrors so it doesn't cause me to waste my time hunting "phantom" errors. ShakespeareFan00 (talk) 22:22, 18 June 2019 (UTC)

Academic journal articles[edit]

Is there any standard way to format the metadata for academic articles? I'm thinking something like Wikiversity:Template:Article info. If not, would it be OK to just copy over that template? HLHJ (talk) 01:52, 20 May 2019 (UTC)

Normally we would just put that info in Wikidata, and link to it from there. —Beleg Tâl (talk) 16:01, 22 May 2019 (UTC)
Thank you, Beleg Tâl. I'm trying to figure out the best method for adding entire copyleft fulltext academic articles to Wikisource. I have an application for this, discussed on the Wikiproject Medicine group (the group is currently supplying Internet-in-a-box wiki subsets to off-the-net medical facilities). Is there a good way to link such a fulltext to the Wikidata metadata? Presumably you'd want to display that metadata here somehow, but hotlinking might be better. Is there an extant example I could look at to figure out how to do this? HLHJ (talk) 22:20, 1 June 2019 (UTC)
Texts on Wikisource are linked to items on Wikidata using the interwiki links functionality on Wikidata. See for example d:Q15625490 which is linked to Biodiversity Assessment of the Fishes of Saba Bank Atoll, Netherlands Antilles. —Beleg Tâl (talk) 20:31, 5 June 2019 (UTC)
Thank you very much, Beleg Tâl, that's just what I wanted. I have looked through it and am looking at the tools credited in its edit history. I also uploaded another rather random non-medical article, but now I look at it more closely, I'm not sure the source (a journal which seems to be a research group's own publication) is reliable... I'll come back to this. HLHJ (talk) 04:10, 21 June 2019 (UTC)

Fixing problematic code (alignment in captions)[edit]

I've been informed that a number of my edits have introduced an HTML problem of some kind. (I'm no HTML expert, so I don't fully understand what it's about.) I'll put an example below. Can anybody suggest a better way to code such captions? I'd like to continue to use {{FI}} template if possible.

Letters from an Oregon Ranch p. 8.png

Copyright, Kiser Bros., Portland, Ore.

MOUNT JEFFERSON, FROM HOOVER'S BUTTE
"We can plainly see Mount Jefferson" (page 46)

This applies to most of the images in Letters From an Oregon Ranch and a number of other works as well. Of course, it would also be good to reduce the amount of space between the image and the caption...maybe a solution could address that as well? -Pete (talk) 19:26, 18 June 2019 (UTC)

@Peteforsyth: Some comments if I may? The caption parameter of {{FI}} always tries to enclose its content in an HTML paragraph (<p>) tag which regretably is somewhat at odds with use of {{right}} as that template in turn uses a division (<div>) tag to do its magic. This is one of the relatively few verboten HTML constructs which may be the origin of the original complaint…and also indirectly explains the gap betwixt image and caption you mentioned! (Oh and {{c}} adds yet another <div>… but by now the damage has already been done and cue parable spilt milk &c.)

May I humbly propose something like:

{{FI
|file=Letters from an Oregon Ranch p. 8.png
|width=90%
|cstyle=max-width:500px
|talign=right
|tstyle=margin:0
|caption={{sm|Copyright, Kiser Bros., Portland, Ore.}}</p>
{{p|ac|m0}}MOUNT JEFFERSON, FROM HOOVER'S BUTTE<br />
"We can plainly see Mount Jefferson" (page 46)}}
which displays as:

Letters from an Oregon Ranch p. 8.png

Copyright, Kiser Bros., Portland, Ore.

MOUNT JEFFERSON, FROM HOOVER'S BUTTE
"We can plainly see Mount Jefferson" (page 46)

Now for a little explanation (as I have cheated a little bit!) talign=right is used solely to align the "Copyright" line and its effect ends at the </p> fragment. tstyle=margin:0 is used to eliminate padding around and within the caption (everybody forgets that paragraphs always add typically around 7px margin-top and margin-bottom!) Finally {{p|ac|m0}} adds a new paragraph with center aligning and margins (re)suppressed to hold the main part of the caption; i.e. "MOUNT JEFFERSON &c.
Hope this is useful? 114.78.66.82 08:56, 19 June 2019 (UTC)
Many thanks, this helps me understand the problem and I think it's a good solution. In an ideal world, I tink there would be a little more space between the (c) notice and the actual caption (and/or a little less space between the caption's two lines). Maybe if I study the template you introduced I can find a way to accomplish this; but I wouldn't say it's mission-critical. Much appreciated! -Pete (talk) 19:12, 19 June 2019 (UTC)
Also, just out of curiosity -- won't this "cheat" introduce an extraneous closing paragraph tag? I assume that's simply ignored, and therefore not a problem -- but curious if I'm interpreting the code correctly. -Pete (talk) 19:13, 19 June 2019 (UTC)
Yes it does create another issues with mismatched tags, the REAL solution would be to fix {{img float}} so it can handle the block level elements correctly, but given past experience I don't see that happening certain contributors are aggressively dissuaded from "too clever by half" solution , as opposed to actual repairs to the underlying templates. ShakespeareFan00 (talk) 19:24, 19 June 2019 (UTC)
@Peteforsyth: Regarding the line spacing in the caption issue; is this more to your liking?
{{FI
|file=Letters from an Oregon Ranch p. 8.png
|width=90%
|cstyle=max-width:500px
|talign=right
|tstyle=margin:0
|caption={{sm|Copyright, Kiser Bros., Portland, Ore.}}</p>
{{p|class=imgCaption|ac}}MOUNT JEFFERSON, FROM HOOVER'S BUTTE<br />
"We can plainly see Mount Jefferson" (page 46)}}
which displays as:

Letters from an Oregon Ranch p. 8.png

Copyright, Kiser Bros., Portland, Ore.

MOUNT JEFFERSON, FROM HOOVER'S BUTTE
"We can plainly see Mount Jefferson" (page 46)

I dropped the m0 as I misunderstood your requirement—which reintroduces that 7px inter-paragraph margin I referred to before. As for the concern about extraneous closing paragraph tags the balance between opening and closing tags is maintained thus:
  • <p> is generated internally by {{FI}} just after image and in front of caption—furthermore this is the paragraph which conveys the talign and tstyle information into HTML, and is closed by…
  • </p> this explicitly coded tag ends the Copyright line fragment and also ends right-alignment…
  • A second <p> is generated by {{p}} (Also a side note here: I added class=imgCaption as I missed the (slight) issue of {{FI}} marking the caption block with this particular class name and thought I might as well make the two paragraphs as similar as possible in this respect.)
  • </p> is generated internally by {{FI}} to close off the caption block. This is the cheat in that {{FI}} "thinks" it is encapsulating a single parargraph's text and in fact here it has been handed two. This is not an issue because {{FI}} furthermore encloses the whole image+caption entity within a <div> block and thus the whole mess hangs together!
@ShakespeareFan00: I hope the above exposition allays your concerns. {{FI}} is a surprisingly flexible and robust template and if anything ought to act as a model for modifications to other templates such as {{img float}}… However the two templates do not satisfy the same purposes at all and are not generically interchangeable. {{FI}} is superior for situations where a (possibly variable size) image+caption stands alone either within a page or floats off to one side. {{img float}} lends itself better to text winding around a captioned image of fixed dimensions. Not at all the same animals!
Thank you for prompting this little stroll down memory lane… 114.78.66.82 22:51, 19 June 2019 (UTC)
Thanks very much, this is all very helpful -- both to the immediate task at hand, and also giving me a nice lesson in the underlying issues. I'll start implementing this shortly! -Pete (talk) 07:25, 21 June 2019 (UTC)

{{Ditto}} and {{hi}} incompatibility...[edit]

Page:The Prince (translated by William K. Marriott).djvu/303

Using {{hi/s}} {{hi/e}} causes {{ditto}} to fail. Please fix the templates, or provide a STABLE way of doing this. ShakespeareFan00 (talk) 08:52, 21 June 2019 (UTC)

{{hi/s}}<span style="display:inline-block; text-indent: 0;">{{ditto|Here is a STABLE way of doing this.}}</span>{{hi/e}} Beleg Tâl (talk) 03:53, 22 June 2019 (UTC)
That is implemented as : https://en.wikisource.org/w/index.php?title=Page:The_Prince_(translated_by_William_K._Marriott).djvu/303&oldid=9381065 , I've also tried it with a table. https://en.wikisource.org/w/index.php?title=Page:The_Prince_(translated_by_William_K._Marriott).djvu/303&oldid=9381236

I'd like a second opinion on which approach would be better to use before formatting all the Notes pages. ShakespeareFan00 (talk) 08:29, 22 June 2019 (UTC)

Changing the title of a page[edit]

I just edited the page for John Donne's epigram "Hero and Leander" - it was incorrectly spelled as "Hero and Leader." I changed the title in the page entry, but "Hero and Leader" is still appearing, and a corrected link goes to the Marlow poem instead of the Donne epigram. Can anyone tell me how to fix this (or do I just need to wait for the change to percolate through)

Thanks unsigned comment by Dkohen (talk) .

Yes check.svg Done , all taken care of now —Beleg Tâl (talk) 03:45, 22 June 2019 (UTC)

Page:The Prince (translated by William K. Marriott).djvu/311[edit]

The approach I am using here works, but adding {{p}} tags for each entry would be inefficient. @Xover: is this an approach where a TemplateStyles approach to redefine the P handling for each block of entries could be implemented for this index? It's mostly a simple margin collapse, and combination of that with the CSS style in the dent. It would be nice to be able to customise the indentation and paragraph break spacing behaviour, but I'm not sure TemplateStyles was advanced enough to handle paramatised generation of CSS per called block yet. ShakespeareFan00 (talk) 08:51, 22 June 2019 (UTC)

@ShakespeareFan00: Provided I understand correctly what you mean, this sounds like it could be reasonably solved by using <p class="no-vertical-space"></p> and a per-work stylesheet that removed the margins. That is, in the page markup you use a template that tags it as a particular class name, and then write custom CSS that styles all instances of that class however you want. Provided each paragraph is styled the same, you would not need actually parametrized CSS for this.
For practical reasons we would probably want to require some kind of prefix on the CSS class name (to avoid collisions), or some magic in MW (ProofreadPage and TemplateStyles) that takes care of the scoping. At small volume, for simple cases, and CSS that is used in a single work, this is not likely to be an actual problem; but worth keeping in mind. --Xover (talk) 09:13, 22 June 2019 (UTC)
Yes but I'd like to avoid having to type the P class=foo stuff individually for each paragraph, Ideally what I'd like is {{p-collapse/s}} and {{p-collapse/e}} I can apply over an entire block, which is at most 4 calls per page as opposed to a considerable number of {{p}} calls. ShakespeareFan00 (talk) 09:18, 22 June 2019 (UTC)
Probably doable by using <div class="no-vertical-space"></div> around all the paragraphs and then using a stylesheet that applies the style to div.no-vertical-space > p. But since the actual paragraphs are then generated by Mediawiki there is some fragility here that may or may not be a problem in practice. --Xover (talk) 10:24, 22 June 2019 (UTC)
The other concern, is that the final paragraph of the block would need to revert back to normal behaviour at the bottom. ShakespeareFan00 (talk) 10:42, 22 June 2019 (UTC)
See - Page:The Prince (translated by William K. Marriott).djvu/311 there is a gap between the A and B block entries.
Also- [13] Why is the bottom entry mis-aligned, I was using the /s /e variants to accommodate the split layout?
It seems that at the end of the page it fails to wrap the end paragraph. This is a LONG-standing issue that no-one seems to have wanted to tackle prviosuly. Using {{nop}} in the footer did not change the behaviour. I've also asked at least TWICE for the whitespace behaviour to be PROPERLY DOCUMENTED so I'm not playing hunt the "pedantic minutiae" MANY, MANY, TIMES. ShakespeareFan00 (talk) 11:16, 22 June 2019 (UTC)
@Xover: can you take a look at the experimental version, and tweak? Thanks..ShakespeareFan00 (talk) 13:40, 22 June 2019 (UTC)
@ShakespeareFan00: You'll need to give me more to work with. What pages am I looking at; what am I looking for there; and what needs tweaking? --Xover (talk) 13:50, 22 June 2019 (UTC)
@Xover: Template:P-collapse/s/style.css being the style-sheet ShakespeareFan00 (talk) 14:03, 22 June 2019 (UTC)
On Page:The Prince (translated by William K. Marriott).djvu/311 The text in the scan has a gap between the A and B block of entries. In the code I've ended one P-collapse block and opened a new one.
What needs to happen in the CSS style, is that the margin behaviour for the top margin/padding reverts to normal for the first entry in a collapsed block (i.e the first entry of the B block) ,and conversely needs to revert to normal for the bottom margin in the final paragraph of a block (i.e the end of the paragrpah representing the last entry of the block of A entries.) I had a possible approach commented in the style sheet, but wasn't sure how to cancel a previously defined style back to the normal/default inherited values. ShakespeareFan00 (talk) 14:03, 22 June 2019 (UTC)
You should be able to do that by simply adding a margin to the div itself. I've done that: take a look and see if that does it? --Xover (talk) 14:20, 22 June 2019 (UTC)
Thanks, Also added some rules for the first and last P elements, hope it doesn't add additional space, I an re-comment them if needed. Seems to work so far.

Text Indentation handling[edit]

@Xover: Relating to Page:The Prince (translated by William K. Marriott).djvu/313 Currently I am using {{dent/s}}, {{dent/e}} to set up the text indent, however here there is a slight issue with this, given that the start of the page is a continuation of the previous entry and so as such doesn't need the indent. The slight discrepancy can be worked with for now, but in time it would be nice to be able to have an expanded {{dent/c}} that gives a more accurate behaviour (My current attempt doesn't actually work properly yet). ShakespeareFan00 (talk) 14:40, 22 June 2019 (UTC)

Alternatively, {{Dent/s}} that could be amended to have a suppression parameter for when it's used in Page: namespace headers? ShakespeareFan00 (talk) 14:40, 22 June 2019 (UTC)
The templates make it kinda hard to see, but all of them are really just spitting out HTML div elements with some associated CSS. Most of the /e templates spit out a plain </div>. Which means what you're really doing here isn't some special Mediawiki syntax: it's just various shortcuts for inserting HTML code. And as such, anything you want treated specially needs to be marked up specially.
I can't immediately think of any way to make {{dent/s}} automatically correct for being in the Page: namespace and set an indentation that is correct relative to whatever you had it set to on the previous page (and the pages may even be stored out of order). But simply wrapping the special bit in a separate {{dent/s}}, ending it when the special bit is done, and then adding the regular dent for the rest of the page is relatively cheap. --Xover (talk) 15:17, 22 June 2019 (UTC)
Good thinking in regard to the modified wrapping, but it would have caused problems for the nesting of HTML tags. For now I've just taken out the indentation entirely, and until {{dent}} or another template can be repaired to work correctly over multiple paragraphs and inside other "classed" DIV's without resetting stuff. ShakespeareFan00 (talk) 16:14, 23 June 2019 (UTC)
For whatever reason putting {{dent/s}}{{dent/e}} inside the {{p-collapse/s}}{{p-collapse/e}} causes the P handling to revert back to the default behaviour. Well at least we tried to to get it working. ShakespeareFan00 (talk) 16:19, 23 June 2019 (UTC)
The style is defined as DIV -> P but where the dent is put in it would be DIV-> DIV -> P, I'm not sure there's a way in CSS to say DIV -> (any number of sub levels) -> P Sigh :( ShakespeareFan00 (talk) 16:30, 23 June 2019 (UTC)
Problem exists between user and keyboard, Seems I'd got the CSS rule wrong :) ShakespeareFan00 (talk) 17:44, 23 June 2019 (UTC)

Bulk replacement request[edit]

Index:The Life of the Spider.djvu Currently this uses {{RunningHeader-centered}} in the header and footer of a number of pages.. The code given could be easily replaced with a much simple {{center}} given that the single element present is in the center location, but to do it for all pages manually would be time consuming. Is there someone here that can make the appropriate change with a script, AWB or bot rapidly? ShakespeareFan00 (talk) 09:08, 22 June 2019 (UTC)

Done manually, but it would be nice to have a response sometimes. ShakespeareFan00 (talk) 11:22, 22 June 2019 (UTC)
Expecting a response for a highly technical request in only 2.5 hours is extremely optimistic. —Beleg Tâl (talk) 16:47, 22 June 2019 (UTC)
@ShakespeareFan00: Are you familiar with the AWB software? If you're using Windows, it's a great option for stuff like this. I think it's pretty straightforward to figure out, but I'm happy to answer questions if needed. -Pete (talk) 19:25, 22 June 2019 (UTC)
I am aware of AWB, but feel I lack the communities trust to use it here at Wikisource. ShakespeareFan00 (talk) 19:29, 22 June 2019 (UTC)

Something is corrupt on this page The War with Mexico/Volume 2/Appendix[edit]

Can someone please take a look and advise. Thanks.Ineuw (talk) 06:27, 23 June 2019 (UTC)

Not to panic. When page 562 is formatted correctly no doubt all will come good! 114.78.66.82 08:00, 23 June 2019 (UTC)
Rather than using a table, had you considered using {{p-collapse/s}}{{p-collapse/e}}? ShakespeareFan00 (talk) 15:37, 23 June 2019 (UTC)
I considered all formats but settled on tables, being the most versatile.Ineuw (talk) 20:30, 23 June 2019 (UTC)
PS: @114.78.66.82:. Thanks, the table ended on Page:The War with Mexico, Vol 2.djvu/542 and the main namespace page is fixed.Ineuw (talk) 22:02, 23 June 2019 (UTC)
@Ineuw: You are quite correct. I did not word it well but meant only after the entire set of transcluded pages is (at least) at proofread standard — if the main-space problem remains then is the time to start seriously bug-hunting. I missed the fact Appendix A (and thus the table, too) ended on page 524! 114.78.66.82 04:44, 24 June 2019 (UTC)
Understood what you said about the set. Instead, there are a lot of small tables within the section.Ineuw (talk) 08:13, 24 June 2019 (UTC)

Page:Atlas of the Munsell color system.djvu/9[edit]

Can someone come up with a way to convert the Munsell colors back to RGB for the table cell backgrounds? I tried using a convertor/picker here [14] but the colors picked bear little resemblance to those in the (faded) chart.

I am out of my depth and so an expert to write a conversion script would be VERY much appreciated. ShakespeareFan00 (talk) 14:42, 23 June 2019 (UTC)

I couldn't find anything better than the link you provided. Maybe w:Wikipedia:WikiProject Color will be able to point you in the right direction? —Beleg Tâl (talk) 13:05, 24 June 2019 (UTC)
You could also just open the scan image in Paint or GIMP or something, and use the colour picker tool to identify an approximate colour to use. —Beleg Tâl (talk) 13:06, 24 June 2019 (UTC)
Due to a 'misunderstanding' I'm not editing on Wikipedia right now, otherwise I would have asked an appropriate project there already. Nothing to stop another contributor from doing so though. ShakespeareFan00 (talk) 13:42, 24 June 2019 (UTC)

Translation:Romance_of_the_Three_Kingdoms[edit]

A number of the subpages for this translation are giving rise to "fostered content" , which typically means a table has been misformatted somewhow. Can an experienced contributor take a look and provide a generalised fix that could be applied across all the pages?

(side note, The translation is marked as incomplete). ShakespeareFan00 (talk) 09:08, 24 June 2019 (UTC)

Template:FreedImg/span/doc[edit]

The second example uses a score.

However, the SCORE extension generates a DIV block wrapping the formatted score output. Per HTML structuring conventions, you can't put a DIV inside a SPAN.

Can someone advis on how this might be repaired, or do I need to raise a Phabircator ticket like I did for a related issue with the POEM tag? ShakespeareFan00 (talk) 13:41, 24 June 2019 (UTC)

Use a different template that does not require the contents to be inline elements? —Beleg Tâl (talk) 02:09, 25 June 2019 (UTC)
Whilst the conventional rule is a normal SPAN may not wrap a normal DIV that is not quite what is happening here. Strictly a SPAN modified via display attribute into an inline-block is attempting to wrap a block DIV element which appears to be permissible in some browser renderings. I pose the question (as I do not know myself) if this is a legal (if rather borderline) construct. Any expert opinions? 114.78.66.82 10:25, 25 June 2019 (UTC)

British Calendar Act of 1751[edit]

Can some PLEASE explain why the formatting on this is COMPLETELY *&&^ED up? ShakespeareFan00 (talk) 22:01, 24 June 2019 (UTC)

Can you please explain what part and in what manner is the formatting completely ***ed up? —Beleg Tâl (talk) 02:08, 25 June 2019 (UTC)
Prior to my subsequent updates, the 'sidetitles' overlapped the main body text, in the portion that represented the original Act. This was determined to be due to it using a version of {{cl-act-t}} which was subsequently edited considerably. Replacing it with {{cl-act-h}} and cleaning up the excessive DIV based formatting in that section solved the issue. The rest of the text could be 'standardised' though.

ShakespeareFan00 (talk) 08:34, 25 June 2019 (UTC)

Page numbers do not display correctly..[edit]

See :-- The Prince (translated by William K. Marriott)/How Many Kinds of Principalities there are, and by what Means they are acquired In Firefox, the page numbers are wrong or mis-aligned with respect to other content on the page. ShakespeareFan00 (talk) 12:39, 26 June 2019 (UTC)

It should be OK now, I excluded the empty pages. --Jan Kameníček (talk) 12:57, 26 June 2019 (UTC)
Thanks, it would be nice if the pages tag had a a noblanks option so the page concerned didn't need to be listed individualy in this use case.ShakespeareFan00 (talk) 13:23, 26 June 2019 (UTC)
Hmm. I though it automatically excluded pages marked as "Without text"? --Xover (talk) 14:02, 26 June 2019 (UTC)
No it doesn't. They take up zero vertical space when they are empty, but they are still transcluded. Comes in handy sometimes, for example when transcluding pages that use {{iwpage}} to pull content from another wikisource, but which have no local content that needs proofreading —Beleg Tâl (talk) 15:35, 26 June 2019 (UTC)

[SOLVED] A database error bug in Save a Gadget setting - already reported[edit]

Unchecked the Easy LST option which generated a database query error on Save. Could someone verify it? Ineuw (talk) 19:33, 26 June 2019 (UTC)

I just checked and can't reproduce. If there is a deployment underway currently then it was probably something transient related to that. --Xover (talk) 20:53, 26 June 2019 (UTC)
Thanks for checking. It was repaired/resolved within a few minutes by the powers that be. Ineuw (talk) 23:01, 26 June 2019 (UTC)

Deleting a duplicate book[edit]

Uploaded this file only to find an identical file already validated in pdf format. The difference is that my upload (.djvu) came from Internet Archive, and the .pdf came from Google books. Downloaded the .pdf and replaced the Google claim with a blank page.

I would like to delete the .djvu version. Unless I am mistaken, deleting the index page does not delete the pages. How can I go about removing the pages as well? Ineuw (talk) 06:40, 30 June 2019 (UTC)

@Ineuw: So far as I know there is no special magic involved: both the index and the pages are just wiki pages that happen to be in the Index: and Page: namespaces, and are deleted just like every other wiki page. But to avoid the tedium you will probably want to enable the MassDelete tool at the bottom of the Gadgets section of your Preferences so that you can use Special:MassDelete to do them all in one batch (temporary bot flag is probably a good idea too). --Xover (talk) 06:59, 30 June 2019 (UTC)
Much appreciated. Will tackle it tomorrow.Ineuw (talk) 07:10, 30 June 2019 (UTC)

Migrating from Index:A Chinese and English vocabulary, in the Tie-chiu dialect.djvu to Index:A Chinese and English vocabulary, in the Tie-chiu dialect.pdf[edit]

Are there any bots that can be used to ease the process of migrating to Index:A Chinese and English vocabulary, in the Tie-chiu dialect.pdf?

(If not, could I personally use AWB?) Suzukaze-c (talk) 02:35, 1 July 2019 (UTC)

Would be preferable in my opinion to repair Index:A Chinese and English vocabulary, in the Tie-chiu dialect.djvu and continue to use it. —Beleg Tâl (talk) 11:09, 1 July 2019 (UTC)
As in converting the PDF to DJVU? I think I like the general quality of the PDF more as well. (although, MediaWiki seems to be returning images of lower-quality than what I can see in PDF.js or pdfimages.) Suzukaze-c (talk) 21:30, 1 July 2019 (UTC)
Eh, using the DJVU file format doesn't cause MediaWiki to ruin the image resolution (??????), so I took the time to assemble a new DJVU. 🤷 Suzukaze-c (talk) 04:51, 2 July 2019 (UTC)

Okay why doesn't something work?[edit]

I created {{table class}} recently:-

{|{{ts|bc}}
|-{{ts|vtp}}
|Line 1<br />Line 2
|Line 3
|}
Line 1
Line 2
Line 3

works, compared to :-

{|{{ts|bc}}{{table class|cell_vtp }}
|-
|Line 1<br />Line 2
|Line 3
|}
Line 1
Line 2
Line 3

where the vertical alignment option is moved to a table class to apply it universally doesn't. WHY? Is Mediawiki being pedantic about where it expects to see things, as with SO many other issues, making it much more complicated than it needs to be? (sigh)

ShakespeareFan00 (talk) 09:36, 3 July 2019 (UTC)

The reason for creating {{table class}} was so I did NOT need to use a multiple {{ts|vtp}} calls. But if it's not going to work properly... as evidenced here - Page:Miscellaneous Babylonian Inscriptions.djvu/79 then why should I bother trying to make things less costly in terms of parser calls etc....

ShakespeareFan00 (talk) 09:40, 3 July 2019 (UTC)

It seems that for the moment I need to import the relevant style sheet outside the table {{table class/import}} ... hmm ShakespeareFan00 (talk) 10:42, 3 July 2019 (UTC)
The answer as to why is simple. Look at the table of parameters in the documentation for {{ts}}. "vtp" has a "no" for table, but a "yes" for row and cell. The solution is therefore logical, and I leave it to the reader to derive. Beeswaxcandle (talk) 08:17, 4 July 2019 (UTC)
So my styles were incorrect. :) Thanks. and I'd like someone to review the new templates (see Scriptorum) anyway. ShakespeareFan00 (talk) 08:36, 4 July 2019 (UTC)

The Christian's Secret of a Happy Life[edit]

This says there are misnested SMALL tags, but despite going over the alleged mistaken sequences MANY times, I can't find the mistake, Can someone please indicate precisely WHERE and WHY the relevant passages are misnested? because right next to them are nearly identical consturctionswhich DO NOT CAUSE the Linter tool to identify them as a mistake. I am getting extremely tired of running around playing hunt the minutiae, because certain tools don't provide enough SPECIFIC infrmation to actually repair a page.ShakespeareFan00 (talk) 13:44, 5 July 2019 (UTC)

My advice: don't even bother. That work is a garbage copydump and contains way more problems than linter mistakes. Don't waste your time playing whack-a-mole with a text that should be replaced wholesale instead. —Beleg Tâl (talk) 16:26, 5 July 2019 (UTC)
I did manage to repair it after a LOT of search and replace. However, as you say a properly scan-backed version would be much much better. ShakespeareFan00 (talk) 17:15, 5 July 2019 (UTC)
I have a theory about what might have gone wrong in respect of the SMALL misnesting though, see the "Pathological HTML test case" example, in my Userspace sandbox, Not that it's something LintError would directly tell you to look for :( ShakespeareFan00 (talk) 17:16, 5 July 2019 (UTC)

Page:Mrs Beeton's Book of Household Management.djvu/633[edit]

This for SOME reason stopped working correctly, when an update was made to the underlying module, I reverted the changes to the module, but I suspect they were made in good faith. What broke it and why?

ShakespeareFan00 (talk) 17:02, 5 July 2019 (UTC)

What module? What changed? What was broken? —Beleg Tâl (talk) 22:36, 5 July 2019 (UTC)
Module:Aligned table, https://en.wikisource.org/w/index.php?title=Module%3AAligned_table&type=revision&diff=9414404&oldid=5704424 removed the code which suppressed the generation of a header and footer portion of the generated table, which I'd used on the page concerned in an attempt to simplfy the table generation. ShakespeareFan00 (talk) 08:31, 6 July 2019 (UTC)

Page numbering, Dynamic layouts... etc...[edit]

Is there a reason why the pages tag doesn't have a layout=foo.css option?

I was looking at the markup here Equitation/Chapter 28 which does a custom layout, which to me (given that it's being applied to the whole work would be better suited as being a 'layout') or a stylesheet.

It's also confusing what needs to be defined in a layout specfically, some more documentation on this would be nice. ShakespeareFan00 (talk) 21:17, 5 July 2019 (UTC)

You'd probably have to ask the devs for why the proofreadpage extension is the way it is. There is also a CSS field in the Index page form which as far as I can tell does nothing at all. Using a template to apply styles to a work as a whole is a clever workaround. I don't think layouts are the right tool for this type of effort. —Beleg Tâl (talk) 22:43, 5 July 2019 (UTC)
The CSS field is supposed to apply that style in the Page namespace, iirc. But, no, it seems, essentially useless in practice. The idea in task T226275 though, might make the style effectively configurable from the Index: page. Or it might make sense to add the |layout= parameter you suggest here.
The page numbers / dynamic layout stuff is a great idea, but it's not really "finished". The layouts are hardcoded inside a javascript that is unconditionally loaded from common.js. I'm trying (off and on; I keep hitting dead ends) to figure out some way to first turn it into a Gadget—so that it can be temporarily disabled by anyone working on a new version of it—and then to clean it up and refactor it. One of the first tasks in that would be to move the actual layouts out of the javascript and into separate .css files that are actually editable by anyone that knows CSS. At that point we might start running into conflicts between the dynamic layouts and a hypothetical custom style provided by ProofreadPage, but that should be manageable if define what gets used for which thing well. It's entirely possible such changes to ProofreadPage will make the local dynamic layouts mostly obsolete. --Xover (talk) 08:48, 6 July 2019 (UTC)

Philosophical Review/Volume 1/September 1892/Der menschliche Weltbegriff[edit]

This apparently has a badly formed header. Can someone with the time and expertise please figure out why the header template is seemingly unable to cope with SIMPLE italics in a title, causing it throw lint errors?

I think the header template needs a complete rebuild anyway, given that a VERY large number of LintErrors I have had to fix recently are ultimately caused by very specfic minutiae of how whitespace and pairs of markup tags are dealt with. As I've said REPEATEDLY it is unreasonable to expect contributors to know these precise miniutiae every single time they might want to use a template. Is the header template sufficiently complicated that it can't actullay be made to work consistently from a contributors perspective, or converted to a Module that is better able to cope with the more unusual things contributors supply as parameters to it?

ShakespeareFan00 (talk) 20:48, 6 July 2019 (UTC)

I don't see any problems in the header, though the title and section field are swapped. I don't expect contributors to know or care about lint errors either (I don't care about them myself). If the devs want us to care about lint errors, they can make tools to prevent lint errors from being introduced in the first place. — I do, however, think it would be worth revisiting the header template, aligning it with modern responsive web design principles, integrating it more heavily with Wikidata, and so forth. I do acknowledge that it would be extremely hard to preserve backwards compatibility if this were done, and backwards compatibility is extremely important given the number of "hacks" that are in place currently to get the desired display in the current structure. —Beleg Tâl (talk) 23:32, 6 July 2019 (UTC)
I care instead and I think it should be enforced and become an habit. I spent quite a lot of effort in cleaning up the backlog. "lintHint" is very quick and quite helpful (most of the times ... and except that in Page ns, page or page-preview behave differently). Immediate clean-up is N times more efficient than cleaning up afterwards. And most of the times issues are wrong nesting of tags, due to misuse of div-based vs. span-based templates. — Mpaa (talk) 20:31, 8 July 2019 (UTC)
I would only support enforcing it if the Wikisource interface were to automatically by default check every edit for lint errors and clearly display exactly what needs to be fixed, in terms any noob editor can understand. Otherwise it is completely unreasonable to expect anyone to do this. Wikisource is a steep enough learning curve already. —Beleg Tâl (talk) 20:52, 8 July 2019 (UTC)
Without making too complex, I think it would be enough to make the gadget mandatory and add a sentence at the bottom of the page in Preview mode to ask (or suggest, as there might be some hard cases to figure out, i.e. it is not mandatory but encouraged) to run it. Errors are quite well explained at mw:Help:Extension:Linter, which could also be added near the message. IMO, it is reasonable to ask at least experienced editors to chip in to maintain the work as clean as possible. Not being visible does not mean we should ignore it.— Mpaa (talk) 22:27, 8 July 2019 (UTC)

Page:Sintel movie 4K.webm/8[edit]

Perhaps someone with sharper eyes can figure out EXACTLY where something is misnested? (because neither LintErrrors or the LintHint script could identify precisely WHICH template call in a overly complex nested set of templates was ACTUALLY responsible). ShakespeareFan00 (talk) 18:21, 7 July 2019 (UTC)

This was an unclosed small-caps template. For future reference, an easy way to fault-find these issues, even on very large pages, is:
  • Copy-paste the content to a sandbox page (optional, but allows you to save "checkpoints")
  • Run the LintHint tool from the edited page, it should show the same errors
  • Remove self-contained (i.e. don't break templates) chunks of text one at a time, checking LintHint each time.
  • When an error disappears, the culprit was in the last block removed.
  • Ctrl-Z to remind yourself what the block was. If the block was very large and the error is still not obvious, subdivide the block and do it again. Saving the sandbox at this point can be helpful, as you use "Show changes" to see the diff.
Hope that helps in future. Inductiveloadtalk/contribs 10:17, 8 July 2019 (UTC)

Sidenotes don't work directly in mainspace?[edit]

Anglo_Saxon_Chronicle_(A-Prime)

This uses sidenotes, but the formatting to do them correctly and the appropriate layouts is never directly loaded because it forms part of the page numbering script used when transcluding pages with a <pages> tag. Can someone come up with a way to use them directly? or provided an alternative format for use here? {{pline}} might be what was intended. ShakespeareFan00 (talk) 09:11, 8 July 2019 (UTC)

{{Pline}} would probably suffice. This edition is a copy of a copy of a copy so I wouldn't put too much bother into it; if {{pline}} works and is easy to implement, go for it. —Beleg Tâl (talk) 14:52, 8 July 2019 (UTC)
I did a quick test, and it doesn't look right. (sigh). Rhetorical: When will the contributors with technical expertise on this project actually get around to ACTUALLY fixing the many problems I've REPEATEDLY mentioned in terms of getting core things like sidenotes, like badly nested templates &c. &c. ShakespeareFan00 (talk) 16:13, 8 July 2019 (UTC)
Maybe try {{np2}}? —Beleg Tâl (talk) 16:32, 8 July 2019 (UTC)
Possibly, but I am going to take a break from trying to solve this problem right now.ShakespeareFan00 (talk) 18:29, 8 July 2019 (UTC)

Page:Tycho_brahe.djvu/111[edit]

The image isn't actually centered despite the stylesheet saying to do the margins automatically. Suggestions before I start sending carefully worded emails with choice comments to certain contributors? ShakespeareFan00 (talk) 15:54, 8 July 2019 (UTC)

The {{img float}} template is for floating images, which are put into spans so they can be inserted without breaking paragraphs. This template has never been intended or worked really well for centred images for that reason (centring a span doesn't mean an awful lot, you have to set text-align:centre on the container, not the span). In fact, when I wrote it way back in 2010, I didn't give it a centre option. The documentation of the template suggests two alternatives, one of which is not to use a template at all, because the "raw" File: method already has a centre argument. Alternatively, specifically for centred images, {{FreedImg}} has "smarter" behaviour for resizing, etc, but there are a few quirks there too (like an automatic 94% font size). Inductiveloadtalk/contribs 16:18, 8 July 2019 (UTC)
Okay so why is the documentation saying something is possible when it CLEARLY isn't? ShakespeareFan00 (talk) 16:21, 8 July 2019 (UTC)
The first suggested approach in the documentation DOES NOT WORK and it would be helpful if at some point it was in fact removed.ShakespeareFan00 (talk) 16:27, 8 July 2019 (UTC)
Hmmm - https://en.wikisource.org/w/index.php?title=Template%3AImg_float&type=revision&diff=9019969&oldid=3864440 I wonder if this is what broke it. I recently had to revert another of this users good faith efforts to "update" something.... ShakespeareFan00 (talk) 16:31, 8 July 2019 (UTC)
{{Img center}} is the start of an experimental image centering template, It still uses DIV's though, so can't yet be used to solve issues elsewhere, If you want to improve it feel free, currently it just passes through a File syntax option, but removes one of the borders. Needs much improvement. (sigh) ShakespeareFan00 (talk) 19:12, 8 July 2019 (UTC)
Why does it need a new template anyway? File: and a {{center}} will work for the most common case, and {{block center}} for the rest. And if that's still not enough, {{FreedImg}} should handle it. Inductiveloadtalk/contribs 21:39, 8 July 2019 (UTC)
{{FI}} is not necessarily inline, which means it can't be embedded inside a SPAN or P based template, or inside a P created by transclusion, Imgcenter is yet another attempt to work around this limitations (sigh) Sometimes I wish there were more people willing to fix these problems in the backend instead. ShakespeareFan00 (talk) 22:02, 8 July 2019 (UTC)
Anyway : Category:Images using center float, That's about 1100 images using a center imgfloat, which DOES NOT WORK, Perhaps you would be willing to get started on finding a CONSISTENTLY behaving LONG-TERM fix, so as with so many other issues, the same concerns do not have to be raised REPEATEDLY here, with no credible approach emerging. I am increasingly fed up, with being told to use various work-arounds that are potentially unstable or building up future problems. Unfortunately to really resolve issues and concern like 'inlined images' would need someone to hold down a developer until they actually respond to concerns like this instead of developing even more controversial bits of wizard gadgetry for a prestige project like Wikipedia. rant rant &c.

ShakespeareFan00 (talk) 22:22, 8 July 2019 (UTC)

On a related note - {{FIS}} doesn't work properly either as evidenced here -A_history_of_the_gunpowder_plot/Chapter_1 when I tried it. Unless someone comes up with a credible fix by the end of the week, I will consider just disabling or removing both templates, because they just DO NOT WORK correctly anymore.ShakespeareFan00 (talk) 22:35, 8 July 2019 (UTC)
Here {{FIS}} screws up the page numbering - A_history_of_the_gunpowder_plot/Chapter_24 at the point the image appears. ShakespeareFan00 (talk) 23:11, 8 July 2019 (UTC)
There is no calign parameter on {{FIS}}. Why are you not following the documentation and using {{FI}} as recommended for centred images? 114.78.66.82 01:41, 9 July 2019 (UTC)
According to the documentation for {{FIS}}, for centred images, you must ensure the width + margin-left + margin-right sums to 100%. You did not do this, so the span's cleared width is only the width of the image + padding + margins. As it is a span, it is embedded in the overall container, of course it doesn't "claim" more block-wise space. The example on the page uses percentages: 30% + 35% + 35% = 100%. You used px, so it's impossible get 100% width with hardcoded values (as 100% could be any number of px). You could do it with CSS calc() function, if it is acceptable WRT browser support (Chrome 26, Firefox 16, IE 9, Safari 7). This works for me:
{{FIS
 |file=Conspiratorspg19.jpg
 | width=600px
 | margin-left=calc((100% - 600px) / 2);
 | margin-right=calc((100% - 600px) / 2);
}}
I'd appreciate input as to the acceptability of this, is there a minimum browser version targeted? Perhaps some e-readers wouldn't appreciate it? Do we care? If so, it could be useful to allow the template to apply a default margin-left/-right of calc((100% - imgWidth) / 2), as this avoids the template caller having to do this.
I do not think issuing an ultimatum threatening to disable/remove a template used by something like 16000 pages is constructive. Moreover, these templates have (relatively complete) documentation, even if they clearly have some issues. If you have beef with the docs, might I also suggest that they do say that charity begins at home? Inductiveloadtalk/contribs 07:26, 9 July 2019 (UTC)
Agreed. And thanks for reminding me to add the documentation for those templates. ShakespeareFan00 (talk) 07:59, 9 July 2019 (UTC)
And thank you taking the time to respond with the above suggestion regarding calc. I would agree with the auto option for the margin handling as it does exactly what was intended. [[15]] looks EXACTLY as intended now. ShakespeareFan00 (talk) 08:11, 9 July 2019 (UTC)
Glad it's working.
Be careful with the word "auto": in CSS it has a different meaning, which doesn't really make sense for inline elements (even with display:inline-block). The current {{FIS}} does actually use auto for margin-left and -right. This doesn't work as it does with {{FI}} because it produces this:
<span id="cSpan1" style="display:inline-block; width:100%; margin-right:auto; margin-left:auto;>
    ...
</span>
This only works for width=100% because there is no space on the floated line for anything else. As soon as width is less than 100%, you'll find the cSpan1 span only has whatever width you give it and no margins. This allows other elements on the floated line, or the embedding container, to creep up next to the image.
WRT to making this automatic, we'd have to agree that CSS3 calc() is "OK" for general use. Unless this is already agreed ({{div col}} already uses CSS3 properties). Inductiveloadtalk/contribs 09:10, 9 July 2019 (UTC)
It seems in some instances Mediawiki or other Wikisourced templates may already be using CSS3 type features.. Examine the HTML generated for the poem in [[16]] for example? ShakespeareFan00 (talk) 14:07, 9 July 2019 (UTC)

Enough is enough: WHERE is the mistake? i.e where the's flipped formatting?[edit]

According to the LintErrors page there's a flipped over DIV SPAN combination SOMEWHERE in a transcluded page for this Nicholas_Nickleby/Chapter_24, however, I've run ALL the relevant pages through the Lint hint script INDIVIDUALLY and it did NOT find a concern on ANY of the transcluded pages. So can someone PLEASE indicate EXACTLY WHERE LintErrors is deciding to be pedantic before I send a very strongly worded e-mail to the maintainers of the Linter tool about it's increasingly frustratingly INACCURATE false-detections ? ShakespeareFan00 (talk) 23:38, 8 July 2019 (UTC)

Could it be this? I found it quickly using Special:ExpandTemplates + an HTML validator.
<div style="display:table; position:relative; margin:0 auto; width:auto;">
<span style="font-size: 83%;"><div class="poem">
<p>Sing, God of Love, and tell me in what dearth <br />
Thrice-gifted <span style="font-variant:small-caps">Snevellicci</span> came on earth, <br />
To thrill us with her smile, her tear, her eye, <br />
Sing, God of Love, and tell me quickly why.
</p>
</div></span>
</div>
Suzukaze-c (talk) 02:43, 9 July 2019 (UTC)
Thank you, I'm very suprised that when I checked that page, the checker script didn't find it initially. Is this something that a localised script could check for and repair automatically, as the repair looks straightforward. @Mpaa:. ShakespeareFan00 (talk) 07:58, 9 July 2019 (UTC)
I don't know about an automated repair tool, as wikitext is notoriously tricky to parse, but finding lint failures in some unknown subpage is easy with Pywikibot:
   pwb.py listpages -linter:html5-misnesting -prefixindex:Page:Archaeological_Journal -intersect
    1 Archaeological Journal, Volume 1.djvu/8
    ....
   10 Archaeological Journal, Volume 5.djvu/5
 10 page(s) found
This won't find lint errors that manifest only when the pages are transcluded together, but it would presumably have found this one. Hope it helps, Inductiveloadtalk/contribs 10:49, 9 July 2019 (UTC)
Thanks, I am not in the best position to ask, but would you also be willing to mention the pywikibot angle in the phab ticket at https://phabricator.wikimedia.org/T226400 ? If this check could be an additional "check transcluded pages" button available from Special:LintErrors it would be a rather useful addition. ShakespeareFan00 (talk) 14:05, 9 July 2019 (UTC)

Is there a bot that checks for ligatures?[edit]

I have just proofread and transcluded Sin_and_Crime:_Their_Nature_and_Treatment. I found quite a few f ligatures in the scan, as listed in the Index talk:Sin_and_Crime.pdf, but they're hard to spot with my eyes and I'm thinking they would be quite easy to catch with a bot? Zoeannl (talk) 10:06, 9 July 2019 (UTC)

They are also very quickly spotted if you use certain fonts as the edit-box font. (I use Bedstead (which is based on a teletext font precisely because it's very easy to spot obviously different things like ligatures. ShakespeareFan00 (talk) 15:19, 9 July 2019 (UTC)
Done.— Mpaa (talk) 21:28, 9 July 2019 (UTC)

Santos-Dumont[edit]

Hi people! Is ok to use these books by Santos-Dumont on their respective language Wikisources (English, French and German)? All the archives are from before 1920s and I remember to saw the French one on the fr.Wikisource sometime ago but I couldn't find now. Thanks, Erick Soares3 (talk) 15:23, 9 July 2019 (UTC)

@Erick Soares3: All works published anywhere in the world before 1924 are in the public domain in the US (95 years after publication). In Brazil, the term of protection is 70 years after the death of the author (pma. 70). Works by Santos-Dumont thus entered the public domain in Brazil in 2003. That means the scans can be hosted on Commons, and the English language works can be transcribed on English Wikisource. I am not familiar with the policies on frWS and deWS, but I would be very surprised if they were stricter than Commons. They may however have other restrictions (taking into account the jurisdiction of the transcriber, say) that affect the issue, so the only way to be sure is to ask on their respective Scriptoriums. --Xover (talk) 16:10, 9 July 2019 (UTC)
@Xover:, thanks! I will upload the English book and then research about the French and German Wikisources. Erick Soares3 (talk) 17:30, 9 July 2019 (UTC)
@Xover, @Erick Soares3: The French WS policy is PD in country of origin and the German WS is PD in EU (death+70), which are both fine for Santos-Dumont. —Nizolan (talk) 17:31, 10 July 2019 (UTC)
@Nizolan: Thanks! The German version was translated by Ludwig Holthof that I can't find any biographical information, but seeing that his works date from late 19th early 20th century I think that is easy to assume that are PD. Erick Soares3 (talk) 17:49, 10 July 2019 (UTC)
I just found that the translator died in 1911]. So, is PD. Erick Soares3 (talk) 17:52, 10 July 2019 (UTC)

Page:The Elements of Euclid for the Use of Schools and Colleges - 1872.djvu/31[edit]

I'm not entirely convinced calling lots of float rights is the best approach? Is there a way to combine the functionality here into a single template or indeed a stylesheet that could be universally applied per page? This works, so hardly a priority. ShakespeareFan00 (talk) 22:50, 9 July 2019 (UTC)

The postulate titles are floated right, so {{float right}} is exactly the best possible approach. You could use {{rbstagedir}} to apply the other formatting along with the floats if desired. However, if by "single template" you are thinking of creating some sort of {{eeusc-header-fl-r}} type monstrosity, please don't. It can do no better than the current solution, and it will be vastly more difficult to maintain. As for stylesheets, this should be accomplished by modifying {{float right}} rather than creating an alternative template whose only difference is that it uses classes instead of inline styles. —Beleg Tâl (talk) 12:19, 10 July 2019 (UTC)
(Aside) Float-right is SPAN based, which may be the reason a number of misnesting errors are being identified in other works. Block based content should not use a float-right in it's current form. Not sure how in some instances this would be fixed without having to do some pusedo-P hacks, to allow a DIV based float, but hiding the paragraph breaks, which I am very unwilling to do for maintenance reasons. unsigned comment by ShakespeareFan00 (talk) .
I didn't notice it is span based. We should create a separate template for block elements (maybe modify {{block right}}?). In the case of the Elements however, the floated content is inline so {{float right}} is fine. —Beleg Tâl (talk) 14:38, 10 July 2019 (UTC)
There's also the issue of precisely where Mediawiki decides to "tidy", or end paragraphs which seems to be a dark art to decipher at times. this is despite REPEATED requests for someone to actually sit down and FORMALLY document what it's SUPPOSED to do. ShakespeareFan00 (talk) 16:14, 10 July 2019 (UTC)

CharInsert no longer displays the User defined row[edit]

Every page opened for editing I must re-select the "User" defined row of characters. I tried working with the "Special characters" built into the Toolbar, but this lacks ligatures among other things. Is there anything can be done to fix the Charinsert.Ineuw (talk) 08:13, 10 July 2019 (UTC)

Not seeing this behaviour in CharInsert for me (Monobook skin, no toolbar (since they stole it), and FF 67). Beeswaxcandle (talk) 08:37, 10 July 2019 (UTC)
@Beeswaxcandle: Are you saying that your "User" Charinsert selection shows up automatically when you open a page for edit? Also, please clarify "no toolbar (since they stole it), and FF 67)". To emulate your setup I witched everything to Monobook (from Vectra).
  • Logged out from WS and deleted the en.wikisource cookie from FF 67.0.4.
  • Logged back, and in the Page namespace I edited a page.
  • Set Charinsert to "User", and saved the edited page.
  • Opened the following page in edit mode, and my Charinsert reverted to "Insert" row.Ineuw (talk) 20:25, 10 July 2019 (UTC)
In preferences, editing tab, I have "Enable the editing toolbar" off. I loathe this one and manage without it. The only thing I can't do is initiate OCR of a page. Beeswaxcandle (talk) 05:54, 11 July 2019 (UTC)

POEM inside REF tags?[edit]

Can Poem not appear inside a REF tag? Because I can't find another reason why King_Solomon's_Mines/Chapter_XVI should be giving a DIV SPAN swap warning. Yet sometimes in other works this behaviour works, and sometimes it doesn't (Sigh!)

Do I actually have to do something drastic to get things PROPERLY fixed? ShakespeareFan00 (talk) 16:03, 10 July 2019 (UTC)

Examining one of the poem based references : here :
<ol class="references">
<li id="cite_note-1"><span class="mw-cite-backlink"><a href="#cite_ref-1" aria-label="Jump up" title="Jump up"></a></span> 
<span class="reference-text">
<div class="poem">
<p><span style="float:left; text-align:right; margin-left:-moz-calc(0em - 3em); margin-left:calc(0em - 3em); width:3em;">"</span>Now haste ye, my handmaidens, haste and see<br>
How he sits there and glowers with his head on his knee."
</p>
</div></span>
</li>
</ol>

Which is very obviously malformed HTML. You clearly can't put a DIV in a SPAN. As this is the behaviour of Extension:Cite itself, this isn't going to be a problem that can be solved easily, given that for it to work, what Extension: Cite actually generates will need updating. Extension:Cite however is a fairly core template... (worried look). I'm also suprised no-one noticed this previously. ShakespeareFan00 (talk) 16:44, 10 July 2019 (UTC)

Looks like it has been noticed previously, (phab:T49544 "<references/> list item must not wrap the text in <span>"), but some kind of server error is preventing me from seeing the content of that ticket. —Beleg Tâl (talk) 16:56, 10 July 2019 (UTC)
I hope by "do something drastic" you mean "create lots of tickets at Phabricator" because that would very likely be the best solution for parser-level issues like this. —Beleg Tâl (talk) 16:59, 10 July 2019 (UTC)
I think I had raised several tickets of this nature prveviously. ShakespeareFan00 (talk) 17:12, 10 July 2019 (UTC)
If I haven't, maybe I should open a new one, linking here. ShakespeareFan00 (talk) 17:38, 10 July 2019 (UTC)
I am not using HTML but have no problem creating tables and poems within <ref></ref> tags with our templates.Ineuw (talk) 20:32, 10 July 2019 (UTC)
You're missing the point a little bit. The Cite extension will absolutely allow you to create tables and poems within ref tags, but every time you do this the Cite extension will generate malformed HTML regardless of what markup you use. —Beleg Tâl (talk) 21:01, 10 July 2019 (UTC)
I stand corrected Beleg Tâl. :-) Never used the Cite template.Ineuw (talk) 21:37, 10 July 2019 (UTC)
If you've used ref tags, you've used the Cite extension. The Cite extension is what provides us with the ref tag, the references tag, and probably a couple of other things. —Beleg Tâl (talk) 23:18, 10 July 2019 (UTC)

China Review scans from HKU[edit]

HKU has uploaded scans of the articles from the 25 volumes of The China Review (1872–1901), all of which should be PD. Unfortunately they only include the articles and not the frontmatter and other non-article pages of the journal volumes/numbers (notably there's no scan of the ToC). Are these OK to upload article by article? The alternatives aren't much: IA has a couple of issues of CR but not more than that; HathiTrust seem to have scans of the whole thing but their nutty copyright policy—they view anything after 1879 as copyrighted by default and allow only pdfs of individual pages to be accessed, and from the US only—makes it technically difficult to transfer them. —Nizolan (talk) 18:57, 10 July 2019 (UTC)

(Worth noting a contents page for The China Review already exists but the external links are all to the mostly unusable(?) HT scans. —Nizolan (talk) 21:21, 10 July 2019 (UTC))
HathiTrust only treats everything after 1879 as copyrighted because you're outside the US; as a general rule, everything before 1924 is free on HathiTrust. Their agreement with Google means you can't download the whole PDF of Google-scanned files (most of them), but they don't make any serious effort to stop people for downloading them page by page. I can do it for any work you need.--Prosfilaes (talk) 07:16, 11 July 2019 (UTC)
@Prosfilaes: I figured, my complaint was more that, afaik, there's nowhere in the world that has a "publication + 140 years" law so it's a pointlessly overrestrictive policy on their part. The articles I'm interested in at the moment are pre-1879 so I should be able to get the volumes from Google for now, but I might take you up on the offer in the future, thanks. —Nizolan (talk) 12:37, 11 July 2019 (UTC)
In 2010, the earliest known work under copyright in the UK was from 1859. In 2011, it was from 1865.[17] So if one wants to be absolutely correct about life+70 law, publication + 151 years is necessary. For a major author, Author:Bertrand Russell's first work will be 145 years old when his works leave copyright in life+70 countries. Restricting, but not pointlessly overrestrictive.--Prosfilaes (talk) 22:52, 11 July 2019 (UTC)

Sometimes Mediawiki makes me want to scream...[edit]

Page:The_Church,_by_John_Huss.pdf/353, A misnesting glitch is PURELY down to whitespace handling such as occurs at the end of a page between the text and the footer. And this means what should be a paired opening and closing SPAN {{hin/s}} (in the body) and {{hin/e}} (in the footer), are incorrectly tidied up, making what was supposed to be an intended template USELESS in one of it's intended use cases, and causing unecessary Linter warnings Or am I not seeing an obvious repair? ShakespeareFan00 (talk) 21:38, 10 July 2019 (UTC)

If the transcluded output renders correctly, I would not consider the template useless. Does MediaWiki always generate lint errors if a span is split this way? If so, this is a bug and the devs have to fix it, because open/close span templates are not going anywhere. —Beleg Tâl (talk) 23:31, 10 July 2019 (UTC)
I'm not sure it transcludes nicely, and I couldn't see any obvious errors in the direct HTML view in the browser. I think Linter MIGHT be misdetecting this very specfic use case... ShakespeareFan00 (talk) 00:30, 11 July 2019 (UTC)

Page edit problems[edit]

The Page header appears below the textbox on top of the footer see display.

Also, the OCR button (activated in Gadgets) is frozen, although the "Site: General utilities needed by the templates and portals of this wiki project." is active.Ineuw (talk) 21:32, 10 July 2019 (UTC)

I tested these in both Windows 10 and Linux Mint 19.1 in Firefox 68 and the latest stable Vivaldi.Ineuw (talk) 21:32, 10 July 2019 (UTC)

Works for me, Windows 10 v1903, Firefox 68 and latest stable Vivaldi. I assume you've tested it while logged out? —Beleg Tâl (talk) 23:38, 10 July 2019 (UTC)
I did and it didn't work, so after taking a long break, now everything works.Ineuw (talk) 07:00, 11 July 2019 (UTC)
@Beleg Tâl: My software is identical to yours but again the same, . . . the OCR stopped working and the header position is again at the bottom. When logged out, the page layout is fixed, but cannot test the OCR (but I am sure it's good). Cleared all cookies. Logged in and after two pages the problem returned. I am convinced that it is the software, because as I said earlier it is the same in Vivaldi as well. Any ideas? Ineuw (talk) 07:37, 11 July 2019 (UTC)
@Ineuw: Do you have any messages in the Javascript Console? Have you tried blanking your user scripts to check whether something in there is affecting this? There was a new Mediawiki release deployed yesterday. I don't see anything obviously related, but in the interaction between changes to Mediawiki and custom user CSS and JS there is a lot of potential for stuff to break. --Xover (talk) 11:11, 11 July 2019 (UTC)
@Xover:, That's the one thing I forgot, because I use it very rarely. Thanks for the reminder. As for my custom scripts, I will remove and re-install them one by one.Ineuw (talk) 20:01, 11 July 2019 (UTC)

┌─────────────────────────────────┘
@Xover: Tracked down the source of the error. It is the pathoschild family of scripts. Emptied vector.js and .css, Then restored the .css and everything was fine. Then, one by one, I added the scripts until the errors popped up. This was when I added the first script pointing to pathoschild tools on wmflabs in the vector.js

A maximum of 6 errors (below) showed up when opened a Page for editing. Otherwise, 3-4 various "Content Security Policy" errors everywhere always, with numerous warnings about outdated load.php issues. Should I file a bug report?Ineuw (talk) 02:54, 12 July 2019 (UTC)

Content Security Policy: The page’s settings observed the loading of a resource at https://tools-static.wmflabs.org/meta/scripts/pathoschild.templatescript.js (“script-src”). A CSP report is being sent.

Content Security Policy: The page’s settings observed the loading of a resource at https://tools-static.wmflabs.org/meta/scripts/pathoschild.templatescript.js (“script-src”). A CSP report is being sent.

Content Security Policy: The page’s settings observed the loading of a resource at https://tools-static.wmflabs.org/meta/scripts/pathoschild.util.js (“script-src”). A CSP report is being sent.

Content Security Policy: The page’s settings observed the loading of a resource at https://tools-static.wmflabs.org/meta/scripts/pathoschild.regexeditor.js (“script-src”). A CSP report is being sent.

ReferenceError: hookEvent is not defined index.php:390:1

Content Security Policy: The page’s settings observed the loading of a resource at blob:https://en.wikisource.org/df413324-e851-40c8-abc0-28ebe15755c9 (“script-src”). A CSP report is being sent.
@Ineuw: Hmm. The CSP messages can be ignored: they're output for everything hosted on wmflabs.org and it's just reporting.
The remaining message, though, is a genuine symptom of an error somewhere. .hookEvent() is a function for attaching multiple event handlers at once that was provided by the old "wikibits.js" library that has been slowly being phased out since before the introduction of ResourceLoader. .hookEvent() in particular, was deprecated in MediaWiki 1.17 (released in 2011) and removed in MediaWiki 1.29 (released in 2016). It seems unlikely that the new MediaWiki version deployed on Wednesday (1.34/wmf.13) would have made any change that affected that one way or another. I also copied your vector.js and failed to reproduce both the header positioning issue and the error message in the console, so the browser would seem to be one factor playing into it. I tested in Safari and Firefox, and neither had the header positioning issue; but Firefox did point to some potential issues in your personal copy of the nop-inserter script (don't we have a Gadget for that now?).
I don't think we have the source of the problem pinpointed enough to make a good bug report yet, so I'll keep poking around to see if I can find anything else useful. You might want to try tacking &debug=1 onto the end of the URL on a page where you see the problem: it tells MediaWiki to send you each javascript separately instead of bundled together through ResourceLoader, so error messages in the console will give you a better chance of tracking down exactly which line in which script is triggering the error. --Xover (talk) 07:18, 12 July 2019 (UTC)
Your help and advice is much appreciated. My copy of the nop-inserter.js highlights the page navigation arrow in green (for a few seconds) to indicate success. The general nop-inserter in Gadgets flashes a message. Both of these options exist in the public Gadget but the community preference was for the message and I was used to the colour highlight. PS. will post the results of &debug=1.Ineuw (talk) 07:33, 12 July 2019 (UTC)

Documentation markers for charcter(SPAN) vs paragraph(block) based templates..?[edit]

I'd like these to categorise the parent template they are on into an appropriate category, but not the Doc page they appear in?

Is this possible? Thanks. ShakespeareFan00 (talk) 09:37, 11 July 2019 (UTC)

@ShakespeareFan00: You might try putting your templates on the /doc page but inside <onlyinclude>{{div-based-template}}</onlyinclude>. The /doc page is transcluded onto the parent template page, but wrapped inside <noinclude>…</noinclude>. The net result ought to be that the template has no effect on the /doc page (onlyinclude); spits out its contents (i.e. the category) on the parent template page; but won't affect whatever other page where the parent template gets transcluded (noinclude). However, this will affect both the category and the visual output, so it might be better then to simply add the category to the doc page directly. --Xover (talk) 11:05, 11 July 2019 (UTC)

Rant part 4...[edit]

https://en.wikisource.org/w/index.php?title=Page:History_of_Hudson_County_and_of_the_Old_Village_of_Bergen.djvu/45&diff=prev&oldid=9427799

Worth filing a Phabricator ticket for better inline images support? ShakespeareFan00 (talk) 12:35, 11 July 2019 (UTC)

Phab ticket raised - https://phabricator.wikimedia.org/T227767 Please comment.

ShakespeareFan00 (talk) 12:54, 11 July 2019 (UTC)

It seems to me that your edit to Page:History of Hudson County and of the Old Village of Bergen.djvu/45 is the correct way to handle such cases - "frameless" and "center" do not make sense for inline images. —Beleg Tâl (talk) 13:29, 11 July 2019 (UTC)
@ShakespeareFan00:I know that this is an old post but we were discussing the {{FIS}} template further on, perhaps you want to look at the change I made in the page mentioned above.

https://en.wikisource.org/w/index.php?title=Page:History_of_Hudson_County_and_of_the_Old_Village_of_Bergen.djvu/45&diff=next&oldid=9427799

By the way, this is my starting layout generated by AutoHotkey. From here on, I delete the non-applicable parameters and modify the rest.

{{FI
 | file         =
 | width        = 500px
 | cstyle       = margin-top:0px; margin-bottom:-5px
 | float        = left|right
 | margin-right = 7px
 | margin-left  = 7px
 | tstyle       = padding-top:.4em;  font-variant: small-caps; 
 | talign       = center
 | caption      =
}}

Ineuw (talk) 22:45, 11 July 2019 (UTC)

OCR button not working[edit]

I am having an issue in which the OCR button on the toolbar isn't working. I encountered this when I was proofreading Index:A History of Wood-Engraving.djvu. For some reason, it worked fine for the first few pages with text, but after that, it simply refused to generate a text layer for the other pages despite the words being clearly readable. Is there a fix for this? DraconicDark (talk) 14:32, 11 July 2019 (UTC)

[CC: Ineuw] @DraconicDark: I just checked in Safari and the old OCR button is non-functional there too. Checking the javascript console it is throwing an error:
[Error] Error: Syntax error, unrecognized expression: An error occurred during ocr processing: /tmp/52004_20706/page_0011.tif
	error (load.php:20:880)
	select (load.php:37:233)
	find (load.php:41:184)
	init (load.php:142:753)
	jQuery (load.php:2:505)
	hocr_callback (Script Element 1:594:825)
	fire (load.php:45:980)
	fireWith (load.php:47:174)
	done (load.php:126:628)
	(anonymous function) (load.php:130)
This indicates a server-side problem: the phetools hOCR tool is returning an error message and the local javascript here that is calling it is choking on the error.
The Google Vision-based OCR tool that you can enable in your preferences ("Development (in beta)" section) seems too work though, and is a decent workaround. --Xover (talk) 15:35, 11 July 2019 (UTC)

Rant part 5 (Scoring points...)[edit]

Page:How to Write Music.djvu/21 Here a {{float box}} is used to wrap the scoring elements, which would work if the Score tag provided span-based output. It currently provides a DIV based output (not unexpectedly) which means that in this page malformed HTML get's generated. I'm starting to wonder if many of the common floats and shoulders Wikisource contributors use, should really instead be local classes in the core Mediawiki styling for the site, like certain of the table classes I've authored recently. ShakespeareFan00 (talk) 18:51, 11 July 2019 (UTC)

It doesn't wrap the score, it's wrapping a {{c}} (div-based). That's the div-span-flip error. Using {{float box}}'s own align parameter allows to avoid this. Inductiveloadtalk/contribs 19:37, 11 July 2019 (UTC)
Thanks. Perhaps someone should start documenting Wikisource:Formatting howlers?
Related is the example in the {{FIS}} documentation here -Template:FreedImg/span/doc, That's also showing up as 'flipped' warning, and there the SCORE tag IS being placed directly into a SPAN ShakespeareFan00 (talk) 19:56, 11 July 2019 (UTC)
What I actually see (in Firefox for that example is :-
<span id="cSpan2" class="freedImg" style="display:block; width:100%;"><div class="mw-ext-score" data-midi="//upload.wikimedia.org/score/g/6/g69wg0c0dcu6sgx5cofnxhc1ag07m1n/g69wg0c0.midi" data-source="//upload.wikimedia.org/score/g/6/g69wg0c0dcu6sgx5cofnxhc1ag07m1n/g69wg0c0.ly"><img src="//upload.wikimedia.org/score/g/6/g69wg0c0dcu6sgx5cofnxhc1ag07m1n/g69wg0c0.png" alt="{ \clef bass \time 3/4 g,4 (b,4 [d4 f4 a4]) r4 \bar &quot;|.&quot; }" width="205" height="48"></div></span>
which is much more clearly malformed...
The actual invocation is :
{{FIS
 | type  = user
 | width = 50%
 | file  = <score>{ \clef bass \time 3/4 g,4 (b,4 [d4 f4 a4]) r4 \bar "|." }</score>
}}

There the Score extension is CLEARLY generating a DIV based wrapper isn't it? ShakespeareFan00 (talk) 19:56, 11 July 2019 (UTC)

@ShakespeareFan00:, Try {{FI}} instead of {{FIS}}? Remove the "S" from FIS and try it again. FI was written first, but it could not float, So, FIS was created with <span></span> instead of <div></div>.Ineuw (talk) 20:11, 11 July 2019 (UTC)
I've checked, in the equivalent documentation for {{FI}} which I suspect is the same documentation as {{FIS}} although written previously, the score example works without generating the warning. Next question would be how to put a simple score (typically a short extract) inline (which might need yet another Phabricator ticket...) There's an open ticket on Phabricator about converting lillypond to MusicXML but any kind of support for doing that is still in the very early stages of development.. ShakespeareFan00 (talk) 20:18, 11 July 2019 (UTC)
For that you'll need to identify a text which has a short extract inline, such that this feature would be necessary for proofreading that text correctly. —Beleg Tâl (talk) 20:48, 11 July 2019 (UTC)
Something like A Dictionary of Music and Musicians/French Sixth or A Dictionary of Music and Musicians/Dot which are inline in the mainspace, but aren't in the Page: namespace? As it works in the mainspace, I don't worry about what happens in the Page: namespace. Beeswaxcandle (talk) 05:16, 12 July 2019 (UTC)

Rant Part 6 (The clever men at oxford?)[edit]

{{Cite DNB|vb=yes|author={{DNB PWJ}}|title=Beranger, Gabriel (DNB00)|work=[[Dictionary of National Biography]]|volume=04|pages=322|url=http://en.wikisource.org/wiki/Beranger,_Gabriel_(DNB00)}}

Generates:

[[File:PD-icon.svg|12px|alt=|link=]]&nbsp;This article incorporates text from a publication now in the [[w:public domain|public domain]]:&nbsp;<span class="citation encyclopaedia"><div></div><p id="DNBfooterInitials" style="clear:both; text-align:right;">[[Author:Patrick Weston Joyce|P. W. J.]]</p> (1885). [http://en.wikisource.org/wiki/Beranger,_Gabriel_(DNB00) "Beranger, Gabriel (DNB00)"].  In [[Author:Leslie Stephen|Stephen, Leslie]]. ''[[Dictionary of National Biography]]'' <b>04</b>. London: Smith, Elder & Co. p.&nbsp;322.</span><span title="ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fen.wikisource.org%3ASpecial%3AExpandTemplates&rft.atitle=Beranger%2C+Gabriel+%28DNB00%29&rft.au=%3Cdiv%3E%3C%2Fdiv%3E%3Cp+id%3D%22DNBfooterInitials%22+style%3D%22clear%3Aboth%3B+text-align%3Aright%3B%22%3EP.+W.+J.%3C%2Fp%3E&rft.aulast=%3Cdiv%3E%3C%2Fdiv%3E%3Cp+id%3D%22DNBfooterInitials%22+style%3D%22clear%3Aboth%3B+text-align%3Aright%3B%22%3EP.+W.+J.%3C%2Fp%3E&rft.btitle=Dictionary+of+National+Biography&rft.date=1885&rft.genre=bookitem&rft.pages=322&rft.place=London&rft.pub=Smith%2C+Elder+%26+Co&rft.volume=04&rft_id=http%3A%2F%2Fen.wikisource.org%2Fwiki%2FBeranger%2C_Gabriel_%28DNB00%29&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span>

There's a DIV in a SPAN, but as this template is used on a LOT of pages, I didn't feel happy trying to attempt a fix. ShakespeareFan00 (talk) 00:20, 12 July 2019 (UTC)

Create a template named Template:SF00, copy and correct the original template's error. Then, use it as a test template on pages which are linked to the original. If the test template works well everywhere, then open a discussion in the Proposals section of the Scriptorium. Ineuw (talk) 01:20, 12 July 2019 (UTC)
Sounds of manic laughter as Sf00 is led away in a virtual strait-jacket, [:https://en.wikisource.org/w/index.php?title=Template%3ACite_encyclopedia&type=revision&diff=9437254&oldid=5167971] ONE misplaced line-feed. :lol :sigh :scowl ShakespeareFan00 (talk) 15:12, 13 July 2019 (UTC)
And it's that the DNB author initials {{DNB PWJ}} aren't a PURE span, they have code that generates the DIV. Is there an alternative template that should have been used?ShakespeareFan00 (talk) 15:22, 13 July 2019 (UTC)

Rant part 7[edit]

Page:Jacobite_broadside_-_Copy_of_the_right_honourable_Lord_Lovat's_letter,.jpg/1

The float left item should be centered, I thought setting a style would do this, but text-align seems to be inapplicable to spans? ShakespeareFan00 (talk) 11:40, 12 July 2019 (UTC)

Also note to other contributors, typically style= when supplied to a template doesn't have wrapping quotes like it would when being supplied directly to an HTML tag..ShakespeareFan00 (talk) 11:55, 12 July 2019 (UTC)

Rant Part 8 ( A Table of concerns...)[edit]

I cannot seem to find a way to generate this row without a warning about fostered content or the resultant transclusion being incorrect.

Template:Markup/row

As we other issues, I've REPEATEDLY said the way to PROPERLY solve this is to have a table syntax that supports proper continuations, but despite raising concerns there's been no further action taken on finding a STABLE long term solution. (sigh) ShakespeareFan00 (talk) 14:32, 13 July 2019 (UTC)

@ShakespeareFan00: Instead of complaining, ask for help, or take the initiative to read the history of the template. Template:Markup/row was originally imported from WP. So I replaced our version with the latest WP copy. At first glance, they look the same. Please try it because I don't know what it is for.Ineuw (talk) 01:09, 14 July 2019 (UTC)

Rant part 9 (Listing yet another concern!)[edit]

https://en.wikisource.org/w/index.php?title=Page:The_Boy_Travellers_in_the_Russian_Empire.djvu/268&oldid=9437291

Despite there being no whitespace (other than line feeds, Mediawiki seems unable to handle multiline content that's supplied to a SPAN based template in a clean way... Collapsing the whitespace made the error go away, but the parser should be much more robust than that? I thought I'd ask here if there is another less drastic way of doing this as opposed to collapsing ALL whitespace because Linter (if not the parser) seems to throw a fit, if it doesn't see exactly what it expects... ShakespeareFan00 (talk) 15:55, 13 July 2019 (UTC)

Use a a div-template.— Mpaa (talk) 18:58, 13 July 2019 (UTC)

That's what I figured as well, but as I said the parser should be more robust. ShakespeareFan00 (talk) 19:43, 13 July 2019 (UTC)

Page tools link in sidebar is broken[edit]

In the Page edit mode the sidebar TemplateScript/proofreading.js link in the "gear" icon (on right of the 'Page tools' title) is broken. Can someone fix this link and check if the contents of that page are still relevant? Ineuw (talk) 20:36, 13 July 2019 (UTC)

Rant part 10 ( Something that really SHOULDN'T have worked.)[edit]

I'm head-scratching... Something I did here worked... And it shouldn't have, as I understood the layout model concerned :(

Page:Ruffhead_-_The_Statutes_at_Large_-_vol_2.djvu/92

Perhaps another very experienced contributor can review what's going on here so I know why it worked when it did not previously? It would be nice to generalise this down a bit so it can be used elsewhere. I have a nasty feeling it's not stable though :( ShakespeareFan00 (talk) 23:02, 13 July 2019 (UTC)ShakespeareFan00 (talk) 23:12, 13 July 2019 (UTC)

Why do you think this should not have worked? This is exactly the solution I suggested to you the last two times you asked for help making it work, and it worked both those times. I also updated Template:Dropinitial#Technical notes with this suggestion last time you brought it up. —Beleg Tâl (talk) 11:01, 14 July 2019 (UTC)
Thanks, The tweak in this particular instance was to adjust the margins by the width, and to use the DIV based version of float-left, which I did not know existed.

That gets me thinking about sidenotes again.. ShakespeareFan00 (talk) 15:08, 14 July 2019 (UTC)

And I said it wasn't stable, but looking at User:ShakespeareFan00/sandbox ( fourth heading) , thanks to some template logic I wrote a while back, I've got the shift when it's transcluded. Next step would be the logic in a template like {{lrpaged}} to read the page number in mainspace and then I don't have to worry about left or right anymore. :)

...ShakespeareFan00 (talk) 15:30, 14 July 2019 (UTC)

Template:GHGterm[edit]

This was leaking a SPAN, I've re done the logic in a sandbox and would appreciate someone else reviewing the code and the testcases before it's hopefully swapped in? ShakespeareFan00 (talk) 16:24, 14 July 2019 (UTC)

@ShakespeareFan00: I took a look and found even your improved version needlessly complicated. I took a stab at simplifying while guaranteeing valid output, and as best I can tell it works as intended now. If you agree then feel free to update the live template. --Xover (talk) 08:30, 15 July 2019 (UTC)
In the original the wraping lang in the span is only applied if parameter en is supplied. In your version it was supplied regardless, which is not the original logic as I understand it. Resolved this in the sandbox and swapped it in. ShakespeareFan00 (talk) 08:50, 15 July 2019 (UTC)

Quoted paragraphs...[edit]

Page:Benezet's_A_caution_and_warning_to_Great_Britain_and_her_colonies.pdf/11

Here each line of the quote is precceded by a ` to mark each line of the quote.

My thought was that this could be styled to insert this with a CSS rule, but no such selector for the start of line exists.

Also some discussions on the #css IRC channel at freenode indicated that it could not currently be done in purely CSS, however a contributor there suggested a Javascript method might work. Would such an approach be feasible, or for simplicity do we just drop this archaic formatting? ShakespeareFan00 (talk) 20:21, 14 July 2019 (UTC)

I'm going to say that this is not something we reasonably can reproduce, nor something we should reproduce. Granted it sometimes obliges us to find an alternate formatting to convey the same information, but that's not usually been a big problem in my experience. We have all the usual typographic conventions at our disposal, including things like indentation and margins. The important factors are that it is clear and understandable for our readers, and that it reproduces the meaning of the original formatting (not its mere visual instantiation). --Xover (talk) 07:14, 15 July 2019 (UTC)
The "traditional" solution to this situation is to enclose the quoted section within <blockquote></blockquote> tags. Granted, the representation looks nothing like the running-left-quotes and maybe never will but at least the semantic structure is captured and for now that has always been regarded as "good enough." 114.78.171.144 07:38, 15 July 2019 (UTC)
Not only is not something we can "reasonably" reproduce, it's not something we should reproduce. Typesetters of printed works that use the device know what the line length will be on every page of their book and can insert the appropriate slug as required. Given we are reproducing works in a non-printed medium for multiple devices that use many different line lengths, the benefit of doing the work to make it behave is minimal (particularly as the situation where a quoted section goes across page breaks will be particularly messy to deal with in Javascript). The nearest equivalent in modern typography is to block indent the text and place a grey bar on the left margin. The suggestion of the IP to use blockquote tags is pretty close and there is a family of templates ({{quote}}) that allow for such that go over pages. I would expect each paragraph within the blockquote to begin with a quote mark and the final paragraph to terminate with one (as per long-established practice) even though they are set off. Beeswaxcandle (talk) 09:32, 15 July 2019 (UTC)
Which is what I eventually did . ShakespeareFan00 (talk) 10:13, 15 July 2019 (UTC)

Identifying Header and Footer in AWB[edit]

Hi all. I am just starting out using AWB on US Statutes at Large Vol. 33, Parts 1 and 2. I've successfully done some very simple search/replace of obsolete template calls, but now - no doubt preparing to trip for the first time over my new and exciting AWB shoelaces, I am being more ambitious! I would love to be able to insert the necessary elements for USStatHeader in the several hundred pages of these two documents. My problem is my ignorance of regex - I thought I could search for <noinclude>*</noinclude> to replace it with my USStatHeader string, but no dice. It then occurred to me that I need a text-layer means of differentiating between header and footer, anyway, which my initial approach would have failed to achieve. Is what I am trying to do possible? If there are any AWB wizards out there, if it's possible to use a search/replace control file whereby for a given page file name, it pastes the next (perfectly formed) line of wikitext from the input file into the header, that would be AWESOME. Thanks, and apologies if this is all an achingly basic question. CharlesSpencer (talk) 11:52, 16 July 2019 (UTC)

An empty header generally takes the form <noinclude><pagequality level="0" user="Beleg Tâl" /></noinclude>. I generally find it helpful to use https://regexr.com/ to build and test regexes that I will use in AWB. The CSVLoader plugin should be able to handle your search/replace control file requirement; see w:Wikipedia:CSVLoader/Find and replace for details. —Beleg Tâl (talk) 12:16, 16 July 2019 (UTC)
That sounds VERY interesting - thank you very much indeed. I shall report back! CharlesSpencer (talk) 12:51, 16 July 2019 (UTC)

The Poems of Henry Kendall[edit]

Would someone with access to HathiTrust be able to grab this scan for me? Thanks. —Beleg Tâl (talk) 19:04, 18 July 2019 (UTC)

@Beleg Tâl: Will this do? --Xover (talk) 22:07, 18 July 2019 (UTC)
@Xover: thank you! —Beleg Tâl (talk) 00:34, 19 July 2019 (UTC)

Inserting a literal asterisk (*)[edit]

I need to begin a paragraph with an asterisk. How does one keep it looking like an asterisk? Klarm768 (talk) 10:36, 19 July 2019 (UTC)

I found the answer... {{*}} embarrassed to admit I asked the question over a year ago. And had forgotten the answer. Klarm768 (talk) 10:57, 19 July 2019 (UTC)

Surprised by the structure of a URL and a blue link leading nowhere—is there something wrong?[edit]

Reviewing the External links at w:The Chaos, I opened https://en.wikisource.org/wiki/The_Chaos to find it is a redirect to: https://en.wikisource.org/wiki/Ruize-rijmen/De_Chaos

Out of editorial curiosity, I opened: https://en.wikisource.org/wiki/Ruize-rijmen/

And: https://en.wikisource.org/wiki/Ruize-rijmen

Both pages said: Wikisource does not have a text with this exact name

Also on Wikisource, clicking the link on the page of The Chaos/De Chaos resulted in the same message in a language from the Netherlands (nl), I trhink. So I opened https://nl.wikipedia.org/wiki/The_Chaos and a search for "Ruize" returned no instances. Google Translate could not translate that term. I don't edit on Wikisource much at all, so I was surprised by the structure of the URL and by a blue link that leads nowhere. There may be absolutely no issue here, but in case there is... Hey! Here's what I found odd!

All I can do is post here and probably not come back due to real-life limitations. I edit en.WP (including technical documentation), en.WT, en.C and occasionally other languages and projects. I mention my WM CV so you can maybe garner from this what an experienced editor might find odd on WS, but I did not check for an existing WS for WP editors page, like the one on WT. There's my data dump! Thanks in advance, Geekdiva (talk) 15:12, 19 July 2019 (UTC)

@Geekdiva: this is why it behaves this way:
  • nl:Ruize-rijmen is a book written in Dutch, which is why the link in the header of Ruize-rijmen/De Chaos points to the Dutch Wikisource.
  • The book nl:Ruize-rijmen has not yet been added to Dutch Wikisource, which is why it says (in Dutch) that this work does not exist.
  • The poem Ruize-rijmen/De Chaos is written in English, which is why this particular page is on English Wikisource instead of Dutch Wikisource.
  • The book nl:Ruize-rijmen is not in English, so the rest of the book should not be added to English Wikisource. This is why it says "Wikisource does not have a text with this exact name" when you go to en:Ruize-rijmen.
  • Finally, and this is the real issue: wikilinks that point to other wikis (including Dutch Wikisource) are always blue, even if the page does not exist on the other wiki. Links to nl:Ruize-rijmen are essentially redlinks, but they appear blue because nl:Ruize-rijmen is on a different wikisource.
Let me know if you have any other questions. —Beleg Tâl (talk) 15:51, 19 July 2019 (UTC)

Page:A_history_of_the_military_transactions_of_the_British_nation_in_Indostan.djvu/11[edit]

I'm asking for someone with experience to review the approach used on this page with {{sn-year}} before deploying it more widely.

I have concerns that the rendering may not be entirely stable. ShakespeareFan00 (talk) 22:58, 19 July 2019 (UTC)

And here I've found another problem, namely Template:Sn-year/sandbox that it seems to be next to impossible to actually emulate what the page numbering script is creating (in respect of dynamic layouts to fake the structure sufficiently to allow for testing of layouts in other than mainspace from a direct transclusion.
It would of course be nice if for once, someone actually sat down (independently of content work) and implemented a PROPER and FULLY DOCUMENTED explanation of what certain core Wikisource functionality ACTUALLY does, so that templates like {{sn-year}} and {{Fake layout}} can be implemented in a logical, consistent and reproducible way, and be used for thier intended purpose, but given the time available to a volunteer project like this, I don't see that happening with any priority. Instead there are various work-arounds, hacks and 'too clever by half' approaches, that aren't stable (including some I've written). This is NOT an approach sustainable in the long-term, in terms of maintainability.ShakespeareFan00 (talk) 23:26, 19 July 2019 (UTC)
Looks good to me —Beleg Tâl (talk) 12:47, 20 July 2019 (UTC)

Lilypond line width[edit]

In OAW vol 1 page 36 and OAW vol 8 page 433, lilypond is generating scores that are much wider than the rest of the layout: this magazine looks best if fixed-width elements are no wider than 600px, preferably 500px. Page 433 could be improved by breaking the score into three lines; is there a way to do that? The same could be done on page 36, or the lines could be horizontally compressed (there is no reason the notes have to be spaced out that much). Levana Taylor (talk) 23:44, 21 July 2019 (UTC)

@Levana Taylor: Poking around like a bull in a china shop, but I did take a stab. Maybe some further tweaking will get you the result you're after? As best I can tell there is no way to make the Score extension generate images of a given web-ish dimension, much less dynamically size them relative to the browser or web page. It is possible something can be achieved by wrapping the score tags in a template that imposes some sizing: it'd be hacky and inconvenient, but might actually work. If this is an issue you run into often then feel free to give me a ping and I'll look into it. --Xover (talk) 21:57, 22 July 2019 (UTC)
When I read the Lilypond manual and didn't see any way of forcing the lines to break, I thought I must have overlooked it, but if you didn't find it either, it must not be there. Your method of globally reducing the size of the output works, though. It forces the user to choose between long lines or else tiny font size for the lyrics. I think the best compromise is "line-width = 130\mm #(layout-set-staff-size 13" which fits inside 600px (although 120/12 fits into 500px, it's ridiculously tiny). Thanks! Levana Taylor (talk) 01:08, 23 July 2019 (UTC)

A Record of Education[edit]

There is a book, A Record of Education: The Schools and Teachers of Dedham, Massachusetts, that is now in the public domain and available on Google Books. It would be very helpful for my current project on Wikipedia if it was in Wikisource, but I am not as familiar with this wikiproject, have limited tech skills, and have no idea how to add it to Wikisource. Could someone please help? Thanks! --Slugger O'Toole (talk) 00:12, 23 July 2019 (UTC) PS - It is also in Internet Archive, if that helps. --Slugger O'Toole (talk) 00:18, 23 July 2019 (UTC)

@Slugger O'Toole: Step one is to upload it to Commons. I'll do that now for you. Step two is to make an index. Step three is to start transcribing. (Easier said than done.) Have you read Help:Adding texts yet? Do you have questions about that guide? —Justin (koavf)TCM 00:29, 23 July 2019 (UTC)
Thanks, Justin. I had not read that help page. I was looking at what I presume to be an older page and was a bit daunted. I have created the index page. I guess the next step is to proofread. Seems like it will take some time. I'd appreciate the help, if you're inclined to give it. If not, thanks for getting me this far! --Slugger O'Toole (talk) 02:55, 23 July 2019 (UTC)
@Slugger O'Toole: Happy to help but I'm too swamped to promise anything. :/ —Justin (koavf)TCM 03:36, 23 July 2019 (UTC)
@Slugger O'Toole: By the way, we don't transcribe stickers, hand-written notes, stamps, etc. that weren't a part of the original work. —Justin (koavf)TCM 03:42, 23 July 2019 (UTC)
@Slugger O'Toole: It seems that the original OCR layer is quite bad and unfortunately our OCR button has stopped working for some reason a short time ago. So I recommend you to enable Google OCR button in your Preferences/Gadgets. --Jan Kameníček (talk) 07:36, 23 July 2019 (UTC)

Chaucer's Works (ed. Skeat) Vol. II/Boethius Book I[edit]

Page numbering to the left with {{page break}} or {{pagebreak2}} is NOT compatible with {{block center}}.It would be NICE if someone eventually sat down and rewrote certain templates so that they have reliably predictable behavior regardless of where they are ACTUALLY used.

Other than stripping them out, I'd like a suggestion on how to get them to format as the original template intended? ShakespeareFan00 (talk) 21:15, 20 July 2019 (UTC)

Then don't use it. It is a very old template and it works for its tasks where it was designed to be used, block center came along later.

P.S. How about you stop the commentary of complaint? Keep things simple and they generally work fine. — billinghurst sDrewth 01:07, 21 July 2019 (UTC)

I am generally not happy taking out templates others have placed, but as I trust your technical expertise, I'll mention your above comment if someone queries my removal of 'incompatible' templates. ShakespeareFan00 (talk) 09:05, 21 July 2019 (UTC)
Is there a policy here about mass removal of 'incompatible' or nominally depreceated templates? ShakespeareFan00 (talk) 09:16, 21 July 2019 (UTC)
You and others, have previously suggested that before making certain types of changes, that I SHOULD consult more. If I don't ask about concerns when I can't find an obvious solution, then what do you suggest? You seem to be saying you would prefer a more neutral 'technical' request, in comparison to the percived venting that's sometimes happened. ShakespeareFan00 (talk) 09:30, 21 July 2019 (UTC)
In respect of the actual concern with the template "incompatibility" https://petscan.wmflabs.org/?psid=10179664 which is about 170 pages to check (most of which do not need any changes so possibly more like about 40-50 pages that need updating), any volunteers? ( the temporary solution is to convert |left to |hide.). A longer term re-design of the templates mentioned would be appreciated,

ShakespeareFan00 (talk) 11:10, 21 July 2019 (UTC)

A technical question arises, how does the PageNumber.js script get to get the page numbering to the side of the page consistently (I am wondering if it's a very specfic form of classing or style? Because if there was a way to arbitrarily call that code directly from mainspace, Could it be utilised by setting the relevant class and idents in {{Page break}} to get the desirable behaviour (of consistently left hand aligned page numbers)? I've not as far as I know had issues with block centered content and page numbers (generated) from a transcluded work vs trying to do it directly in Mainspace with {{page break}} As you are more familiar with the scripting code concerned, would it be possible to implement a way of calling it arbitrarily? ShakespeareFan00 (talk) 12:21, 21 July 2019 (UTC)
In PageNumber.js, all page numbers are listed before any of the text content, and each page number is manually positioned by the algorithm based on the calculated location of the transcluded content within the browser window. —Beleg Tâl (talk) 17:21, 21 July 2019 (UTC)
And is there any reason why that approach could not be used directly in mainspace? using Page break or Page break 2 to insert markers read by an algorithm? ShakespeareFan00 (talk) 14:00, 24 July 2019 (UTC)


I don't think it makes sense to use {{page break}} to simulate PageNumber.js on non-scan-backed works, and I would support removing all instances where it is used in this way. —Beleg Tâl (talk) 17:21, 21 July 2019 (UTC)

Little help?[edit]

Hi! Someone could help with the "Contends" and "List of images" from the book My Airships? I'd like to release each chapter when I finish each proofreading. Thanks, Erick Soares3 (talk) 17:55, 21 July 2019 (UTC)

@Erick Soares3: I took a stab at the ToC: here and here. Note in particular that I changed from roman to arabic numerals in the chapter subpage names. Looking quickly at the "List of images" it looks like the same approach would work there. There are, of course, also other ways to go about it, so please do not feel obliged to keep my changes if you prefer a different approach. --Xover (talk) 21:23, 22 July 2019 (UTC)
@Xover: Thanks! But I saw that something went wrong between page 11 and 12 (see My Airships). Have any idea? I will see what to do in the "List of images" - I'm still learning all that part of Wiki code. Erick Soares3 (talk) 21:34, 22 July 2019 (UTC)
@Erick Soares3: My apologies. It was that darn magic mystical {{nop}} that needs to be inserted in oftentimes seemingly random places. When we combine multiple separate pages, each containing wiki markup, into a single page with transclusion, it is always tricky getting the whitespace right for the markup where whitespace matters. For example inside a table, the "|-" that starts a new table row needs to start on a new line, but the transclusion removes the preceding newline because most of the time that page break occurs "within
a sentence". The "magic nop" template forces a new line there, which makes it work. This is about the fiddliest and arcane bits of wiki syntax you will have to care about. --Xover (talk) 22:05, 22 July 2019 (UTC)
Can I remind users that inside tables, that we should be using {{nopt}} (nop for tables) as it is <span> type. — billinghurst sDrewth 22:19, 22 July 2019 (UTC)
Thanks!! Erick Soares3 (talk) 22:26, 22 July 2019 (UTC)
I have never heard of {{nopt}} - smart idea. Could you perhaps fill out Template:Nopt/doc and update Template:Nop/doc so future editors will know about it? —Beleg Tâl (talk) 01:50, 24 July 2019 (UTC)

Adding missing pages to a file[edit]

I uploaded vol. 31 of Poet Lore from HathiTrust, but then I found out that some pages were missing. HathiTrust has one more copy, which has other problems (missing index pages), but it has got the pages that are missing in the uploaded file, i. e. pages no. 328–329 and 371–374. Could someone who has got the needed software extract these pages from the other copy and add them to the uploaded file?

Thanks very much! --Jan Kameníček (talk) 21:36, 22 July 2019 (UTC)

@Jan.Kamenicek: I don't have tools for working with PDF, but I can probably generate a new composite DjVu file for you. It'd also get a completely new text layer which I cannot guarantee is as good or better than the existing one. In my limited experience it's as good or better than the alternatives but this will depend strongly on the work in question as well as a bit on individual preference. But if those caveats are acceptable to you I can take a stab at it. --Xover (talk) 11:38, 23 July 2019 (UTC)
@Xover:I do not insist on PDF, I prefer it mostly because it is usually easier to handle for me. So if you make a DJVU composite, it will help. Thanks very much! --Jan Kameníček (talk) 11:50, 23 July 2019 (UTC)
@Jan.Kamenicek: Done: File:Poet Lore, volume 31, 1920.djvu. Please check that I didn't mess up anything with the page doctoring.
I would also be very interested in your impressions of the OCR quality. Both overall; if there are specific features that are handled better or worse than expected; and whether there are particular pages where it does unexpectedly well or falls down completely. The OCR here is performed using different software than IA and that used in both the OCR button and the Google OCR button, and OCR results are to a certain degree dependent on the preprocessing of the page images (which is obviously different here), so I'm interested in such feedback to get a sense of how well my tools are doing compared to the alternatives (and it may be that there is further pre- and post-processing I can do to improve the results).
No need to make a study of it, but if you happen to notice anything while working on it I'd appreciate a note on my talk page. --Xover (talk) 15:45, 24 July 2019 (UTC)
Perfect, thank you, you have helped me very much again! For more, I am going to write on your talk page. --Jan Kameníček (talk) 17:17, 24 July 2019 (UTC)

OCR failed and the button is frozen[edit]

On several pages, including this, I clicked on OCR in edit mode, and nothing happened. The old text remained. So, I saved the page and the text is gone. Ineuw (talk) 04:16, 20 July 2019 (UTC)

I tried using my alternate account and it was the same. Unfortunately, an unregistered user has no access to the OCR button.Ineuw (talk) 04:23, 20 July 2019 (UTC)

Emptied the vector.js and .css files and repeated the OCR action . The result is the same as with the files installed. — Ineuw (talk) 06:09, 20 July 2019 (UTC)

I have the same problem. --Jan Kameníček (talk) 06:14, 20 July 2019 (UTC)
@Ineuw, @Jan.Kamenicek: See #OCR button not working above. This is a server-side issue with Phe's OCR tools: the javascript gadget that implements the OCR button here calls a service on the toolserver that in turn attemps to perform OCR on the page requested, and that service is choking on something in certain DjVu files and returning an error message to the javascript gadget here. Since the gadget here doesn't specifically handle that error it just gets logged in the web browser's "Javascript Console" and the script just terminates (which looks like "nothing happened" to the user).
The quickest workaround is to just enable the Google OCR gadget in your preferences and use that. If it produces results that are unusable (it usually does at least almost as well as the old OCR gadget in my experience) it's also possible we can regenerate the whole DjVu file with a text layer generated by Tesseract 4 (Phe's tool uses Tesseract 3, and Google's uses the Google Vision API). It depends entirely on the work, how many pages are affected, whether original scan images are available, and so forth, whether it's worth doing the not-overwhelming but not-quite-trivial amount of work involved. For this particular work it doesn't seem obvious that regenerating the DjVu would produce any better results than the existing OCR text layer, but if you would like to test the results I'd be happy to try it. --Xover (talk) 09:04, 20 July 2019 (UTC)
@Xover:, Should I file a bug report? — Ineuw (talk) 09:49, 20 July 2019 (UTC)
@Ineuw: Phe isn't active on-wiki or on Phabricator, so it'd probably have to be at Github. --Xover (talk) 10:13, 20 July 2019 (UTC)
I am not experiencing the problem with a .djvu, but with a .pdf file. It has got an OCR layer, which is unfortunately quite bad, and so are the results with the Google gadget :-( I hope the OCR button will be repaired soon... --Jan Kameníček (talk) 16:40, 20 July 2019 (UTC)
I just checked and it's the same error, so whatever the issue is it affects both DjVu and PDF files. --Xover (talk) 18:37, 20 July 2019 (UTC)

┌─────────────────────────────────┘

@Xover: Thanks again for your kind help. Unfortunately, Phe's Github activity and his activity on French WS, ceased two-three years ago. I don't know what is Phabricator's policy in such a case, so I will post the question in their community forum. Also noticed a bug report about the .pdf scanner. task T224355 — Ineuw (talk) 20:24, 20 July 2019 (UTC)

The OCR gadget is an inseparable part of my work with the proofread extension and I am really surprised that its maintenance depends on one particular person... That is not good. --Jan Kameníček (talk) 06:55, 22 July 2019 (UTC)
I have announced the problem at phabricator. Please add there any relevant information that I missed. Thanks. --Jan Kameníček (talk) 13:46, 24 July 2019 (UTC)
It seems to work. — Ineuw (talk) 04:53, 25 July 2019 (UTC)
I have just tried it at Page:Magdalen by J S Machar.pdf/106 and it does not :-( --Jan Kameníček (talk) 06:26, 25 July 2019 (UTC)
Just tested it again, and it now doesn't work for me as well. Wish I could track down the version of 04:35, 25 July 2019 (UTC). — Ineuw (talk) 18:37, 25 July 2019 (UTC)

Adding to Wikisource[edit]

Hi there,

I made a translation into English from German of the poem "Wandere!" by Heinrich Heine. A user Huon (administrator of Wikipedia) suggested I contacted the Wikisource to inquire if I possibly should have this translation added to the Wikisource. That is why I am writing. I visited "Wandere!" page ( https://en.wikisource.org/wiki/Wandere! ) on Wikisource but I am not quite sure how to do all this (adding the text, should it be just a translation or the original poem in German too, etc.). The poem itself and the translation of it is currently on English Wikipedia Heinrich Heine page ( https://en.wikipedia.org/wiki/Heinrich_Heine ) under the heading "Wandere!".Sergeismart (talk) 16:13, 23 July 2019 (UTC)

@Sergeismart: Danke, we do welcome translations, as long as you agree to freely license them. In the {{header}} template that begins the work, include yourself under the translator field and make sure to add the appropriate copyright tag at the bottom. It may be something like this: {{translation licence | original = {{PD-old}} | translation = {{CC-BY-SA-3.0}}}}. See {{translation license}} for more on that. Then, add a link to it to Author:Christian Johann Heinrich Heine and it seems like you're all set. I look forward to it being added here. —Justin (koavf)TCM 18:26, 23 July 2019 (UTC)
Hey, Justin (koavf), will you check it out here - https://en.wikisource.org/wiki/Wandere! - if I did more or less fine (I mean if all spaces are filled correctly, etc.). And by the way I will appreciate your thoughts on the translation itself (if you have a spare second to read through it). Thanks.
Sergeismart (talk) 20:07, 23 July 2019 (UTC)
Ja, meine Duetsche nichte ist gut but I'll take a look. Odd about the translation notes below, because we definitely do have locally-hosted translations that are not in that namespace and that use the standard header template. —Justin (koavf)TCM 21:53, 23 July 2019 (UTC)
@Koavf: Independently published translations (like other independently published works) go in mainspace and use {{header}}. User-generated translations go in Translation namespace and use {{translation header}}. —Beleg Tâl (talk) 01:40, 24 July 2019 (UTC)
@Beleg Tâl: We do, in fact, have local pages that are not in the Translation namespace like Bible (Wikisource)/2 Chronicles. Likely an error but true nonetheless. —Justin (koavf)TCM 01:51, 24 July 2019 (UTC)
@Koavf: yes, that's an error, and thanks for identifying it. —Beleg Tâl (talk) 01:54, 24 July 2019 (UTC)
@Beleg Tâl: Lots more examples: Category:Wikisource translations of works in Thai. Not sure how interested you are in fixing them all but there are several dozen. —Justin (koavf)TCM 02:00, 24 July 2019 (UTC)
I've taken care of Category:Wikisource translations up to about P so far. —Beleg Tâl (talk) 02:12, 24 July 2019 (UTC)
I will just add that original translations by Wikisource contributors (unlike published translations)
For an example see Translation:Absolute.
If you have any further questions, do not hesitate to ask. And welcome at Wikisource :-) --Jan Kameníček (talk) 20:17, 23 July 2019 (UTC)
I just added " Category:Wikisource translations " at the bottom of an edit, couldn't do it through adding "Translation header" in the beginning of an edit (for some reason it didn't go through, it went very well though with just a "header" template). Hope now it is more or less fine. Enormous thanks for your help.
Sergeismart (talk) 20:56, 23 July 2019 (UTC)
@Sergeismart: I have made the following fixes:
Beleg Tâl (talk) 21:23, 23 July 2019 (UTC)
@Beleg Tâl: I was looking at other works in the translation namespace and it seems to me that the prevailing custom is to use the translated (English) name of the work in the name of the page after "Translation:" --Jan Kameníček (talk) 21:44, 23 July 2019 (UTC)
@Jan.Kamenicek: It appears to be at the discretion of the translator(s) what title they want to give their translation. —Beleg Tâl (talk) 01:40, 24 July 2019 (UTC)

Hey, Beleg Tâl, I greatly appreciate it! No need to add myself as an author of a translation into the "translation license", right? Just asking cause User:koavf told me previously to include myself in the "translator" field. Thanks again. Sergeismart (talk) 21:51, 23 July 2019 (UTC)

@Sergeismart: The {{translation license}} template is for license tags, not for authorship credits. User-submitted translations, like Wikipedia articles, are collaborative projects, so each edit is credited individually on the page history page instead of in the header. —Beleg Tâl (talk) 01:40, 24 July 2019 (UTC)
@Beleg Tâl: Thanks for your response and for your help. It is greatly appreciated. - Sergeismart (talk) 11:39, 24 July 2019 (UTC)
@Sergeismart: Two more things: (1) The author's name is not part of the poem text, and so should not be included in the poem or translation. The original certainly doesn't have it there. (2) There is no reason to italicize the entire poem or its translation. The original is not italicized. --EncycloPetey (talk) 18:25, 25 July 2019 (UTC)

Section Labels and known problems[edit]

I have started publishing pages, but not transcluding any of them yet. I see in Help:Transclusion that "Use of letters and numbers is usually a recommendation, and other extended characters may cause some issues when transcluding." Section Labels published so far contain the following characters: underscore, hyphen, colon, ampersand, and period (_ - : & .) I am hoping that someone has used these without problems. Or that someone can attest to having used other non-alpha, non-numeric characters with impunity?

I need to decide whether I should I start over and republish all the pages done so far. I have over 25000 Section Labels yet to be inserted. ¯\_(ツ)_/¯ Klarm768 (talk) 21:07, 20 July 2019 (UTC)

In my humble opinion, just use a character and a number, and without space. In this manner, enclosing it in quotes is superfluous. In my scheme of things I use the following syntax. For the ending section "E" = End and "289" equals djvu page number and "B" = Begin of next section. Do not use page numbers, they can be either missing or duplicated. Djvu numbers are always unique.
<section begin=E289 />
<section end=E289 />

and for the second 

<section begin=B289 />
<section end=E289 />

— Ineuw (talk) 00:41, 21 July 2019 (UTC)

I have not found that to be a useful process for biographical works as you have to track too many things, and too many possibilities for mistakes and omissions. I have found it significantly more helpful to use a section name that matches the article name (subpage) and for the article to match the identifying component. You will see that approach in many of our biographical works (though noting that in have been involved in most).

This also enables a quick and easy transclusion process, as I have two sidebar scripts that insert things like

{{#tag:pages||index={{subst:BASEPAGENAME}}.djvu|from=|to=|fromsection={{subst:SUBPAGENAME}}|tosection={{subst:SUBPAGENAME}}}}

{{#tag:pages||index={{subst:BASEPAGENAME}}.djvu|include=|onlysection={{subst:SUBPAGENAME}}}}

which means that if you have a ToC to work from then you are just inserting page numbers (first example where it spread over multiple pages), or one page number, when the article is contained within a page. Noting that this method as it can have spaces means you need to wrap the section name within quotes in the Page: ns.— billinghurst sDrewth 00:55, 21 July 2019 (UTC)

I guess that my projects are easy because having two sections on the same page is very rare. — Ineuw (talk) 06:48, 21 July 2019 (UTC)
Thank you both for your thoughts... although I'm a bit uncertain whether I rightly untangle the comments. I have revised 689 section labels to contain two "words"... entirely alpha-numerics. I do not understand whether there is additional advantage to truncating to a single "word" but I want to understand before resuming.

The work (Imperial Dictionary of Universal Biography) is a three volume set comprising 3940 page images. The 3672 pages-to-publish I have assigned into 25,740 sections, using a spreadsheet. There are 256 "signatures." Within my personal dissection I assign these "signatories" to 240 "identities" or "Contributors." This work has no de facto ToC. My sequencing spreadsheet is as close as probably ever will exist. I presume it is not eligible to be published with the IDUB, but it might have a usefulness in transclusion. I do not grasp the reference to "sidebar scripts," but I like the idea of facilitating transclusion. My background is not in computers. My mental-model is a mail-merge involving a "namespace template letter" into which fields are assigned and populated from each row of the spreadsheet to create templates to paste for transclusion. I'm sure that there are sophisticated methods but I work with the tools I have. Klarm768 (talk) 21:21, 21 July 2019 (UTC)

@Klarm768: Which project(s) are you referring to? — Ineuw (talk) 19:10, 23 July 2019 (UTC)
@Ineuw: I'm not sure what the word "project" means in your question's context. If there is an "official" Wikisource project regarding "Imperial Dictionary of Universal Biography" I do not know of its existence. As far as I know, billinghurst has created a few pages at the beginning of Volume 1 such as "List of Contributors" and other preparatory pages. Otherwise, as far as I know, I am the only person who has ever transcluded any portion. That occurred due to quest to track down as-complete-as-possible-works of James Frederick Ferrier. I choose to pursue the entire work. My reasons are personally motivated... but available on request.

Whether nobody else would choose to make it a project is not my concern. As far as a Wikisource IDUB project... which, if there were one, would have to mean I am deemed unwelcome/uninvited. I have spent many hundreds of hours getting the entire text in fair-copy-MS-Word... getting every entry & article sequenced and titled... getting the contributors disambiguated to considerable degree (actually one of the most confusing aspects). I would prefer to have a Wikisource-pilot steering my trireme... so many Scyllas and Charybdises. (Perhaps the only one who attempted the role got in trouble because of my errors... choices made before I ever discovered that Ferrier contributed to IDUB.) Besides... helping me with a project of 5,845,911 word-count is not Wikisource priority. In a year or two I hope to have IDUB in fair-copy-Wikisource and transcluded. The Wikisourse Mysteries are reserved for the initiates. Klarm768 (talk) 21:17, 23 July 2019 (UTC)

For what it's worth, there is one page of IDUB with 38 Sections on a single page. There are hundreds of redirects & biographies with fewer syllables than the subject's name. Klarm768 (talk) 21:24, 23 July 2019 (UTC)
@Klarm768:If there is more than 1 section on a page then you must use user:billinghurst's method. As for "project" I meant the title, just to take a look. — Ineuw (talk) 07:57, 24 July 2019 (UTC)
@Ineuw: I'm not sure what the phrase "user:billinghurst's method" means in your context. I have already gone back and converted all Section Labels to a single 'word' of alpha-numerics. The numeric portion is based on the image# & and the alpha portion reflects/preserves the sort order of the Sections. Is that the "method?" I scrolled through the "user:billinghurst" site but found nothing I could otherwise apply myself. I have previously transcluded articles from pages with multiple sections on a page. Does that mean I used the method" at that time? Or is the "method" something new in the past 18 months?

BTW, I do appreciate your taking time to respond. Hopefully I will eventually have more comprehension and fewer confusions. Klarm768 (talk) 15:22, 24 July 2019 (UTC)

We use the word project to collectively to describe major transcription efforts, be it formal or informal, though usually something that sits within Wikisource:Projects. Ineuw has done a lot of work within PSM and I have done work within DNB and other works within Wikisource:WikiProject Biographical dictionaries. In PSM there is usually an end of one and start of another article on a page, hence a rhythmic simpler use of sections. Whereas a biographical work like Index:The Dictionary of Australasian Biography.djvu or Index:Men-at-the-Bar.djvu can have many multiple sections. — billinghurst sDrewth 15:39, 24 July 2019 (UTC)
@Billinghurst: Thank you for your input. As I'm sure you are aware, Imperial Dictionary of Universal Biography has no ToC of its own. Is it conceivable that my Section-sequenced spreadsheet could be adapted (eventually) to generate the "records" to populate transclusion data. The Indexed Images are PDF rather than DJVU. Despite repeated attempts, I could not upload the entire Volume 3 in one piece, so I settled for making it into Volume 3a & 3b. Have I compromised automating the transclusion process? Klarm768 (talk) 20:14, 24 July 2019 (UTC)

@Klarm768: None of that changes my commentary about the preferred means to label sections with the resulting (subpage) article name. With regard to

  • the name list that you have, if you dump it somewhere as a text list, one name per line, I will convert it into a linked list for you, that is an easy task. The change that we make is to make it overt that OUR table of contents is not part of the publication, it is our generation. Men-at-the-Bar, Alumni Oxonienses, etc. are all in that boat.
  • DjVu vs PDF, again no issue, beyond DjVu has some advantages for our work
  • reupload as a split file, again no issue, the transclusion will care not, and as I suggested about ignoring volumes for your presentation, it makes no difference.

billinghurst sDrewth 22:02, 24 July 2019 (UTC)

┌─────────────────────────────────┘
@Klarm768: Some additional comments.

  • If your material is in spreadsheet format it can easily be used to create a ToC. You can create a ToC in the main namespace, as it was done in PSM. I don't think that its against the rules of WS if one adds relevant material, which does not exist in the original. The rule is not to change the original itself when proofreading.
  • In reference to section tags, you should familiarize yourself with billinghurst's method of sectioning the text. I think that the second option is the simpler. If help is needed, just ask.
  • If the text is in MS Word format, there are people who use it for editing, spell checking, and then copying and pasting as plain text.
  • Finally, "Seeing is believing". Create a couple of pages and ask for input here until you get up to speed. — Ineuw (talk) 21:46, 24 July 2019 (UTC)
@Billinghurst: @Ineuw: If it would be prudent to perform a test batch on an IDUB subset I could make X-Y-Z available soon. When inductiveload helped with a ToC for Institutes of Metaphysics we used pastebin.com and I exported a delimited text file. I presume I still can use that when the time comes. The columns (fields) in my spread sheet are entitled thus:

Volume# | Image# | Page# | Entry-Sequence per page | ABC | Contributor# | Contributor's Text-Signature | * | Title of Entry | word count | Disambiguation/Clarification | SectionLabel (which is built from Image#&Sequence)

I can arrange or reorder to your specifications. Yes, I have "Word Counts" on 25,740 sections and assorted clarification errata which I hoped to insert into the "notes" area at transclusion. Contributor# is my creation, an assigned number signifying the sequence in which a contributor-signature is first observed in IDUB. Then if a new signature is discovered which is defensibly thought to be the same contributor I assign that signature to the existing Contributor#. I try to include the reasoning behind that assignment in the Disambiguation/Clarification field. The * field is for IDUB biography titles whose names are preceded by * signifying the subject was thought to be alive. This indicator is nowhere explained on any page of IDUB but is findable in the IDUB advertisements in other books.

I have a whole other spreadsheet upon which I have researched all the contributor Signatures and IDUB "Lists of Contributors" and wherein I pursue the disambiguation process. I don't know if that can be found useful, but it exists. Klarm768 (talk) 11:29, 25 July 2019 (UTC)
Just go ahead and do a test page or two according to your plan. A Wikisource test page is = 1,000 words in the Scriptorium. — Ineuw (talk) 18:32, 25 July 2019 (UTC)
@Ineuw: I shall presume that you mean right here. Klarm768 (talk) 14:09, 26 July 2019 (UTC)
@Klarm768: Moved sample text to User:Klarm768/Sandbox01. — Ineuw (talk) 15:26, 26 July 2019 (UTC)

Quality differences between PDF and DjVu[edit]

Following on from this thread

Hmm. This is odd. The OCR text showing in the Page: namespace here is pretty poor; but when I look at the original PDF and DjVu files at IA the OCR text looks just fine. I can even copy from the PDF into a text editor and get much better quality than what appears online here. So I uploaded copies of both files locally here (PDF, DjVu) and checked the same page in both. This is the result:

PDF
OF DEDHAM, MASSACHUSETTS

7

Jno BuUard, Robt. Grossman, Hen Wilson, Jno N[ewton], Edw. Colver. Hen. Smith, Nath Colborne, Nath. Aldus, Hen Phillips, Sam^
Morse,

Dan Morse, Jno. Morse, Jos. Kingsbury, Jno. Dwite, Lamb.
Kemp, Edw. Richards, Tho. Leader, Geo. Bearstowe,

G[enery], Edw.

Jonath. Fairbanks,

Jno Frarey,

Eli.

Mich Powell, Mich Metcalfe

juno'^,

Jno Metcalfe,

Lusher, R[obt] Hinsdell, Pet. Woodward, Jno Guyle,

Rich. Evered, Robt. Gowinge, &ce.

The

said Inhabitants, taking into Consideration the great necesitie

some means for the education of the youth in o^ s'd
Towne, did with an unanimous consent declare by voate their willingness to promote that worke, promising to put too their hands to provide
maintenance for a Free Schoole in our said Towne. And farther did
resolve and consent, testifying it by voate, to rayse the summe of
Twenty pounds p annu, towards the maintaining of a Schoole M^ to
keep a free Schoole in our s'd Town.
of providing

And

and consent to betrust the s'd 2(d£ per annu
Towne, formerly set apart for publique use, into
the hand of Feofees to be presently chosen by themselves, to imploy the
sd 20;^, and the land afors'd, to be improved for the use of the said
Schoole that as the profits shall arise from the said land, every man
may be proportionably abated of his some of the s'd 20£ aforesaid,

&

also did resolve

certain lands in o^

:

freely to be given to the use aforesaid.

have power
land

:

make

to

And

y* y® said

Feofees shall

a Rate for the necesary charg of improving the s'd

they giving account thereof to the Towne, or to those

whom

they

John Hunting, E^^"^, Eliazer Lusher, Francis ChickerJohn Dwight & Michael Powell, are chosen Feofees and betrusted

should depute.
inge,

in the behalf of the school as afore said.

The school thus
was designed

established, to be

managed by Feoffees,

to continue seven years, as will appear in the

following record relating to the training ground
1644. 4^

12°^*^.

:

Granted to the Feofees for the free schoole

in

Ded-

ham for the use of the s'd schoole a parcel of the Training ground
much as shall be set out to them by the Towne, which said p'cel

so
is

granted from this present day unto the last day of the eighth month

which shall be in the year 1650.
Hen. Phillips deputed to set out the

Hen. Chickering,
s'd parcell of

Eli.

Lusher

Land above

said.

&


DjVu
OF DEDHAM, MASSACHUSETTS 
7 
Jno BuUard, Robt. Grossman, Hen Wilson, Jno N[ewton], Edw. Col- 
ver. Hen. Smith, Nath Colborne, Nath. Aldus, Hen Phillips, Sam^ 
Morse, Dan Morse, Jno. Morse, Jos. Kingsbury, Jno. Dwite, Lamb. 
G[enery], Edw. Kemp, Edw. Richards, Tho. Leader, Geo. Bearstowe, 
Jonath. Fairbanks, Mich Powell, Mich Metcalfe juno'^, Jno Metcalfe, 
Jno Frarey, Eli. Lusher, R[obt] Hinsdell, Pet. Woodward, Jno Guyle, 
Rich. Evered, Robt. Gowinge, &ce. 
The said Inhabitants, taking into Consideration the great necesitie 
of providing some means for the education of the youth in o^ s'd 
Towne, did with an unanimous consent declare by voate their willing- 
ness to promote that worke, promising to put too their hands to provide 
maintenance for a Free Schoole in our said Towne. And farther did 
resolve and consent, testifying it by voate, to rayse the summe of 
Twenty pounds p annu, towards the maintaining of a Schoole M^ to 
keep a free Schoole in our s'd Town. 
And also did resolve and consent to betrust the s'd 2(d£ per annu 
& certain lands in o^ Towne, formerly set apart for publique use, into 
the hand of Feofees to be presently chosen by themselves, to imploy the 
sd 20;^, and the land afors'd, to be improved for the use of the said 
Schoole : that as the profits shall arise from the said land, every man 
may be proportionably abated of his some of the s'd 20£ aforesaid, 
freely to be given to the use aforesaid. And y* y® said Feofees shall 
have power to make a Rate for the necesary charg of improving the s'd 
land : they giving account thereof to the Towne, or to those whom they 
should depute. John Hunting, E^^"^, Eliazer Lusher, Francis Chicker- 
inge, John Dwight & Michael Powell, are chosen Feofees and betrusted 
in the behalf of the school as afore said. 
The school thus established, to be managed by Feoffees, 
was designed to continue seven years, as will appear in the 
following record relating to the training ground : 
1644. 4^ 12°^*^. Granted to the Feofees for the free schoole in Ded- 
ham for the use of the s'd schoole a parcel of the Training ground so 
much as shall be set out to them by the Towne, which said p'cel is 
granted from this present day unto the last day of the eighth month 
which shall be in the year 1650. Hen. Chickering, Eli. Lusher & 
Hen. Phillips deputed to set out the s'd parcell of Land above said. 

OCR button
OF DEDHAM, MASSACHUSETTS 7

Jno Bullard, Robt. Crossman, Hen Wilson, Jno N[ewton], Edw. Col-
ver, Hen. Smith, Nath Colborne, Nath. Aldus, Hen Phillips, Sam’
Morse, Dan Morse, Jno. Morse, Jos. Kingsbury, Jno. Dwite, Lamb.
G[enery], Edw. Kemp, Edw. Richards, Tho. Leader, Geo. Bearstowe,
Jonath. Fairbanks, Mich Powell, Mich Metcalfe juno", Jno Metcalfe,
Jno Frarey, Eli. Lusher, R[obt] Hinsdell, Pet. Woodward, Jno Guyle,
-Rich. Evered, Robt. Gowinge, &ce. ~

The said Inhabitants, taking into Consideration the great necesitie
of providing some means for the education of the youth in o' s’d
Towne, did with an unanimous consent declare by voate their willing-
ness to promote that worke, promising to put too their hands to provide
maintenance for a Free Schoole in our said Towne. And farther did
resolve and consent, testifying it by voate, to rayse the summe of
Twenty pounds p annu. towards the maintaining of a Schoole MT" to
keep a free Schoole in our s’d Town.

And also did resolve and consent to betrust the s’d 20£ per annu
& certain lands in o° Towne, formerly set apart for publique use, into
the hand of Feofees to be presently chosen by themselves, to imploy the
sd 204, and the land afors’d, to be improved for the use of the said
Schoole: that as the profits shall arise from the said land, every man
; may be proportionably abated of his some of the s’d 20£ aforesaid,
freely to be given to the use aforesaid. And y* y® said Feofees shall
have power to make a Rate for the necesary charg of improving the s’d
land: they giving account thereof to the Towne, or to those whom they
should depute. John Hunting, E’", Eliazer Lusher, Francis Chicker-
inge, John Dwight & Michael Powell, are chosen Feofees and betrusted
in the behalf of the school as afore said.

The school thus established, to be managed by Feoffees,
was designed to continue seven years, as will appear in the
following record relating to the training ground :

1644, 44 12™°, Granted to the Feofees for the free schoole in Ded-
ham for the use of the s’d schoole a parcel of the Training ground so
much as shall be set out to them by the Towne, which said p’cel is
granted from this present day unto the last day of the eighth month
which shall be in the year 1650. Hen. Chickering, Eli. Lusher &
Hen, Phillips deputed to set out the s’d parcell of Land above said.
�
Google OCR
OF DEDHAM, MASSACHUSETTS
7
Jno Bullard, Robt. Crossman, Hen Wilson, Jno N[ewton], Edw. Col-
ver, Hen. Smith, Nath Colborne, Nath. Aldus, Hen Phillips, Sam1
Morse, Dan Morse, Jno. Morse, Jos. Kingsbury, Jno. Dwite, Lamb.
G[enery], Edw. Kemp, Edw. Richards, Tho. Leader, Geo. Bearstowe,
Jonath. Fairbanks, Mich Powell, Mich Metcalfe juno", Jno Metcalfe,
Jno Frarey, Eli. Lusher, R[obt] Hinsdell, Pet. Woodward, Jno Guyle,
Rich. Evered, Robt. Gowinge, &ce.
The said Inhabitants, taking into Consideration the great necesitie
of providing
Towne, did with an unanimous consent declare by voate their willing-
ness to promote that worke, promising to put too their hands to provide
maintenance for a Free Schoole in our said Towne
some means for the education of the youth in oF s'd
And farther did
resolve and consent, testifying it by voate, to rayse the summe of
Twenty pounds p annu. towards the maintaining of a Schoole Mr to
keep
a free Schoole in our s'd Town.
And also did resolve and consent to betrust the s'd 20£ per annu
& certain lands in or Towne, formerly
the hand of Feofees to be presently chosen by themselves, to imploy the
sd 20, and the land afors'd, to be improved for the use of the said
Schoole: that as the profits shall arise from the said land, every man
may be proportionably abated of his some of the s'd 20 aforesaid,
freely to be given to the use aforesaid.
have power to make a Rate for the necesary charg of improving the s'd
land: they giving
should depute. John Hunting, Eldr, Eliazer Lusher, Francis Chicker-
inge, John Dwight & Michael Powell,
in the behalf of the sch0ol as afore said.
set apart for publique use, into
And yt ye said Feofees shall
or to those whom they
account thereof to the Towne,
are chosen Feofees and betrusted
The school thus established, to be managed by Feoffees,
designed to continue seven
following record relating to the training ground:
will appear in the
was
years,
as
1644. 4d 12mo, Granted to the Feofees for the free schoole in Ded-
ham for the use of the s'd schoole a parcel of the Training ground
much as shall be set out to them by
SO
e Towne, which said p'cel is
granted from this present day unto the last day of the eighth month
which shall be in the year 1650.
Hen. Chickering, Eli. Lusher &
Hen. Phillips deputed to set out the s'd parcell of Land above said.

The immediate conclusion is that the best result comes from the OCR button, followed by the DjVu, followed by Google OCR, and with the PDF dead last. But since the text looks fine in the PDF locally, this means the problem must actually be the function that extracts the text from the PDF on-wiki!

I haven't done systematic testing of pages in this work or across works, but the results above are quite suggestive. For one it means we should very strongly prefer the DjVu to the PDF as a source. It also justifies the reliance on the OCR button for those who routinely use that. And it raises the question of what the difference is between the OCR button and the OCR at Internet Archive. The OCR button uses Tesseract, but IA uses a commercial product if I'm not mistaken. It would be interesting to compare the text produced by the OCR button with that produced by the latest Tesseract directly to see if the results are comparable. --Xover (talk) 11:06, 23 July 2019 (UTC)

Hm, that is very interesting, thanks for sharing this info. As for better OCR with DJVUs than with PDFs: besides various problems with DJVU format (common browsers cannot read it), e. g. HathiTrust does not offer scans in DJVU, only in PDF :-/ Many contributors are able to download a PDF and upload it to Commons, but they are not always able to convert it to DJVU prior uploading. So the best solution is not to stop using PDFs, but to make Wikimedia projects environment friendlier towards them. --Jan Kameníček (talk) 11:21, 23 July 2019 (UTC)
I meant, when you have both DjVu and PDF available, you should always prefer the DjVu. Creating a new DjVu when one is not already available is a fiddly, obscure, and highly technical task: I've created my own tooling that makes it somewhat bearable, but it's not something I would suggest anybody else tries to do unless they are otherwise undaunted by such work. --Xover (talk) 11:31, 23 July 2019 (UTC)
@Xover: I understand that DJVU is shown better in the Page namespace. Does it applie also to DJVU converted from PDF? I personally would expect that any further processing deteriorates the text, so it is really strange if it improves after the conversion. --Jan Kameníček (talk) 11:43, 23 July 2019 (UTC)
@Jan.Kamenicek: Sorry, I missed this question. There is nothing inherently lossy about converting between PDF and DjVu where the text layer is concerned. We're converting structured data from one format to another, not doing OCR on an existing OCR text or stacking lossy compression algorithms. If the extraction from PDF in Mediawiki gives poorer results than the extraction of the exact same text from a DjVu, then any process that moves the text layer as is to a DjVu should give better results. But, of course, if you use the same method that Mediawiki uses (which gives bad results from good data) and puts that into the DjVu, then the conversion will give equally bad results (or maybe even worse results).
But I'm not familiar with the way PDF stores text layers internally or the existing tooling for extracting it. It is entirely possible that actually doing this in practice is too complicated to be realistic. So at least for now, my approach will be to generate a new DjVu, with a new OCR text layer, from original page images, when this issue crops up. And I'd be happy to help out anyone who doesn't have the tooling available to do it themselves. Just with no promises on turnaround time: it's a somewhat fiddly multi-step process where each step takes a significant amount of processing time. --Xover (talk) 09:59, 28 July 2019 (UTC)

Tables of Contents[edit]

In the past I have mostly relied on {{Dotted TOC line}} when building tables of contents, and in many cases that works fine.

I've seen others use a table-based approach, rather than a template on each line. I don't see anything under help:Table of Contents or WS:Table of Contents, and I'm wondering if somebody could help me learn this other system.

I'm currently looking at this page, and related ones: Page:American Historical Review vol. 6.djvu/9 What's the best approach for a page like that, with 3 columns for text entries? Maybe somebody could get it started on that page, and I could carry it to completion? -Pete (talk) 22:08, 26 July 2019 (UTC)

That page uses {{TOCstyle}}, you can read the documentation on its template page to get up to speed. I personally would use {{TOC row 1-dot-1}} and its related templates, which are also documented on their own template pages. —Beleg Tâl (talk) 12:46, 28 July 2019 (UTC)

OCR failure is not universal[edit]

I work in several books in the same session, and found an inconsistent OCR behaviour. In this volume, the OCR works, and in this volume, OCR deletes the text on save. — Ineuw (talk) 04:02, 27 July 2019 (UTC) P.S: Please test the OCR repeatedly on the page. — Ineuw (talk) 04:05, 27 July 2019 (UTC)

I tried it and confirm that it behaves the way you have described. --Jan Kameníček (talk) 07:33, 27 July 2019 (UTC)
@Jan.Kamenicek: It seems that Phabricator found the problem and by comparing the results of the two pages and I hope that the solution will soon be found and applied. — Ineuw (talk) 22:26, 28 July 2019 (UTC)

Need index verified[edit]

Index:The Life of the Spider.djvu is completely verified except for the index (pages 401–404). Could someone verify those 4 pages? Thanks! Kaldari (talk) 11:24, 28 July 2019 (UTC)

Yes check.svg Done [@Kaldari] --Xover (talk) 18:40, 28 July 2019 (UTC)

Template styles to reduce calls to ts...[edit]

Template:Os Lusiadas (Burton, 1880)/errata.css This is a useful technique, Is someone considering documenting this so it can be used more widely? ShakespeareFan00 (talk) 15:23, 21 June 2019 (UTC)

@ShakespeareFan00: (and CC Inductiveload) There is documentation for TemplateStyles itself at mw:Help:TemplateStyles. It's not much used here yet because until very recently there were serious bugs in MediaWiki when it was used, and that broke stuff here on enWS. Those have now been fixed so as a general rule TemplateStyles should be safe to use.
However, note that the intended use for mw:Extension:TemplateStyles is in actual templates, and use elsewhere is not necessarily a good idea. Even if it does not create any other technical issues, I am uncertain we would want a work, like The Lusiads (tr. Burton), in mainspace to have an associated custom stylesheet over in the Template: namespace (i.e. Template:Os Lusiadas (Burton, 1880)/errata.css). Until some kind of practiice and guidelines is figured out for this use case I would recommend using it only very sparingly and only when the benefits are significant (avoiding a large number of {{ts}} calls might be one such case).
The method does look like a very useful one with many potential benefits for the Wikisources though. Perhaps it would be worthwhile to poke Tpt and Anomie and see if something tailor-made for Wikisource could be made based on ProofreadPage and TemplateStyles? There is that "CSS" field in the Index: that only kinda sorta does work sometimes maybe. Perhaps it would make sense to have per-work custom CSS in a subpage of that work's Index:, and use the "CSS" field on the work's index to load it?
Whether or not we would want to actually allow per-work CSS is a different matter, and one that would need discussion on the Scriptorium to determine. I imagine the benefits might be obvious for larger works like the DNB, but more controversial for most smaller individual works. --Xover (talk) 16:23, 21 June 2019 (UTC)
@Tpt: @Anomie: , Let's start the discussion.. I know with some works I did that I was using a LOT of {{ts}} calls, when some form of advanced per work classing would be more appropriate, assuming it was possible..
It's definitely a nice idea. I have opened a task about it. Tpt (talk) 17:38, 21 June 2019 (UTC)
FYI, you should be able to do <templatestyles src="Index:Os Lusiadas (Burton, 1880)/errata.css" /> to include Index:Os Lusiadas (Burton, 1880)/errata.css. You should be able to convert that Index page to the "Sanitized CSS" content model using Special:ChangeContentModel, or by moving the existing Template:Os Lusiadas (Burton, 1880)/errata.css with that content model to the new title. Anomie (talk) 13:39, 22 June 2019 (UTC)
@Anomie: - Thanks, but I think Index: pages generate their own edit form, which would need to be DISABLED if whats being seen is in fact the per work styles.. 13:44, 22 June 2019 (UTC)


Note that any transcluded styles for Page: 's would also need to be made in such a way that the CSS concerned could also be used in Main namespace, but I'm not sure how you would be able to write CSS that was transclusion aware.. ShakespeareFan00 (talk) 16:28, 21 June 2019 (UTC)


ShakespeareFan00 (talk) 16:28, 21 June 2019 (UTC)

(Aside) It would be nice in time (i.e when anyone cares to implement it) if {{ts}} was re-written slightly, so that adding new codes to it and other templates like {{tf/s}} {{span}} {{p}} etc. could be done WITHOUT having to add new clauses to the MASSIVE switch statements inside them. ShakespeareFan00 (talk) 16:45, 21 June 2019 (UTC)
If necessary, you should be able to use body.ns-0 as part of a selector to apply only on main-namespace pages, and similarly body.ns-104 as part of a selector to apply only on Page-namespace pages. Anomie (talk) 13:39, 22 June 2019 (UTC)
Thanks
In terms of name-mangling if needed, could you do something like __indexpage_id__localclassname?

ShakespeareFan00 (talk) 13:44, 22 June 2019 (UTC)

In terms of what's required to use this right now:
  • If it's acceptable to put the CSS styles in the Template namespace, nothing needs to be done right now.
  • If it's preferred to put per-work styles in the Index: namespace (which I think is probably a good idea) then any of these will suffice:
    • Set $wgTemplateStylesNamespaces so that Index namespace CSS pages get the Sanitised-CSS content model by default (IMO, this is best), or
    • Permit non-administrators to change page content models (to work around the lack of default). This can be either by a change of config, or a resolution of phabricator:T85847.
    • Put them in the Template: namespace and move them later when one of the above is done.
In terms of nice-to haves, a resolution of phabricator:T226275 would allow the <pages/> tag to pull in a style that every page of a work uses. But this can be worked around for now by manually placing the shared <templatestyles/> tag before the <pages/> tag and adding to the auto-header in the index page. THis would be easy to bot out later, and harmless if left in place.
Inductiveloadtalk/contribs 14:19, 2 August 2019 (UTC)

Including indexes in exports[edit]

Just finished validating my first Wikisource text, The Life of the Spider (with some help from Xover above). One thing I'm not sure about is linking to the book index from the Wikisource page. The book index isn't listed in the table of contents, so it isn't linked to from the Wikisource page, and thus isn't included in exported versions. Is there a way to fix that (aside from just transcluding the book index directly into the Wikisource page)? Kaldari (talk) 15:06, 29 July 2019 (UTC)

I think I would have gone with treating it as a chapter (its own subpage) and used the previous/next links in the header to link it in. And if the original table of contents is insufficient for some reason, {{AuxTOC}} is usually used to supply the want. But I don't think I've run across this specific issue previously so you may want to hold off and see if anybody else has a better or more definiitive answer. --Xover (talk) 16:55, 29 July 2019 (UTC)
Yep, I'd just stick an {{AuxTOC}} at the start/end (as appropriate) of the real TOC. For example, The Amazing Emperor Heliogabalus has a Preface that isn't listed in the real TOC. Its quite common for front matter and indexes. It could probably do with a note somewhere if this is actually good practice. Inductiveloadtalk/contribs 17:27, 29 July 2019 (UTC)
Thanks for the suggestions! I tried the {{AuxTOC}} template, but I didn't like that it created a separate TOC in the export that wasn't part of the original book. Instead I ended up just adding a hidden link to the Index from the existing TOC (Page:The Life of the Spider.djvu/10) which actually worked perfectly. Kaldari (talk) 02:00, 30 July 2019 (UTC)

The pages tag is supposed to add a Back and forward link?[edit]

It was my understanding that header=1 added forward and back buttons:- but here it's use here

https://en.wikisource.org/w/index.php?title=White_Fang/2&oldid=9512026 didn't immediately add them.

Where is the mistake so I don't have to run around playing hunt the quirk again, when trying to rely on what has and hasn't been purged in the backend yet? ShakespeareFan00 (talk) 17:12, 2 August 2019 (UTC)

For anyone trying to use this, the way it works is that when you add |header= to the <pages /> tag, ProofreadPage automatically inserts a {{header}} template with automatically generated variables for |previous= and |next=. To find the right previous and next chapter it uses the work's Index: page as a table of contents: every link to mainspace (i.e. ignoring links to Author: and Portal: pages) is assumed to be a chapter link, except the first link which is assumed to be the link in the title field to the work's main page. This last point was what tripped up ShakespeareFan00 here: in the Index: page the work's title wasn't linked, so ProofreadPage instead ignored the link to the first chapter. Thus the previous link on chapter 2 didn't get filled in (but subsequent chapters' previous links did). --Xover (talk) 18:11, 2 August 2019 (UTC)

How should I add incomplete indexes to Author pages?[edit]

Hello! I've recently upload scans of Nutcracker and Mouse-king by E. T. A. Hoffmann to commons and i've uploaded a Index to wikisource. I'm going to start transcription soon, but I would like some help. Can I add a link to the index on the authors page and if I can, how do I do that? If I can't add a link to authors page, where on Wikisource can I ask for help and/or boost the index's popularity? Pago95 (talk) 18:39, 4 August 2019 (UTC)

In my experience, you can choose one of three ways:
  1. If the work has been partially transcluded, place {{incomplete}} on the transcluded work page, and do not link to the Index page from the Author page.
  2. Otherwise, in general you would use {{small scan link}}; see Author:Dwijendra Nath Neogi for example.
  3. If there are a lot of works listed on the Author page and it looks too cluttered when you use {{small scan link}}, or if you want to distinguish between works that have scans and works which were added but do not yet have scans, you can use {{scan}}; see Author:William Schwenck Gilbert for example.
Beleg Tâl (talk) 19:15, 4 August 2019 (UTC)

Links to non-Commons files for speech transcriptions?[edit]

I'm interested in adding transcription of speeches by, and interviews with, US Government people (so no copyright issues). I believe that this type of content is welcome at Wikisource (https://en.wikisource.org/wiki/Wikisource:Scriptorium/Archives/2007-09). I have two questions.

1) How can I add a speech transcription entry to Wikisource without first uploading a file to the Commons? I understand from the Beginners Help how to create a Wikisource entry from a Commons upload, but what if I haven't done one? ETA: I realize now there is no requirement to have a Commons upload.

2) If I have a link to video or audio of the actual speech, but the link is not to the Commons, what is the format to include this link in the Wikisource entry? For example, this https://en.wikisource.org/wiki/Presidential_Weekly_Address_-_14_January_2017 is a transcription of an Obama Weekly address which can be viewed at Youtube. I think the entry would benefit from a link to the video, am I wrong and such external links are to be avoided?

-Dennis.the.Anarcho-syndicalist (talk) 04:13, 5 August 2019 (UTC)

Disambiguate plus Create an Author Page[edit]

I MUST create an author page for a "James Orton." He is not the same one who populates the existing "Author:James Orton" identified as an American Naturalist. ALL the background ID available on my "James Orton" reads as follows:

  • James Orton, Dublin, Author of "The Enthusiast," "The Three Palaces," &c., &c.

    My Jame Orton contributed 4 brief biographies to the "Imperial Dictionary of Universal Biography." Both authors wrote in the mid to late 19th century. I have found a few references in periodicals but have not been able to add a middle initial or vital statistics. What is the recommended remedy?Klarm768 (talk) 17:05, 7 August 2019 (UTC)

Have you used Wikidata at all? One good first step would be to ensure that each has a thorough Wikidata entry. The naturalist has an entry: wikidata:Q6140665 It would be good to start another for the other Orton.
More specifically, it's my impression that English Wikisource policy is generally to use the most complete name of the author, as opposed to the name by which they are best known. So if there is a known middle name for either, that's the most straightforward way to distinguish them. If not, Help:Disambiguation#Authors says we should use birth and death years to distinguish. -Pete (talk) 17:30, 7 August 2019 (UTC)
I can find no dates for the author of The Enthusiast &c., so a floruit date would be the next best thing: i.e. Author:James Orton (fl. 1843-1859), and the existing author page should be moved to Author:James Orton (1830-1877). —Beleg Tâl (talk) 17:40, 7 August 2019 (UTC)
I can see a James Orton in Ireland in the 1850s, and early 1860s. James Orton married Julia Colthurst in 1853, he was of St. Margaret's Bay, Kent. (Dover?) Wife died 1857 (seems to be childbirth), and daughter 7 months later, at 7mo. This gent is Bray, Wicklow (selling up 1862). Directories and newspapers shows James Orton an inspector of branches (People's Provident Assurance Society) in Dublin and Bray in 1858. [Baptism of John Nicholas Colthurst Orton in Westminster in 1854, so this is a UK & Ireland search. JNCO cited as actor in census. Death of same, also called Charles Overton, 1898]
Thank you to all who have pitched in... particularly @Beleg Tâl:. I was going to need further help implementing BT's advice, but it appears BT has performed what was proposed. I wish I could say that understand what BT proposed and appears to have done. Perhaps then I could do the remainder myself. Wikidata is mysterious to me. HOWEVER I have 3 remaining disambiguate+create problem authors. Should I create a new Scriptorum Section for each or continue this one? Klarm768 (talk) 14:35, 8 August 2019 (UTC)
The steps are as follows:
That's really all there is. A wikidata item for the new author will need to be created, but you can ask someone else to do it for you, or you can look at d:Wikidata:Tours to learn how to do it yourself. —Beleg Tâl (talk) 14:42, 8 August 2019 (UTC)
Thanks. I've now started the Wikidata Tours. A number of the IDUB contributors are not published elsewhere, no dates of birth/death are provided, often possess rather common names, are distinguishable by their profession/city/academic&heraldic_credentials. Overall I am proud of my detective work on 230+ discoverable contributors. BUT My last three provide least of any distinguishable facts, their Author:names are already in use. My numerously-configured Google searches are not adequate. More successful search methods are not mine. The dates of contribution-composition are not provided so floruit date could be 1854-1876.

I can provide a titles of their contributions and/or the full content of contributions. The TOTAL contributor data points are these:

  • Rev. James Anderson, Edinburgh.
  • James Barr.
  • Frederick M. White, Aylesbury.
Klarm768 (talk) 16:09, 8 August 2019 (UTC)
Possibly useful: Frederick M. White contributions (numbering about 370) are mostly biographies of Spanish historical and then-living contemporary figures. Klarm768 (talk) 16:23, 8 August 2019 (UTC)
I think James Anderson (1804-1863) is the first one; see these ads in the Imperial Dictionary for reference. —Beleg Tâl (talk) 17:50, 8 August 2019 (UTC)
Frederic(k) Meriton White (1828-1895), the brother of w:Jessie White Mario, wrote letters on Italian affairs signed "Frederick M. White, Aylesbury". His page will be Author:Frederic Meriton White, because his full name is unique. —Beleg Tâl (talk) 18:05, 8 August 2019 (UTC)
James Barr, it appears, wrote only a short article on the Lutheran theologian Daniel Hoffman, which may be a clue —Beleg Tâl (talk) 18:31, 8 August 2019 (UTC)
Thanks for your help... BUT I failed to include parentheses and I created Author:James Anderson 1804-1863. So now I need advice on how to remedy that.

I find 9 contributions by Barr. Most of them are ecclesiastics; but not of any particular denomination, nation, or doctrinal theme that I recognize. I observe that not only Barr's but many of the signatures fall in a segment of the alphabet. I have surmised that they were contracted for a "duration" (sub-editor switches were numerous). The original IDUB was created from A-to-Z. This might explain why all of Barr's biographies start with G, H, I, J, or L. At least one of the less august contributors was employed while a University student. Perhaps contributions ceased with graduation or acquiring a better job elsewhere. Klarm768 (talk) 20:35, 8 August 2019 (UTC)

I finally figured out how to perform "Move" and fixed Author:James Anderson (1804-1863) myself. Klarm768 (talk) 21:19, 8 August 2019 (UTC)
I think that I performed the 4 steps described above creating Author:James Barr (fl. 1854-1863). Please advise of any deficiencies. Thanks! @Beleg Tâl:

I happen to possess a physical copy of the 1863 Edition and could confirm that Barr's contributions are there. His originals were probably first printed 1856-1860. I know of no digital version of 1863 Edition. Klarm768 (talk) 21:48, 8 August 2019 (UTC)

Add floruit range to Module:Author[edit]

Would it be possible for someone to add floruit ranges to Module:Author? The relevant properties are d:P:P2031 and d:P:P2032. I could probably figure it out, but it would take a while. —Beleg Tâl (talk) 12:53, 8 August 2019 (UTC)

Maybe Sam Wilson could have a look at it, we discussed it some time ago. --Jan Kameníček (talk) 20:55, 8 August 2019 (UTC)

Navaho Legends or Memoirs...?[edit]

I'd like to move this book from Commons over to Wikisource. I've created a few books before from Commons to Wikisource but I don't know what to name this one. This is what I named it on Commons "File:Navaho Legends.djvu" But maybe I was supposed to name it "Memoirs of the American Folk-Lore Society V". This one in Wikisource is from the same series.
Index:Memoirs of the American Folk-Lore Society XVII.djvu
Should I have named the original file, on Commons, Memoirs of the American Folk-Lore Society V ?
And then there's this also, already on Wikisource, with a red link for Navaho Legends: Memoirs of the American Folklore Society Please help with advice or please go ahead someone and do it because I have no idea how to proceed and I would like to start reading and working on the Navaho Legends. Also note that same book is available on books.google except there is an image that doesn't show on the book in Commons AND images are in books.google are in color. Thank you much.--The Eloquent Peasant (talk) 00:24, 9 August 2019 (UTC)

Sorry for answering my own question. I've requested the file in commons be moved to: File:Memoirs of the American Folk-Lore Society V.djvu so then I can create the index file here. I think this is the correct thing to do. Thanks! The Eloquent Peasant (talk) 02:03, 9 August 2019 (UTC)
Ultimately the name of the file doesn't really matter, but it's preferred (especially on Commons) if files in a series have consistent naming. Since the other files in this series have the format "Memoirs of the American Folk-Lore Society #.djvu", I think you were right to rename the file. —Beleg Tâl (talk) 14:53, 9 August 2019 (UTC)

Translation:Order No. 227 by the People's Commissar of Defence of the USSR[edit]

I recently found Translation:Order No. 227 by the People's Commissar of Defence of the USSR, which though its original text is in Russian public domain (as per Template:PD-RU-exempt). Yet the translation still cannot give out a license for translation. Is that piece of text eligible for deletion? Thank you.廣九直通車 (talk) 13:12, 9 August 2019 (UTC)

This is a Wikisource original translation and as such the translation is licensed under CC BY-SA. —Beleg Tâl (talk) 16:30, 9 August 2019 (UTC)

Mark above line[edit]

On this page, about the middle of the right column, there is an odd character: a rho with a wavy line above it. This squiggle is intended to reproduce a manuscript mark and looks to have been added to the type plate freehand. How should it be reproduced digitally? Levana Taylor (talk) 01:44, 8 August 2019 (UTC)

A Rho or a P with a tilde. For our grade of work, it should be suitable to use w:P̃ billinghurst sDrewth 05:05, 8 August 2019 (UTC)
Nonono don't use Latin letters to transcribe Greek! The correct character is Rho + combining tilde: ΧΡ̃Ο ΧΡ&#x303;Ο or Χ{{subst:cdm|Ρ|303}}ΟBeleg Tâl (talk) 10:36, 8 August 2019 (UTC)
I agree with Beleg Tâl. An alternate method (as if you need more!) could be: <math>\Chi\tilde{\Rho}\Omicron</math> which renders as: . Incidentally in case you are wondering the sequence in Greek is usually translated as Christo (as in Jesus)… 114.78.171.144 11:44, 8 August 2019 (UTC)
Cool, thanks for the math code. I had actually tried the combining tilde and noticed that it’s not suitable for capital letters because of rendering on the letter instead of above. But ‘math> can do so much. Levana Taylor (talk) 15:13, 8 August 2019 (UTC)
The combining tilde renders above the letter. Your system may not work right, but it works right on this system (a generic Windows 10 system), and hopefully the percentage of system that have problems with it will just decrease over time. The math code is less well supported and I'm pretty sure it won't work with screen readers, whereas I'm pretty sure that ΧΡ̃Ο will at least get spelled out.--Prosfilaes (talk) 01:10, 9 August 2019 (UTC)
Of the two browsers on my laptop, Microsoft Edge renders the combining tilde correctly and Firefox doesn’t. Can some other people try out Safari, Chrome, and mobile browsers? Levana Taylor (talk) 23:55, 9 August 2019 (UTC)
For me capital Rho + combining tilde as suggested by Beleg Tâl display well both in Firefox and Chrome. --Jan Kameníček (talk) 07:37, 10 August 2019 (UTC)
It's going to depend a lot on more things than just the browser. Edge and Chrome on Windows 10, and Chrome on my Android system all display it correctly.--Prosfilaes (talk) 07:47, 10 August 2019 (UTC)
OK, I should stop worrying then. Somehow I hit the one browser setup (Firefox + whatever addons on Windows 1) that wasn’t working correctly. Probably won't happen for anybody else. Levana Taylor (talk) 08:02, 10 August 2019 (UTC)

Problems with specific transclusion[edit]

Despite my repeated attempts, I have been unable to properly transclude this work, do to a number of incorrect line breaks added by the <pages /> command. Is there any way to fix this, other than to either fully correct the file, or to give all of the pages as templates (i. e., {{Page:}})? TE(æ)A,ea. (talk) 15:11, 9 August 2019 (UTC).

Took me a couple of goes, but the answer according to H:POEM is a <br/> before the poem tag end to force a stanza break. Inductiveloadtalk/contribs 16:05, 9 August 2019 (UTC)
  • That’s the problem; the poems are transcluding as intended. It is the unnecessary page breaks inside of a paragraph that are the problem. “[A]nd that no State could/either…” should be in one paragraph, not two (here). I’ve used (perhaps broken) <pages index="Marmor Norfolciense.djvu" include=25-55,64-65,56-63,82,66-78 />; that shows the correct “page” range. TE(æ)A,ea. (talk) 17:35, 9 August 2019 (UTC).
    • Since the paragraph that starts on page 55 is continued on page 64, I think that this include method is the only way to preserve that flow within the pages tag. —Beleg Tâl (talk) 18:26, 9 August 2019 (UTC)
      • That is what is currently being used; however, it is not working. With the “include” parameter, regardless of given order, it proceeds in numerical order. This causes problems, as the scan is not in numerical order. TE(æ)A,ea. (talk) 23:26, 9 August 2019 (UTC).
        • I see what you mean. I think I have an idea of how we could make it work, but honestly I think it would be better to just fix the scan. —Beleg Tâl (talk) 01:30, 11 August 2019 (UTC)
          • I have fixed the scan; there remains only to find images of pages 41 and 42 to replace the blank placeholders. —Beleg Tâl (talk) 02:32, 11 August 2019 (UTC)

Remove Index (Delete because it's missing images)[edit]

I'd like to have the Index:Memoirs of the American Folk-Lore Society V.djvu removed- it came from archives and is missing tons of images.
A better version of the same is on books.google and it's not missing images.
--The Eloquent Peasant (talk) 03:56, 11 August 2019 (UTC)

Upload the replacement file over the top of the current one. Beeswaxcandle (talk) 04:06, 11 August 2019 (UTC)
@Beeswaxcandle: Would you be able to point me to instructions on how to do that? I don't know how to upload a .pdf from books google. Thank you.--The Eloquent Peasant (talk) 04:13, 11 August 2019 (UTC)
It is slightly complicated as you want to upload a .pdf file, while the current one is .djvu. I personally would upload the pdf version to Commons independently of the original djvu, and then started a new index page. (The old one can be deleted then).
To get the book to Commons you need first to download it from Google Books to your computer, and then you can upload it to Commons using their UploadWizard. Unfortunately I cannot do it for you, as Google Books limit the access to many publications of theirs (including this one) in my country. If you need any other help, just ask. --Jan Kameníček (talk) 07:15, 11 August 2019 (UTC)
I did it! Thanks! 1) I downloaded the Google version (with images). 2) I converted it to djvu format. 3) I uploaded it over the old version (without images). Now I'll fix the pagelist. Thank you.The Eloquent Peasant (talk) 12:36, 11 August 2019 (UTC)
Nice job! Thanks for getting this squared away. -Pete (talk) 18:14, 11 August 2019 (UTC)
Thanks everyone for your tips!--The Eloquent Peasant (talk) 16:41, 13 August 2019 (UTC)

Wrong order of pages[edit]

A scanned file has got two wrongly ordered pages (no. 111 and 112). Having checked it with a different copy I found out that the original book has the pages correct and so it is only a fault of this particular scanned file. Unfortunately, the other copy has many other flaws, and so it is not possible to replace it. Could somebody skilled with djvu files fix it and reorder the two pages, please? --Jan Kameníček (talk) 18:30, 12 August 2019 (UTC)

Done. Please check, just in case ...Mpaa (talk) 22:30, 12 August 2019 (UTC)
Perfect, thanks. Now I'll just have to wait until the index pages get updated as clearing the cash has not helped, but I guess it is only a matter of time. --Jan Kameníček (talk) 06:59, 13 August 2019 (UTC)

Help with botched page move[edit]

In the midst of some discussion about book titles (see here if you want the background), I moved Vol 1 History of Mexico by H H Bancroft to History of Mexico (Bancroft)/Volume 1. I expected to see a checkbox that would have permitted simultaneously moving all the sub-pages (the chapters) as well, but I didn't see that option. I foolishly forged ahead, hoping that the checkbox I remembered was on the next screen in the process; but of course, it wasn't.

(1) Where did I go wrong, and (2) (more importantly) Is somebody able to move the sub-pages to clean up my mess?

The answer to (1) is actually somewhat important, because there are 3 other volumes in this series that will need similar treatment.

Please note, in this case the works have existed for some time, so it's important to preserve redirects rather than deleting the original page names. -Pete (talk) 06:03, 13 August 2019 (UTC)

You didn't go wrong, you just don't have the ability to do it because you're not an admin. Let me know on my talk page the exact names of origin and target that you want the other volumes moved to. Beeswaxcandle (talk) 06:53, 13 August 2019 (UTC)
OK. Now moved with subpages. I'll leave you to fix the links to the old title and the internal links in the headers and TOC. Beeswaxcandle (talk) 06:59, 13 August 2019 (UTC)
Ah, of course. I guess I'm remembering from other wikis where I'm an admin. I just didn't realize that checkbox was an admin thing. Thanks for doing that, and yes, I'm happy to dig through and fix any remaining idiosyncracies. -Pete (talk) 07:48, 13 August 2019 (UTC)

My custom edit toolbar gone again...[edit]

...which I could live with if I could possibly bring the Insert/Wiki markup, etc. toolbar from the bottom of my editing space to the top. Is this possible? Thanks, Londonjackbooks (talk) 04:11, 14 August 2019 (UTC)

please include athorisms of G.C. Lichtenberg[edit]

G.C. Lichtenberg was Germany's first professor of physics who had laid the theoretical groundwork for the Xerox machine by the mid-eighteenth century. Severely hunchbacked , he nevertheless became one the great aphorists of the age, recording his thoughts and observations - such as "Everyone is a genius once a year. A real genius has his original ideas closer together." - in a series of alphabetical "waste books"(he'd reached volume "l" by the time he died in 1799). Can you include the waste books, please ? Thank you! —Preceding unsigned comment added by 80.41.196.51 (talk)

Feel free to upload a public domain translation of this work: see Help:Beginner's guide to adding texts for how to get started. —Beleg Tâl (talk) 13:02, 14 August 2019 (UTC)
The only available book seems to be Lichtenberg's Reflections. I have uploaded it for you and created the index page, so if you want, you can start transcribing. I have also proofread two pages as an example, see e. g. Page:The reflections of Lichtenberg.djvu/28. If you need some advice during the work, just ask, somebody will always help you. Happy editting! --Jan Kameníček (talk) 15:41, 14 August 2019 (UTC)

IwPageSection generates badly formatted HTML...[edit]

<span class="iwpage" title="fr|Ruffhead - The Statutes at Large, 1763.djvu/206|viscount" id="fr:Ruffhead_-_The_Statutes_at_Large,_1763.djvu/206:viscount"><div class="mw-parser-output"><div class="pagetext"><div class="mw-parser-output"><p><br>
rien receu des dettes le Roi &amp; qe riens ne prendretz par quoi le Roi perde ou par quoi droiture soit desturbe ou la dette le Roi delae e qe loiaument freez retourner &amp; loiaument suire les brefs le Roi a vostre fen &amp; a vostre poair &amp; qe vous ne prendretz nul ballif en vostre service por qi vous ne voletz respoundre et qe vous swreez voz ballifs faire autiel serment come a eux apent et que nul brief ne receivretz, par vous ne par les voz souz seal des Justices forsqe en eyre ou autres justices assignetz en meisme la counte ou Justice de Neugate &amp; qe vous mettretz voz ballifs de plus loiaux du pais &amp; qe nul ballif ne ministre qi ad este od lautre viscounte retendretz en vostre service.
<span class="iwpage lang-en" title="en|Ruffhead - The Statutes at Large, 1763.djvu/206|p160-n1" id="en:Ruffhead_-_The_Statutes_at_Large,_1763.djvu/206:p160-n1" lang="en"></span>
</p>
<!-- 
NewPP limit report
Parsed by mw1290
Cached time: 20190816083951
Cache expiry: 2592000
Dynamic content: false
Complications: [vary‐revision]
CPU time usage: 0.008 seconds
Real time usage: 0.011 seconds
Preprocessor visited node count: 34/1000000
Preprocessor generated node count: 0/1500000
Post‐expand include size: 1917/2097152 bytes
Template argument size: 176/2097152 bytes
Highest expansion depth: 4/40
Expensive parser function count: 0/500
Unstrip recursion depth: 0/20
Unstrip post‐expand size: 0/5000000 bytes
Number of Wikibase entities loaded: 0/400
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
100.00%    7.960      1 Modèle:Lst
100.00%    7.960      1 -total
 25.16%    2.003      1 Modèle:IwpageSection
-->
</div></div></div></span>

This is malformed as a DIV cannot be inside a SPAN. LintErrors doesn't detect this,(and currently there is no visible impact as far as I can tell) but as I expressed previously on a different issue trying to shorehorn everything into a SPAN is leading to longer term issues. It's time certain contributors with the expertise, took another look at this. ShakespeareFan00 (talk) 08:47, 16 August 2019 (UTC)

Updated ShakespeareFan00 (talk) 10:07, 16 August 2019 (UTC)
I agree that this does not look like a good place to use <span></span>. By its nature it will regularly and quite appropriately contain block elements, and this will lead to all sorts of weirdness and undesirable behaviour. My initial thought is that this should be changed to <div class="iwpage-section"></div>, and site CSS changed to treat that wrapper as .iwpage-section {display: inline}. No guarantee this will not break anything that relies on the old quirks, but I would be inclined to argue that those instances are in principle broken to begin with. --Xover (talk) 10:11, 16 August 2019 (UTC)
I was saying eslewhere, that the iw templates and {{Page}} could ideally be a module, to centralise the core behaviour and provide options to overcome some of the current limitations, like in some instances the desirability of getting the semi-'raw' markup back, so that a local wiki could reprocess it slightly (However as templates are widely divergent on other wikiks, that proabably too risky.).ShakespeareFan00 (talk) 10:16, 16 August 2019 (UTC)
As such, see Special:WhatLinksHere/Template:IwpageSection so far only 1 work is actively using this, so it can be considerably overhauled. ShakespeareFan00 (talk) 10:18, 16 August 2019 (UTC)
I also note - https://wikisource.org/w/index.php?title=MediaWiki:InterWikiTransclusion.js&action=history had some performance improvments susequent to the local version. Sometimes I wonder if certain core code like this should be in a Centrally updated repository. (hard look at heavens). ShakespeareFan00 (talk) 10:37, 16 August 2019 (UTC)
The templates don't do much that's worth modularising; they just spit out a span or div with the provided params concatenated into the title or id attributes. The actual work happens in JS at MediaWiki:InterWikiTransclusion.js (globally loaded from MediaWiki:Common.js), which is a three year old copy of mul:MediaWiki:InterWikiTransclusion.js (I don't think the intervening changes are particularly relevant to this discussion). The templates expose the provided parameters as html attributes (id/title) which the javascript then picks up, and then requests the relevant content from the remote wiki using the MediaWiki API, and finally inserts it inside the span or div generated by the template here. In other words, the only bit worthwhile centralising is the javascript, and that is already centralised (it's just insufficiently maintained, but that's a separate matter).
A central repository for templates and Gadgets that are available across projects is on a long-term wishlist at the WMF, but nothing much is being done with it that I am aware of. The problems are not primarily technical: separate projects have separate goals and practices, making sharing code often be challenging. --Xover (talk) 10:53, 16 August 2019 (UTC)
I will also note the concerns expressed here User_talk:Beleg_Tâl#Page:Ruffhead_-_The_Statutes_at_Large,_1763.djvu/206 concerning whitespace insertion, there may be a need for a new template or approach in terms of my efforts. ShakespeareFan00 (talk) 11:15, 16 August 2019 (UTC)
Attempted this , but it doesn't work : {{IwpageSection/sandbox}} ShakespeareFan00 (talk) 12:11, 16 August 2019 (UTC),
See - https://en.wikisource.org/w/index.php?title=Page:Ruffhead_-_The_Statutes_at_Large,_1763.djvu/206&oldid=9543090 ShakespeareFan00 (talk) 13:15, 16 August 2019 (UTC)

Subpages in Page:namespace[edit]

Page:Ruffhead - The Statutes at Large, 1763.djvu/206/fr displays the first or last page not the actual scanned page. Working as designed but tiresome, because this would have been one approach to re-consolidating this page, or more complex layouts between many pages. ShakespeareFan00 (talk) 12:38, 16 August 2019 (UTC)

There is no scanned page, ProofreadPage simply has a default view for a non-existing page. Things are being displayed as expected, it is your actions that are not expected or within scope. Keep within scope, and things will work fine. — billinghurst sDrewth 13:20, 16 August 2019 (UTC)
As I indicated, this IS working as designed. What would be useful is the ability to transcribe different portions of a complex layout to different sub-pages, but using the same scanned image (an example would be a newspaper scan with many individual articles, in each 'frame' of the print layout ). This would not necessarily be the same as using sections. If this isn't currently supported fair enough, but it's a limitation.

ShakespeareFan00 (talk) 13:57, 16 August 2019 (UTC)

We are working in the Page: namespace, why should we be bothering with intricate complexity for no valid purpose. Our purpose is the presentation in the main namespace in a clean and as simply as reasonable possible. Why do we even have the discussion about some fancy? You keep trying to make things more difficult and convoluted than is necessary. — billinghurst sDrewth 14:52, 17 August 2019 (UTC)
Okay so, 1 page per scan, where would be appropriate to document that this is a direct design/policy decision then? ShakespeareFan00 (talk) 15:26, 17 August 2019 (UTC)
It's an interesting idea. Unfortunately, I don't think the devs would implement it; it would require a lot of work to implement and would not be used very much at all. I've seen the devs shut down ideas that are better than this and easier to implement. —Beleg Tâl (talk) 21:38, 16 August 2019 (UTC)
And sometimes, my seeming unreasonableness, comes from the fact that I do actually "care" (as you do.), I'm just more likely to bluntly express the frustrations I have about quirks and limitations, because there is seemingly (as you mentioned previously) not necessarily the community expertise for someone to sit down and take a closer look at the responsible code. In many instances Wikisource IS pushing the limits of what Mediawiki and wikitext was originally designed to do, and the flexibility offered means that slightly less experienced contributors (myself included) are only to able to create combinationally complex templates, that a more considered approach wouldn't have. If I seem to be complaining a lot, it's not because I like complaining, it's out of frustration at encountering the same concerns and temporarily lacking the recall of what had been suggested or decided on as a reasonable solution previously. Given this I am wondering if I should stop contributing, as I seem to unable at times to express 'technical' concerns without ranting, or the ability to reason if previous solutions, (even some I had suggested) would be applicable. ShakespeareFan00 (talk) 16:46, 16 August 2019 (UTC)
I'll strike this out, on re-consideration. ShakespeareFan00 (talk) 18:11, 16 August 2019 (UTC)

Index:A Treatise on Electricity and Magnetism - Volume 1.djvu[edit]

There seem to be three different approaches being used to the Subject and chapter headings across this work. Before I continue I'd like to ask someone to consider writing a style guide for this, so I'm not necessarily going to have to go back over stuff that was previously validated. ShakespeareFan00 (talk) 14:41, 17 August 2019 (UTC)

How to on footnotes that overflow on Narrative of the Proceedings of Pedrarias Davila[edit]

Well. Here it definitely feels like the blind leading the blind. Which is better, before or after? I proofread the pages leaving the footnote overflow formatted the way it had been done before my time. Newer user changed the footnote overflowing wikimarkup and I don't think it works. Sometimes the page on the finished product shows a broken sentence. I let the user know that I thought he should undue his footnote formatting changes. This is an example of the page: [[18]] Please guide us or tell us where to go for guidance. Thanks. --The Eloquent Peasant (talk) 16:31, 17 August 2019 (UTC)

I left a couple of newlines preceding the footnotes, which interfered with the transclusion. Sorry about that. I've now removed them. Feel free to revert my changes if they've somehow made things worse. 8582e (talk) 16:42, 17 August 2019 (UTC)

I have fixed one ref, now it should work fine. Imo the best solution is to use <ref name="xy"> text </ref> on the page where the reference starts and <ref follow="xy"> text </ref> on the following page. I have never met any other solution. --Jan Kameníček (talk) 17:00, 17 August 2019 (UTC)
TY VM!--The Eloquent Peasant (talk) 18:04, 17 August 2019 (UTC)
@8582e: I think you were doing it right. The way it was there before is from long ago. See Jan's response. Sorry to cause you a headache and thanks again.--The Eloquent Peasant (talk) 18:06, 17 August 2019 (UTC)

<pages>tag fails when placed inside <ref></ref>[edit]

See the reference for Page:The seven great hymns of the mediaeval church - 1902.djvu/31 ShakespeareFan00 (talk) 10:30, 16 August 2019 (UTC)
<ref>…</ref> is itself technically provided by an extension (mw:Extension:Cite) and as such has severe limitations in what you can do inside of it: in particular, executing another extension (mw:Extension:Proofread Page) inside it is highly unlikely to work. --Xover (talk) 11:03, 16 August 2019 (UTC)
So is there a credible alternative approach, it did work at some previous date as the page was validated. ShakespeareFan00 (talk) 11:08, 16 August 2019 (UTC)
According to the ref documentation, you can use the #tag parser function for the ref tag. {{page}} inside a normal ref tag might work too. Inductiveloadtalk/contribs 11:14, 16 August 2019 (UTC)
You're actually missing the mark a little. The <pages> tag works great when placed inside <ref></ref>. However, it does not work at all in Page namespace. That is why the transcluded reference does not appear on Page:The seven great hymns of the mediaeval church - 1902.djvu/31, but it appears just fine on The seven great hymns of the mediaeval church/The Celestial Country. —Beleg Tâl (talk) 11:23, 16 August 2019 (UTC)
Then the second suggestion works: <ref>{{page|The seven great hymns of the mediaeval church - 1902.djvu/66|section=note01}}</ref>. The {{page}} template defers to LST's #section parser function, so it's independent of the pages tag. Regardless, the current state is not actually "broken" per se, since it does transclude correctly (edit: kinda, it has linter errors) (and the original work doesn't have the note on that page anyway). Inductiveloadtalk/contribs 11:30, 16 August 2019 (UTC)
HTH (sigh) ShakespeareFan00 (talk) 11:55, 16 August 2019 (UTC)
The LintHint script is however claiming for [[19]] is there's a DIV SPAN swap sowmewhere though. but I can't see it visually in the output, so hardly a priority. ShakespeareFan00 (talk) 12:02, 16 August 2019 (UTC)
That would be because there is the following construction for each ref:
<span class="reference">
    <div class="prp-pages-output">
       REF CONTENT
    </div>
</span>
The solution above with {{page}} doesn't suffer from this, as there is no class="prp-pages-output" div.
You could also do this all manually with anchors and links if refs doesn't get you what you want. The reference extension is just a helper. Inductiveloadtalk/contribs 12:41, 16 August 2019 (UTC)

Pictogram voting comment.svg Comment Not sure why we are going around this roundabout yet again. It will never work successfully, and it is completely known that it will be problematic within wikis. So please stop the incessant complaining; it is getting beyond a joke.

See mw:Help:Magic words and #tag for the means to address these sorts of matters. Others use of #tag:ref and #tag:pages over many years has not been accidental. So please utilise the solution that has been around for years, and look at using template:authority reference as it will probably manage what you are doing; actively used in {{IrishBio ref}}. — billinghurst sDrewth 12:48, 16 August 2019 (UTC)

Thanks, if that's the approach that SHOULD be used, where would be an appropriate place to document it? ShakespeareFan00 (talk) 13:16, 16 August 2019 (UTC)
And I'm sorry if I appear to be raising the same issues repeatedly. ShakespeareFan00 (talk) 13:21, 16 August 2019 (UTC)
I think this is just phab:T49544 rearing its ugly head again. We should definitely not start removing block content from references just because the references algorithm hasn't been updated to accommodate them yet. In this case the current construction works exactly as intended. —Beleg Tâl (talk) 21:35, 16 August 2019 (UTC)

┌─────────────────────────────────┘
Why make this so ludicrously complicated? To use the existing symbolism:

substitute:

<ref><pages index="The seven great hymns of the mediaeval church - 1902.djvu" from=66 to=66 onlysection="note01" /></ref>

with:

<ref name="note01"> </ref>

N.B. Do not get clever and remove the space or use form <ref name="note01"/> as Cite is not without finicky limitations…

substitute:

{{sup|1}} 
## note01 ##
"Le {{ls}}urnom de Bernard &c. &c.
####

with:

<ref follow="note01">
"Le {{ls}}urnom de Bernard &c. &c.
</ref>

Now was that so hard? No need for nested extension invocations at all! Oh and don't forget to rinse and repeat for each case. 114.78.66.82 23:07, 16 August 2019 (UTC)

Or, you could leave it alone since it's already validated and working as intended. I probably would have used this method if I had known about it when I proofread that work, but the method in place currently is fine. —Beleg Tâl (talk) 23:17, 16 August 2019 (UTC)
@Beleg Tâl: You speak as the person who tweaked the page twice (out of nine edits) subsequent to validating the thing. Even if what you were attempting unsuccessfully to do actually worked it would be wrong and result in a large amount of footnote content which should not appear in Page: space. So, umm—no. Do it right instead.

Recall I have no real dog in this fight so do not care if you persist in being stubborn, foolish or foolishly stubborn. 114.78.66.82 01:19, 17 August 2019 (UTC)

Foolish, would be breaking or unnecessarily uglifying something. And it's definitely not stubborn to not want to change something the only issue with is a small linter concern (which as I said above was hardly a priority.) Your solution when tested did not render in the expected way in respect of the Notes Pages itself. Namely I ended up with a a list of superscripted numbers followed by a list of the notes broken out of the formatting. (There may have been numerous reasons why that formatting was being retained.) Did you try sandboxing the approach you suggested above? User:Billinghurst's suggested template was a much cleaner approach, and a more sensible solution to this. Yes I can agree with doing it right, provided that it IS actually the right way, something many of my own "too clever by half" approaches to certain layout issues have eventually floundered on.ShakespeareFan00 (talk) 20:07, 17 August 2019 (UTC)
While it's great that you have given the valuable advice above and I guess everybody really appreciates it, the way of doing so reminds a golden rule from meta. --Jan Kameníček (talk) 07:19, 17 August 2019 (UTC)
I have solved the references on The seven great hymns of the mediaeval church/The Celestial Country using {{authority reference}}, which is basically a wrapper around the solution using #ref and #section tags with a bit of namespace-sensitive code on top. I did modify the template slightly for flexibility in cases like this when the reference text is not a single section on a singe Page. I didn't do so to break the validated text, but more because I wanted to ensure that the {{authority reference}} approach would, in fact, work. Indeed, it was previously not quite possible with that template as-was, and it now is. I have also overhauled its documentation. Inductiveloadtalk/contribs 13:14, 19 August 2019 (UTC)

Scanned pages and OCR layer do not agree[edit]

I have uploaded Index:Philosophical Transactions - Volume 050, part 1.djvu and then found out that the OCR layer is one page ahead to the scanned pages (e.g. page no. 2 has the OCR text of the page no. 3, etc.). I guess that the reason could be that IA uploader added one extra page before the cover, which was not in the original file. May I ask if somebody could fix it, please? --Jan Kameníček (talk) 21:18, 17 August 2019 (UTC)

I have uploaded a new version, without first pages. Text layer should be aligned now. Please corsscheck pagelist.Mpaa (talk) 19:24, 18 August 2019 (UTC)
Thanks very much, again! --Jan Kameníček (talk) 20:19, 18 August 2019 (UTC)

Pages tag without a wrapper?[edit]

This page Short_Titles_Act_1896/First_Schedule/1838 uses the deprecated {{Page}} template because it builds up a table where the sectional boundaries do not align with the page boundaries in the scan.

Is there an equivalent {{pages}} template or module that would do the same thing with a single template call or invocation which is equivalent to if it weren't for the table would be a straightforward &ltpages&gt tag (which according to it's documentation cannot currently be used in this way)? ShakespeareFan00 (talk) 08:48, 18 August 2019 (UTC)

If this is the correct way to build these pages, fair enough, but concerns were raised about overly convoluted solutions recently. (I'd already started on trying to subst down the templates used in Page: namespace on this so that it was simpler to understand. ShakespeareFan00 (talk) 08:48, 18 August 2019 (UTC)
I'm sure there's a better way to do this directly from the scan. I'd probably do it by placing the table headers in Page space within <includeonly> tags. Then you can use the standard <pages> transclusion without difficulty. —Beleg Tâl (talk) 13:27, 18 August 2019 (UTC)
If the <pages> tag had an 'embeded' variant then I would certainly prefer to use it directly. Multiple <includeonly> tags. seems to me to be the wrong way to go, in terms of simplicity. Maybe the whole structure needs a rethink. ... ShakespeareFan00 (talk) 14:37, 18 August 2019 (UTC)
HTH - Given that the only reason this was sectionalised in the first place, was because it blew out the transclusion limits, I wondered if it was the repeated/nested template calls doing that, having removed one layer of complexity, I rewrote a lot of the repeated calls as part of TemplateStyles stylesheet (which when this work was first done wasn't possible), and the resultant removal of a number of {{ts}} calls meant that the transclusion limits were not being hit nearly as rapidly. Unless I hit the limit for building a table, it may be possible to remove the need for the sectioning altogether and have the table as one LARGE page again :) .ShakespeareFan00 (talk) 07:11, 19 August 2019 (UTC)
While I think using TemplateStyles for table formatting is a good idea, I do not think it's a good idea to pile work-specific CSS into a generic stylesheet like Template:Table class/tableclasses.css. This stylesheet should contain only the most generic classes that are applicable across all works, as it will be loaded/embedded for every page that transcludes {{ts}}. Any work-, scan- or table-specific formatting should go into a dedicated stylesheet. There are very very few classes that truly belong at the global scope. In fact, there's an argument to say there should be no global styles, because, assuming we do use TemplateStyles, they are easy to implement on a per-work/-scan/-table basis, and having a core set of classes globally is fragile: if the central CSS is changed, the changes will propagate to tens of thousands of pages and breakage (subtle or not) might go undetected for a very long time, by which time going back would possibly break pages made in the meantime. Unpicking which pages are and are not affected would be frustrating at best. With CSS only at the work level or lower, the effects are siloed into their own scopes and are easy to search for and adjust. Inductiveloadtalk/contribs 08:26, 19 August 2019 (UTC)
Huh? {{ts}} doesn't import it Special:WhatLinksHere/Template:Table_class/tableclasses.css.. {{table class/import}} does. And that so far as very limited use ShakespeareFan00 (talk) 09:04, 19 August 2019 (UTC)
I do see you concern about the short-titles stuff being highly specific so separated it out. There are some other rules in it that could probably be reworked into more tightly specfied layouts as well , hmm.. ShakespeareFan00 (talk)
Cool, __ntrans probably needs to move out as well.
I'm also not convinced the single-rule classes like "__bb" are necessary. You still need to put "{{tc|__bb}}" on every single element, instead of {{ts|bb}} or style="border-bottom:1px solid black;", so it's not saving typing, and it's going to end up with loads of tiny classes in the global CSS scope. CSS is really good at applying multiple styles (e.g. "__boxc") or applying styles to many specific subelements (e.g. "__col"). But having tons of rules which are essentially just aliases for individual styles seems odd. Especially when you are repeating for table, tr and td.
If you find yourself repeating {{ts}} calls a lot, then it might be time for a work- or table-specific CSS. But only hoist to global scope if you are sure that 1) the style applies to enough works to merit it and 2) the style is well-defined enough that people won't need to tweak in future, as tweaking global CSS is risky.
Perhaps "__t_" might be a better prefix too, where "__" denotes global and "t_" denotes "table CSS". Otherwise, you could get silent collisions in future if, say, some image formatting CSS used "__foo". Making sure they're siloed into "__t_foo" and "__i_foo" pre-empts that problem. It might not happen, but if it does, it'll be frustrating. Perhaps a defined prefix for "work-specific CSS" should be defined too. At Template:Os Lusiadas (Burton, 1880)/errata.css, I used the schema "_oslus", where "_" denotes "work specific" and "oslus" denotes that particular work (which only has to be unique in each context it might be transcluded and is more for documentation ans searching than necessity).
On the subject of searching, a handy way to find pages using a certain class is like this: insource:/__boxc/. Underscores are "greyspace", so they're otherwise tricky to search for. Inductiveloadtalk/contribs 10:06, 19 August 2019 (UTC)
That was partly a deliberate design decison :) .

Section break to follow up with some CSS questions..[edit]

Question can TemplateStyles import more than one stylesheet at a time? ShakespeareFan00 (talk) 10:24, 19 August 2019 (UTC)

Of course you can. Otherwise TemplateStyles would only allow a single template per page to use it. And then you'd have to pile everything that could possibly be needed on each Wiki into a monstrous CSS file. Which would be called...common.css! Inductiveloadtalk/contribs 10:47, 19 August 2019 (UTC)
Sorry to be hard of understanding but can you do this:?
<templatestyles src="genericstyles.css tablestyles.css minutiae.css" />
If you can then {{table class/import}} can be generalised into an {{importCSS}} line ? Unless I'm overthinking again. ShakespeareFan00 (talk) 14:32, 19 August 2019 (UTC)
You can't do that because that would try to import the content at Template:genericstyles.css tablestyles.css minutiae.css (and pages can have spaces in the title, so you can't naively split on spaces). You also can't repeat the src attribute, as XML doesn't allow that. If you actually wanted to do this, you'd just add multiple calls:
<templatestyles src="genericstyles.css" />
<templatestyles src="tablestyles.css" />
<templatestyles src="minutiae.css" />
And, yes, you can put this in a template and it will work. Try it out.
As I said in the earlier section, a workable solution, until phabricator:T226275 is done, might be to put CSS common to a work in the "header" of the work in Page namespace, and then also transclude it in mainspace manually. If ProofreadPage gains the ability to implicitly include one or more CSS sheets, the <templatestyles/> calls in mainspace and Page namespace will be pretty easy to clear up, and won't break anything in the meantime. Inductiveloadtalk/contribs 15:18, 19 August 2019 (UTC)

You may be correct about the "small" classes, but the thinking here (experimentally) was that {{table style/parse}} is a massive switch statement. It's not easy to add new short codes (the same data/logic combination occurs with {{tf/s}} (in the absence of {{div}} {{heading}} {{span}}. By moving the 'style' data OUT of the template logic, it's easier to maintain that logic or protect it, isn't it?ShakespeareFan00 (talk) 10:36, 19 August 2019 (UTC)

Why is that difficult? It's just adding a line like this:
      -->|w15=width:15%<!--
Why is that harder than adding this to the CSS?
table .__w15 {
     width: 15%;
};
But this begs the question: why is "width:15%" useful to have as a global style class anyway?
I think {{ts}} has gotten a bit out of hand with too many styles being added for niche cases, but it dates from a time years before TemplateStyles was even conceived, when doing everything per-cell is extremely verbose and tedious, and it seemed useful at the time. The worst excesses of {{ts}} can probably be replaced with much more concise CSS targeted to the table, the work or, (very, very, carefully) globally. Any shorthands that then aren't globally useful can be trimmed from {{table style/parse}}. But they aren't especially harmful, because they're not polluting any scope outside the internal switch of {{ts}}. The worst case is that template evaluates slowly, but I don't think even a big switch like that does.
{{ts}} is purely a shorthand template. It could be subst'd quite happily. You can't do that with CSS classes that pull the data in from another document. There's no semantic difference between "{{tc|__bb}}" and "{{ts|bb}}". Both rely on a mapping from a shorthand to real CSS, and both have to be applied per-cell (or per-row). The technical difference is that one is spraying hundreds of CSS rules into the global CSS scope, and {{ts}} is not.
I don't even understand what {{tf/s}} is trying to achieve. Inductiveloadtalk/contribs 11:05, 19 August 2019 (UTC)
It was trying to do what {{ts}} does for block level formatting (DIV) more generally. It's not widely used, and could be converted if needed. ShakespeareFan00 (talk) 12:47, 19 August 2019 (UTC)
Why not just <div {{ts|ba}}></div>? Since one rarely has hundreds of tiny divs like you do table cells, I question the need for such shorthand anyway. And if you do find yourself needing hundreds of styling calls for divs, dedicated templates and/or TemplateStyles might be a better choice? There's no need to totally eschew HTML, IMO. Inductiveloadtalk/contribs 13:06, 19 August 2019 (UTC)

Page:Public General Statutes 1896.djvu/21[edit]

I've experimentally updated the first of the Acts in this to use a format more like that used on legislation.gov.uk, and in the process remove the sidenotes in favour of a simpler approach.

Before continuing , I'd like a consensus that this would be a reasonable method for proceeding, and an agreement as to the use of x.0, x. or x.1 to set anchors for singular numbered sections. (They can't use anchors of the form x directly, because those are the anchors the Page numbering script uses.) ShakespeareFan00 (talk) 11:54, 18 August 2019 (UTC)

Looks good to me, though I would do it like this since it preserves the original layout better. —Beleg Tâl (talk) 13:31, 18 August 2019 (UTC)
Agreed. So x.0 or x.1 as a numbering convention for single level 1 paragraphs? (0.0) would be the Preamble... ShakespeareFan00 (talk) 14:38, 18 August 2019 (UTC)
Sure, works for me. —Beleg Tâl (talk) 15:30, 18 August 2019 (UTC)
Which? , I'd like to leave a note so others formatting, know which to use to be consistent.ShakespeareFan00 (talk) 16:51, 18 August 2019 (UTC)
Oh, I thought you meant x.0 for part 0, x.1 for part 1, and so forth. Whatever you think makes the most sense. —Beleg Tâl (talk) 01:39, 19 August 2019 (UTC)
What I was proposing was 1.0, 2.0 , &c. for sections numbered 1., 2. &c. but 1.1, 2.1, &c. for those that lead directly into a sub section i.e those 1.—(1), 2.—(1) &c. in the original, (with obvious addtions for further sub-levels). Does that meet with approval, because I was wanting this to apply across a number of works. As you I should use what makes sense (and document it I suppose). ShakespeareFan00 (talk) 07:46, 19 August 2019 (UTC)

Automating a cleanup?[edit]

Is there a script that could do the semblance of this diff? over the remainder of the affected pages, being : Page:Public General Statutes 1896.djvu/66 to Page:Public General Statutes 1896.djvu/227

If not, no problems, it will just take a while. It should be simple as a Regexp replacement in AWB? ShakespeareFan00 (talk) 15:55, 19 August 2019 (UTC)

You'd need to set up a whole dictionary so that it can recognise if a word is made of two other words but is not itself a compound word. I think that's beyond what AWB can do. It's certainly beyond what I can do. —Beleg Tâl (talk) 16:24, 19 August 2019 (UTC)
@Beleg Tâl:, I typoed the diff number, Updated to the correct one, as I said a simple regexp replace.ShakespeareFan00 (talk) 16:37, 19 August 2019 (UTC)
If the example is truly representative, removing the ts stuff from the table body should be mostly trivial for somebody with a batch edit tool with regex support. Replacing the heading block with {{statute table/titles/header}} is less so, depending on the capabilities of the tool and how much variability there is in that block across pages. --Xover (talk) 18:15, 19 August 2019 (UTC)
If {{statute table/titles/header}} is always in the header and it is guaranteed to be in the form {{rh ....}}{|...., it is feasible.Mpaa (talk) 19:56, 19 August 2019 (UTC)

PDF Combiner?[edit]

Does anyone have a script for combining PDF files together? Commons:Category:The_Public_General_Acts_and_the_Church_Assembly_Measures_of_1948,_Part_II ShakespeareFan00 (talk) 18:07, 20 August 2019 (UTC)

I have had good success with PDFsamBeleg Tâl (talk) 18:34, 20 August 2019 (UTC)

Cleaning up the Statute Tables...[edit]

Feel free to reason that as I created an overly complex layout, I should do my own cleanup, but if anyone wanted some tedious, mind-numbingly repetitive "cleanup" tasks to just get on with:-

Any other typo or transcription errors that can also be cleared up in the process would be a bonus. ShakespeareFan00 (talk) 20:23, 20 August 2019 (UTC)