# Wikisource:Scriptorium/Help

 ←Scriptorium Scriptorium (Help) Archives, Last archive→
 The Scriptorium is Wikisource's community discussion page. This subpage is especially designated for requests for help from more experienced Wikisourcers. Feel free to ask questions or leave comments. You may join any current discussion or a new one. Project members can often be found in the #wikisource IRC channel webclient.

## HotCat not functioning?

I have HotCat selected in the gadgets but it's not working on WS but works on the commons. Have I missed something? — Ineuw talk 18:53, 2 January 2014 (UTC)

I may not have asked the question properly. Is anyone using HotCat on Wikisource and is it working? — Ineuw talk 11:02, 3 January 2014 (UTC)

## TOC Formatting

You made a great start! The details can be confusing. I made edits to show you one way of doing it. The main article page refers to the three page scans: #6 with the cover, and #8 + #9 for the TOC. On scan page 9, we can move the column headings for chapter and page into the no include at the top. The table will appear continuous with the previous page of the TOC, so only one set of headings are needed. For the page numbers on the right column of the TOC, they do not need to link anywhere. Page numbers are less important for the on-line reader. On the pages, I replaced the <references/> with the template {{smallrefs}} template at the bottom of each page. This formats closer to the original scan. Within each chapter, I added sections which can be used from the TOC. See documentation at MediaWiki Labeled section transclusion -- DutchTreat (talk) 12:01, 4 January 2014 (UTC)

## Inclusion guidelines for American poems published 1881.

Is more searching needed? -- unsigned comment by User:Twigs_Vorron (talk) .

Going by as much detail as was given, I'd say they are OK for inclusion here. -- George Orwell III (talk) 07:55, 6 January 2014 (UTC)

## Songbook transclusion help

Looking for help properly transcluding a songbook to mainspace. This will supersede the current extract now in mainspace, although it might be best to use a different title. I'm not even sure if I'm not even using the proper series title for these songbooks, they seem to have multiple.

I have a later edition of the songbook already done, that can be compared to, though I'm not sure if this is entirely done properly. I just went the route most obvious to me.

Possible, though minor, issues may include choosing how to name the subpages, as well as whether the little notes spread throughout the book, not directly related to the songs they follow, should simply be transcluded along with the nearest song or given a separate subpage. Some of these notes have titles, EG being little poems themselves, but are not listed in the book's index. I have the songs, at least, prepared with section labels.

And if that's not enough, working through the versions pages for each of these songs will be quite a feat! djr13 (talk) 23:08, 10 January 2014 (UTC)

## Index page TOC and length

According to Help:Beginner's guide to Index: files, the table of contents field on the index page can either be type manually, or transcluded from the book itself if there is one in the file:

What, however, should be done when the table of contents is too long for transclusion? There apparently is a limit in the MediaWiki software on transcluded length, and if you trip that limit it blanks the page unhelpfully.

See, for example, Index:An introduction to the early history of Christian doctrine to the time of the Council of Chalcedon.djvu. This text has a 10-page table of contents. (The table of contents is also ridiculously detailed, which accounts for the length. It could double as an outline of the work.)

What is the appropriate thing to do in this situation? Would it be better to not include the entire table of contents on the index page? Or perhaps to manually enter a short-form table of contents with just the chapter titles?

Thanks. Mukkakukaku (talk) 00:08, 11 January 2014 (UTC)

With overly detailed TOC, I just put a cut-down version on the Index page with just the "chapter" names that I'm going to create as sub-pages. e.g. Index:A Critical and Exegetical Commentary on Haggai, Zechariah, Malachi and Jonah.djvu and Index:History of England (Froude) Vol 5.djvu, which are two most recent ones I've done this for. Beeswaxcandle (talk) 00:24, 11 January 2014 (UTC)
A huge part of the "bloat" there is the application of the Greek missing template. Its possible if somebody properly replaced those missing characters and removed the missing template in the process, the overall post-expand template size might come in under the limit. -- George Orwell III (talk) 02:21, 11 January 2014 (UTC)
Another option is not to use {{TOC row}} but directly table markup.--Mpaa (talk) 09:39, 11 January 2014 (UTC)

Thank you everyone for your suggestions. I decided to just hand-craft a shortened form of the table of contents using just the chapter titles. Thanks. Mukkakukaku (talk) 19:48, 11 January 2014 (UTC)

I've inserted the missing Greek. Angr 17:29, 12 January 2014 (UTC)

## Error

Why does it say "Error: No Such File" on Index:Farewell letter to Soviet Russia.png? --Wylve (talk) 07:07, 11 January 2014 (UTC)

Because it’s an image file, I think you have to give the pages in the work as separate links. The <pagelist/> tag won’t work here. I’m not too sure about the technical side of it, though. —Clockery Fairfeld (talk) 07:18, 11 January 2014 (UTC)
Ok, thanks. --Wylve (talk) 08:37, 11 January 2014 (UTC)

## Sidenotes pointer request

Can someone please point me to a work that uses left and right (inset) sidenotes so I can copy the formatting for this work? Thanks, Londonjackbooks (talk) 19:20, 12 January 2014 (UTC)

Thanks... How will that transclude into the Main? Will inset headers be on one side or both? Seems one side would be preferable. Londonjackbooks (talk) 19:40, 12 January 2014 (UTC)

Of course I realise this is not what you were asking for at all, but recently I made a template for use in Mexico of the Mexicans which I think could be fairly easily "bent" into what your work needs without resorting to actual side-notes. What do you think of the possibilities of this? Yes: the bolding and centering of the note need more work. Viewer2 (talk) 19:45, 12 January 2014 (UTC)
The text of the inset headers are not centered in the original. Ideally, text would be left-aligned (as opposed to centered), and have less padding space. I'm not against using "raw" formatting/markup as opposed to a template (something similar to this—only better still), but I am wiki-markup challenged. Londonjackbooks (talk) 20:06, 12 January 2014 (UTC)
I took you quite literally and converted it to direct mark-up which I think is pretty close. To achieve the mirror effect (a left inset) would require use of <span style="float:left;font-size:smaller;line-height:70%;margin:0.7em 1em 0.7em 0;width:7em;">"The force of heaven-bred poesy."</span> (Note: the only changes are to float:—left or right; and to margin:—the 1em and the 0 swap places.) Viewer2 (talk) 20:24, 12 January 2014 (UTC)
Further note: you may need to experiment with width:—try to find the lowest amount which achieves the wrapping you desire (or you could cheat and insert <br/>s wherever you want.) But for consistency throughout the work I would recommend choosing a common value for all (of these) spans. Viewer2 (talk) 20:30, 12 January 2014 (UTC)
That is much better, thanks! I took the liberty of increasing line height to 100% and making the text bold. Thanks also for the note/tips above. Londonjackbooks (talk) 20:37, 12 January 2014 (UTC)
Always forget to mention one more thing! Worth remembering (particularly later in transclusion); if you find two notes overlap because your screen is wider than the printed page, adding a {{-}} between the lowest possible paragraph (if there is one or more) between the overlapping notes will space the paragraphs apart automatically and avert the overlap. (I know I did not express that well—if you notice it happening and can't figure out the foregoing please remind me, because I assure you the cure is simpler to show than it is to explain!) Viewer2 (talk) 20:55, 12 January 2014 (UTC)
Thanks. That happened to me when I tried {{float left}} on the following page; another reason why I went looking for another option. I'll make note of your {{-}} tip, thanks. Londonjackbooks (talk) 21:00, 12 January 2014 (UTC)
if you are interested, I recently learned about {{float box}}, see Remarks_on_Some_Late_Decisions_Respecting_the_Colonial_Church.--Mpaa (talk) 21:51, 12 January 2014 (UTC)
Thanks. Question: with either option, what is the layout like in the Main? Preferably, the inset headers will only appear on one side. Is there a way to make that happen? Do we want the headers to be on both sides in the Main? Londonjackbooks (talk) 22:00, 12 January 2014 (UTC)
If I got your question, I would put all the notes on the same side. Left/right on paper is to have the notes always on the outer margin of the page (depending if it is even or odd). As we do not break pages, might as well put them on the same side. Would be interesting to see how it renders on EPUB or similar.--Mpaa (talk) 22:40, 12 January 2014 (UTC)
I'll place all of the notes on the left then. Thanks, Londonjackbooks (talk) 23:07, 12 January 2014 (UTC)
I did not know about {{float box}} before. Looks very slick, and makes my suggestions look properly clunky. Viewer2 (talk) 22:36, 13 January 2014 (UTC)
This looks very messy; while I don't think {{float box}} would be any better(?) Unfortunately, no paragraphs are handy to make use of {{-}} Londonjackbooks (talk) 00:37, 14 January 2014 (UTC)
Whilst obviously not a brilliant solution, how about this? I narrowed the top and bottom margins on the two single-line insets, and probably more controversially, moved the positioning of the lowest one on the previous page a little higher. This happens to work on my settings: hope it does for you too? Viewer2 (talk) 02:39, 14 January 2014 (UTC)
A bit better: Two tiers as opposed to three in the Mainspace (from my viewpoint). I plan on setting the Mainspace pages to Layout 2 (if I can get it to work...see Help request below), which will help output some more. Thanks, Londonjackbooks (talk) 02:59, 14 January 2014 (UTC)
How about now? Like a fool I forgot a styling in the original specification. It should have read (for the left-inset case you are using throughout this work): <span style="clear:left;float:left;font-size:smaller;line-height:70%;margin:0.7em 1em 0.7em 0;width:7em;">"The force of heaven-bred poesy."</span>

The addition of "clear:left" instructs HTML to move the floating element down to where it will next fit automatically (literally: "keep my left margin clear".)

This is only worth reworking on problem transclusions, as it will have no effect on most cases. Viewer2 (talk) 03:35, 14 January 2014 (UTC)

I applied the change to other problem pages (cases). I'll use the new markup from now on. Seems to be only one hard case now (page 27 [DJVU page 57]). Thanks for all, Londonjackbooks (talk) 03:58, 14 January 2014 (UTC)
I don't think I can help with 27(57), because it looks correct from my perspective. What is misbehaving for you? Viewer2 (talk) 04:06, 14 January 2014 (UTC)
Page 27 seems to work now. Must have been a lag in my system. All good. Londonjackbooks (talk) 04:02, 14 January 2014 (UTC)
Sehr gut! Viewer2 (talk) 04:08, 14 January 2014 (UTC)

## Layout display question

I have The poor Sisters of Nazareth set to view with Layout 2 using {{default layout|Layout 2}}, but it doesn't seem to be working. It used to work. Any thoughts? Thanks, Londonjackbooks (talk) 15:56, 13 January 2014 (UTC)

The override code currently only affects users who have never selected a layout manually. Users who picked a layout on any page via the sidebar will continue to see that layout on all pages. There has been discussion of adding a gadget or preferences setting to make this adjustable. For now, clearing cookies should reveal the behavior you want to see. --Eliyak T·C 10:22, 14 January 2014 (UTC)
Thanks. Londonjackbooks (talk) 15:53, 14 January 2014 (UTC)

## Index:Agreement relating to Malaysia (1963) Malay Texts.djvu

What's the template for a language transfer? - Non english work. ShakespeareFan00 (talk) 09:03, 14 January 2014 (UTC)

## The ongoing saga of the sidenotes

Template:Sn-paragraph/sandbox and {{sn-note}} where my current efforts on this.

A logic check of these would be appreciated. ShakespeareFan00 (talk) 14:40, 14 January 2014 (UTC)

I tried to do some formatting using template dottec toc page listing, on this page. Is there an experienced editor who can check this, before I continue? Thnx, Dick Bos (talk) 19:11, 14 January 2014 (UTC)

Check it now. Better? If you see the changes, you can get the gist of it.--Mpaa (talk) 20:40, 14 January 2014 (UTC)
Thank you for helping. I again made some small changes. Your solution created rather a strange effect on the index-page. I think it will do now. But before I continue, could you please check it again? Greetings, Dick Bos (talk) 19:40, 16 January 2014 (UTC)

## How to add "as of" date?

Hello, I've found my way here from Wikidata and I'm trying to figure out how you handle amended documents. You have British North America Act, 1867, which is the original 1867 version of the statute, and Constitution Act, 1867, which is the same document with all of the amendments made over the last 147 years (including the name change). However, The latter document is missing the most recent amendment, which came into force in 2011 (the last amendment your page contains came into force in 1999). Until I get a chance to update the page, I want to add "as of 1 April 1999" to the header, but the Template:Header doesn't seem to have an "as of" parameter. What's your standard practice for tagging something like this? Even after I make the updates I want to mark it "as of 2011" in case no one updates it next time a Constitutional amendment is passed. --Arctic.gnome (talk) 00:45, 16 January 2014 (UTC)

Information such as that would normally go in the notes section of the header template (currently bloated by a snippet taken directly from Wikipedia - a practice no longer really practiced anymore btw). Technically, we operate under the assumption that hosted works are static and not subject to any future changes so we don't have anything like the field you describe by design - but this instance seems to have been grandfathered in due to its creation preceeding the policy nevertheless. Otherwise, info such as that could/should also go in the "notes" section" of the textinfo template (when one exists) located on the article's talkpage. -- George Orwell III (talk) 01:08, 16 January 2014 (UTC)
If we prefer stable versions, should I move the existing Constitution Act, 1867 to Constitution Act, 1867 (as amended in 1999) and create a version with the new amendments at Constitution Act, 1867 (as amended in 2011)? --Arctic.gnome (talk) 02:17, 16 January 2014 (UTC)
No there is no point in doing that at this stage of the work's timeline & modifications. The best thing to do is make it current & complete by adding the since ratified amendment(s). -- George Orwell III (talk) 03:36, 16 January 2014 (UTC)

Thanks for your quick and helpful replies. I have one more question. We have Constitution Act, 1867 (annotated) (plus several other annotated Acts). These annotations give important information like the date a given section came into effect. I have two concerns about these pages. The first concern is about copyright. These annotations come from versions of the statutes published by the Canadian Department of Justice (e.g., see here), and I can't tell whether the annotations may be freely distributed like the laws can. The terms of the DoJ website suggest that they can be redistributed, but it's under a different licence than the laws themselves. My second concern is that we don't really have a firm publication date for the annotations. The website has been updated more recently than the date of the last amendment, so it might be necessary to cite the annotations to a print version of the annotated laws. --Arctic.gnome (talk) 18:08, 16 January 2014 (UTC)

Well our policy on annotations isn't set in stone quite yet.

Regardless, I don't see any links to an "annotated" version at the DoJ site you linked - are we sure these are published annotated versions or are they User: created annotated versions based on the published DoJ versions? The latter would be fine for inclusion on en.WS per the previously linked policy but the former would need to have an acceptable license of some sort in order to be able to host them here. If you are thinking of material linked from the "notes" section(s) or similar, which appear to be in footnote/reference form - those are fine to reproduce and are covered by the same license as the rest of the content (afaict).

As far as the publication date goes, again depending on if User: generated or if DoJ published, we try to do the best we can when ascertaining such dates only in the case of formally published works. Whatever the site's "last modified" date is would be what we use in those cases I suppose. For User: created annotations, a review of the article history should help nail down the date of the last edit concerning creation of the annotated content. Hope that helped. -- George Orwell III (talk) 21:27, 16 January 2014 (UTC)

## Newspaper reports

I have a short (35 line) newspaper report from 1920 that I would like to refer to on at least two pages of Wikipedia. The original is microfilm to which I have limited access, in other words I can't easily get it scanned. I'm quite happy to copy type it. Is Wikisource the appropriate repository or if not, where is? Thanks, Martin of Sheffield (talk) 17:38, 18 January 2014 (UTC)

Yes, we are the appropriate repository. In terms of titling the page, so that it can be linked into any future use of the particular issue, use Newspaper name/Year/Month/Day/Article name. An example is at The New York Times/1915/10/04/Correction by Mr. Tesla. Beeswaxcandle (talk) 17:52, 18 January 2014 (UTC)
Thanks, I've done my best, please see The_Chatham_News_1920-12-20. It's my first edit in Wikisource, so please let me know if I've messed up somewhere! Martin of Sheffield (talk) 23:21, 18 January 2014 (UTC)
I will second Beeswaxcandle's suggestion of using subpages for issue date and title of article. When we have the publisher The Chatham News as the parent article, then it allows for a description of the source with room to easily navigate between multiple issues. If you need help moving the article into subpages, please let me know. -- DutchTreat (talk) 01:06, 22 January 2014 (UTC)

## How to mark a duplicate for deletion?

This and this are the same work, same edition. One could even argue it's actually the same file uploaded twice to commons with different names. How does one go about marking one version for deletion as a duplicate? Mukkakukaku (talk) 23:02, 18 January 2014 (UTC)

Here (enWS) you can mark one with {{sdelete|G4 "reason"}} and in the reason put a link to the one you want to retain. G4 indicates that the page is redundant. As part of deleting an Index any pages in the Page: namespace need to be deleted as well, so make sure that anything useful has been moved across to the version being kept before request a speedy delete. On Commons, once there are no pages anywhere linking to the redundant version, you can request deletion under their deletion process. Beeswaxcandle (talk) 23:16, 18 January 2014 (UTC)
Thanks. I found yet a third index for the exact same work, so I tagged two as duplicates. Hopefully there aren't any others lying around. The work itself has a 'ready for match and split' status, which doesn't appear to have started yet, so speedy delete should be OK. Mukkakukaku (talk) 23:22, 18 January 2014 (UTC)

## Toolbars shift their position in the editor

Everything is working fine with the minor exception that the user defined and the predefined toolbars alternate their positions in the editor. I was wondering if there is a .js solution to keep their loading order consistent? — Ineuw talk 14:07, 19 January 2014 (UTC)

Ineuw, that happened to me also. I still used it like it was and within 2-3 days it corrected itself except for one item (View History) disappears. Perhaps George was experimenting. —Maury (talk) 15:00, 19 January 2014 (UTC)
Thanks Maury, this problem has been around for a very long time but since there were other more urgent issues, I never bothered with it. I vaguely remember Inductiveload experimenting with this issue but since he's not here for the time being, I was hoping someone resolved the issue with some "wrapper".— Ineuw talk 15:21, 19 January 2014 (UTC)
Not this time fellas. The shifting toolbars thing has been around forever - has something to do with the way or the order resources are being loaded but I couldn't tell you what or how to fix that if my life depended on it; sorry. And there is so much going in Maury's common.js file, that I wouldn't know where to start.

The only thing I can recommend trying is to first see if you can reproduce the "quirk" when you are not logged in. If the problem goes away, its likely the bug has to do with something within (or some combination of) your User: preferences and/or gadgets selected. If its still there when you're not logged in, then its something far more complicated.

Of course, this is over simplified when it comes to troubleshooting and won't apply to something like custom toolbars where you need to be logged in to enable that in the first place. Nevertheless, experimenting with your preferences can only help isolate the cause. Finally - some stuff just goes bad because its obsolete code-wise and is no longer being developed/maintained (hint, hint). -- George Orwell III (talk) 16:44, 19 January 2014 (UTC)

I have no problems with my minor change after the initial problem. Even then I just kept going with the flow. All I have to do now it click on "reload" to see "view history". We love ya George, you keep things going so that what we have is due to you. You've helped us a hundred times over. I have no complaints. It works fine as it is. Kindest regards, —Maury (talk) 16:57, 19 January 2014 (UTC)
This happens to me at other Wikisources too: French, Multilingual, and Welsh. Angr 17:31, 19 January 2014 (UTC)
For me too, it has been like that for a long time here and in other Wikisources as well. --Zyephyrus (talk) 19:37, 19 January 2014 (UTC)
You folks must be aware that the "old" toolbar scheme has been deprecated for some time now. Just because you can manage to pull something into existence around here doesn't really mean that its truly supported. If you don't like WikiEditor (or its eventual replacement, VisualEditor) then at least dump this toolbar nonsense and move those characters and inserts to CharInsert already. All you need to do is add something like this...
// CharInsert specific
window.charinsertDontMove = false;
window.editToolsRecall = true;
window.charinsertCustom = { User: ' Æ  æ  Œ  œ  à  á  â  ä  è  é  ê  ë  î  ï  ñ  ô  ö  û  ü  —  ␥‽  #REDIRECT.[\[+]] ' };
if(window.updateEditTools) window.updateEditTools();

.... to your common.js file and your done. Those characters can then be found on the User menu of what use to be EditTools (deprecated -- replaced with Char[acter ]Insert).

At the very least, please consider porting your buttons over to CharInsert - you're just prolonging the agony for everybody else by artificially keeping this 'monobook-love' around for really no good reason anymore. -- George Orwell III (talk) 20:42, 19 January 2014 (UTC)

I suppose I use the "old" toolbar because I have never changed anything with it. I use Vector which is default. I never add to or remove common.js because you, George, have always adjusted that by adding to or removing portions like you did earlier today. I do have a wonderful java script created by InductiveLoad that allows for color background (I use grey) and text (I use black text) which allows me to work. Otherwise all white background hurts my eyes (eye strain). CNN reported on this subject just a few days ago and I have been asked how can I look at the computer so long by friends who can't. I am not opposed to using WikiEditor but it appears, from statements above, I may as well as wait for VisualEditor. How are we to know when these newer editors come along? I don't spend much time reading in this area. I prefer to work on images and text not set up a new editor which should be done automatically as "default"--or at least alert every individual the option is there and have a screenshot of what it looks like. I do nothing fancy so I haven't had a need to have a different editor. This "old" editor does all I need. I don't bother going to other areas with different languages and this old editor works on WikiPedia. Simplify, Simplify, Semper Fi --Ben Franklin. —Maury (talk) 00:43, 20 January 2014 (UTC)
I don't use the toolbar to insert characters, I use it to zoom in and out of images and to open and close the noincluded headers and footers. Angr 08:39, 20 January 2014 (UTC)

## Useless Toolbar Buttons vs User defined buttons

The following toolbar buttons are on my editor and I never use them. They are a waste of space where preferred buttons could be added. Toolbar buttons should be easily chosen and removed by users. B, I, Ab, image of world for external link, image of frame for Embedded Link, image of a yellow trumpet for "file link", Square root of N, letter W inside red circle for ignore wiki formatting, Your signature with timestamp, horizontal line, Abc for small caps, poem & /poem, Hws, Hwe. —Maury (talk) 01:20, 20 January 2014 (UTC)

You can disable these buttons to gain extra space. Copy the code from HERE and let me know which other buttons you wish to disable but not on my list.— Ineuw talk 12:47, 20 January 2014 (UTC)
Thank you, Ineuw. It didn't work though. The useless buttons were retained. It removed my ae AE oe OE which I do use and kept the useless buttons. No problem though, I never use those useless buttons previously described. They are just extras that are never used. Respectfully, —Maury (talk) 22:17, 20 January 2014 (UTC)

/* Hide unused buttons */
#mw-editbutton-link { display: none !important; }
#mw-editbutton-extlink { display: none !important; }
#mw-editbutton-image { display: none !important; }
#mw-editbutton-media { display: none !important; }
#mw-editbutton-math { display: none !important; }
#mw-editbutton-headline { display: none !important; }
#mw-editbutton-signature { display: none !important; }
#mw-editbutton-hr { display: none !important; }

Did you place the above in User:William Maury Morris II/common.css? — Ineuw talk 18:13, 21 January 2014 (UTC)
I am sure I did. It looks very familiar. I looked it over before placing it at the bottom of the java script. In looking at it now I do recall seeing "math" but I will try again. However, it is just an experiment because those buttons do not bother me in any way as I stated above. The idea was not to just remove them but to replace them with other buttons that could be of some use. I have no idea what any other buttons would be worthy though. I did not use and do not believe that is to be included. Respectfully, —Maury (talk) 21:40, 21 January 2014 (UTC)
Yes, identical outcome Ineuw. But it does not matter. I don't use the buttons. They're all worthless. Are there any good ones to be inserted? What buttons do you use? The best script I have is the "eyestrain" color code. Respectfully, —Maury (talk) 21:53, 21 January 2014 (UTC)
My tool-bar has 24 buttons totaled and I use none of them. There is no need for them. I can and do type in the codes instead of clicking on buttons. e.g. small caps sc, bold, italics, et cetera can all be done by hand. I have no problem with this, they're just there. —Maury (talk) 22:05, 21 January 2014 (UTC)
Please correct me if I am wrong, but from what you wrote I must assume that you placed the code in your .js (javascript) page. That's not the same as the common.css page indicated above, because it was not yet created. The User:William Maury Morris II/common.css needs to be created, the above code pasted and this makes the listed buttons disappear. If this works, I will fish out the other codes for the rest of the buttons, and you just add them to the list. At this point, this is the only way I know how to hide the toolbar - by hiding the individual buttons.
I also noticed that you already have some custom buttons declared in your .js file. Do they show up along the 24 standard buttons? — Ineuw talk 22:26, 21 January 2014 (UTC)
Ah! so there is the difference. You are correct as usual, Ineuw. I added what you posted to my common.js which made my custom buttons disappear and left the original old buttons listed above. As you state, I do not have a common.css I thought .css = cascading style sheet. Beeswaxcandle created a couple of custom buttons for me that I asked for but no longer use. The English pound button is important to me and I use that when I encounter it in texts but it is also available elsewhere. There is an old saying my friend, "If it ain't broke don't fix it" and I have nothing on my toolbar that doesn't work. If I tinker I may lose my eyestrain color code which could be retrieved but this situation is a code person's exploration. It serves me no purpose that I am aware of to just remove all buttons. Let them sit there. Our mutual friend, Raul, has returned from a long trip and we have books we want to start working on. Respectfully, —Maury (talk) 23:14, 21 January 2014 (UTC)

## Overfloat image

A fix required here. Thanks in advance. :) —Clockery Fairfeld [sic] 17:47, 23 January 2014 (UTC)

I've split the image in two as it should be, but again my HTML is lacking. Perhaps someone can add the proper code to complete my efforts.— Ineuw talk 21:44, 23 January 2014 (UTC)
This is exactly how I wanted it to be. Thanks a lot, Ineuw, Eliyak and Mukkakukaku... Clockery Fairfeld [sic] 06:11, 24 January 2014 (UTC)

Cannot center a <div> caption of an image on a main namespace page. The image originates here Page:Popular Science Monthly Volume 87.djvu/208 and is diaplayed HERE.— Ineuw talk 20:09, 23 January 2014 (UTC)

I fixed the issue using the {{img float}}. Hope that helps. --Xxagile (talk) 20:19, 23 January 2014 (UTC)
Thanks for your quick response, but unfortunately this is not what I was looking for. The images & captions (some 8,000+ of them) have various standardized formats throughout the PSM project. The images and their captions vary in size independently. I used this page as an example (and a bad one at that because the image and text are both 430px), but there are many images using this independent caption style. What I was looking for, is how to center this specific non-template HTML <div> code.P.S: Just as it formats this response.— Ineuw talk 21:02, 23 January 2014 (UTC)
Oh ok. I think I understand what you mean, but unfortunately I don't know how to solve that problem (easily) either. Good luck. --Xxagile (talk) 21:51, 23 January 2014 (UTC)
Ineuw, if you'll forgive me for messing with the format of your reply -- is that what you intended? I added margin:0 auto; and changed the align:center-justify to text-align:justify;. Mukkakukaku (talk) 04:17, 24 January 2014 (UTC)
Mess with it all you want . . . . and thank you. This is exactly what I needed.— Ineuw talk 04:41, 24 January 2014 (UTC)

## page break and left margin

Hi there. Can anyone please help me with a paragraph that crosses a page break, and that should have a left margin (it has a fine block as well, by the way; but that runs without a problem). This is the example. Thanks, Dick Bos (talk) 20:14, 24 January 2014 (UTC)

See if it is OK. I leave to the template experts to see if we need to have a {{left margin/s}}, {{left margin/e}}.--Mpaa (talk) 21:09, 24 January 2014 (UTC)
I've been doing this sort of thing with blockquote tags. They seem to work in the footer of the first page and header of the second page. See Page:A Critical and Exegetical Commentary on Haggai, Zechariah, Malachi and Jonah.djvu/61 and the following to see it in action. Beeswaxcandle (talk) 21:43, 24 January 2014 (UTC)
Thanx, Mpaa and Beeswaxcandle! re Beeswaxcandle: I used the blockquote for testing in your book: Page:A_Critical_and_Exegetical_Commentary_on_Haggai,_Zechariah,_Malachi_and_Jonah.djvu/49 and the following. That works good. But..... When using it halfway the following page in a block the space between lines is not small, but the same as "normal" text. What's going wrong? Dick Bos (talk) 19:03, 26 January 2014 (UTC)
If you mean the list of people on /50, that's a series of paragraphs, so it has paragraph spacing. Beeswaxcandle (talk) 19:14, 26 January 2014 (UTC)
I think he's commenting on the perceived spaced between the lines, not between paragraphs. (Eg. if this was in a word processor, the property called 'line spacing.') Indeed, on page 50 of the above work, the top blockquote (which, by the way, contains a <p>aragraph) has line-height of 1.2em and the second blockquote has a line-height of 1.5em. The point I believe he is trying to make, that I agree with, is that within a paragraph, the line heights should be the same. The problem is that the {{fine block/s}} template declares class="fslhInherit" on the surrounding <div>, while {{fine block}} does not. This class causes the second set of paragraphs to inherit the line-height from a different declaration. Mukkakukaku (talk) 20:14, 26 January 2014 (UTC)
A "paragraph" (i.e. the wiki code mark-up variant) normally won't inherit such attributes, being block level elements themselves. The class definition forces any & all of the "paragraphs" wrapped within to inherit the containing div block's values. {{fine block}} is for one block of text (one paragraph, or one div acting like a paragrpah). Multiple paragraphs = multiple block elements so {{fine block}} (singular) is always the wrong template to use in those cases. Use the start & end variation instead. -- George Orwell III (talk) 20:42, 26 January 2014 (UTC)

It's still not quite clear to me. See my latest test on this page: Page:A_Critical_and_Exegetical_Commentary_on_Haggai,_Zechariah,_Malachi_and_Jonah.djvu/50. I now used fine block on one paragraph (two times), and the spacing is still different from the paragraphs below that are done with fine block/s and .../e. So even when I apply fine block to one paragraph, the line spacing is not altered.

Apart from that my objection to using the blockquote tag is, that it creates a left margin, and a right margin too. I only want a left margin. - Dick Bos (talk) 13:32, 27 January 2014 (UTC)

## oe or ae?

On this page, toward the bottom, in italics: Is it "cum fœnore" or "cum fænore"? Thanks! Londonjackbooks (talk) 23:52, 25 January 2014 (UTC)

Wikitionary says that fœnore is an alternate spelling to fænore (wikt:foenus). I'd go for æ. In either spelling it means "with interest". Beeswaxcandle (talk) 00:16, 26 January 2014 (UTC)
Much thanks. Londonjackbooks (talk) 00:18, 26 January 2014 (UTC)
I reckon it's an œ because (a) why would a font use the double-storey lower case a, then revert to a single-storey lower case a within a ligature?; and (b) in my experience when a font uses single-story lower case a in the ae ligature, the bottom of a's vertical may be lost but the top of the vertical nearly always presents as a small bump nestled between the letters. There's a good visual example at File:Ligatures.svg. Hesperian 02:43, 26 January 2014 (UTC)
See page 12 for an æ, which, as expected, uses the double-storey a. Therefore this is an œ. Hesperian 02:46, 26 January 2014 (UTC)
In many (most?) serif typefaces, both a and æ use the single-story a in italics but the double-story a in roman. Angr 08:17, 26 January 2014 (UTC)
A note about Wiktionary. When Wiktionary says "X is an alternate spelling of Y", it does not necessarily imply one or the other is the primary spelling. It is simply indicating that both X and Y are possible spellings found in print. --EncycloPetey (talk) 03:27, 26 January 2014 (UTC)

There's actually an example of an italic ae (Anima Poetæ) on the page in question as well... I didn't realize it until just now... Definitely a distinction between the two in the original. Noted. Thanks all, Londonjackbooks (talk) 04:10, 26 January 2014 (UTC)

## Missing images?

Using the 'Random transcription' link, I ended up at Index:A Glimpse at Guatemala.pdf. However, it appears that there's something glitching with the file, or perhaps with the software -- none of the pages have images (which makes it rather hard to proofread.) I opened one of the images in a new tab (via 'image' tab at the top of the page) and was greeted with this lovely error message:

 “ Error generating thumbnail Error creating thumbnail: convert: no decode delegate for this image format /tmp/magick-E0sH8bmV' @ error/constitute.c/ReadImage/532. convert: missing an image filename /tmp/transform_ec0b6ee14dd3-1.jpg' @ error/convert.c/ConvertImageCommand/3011. ”

I even tried going to the File:A Glimpse at Guatemala.pdf page, and that has broken thumbnails too. It's worth noting that the thumbnails are broken on Commons too. I can open the raw PDF file, so the file works. But I'm not sure what's wrong with the software's interpretation of said file -- or how to fix it.

Has anyone seen this happen before, or know of a fix or workaround for the problem?

-- Mukkakukaku (talk) 06:18, 26 January 2014 (UTC)

(see File:Cox and box.pdf) According to Commons, that file is "affected by MediaWiki restrictions". What exactly are those restrictions, I have absolutely no idea, but maybe you could upload a Djvu version of the file using another title...? Apart from that, I have no clue as to what could be done.

Of course, someone else might know better... —Clockery Fairfeld [sic] 06:27, 26 January 2014 (UTC)

Documentation seems to exist only in the relevant bugzilla bugs. You'll find links to these bugs at the top of Commons:Category:PDF files affected by MediaWiki restrictions. Hesperian 06:41, 26 January 2014 (UTC)
Looks like the server is running a very old version of ghostscript, but the devs are reluctant to update. Or maybe I read the bugs reports wrong. The official solution appears to be to "fix" the PDF file. Mukkakukaku (talk) 06:55, 26 January 2014 (UTC)
In addition to the PDF "bug" thing, something else is clearly off. The PDF on IA is ~24Mb and the one uploaded to Commons is ~33Mb. Seems corrupt to me - I'd try re uploading the PDF from IA again over the one currently on Commons for kicks. -- George Orwell III (talk) 06:59, 26 January 2014 (UTC)
I re-uploaded the version at IA and while the filesize is now right, the current version has 10 fewer pages. And appears to be still broken. Mukkakukaku (talk) 07:18, 26 January 2014 (UTC)

## Viewing page links in a sandbox

I am using one of my sandboxes to view the progress of a work. Is there some way I can view page numbers so if I find an error I can link directly to the affected page instead of having to search for the correct page page-by-page in the Index? Thanks, Londonjackbooks (talk) 23:26, 27 January 2014 (UTC)

if ( $.inArray( mw.config.get( "wgAction" ), [ "view", "submit", "purge" ] ) !== -1 ) { if ( !self.debug_page_layout // don't do anything on DoubleWiki or difference comparison views && document.URL.indexOf( "match=" ) === -1 && document.URL.indexOf( "diff=" ) === -1 && mw.config.get( "wgNamespaceNumber" ) === 2 ) { if ($( ".pagenum" ).length !== 0 ) {
if ( ! $.isEmptyObject( self.ws_layouts ) )$(document).ready( layout.init );
$(document).ready( pagenumbers.init );$(window).load( pagenumbers.refresh_offsets );
}
}
}

It should make pagenumbers and dynamic layout work on userspace pages that are transcluding from the page namespace. Prosody (talk) 03:48, 28 January 2014 (UTC)
Unless I applied incorrectly, I'm still not seeing page numbers... Londonjackbooks (talk) 04:15, 28 January 2014 (UTC)
Oh, sorry, I didn't really test that through the normal methods. It looks like the user javascript loads before some of the system stuff so it doesn't know about it. Try this one instead. I tested it normally and I got it to work.
$(window).load(function() { if ($.inArray( mw.config.get( "wgAction" ), [ "view", "submit", "purge" ] ) !== -1 ) {
if ( !self.debug_page_layout
// don't do anything on DoubleWiki or difference comparison views
&& document.URL.indexOf( "match=" ) === -1
&& document.URL.indexOf( "diff=" ) === -1
&& mw.config.get( "wgNamespaceNumber" ) === 2 ) {
if ( $( ".pagenum" ).length !== 0 ) { if ( !$.isEmptyObject( self.ws_layouts ) )
layout.init();
pagenumbers.init();
pagenumbers.refresh_offsets();
}
}
}
});

Prosody (talk) 22:17, 28 January 2014 (UTC)
Still not appearing. Thank you though, for and while you are making the attempt! Londonjackbooks (talk) 22:23, 28 January 2014 (UTC)
I believe this feature was pulled from other namespaces in order to have it work in the Translation: namespace a few months ago. Eliyak would be the one to tap to see if User: namespace can be included back again. Otherwise I'd just test in the mainspace for now and request a speedy deletion if the test page can't be recycled for final/finished tranclusion. -- George Orwell III (talk) 04:15, 29 January 2014 (UTC)
OK. Thank you, Londonjackbooks (talk) 23:39, 30 January 2014 (UTC)

## A problematic PSM Volume

This PSM volume has some pages marked problematic because they are too fuzzy to proofread, and now, in edit mode, the original is shrunk to a tiny image. I cleared all caches (WS page, volume & FF) but the problem didn't go away. Do others see the same problem as I do?

Furthermore, with all the pages I marked problematic, in the AI source of the Commons copy, and the two additional copies I found on AI are all clean. This makes me assume that the problem may not be with the originals. Can someone please help? Thanks in advance.— Ineuw talk 16:52, 30 January 2014 (UTC)

I don't know about the shrinking-image problem, as I don't find it affects me (I use FF 26.0). But maybe the fuzzy-page problem can be fixed by reuploading the file from AI...? Or you can try checking the copy you've downloaded, to see whether there's a problem in that file. —Clockery Fairfeld [t·c] 17:03, 30 January 2014 (UTC)
I'm not sure what's causing that. I'm not getting a tiny image but I am getting blurred text (and the zoom function doesn't change that). However, when I click on the "Image" link, I see the page image clear text. Purging locally hasn't helped. I've purged at Commons as well but I think that might take a while to take effect here (if it changes anything at all). Failing that, as I mentioned, the separate "Image" link works, so you could proofread from that for now (even if it is a little awkward). - AdamBMorgan (talk) 19:03, 30 January 2014 (UTC)
Thanks for all the input. Here is the image of a page with the shrunken scan. Earlier, only a few pages were so, but now the whole volume is like this. I have no problem downloading and uploading other copies from IA. I counted at least two more identical versions, but my concern is that I don't destroy the pages already proofread. Already posted a Help request to my DjVu Guru about how to protect the text layer, and will wait until he replies.— Ineuw talk 20:02, 30 January 2014 (UTC)
Randomly checked Vol 18 and the scans are OK, BUT someone changed the text layer width in Read mode. For the past years the text width was always 430px and now it's 520px. I monitor this using a pixel ruler so that inserted images are in proportion to the Page namespace text width. Can someone check on this please? Thank you.— Ineuw talk 20:09, 30 January 2014 (UTC)
While discussing these issues with myself, I suddenly remembered that there may have been new software update. Ineuw talk 20:13, 30 January 2014 (UTC)
Check those problematic pages now. That default ~430px has indeed been changed in one of the recent PR core updates (which more often than not will now "conflict" with any manual scan resolution settings added near the bottom of the Index: page form in edit mode - as was part of the problem here).

The other part always has to do with once such a conflict has been cleared and then trying to get Commons to refresh the entire File: --> Index: --> Page: framework properly. I find that unless you keep hitting purge there until a refresh is "instantaneous", wait up to 45 seconds afterwards and then look for Commons to refresh the File page once again on its own - only then is true Purge & refresh accomplished. Your mileage may vary. -- George Orwell III (talk) 00:03, 31 January 2014 (UTC)

## May I share a document with Wikisource?

My new manuscript, titled Knowledge For The People, has already been listed in the United Nations Public Administration Network online library. I would like to share it with Wikisource. I am not seeking remuneration, just to share important ideas. I am the sole copyright holder of the document.

My email provider sets limits on the size of uploads permitted, so I have placed a copy of the document in Dropbox. The document can be located and uploaded by going to the following link and logging in: https://www.dropbox.com/home/Public?select=KnowledgeForThePeople.pdf

If you accept this offer, please let me know if it works, at williamsheridan@rogers.com

I am not knowledgeable on copyrights but THIS SECTION may be relevant to your posting material here. In fact, the whole article is relevant. — Ineuw talk 15:19, 31 January 2014 (UTC)
I tried to open the link, but it requires sign in or something, in any case Wikisource:What Wikisource includes is also relevant. Based only on the title of the work, I would say it probably does NOT meet our inclusion criteria. JeepdaySock (AKA, Jeepday) 15:42, 31 January 2014 (UTC)

## Digraph issue

I'm having issues with a digraph on this page, near the bottom with the word alltud. In Welsh, this is a digraph l with a tilde going through it. I'm having issues getting the tilde to look right. For one, I have no digraph l on my computer, so I used two ls, each with a combining tilde on it, and for two, the tildes are close to the bottom of the letter, even though I used a middle combining tilde. Has anyone else had this issue and found a way around it?—Zhaladshar (Talk) 14:36, 31 January 2014 (UTC)

Just curiosity to know the unknown led me to to this wiki link and found and replaced the missing Unicode character ỻ. Apart from that, I think that the references are {{smallrefs}}— Ineuw talk 15:05, 31 January 2014 (UTC)
If you need any more weird Welsh characters, you might find some ready for cut-n-pasting toward the bottom of User:Angr#Toolbox. Angr 17:52, 31 January 2014 (UTC)
My computer can't view the character. Is there any way to make it visible using the nifty font thingy we've got going on Wikimedia sites?—Zhaladshar (Talk) 03:11, 1 February 2014 (UTC)

ɬɬ <--- what about now? -- George Orwell III (talk) 03:43, 1 February 2014 (UTC)

That I can see.—Zhaladshar (Talk) 04:31, 1 February 2014 (UTC)
Great, but that's not the character the page is using. What GOIII typed above is two copies of the IPA character ɬ (U+026C) next to each other. What the text is using is (U+1EFB), which unfortunately has very limited font support, meaning a lot of people can't see it. Nevertheless, I think we ought to be using the correct characters as far as possible, rather than workarounds. Angr 14:43, 2 February 2014 (UTC)
Correct of course. It's odd because I thought the DjVu Sans package supported both (among many other eclectic fonts), so if one could see mine, I thought there might be a good chance it's already present. Oh well; when a solution presents itself - please report back so I can see if it can't be added to CharInsert somehow. -- George Orwell III (talk) 15:49, 2 February 2014 (UTC)

## Table transclusion/formatting help

I need an extra set of eyes... Can someone please take a look at the table formatting on DJVU pp. 352-355 and see why it is not transcluding correctly in the Main? Thank you! Londonjackbooks (talk) 23:47, 31 January 2014 (UTC)

Seems to be okay now... Londonjackbooks (talk) 00:12, 1 February 2014 (UTC)

## Formatting error

In the page The Burglar, where pg. 111 begins, the formatting is broken (appearing as it would on Wikipedia if the line began with a space). I have no idea how to fix this, as I'm not an editor on this project and the interface is different, so I figured I'd mention it here instead. Sven Manguard (talk) 05:00, 4 February 2014 (UTC)

Thanks, fixed. Hesperian 05:22, 4 February 2014 (UTC)

## Can I upload these scans to Wikisource?

Can I upload a copy of a scan that someone else made to Wikisource so that I can make a searchable version of it? Specifically, I'd like to upload scans of some orders-in-council amending the Constitution of Canada, such as this one and make pages for the documents under the Template:Legislation-CAGov licence. --Arctic.gnome (talk) 21:19, 5 February 2014 (UTC)

The last time I tried uploading a Government of Canada document & image, it was rejected by Commons because, while the Canadian Parliament Archives emailed me the permission, it was not in the format demanded by Wikimedia Commons. It's best if you get the proper format from Wikimedia Commons and forward it to GoC archives for permission.— Ineuw talk 23:26, 5 February 2014 (UTC)
Arctic.gnome, if the underlying material may legally be hosted (it's not clear to me from {{Legislation-CAGov}} that it may, but I'll leave that to you) then the fact that someone else made the scan is of no importance: no copyright arises from "a mere mechanical scan or photocopy". Hesperian 01:17, 6 February 2014 (UTC)

Being able to use another's scan solves one hurdle. The other is where I can upload them. As I understand it, I can't upload them to Commons because they have two additional conditions attached to the licence beyond cc-by-sa--namely the requirement to be accurate and the requirement to state that they aren't official. If these requirements are acceptable to Wikisource but not to Commons, what are my options? Can I transcribe the texts to Wikisource without uploading an image to Commons? Can I upload the image to Wikisource instead of Commons? --Arctic.gnome (talk) 03:20, 6 February 2014 (UTC)

We work on a priority order. 1) Host them at Commons if at all possible [this makes them available to all wikis, not just ours] 2) if Commons cannot take them, and they are public domain documents (or equivalent) in the US and fit within WS:WWI, then they can be hosted at English Wikisource. That said please ensure as part of the WS:WWI that you look at the licensing and also Help:Copyright tags.

Re the scan type, it is what works well in our side by side system. If we have PDF or DJVU they have text layers that can be scraped and imported. If it is a jpg or something else the system recognises then you have typing or copy and pasting to do. If it is something not recognised, then we a problem, though that doesn't mean that we cannot host the text, it just means that it is unsupported by the image (which is not our preference). — billinghurst sDrewth 11:21, 6 February 2014 (UTC)

Hi

Seasons greetings from Marathi language wikisource(mr). We tried to upload a India public domain book in PDF format. It showed upload completed but PDF document commons:File:Chhandorachanaa.pdf was not readable at all . We want and request some one upload document for us either on mr.wikisource.org or on commons. We need it for a collaborative wikisource writing project.

• Reffered and requested upload book is Chandorachana (Marathi:छन्दोरचना)
• Is writtern by : W:en:Madhav Julian (Marathi: माधव जुलियन) (January 21, 1894 – November 29, 1939)
• It is Public Domain copyright free due to expiry of copyright period in India Please refer licence commons:Template:PD-India {{PD-India}}
• The Book is available online at https://archive.org/details/Chandorachana

Earliest help will be apreciated.

Thanks and Regards Mahitgar (talk) 14:17, 7 February 2014 (UTC)

Does this work for you: Commons:File:छन्दोरचना.djvu? - AdamBMorgan (talk) 17:33, 7 February 2014 (UTC)

This has worked. Lot of thanks Thanks and warm greeting. For some technical reasons i have not been able to use djvu on PC. This has been very valuable support from your side. Regards

Mahitgar (talk) 08:04, 8 February 2014 (UTC)

## Request for help with TOC page listing

Can anyone pls help me with this little nasty problem on Page:The_Economic_Journal_Volume_1.djvu/7. The problem is at the lower part of the page, just above “NOTES AND MEMORANDA”. There is a link to four pages there. I can't get them in one row. This is how far I got. Thnx. - Dick Bos (talk) 12:13, 8 February 2014 (UTC)

The secret is parameter col3-width of {{dotted TOC page listing}}. The default width is only 2em, which is just about full with 3 digits, let alone four references + ancillary spaces and commas (which is why they formatted vertically.) I gave it 12em for the sake of this trial, but feel free (of course) to tweak that as you want. AuFCL (talk) 12:56, 8 February 2014 (UTC)
Thanks a lot. I'll soon try it in another spot. Dick Bos (talk) 13:50, 8 February 2014 (UTC)
I forgot to mention: to make the page-numbers column completely "set-and-forget", try setting parameter |col3-width=auto. The price you pay is ragged ends to the dot leaders, but you might find it the simplest option. AuFCL (talk) 00:09, 9 February 2014 (UTC)
Last suggestion retracted, as it does not appear to work well in some browsers. AuFCL (talk) 16:35, 10 February 2014 (UTC)

## Non english charecters...

Can someone that's familiar with the relevant languages look over this and insert the appropriate characters?

I've tried to make intelligent guesses in places, but would appreciate someone else taking over.ShakespeareFan00 (talk) 09:31, 10 February 2014 (UTC)

I've looked a few random pages and can't see any non-Latin characters. Could you give some pointers as to what the problems are (page numbers, particular language, &c.)? Beeswaxcandle (talk) 05:23, 12 February 2014 (UTC)
https://en.wikisource.org/wiki/Page:Adapting_and_Writing_Language_Lessons.pdf/185 - Thai. For starters.. ShakespeareFan00 (talk) 23:19, 12 February 2014 (UTC)
First, that's not Thai, or else I would suggest you don't touch it. Hehe. However, as far as I can tell, it is IPA for Thai words, so you can just use that alphabet for it. For example, using text from the page:
nîi ʔaray
nîi mîitkoon
pàakkhîip
sǎmlii
ʔɛɛlkɔɔhɔɔ


OK It looks like IPA, but in places it's accented, and the accented versions are not in the Charcters box, I stil think it requires a specialist. ShakespeareFan00 (talk) 10:18, 13 February 2014 (UTC)

## Weird typesetting issue

I just worked on this page, and it has an unusual versification in it. Does anyone have any idea how to transcribe it? Would it be best just to use an image in its place?—Zhaladshar (Talk) 14:26, 10 February 2014 (UTC)

Yes.. Given its an inscription marking? ShakespeareFan00 (talk) 17:13, 10 February 2014 (UTC)
I took a shot at transcribing it in Unicode. Given that it's not like an etching or something I think it might be more appropriate to render it that way rather than with an image, even though I think most/all Ogham fonts are going to have that center line which isn't present in the text's typeface. Prosody (talk) 22:00, 10 February 2014 (UTC)
Erm, what font did you use? All I see are little boxes... Mukkakukaku (talk) 03:15, 11 February 2014 (UTC)
Oh, damn, that hadn't occurred to me. It's Segoi UI Symbol on Firefox on Windows 7. Default Windows 7 font, but it's not going to be available everywhere. Chrome on the same machine doesn't even use it. I don't think there's any support in Universal Language Selector even if that gets turned back on. I guess we'll have to fall back to using images. Prosody (talk) 03:29, 11 February 2014 (UTC)
Wait, the DejaVu family has Ogham. Anyone know what the list of fonts on the Universal Language Selector is? Prosody (talk) 03:50, 11 February 2014 (UTC)

## Integrating plate images into mainspace

I just finished proofreading The Indian Dispossessed (index), but before announcing its completion (however that's done), the book has a few plate images which don't have any obvious location within the chapters and text. How might these be best included in mainspace? djr13 (talk) 00:34, 12 February 2014 (UTC)

They should be included in the text as I did one formatted sample Page:The Indian Dispossessed.pdf/112, Main mnamespace = The Indian Dispossessed/The Nez Perces. Please look at the changes in the "File" image wrapper and caption centering. For some reason, when wrapped as before, the caption becomes noticeably offset. I also reduced the image size to 430px. My reasons for this are complicated, but primarily it's because the text width of the Main namespace Option #2 is about ~450-460px. An oversized image may lack esthetics.— Ineuw talk 03:14, 12 February 2014 (UTC)
Thank you for your help. I had thus far avoided doing it that way, as breaking paragraphs (usually unrelated to the image) for full-page plate images seems sub-optimal. And what to do with the frontispiece image? Sure there isn't another way? (Hmm, it looks like I was possibly supposed to name each mainspace subpage a generic "Chapter 1" etc....) djr13 (talk) 07:37, 12 February 2014 (UTC)
Just picking up on a couple of your questions:

For the chapter numbering, the generic version is only when the chapters are numbered either in the TOC or in the chapter headers. If the chapters don't have this, then the way you've named them is fine. It's really about linking to them from other works.

In re your other concern, have a look at Picturesque Nepal where we put the images in wherever they came in the book. The alternative is more complex, but can be seen in the earlier chapters of The Conquest of Mount Cook. The proofreader here chose to move the images to the end of paragraphs in the mainspace but left them where they are in the Page: namespace. This was done by using includeonly and noinclude tags. Both of these books have frontispieces that have been done slightly differently. Nepal has the frontispiece as the opening page before the title. Mount Cook transcludes them the other way around, so that the title page is up-front. If the cover image is a good one, then that can go in first. A recent example of this is On to Pekin. Beeswaxcandle (talk) 08:38, 12 February 2014 (UTC)

Beeswaxcandle is correct and I should have been more specific in regard to images. In the main namespace, one has the latitude to place images, especially full page images, at the beginning of a chapter. It's your choice. Already moved the image in The Indian Dispossessed/The Nez Perces to the beginning since it's the only image in that chapter. — Ineuw talk 17:24, 12 February 2014 (UTC)
I've gone with including the images at the beginning of each chapter, and including the frontispiece where it otherwise would be plus including the half-title before it where otherwise I excluded this as redundant. It's still a bit cludgy but seems workable. It seems like there's no good way to include such large, text-breaking images in mainspace due to format limitations. The most obvious alternative to me would be either folding them into thumbnails or offsetting them into the side-area in a similar way to what annotations are heading. I'll look into announcing the completion now. Thanks both. djr13 (talk) 21:07, 12 February 2014 (UTC)
I think it looks great. — Ineuw talk 21:46, 12 February 2014 (UTC)

## Oversized mathematical operators in print

I've been looking for oversized mathematical operators used in 19th century printed matter: like double length = signs, double size + signs etc., but have not found in any UTF-8 reference tables. Do they exist? — Ineuw talk 02:49, 12 February 2014 (UTC)

I don't think they exist as unique symbols per se, but perhaps try wrapping them in {{larger}} or {{x-larger}}? Eg. to get an affect like so: 7 ÷ 2  π .
Alternatively -- does the wikisource software support LaTeX? If it does, there are some commands to support resizing of portions of equations that may be possible to use. Mukkakukaku (talk) 04:58, 12 February 2014 (UTC)
Thanks for the reply. I believe WS does support LaTeX.— Ineuw talk 05:12, 12 February 2014 (UTC)
Would you please be so kind as to supply context/examples? I expect these are not quite what you are looking for, but there do exist UNICODE for (say) double- and triple-equals (&#10869;:⩵ and &#10870;:⩶ respectively), and so-called "heavy" plus (&#10133;:➕), minus (&#10134;:➖) and division signs (&#10135;:➗); and the dual-purposed "cross mark" (&#10060;:❌) paired with "heavy large circle" (&#11093;:⭕).
Thanks for your help. The start of this page is a perfect example of the hundreds of times it's used. Unfortunately, the above symbols are not the ones I was looking for, but the LaTeX symbols are.

WS does not support all of Latex, only the texvc subset (see mw:Extension:Math, but that gives you $=+-\times\div$ at least. AuFCL (talk) 14:22, 12 February 2014 (UTC)
These are the very symbols I was looking for since 1872 - when PSM started publication. . As for the LaTeX support I was only aware of {some] math, but didn't know that they can be used for just the symbols. My thanks to you both.— Ineuw talk 17:01, 12 February 2014 (UTC)
The first line of that page might be produced by something like:
 $\scriptstyle{+,~-,~\sqrt{}}$. In the same century Vieta… —with result: $\scriptstyle{+,~-,~\sqrt{}}$. In the same century Vieta…
Notes and hints:
1. Make sure that is a "normal" minus sign; dashes or mdashes send $into (lexing error) sulks! 2. Tildes (~) may be used to add spaces inside the [itex] string. Normally spaces are stripped out as if they were never there. 3. Although [itex] doesn't seem to analyse the command string too closely, thinks like \sqrt are considered to be functions and won't work (syntax error)) without at least empty {}s following. 4. I routinely enclose [itex] strings in \scriptstyle{}, mainly because I find the text is too large to match surrounding text. Of course your aesthetics and the situation may differ. 5. Be aware that [itex] produces its output as an image, with the side-effect it will not "split" when line-wrapping occurs. It is often wise to make several short [itex] blocks (say between commas) rather than one long one and risk later disappointment. Hope this is useful, and I am not merely repeating stuff you already know. AuFCL (talk) 22:58, 12 February 2014 (UTC) Could {{FI}} be of any use here? {{FI | type = math | width = 25% | file = [itex]sin x = {e^{ix} - e^{-ix} \over 2i}$
}}


$sin x = {e^{ix} - e^{-ix} \over 2i}$

Just wondering...... -- George Orwell III (talk) 00:00, 13 February 2014 (UTC)
AuFCL, thanks for those very important points, of which I was only aware of \scriptstyle. If you haven't done so, please consider including your instructions on the Math help page. Otherwise these will be buried in the Archive.
Wonder no longer GO3. I will be using {{FI}}. There are hundreds of formulas need to proofread/updated in PSM.
Many thanks to all for the above info.— Ineuw talk 04:27, 13 February 2014 (UTC)
Point of Order - please use math instead of user for FI's type= parameter. Both should produce the same output but one day User might be needed for a 4rth application or something. Thanks. -- George Orwell III (talk) 04:36, 13 February 2014 (UTC)
Note that the {{FI}} above produces quite blurry results, and evidently doesn't even work outside PNG mode. (I don't think it will show up at all in PDF output, for example.) —SamB (talk) 03:12, 17 February 2014 (UTC)

## Quick access icon link to the Commons is gone from WS images

Can someone please restore the quick link icon to the Commons image source. In one of the recent mw software updates, it disappeared. Thanks in advance. — Ineuw talk 03:17, 12 February 2014 (UTC)

Odd. I still see the icon linked to Commons on my File: pages (inline with header text to the top-right). Can anyone else replicate? -- George Orwell III (talk) 00:05, 13 February 2014 (UTC)
I can confirm the Commons icon is visible on for example, say, here. AuFCL (talk) 01:00, 13 February 2014 (UTC)
OK then - back to basics....

Ineuw, can you see the icon on

at all? -- George Orwell III (talk) 01:52, 13 February 2014 (UTC)
Yes, I can see both.— Ineuw talk 17:01, 13 February 2014 (UTC)
To further clarify, I can see the two icons GO3 has included, but there is no icon on the smiley image, nor on any other image from the commons.— Ineuw talk 17:05, 13 February 2014 (UTC)
I inverted the order in MediaWiki:Sharedupload-desc-here; see if that made any difference on any File: namespace page for you & report back. -- George Orwell III (talk) 22:27, 13 February 2014 (UTC)
Thanks for the effort but no go. Here is a screen image File:No icon link to the Commons.jpg I've taken earlier. This issue is an old one. Haven't had a commons link for many weeks. Would this be controlled in Preferences? — Ineuw talk 01:32, 14 February 2014 (UTC)

@Ineuw: GOT IT - Apparently (& Sadly) you are always going to be "less than whole" when it comes to certain defaults because you are in Canada but use [American?] English in your settings. Without your own Canadian MediaWiki message base, your "setup" surps from the US set when it can but fails unless a proper subset(?) is created in certain instances (or at least that is how I've come to observe this behavior to date).

Added MediaWiki:Sharedupload-desc-here/en-ca and that should "rectify" your missing icon issue. I guess it comes at the expense of what amounts to a "redundant" MediaWiki message.

Anyone have the same problem but is a "closer" subject of the Crown than Canada? -- George Orwell III (talk) 01:48, 14 February 2014 (UTC)

O.K. Now you point that out, en-gb (which would normally be my preferred choice; my earlier "working" observation was made as Preferences/Language/en—now [temporarily?] retracted) exhibits the same issue (i.e. missing Commons icon). Regards, AuFCL (talk) 02:33, 14 February 2014 (UTC)
@AuFCL - can you verify both of your prior observations still hold now? I just discovered [:MediaWiki:Sharedupload] (created 2005 & made a redirect in 2012) might be involved in this & just deleted our local copy of it to see what happens (if anything). It would be great if that restored everything but I'll add the gb if it didn't. TIA --- George Orwell III (talk) 02:46, 14 February 2014 (UTC)
No, only MediaWiki:Sharedupload-desc-here shows Commons icon (which should not be a shock, because that is what it really does) here. The others, all nada, since changing Preferences from 'en'→'en-GB'. AuFCL (talk)
Thanks. IMO - It's a bit crazy to add something like the Commons top icon to a MW message that isn't working across the board in the first place. I'm going to try finding a better MW message to host the icon so the crippled message [in theory] really is separate from the icon. Back in a bit. -- George Orwell III (talk) 03:13, 14 February 2014 (UTC)
OK @AuFCL: - {{Commons top icon}} is now hosted via [:MediaWiki:Filehist-help]. Please check any File: page to see if the icon appears (& works!) like it should no matter the language setting in use. Only difference, now, should be one has a FMbox (for the blind?) for a default message while the other(s) use the system standard default, plain-text message w/ link to shared file description info back on Commons found just below the file-size/mime type, etc. info (The icon should appear in the top right corner regardless!) -- George Orwell III (talk) 03:27, 14 February 2014 (UTC)

Scratch all that attempted 'moving around', en-ca & en-gb created but all 3 call Template:Sharedupload-desc-here instead of hosting the same stuff 3x in the MW namespace. Please report in now that this seems like the "final" solution moving forward. -- George Orwell III (talk) 04:10, 14 February 2014 (UTC)

Many pardons for delayed response (Real Life™ interfered.) All O.K. re: Commons icon again this side now. Thank you. AuFCL (talk) 04:15, 14 February 2014 (UTC)
My hero. Just another heartfelt thank you GO3. It works! — Ineuw talk 05:36, 14 February 2014 (UTC)

## PROOFREADPAGE - Both the default and auto edit-summary texts based on status no longer being populated

originally titled: On Page creation, "Not proofread" is not showing up in the Summary

Since I've been on a roll of success today, would it possible to display the default "Not proofread" in the Summary field when the page is created? This used to be so several software updates ago. I request this because most pages need proofreading.— Ineuw talk 09:56, 14 February 2014 (UTC)

• Verified (XpPro, IE8).

In addition, when opening edit mode on existing pages already given a PR status, the corresponding edit-summary text matching that current status once was pre-populated in the summary field upon entering edit-mode by default & remained that way until/unless the Editor manually 'ticked' a change in status prior to adding additional comments and saving. That "function" has also stopped working (under edit or preview; no difference) and a blank field is now the default instead (of course, until/unless a ststus is manually ticked &/or edited before the final save). -- George Orwell III (talk) 06:03, 15 February 2014 (UTC)

## Unpublished works of unknown authorship

I found in some family documents a carbon copy of a poem or song from c. 1918. Based on the POV of the narrator, it pretty clearly wasn't written by the family member who kept it, but rather by an enlisted man stationed at the same air field. I googled some of the lines in case it was published, including more generic lines in case it was just a local take on a more widespread song, but if so it's certainly not on the Internet yet. (And honestly, I don't think it was terribly well constructed.) I'm really not sure whether to use {{PD-anon-1923}}, which says it's for published works, or {{PD-US-unpublished}}, which requires knowing when the creator died, or whether it's just not kosher at all. It seems like something that would be of some interest historically, so it'd be nice to make it available. Laurascudder (talk) 18:29, 14 February 2014 (UTC)

Neither of those will work, you don’t know it was published and you don’t know when the author died. Jeepday (talk) 00:17, 15 February 2014 (UTC)
And that's why I'm here. Any solutions? Laurascudder (talk) 03:24, 15 February 2014 (UTC)
It's a copyright issue. Unpublished works aren't subject to the 1923 thing as you might otherwise expect. See here: Help:Public domain#Unpublished works See if you can find if the author died in 1943 or earlier. djr13 (talk) 03:45, 15 February 2014 (UTC)
According to this table, unpublished works with no known year of death are under copyright for 120 years from the date of creation. Assuming 1918 is correct, it won't be in the public domain until January 2039. There seems to be some clause involving certification by the Copyright Office but, otherwise, legally it cannot be hosted here. Sorry. - AdamBMorgan (talk) 20:58, 15 February 2014 (UTC)

## How to prepare this text from archive.org for proofreading

I'm thinking about trying to prepare https://archive.org/details/federalregister53lunit/ for upload (it should be obvious why), which was scanned from microfilm and has two pages on each "page", and looks not to be very thoroughly OCR'd. What approach would be simplest? Tell I might be willing to let him tackle it? (It's quite huge! On the other hand, the scans are neatly bundled in a PDF, from which they can presumably be losslessly extracted quite trivially.)

See also w:Federal Register for bibliographic information, including the usual citation convention. —SamB (talk) 02:58, 17 February 2014 (UTC)

Forgive me, but the 'obvious-ness' escapes me. What exactly is it that a partial FR volume "gets us"? -- George Orwell III (talk) 21:54, 19 February 2014 (UTC)

## Showing thumbnails of pages

Hi wikisorcerers,

Can you check this template: {{PageFile}}. It is used to show thumbnails from the pages in the Index Talk page (example here), so we can locate more easily and quickly a page. Is everything correct? I have imported and translated it from French Wikisource (history here). Please don't hesitate to improve it! --Zyephyrus (talk) 21:35, 17 February 2014 (UTC)

Very neat, ty.— Ineuw talk 22:57, 19 February 2014 (UTC)
Indeed, though I'd much rather have Book2Scroll (2nd Icon at the top-right of every Index: Page) "refined" a bit further so it loads/renders properly under our current code environment. -- George Orwell III (talk) 23:33, 19 February 2014 (UTC)

## Category for materials under CC0

I am wondering why CC0 is not mentioned in Wikisource:Copyright policy, nor in some category similar to. Any pointers? -- Daniel Mietchen - WiR/OS (talk) 22:30, 18 February 2014 (UTC)

Commons has a template and category. I suppose we should follow their lead if there's any works we have which it's applicable to. Prosody (talk) 23:02, 18 February 2014 (UTC)

## text formatting help

Forgot to ask for formatting help here, if anyone has a good idea how to best format the text in caps. Thanks, Londonjackbooks (talk) 21:32, 24 February 2014 (UTC)

A possible hint in the first paragraph.--Mpaa (talk) 22:24, 24 February 2014 (UTC)
I tried to understand the markup, but with little success. I think the text should be recreated exactly as in the original (breaks where there are breaks, etc.), for I think it was transcribed as found "scratched upon the walls" (if I read correctly). Londonjackbooks (talk) 22:40, 24 February 2014 (UTC)
I've had a go. See what you think. Beeswaxcandle (talk) 23:32, 24 February 2014 (UTC)
Permit my 2 Canadian cents' worth of input but tables are superior - and never fail. I won't revert the most recent edit by Beeswaxcandle, but pasted my enhancements of Mpaa below
 1. NON TI FIDAR AD ALCUNO PENSA e TACI SE FUGIR VUOI DE SPIONI INSIDIE e LACCI IL PENTIRTI PENTIRTI NULLA GIOVA MA BEN DI VALOR TUO LA VERA PROVA 1607. ADI 2. GENARO. FUI RE-TENTO P' LA BESTIEMMA P' AVER DATO DA MANZAR A UN MORTO IACOMO . GRITTI . SCRISSE.

IneuwPublic (talk) 23:44, 24 February 2014 (UTC)

I agree about the stability of tables, but I think BWC's rendering is most faithful to the original, and what I was looking for. My first thought was tables too; I didn't at first consider gaps, but unless one can recreate BWC's rendering with a table, I think I'll keep things as is. Thanks all for your input! Londonjackbooks (talk) 23:53, 24 February 2014 (UTC)
Sure, it can be done as a table. But you still need gaps to match the alignment of the inscriptions.
 1. NON TI FIDAR AD ALCUNO PENSA e TACI SE FUGIR VUOI DE SPIONI INSIDIE e LACCI IL PENTIRTI PENTIRTI NULLA GIOVA MA BEN DI VALOR TUO LA VERA PROVA 1607. ADI 2. GENARO. FUI RE- TENTO P' LA BESTIEMMA P' AVER DATO  DA MANZAR A UN MORTO  IACOMO . GRITTI . SCRISSE.
Alternative methods would be to nest a table with the indented lines within the larger table or to set each line of the inscriptions as a line in the table with 8 or 9 columns and lots of colspans. But why complicate things? Beeswaxcandle (talk) 00:31, 25 February 2014 (UTC)
Looks good as well. I would not be able to complete the page with my 'skill set', however. I'll leave that to those familiar with the markup, or I am happy to keep things as is. Thank you all for taking the time to help; and BWC, thanks again for checking/amending my Greek. There are two more pages that I forgot to add the Greek missing tag (now added), and then the text can be marked as proofread! Thanks again for your help! Londonjackbooks (talk) 00:40, 25 February 2014 (UTC)

## Couple minor works pending help

I have a couple works I have proofread which are pending some assistance. One of these I had posted about last month, a songbook, thus needing relatively heavy transclusion work (I've done this with another edition, but could use review on if I'm doing it right such as choice of page names). The other is Evolution of American Agriculture (index), for which I have three things I am hindered by: tables (full pages 62, 63, 64, and 65; smaller tables pages 47 and 48), what to do with the heavy illustrations which mix with text, and whether I should interpret the last listed chapter (see index) as "Chapter 11" despite it not being listed as such in the TOC. Thanks, djr13 (talk) 16:45, 26 February 2014 (UTC)

I got the smaller tables on pp 47-48 working by (ab)using {{dotted TOC page listing}}. The images that are the chapter headers should be done by carefully splitting the images into parts and then using floats. (See, this as an example of what I mean by that.) As for the full-page tables, or the mysterious "Chapter 11", I have no idea. Mukkakukaku (talk) 05:24, 27 February 2014 (UTC)
Is it possible to use either the split or "flow under" method without breaking the drop caps, eg, alt text? djr13 (talk) 06:02, 27 February 2014 (UTC)
I've had a go at the table on p62 for you. If it's OK, then copy that formatting onto the other 3 pages and drop the text into the appropriate spots. AuFCL is currently working on the flow under technique, so he'll be the best to answer that. In re "Chapter 11", there are no particular guidelines on how to deal with this situation. We just need to be able to link to it should another work refer to it. The way I personally would do it would be to name it (i.e. Evolution of American Agriculture/Development of the Agricultural Workers Union No. 400). This maintains the authorial intent (or the publisher's intent) as I'm guessing it's really an appendix to the main work. Beeswaxcandle (talk) 08:11, 27 February 2014 (UTC)
Regarding use of {{flow under}}, I would be inclined to set the image alternate text (i.e. File:...alt=) to reflect the drop capital which the chapter image effectively represents. Apologies for not doing this on the first edit (hope this is a bit more to your liking?) Actually clicking on the image still works and takes you to the background image as before (and may be controlled at need by resort to the native File:...link= parameter.)

All of these remarks should apply equally to the "split" image method if you choose to go that way.

Specifically regarding "breaking the drop caps," what exactly would you like to happen? Certainly wrapping {{drop initial}} around the chapter header image will fail using either image approach, but would you really need or want to do so?

Oh, and please don't give me credit for the technique: the more I look into the idea, the more previously existing instances keep turning up. I am, however guilty of trying to shoehorn it into a template (set) [hat tips to GOIII Beeswaxcandle & Eliyak for valuable advice], which of course I hope you may find usable/useful. AuFCL (talk) 09:49, 27 February 2014 (UTC)

After you made the first edit (which I'm still pretty damn impressed by as is) I did dig into it to try learning how it was done...it's obviously still rather experimental, for better or worse. I'm still at the point of being intimidated by the simplest wiki tables. :-) By "breaking drop caps," I mean, to put it in the most easily testable terms, ensuring that given degradation of images (whether by technical limitations or nonvisual reading devices), the text will still render clearly. For example, you can check this by seeing if the text otherwise represented in images displays as would be expected when you copy/paste into a plain text editor. I appreciate all the help, I am trying to learn from all of it. djr13 (talk) 10:38, 27 February 2014 (UTC)
A perfectly valid point, and that last edit of mine fails; as the alt-text on the image "cuts" before the "Development of A.W.I.U. 400" title, even though ideally it should come afterwards. Some (more) things to check for! AuFCL (talk) 12:25, 27 February 2014 (UTC)

## Poems and page breaks

I'm trying to transcribe a poem that has stanzas (or whatever the "paragraph" equivalent is called in poetry), and I'm having a problem with their transclusion into the main namespace. Namely, there's a stanza break at the end of one page, and the next page starts with a new stanza, but when transcluded into the main namespace it's all clumped together into one long double-stanza.

The pages in question are pages 5 and 6 of Index:Morning-Glories and Other Stories.djvu. Their transclusion is here.

I tried using {{nop}} like I would use if it were a paragraph that ended at the page break, but that didn't work. Nor did using a second {{nop}} at the top of the second page. I also tried inserting an extra few lines of whitespace within the <poem> tag, since those tags are whitespace-sensitive, but that didn't work either.

What is the appropriate template, tag, or structure to use to get this stanza-break to show up in the main namespace transclusion? Mukkakukaku (talk) 15:40, 1 March 2014 (UTC)

I tried using an {{nop}} inside the <poem> tags at the bottom of the first page and the top of the second page; for some reason, it seems to have worked. Could you please check whether it works now? —Clockery Fairfeld [t·c] 16:00, 1 March 2014 (UTC)
Yep, works now! Thanks, Clockery. I'd like to say that I would have figured it out eventually, but I'd never have thought to put the {{nop}} inside of the <poem> tags themselves. It seems like a very convoluted solution to what appears to be a rather imple problem. Thanks! Mukkakukaku (talk) 16:12, 1 March 2014 (UTC)
I'm not sure, but I seem to have inadvertently avoided this in my poems-across-breaks endeavors. I've been adding little passive-aggressive hidden comments onto poem tags that should ideally wrap gracefully, the presence of these extra tags being that which may or may not be related to the joining behavior. For example, see the page breaks between 22, 23 and 24. Might be another option in your arsenal, especially if you want to blow off steam while at it. :-) djr13 (talk) 21:46, 1 March 2014 (UTC)
I rather like Djr13's approach. Almost psychotherapy: "How does young madam Poem feel about behaving today?"

Please pardon my mucking about thrown into the mix. Apart from the centring I don't think I've added anything much useful.

I am aware of editors who avoid the use of <poem> entirely. Enclosing the whole passage inside (say) {{block center/s}}/{{block center/e}} pairs (which cross pages O.K.) and then using <br/>s at every line-break is much more robust, but of course the raw source is then quite ugly. AuFCL (talk) 22:17, 1 March 2014 (UTC)

## Paragraph break not visible

On this page A break between two paragraphs is not visible in read mode and they appear as one continuous paragraph. The text is enclosed by {{fs90/s}} — with {{fs90/e}} embedded in the footer. Since I am using the Modern skin, I also checked if the problem was skin related by switching back to Vectra, but the result is the same. Can someone please point out what's wrong? Thanks. — Ineuw talk 18:37, 2 March 2014 (UTC)

The first sentence of the {{fs90/s}} template page says "This template renders the text of a single paragraph at 90% of normal size." (emphasis mine) Mukkakukaku (talk) 19:13, 2 March 2014 (UTC)
The text was copied from {{fs90}} which I created. {{fs90/s}} was created for multiple paragraphs. (I should correct that). Also, the paragraph break has nothing to do with the font. There is something wrong with that page. If you look at subsequent pages, the paragraph breaks work fine.— Ineuw talk 19:33, 2 March 2014 (UTC)
Thanks for pointing this out. Two different templates share the same documentation which technically shouldn't happen. I posted a request on GO3's talk page, to help me sort it out.— Ineuw talk 19:55, 2 March 2014 (UTC)
I kicked it, and it seems to work now. djr13 (talk) 20:22, 2 March 2014 (UTC)
Thanks, a good kick. — by Ineuw earlier this afternoon.
I cannot necessarily give a lucid explanation, but {{fs90/s}} only works for a single paragraph unless:
1. You separate the last "}" of the template from the text you want it to affect by a new line; or
2. You enclose the following paragraphs in <p>/</p>s (or some template (like {{p}} which generates them.)
Mediawiki appear to "shoehorn" <div>s (upon which the operation of e.g. {{fs90}} relies) correctly in only at certain points. This is not the problem; the real problem is that if it cannot find a suitable "spot" (<p>s being one, there may be others..?) it silently refuses to process "double-new-lines" into proper paragraphs up to the end of the enclosing </div>. I can only assume this is a still-extant parser limitation of some antiquity. AuFCL (talk)
To be clear, in the above example I used {{fs90/s}} and not {{fs90}}, which was my own rudimentary & elementary contribution - functioning on single paragraphs and I no longer use, having switched to GO3's version of {{fs90/s}} & {{fs90/e}} hundreds of times, but never came across this problem beforehand.— Ineuw talk 00:58, 3 March 2014 (UTC)
<generic expletive>I mistyped. The earlier discussion was meant to refer to {{fs90/s}}, not to {{fs90}} as originally stated. The rest of the discussion, however clumsy, still stands. AuFCL (talk) 01:54, 3 March 2014 (UTC)
Understood both the correction and your explanation. I just wanted to clarify the history for those who still use {{fs90}} to span multiple paragraphs. In any case, I replace them when I come across them, whether they are used on single or multiple paragraphs.— Ineuw talk 02:32, 3 March 2014 (UTC)