“ I am rather of two minds regarding LUA. The overhead of launching and tearing down a new process for each #invoke must cost pretty highly, so use on a per-paragraph/div/span/whatever basis runs the risk of being even less efficient than the template equivalent (Yes, true blasphemy; but you did ask.) On the other hand, having fewer invocations acting upon large slabs of text has a hidden cost of its own. The syntax is deceptive in the sense an #invoke looks like a parser function. ”

“ All I was trying to steer the discussion to, if it got picked up, was to suggest a return to the practice of folks adding their scripts to a shared scripts page and updating their User pages more frequently to better reflect what they currently working on & with who. They say sunlight is the best disinfectant, but I believe open access is when it comes to being online. Distrust and skepticism are more likely to develop online than in real life (especially by older folks) since there are few normal human nuances one can actually see and interpret like in real life. ”

“ I'm thinking about a template that includes images into the text using the thumbnail of the page already uploaded into nsPage, showing only the right part of it into a box. The advantage would be, to include a (draft) image into a page without any need to extract the image from the djvu file and to upload it into Commons; the drawback, the need to pass to template al least five parameters (the coordinates x1,y1 and x2,y2 into the original image (whose name is known: it's simply the page name) and the box width) . I feel that it would be a useful exercise, and I'll try. ”

“ What EncycloPetey describes does not pertain Google Books. There is no person or program making such subjective choices for Google - if their "programing" thinks there is even a slight chance of copy violation taking place in one of their digitalization projects, the book would never be offered as full-view as is the Google Book PDF's status in this case. ”

“ Same problem - folks treating a simple form field like a big ol' textarea box because the current MediaWiki namespace implementation as a faux template won't allow you to add things like categories etc. as one normally would. When its present, it forces the parent table cell to a width of 30% even though no remark-text is actually being displayed (EXAMPLE) . The various icon-linked tools were originally put in the "same" container because it was understood they would be better positioned at some point down the road (currently scripted to force them up top) . ”

“ Good source file is ALMOST ALWAYS the easiest way to re-use or convert content.Fix your source files to meet most basic semantic HTML markup &/or most common file specification and you can convert or re-apply content 1000s of times - here on WS or in real world as needed. ”

“ Find me a javascript/Lua way to generate custom markers that works across more than just one browser and I'd gladly utilize it in the needed generation of those pages under the vast majority of .DjVu files that I've uploaded within a week or two.I'm also not happy with some of the thumbnails being produced by some of the current DjVu source files. I have since learned how to crop the .PDF file so the resulting DjVu file produces far superior thumbnails - I just haven't got around to re-doing those (laziness) regardless of ever finding a solution to my list-item-marker problem. ”

“ I have Acrobat Reader and Acrobat Pro both updated as anyone can get and I am familiar with removing the watermarks as well as uploading to Internet Archives and then d/loading and up/loading to Commons then placing a book on WikiSource. These are just a few of the many things you have taught me over time. You are a good person always doing good for others but what you teach is most important because then any person can know how to "catch his own fish for dinner." ”

“ Its not really a trick. Its more a workaround for stupid File: wiki-markup that restores the possible HTML behaviour expected when "inherit-tree" is properly setup and defined thru .CSS in the "real" world. Note that the IMG is wrapped in a Paragraph tag instead of DIV to make shortest block->inline / parent<-child chain. This way inherit has better chance to work under annoying wiki mark-up. Add back |link=$ and wiki mark-up breaks chain like always. Real pain in the ass.Same "bug" exists through-out most anything that is wiki mark-up compared to outside wikifoundation. ”

“ I'm rather irritatingly over-confident that the FI core (with the single primary DIV container in "control") can handle anything you throw at it - it's when people try re-impose some degree of the existing image-file limitations or start trying float an image in the middle of a block of text without adding the needed additional DIV containers/wrappers to compensate/accommodate for those situations is where things start to go off the rail.The math and score outputs are just .png images compiled on the fly so they aren't that much different (if it all) than a static .png file hosted on Commons. ”

“ You can parse the workflow however it makes you feel better about your work, etc. but in general, we think of Books as being originally published/printed, and Works are [source] files/digitalization of those "Books".The Page: namespace is only a tool to help get you from a Book to a Work ”

“ In short, I deal with the wikicode whereas most other folks believe they are utilizing it.Second, I come from the old-school days of the internet so I'm biased in the old-school ways of doing things. Not much has changed when it comes to the use of Divs (&spans) however - those who once lived by the old standards seem to have been overwhelmed by the latest & greatest improvements and forgot the basics while newbies never get the chance to learn the proper foundations from jump...
A DIV element tag is today as it has always been and forever will be... ”

“ Would it be best to upload a no-text-layer (but with the Google disclaimer still moved) version of the file, or just leave it as it is and hope any proofreaders have a non-broken version of the file? —Kierkkadon talk/contribs 22:04, 25 February 2013 (UTC) It would be best to avoid .PDF file variants that are created from a nameless bot at GoogleBooks and stripped of any useful text-layer/image-compression to begin with - but that was your choice nevertheless and I tried to honor it by fixing up a losing battle. Live & Learn. ”

“ How to enforce sane usage is a hard issue, to which I have no clear answers. Viewer2 (talk) 12:35, 20 November 2013 (UTC) Sticking the template data on the parse sub-page is almost certainly the wrong place to put it, but I would prefer somebody putting the effort into making their damned parser look for it properly (i.e. expand the templates, then look at the result) , rather than mindlessly expect the end-users to slavishly copy the same things into every template just to satisfy a stupid standard. ”

“ Since my crystal ball is on the fritz, there is no way ascertain how "static" anybody really is so we figure 'why take the chance?' And the only implication, afaict, is: 'You are prone to making mistakes like everybody else'. ”

“ You can find the basic usage for all the other .exe files in DjVuLibre in its [Man] uals folder. DjVm.exe is used to insert or delete pages and DjVused.exe is used to extract or insert text layers -- the other .exe files are geared more to the really technical manipulation of DjVu's. You should make yourself familiar with at least those two DjVuLibre command line exe files. Hopefully by now, you might better understand a DjVu file is more akin to a .Zip file that compresses the individual files within it but maintains a static reading order of those content files. ”

“ I have seen someone using nop at the end of every page even though the last sentence carries on to the next page. In my view (coupled with my expierence) - that is 100% "wrong". The ultimate test would be to see what the final rendering of the transcluded range of Pages looks like in the mainspace I suppose. Too, while I use nop at the bottom of an image page I have seen images with nop at the top of the image and below the image. ”

“ Even in your Pop Science example we are "governed" primarily by the width of the paragraph block (and that is determined by your browser-window, monitor dpi, etc.) . No matter where the span is inserted within that Paragraph block it will take 50% of that width & not 50% of the image file's actual dimensions. This is not (?) dynamic re-sizing - its acting like a container rather than just 'hand-offs of inherits' framed by a container. Again, this could be useful in of itself (if font sizes &/or line heights are pretty much fixed - like when transcribing a book) as a separate (or sub-?) ”

“ Its work-a-round for a poor design to begin with (i.e. using noincludes for a header & footer leaves no room for a closing paragraph tag under transclusions to the main namespace. Works great when a paragraph spans the end of a Page: and the start of the following Page: -- not so much if a paragraph ends the Page: as well as a new paragraph starting the Page that follows it. This is the only reason to use nop. You can simply use the paragraph tags to avoid its use altogether but for some reason that was not route taken long before I got here.) ”

“ As long as I have a sense that an admin is an active and present member of the community, I couldn't care less how many edits they have, when they last wielded the tools, or how they score on any other metric you might put forward as an alternative measure of active. ”

“ In theory, a DIV should behave as well a P would in this scenario since they are both block elements; yet in my experience the DIV seems too far removed (the "grandfather") compared to when using P (the "father") . I find using P works in more situations reliably than using DIV did so I go with that child (IMG, SPAN) to parent-father (P) to parent-grandfather (DIV) scheme (i.e. not 'skipping a generation') to insure inherit works as best as I know how in FreedImg. That's why I'm such a d*ck about keeping it as "pure" as possible or ask for proper div tag usage and so on in FreeImg's case. ”

“ You may not have realized that bulk moves in the Page: namespace also covers any change needed in the existing page ranges assigned in the pages tag in the main namespace. Its far easier (as well as more reliable .DjVu structure wise) to let the Bot do the needed moving up or down as many times as it might take to align all the pages in the new source file than it is trying to edit the new source file to match the old one. ”

“ The rest of the planet starts with the assumption our document tree follows the norm - or in other words - having a header tag in place for the common chapter title or section header. Because we DIV everything from simple letter positioning to entire page layouts, the conversion routines for other file formats out there can't tell the difference between lists, paragraphs or section headings in our text content. Anyway, now at least you know about it/them. Oh - & I fixed your Chart template thingy so your User: page should mirror the one on WikiPedia now as well. ”

“ UPDATE: Well the premise works like I thought it would when values for the number of pages/percentages for each PR status are a User driven input rather than API (or whatever) calculated; see Template:PageStatus & associated. Now if I just knew how to pull the current values automagically via Module: or Template: in addition to the total position count of a source file to work from, the whole bit could finally be trimmed once and for all from the christmas-tree of existing ProofReading/DynamicLayout server based stuff in addition to giving the W3.org HTML validator a well-deserved break. ”

“ Nop was never meant to be used in any other scenario other than at the very start of a Page: (rare) or at the very end (common) . You shouldn't get mad at something that wasn't suppose to be in the first place. ”