User:Pathoschild

“ The historical problem of "header" is one we need to get beyond so we can become too imaginative. I would like to see a specific header template for patents, and maybe even obits. The header on sub-pages can also be improved by having per-book navigational templates. The list goes on. Decisions are made by those who turn up and do the work. Sadly most of our contributors only use Wikisource as an extension of their Wikipedia activities. Curators are a rarer breed. ”

“ I just noticed that the author parameter doesn't work in EB1911 template. Many of the articles have identified authors indicated by initials at the end of the article, with a table at the beginning of each volume to identify the initials. It seems that these authors should have the same credits as authors on other articles. Sometimes it just seems as though more attention is given to the interests of bots than of humans. A "sequencing" template could be separated from the header to deal with the previous and next entries in a series. ”

“ As that page is reserved for "behind-the-scenes" editorial discussion— something that users who want the bibliographic information shouldn't be shown or bothered with. I propose adding an optional appendage to the header (or even a separate template at the foot of the document) which can give concise information regarding the text being read. Such as: original publication, publication Wikisource text is based off, text quality/progress, notes, etc. A rough sketch of what I had in mind can be found on my development page on Wikipedia. ”

“ Having this in the/a template also helps to standardise and so encourage the inclusion of this data for a text, which I feel is as important as citing and referencing sources in a Wikipedia article. A work can be revised and edited continuously throughout an author's life (and unfortunately beyond) , so knowing what version of a text I'm reading can be very important. ”

“ Sometimes the translator really does matter, as there are very famous translations of works. But most of the time, the translator is not a popular person, the translation is nothing spectacular, so relegating that information to the notes parameter is enough. I would rather not add much verticality to the {{header}} template by adding a new parameter, but just keep such information in the notes section.—Zhaladshar (Talk) 15:55, 6 June 2006 (UTC)
Yes, but isn't that exactly the point? When the translator is important, there is easy option to feature that. ”

“ Perhaps it is possible to solve it in the same way the new "translator" parameter, which automatically works out whether it should be wikilinked. Do we want to set up a (temporary?) category for all works which use this "override_author" param? The header/header2 templates can automatically fill the category so that we can make a more informed decision. John Vandenberg 21:46, 12 November 2007 (UTC) I see now that Eclecticology proposed at Wikisource:Scriptorium#Bad syntax in headers that the "author" param handles normal wikilinks. ”

“ I have raised the EB1911s issue at WT:EB1911#author in header and WT:EB1911#navigating sub sections. This project to merge the templates isnt being done primarily for the benefit of the bots - if anything it is for the benefit of the bot operators. It isnt fun having to manually approve 2,000 bot operation because of all the irregularities. Standardising the templates removes the complexity in parsing them, which allows the humans to run the bots in a more automated fashion. ”

“ The participation shortage, has wider effects than just on technical development. Vision too easily gets trapped in the details; I am sure that our vision needs to be much bigger than an accumulation of cut-and-pastes from Gutenberg. Policy suffers too when only a very small number participate in a decision ”

“ The {{script}} template does not work, so we're still stuck with unnecessary footers. In my opinion, no page should have a footer if the footers can't be removed from the short pages. Scrolling to the top of a page is not difficult. Short pages look very cluttered when they have a footer. I wouldn't mind scrolling once in a while if it meant our shorter pages weren't as cluttered. Psychless 22:21, 6 February 2008 (UTC)
header inclusion update There are between 35,000 and 40,000 pages that still include "header" instead of "header2". ”

“ I've added the plainlinks class. —{admin} Pathoschild 02:17:50, 30 September 2007 (UTC) This still doesn't explain why we need the "permanent link" comment above the header. Eclecticology 08:20, 2 October 2007 (UTC) See "Soft redirects" (Scriptorium, August 2007) . —{admin} Pathoschild 14:35:33, 02 October 2007 (UTC) It all reads like a solution in search of a problem. What you say there is that if people are unwilling to learn how to fuck around with style sheets, too bad. The necessity of protecting every broken link is overblown. ”

“ We do this because we want the most important parameters to be used, even if they're blank. This makes it very easy to use the template simply by copying and pasting it from one page to the next, without needing to refer to the documentation. If you don't want that, you can remove it entirely. —{admin} Pathoschild 22:43:22, 27 March 2008 (UTC) Thanks so much for your explanation. ”

“ This is less obvious when used in {{header}}. For the same reasons, it's a good idea to standardize {{script}} for all scripts, ranging from footer overrides to bot archival instructions. It is easier to see and refer to one template than have script overrides in many places. —{admin} Pathoschild 23:36:14, 23 October 2007 (UTC) Ah. I did not realise that the footer is coming from js that is being executed... ”