Main namespace

“ Inductiveload—talk/contribs 15:50, 1 September 2020 (UTC) Comment Periodical main namespace pages should not contain the curated information of scans, etc., that is the job of the Portal: namespace. Main namespace should only contain published information for works that we have prepared. So under your proposal, the main ns can exist, and it should contain contents of works that we have transcribed, and there should be a corresponding portal: or there can be a constructed Wikisource: project page where there is a project to do the work. ”

“ Beyond the standard namespaces (Template: Category:, Help:, Mediawiki:) Main namespace is for Works, (and to disambiguate works) ; we also have newspapers in the same zone, though they are sometimes more than a specific edition/volume Author: namespace for Authors Index: namespace, Page: namespace, File: namespace for organising copies of works Wikisource: namespace for WS material and to enable collections of data Portal: namespace, pretty much unused. The Wikisource: space does have some subject type material, eg. Wikisource:Biographies. ”

“ Please don't create these unfinished in main namespace. If you want to undertake a progressive transcription like that, then create it in your user space in a sandbox. [This is not the first time this has been mentioned and you have a string of unfinished transcriptions sitting in Special:PrefixIndex/user:Richard_Arthur_Norton_ (1958-_) .] Of course the best practice when you have a scan of the text is to utilise the Index:/Page: namespace like everyone else is encouraged to do. ”

“ There exists plenty of discussion about about linking and especially in around the subject matter of moving data from Wikisource to Portal. Public view content sits in main, author and portal namespace, and annotations (this discussion) sit within a simple subset of main namespace; the other spaces are either workspace, or organisational in practice, and there is no general requirement to link to these from works, in fact the practice has been actively removed such links. Why make it more complex than it has to be? ”

“ No, the template is intended for use in the Main namespace to automatically generate structured category names, which makes it very limiting. The person who created the template comes from working on Wikipedia, and does not understand about backing scans on Commons or multiple namespaces. ”

“ As a result, the solutions for proper Page: namespace rendering and main namespace rendering are far from simple template trickery anymore -- though forcing all-right or all-left main space rendering of 'alternating' side-notes dramatically helped us at one point, that too became a moot endeavor (again) with the ever-increasing rise of mobile mode on the scene. The problem boils down to "margin-management". ”

“ The way that this page is set up is outside of how we would normally present in the main or translation namespace. The main and translation namespace are for the works themselves as published. This page is a construct and as such it belongs in the portal namespace, especially with all the variety amendments which themselves belong here as a separate published item, though the sense-making and construction of the explanation is portal namespace. ”

“ At current count there are 3,920 main namespace titles. There are numerous links in the indexes which would require change. Each title also exists as a redirect, without the project name, volume and month/year, and duplicate article titles are resolved by disambiguation pages, courtesy of Hesperian. If you agree, the it's the redirects should be changed, but not the actual title. I am also aware that the Google search engine brings up all manner of variations of the name, and pages, regardless of the namespace. ”

“ Replacing font size templates with PSM specific font templates. Linking the volume index entry anchors to the titles. Relevant namespaces, a short explanation Index namespace - Container storing the individual pages of a book. Page namespace - page by page storage contained by the Index container. It is where most of the work takes place, the proofreading of the pages. Transclusion process - links the proofread pages and the Main namespace. Main namespace - Assembled display of the transcluded pages from the Page namespace. ”

“ In the sense you're intending here, there is only one way to transclude works from the Page: namespace to a main namespace page (there are some variations surrounding use of sub-pages for chapters and such) . The syntactical variants you've found are mere technical artefacts: think of them as bugs, in software development terms. You might also want to take a moment to look into what the purpose of Wikisource is. We reproduce the original work faithfully (within reason, and there are unsettled gray areas) , rather than make new editions. ”

“ Everything in main namespace needs to fit the policy at WS:WWI. There are some index pages in the Wikisource namespace (Portal:Supreme Court of the United States) , but nothing really on such narrow topics. We really discourage index pages on narrow subjects, although you could probably find some that need to cleaned out. ”

“ Redirect from main namespace I'm a bit confused by this. Is the Portal namespace going to be subsuming disambiguations? Prosody (talk) 07:10, 29 April 2013 (UTC)
... Ditto. To be clear - all I've just done is fix some double/cross-namespace redirects by making them dated soft-redirects instead of the usual deletion. I think it was User:Hesperian who originally created one namespace's content a redirect to another to start this all off. ”

“ I also wish to avoid the really ugly situation of people uploading a work, creating the front page, and then just leaving it for other people. That facadism of a work is just problematic, and we know that nothing happens to it. It is why we developed {{ext scan link}} and {{small scan link}} for use in the author namespace to do that role of managing that list build. So portal and author namespaces play that role and keep main namespace cleaner and more functional. ”

“ You just have to put the annotation into its context and scope, hence a definition Annotation = a modification from plain text when working in the main namespace anywhere else on site it isn't an annotation as we are not bound to text. There is simply no general scope to link from a work to WS:, and it is next to pointless to discuss it and wish to codify. I have a solution, call it Wikisource: ns and you have no argument from me, just don't pick the page. ”

“ The images not only shifted by two pages, but they are inserted altogether in the wrong places and unless I go step by step, I can't see my way through as to where the additional pages go. At this point, I don't care about incorrect main namespace links, section tasks and anchors. I must correct my database from where these are generates from one central entry. The system generates the table of contents, the main namespace links and the sections to the pages and the Index with 400+ entries and their anchors. ”

“ Best to get into good habits ASAP I always think. We are a little recalcitrant beyond Wikisource:Style guide and H:Side. Often we try to replicate the look of the book, though we leave that to the editor's discretion. Sometimes we do display a little different between the Page: namespace, and the text transcluded into the main namespace, as what is right in a book, may not be on a computer screen. tag is very useful, and used far more widely than in just poetry. ”

“ To summarize, as long as the Page: namespace relies on "dynamic" layouts for main namespace transclusion then display rather than the padding, margin, column, etc. parameters assigned in any good .DJVU's text layer following the .DJVU file standards, you can map PDF embedded text anywhere within the DJVU's page width (x-axis; 0, 3886) and height (y-axis; 0, 5450) coordinates and get the same results as if the original scans were perfect and the OCR routine used was just as flawless. ”

“ It just isn't getting traction. More to that, I am not sure why we would want to categorise Index: ns pages. Until we have a schema that pulls data together, it is just another place to add more data, and we would still have to add it to the work in the main namespace. FWIW the Commons hotcat script is what we use here, and from memory, I think that I have it so we just use theirs all the time, but I can double check that. ”

“ Perhaps promote our existence by explaining that we are related to Wikipedia. Do we have a category indicating completed main namespace volume titles? Is there a way to exclude incomplete Main namespace works not to be added to search engines?
P.S: Did a simple web search on two words, "Proofreading" and then "free book downloads" and the results are not very encouraging. — Ineuw (talk) 04:28, 30 August 2019 (UTC) The proofreading aspect should be moved further down and not be immediately visible. Yes! The best way to recruit new Wikisourcerors is to showcase what we have already achieved. ”

“ The Index and Page namespaces serve the main page, ns0, enhancements, compromises, and namespace dependent templates are useless when the page is done. Two people spend about 120 seconds at each of the hundreds of pages in an Index, any additional keystrokes or distraction from its primary purpose is probably unwarranted. ”

“ I have noticed you have nominated a A Letter from a Noble-Man Abroad, to his Friend in England for validation. I have got just one point to raise before the validation starts: According to Wikisource:Style guide/Orthography#Phonetically equivalent archaic letter forms long s should be transcribed using the template {{ls}}, which keeps the original form of the letter "s" in the page namespace, but transcribes it as ordinary "s" in the main namespace. ”

“ I think we should define a common flow for what properties to check. I think in the most part we can not worry about what namespace we're checking from because the properties are prioritized (e.g. if a category has category's main topic (P301) and main subject (P921) defined, we use the former) . So, for any page in any Wikisource NS:
Use sitelink if a direct one exists. For 'Wikidata' sister links, only ever use direct sitelink. ”

“ When these 'original navigational pages' are transcluded into their Index's page they provide a guide to the existing and paginated links. A long way of describing something that becomes a simple way of enhancing a work in mainspace, I see many advantages to readers and contributors and little possibility of confusion or misdirection. I don't see how cross namepace links are useful for these pages when they are: Page: -> Page: Index: -> Page: (tranclusion) Main: -> Page: (makes me dizzy too) What is the advantage of adding namespace switching links in the Page:namespace? ”

“ Using spacing looks bad in final production. Your advice is needed RE: adopting a volume-wide-policy. Klarm768 (talk) 10:08, 11 December 2017 (UTC)
I think the "Prop XI" sidenotes can actually be skipped, as they are page-based reminders of what Proposition is currently being read. A bit like Running Headers, they don't add anything to the find work in the main namespace. Therefore, I think they can safely be put in the "header" field and not transcluded to the mainspace, which will simplify things a little (plus take the pressure off for getting formatting exactly right) . Eg: this page. ”

“ Orientation Where is everything? There are multiple namespaces involved: main, Page:, Index: and Author: are all relevant to working on articles. There are project management in the Wikisource: namespace, hundreds of special templates, and several categories that belong to the project. [8]
How do I see if the article I'm interested already exists in article space? The safest method is to go to the volume listing, also known as volume ToC, starting from Dictionary of National Biography which links to all 63 volume listings. ”

“ Agree that this looks very useful. I note that putting the contents pages into the Index field "Table of Contents" causes them to be on the Transcluded list even though they're not in Mainspace. This has potential for puzzlement. Beeswaxcandle (talk) 07:58, 23 April 2011 (UTC) Good catch. Turns out the output is also sortable. Just click on the column-header text. — George Orwell III (talk) 08:19, 23 April 2011 (UTC) Yes, it just checks for the act of transclusion, which was my request, if I have the words "main namespace" prominent then we will need to amend it. ”

“ Unless sombedy declares that they are going to work on it, I vote for deletion of the abandoned work from the main namespace while keeping it in the index namespace. --Jan Kameníček (talk) 17:52, 14 January 2020 (UTC) Delete mainspace as abandoned extract and per Jan above. Index: and Pages: can stay. --Xover (talk) 18:06, 19 January 2020 (UTC) I'm going to hold off on closing this for a bit in case anyone else would like to chime in, but based on the above the outcome here looks like deleting the excerpt/incomplete mainspace transclusion and keeping the Index:/Page:-pages/scan. ”

“ Positive Works within existing framework with limited upheaval Negative Not consistent—separates non-people from non-author people. Bob Burkhardt, Charles Matthews Positive Intuitive: the reader will most often be sent to what he expects when he types something in to the search box Negative Not clean, because of cross namespace redirects, and moving of pages from Main to Author when a work is found by that person. ”