“ I have no idea whether your supposed solution works as I cannot see any difference on the page between this morning, when I responded, and now. The page continues to have a proofreading error on every line, that cannot be fixed short of disposing of your (poorly explained) templates and strange initial punctuation on each line and then implementing a simple solution.In terms of your comments about "offense", what is actually becoming offensive is tripping over these snide asides almost anywhere across the Wikisource namespace, including in edit summaries. ”

“ The order of moving doesn't matter BUT it won't all be functional until it is all aligned. In the end the Index: / Page: / File: all need to align in their names, and then the transclusions need to be fixed and each of those is just an opportunity to create errors, and to have to run numerous checks for no designated value. So, we suggest not to move them without a good reason. — billinghurst sDrewth 07:10, 11 February 2020 (UTC)
NB! You now have ~100 redirects as subpages of that dummy page. ”

“ If imported styles are going to interact with inline ones in ways that aren't expected, then I'd ideally like to know where those interactions are likely to occur, so the relevant stylseheets can be designed accordingly. ”

“ However, with an average of 4 or 5 templates per page, and so far 270+ pages transcluded on United States Statutes at Large/Volume 33/Fifty-Eighth Congress/Private Acts of the Second Session, we have inevitably smashed through MW's Template limits. Ahah, I hear you say - easy! Once it's all proofed, ask AWB to subst: everything and the problem goes away. ”

“ With a clean DOM to examine it should be entirely manageable to at least figure out whether we can set redlink/bluelink status reliably, and, if not, discuss and decide which tradeoff to make on that (e.g. all-bluelinks vs. sometimes misleading redlinks) . --Xover (talk) 12:27, 19 February 2020 (UTC) A workaround for that is to add https://en.wikisource.org/w/index.php?title=MediaWiki:PageNumbers.js to your adblocker. For me, adding exactly that line to uBlock Origins "My filters" panel blocks the loading of the script and the page numbers logic never fires. ”

“ Working with what you have is just reality. Inductiveload—talk/contribs 11:12, 6 February 2020 (UTC) Having had a previous transcription effort blow out the template transclusion limit due to a lot of effectively repetitive calls, I was trying to minimise repeated use of a repetitious template call, 26*2 calls over an entire set of pages is going to be considerably lower workload than say 500 or more by doing a call to {{smallcaps}} on each new definition. On transcluding, TemplateStyles code is de-duplicated anyway isn't it? ”

“ Or put another way, the linter errors are in effect the WMF / Mediawiki devs. telling us "You really shouldn't be doing this!". Completely ignoring them is not a winning strategy in the long term.
PS. But, ShakepeareFan00, for the block/inline and refs thing, the linked Phab/patch is the way to solve this issue, so until that gets merged there's really not much point expending energy on this. If there's no visible problem, we should just ignore the lint errors until the software gets fixed: before that it's a lose—lose proposition. ”

“ There is no perfect solution to every situation out there. There never will be. Live with it and deal with it as best you can. Also, you complaining about poor documentation is somewhat hypocritical given the dearth of comments in your template code, and incomplete documentation subpages. Beeswaxcandle (talk) 09:33, 6 February 2020 (UTC)
The strange punctuation is definition list syntax, which when used for something that is a semantically "definition list" should have been an obvious use case. ”

“ Does anyone have examples of this style of index done semi-naturally, without resorting to more formatting instruction text than text? Shenme (talk) 20:32, 10 March 2020 (UTC)
@Shenme: There is {{hii}} which you can use in the header and footer through the index, and just ensure you use it in the lede of the body section of the first page though it isn't perfect either. I have done over a hundred and I still don't have a standard process, so sometimes best to have a look at what has been done by others that suits your work. Intitle "Index" search main ns. ”

“ Is there something like jsfiddle in the Wikimedia sphere? ShakespeareFan00 (talk) 09:17, 11 February 2020 (UTC) The rule of thumb for CSS selectors is that specificity wins: a selector targeting a specific class will get overridden by a selector targeting an element with a class (specifying both the element name and the class makes it more specific) . Inline styles (in the |style= attribute on an element override styles given in a stylesheet. !important should really not be used, but is, sadly, sometimes necessary in practice to get things to work (but try really hard to avoid them) . ”

“ Namespacing work/domain-wise with "_prefix_" based on work is probably a good idea too, if for no other reason than making it easy to search for without popping up hundreds of difference instances of generically-named "_table" classes. ”

“ Do you have any adblocker browser plugins, or other such that might conceivably interfere with loading of javascript or stylesheets, or insert themselves somewhere in the web page that might confuse the scripts handling the layouts? Do you have any particular gadgets enabled in the Gadgets section of the preferences here? There was also a software update to MediaWiki yesterday that made some changes to the editor. Did the situation by any chance improve? --Xover (talk) 18:03, 20 February 2020 (UTC) In usual browser, disabled in-browser adblockers with no change. ”

“ I've done it for page 8 and 9. -- Contrapunctus-1 (talk) 08:56, 24 March 2020 (UTC) Separating semantic and formatting information I'd like to separate the semantic markup of text (e.g. "chapter title") , and that of how it should be displayed (e.g. a specific font size, style, and alignment for all chapter titles) , in hope of better exporting to other targets, like LaTeX. Is this viable on Wikisource? From reading around, dynamic layouts seem closest...is this correct, or are there better ways? ”

“ As I have said REPEATEDLY, expecting normal contributors to know the minutiae of under-documented internals in order to implement what should be relatively simple templates and moderate CSS is unacceptable. I do not appreciate having to essentially abandon templates (and change a LOT of invocations to code I know isn't that efficent) because Mediawiki or CSS can't apparently cope. ShakespeareFan00 (talk) 23:58, 5 February 2020 (UTC)
This page is an excellent example of when using poem tags is a good idea. Simply use a {{sc}} template for each lead term and then follow it with the definition. ”

“ Premature optimisation is famously the root of all evil. WRT to "but that seems like a kludge that SHOULD not be necessary.", that seems like a [citation needed] moment. How exactly do you think this should be working, and how will you justify to the W3C committee or Mediawiki maintainers that your use case (transcribing a book's physical formatting from 1881 into HTML via Wikitext with some unspecified limit on "performance") merits the associated technical debt and should be considered when drafting web standards? ”

“ Note, the CSS in inlined up front, so you can't have the CSS apply only after a certain point. Inductiveload—talk/contribs 20:05, 31 January 2020 (UTC) I meant having something in the table syntax for wikitext markup that does what TemplateStyles (or {{table class/import}} does albiet on a per table basis... I can of course set id= on the table and use that id as a suitable selector if I want to classes to a specfic table... ShakespeareFan00 (talk) 09:30, 1 February 2020 (UTC) The inlined upfront, is why I'd like to see the phab ticket you mention resovled (2021 Tech wishlist maybe?) ”

“ Creating a template means to expose an API to users and commit maintainers to cope with it from now on. To "undo" a template can be very tricky and require a lot of effort. Also, you are not new in proposing deletion of your own templates, as being too complex etc.. Mpaa (talk) 21:45, 6 February 2020 (UTC) ditto inside dotted TOC On this page, it looks like {{ditto}} doesn’t work quite right inside {{Dotted TOC line}} (too far to the left}. Can anyone figure out why that is? Levana Taylor (talk) 02:17, 6 February 2020 (UTC)
@Levana Taylor: You poor thing. ”

“ Should these just be rendered as text or is there a template/code for this?
An example of the text showing both the Contents and a section heading is here Page:Abstract_of_the_evidence_for_the_abolition_of_the_slave-trade_1791.djvu/31
Thanks RT764 (talk)
Sidenotes are not easy for us, and honestly drive some of us "spare", as they are truly an artefact of the book as typeset at the time. There are numerous examples of them around the place, and rendering them onto mobile screens and wide monitors reliably is problematic. ”

“ ShakespeareFan00 (talk) 10:56, 6 February 2020 (UTC) WRT to "performance": what metric are you even targeting? Pages are cached on save, so render times are generally negligible for readers, since they only need to be rendered once every now and again when changing templates and if it gets evicted from the cache. The Wikimedia servers aren't particularly overstressed AFAIK and the only technical "performance" limit you might run into is the template arg length, template depth or Lua memory usage. As long as the page renders, performance isn't something you need to be overly stressed about. ”

“ Seems to works now. The question now is: are there any cases where setting text-indent:0 on the ditto is wrong (and therefore the embed parameter should be optional) , or should it just be always set by the ditto template on its outer span (along with position:relative, etc) ? Inductiveload—talk/contribs 10:17, 6 February 2020 (UTC) According the CSS spec itself, text-indent:0 is the correct approach for display:inline-block element inside an indented block. ”

“ Looking at the actual page source from HTML (choose "view source" from your browser, likely Ctrl+U) : .img-floatright{float:none!important;clear:none!important;margin:0 auto!important;padding:0!important}}.mw-parser-output as well as .img-floatright{float:right;clear:right;margin:0 0 0 1em;padding:0 0.5em} So it appears that your margin-right:10px;margin-top:5px; is overridden in the cascading style sheet by an !important rule. Adding !important to your rule manually didn't work so maybe the rule can be added automatically into the template? ”

“ It makes it sooo much easier for those who try to use them, and for anyone trying to maintain them later. We could probably all take this opportunity to remind ourselves that we can do better at documentation (I know I certainly can) . :) --Xover (talk) 13:28, 10 February 2020 (UTC) Page:Food and cookery for the sick and convalescent.djvu/17 Am I just being completely blind in my thinking here?
A locally set inline style with {{ts}} seems to be overriden by an inline one that's by an imported style-sheet. ”

“ Mediawiki should be robust enough not to rely on contributors having to recall whitespace minutiae. The cause of the LintError generation in the latter example above is an already reported issue. ShakespeareFan00 (talk) 21:54, 3 February 2020 (UTC) Does someone have a more elegant solution, that doesn't rely on creating groups of templates, to work around "known issues"? ”

“ The "known issue" being (T134469) ShakespeareFan00 (talk) 21:54, 3 February 2020 (UTC)
These aren't entirely identical. the template has a line break in it, which will not play well with the colon as a margin setting device. Any any case, using a colon before a <div> is poor syntax. --EncycloPetey (talk) 23:44, 3 February 2020 (UTC) That's partly why I asked if there was a better way to do this. (I'm trying to shift some entries on a specfic page) , Is there a way to do that shift directly in markup, avoiding the need for a templated shift? ”

“ Maxim: "It's always a minor typo or mis-syntax if you think something is really broken!" I think it's time I took a break. I seem to be making too many mistakes of this type, which tragically leads to the kind of angry ranting (see many previous instances in the archives and edit summaries) that is not conducive to effective coding or documentation. ShakespeareFan00 (talk) 10:58, 6 February 2020 (UTC) @Levana Taylor: Please note a small but important change to Page:Once a Week.../10 remains. ”

“ There's no on-wiki way to fix it, but I've regenerated the file from the source scans in such a way that it will no longer trigger the MediaWiki bug, and the page offsets should be ok now. --Xover (talk) 17:47, 28 February 2020 (UTC) @Xover: Thank you! -- Don Elbourne (talk) 18:07, 28 February 2020 (UTC) Documenting ambiguous authorship In the Imperial Dictionary of Universal Biography, vol. 1, page 404, three segments in sequence appear (undeniably, in my opinion) to all have been written by a single author. ”

“ The LintError wasn't showing up in the page but on the transclusion:- King Solomon's Mines/Chapter XVI, I couldn't find anything other than this reference with a DIV issue in the pages themeselves.. ShakespeareFan00 (talk) 08:49, 27 January 2020 (UTC) Converting both references in the chapter to {{#tag:ref|{{#tag:poem|...}}}} seemed to temporarily silence the lint concern, but a longer term stable solution is needed ( as using a lot of parser functions isn't good on performance.) ”