Namespace

“ From a pure "only reproduced content in mainspace" angle, perhaps, but does that serve readers best? Inductiveload—talk/contribs @Inductiveload: Main namespace is content for the reader. There is nothing worse for a reader to go to a page and have to drill down multiple pages to find that there is no content just some dashed skeleton of hierarchy. Main namespace is not built to drive transcribers and transcriptions, that is our other content spaces. We can create a page there once we have content to display what we have to read, and point to the portal for what we have to transcribe. ”

“ 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. ”

“ Main namespace is for works, and they all belong at the top level, and may utilise subpages. Author namespace is for the authors, and list their works, and link to appropriate sister sites Wikisource namespace is for select listings of works, usually based on subject matter, and has more flexibility for mixing works and authors. — billinghurst sDrewth 02:12, 19 April 2010 (UTC)
Yes, I think I am looking to create a listing for the Breslev subject matter. so I made the page Breslov and put the process header in it. Did I do it right? Thank you. ”

“ Concrete suggestion: a category like Category:Topical classification (don't mind the precise name) to be created, to house at least Category:Portals, to be an over-category of Category:Works by subject which obviously remains a subcategory of Category:Works too — and to have some other pages in it. Those other pages would be the pages in the notional Topic namespace, so defining what that namespace would be for ought to be the same debate as what further classification pages are required. ”

“ 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. ”

“ One man's hero is another man's goat - allowing one so-called individual in the Portal: namespace opens the door to adding ANY individual in the Portal: namespace; and history has shown us THAT repository eventually competes with Wikipedia rather than compliment/support it. ”

“ 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. ”

“ 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-one needs to be there unless they are contributing. Keeping the two namespaces as separate as possible is a fundamental design principle. Links that take the unsuspecting reader from the readers' view into our editorial namespace are Evil.
To address Billinghurst's example, I put it to you all that any reader who went to that index in search of references to Adam's Diary, would expect that "51" to take them to The Craftsmanship of Writing/The Power Of Self-Criticism#51, and would be utterly bamboozled when they instead find themselves at Page:The Craftsmanship of Writing.djvu/65. ”

“ Our policy is that two different people look at every page in the Page: namespace. So, you won't be validating your own proofread pages, but you are able to validate the work of other editors. You don't have to wait to transclude the pages. Once a chapter is completely proofread in the Page: namespace, then it can be brought through to the mainspace. I've used a table for this page. Have a look at what I've done as it's easier to understand tables by looking at real examples rather than by description. Beeswaxcandle (talk) 02:25, 1 June 2013 (UTC) Marvelous! ”

“ Currently, the Page namespace depends on a plain old text dump that basically ignores the column, paragraph, line, word and other meta/mapping detail-types among some other possible shortcuts that could lead to easier proofreading & validation if developed fully.I was schooled to understand that making a flexible spell checker routine part of the Page: namespace without the benefits of XML and a customized WS document type definition file (.DTD) would not be worthwhile even as an attempt (I have no reason to doubt that evaluation if it matters) . ”

“ I see it as tidying up the ramshackle Wikisource: namespace, and giving it a more navigable logical structure; a place to undertake resource and information building for a subject matter (person (non-author) , place, organisation) ; and finally a place to align portals between sister sites.
Some may not want it overly formalised, and while that is okay for their needs where they work within a tighter zone of interest, some of us are more nomadic and eclectic in our work, and would like some assistance. ”

“ 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. ”

“ 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. ”

“ 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 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. ”

“ 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. ”

“ 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. ”

“ 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. ”

“ Followed by Portal: and Category: namespaces which we sort of do.
What should happen? People should be bringing in works they are going to undertake in the index: and page: namespaces, and start undertaking them. People should not be dumping links to internet archive into main namespace that they think others should be working on, or might work on; and rinse and repeat that. We need transcribers, and people to do the work. We could dump tens of thousand pages into main ns with links to archive.org and that would look totally shit, and help no one find anything. ”

“ Works Works would be defined as main and Translation: namespaces for the purpose of this guidance, and it would be expected that the disambiguation pages would occur in the main namespace, not in the Translation namespace. Disambiguation pages are for listing works that share the same or very similar title. One shouldn't list works with distinct titles on a disambiguation page, even if they are versions of the same work, or commentary on the same subject. ”

“ Your Index: and Page: namespace are not defined. cy compared to en. A bugzilla will need to be submitted to get the namespace created, and the pages updated for those creations. We did that for nlWS recently, see their request and resolution at bugzilla:37482 Bugzilla:39264, though you will need to chase it. — billinghurst sDrewth 14:50, 11 August 2012 (UTC) Thanks. I wonder why it used to work. What do you mean by "you will need to chase it"? ”

“ 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. ”

“ 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. ”

“ 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. ”

“ Our problem is that we are a small project team with a huge project: 63 volumes, 29,000+ articles, 25,000+ pages. We are working on articles in order of importance rather than front-to-back. But what should we tell a reader to do if we have not yet transcribed the article the reader is looking for? Well, I unilaterally decided to pierce the namespace boundary by providing a "source cescription page" for each volume. ”

“ 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. ”

“ Same goes for large swaths of indented sections or sub-sections under a paragraph typically found in legalish works -- its better to address this in the transclusion rather than trying to get things to line up from one Page to the next. However, simple things (bold text, small-caps or italics) should be made within the Page: namespace just as they are found in the original scanned djvu or pdf files. ”