“ Linking every other possible path is not appropriate: 'disambiguating' the sections within a title, especially reference works, without an author's reference, is insane. The real-politick of our situation is that editors are addicted to making things 'light-up', operating on more or less flimsy premises, they get their fix at wikipedia until someone says "No!", there is a drama, they get censored, then come here to create duplicate or maverick schemes. We are not editors here, what we 'know' about other texts is utterly irrelevant. ”

“ If I am doing my own work (or a work that doesn't seem to have some special formatting preferences) then I will, using a script: Use straight quotes (and change curly quotes in OCR to straight) . Most (non-WS-regular) people are barely aware they are a distinct glyphs (some may never even notice the difference due to font issues) , and wouldn't know where to find them. The reason I used them in TIJ was not a personal preference, but rather because Doug, as the primary contributor, wished to keep them. ”

“ If one constrains one's title pages on the basis of what the best technology of today can handle... one takes upon oneself the risk that one may look quite antiquated in a year's time; let alone quite silly for the subsequent nine years... ”

“ Replicate the work is the internal requirement, so it is not exclusively en dashes. Consistency through a work is the requirement, and generally people have preferred en dashes. For works and author page titles we have used hyphens, not en dashes, though redirects are generally done to cover the mix. ”

“ This is a Style Guide that indicates a group of norms that the community has agreed on over the 11 years we have been in existance. If there is doubt about to proceed in a situation, it is something we can point to as a standardised way of doing things. It is not intended to be a rigid set of rules that will never be deviated from. If, for a particular work, there is a good reason to deviate from the agreed norm, then we do that with appropriate documentation on the Index talk page. ”

“ Quotes should be consistent throughout a work, either straight or curly, if curly quotes are used then curly apostrophes should also be used (a curly apostrophe is the same character as a curly right single quote) . Hyphens/Dashes: Hyphens and dashes are not interchangeable. Hyphens should be consistent throughout a work and a hyphen-minus (-) (U+002D) should be used unless another form of hyphen is determined in advance for the entire work. Dashes should be an em dash (—) (U+2014) or an en dash (–) (U+2013) should be used. ”

“ Even if we wrapped some of the lines of title pages (those assumed by somebody not to be "deliberate") , others would still stay unwrapped and so the problem of small devices stays unsolved anyway. I do not think it is contributors of Wikisource who should bother about it, it is the task for programmers to give different choices of view to desktop and mobile users and to prepare e.g. some templates displaying line breaks differently on different devices. We should not adapt our behaviour to imperfect software, it is the software that should be adapted. ”

“ I don't have the expectation that everyone will search, or want to search, some will want to browse, to wander, to find new paths, new knowledge. As an editor it is my job to get the text right to the work as expected by the author ”

“ When writing an article one refers to multiple articles, which is expected for WP biographical articles. So to me, it does not seem inappropriate to link to related articles that provide a perspective, and often a perspective sometimes contemporaneous, sometimes retrospective. Linking them or listing them on a page is collating, not judging them. Then to think that WP is going to be fully comprehensive of any listing at WS does seem to reflect that it is an encyclopaedia, which pretty much means filtered, abridged, rather than exhaustive; something always has to go. ”

“ There are good reasons that the community has arrived at the style guide, and some things are not particularly negotiable in a standard work. The reason that the style guide is not absolute is that certain works are formatted particularly as a look by the author, so to disregard that is inappropriate when rerendering an author's work. ”

“ The most important thing should that a work should be uniform in its approach. The problem has previously been where the style guide has been autocratically imposed as a rigid set of rules. Looking to what you are trying to address it seems more about hard guidance (rule/shall) and soft guidance (preference/should) . ”

“ One of the things that we are trying to achieve is to not overly enforce formatting, and to allow people's viewing preference to come into play. So our font-size changes are proportional, rather than set; our right width is unset; font-face is left to the browser of the user ”

“ If I edit a work that you have set up, I'll use straight quotes but you may still have to go back and "fix" my dashes if you don't like the codes. If you edit Index:The International Jew - Volume 1.djvu (or 2 or 3 or 4) , you will either use curly quotes or your edits will be changed. Anyone who tries to say it's wrong is likely to be simply ignored. Inductiveload and I had no justification for making the quotes curly except that it's very easy to do and we're setting up the work, and most importantly, we both want it that way. User preference should be king. ”

“ I apologize for my lack of clarity: semantic is used by web developers, possibly with too much flexibility, to identify the elements of the layout that have "some meaning" and therefore can be considered part of the content. These are lists, paragraph, titles, some breaks (not every one) , etc. —Esponenziale (talk) 19:34, 2 May 2019 (UTC) I disagree as I think that line breaks at title pages are always deliberate. Publishers carefully decide on the size of font, letter-spacing, word-spacing and so on to achieve exactly the layout they want. ”

“ Smartphones have revolutionised web fruition and web design. Currently they accounts for 19% of visits to Wikisource main page (pageview analytics) . It is possible that most editors are not fully aware of this. —Esponenziale (talk) 21:54, 1 May 2019 (UTC) "Smartphone" and "mobile web" are not the same thing. The statistics show mobile web access of the main page. --EncycloPetey (talk) 22:26, 1 May 2019 (UTC) A comment (if you will permit) from the floor: Only a complete idiot designs for an evolving target (especially a target where one does not know where it will be in (say) ten years time!) ”

“ The Style Guide should be limited to giving guidelines compatible with producing sufficiently simple HTML amenable to rendering on as many desktop and mobile browsers as possible, and also with the Download utility family. Anything more is not going to stand the test of time as the consuming platforms of the coming decade will have characteristics we cannot currently even anticipate. ”

“ I suggest we should consider the de.ws way (one of the few places I'd suggest this) which is actually pro-preference in this arena. They have a strict style guide which they will aggressively enforce (e.g. all dashes are transcribed as en-dashes) , but they also have a firm rule that the person who sets up a work can make all sorts of deviations from the style guide by declaring the variations on the index page (e.g. em-dashes will be transcribed as em-dashes) . ”

“ The naming convention is for titles with no original capitalisation, intended to correct problematic titles like "Presidential Radio Address Of 17 May 2006" or "NEWSPAPER ARTICLE ON THE WAR OF 1812". For most words, the phrase "unless an original capitalisation is consistently used" overrides the previous statement. For example, if "Pride and Prejudice" is the most common capitalisation, that one should be used instead. Think of it as a default capitalisation for works with no original capitalisation. ”

“ As more prolific editors we intuitively do such things, however, for the casual editor, they will/may like to be guided.
Where we have probably been poor in documenting and enforcing is where a specific work varies from the style (for whatever reason) . We need to be much better at annotating the Index/Index talk pages where a work deviates from the norm; such would be on Index a note that says see the talk page for specific editing styles for the work in question. — billinghurst sDrewth 08:00, 23 December 2011 (UTC)
+1 for each work explaining its deviations from the style guide. ”

“ The most important thing is consistency within a work—whether that be the single page of the Treaty of Waitangi or the entire 70 volumes of the DNB.With respect to the straight vs curly quotation marks issue, the agreed norm is to use straight marks. ”

“ The underlying reason for this is the inability to type curly quotes directly from a standard keyboard in a Windows OS, but they can be typed in any of the Apple OS. Without the guideline in the Style Guide we would then risk having a mixture of curly and straight quotation marks in a work. That said, if the editors who join together on a particular work decide between them to use curly quotation marks, then that is allowed and is the norm for that work. "Fly-by" editors should not go against the consensus for that work. ”

“ It doesn't help that the default font here doesn't have a character for the thin spaces and so I see a couple of ugly little boxes on either side. Yes, there are times when colons and semicolons are spaced as words. This is mostly in liturgical works to assist with pointing the chant. However, in all other circumstances I think the space before is an artefact of the typesetting process and I find it ugly. With respect to double spaces after a full-stop: fortunately the software collapses these to a single space (although Hesperian's cleanup script does this anyway) . ”

“ We shouldn't require a "justification for [a] variance". The person who sets up the work sets the style and might just decide to follow another way because he or she likes it better, it's easier and they won't do it at all otherwise, or whatever. You seem to like ... and, apparently, straight quotes. I prefer curly quotes and will rarely bother to figure out which dash is which on the tools below but will instead type ߞ or —. ”

“ The DNB project made a decision for that project to standardise and use hyphens, and that was a simple way to have them as it is on the keyboard, and many just scanned that way (KISS) . At the same time, we do encourage redirects as many are done with ndashes. ”

“ Curly quotes is but one of the items on that list. --EncycloPetey (talk) 06:57, 12 December 2014 (UTC) I don't know how long ago you went to that library or what browsers they were using, but I say unequivocally that every browser in use today supports them. I defy anyone to show me one that doesn't. The "extra work" argument doesn't hold weight either, if I'm willing to do the extra work. I'm not saying to require them, just to allow them. Finally, left and right quotes aren't some quaint outdated convention but the standard in use in all printed matter to this day. ”

“ Definitely about two spaces between sentences, we obviously learnt from the same style guide for typing on an old-fashioned typewriter prior to word-processing justification. Our guidance about not doing pointless editing should stand. — billinghurst sDrewth 13:04, 22 December 2011 (UTC) I continue to not follow. I don't think "we are looking to impose rules" at all; except maybe with respect to dashes and hyphens because anyone who uses a hyphen-minus for a dash will likely get a talk page full of explanation and if they don't fix it, it will be fixed for them. ”

“ Let people do what they want; we can always fix things up later — far more important that people feel able to contribute! — Sam Wilson ( Talk • Contribs ) ... 05:22, 23 December 2011 (UTC) A few points/thoughts:
I've never bothered to change the standard browser font on this laptop and so I can't see the difference between "curly" quotes and "straight" quotes. This means that, because I can't type curly quotes directly I don't bother. If I was always editing on a Mac then I might consider it. Additionally, I use Hesperian's cleanup script which changes all curly quotes to straight ones. ”

“ Fwiw, of course we should use title case for the titles of works. It's right there in the title. Fine to link from sentence case. — LlywelynII 19:20, 5 March 2019 (UTC) Titles of compiled works I suggest a change in Wikisource:Style guide#Page titles, number 2, second bullet, as follows: When a work is a collection (e.g. poetry) or a compiled work (e.g. a journal or almanac) , then the subpages are works in their own right, and the original title of the work should be used in the subpage title. ”

“ NOTE that these classes are now redundant with the change to the underlying layout that is deployed in left hand side links. — billinghurst sDrewth 11:55, 4 November 2010 (UTC) Author naming convention Following on from the discussion about {{Initials}} on template's talk page and WS:S, it would seem that we have a policy to have full names, not partials (first/last) or initials. I would think that if we have the preference for full names then we should be specifically stating that, rather than leaving it for contributors to discover for themselves at a point in time. ”

“ But there was a work not long ago that specifically requested that contributors use 'em; I can't for the life of me find it now though, sorry.@Ekips39: I'm not really sure what you're saying? That curly quotes are less work than straight ones? I think double spacing and paragraph justification are things best 'normalised', just as we normalise font size or page margins (they can be changed by custom stylesheets anyway) . Quotes are different. — Sam Wilson ( Talk • Contribs ) ... 01:09, 12 December 2014 (UTC)
Curly quotes create technical problems and should be avoided. ”

“ Is "so much" work really being put in when double spacing and justification or lack thereof are not respected? (See pages of Index:US Senate Report on CIA Detention Interrogation Program.pdf.) Ekips39 (talk) 23:44, 11 December 2014 (UTC)
@Chowbok: Hm, yes it seems that I might be mistaken as to the level to which curly quotes are accepted. ”