Wikipedia talk:Manual of Style/Archive 204

Idiosyncratic styling
At Manchester Small-Scale Experimental Machine and other articles, User:Eric Corbett has styling the reference sections in a novel way using Template:style-nt that he created recently, to give himself control over text point size, whether or not an edit button appears by the headings, whether they show up in the TOC or not, and what-all. The coding looks cryptic, and it's hard to discern any good reason for not going with the usual default style that one gets with normal section and subsection heading markup. He keeps putting it back, with little justification; see User talk:Eric Corbett. Does the MOS have anything to say about editors going their own way on such styling? Dicklyon (talk) 04:28, 7 May 2018 (UTC)
 * What does it do? What's the point of writing documentation if nobody reads it? Eric   Corbett  04:55, 7 May 2018 (UTC)
 * This template should probably be submitted to WP:TFD. The headings are the way they are and users really shouldn't be trying to Make Pages Perfect With Respect To  Preferences. There is also a bit of false documentation regarding whether bold headings are allowed by MOS--they aren't. --Izno (talk) 05:15, 7 May 2018 (UTC)
 * That's not what the MoS says at all. What it explicitly discourages is the use of the semicolon as in ";pseudo-heading" to produce bold headings, not bold headings per se. And it strongly encourages the use of heading markup as in "===Real heading===" for accessibility reasons, which this template supports. But I'm interested in which part of the MoS you're using to justify your assertion that "users really shouldn't be trying to Make Their Pages Perfect". Do you have a link? Eric   Corbett  06:45, 7 May 2018 (UTC)
 * Focusing on the template issue is really to miss the point. I could, for instance, achieve a similar result to the template by prefixing a normal section header with something like and suffixing it with  , or I could even override the default look of a level 3 header - or any other - by writing a new CSS definition. What would the MoS have to say about that, and why should it care?  Eric   Corbett  07:12, 7 May 2018 (UTC)
 * Yes, you could do that, and it would likely get reverted (I see you've made a pointy edit to that effect at already). The use of the template is more insidious, as the naive editor will see it and just think it's some widely used way of making some consistent styling, rather than your personal idiosyncratic way of styling, which is what it really is.  Can't we all just use a consistent style?  Aren't you a software engineer?  Have you not bought in to the advantages of coding with a shared and understood style guide? Dicklyon (talk) 14:23, 7 May 2018 (UTC)
 * Why would it get reverted? In what way does it go against the guidance in the MoS? Of course we could all use a visually consistent style, this one for instance, which is more aesthetically pleasing than the default site-wide css for level 3 headers. Is it necessary to point out that the purpose of such css definitions is so that they can be overridden? And it's rather insulting to call my demonstration, clearly labelled as such, as pointy, but insulting behaviour appears to be your forte. One final thing: inconsistency in other areas of the MoS is actively encouraged, date formatting and spelling are two obvious examples. Is your next campaign going to be to force a single date format down everyone's throats? Eric   Corbett  14:35, 7 May 2018 (UTC)
 * That sounds uncomfortable. Dicklyon (talk) 14:46, 7 May 2018 (UTC)
 * To address the broader question: MoS is a guideline primarily about the most common WP-writing "style" (spelling, grammar, tone, layout, etc.) questions and problems. It is not the One True Source of all common sense and consensus on Wikipedia, the general operating principle of which is that what has been working fine for a long time and is well-accepted by the community is the consensus, even if it was not established in a particular discussion. If someone changes something about that de facto consensus, and the change is met with little or no objection then widely adopted by others, it becomes part of the new consensus. Otherwise, we'd have to have millions more consensus discussions and a huge database to keep track of them, a project that might exceed the scope fo WP's actual public-facing content. "MoS doesn't have a rule stopping me" doesn't equate to "I can do anything I want". Otherwise MoS would have to be longer than The Chicago Manual of Style combined with New Hart's Rules, to account for every imaginable style idea.  PS: I have no objection at all to adding an explicit MoS rule against using CSS tricks (manual or templated) to alter the default formatting of headings and other page elements, except inline CSS  a heading to make it conform to a particular MoS expectation. There may be some other already-accepted tweaks of this nature, such as ToC template options to suppress display of level-3 and lower headings in some cases when necessary to prevent excessively long tables of contents. If there's something wrong with how elements like the headings work on Wikipedia, and it can be addressed in CSS, then the idea should be proposed at Mediawiki talk:Common.css for inclusion in the site-wide stylesheet. If it's a sweeping change, it should probably be proposed at WP:VPTECH first.  — SMcCandlish ☏ ¢ 😼  00:45, 8 May 2018 (UTC)
 * One more question: what does the name style-nt mean?  nt for "next thing" maybe? Dicklyon (talk) 14:24, 7 May 2018 (UTC)
 * What does it matter? I would have preferred to call it simply style, but a template with that name already exists. Eric   Corbett  14:40, 7 May 2018 (UTC)
 * So why not style-ec? It matters because the Template namespace is intended to be understandable and usable by editors; it's not your personal playground. Dicklyon (talk) 14:46, 7 May 2018 (UTC)
 * I've really done with discussing anything with you, anywhere. You're quite impossible to deal with. Eric   Corbett  14:51, 7 May 2018 (UTC)
 * In what way? His point is correct and sensible, though what this template is named is the least of the concerns about it.  — SMcCandlish ☏ ¢ 😼  00:45, 8 May 2018 (UTC)

... you want to know…what it is? A specimen, for delectation. I like gadgets, this is fun! Batternut (talk) 11:08, 7 May 2018 (UTC)
 * Apparently WP isn't meant to be fun. ;-) Eric   Corbett  12:00, 7 May 2018 (UTC)
 * When misinterpreting WP as a CSS hacking playground and display case of Web-styling wizardry, that assessment is essentially correct. WP is meant to be an enjoyable environment in which to work on building an encyclopedia, but it's not even intended to be "fun" for readers, but simple and informative. It's not an entertainment website or a MMPORG, nor a place to flex one's Web coding skills in personally aesthetic ways. This is all covered at WP:NOT (#GAME, #WEBHOST, and some other sections).  — SMcCandlish ☏ ¢ 😼  00:45, 8 May 2018 (UTC)


 * See Templates for discussion/Log/2018 May 7 Jc3s5h (talk) 13:16, 7 May 2018 (UTC)
 * I was about to suggest TfD.  — SMcCandlish ☏ ¢ 😼  00:45, 8 May 2018 (UTC)
 * I don't think this really has anything to do with references, apart from the fact that the headings being formatted are in reference sections. The issue is using markup to change the way that section headings are formatted.   The MOS does not cover this explicitly, but that's because it does not try to discuss every convention.  In this case, there is a clear convention across the project not to try to change the font, size, weight, or other aspects of section titles. So editors should just leave that formatting as is, rather than trying to achieve some kind of special heading formatting in specific articles. I don't think this needs to be in the MOS, actually - 99.99% of editors seem to follow the convention without any trouble, so it's just a matter of fixing any uncommon articles that don't follow the convention. &mdash; Carl (CBM · talk) 15:18, 7 May 2018 (UTC)
 * Agreed. This isn't about refs, but about consistency of standardized interface elements – or, rather, about unusual deviations from that consistency which don't seem to provide enough reader utility to cover the editorial cost of the divergence, or the cost to reader expectations in loss of consistency. There's a reason we don't do things like switch to a green background and a Celtic-y uncial font at articles about Ireland, and so on, despite the sense that "designer" types have that it would be fun and evocative to do so.  WP is not a brochure, nor a Web-design experimentation platform. PS: Speaking of which, I'm strongly reminded of WP:TFD deleting quotation-stylization templates that attempted to mimic the blockquote styles of various blogging platforms.  — SMcCandlish ☏ ¢ 😼  00:45, 8 May 2018 (UTC); annotated further: 23:36, 18 May 2018 (UTC)
 * More on this matter at User talk:J3Mrs/Archive 16 where I was shot down for daring to question the purpose of what was, at the time, the template (I shall probably be shot down for bringing up the matter here, but I see it as germane to the topic). When I first saw this thread, I hadn't actually realised that  had originated as  which is why I've not commented here previously. -- Red rose64 &#x1f339; (talk) 07:26, 19 May 2018 (UTC)
 * Note: Multiple closely related templates&modules are being discussed at TFD Template:H4. Alsee (talk) 06:48, 24 May 2018 (UTC)

ndash vs hyphen vs slash in article titles
Advice is requested at Talk:Regional corporations and municipalities of Trinidad and Tobago. Shhhnotsoloud (talk) 07:26, 24 May 2018 (UTC)

Semi-protected edit request on 10 May 2018
In Manual_of_Style, it says sun, earth, and moon are not capitalized except in astronomical use. MOS:CELESTIALBODIES says the same exact thing except with solar system added. I am questioning whether solar system should be added to Manual_of_Style because the article title of the solar system on Wikipedia is capitalized while on other sites it is not. I can't think of other ways solar system is used outside of astronomical use. 2601:183:101:58D0:34E8:552C:3EB8:46BF (talk) 20:07, 10 May 2018 (UTC)
 * Umm ... you seem to be requesting that this page not be changed but rather MOSCELESTIALBODIES (which you could edit directly) be changed and the article Solar System be moved accordingly. For this reason, your edit request is unanswerable on its face. If I am misinterpreting you and you actually think this page should proscribe the use of "Solar System" ... well, that's not going to happen because you made an edit request on this page, unless there is also consensus to move the article. It should, however, be noted that there is not currently a contradiction between that article's title and MOS:CELESTIALBODIES; the article is about astronomy, and specifically our solar system (i.e., it's using it like a name rather than a common noun). That this page doesn't go into quite as much detail as the capitalization subpage should be a given. Hijiri 88 ( 聖やや ) 01:43, 17 May 2018 (UTC)
 * I think (aside from the fact that one page contains extra detail, which is not necessarily an error) that the anon is misunderstanding. "I can think of other ways solar system is used outside of astronomical use" is an indication of this.  If you say something like "There's a whole solar system of lobbyists orbiting around the senator", that's  something MoS (at either page) would have you capitalize, and this is not an oversight.  Nor would it have you capitalize "the solar system of Alpha Centauri", for that matter.  It means for you to capitalize  solar system when it is referred to as "the Solar System", a proper name.  It the same as astronomical use of "the Sun" to refer to our star as a celestial body.  But it's "She received a second-degree burn from extended sun exposure while unconscious in the desert". Here, it's a not a reference to the star, but a shortered version of "sunlight". If you were actually exposed to, literally, then you'd become plasma in under a nanosecond.  Sun even in an astronomical sense isn't capitalized when it doesn't mean  sun as a celestial body: "the two suns of Tatooine" (celestial body, not ours); "Apollo was the sun god of the Romans" (our sun, not as celestial body in the literal sense, but as something the ancients didn't understand and deified); "My car gleams as bright as the sun" (our sun, not as a celestial body literally, but as a source of light we squint at, used in a figurative sense).  — SMcCandlish ☏ ¢ 😼  23:14, 18 May 2018 (UTC)

Closing duplicate threads: This has also been forum-shopped or at least talk-forked to Wikipedia talk:Manual of Style/Capital letters (closed) and Talk:Solar System (speedy closure requested). — SMcCandlish ☏ ¢ 😼  23:11, 24 May 2018 (UTC)

Use of "founded" to describe in-name-only change of status of a municipal government?
The lead of our Katano, Osaka doesn't quite sit well with me. According to ja.wiki, the town of Katano was formally declared a "city" in 1971, but using "founded" brings to my mind an image of settlers venturing into the wilderness and establishing a new settlement. Our Takizawa, Iwate article describes a similar process with the word "promoted". There's also the problem of "new" municipal governments being established from mergers or dissolutions, which I also wouldn't think "founded" would accurately describe.

But this might all just be me and my hang-ups, so rather than changing it unilaterally (and I could almost certainly "get away with it") I figured I'd ask here. Thoughts?

Hijiri 88 ( 聖やや ) 01:33, 17 May 2018 (UTC)
 * Reading the Japanese version, it sounds like that's when it went from being a -chō "town" to a -shi "city". The ja.wp version describes the -chō as being "市制前の名称" ("the name before municipal organization"?)  I get the feeling that that's something like "incorporation". Curly "JFC" Turkey 🍁 ¡gobble! 01:45, 17 May 2018 (UTC)
 * No doubt - alternatives might be "achieved city status", "was declared a city" or something. Not founded if there was a pre-existing settlement. Johnbod (talk) 02:01, 17 May 2018 (UTC)
 * What about cases like Ōshū, Iwate, which was apparently "created" in 2006 from two cities, two towns and a village that had existed before without any specific connection to each other? I'd still be averse to saying "founded" when describing municipalities that were created from mergers even when no city called "Ōshū" had existed before. (BTW, I'm pretty sure the name of the city is just as arbitrary as it sounds.) It may be hypothetical because that article currently uses "established", which I'm fine with, but I'm pretty sure there are a lot of places like this in Japan and maybe elsewhere (not Ireland, if I recall, and I don't know a lot about others). Hijiri 88 ( 聖やや ) 07:07, 17 May 2018 (UTC)
 * "Merged" or "amalgamated" work—or "formed as a result of the amalgamation/merging of XXX and YYY". That was part of the whole 平成の大合併 about a decade-ish ago. Curly "JFC" Turkey 🍁 ¡gobble! 07:29, 17 May 2018 (UTC)
 * Yes - "founded" is really only appropriate for greenfield sites, or where there was just a little village. It's mainly appropriate for once-colonial places, or imperial whims. Johnbod (talk) 13:06, 17 May 2018 (UTC)
 * The term "incorporated" seems to be the more appropriate term, as far as I know, from municipal corporation. A city is incorporated rather than founded.-- Jayron 32 16:17, 18 May 2018 (UTC)
 * "Achieved" and "promoted" are PoV wording that presupposes that towns are worse, somehow, than cities. A neutral term would be "designated".  — SMcCandlish ☏ ¢ 😼  23:33, 18 May 2018 (UTC)
 * Towns are not worse, but lesser. Are majors "worse" than colonels? The term "incorporated" does not help when a town goes to a city. Johnbod (talk) 16:45, 20 May 2018 (UTC)
 * You're making my point for me, really. There is no hierarchical relationship between "city" and "town" (except perhaps within a particular municipality defined as a city and which has named its encompassed boroughs "towns" just to be a pain in the backside of collective understanding). If I live in the town of Apple Valley, California, the nearby cities of Victorville and Hesperia do not have jurisdiction over me (or control over my town's local government).  If I serve under Major D'Lemma, and she answers to Colonel Korn, I also answer to Korn. They cases are not even remotely parallel.  Anyway, the entire notion is still biased. Just read what you said: "Towns are ... lesser."  This simply isn't a true statement categorically, only by particular rubrics that happen to interest you, such as perhaps the population level, the square mileage, or the tax monies in the coffer.  By various other measures, cities are lesser.  Some typical examples are quality-of-life and safety-related, including crime rates, suicide rates, frequency of deaths by fires and car wrecks, pollution levels, and many other things. Many towns also have longer and richer histories than many cities, with many of the latter being less than a century old, especially in difficult ecozones like Arizona that take significant modern technology to be support large human settlements.  — SMcCandlish ☏ ¢ 😼  22:47, 23 May 2018 (UTC)
 * I think you're making my point here - none of this matters in the slightest for the issue at hand. What about villages? They can be lovely too. So what? Johnbod (talk) 15:03, 24 May 2018 (UTC)
 * , they aren't in a better/superior/commanding versus worse/lesser/subordinate hierarchy, in which wording like "achieved" and "promoted" might make sense. I thought that was pretty clear in my first post, especially since we have wording like "designated" that is accurate (the labels are an official designation, not a law of nature) and doesn't have this PoV problem, nor the reader confusion (hell, confusion) problem of "founded" or "established" being used for something that was actually founded/established long before the city designation.  — SMcCandlish ☏ ¢ 😼  23:19, 24 May 2018 (UTC)
 * This started off dealing with Japanese cities, now it is appearing to be US-centric. Frankly if any city hasn't got roots of a thousand or more years it ought to be called a modern town. :-)  Consider the cities of Heidelberg, London, Rome, Athens and then approach on bended knee. Martin of Sheffield (talk) 13:27, 24 May 2018 (UTC)


 * I noticed the same thing in another article, there are three people claiming to be the first mayor of a location. One was mayor when it was part of another township, one was mayor when it was incorporated as a township on its own, and the final one was mayor when it was reorganized as a city. The obituaries all call them the first mayor of the location and the local government does not keep a canonical list. --RAN (talk) 14:55, 20 May 2018 (UTC)
 * So we should simply be specific: "first mayor of the township of Foo", "first mayor of the city of Foo", or whatever the case may be. Sometimes this requires better research than that performed by an obit writer.  — SMcCandlish ☏ ¢ 😼  22:47, 23 May 2018 (UTC)
 * Local government reorganisations, like rail-replacement buses are a local speciality round my way. Take a look at City of Rochester-upon-Medway to see multiple ways of describing the disruption. ClemRutter (talk) 08:04, 23 May 2018 (UTC)
 * Rochester. The only English town to lose its city status by accident. -- Red rose64 &#x1f339; (talk) 22:49, 23 May 2018 (UTC)

Semicolons.
Is their a stylistic difference we should be aware of between en-us and en-gb usage of semicolons? There obviously is a difference in what we call conjunctival adverbs - does this permeate further?--ClemRutter (talk) 19:02, 22 May 2018 (UTC) IMHO there's no encyplopedic reason to insist on any particular usage or to correct an article's usage of semicolons; however,  tags should always be respected. — Stanning (talk) 20:20, 22 May 2018 (UTC)
 * In both variants, AFAIK there's no pedantically fixed standard, and use or non-use of the semcolon varies between writers. The article on the semicolon has some opinions on its use. Here's a New Yorker article: Semicolons; So Tricky. Here's a fairly standard note on British usage from the university of Leicester (England): Using the semi-colon and colon.
 * Except that comma and semicolon usage in various articles here is often wrong by all "standards". If you think you're going to get some moratorium on cleanup of their abuse, think again.  — SMcCandlish ☏ ¢ 😼  22:33, 23 May 2018 (UTC)
 * Just a question that came up while training- you have to check before you give too forceful an answer! ClemRutter (talk) 22:50, 23 May 2018 (UTC) ;}
 * Sure. I was responding to Stanning's serious misstatement, "there's no encyplopedic reason to insist on any particular usage or to correct an article's usage of semicolons", which is just flat-out wrong in both parts. Otherwise MoS would have nothing on semicolons, nor would off-WP major style guides, but of course they do, because there are actual norms of use, most of which are cross-dialect.  — SMcCandlish ☏ ¢ 😼  23:21, 24 May 2018 (UTC)

In particular/usually
I made an edit to change the wording "in particular" to "usually" to more accurately reflect the content of the guideline, which state, "Capitalize the title's initial letter (except in rare cases, such as eBay), but otherwise follow sentence case[b] (Funding of UNESCO projects) not title case (Funding of UNESCO Projects). This does not apply where the title would be title case in ordinary prose". I summarize this that usually, not always, section headings should use sentence case, not title case. previously made an addition to the guideline, stating that "In particular, they should use sentence case, not title case (capitalize only the first word and proper names in headings)". This wording implies that in all cases the section heading should use sentence case, ignoring the exceptions mentioned in the article titles guideline. Therefore I changed "in particular" for "usually". Thinker78 (talk) 06:14, 24 May 2018 (UTC)
 * I saw that one, and pondered on which was right, concluding that neither reflected the meaning. Have you considered just using the humble colon to connect the two independent but closely related sentences. --ClemRutter (talk) 09:48, 24 May 2018 (UTC)
 * The only thing at title that's particularly relevant to headings is the capitalization; the "usually" or colon doesn't really connect this remark as intended. So I went back to "In particular" and noted that there are exceptions.  See if that's more satisfying now. Dicklyon (talk) 14:16, 24 May 2018 (UTC)
 * Saw those edits... I like how it is with the "in particular" but then mentioning there are rare exceptions. I was wondering though... other than eBay, iPad, etc... are there any other exceptions? It says "except when the title would be title case in ordinary prose" but I'm having a hard time thinking up an example of that. Does it simply mean when the title of a work, for instance, is included in a section or article title, say "Imagery in A Clockwork Orange"? Or am I missing some other weird case? —Joeyconnick (talk) 18:13, 24 May 2018 (UTC)
 * I don't know. If and when exceptions are needed, I'd expect them to be obvious. Dicklyon (talk) 21:21, 24 May 2018 (UTC)
 * And it's not rational to assume that if one statement is simple, and another details some rare exceptions, that the exceptions don't apply because the other section didn't mention them. Much of the main MoS page is a glossing over of details and exceptions, the goal at this page being to lay out generalities. This is even true of material in one section that defers to material in another section of the same page with more detail on whatever that little side matter is. I have no objection to rewording either or both bits, as long as the intended meaning isn't changed.  — SMcCandlish ☏ ¢ 😼  23:26, 24 May 2018 (UTC)

List of definitions?
Someone added a list of symbol definitions for equations in the Lateral earth pressure article. All the definitions are correct, and they will help reading the equations in the article. My question is whether this table should be its own section, whether it should be a table or a list, and other stylistic questions about its placement. It's not whether the information belongs in the article, it's how the information should be presented. The presentation is a very textbook sort of presentation, and textbook is one of those things which Wikipedia is not. So what say you style mavens? — Preceding unsigned comment added by Argyriou (talk • contribs) 00:06, 23 May 2018 (UTC)
 * Containing one element of a textbook, does not make it a textbook article. I expect symbols to be identified in a mathematical article. In articles on films, I expect the characters in the plot summary to be identified in a list or table. --RAN (talk) 02:53, 23 May 2018 (UTC)
 * Presumably you refer to ; since it is a list of definitions, mark it up as a definition list, . -- Red rose64 &#x1f339; (talk) 20:55, 23 May 2018 (UTC)
 * Agreed that's the right markup. We even have a nice template system for it, covered in detail at MOS:GLOSSARIES.  — SMcCandlish ☏ ¢ 😼  01:54, 27 May 2018 (UTC)
 * If it's not something we made up and it might be useful for other articles, maybe it should be its own article. We have many glossaries and other lists.  — SMcCandlish ☏ ¢ 😼  23:27, 24 May 2018 (UTC)

Citing a bowdlerised source
Comments welcome at Talk:Bruce McArthur. The source reads I'm tired of these f---ing f---ots but that supports and verifies that the (alleged) statement was I'm tired of these fucking faggots. By the letter of the MOS we should reproduce the bowdlerised version, but by its spirit I think we should reproduce the quotation exactly as (allegedly) said. Andrewa (talk) 16:20, 26 May 2018 (UTC)
 * I notified WT:Citing sources and WT:Verifiability about this thread, since it's more about sourcing than style.  — SMcCandlish ☏ ¢ 😼  00:49, 27 May 2018 (UTC)

Just to clarify, I'm not suggesting that we ever guess what the source means. But I am suggesting that when a reliable source is clear and explicit as to what was really said, but employs bowdlerisation because of the source's own style and content policies, and when the bowdlerisation has only one reasonable interpretation (as in the example), then we should read the source as verifying the unbowdlerised version. Because that is the only reasonable reading of the source.
 * Use attribution would be my solution: 'According to Title of Source, McArthur said: "I'm tired of these f---ing f---ots".' Or use something more specific, e.g. 'According to an article by I. M. Whoever, ...'.  — SMcCandlish ☏ ¢ 😼  00:49, 27 May 2018 (UTC)
 * That would solve the problem, but it's a bit wordy and seems unnecessarily so to me... Surely, if I.M Whoever is a reliable source and states McArthur said: "I'm tired of these f---ing f---ots" in writing, we have verified by this source that McArthur in fact said "I'm tired of these fucking faggots"? But yes, it does overcome the more serious problem... McArthur did not say "I'm tired of these f---ing f---ots", and to cite this source as verifying that he did say this, rather than that he said I'm tired of these fucking faggots'', is f---ing ridiculous. But a legalistic reading of the MOS did, in this example, lead to our article saying exactly that. Andrewa (talk) 09:18, 27 May 2018 (UTC)
 * "McArthur is quoted by Whoever as saying..."? This establishes that this isn't directly what McArthur said, just how the source quotes them. Ian.thomson (talk) 17:25, 27 May 2018 (UTC)
 * The "style" question – the question of writing – is whether this quotation is actually necessary at all. That paragraph feels a bit too blow-by-blow for me:  Some (apparently random) guy describes a ten-minute temper tantrum that has no direct connection to the "plot".  Encyclopedias do more "telling" than "showing".  If the person telling the story is just some random acquaintance, it should be omitted altogether; if it isn't, then the connection should be explained (e.g., "father of one of the murder victims" or "brother of the accused") and the content should be summarized concisely:  "He had an explosive temper".  WhatamIdoing (talk) 05:42, 27 May 2018 (UTC)
 * That's another issue that may apply to this particular example, but ISTM it's a content issue. Andrewa (talk) 09:18, 27 May 2018 (UTC)
 * Unless there is an alternative source, we do not know for certain what McArthur did say. He might have said those "flaming flibbertigibbots".  Unlikely, I know, but SMcC's suggestion avoids (mis)interpretation. Martin of Sheffield (talk) 17:21, 27 May 2018 (UTC)
 * Strongly disagree. While I agree we do not know for certain what McArthur did say, that's splitting hairs. We know what the source says, and when we say they're reliable we assume that they're not deliberately misleading us! And to say that he said I'm tired of these f---ing f---ots when in fact he said flaming flibbertigibbots would be so misleading, it would be reasonable to call it deliberate. So it's not a guess (as the edit summary of that last post claims) that according to the source he said fucking faggots. It is the only sensible reading of the source. Andrewa (talk) 18:39, 27 May 2018 (UTC)

If, on the other hand, we publish the bowdlerised version while knowing full well what the source means, we are ourselves guilty of bowdlerisation. Which is of course contrary to policy, and surely the MOS should reflect this policy? Andrewa (talk) 18:51, 27 May 2018 (UTC)

See WP:BOWDLERIZE on precisely this point "However, when quoting relevant material, rendering a quotation as it appears in the source cited trumps this style guideline". WP is not bowdlerising, the original source is. If you are worried, use the format suggested above and add to clarify: 'According to Title of Source, McArthur said: "I'm tired of these f---ing f---ots [sic]".'  See MOS:SIC for guidance. Martin of Sheffield (talk) 19:16, 27 May 2018 (UTC)

Guideline clarification proposal to curtail MOS:TM vs WP:TITLETM gaming
Please see Wikipedia talk:Manual of Style/Trademarks — SMcCandlish ☏ ¢ 😼  20:59, 28 May 2018 (UTC)

In re single subsections
Please see Wikipedia talk:Manual of Style/Film, on whether the use of a single ===Subsection=== (rather than two or more) within a ==Section== is compatible with good writing style. Please comment over there, not here. WhatamIdoing (talk) 23:33, 28 May 2018 (UTC)

MOS for portals
I've started a draft Manual of Style/Portals, which would formalise the applicability of the MOS to portals, with just a few exceptions. Your feedback would be appreciated – discussion is taking place at (please respond there, not here). Thanks, Evad37 &#91;talk] 16:35, 27 May 2018 (UTC)
 * Thanks for doing that. Looking good so far. Dicklyon (talk) 17:00, 27 May 2018 (UTC)

Discussion at Wikipedia talk:Manual of Style/Portals
You are invited to join the discussion at Wikipedia talk:Manual of Style/Portals. - Evad37 &#91;talk] 03:00, 31 May 2018 (UTC)

MOS:GNL side-matter
Please see Talk:Gender neutrality in languages with grammatical gender

People who edit here may be interested in it. The gist: there's a pattern of using the single character x as a stand-in for "a or e/i/o depending on your gender", and it's increasingly coming up in the proper names of organizations, forums, etc. So, we might want to address (in a footnote?) either here or at WP:GNL that good markup for this sort of thing is, for example,   or the equivalent   (rendered: usuari x s) as the shorthand for "usuarios/usuarias" or "usuari[a|o]s" or whatever. This will alert editors that the x is not a typo but a metasyntactic variable. This mark-it-up approach is consistent with various advised uses of or. — SMcCandlish ☏ ¢ 😼  05:13, 2 June 2018 (UTC)
 * Is it standard to render the x in a different font than the rest of the text, the way your markup does? That formatting looks ugly, because fonts are not designed to mix in the middle of words like that so the kerning is wrong. —David Eppstein (talk) 07:07, 2 June 2018 (UTC)
 * Please centralize the discussion at the thread pointed to. Avoding talkforks is why we make pointers from one page to a thread at another. :-)   — SMcCandlish ☏ ¢ 😼  00:42, 8 June 2018 (UTC)

RfC
An RfC concerning the categorization of biracial people has been opened at Wikipedia talk:Categorization/Ethnicity, gender, religion and sexuality. StAnselm (talk) 04:31, 31 May 2018 (UTC)
 * It does touch on MOS:IDENTITY but seems mostly to be a WP:NOR dispute (including about the term biracial and when to apply it, though it's mostly actually about African[-]American in the context of Meghan Markle).  — SMcCandlish ☏ ¢ 😼  06:43, 9 June 2018 (UTC)

Singular possessives in -s
It's somewhat unfortunate that the section on Possessives includes "Jesus" as an example (Jesus's teachings). Whereas it's fine to add apostrophe+s on names ending in -s the most well-known exception to this in many style manuals is Jesus, which adds only the apostrophe: Jesus' teachings. I'm not saying that MOS needs to adhere to what most style manuals do, I'm only saying that we shouldn't pick as our example to illustrate the general -s rule, the most famous example which is an exception to that rule in many style guides; we can pick something else. Here is Bryan Garner:"To form a singular possessive, add -&apos;s to most singular nouns&mdash;even those ending in -s and -x (hence witness&apos;s, Vitex&apos;s, Jones&apos;s, Nichols&apos;s). ... There are three exceptions to this rule. The first is the standard one: Biblical and classical names ending in -s take only an apostrophe:, hence Jesus' suffering, Moses' discovery, Aristophanes' plays, Grotius' writings. (No extra syllable is added in sounding the possessive form.) The second exception is words formed from the plural. Thus General Motors should make General Motors&apos;&mdash;e.g.: 'A merger by General Motors will excite great interest in an enforcement agency simply because of General Motors&apos;s [read General Motors&apos; ] size.'" HTH, Mathglot (talk) 09:07, 8 June 2018 (UTC) — SMcCandlish ☏ ¢ 😼  12:05, 8 June 2018 (UTC)
 * Consider, perhaps, that it was chosen because some style guides make such an exception, others don't, and the intent here is to dissuade insistence on that variance because "my style guide at work says so". Also, as of the edition put out last year, The Chicago Manual of Style (which has much more buy-in than Garner's Modern English Usage, a.k.a. Garner's Modern American Usage until its latest version) has shifted strongly away from such exception-making, for the first time in generations (though it observes that some do use such exceptions; the Hafiz' and Beatrix' variants are also fairly common). The relevant material in CMoS – the whole set of chapters on grammar, punctuation, and spelling, actually – were actually written by Garner under contract. So, either his own position is shifting, or he gives conflicting advice in different books on purpose, but a purpose we can't, of course, psychically determine. And Garner isn't a linguist, he's an attorney. Many of the things he says about language are demonstrably wrong (e.g. "No extra syllable is added in sounding the possessive form" is only true in some regional dialects, and not a majority of them). Regardless, the CMoS shift is an indication that "Jesus isn't a rule in a sense we should care about here, but a subjective preference of some American writers and editors primarily (it's neither exclusive to them nor consistent among them), and is slipping in acceptance because it's confusing and illogical (it seems to've been picked from the Elizabethan-era [pre-orthography-standardization] King James Bible, used by many American Protestant sects, and retained in the 20th century because it coincides with a particular, blurred pronunciation in some variants of US Midwestern English (and some other dialects, e.g. in parts of Texas [that's /ˈtɛksəz/ !], though CMoS wouldn't care). But it isn't actually dominant across the language or even in the US. Our own conversations on this page show it; every time the issue comes up, editors from around the English speaking world and the US more narrowly tell us that they pronounce "Jesus" and "Jesus'[s]" differently, with a distinct syllable added to the possessive (the suprasegmental length is apt to vary, and might be rather short; it is for me).  There is no escaping a simple fact: for every single point of English usage on which different self-styled authorities disagree, there will always be some subset of readers and editors who don't like the version we pick. So, MoS works best when it detects and defuses "style-guide thumping" that's likely to recurrently arise.  E.g., we've done the same thing with capitalization of prepositions in titles of works, something that style guides disagree on even in the same field, like journalism, and which is often laden with style-guide-specific exceptions. We just swept away the exceptions as inconsistent and troublesome, and went with neither of the more extreme approaches.
 * So there! Any more questions? EEng 14:06, 8 June 2018 (UTC)
 * [sigh] The intent isn't to WP:WIN, it's cover what the rationale is for the MoS wording, and why a "Garner says ..." observation isn't particularly meaningful as an isolated point, without both comparison to other style guides and awareness that Garner writes more than one of them (at least 4 to date), often inconsistently. (Aside: As far as I can tell, Garner has carved this niche simply by having been one of the editors of Black's Law Dictionary; it's what got his foot in the door to put out A Dictionary of Modern American Usage in 1998, when OUP figured there was a market for an American counter to the very British Fowler's (and of course wanted to publish both of them).  — SMcCandlish ☏ ¢ 😼  22:36, 8 June 2018 (UTC)
 * Actually, that example is there simply to illustrate what "rearrange the wording" means with a practical example. It is carefully worded so as not to give the impression that it is an example of a possessive that is difficult to pronounce, or indeed the reverse (hence my revert of yesterday's bold edit, which changed the phrasing so as to make it such an example).  We sidestepped the question of whether Jesus's is or is not "difficult to pronounce" and simply offered the two alternative phrasings to illustrate the preceding provision in the MoS. MapReader (talk)
 * That's reason it's there. I'm pretty sure I wrote the wording in question.  :-)   — SMcCandlish ☏ ¢ 😼  23:04, 12 June 2018 (UTC)

A move review to consider
Please see Move review. Some comments at WT:MOSCAPS has suggested there could be insufficient input so far to reach a clear consensus. Depending on how it turns out, MOS:JOBTITLES might require substantial revision, which could in turn affect the wording at the main MoS guideline. (That might or might not be a good idea, but people who watch this page should be aware of it either way.)  — SMcCandlish ☏ ¢ 😼  03:12, 14 June 2018 (UTC)

MoS section merge discussion
Please see Wikipedia talk:Manual of Style/Biographies.

The proposal is to merge WP:Manual of Style/Capital letters (a.k.a. MOS:JOBTITLES) to WP:Manual of Style/Biographies, where the rest of the material about human titles is (academic, post-nominal, honorific, regnal, etc.). A short summary and hatnote pointer would be left behind in MOS:CAPS (about the same as those presently at found at MOS:CAPS pointing to MOS:CAPS; the relationship would simply be reversed). — SMcCandlish ☏ ¢ 😼  06:50, 14 June 2018 (UTC)

A whole lot of MoS-related WP:Redirects for discussion
Please see: The "NOTES" one proposes that "MOS:" shortcuts should point to non-Manual of Style pages. The AMEN and BRIT ones are about ambiguity. The pseudo-namespace ones boil down to this: "MOS:" is a pseudo-namespace created, after a consensus discussion, to point to WP's Manual of Style and sections and subpages thereof, to deal with the decreasing availability of meaningful and memorable "WP:"-namespace shortcuts, and because there's often an MoS page and a content, naming, or other page about the same thing. However, pseudo-namespaces are actually in mainspace (articlespace). Some editors thus do not want to see a profusion of "typo redirects" like "MoS:CAPS", "mos:CAPS", "Wikipedia:MOS:CAPS", etc., while others are convinced that all redirects are necessarily "cheap" and always should be permitted even if only used by a handful of editors and of no use to readers. — SMcCandlish ☏ ¢ 😼  06:42, 10 June 2018 (UTC)
 * Redirects for discussion/Log/2018 June 7 – possible retargeting
 * Redirects for discussion/Log/2018 June 5 – possible deletion
 * Redirects for discussion/Log/2018 June 5 – possible deletion
 * Redirects for discussion/Log/2018 June 4 – possible deletion (of "Mos:" not "MOS:")
 * Redirects_for_discussion/Log/2018 June_3 – possible deletion (of "MoS:" not "MOS:")
 * Redirects_for_discussion/Log/2018 June 3 – possible deletion (of double-namespace version)
 * There's some follow-up discussion relating to the now-closed RfDs about the pseudo-pseudo-namespace ones, at User talk:Amorymeltzer.  — SMcCandlish ☏ ¢ 😼  01:06, 15 June 2018 (UTC)

Towards or toward
Quick question... In a statement such as: “The media’s attitude toward(s) the military shifted during the war”, should we use “toward” or “towards”. Blueboar (talk) 17:42, 3 June 2018 (UTC) Blueboar (talk) 17:42, 3 June 2018 (UTC)
 * I believe "toward" is preferred for American English, and "towards" for British English. The same style generally applies to other directional words as well (e.g. forward/forwards). - adamstom97 (talk) 21:46, 3 June 2018 (UTC)

Isn't this a better question for the Refdesk? Primergrey (talk) 21:48, 3 June 2018 (UTC)
 * Yeah... but I knew I would get a quicker answer here. Thanks. Blueboar (talk) 13:44, 4 June 2018 (UTC)
 * Bryan Garner is my go-to guy for this, and he agrees with adamstom97 on AE/BE distinction. However, this may be the wrong word entirely in this situation.  As Garner says, Misused for to. Toward implies movement. It shoudln't be used when the sentence would be served by to or against&mdash;e.g.,... followed by three bulleted examples. The examples include expressions like "objections toward" (use to), or "prejudice toward" (use against).  Attitude isn't movement, so my guess would be that you should probably not be using toward here, maybe about? However a quick check of other online grammar resources seems to indicate a preference for toward/s with attitude. Ngrams shows the top ten prepositions after attitude, but doesn't include multi-word expressions like with respect to or vis-a-vis. Mathglot (talk) 04:06, 8 June 2018 (UTC)
 * An additional way we approach this, especially on WP, is MOS:COMMONALITY, which is more important than the argument to authority inherit in relying on a favorite style book. There is no intelligibility problem with toward, in any dialect, so it's preferable for concision. However, towards isn't an unencyclopedic colloquialism, even in American English, so MOS:RETAIN would suggest not going around changing it to toward just for the heck of it (especially not as a trivial edit unto itself), since the potential editorial kvetching would probably not be worth saving a character here or there. If I were writing a new article, or substantively overhauling an extant one, I would use toward (if it weren't better replaced by to, etc., as Mathglot says). Same goes for similar words like forward[s], amid[st], etc.  — SMcCandlish ☏ ¢ 😼  06:41, 9 June 2018 (UTC)
 * This American finds the usage of "toward" in that construction to be extremely jarring. The point about movement sums up the usage I am familiar with. --Khajidha (talk) 04:13, 15 June 2018 (UTC)

If this isn't a suggestion to include some sort of guidance on this particular point to the MOS, then this entire discussion ought to be at the refdesk or a user's talkpage...no? Primergrey (talk) 00:13, 13 June 2018 (UTC)
 * Agreed, this is not WP:RDL. But (to me) it isn't clear that does not propose an MOS change. &#8213; Mandruss   &#9742;  00:20, 13 June 2018 (UTC)
 * My bad, per I knew I would get a quicker answer here. Make that: This is not WP:RDL, speed of answer irrelevant. &#8213; Mandruss  &#9742;  00:22, 13 June 2018 (UTC)

Ellipses, capitalization, and whether an example of a common construction constitutes a quotation
Please see Talk:Ellipsis. — SMcCandlish ☏ ¢ 😼  05:14, 19 June 2018 (UTC)
 * Additional input requested. This has turned completely circular in WP:IDHT fashion.  — SMcCandlish ☏ ¢ 😼  18:32, 21 June 2018 (UTC)

Why capital S?
Why is this page titled Manual of Style, not Manual of style? --SmokeyJoe (talk) 07:06, 22 June 2018 (UTC)
 * This should be a good one. EEng 07:19, 22 June 2018 (UTC)
 * I imagined it was based upon the ancient Manual of Stylos, the Greek etymology of the village being 'column' or 'pillar', with the MoS being the pillar that supports all good editing? But I am sure that other views are available... MapReader (talk) 09:58, 22 June 2018 (UTC)
 * Indeed. It was brought unto us by the ancients, passed down generation-to-generation by the Secret Order of Stylos (now a subsidiary of Brotherhood of the Cruciform Sword).  — SMcCandlish ☏ ¢ 😼  12:07, 22 June 2018 (UTC)
 * There was a discussion about it way back when. The gist is that it's intended as a work, of sorts. It was also observed that various other project pages, like a lot of wikiprojects, use title case. I'm not sure anyone feels strongly about it these days.  My only qualm would be that lowercasing these pages would produce an  redirect cleanup job, which might have to be done manually. The recent move of WP:Manual of Style/Biographies to WP:Manual of Style/Biography had the double-redirect-fixing bot actually fail to do its job. Just fixing shortcuts to that page alone took me about two hours.  I don't know who'd volunteer to fix several thousand redirs to all the MoS pages.  Also, we typically abbreviate it "MoS", which would no longer make sense if it was down-cased to "style".  In short, I don't think a lower-case tweak would be worth the effort. We're going to have a consistency issue no matter what: either it's not consistent with our mainspace article titles, or it's not consistent with its own advice on how to style the titles of works like The Chicago Manual of Style. So, I think we should choose the path of least agony and leave it as-is.  — SMcCandlish ☏ ¢ 😼  12:07, 22 June 2018 (UTC)

Variants of English
Should Singapore English be included for Singapore-related articles? -- occono (talk) 17:58, 22 June 2018 (UTC) — SMcCandlish ☏ ¢ 😼  18:41, 22 June 2018 (UTC)
 * Stand by for a tongue-lashing (so to speak) (so to speak) . EEng 18:07, 22 June 2018 (UTC)
 * We should not list anything that doesn't exist in a codified, formal written register with its own style guides, distinct from British/Commonwealth English in general (Canadian and Australian English do, and I think I saw one for New Zealand, and maybe South African). In virtually all other former countries of the British Empire where English is still used as a first language by a notable percentage of the population, they refer to British style guides like New Hart's Rules, New Oxford Dictionary for Writers and Editors (combined as New Oxford Style Manual), Fowler's Dictionary of Modern English Usage, The Cambridge Guide to English Usage, etc. Even most of the journalism and lower-register professional writing (business, marketing) follows the same shared conventions as BBC News (a dominant news provider in most of them), The Guardian, The Times, The Economist, etc. I've been looking for, and I cannot find any "produced for public use" style guides for places like Malta, Pakistan, Kenya, Grenada, Singapore, Belize, etc., etc.  These dialects exist almost entirely as  dialects and  writing based on it, but WP isn't written in informal English, so it's not an ENGVAR matter.  Formal writing from such places is generally indistinguishable from British, aside from some locally specific vocabulary words (just as you'll find in Wales or Scotland). Editors branding "their" articles as being written in such dialects is a) nonsense and b) a recipe for insertion of unencyclopedic colloquialisms.  There's a good reason we don't have templates for "This article is written in Texan English" and "This article is written in Cockney".  There's more difference between Texan and Manhattan English, and between Cockney and Shetland English as dialects than there is between written formal Singaporean or Maltese English and written formal British English.  Basically, WP isn't written in bar/pub talk, and we mustn't pretend otherwise just because a handful of editors want to slap huge flag-waving banner templates in articles' editnotices for territorialism and national-pride reasons.  PS: Listing Irish English is basically an "avoid an ethno-political shitshow" concession; at the formal written level it also follows British norms (and I have yet to see an Irish English style guide), but people might quite literally threaten each other over putting "Use British English" templates on Ireland-related articles.
 * and and related templates and categories now exist.  We should consider nominating templates we don't need for merger with and redirection to the Commonwealth versions.  — SMcCandlish ☏ ¢ 😼  20:17, 22 June 2018 (UTC)

MOS:CONFORM and citation titles
In sourcing for most contemporary entertainment, sources generally omit italics or the like to format the name of the work being discussed in the title of their articles. So it seems that most of our citations/references generally end up presented these citation titles without italics/etc. for named works. Should MOS:CONFORM apply to citation titles, considering that these are technically quotations ? I do know we frequently removal allcaps and other unreadible aspects of titles in citations, so it would seem logical to apply appropriate MOS-elements like italics where they can apply. --M asem (t) 13:21, 16 June 2018 (UTC)
 * Yes. Any given written source will do any of at least 10 different things in presenting the title of a major published work inside the title one of that source's articles (e.g. giving a movie title in the title of a review of the movie): 1) italics, 2) double quotes, 3) single quotes, 4) bold-face, 5) ALL-CAPS, 6)  (rarely), 7) underline (rarely), 8) some other font tweaking (rarely), 9) some combination of more than one of these, 10) no markup at all.  This is just farcically messy, and trying to mimic the other publication's style, under their stylesheet, in our citations is "reader-hateful" and just not what we would do in any other circumstance (e.g. we do not mimic logo stylization per MOS:TM, we do not over-capitalize job titles and do other "specialized-style fallacy" mimicry of other organization's house style quirks).  We already routinely down-case any SCREAMING ALL-CAPS HEADLINES to title case (or to sentence case, if the citation style in question demands that for article titles), and do other font normalization in our citations (e.g., if a title looks boldface in the original publication, we do not ape that stylization here). This isn't any different.  For over 12 years, I've been doing cleanup of this sort, especially italicizing the names of books and films in review articles' titles (per MOS:TITLES), and italicizing genus and species scientific names in biology journal article citations (per MOS:LIFE), and as far as I can tell not one single person has ever reverted me on it.  It's completely normal do this sort of MOS:CONFORM tweaking.  — SMcCandlish ☏ ¢ 😼  11:22, 17 June 2018 (UTC)
 * This clearly makes sense, but it should be qualified somewhere, as I ask from seeing a recent dispute on a video game article. (assuming this is the consensus). --M asem (t) 15:21, 17 June 2018 (UTC)
 * Meh. We should generally avoid adding redundant line-items that simply re-state what can already be intuited from the existing ones and from actual overall editorial behavior. At an infrequent and weird dispute at an article talk page, maybe just point people to this thread (here now, or later at its eventual archive location).  If we kept adding "rules" we don't strictly need (i.e., ones that do not address an actually frequent dispute type), we'd have thousands more lines in MoS, a major WP:CREEP problem.  — SMcCandlish ☏ ¢ 😼  20:14, 17 June 2018 (UTC)
 * Maybe this could be addressed in a footnote, if we can come up with a concise one. And/or maybe address it at MOS:TITLES instead of the main MoS page. Length is less of a concern in a topical MoS subpage.  — SMcCandlish ☏ ¢ 😼  20:22, 22 June 2018 (UTC)

New RFC on linking to Wikidata
Should we ban links to wikidata within the body of an article? --Rusf10 (talk) 00:50, 10 May 2018 (UTC)

Background
Over two months ago we had an RFC on linking to Wikidata, the result of which was "no consensus". I initiated the RFC after a user was continually adding links to wikidata to replace articles that were deleted through AfD for notability concerns, here is an example. Unfortunately, I did not create the question that we voted on and it was worded with the extreme position of "Never link to Wikidata" which got mixed support. I think most people generally agree that the links are the sidebar are useful (in particular the inter-language links) and should not be removed. However, within the body of the article there was less support for using wikidata. Some people also indicated that inline interlanguage links (see WP:ILL) may also be appropriate. However, almost everyone agreed wikidata links should not be a substitute for a red-link (or a deleted article). While I agree that linking different language versions of wikipedia is a great feature, otherwise I find wikidata to be unreliable and directly linking to it would be confusing for the average user.--Rusf10 (talk) 00:50, 10 May 2018 (UTC)

NOTE- Since there is another RFC on using wikidata in infoboxes, none of the options below will apply to the usage of wikidata in infoboxes since that is being determined separately.

I'm providing three options:
 * 1) Support- Wikidata should not be linked to within the body of the article (this includes hidden text links). This will have no impact on the sidebar links nor Authority control
 * 2) Support, but with exception for inline inter-language links- Same as above, but allows for exception for use of Template:Interlanguage link
 * 3) Oppose-Link to Wikidata if an article does not exist

I am adding an additional option to clarify: --RAN (talk) 03:16, 10 May 2018 (UTC)

4. Oppose- Allow hidden text links with Wikidata Q-numbers such as <!-Q1123456--> so that a duplicate Wikidata entry is not created in the future

And another, because the one above isn't an oppose rationale but another exception:

5. Support, with two exceptions: for inline inter-language links and hidden-text Q numbers, as described above. — SMcCandlish ☏ ¢ 😼  09:54, 18 May 2018 (UTC)

Survey
PS: I also agree with Tony1 that an "External links" entry (a regular line-item or a templated one) might be appropriate, as we'd use for a Wiktionary entry, etc. But we don't need any kind of policy change with regard to that, since it's already covered by WP:EL and MOS:LAYOUT as a general matter. I.e., this RfC isn't going to magically carve out a special exception to those rules, so people can stop wringing their hands about it and casting FUD at the RfC. — SMcCandlish ☏ ¢ 😼  12:56, 20 May 2018 (UTC)
 * Support- full ban in body of article as proposer.--Rusf10 (talk) 00:50, 10 May 2018 (UTC)
 * NOTE: Some !voters below may have arrived via partisan audience CANVASS. This RFC was posted & linked on the Wikidata central Project Chat at 01:52, 10 May 2018. Alsee (talk) 01:33, 13 May 2018 (UTC)
 * WP:Canvas says to post at the projects involved! Calling them a "partisan audience" is just silly. They have as many diverse opinions as there are here. --RAN (talk) 20:50, 18 May 2018 (UTC)
 * RAN, WP:CANVASS says notifying WP:Wikiprojects here on EnWiki is appropriate. We have had RFCs relating Wikinews, Wikiversity, and others. For example whether we wanted those wikis to appear in local search results, and whether our policy pages direct users to go to those other wikis for various purposes. Those RFCs were not advertised on those other wikis, because it was a purely local EnWiki matter and EnWiki community decision. It would have been seriously inappropriate to canvass Wikinews or other communities trying to swamp the EnWiki RFC to promote external agendas. You do not want to win this argument. A canvassed mob from EnWiki could overwhelm any other community at will. A canvassed EnWiki mob could delete or re-write Wikidata polices any way we please. We could re-write Wikidata policy to require deletion of any unsourced claims, and even deletion of all sourced claims which don't comply with EnWiki WP:RS policy. The fact that Wikidata would cease to exist as an autonomous community would actually help resolve some of the issues with using Wikidata on EnWiki, all content on Wikidata would be subject to EnWiki policies and EnWiki administration. Alsee (talk) 04:18, 20 May 2018 (UTC)
 * Yeah, notifying off-site (even WMF-related) groups who have a vested interest in the outcome is WP:MEATPUPPETRY, a particular form of canvassing.  — SMcCandlish ☏ ¢ 😼  06:48, 9 June 2018 (UTC)
 * Oppose - This appears to be about Rusf10 removing hidden links Q-numbers formatted as <!-Q123456--> to Wikidata from tables that list multiple people that do not currently have an entry in English Wikipedia. The Wikidata entry links to Wikipedia entries in other languages and links to Wiki Commons and Wiki Quote, even if they do not have an English Wikipedia entry. The hidden links will let an editor know that if an article is recreated or a new entry is created for this person, an entry at Wikidata already exists. This will hopefully reduce duplication of Wikidata entries. It also allows Wikipedia to disambiguate people that appear in articles and lists that currently do not have Wikipedia entries. This way a person can know that say "John Smith, Mayor of Yourtown<!-Q123456-->" in an article on Yourtown is the same person as "John Smith, President of BigCompany<!-Q123456-->" that appears in the article on BigCompany. It will allow someone who creates an article in the future to search for hidden text on the string "Q123456" and find both entries and create the properly disambiguated link to the article. Of course only someone actually editing an article will be able to see the hidden link Q-number. --RAN (talk) 02:06, 10 May 2018 (UTC)
 * This will do absolutely nothing to prevent duplicate entries in wikidata for topics that already have articles in wikipedia, so it seems to me to just be an excuse, not a real solution to a problem. If duplicate entries is really a widespread problem in wikidata then why doesn't wikidata come up with its own solution for this that doesn't involve wikipedia?--Rusf10 (talk) 03:38, 10 May 2018 (UTC)
 * Okay, to clarify what I think RAN is talking about: Suppose there is a redlink here. Somebody sees it, creates an article, and then creates a Wikidata entry for the new article. What I think RAN is suggesting is that any hint we can give here is useful, that a Wikidata item already exists, and so if/when a new article is created here, then it should be linked to the existing Wikidata item, rather than have a new one created for it.
 * Wikidata users make quite an effort to try to hunt down and merge duplicates, eg trying to spot potential duplicates that matching birth/death dates, or the same value for an external ID, or apparent duplicates that come up organically in search. But all these are playing catch-up, and are never 100%. It's altogether better if the new article gets linked properly from the outset.
 * Another reason (IMO) may also be worth considering why such references in comments might be useful, namely that if a wikidata item exists, it may have some useful information and references for basic facts like full names, dates, external identifiers, places of activity, birth, death, etc that all may be of use to somebody creating an article. Jheald (talk) 10:54, 10 May 2018 (UTC)
 * Support a ban, or at least strongly discourage them, similar to the language in WP:EXTLINKS. Pburka (talk) 02:38, 10 May 2018 (UTC)
 * Oppose Such links should be allowed to be used where they can provide extra information to readers and editors about the topic. They are not completely external links, they are links within the Wikimedia movement. Thanks. Mike Peel (talk) 12:07, 10 May 2018 (UTC)
 * Support, but with exception for inline inter-language links. I oppose the concept of comments that point to Wikidata, because there is no unambiguous format to determine the exact meaning of such comments, or exactly how the comment would be associated with the text in the article. Such a situation is an invitation for people to write bots that screw things up. Jc3s5h (talk) 12:20, 10 May 2018 (UTC)
 * We should not link to wikidata at all. Inline interlanguage links have always been discouraged in practice (notice how few of them exist). There is no reason to add an exception for Wikidata about them. &mdash; Carl (CBM · talk) 12:40, 10 May 2018 (UTC)
 * Support with exception for interlanguage links per Jc3s5h. Ealdgyth - Talk 13:16, 10 May 2018 (UTC)
 * Support with exception for interlanguage links per Jc3s5h and Ealdgyth. ILLs may be rare due to the fact that the English Wiki is currently standing at 5,646,567 articles, well ahead of most other languages (wp:List of Wikipedias).  (Indeed if you ignore those articles written by Lsjbot, well over double the size of any other Wiki.)  Therefore few articles will appear in another language and not in English, except for small geographic features and locally notable persons.  ILLs are invaluable for setting up a link that can be subsequently translated either full or as guidance.  When I was working on Peter Harlan I used an ILL to get the basis of the article and there are still ILLs for Cornelia Schröder-Auerbach,  Hanning Schröder and Castle Sternberg within it.  It means the reader has at least the possibility of finding the information until someone has the time to create an English version. Martin of Sheffield (talk) 13:40, 10 May 2018 (UTC)
 * Oppose any restriction per my comment in the previous RfC. This an utter baby-with-the-bathwater case, which would disallow links to Wikidata in tables, for example. Andy Mabbett ( Pigsonthewing ); Talk to Andy; Andy's edits 14:35, 10 May 2018 (UTC)
 * Mu I'm all for creating a policy to explain how and what sorts of links are useful. This sort of RFC, which is too restrictive and too ignorant of nuance, is not the way to do it.  -- Jayron 32 14:51, 10 May 2018 (UTC)
 * I cannot choose any one of the four options, although the closest thing would probably be "support with exception" + "allow hidden comments". The status quo appears to be to discourage inline interwiki links in general, except for Wiktionary and Wikisource links and those generated by Interlanguage link. Regardless of whatever concerns there are with Wikidata at this juncture, I think the current Manual of Style guidance should be sufficient, although I would update it to explicitly permit ill links to the Wikidata item. Banning hidden comments based on innocuous material, if the proposer is indeed in support of this, is patently ridiculous and unnecessarily heavy-handed, especially since these are not actually links and readers aren't supposed to see them. I don't think it's necessary to lump them together with real working links. Aside from the issue with hidden comments, I think the RfC should be clarified to indicate that the proposer is, at least according to their own words, in support of the status quo that currently exists. Jc86035&#39;s alternate account (talk) 15:06, 10 May 2018 (UTC)
 * Support—there are far too many issues with WikiData's implementation and with WikiData-folk contemptuously imposing WikiData on articles beyond the control—or even awareness—of the custodians of Wikipedia articles. This shouldn't be re-opened for discussion until it can be clearly demonstrated that all the issues—both technical and behavioural—have been dealt with. Curly "JFC" Turkey 🍁 ¡gobble! 00:32, 11 May 2018 (UTC)
 * Oppose A QID or URL in a comment is a good way to tip about the existence of the article in sister sites. At this stage practices are evolving and improving every day, but banning such info would just kill innovation. Syced (talk) 06:29, 11 May 2018 (UTC)
 * Note: This editor has acknowledged arriving at this RFC via the partisan-audience advertisement at Wikidata. Alsee (talk) 01:33, 13 May 2018 (UTC)
 * Oppose. The only reasonable usage of linking to wikidata (as opposed to pulling data from Wikidata, which the topic starter explicitly excluded from this RfC by saying it has no impact on Authority control), is to indicate next to a redlink that a Wikidata item for this redlink exists. I can not envision a single rational argument ("Wikidata is evil" is not a rational argument) against connecting a redlink on Wikipedia with Wikidata in the case the Wikidata item exists (there are plenty of items on Wikidata which do not have any sitelinks and which would be notable by our standards). Whether it should be a link similar to ill or just a number commented out is debatable, but I am not looking forward for this debate, as this RfC is very badly organized (similarly to the previous one) and is very untimely (similarly to the previous one).--Ymblanter (talk) 07:01, 11 May 2018 (UTC)
 * Support- with the possible exception of interlanguage links. From what I've seen of WikiData, its content is confusing, often mostly empty, and frequently erroneous. As Curly points out, it feels lioke this junk is being inflicted on Wikipedia with minimal oversight. I'd put a moratorium on the use of WikiData until we can be satisfied that we're not just rubbishing our standards of accuracy. <b style="color: Maroon;">Reyk</b> <b style="color: Blue;">YO!</b> 07:08, 11 May 2018 (UTC)
 * Support until such time as Wikidata develops a better reputation for fact-checking, referencing, and accuracy, especially for details such as citizenship of living people (often listed, rarely sourced). —David Eppstein (talk) 07:24, 11 May 2018 (UTC)
 * Support - not a community based here.--Moxy (talk) 11:56, 11 May 2018 (UTC)
 * Oppose Banning comments is excessive, and doesn't seem to have had any justification given. Limited use of ill-style links in tabular material and lists could also be useful. Jheald (talk) 18:39, 11 May 2018 (UTC)
 * Support. Wikidata links are an inappropriate destination, except perhaps in the Wikidata article or other articles actually discussing Wikidata. In rare cases I could see a valid purpose for a hidden comment mentioning Wikidata. However hidden links are inappropriate without some unusual need in the specific case. Links to foreign language articles are generally a bad idea for a number of reasons, but sending a reader to Wikidata for interlanguage links is even worse. Alsee (talk) 02:56, 13 May 2018 (UTC)
 * Support. Sending readers to Wikidata is very rarely helpful, and if an editor believes that more information about a redlink or an unlinked term / name is needed, it would be better if they added a reliable source as a reference to it. The same applies to the vast majority of regular interlanguage links in our articles. Fram (talk) 13:33, 17 May 2018 (UTC)
 * Support., I'm not sure what "with exception for interlanguage links" has to do with the question "Should we ban links to wikidata within the body of an article?" SarahSV (talk) 14:13, 17 May 2018 (UTC)
 * SarahSV I believe wikidata interlanguage links refers to replacing a redlink Jokery with Jokery, which sends the user to the bottom of a Wikidata page. In my opinion the typical reader will WTF when they see the link, and they'll be confused as hell if they click on it. Alsee (talk) 09:26, 18 May 2018 (UTC)
 * That's really confusing. I was thinking more along the lines of Olena Chaplynska. That could possibly have a use, but in my opinion, neither should be allowed. I just wanted to offer it as an option since some people had expressed support for these types of links in the past.--Rusf10 (talk) 14:24, 18 May 2018 (UTC)
 * , that's what I thought. It might be worth striking through that option, because those links have nothing to do with Wikidata that I know of, so it introduces a confusing tangent. SarahSV (talk) 16:08, 18 May 2018 (UTC)
 * Someone can correct me if I'm wrong, but I was under the impression that the ill links work by pulling information for the wikidata database.--Rusf10 (talk) 16:19, 18 May 2018 (UTC)
 * , you could be right, in which case it's a good idea to offer it as an option. SarahSV (talk) 17:21, 18 May 2018 (UTC)
 * Support. Disruptive without sufficient utility for almost all readers. Who actually uses Wikidata? My guess is a special type of reader. I have no objection if Wikidata links are added where they're easy to find and unobtrusive—in the "See also" section at the bottom, or some such. <b style="color:darkgreen">Tony</b> (talk)  14:23, 17 May 2018 (UTC)
 * Support with the two exceptions. My reasoning is basically the same as that of David Eppstein who put it more succinctly than I would have.  At some point, we can work-in an exception for WD material that is sourced to en.wp standards, when WD provides a means for us to be certain of this.  WD-provided information would be useful for certain things, especially tabular data.  But we're just not there yet.   project's core content policies are way more important that link-making convenience or data-provision centralization.  — SMcCandlish ☏ ¢ 😼  10:04, 18 May 2018 (UTC)
 * Here's the problem I have with the ILL template. It can be used to directly link to the wikidata entry rather than the different language articles. For example how it is being used here Take Paul Kiernan for example. He doesn't have any article on English wikipedia (It was deleted) and I'm near 100% sure no one is even going to attempt to create an article about him in another language, so why is an ILL being used here?--Rusf10 (talk) 04:12, 20 May 2018 (UTC)
 * Given what looks like an emerging consensus to not dump our readers into the middle of a WD page as if it's an article, I would expect that ILL would be changed to no longer do that, or to not do it when used in mainspace, or to put a red warning if done in mainspace (to permit the possibility in some circumstance we haven't accounted for, but which is rare), etc. I wouldn't dwell on this particular detail here and now.  — SMcCandlish ☏ ¢ 😼  12:56, 20 May 2018 (UTC)

*Support. <b style="color:darkgreen">Tony</b> (talk)  06:25, 4 June 2018 (UTC) [Sorry, mistakenly posted support twice. <b style="color:darkgreen">Tony</b> (talk)  03:34, 5 June 2018 (UTC)
 * Support with the two exceptions. Wikidata links can be useful external links, when used with consensus, as in the Taxonbar template), but direct links to Wikidata are not appropriate in the body of an article any more than a link to any other external database would be. Peter coxhead (talk) 05:58, 19 May 2018 (UTC)
 * Support Wikidata links should not be allowed in either the Lead or the Body of the article. I'm agnostic on links in infoboxes, external links, etc. LK (talk) 06:53, 20 May 2018 (UTC)
 * Oppose. I definitely support inline inter-language links and hidden-text Q numbers. That said, I support removing wikidata links from non-notable subjects where the sole purpose of the link is disambiguation. I'm not sure where the guideline is on this, but I believe inter-language Wikipedia links should always be required to meet WP:N. If there's debate, I expect the person arguing for the link to begin a draft on the subject. However, I think this blanket restriction on Wikidata links is too broad. Daask (talk) 20:27, 29 May 2018 (UTC)
 * Support with two exceptions - per SMcCandlish. Furthermore, Endorse SMcCandlish on not letting the ILL template dump a reader onto wikidata from mainspace easily. Tazerdadog (talk) 01:49, 1 June 2018 (UTC)
 * Oppose. They're not often going to be useful but as exceptions to that are possible it doesn't make sense to ban it. For the same reasons we don't ban links to the Esperanto Wikipedia or the Daily Mail - just because they are not often helpful doesn't mean they never are. Thryduulf (talk) 09:28, 3 June 2018 (UTC)
 * Support, with possible exceptions by specific consensus after verifying the specific Wikidata entries. Links are almost always confusing to readers.  Invisible comments are only helpful to editors if it is probable that Wikidata does not have multiple entities conflated with the same index and multiple indicies covering the same entity, which is, at best, not proven.  — Arthur Rubin  (talk) 05:35, 4 June 2018 (UTC)
 * Support I have just seen a horrendous example of circularity caused by this. Wikidata simply does not have the controls necessary to make it a worthwhile addition and it has the potential of allowing people to game en-WP's controls. - Sitush (talk) 13:44, 4 June 2018 (UTC)
 * Support ban, per others, and per my essay about the godawfulness of Wikidata for the accuracy of Wikipedia's articles. Outriggr (talk) 02:47, 6 June 2018 (UTC)
 * Oppose – I've placed several-to-many inter-language links and find them helpful. I have no opinion on the other usages. However, the proposal makes no distinction, although several supporters of the ban do. Dhtwiki (talk) 19:03, 6 June 2018 (UTC)

Overlaps with another RFC

 * Please note - This RFC overlaps somewhat with another that is still ongoing (see Wikidata/2018 Infobox RfC). I do not believe that there is any intentional forum shopping involved... but we do need people to know that similar questions are being discussed elsewhere. Blueboar (talk) 15:01, 10 May 2018 (UTC)
 * Thank for letting me know about this, I will add a statement above to clarify the proposal will not apply to infoboxes since that is being decided elsewhere.--Rusf10 (talk) 16:07, 10 May 2018 (UTC)
 * Fair enough. However, please note that the other RFC has grown beyond just discussing infoboxes.  It may be better to put this discussion “on hold”... Until we see how the other closes. Blueboar (talk) 16:36, 10 May 2018 (UTC)
 * Disagree strongly. RfC is straightforward and already looking like a WP:SNOWBALL.  That other RfC is a sprawling mess of 1A, 3C, etc. options, from which obviously no consensus is going to emerge, other than possibly the one that points in the same direction  RfC is going.  Virtually every single answer there conflicts with ever other answer, except that multiple respondents are arriving at the most-restrictive option (1A+2A+3A+4A). It's a textbook example of why to not structure RfCs that way.  Ask  question, then do another RfC to ask another question. Also, as I commented over there, the excessively geeky structure and wording of that RfC basically makes it invalid: it's heavily skewed toward the input of IT professionals (few who are not in that camp will be able to parse it), and they have a strong bias in favor of data centralization and automation.  — SMcCandlish ☏ ¢ 😼  10:27, 18 May 2018 (UTC)
 * I do not see it is straightforward, since different users are clearly addressing different issues, and the RfC question has been amended already during the RfC. I opened a proposal below to close it as invalid.--Ymblanter (talk) 20:19, 18 May 2018 (UTC)
 * That's not true! Since the day the RFC opened the question has been "Should wikidata be linked to in the body of the article?" as it is now. Stop trying to mislead people, just so you can shut down debate and get your way.--Rusf10 (talk) 20:30, 18 May 2018 (UTC)
 * No closer would shut this down as "invalid", because the course emerging is clear, as is the question, and that course matches the one at the other RfC (see the analysis I posted at bottom over there, to counter some similar snow-jobbing that was going on). The two discussions are in close synchrony. And whether some commenters choose to raise additional related issues that occur to them has nothing to do with the validity of an RfC; show me any RfC where this doesn't happen. What this all really comes down to: We all want WikiData to work, but the WD editors and their promoters on en.WP (to the extent they're not the exact same people, which may be 0%) have to do the work on the WD side to enable en.WP to filter WD data for en.WP policy compliance (and so on for other sites), or we simply can't use it, any more than we'd copy-paste content from any other website just because it was open-licensed, without also verifying the content and being able to control is appearance here.  We'd never inline anything from another site where random people can change it and thereby instantly change what appears on Wikipedia, unless we can some way to control, undo, be alerted, etc.  Even then it's a really, really iffy idea. The fact that WD in particular has received some WMF money doesn't change that. They fund all kinds of things that aren't pipelined directly through en.WP into readers eyes and brains.  — SMcCandlish ☏ ¢ 😼  23:28, 18 May 2018 (UTC)
 * SMcCandlish, what you write demonstrates very clearly that the two of us, to start with, understand the question of this RfC very differently. For me, it has nothing to do with the reliability of Wikidata (whereas another one does). The RfC does not define what "links" mean. It does not specify what is its scope - are templates which are not infoboxes included? Are hidden comments included? Nobody directly links to Wikidata now in the articles (with the exception I guess the article Wikidata). It is pretty clear from the comments of the !voters that they understand the scope differently. The RfC was not properly prepared. And the RfC with an unclear scope must be, well, closed as invalid.--Ymblanter (talk) 05:32, 19 May 2018 (UTC)
 * None of that is a problem we're unfamiliar with or incapable of dealing with. Many RfCs involve later detail clarification and hashing-out. RfCs are not legalistic or robotic processes; they are calls for discussion. One discussion leads to another. We do not try to shut down discussions, unless they are disruptive for some reason. The more detailed RfC covers, well, the details.  This more general RfC takes an overall pulse, and it's beating with the same heart as the leading cluster of responses to the more detailed RfC. This one demonstrates (in being neither dominated by WD boosters nor mired in complex details only understood by entrenched WD boosters and WD critics) that the consensus emerging at that one (despite the cluster of WD fans gathered there) isn't false. Next, when different respondents have differing but compatible and rational reasons for arriving at the same conclusion, this makes the conclusion stronger, not weaker. The fact that one person cares more about data verifiability (over time, not just once), while another cares about editorial complexity and confusion, and another about something else, doesn't invalidate anything at all. Any proposal can raise multiple concerns. If this RfC isn't limited to infoboxes, then it isn't.  It's also clearly about pulling data directly from WD; so, no, it's not about HTML comments.  We might end up not needing those, depending on how and if WD integration into en.WP proceeds, and how WD evolves to deal with the core policy problems being raised at multiple other sites.  But for now, I've agreed with you that trying to expunge Q numbers in HTML comments is overkill and even a net negative.  — SMcCandlish ☏ ¢ 😼  12:47, 20 May 2018 (UTC)

Proposal to close
Since the RfC so badly formulated that the participants do not really understand what is exactly asked, and one week after it was open new proposals appear (which are not reflected in the past votes), and the proposer says that they are thinking about adding new options, I propose to close this RfC as invalid. Any user in good standing can open a new one, formulating the options clearly and not changing them as the RfC runs its course. I would have also suggested to topic-ban Rusf10 from opening new RfCs about Wikidata, since the previous one was a disaster and this one is going to be a disaster, but this is clearly not an appropriate forum for such a proposal.--Ymblanter (talk) 20:17, 18 May 2018 (UTC)
 * Please strike your comment. You are making false statements. I have not changed any of the RFC options since the day the RFC opened. The only thing I changed on the second day was to add a note clarifying that the proposal would not apply to infoboxes since that is being determined elsewhere (and if you want to see a really bad RFC, take a look at that one). Also, where did I say I was "thinking about adding new options"? because I have not. The suggestion of a topic ban is uncalled for as I've done nothing wrong here. If you really want to pursue it though, I dare you. Wait until you see how quickly that will get shot down. The only reason the past RFC was a disaster is because your friend RAN worded the RFC options in a way to make the proposal more extreme so it would not pass. You obviously just want to shut down debate because the RFC is not going your way.--Rusf10 (talk) 20:27, 18 May 2018 (UTC)
 * . The rest of your comment are baseless personal attacks. RAN is not "my friend", it is still not clear whether the proposal covers for example commonscat and other similar cases (and it is too late to clarify ot now), and I am not going to strike anything. It is up to administrators to listen or to not listen to my opinion in this section.--Ymblanter (talk) 20:41, 18 May 2018 (UTC)
 * People appear to be confusing a clickable link with a hidden annotation. There is no clickable link that Rusf10 is removing, he is removing hidden Wikidata Q-id annotations such as . They are used to properly disambiguate people that do not have Wikipedia articles, but have a Wikidata entry with more information on them. The annotation is only visible to someone editing the article. They let a future editor know that the person in the table of "Mayors of X" is the same guy appearing in the article on "X Township" and the article on "X Cemetery" and that the person has a photo in Wikimedia Commons. It lets a future editor know that the James Smith in one article is the same as the Jimmy Smith in another article and same person as the James Smith named in a quote in another article. People also seem to be confused about the !vote, it is not a binary support/oppose !vote. They are writing "support" without choosing one of the five mutually exclusive options, it is not clear what they are supporting. --RAN (talk) 20:46, 18 May 2018 (UTC)
 * Interpersonal venting aside, yes, the HTML-comment annotations should not be deleted since they're harmless, serve a useful function, don't cloud the code very much, and are invisible to readers. It would probably be preferable if there were another way to do it. Maybe the system being worked on to shunt CSS code for pages, and various metadata for templates, into special subpages could also be adapted to this purpose.  I'm not really clear on the details of that work, and haven't looked into it all in months, so someone else should who understands it better can probably chime in about whether that's feasible.  — SMcCandlish ☏ ¢ 😼  23:31, 18 May 2018 (UTC)
 * How does change anything? my comment there is consistent with my original position that I support banning all wikidata links within the body of an article (including ILL). The rest of your comment are baseless personal attacks. Actually, it is a response to your personal attack. RAN is not "my friend" Good, at least we have something in common. it is still not clear whether the proposal covers for example commonscat and other similar cases (and it is too late to clarify ot now) It does not apply, the RFC is already clear that it applies only to the body of the article, of which categories are not a part of. and I am not going to strike anything. It is up to administrators to listen or to not listen to my opinion in this section. You are entitled to your own opinion, but if you are going to continue to make up facts (ie. the question has been changed or that I am thinking of changing the options), I will call you out on it.--Rusf10 (talk) 00:49, 19 May 2018 (UTC)
 * Call me out on what? On that you have opened a second RfC with an unclear scope? Is it exclusively about ill? Then it should have been in the RfC question, and it is not. If it is about anythong else, it should have been in the question. Nobody is linking the Wikidata from the body of the article directly. You opened another "Wikidata vs anti-Wikidata" shitstorm, and the result of the storm will be nothing because you could not even define the question properly.--Ymblanter (talk) 05:36, 19 May 2018 (UTC)
 * The RFC is crystal clear, it is about linking to wikidata in the body of the article. RFC questions are supposed to be short and simple, not complex. (read WP:RFC if you don't believe me)"Nobody is linking the Wikidata from the body of the article directly." You could not be more wrong! Go back and read the first RFC, that is what caused this issue to begin with. RAN was adding direct links to wikidata in the body of articles and insisting that he could do so because there was no rule specifically banning him from doing so. The reason the last RFC didn't work was RAN (not me) worded the position as "never link to wikidata" in hopes of getting more opposition and keeping the status quo (ie. there is no rule, so he can do whatever he wants). Now you're trying to paint this RFC as flawed, so debate can be shut down and nothing changes. Your obstructionist behavior, is not helping your cause. In both this RFC and the previous one, it has been clear that the consensus is wikidata has problems and its use must be limited. The only question is how exactly do we want to limit it? Its clear something need to be changed, so do you want to be part of the problem or the solution? I took the position that at least in the body of the article wikidata shouldn't be used at all (at least for now). If in the future, some major improvements are made to the reliability of wikidata, then we can revisit the best way to use it within articles. But if there are any really good uses of wikidata within the body of the article I'd like to hear about them. Although, I am not changing my vote as of now, I could certainly live with 's proposal. --Rusf10 (talk) 06:38, 19 May 2018 (UTC)
 * Again, the example you have given is linking to Wikidata next to a redlink which can not be a valid article. Red links which can not become valid articles are not allowed. Period. We do not need an RfC to establish this. Concerning possible Wikidata links next to valid redlinks, this has whatsoever no relation to reliability of Wikidata, because the function of such a link (which is next to a redlink) is not to provide information, but to facilitate future linking. If a Wikidata has an item about X, it stays forever an item about X, even if it gets vandalized or sourced to unreliable sources. If someone links to Wikidata from the body of the articles (not in templates), and these links are unrelated to Wikipedia redlinks, I would like to see an example. Instead, we have the whole rant again "Wikidata is not reliable, OMG". Just because of the way you formulated the question and because you did not care to discuss it with anybody before running it live. This is why we have supports which are actually opposes, and opposes which are actually supports.--Ymblanter (talk) 06:53, 19 May 2018 (UTC)
 * And please stop telling me such as "your cause" and "your case". My cause is to improve Wikimedia projects, including the English Wikipedia. I have been doing it for years, and I am currently one of 500 most active editors here of all times. If you believe I have a double agenda pls go to ANI, but stop saying it here.--Ymblanter (talk) 06:56, 19 May 2018 (UTC)
 * (1) I don't think there's any serious problem in relation to the other RFC. During the drafting of the other RFC, there was a deliberate decision to focus on infoboxes. This RFC focuses on the body of the article. There are wide-ranging discussions and arguments spilling over to both areas, but I don't see any inherent-or-likely conflict in allowing the RFCs to proceed in parallel.
 * (2) Concerns have also been raised about the formulation, scope, or intent of this RFC. I don't think it would be productive or appropriate to invalidate and restart the RFC. We've got substantial and productive examination of the issues invested from many people, and I believe participants have a reasonable understanding of at least the generalized topic. Either the !votes and discussion will be sufficient for the closer to sort out the issues, or the closer may may be able to provide a partial result and/or guidance on exactly what unresolved point(s) we need to focus on in any new RFC. Alsee (talk) 18:40, 20 May 2018 (UTC)


 * Note to closer If this is closed with no clear consensus, please restrict when it can be brought to RFC again. We really do not need to go through this every two months. It consumes a huge amount of time. The issue is complex, involving half a dozen permutations. The sister RFC on WIkidata and Infoboxes has over a dozen permutations. --RAN (talk) 20:17, 20 May 2018 (UTC)
 * unfortunately, I think this is going to need further RFCs... we are going to have to explore each permutation separately (rather than all at once)... so we can better determine consensus on which permutations the community approves of, and which it does not. Blueboar (talk) 20:33, 20 May 2018 (UTC)
 * Restrict future RFCs so you can keep gaming the system, I think not. I'd actually be willing to support the ILL exception if the use of template wasn't being abused by yourself to do something it never was intended to do (that is, be used for topics that don't have an article in any language). If we don't deal with this, you're going to make hundreds of other pages into a complete mess, just like Mayor of Long Branch, New Jersey.--Rusf10 (talk) 23:30, 20 May 2018 (UTC)
 * Is that what all this fuss is about? You wanting to remove links to Wikidata in a table that you have not contributed to, and have no interest in reading. It is kinda silly overkill. You can always just not look at what I am editing, have you tried that? --RAN (talk) 01:27, 21 May 2018 (UTC)
 * So what is the intended audience for that article? yourself? Articles should be easy to read for the average person, not contain complex tables scattered with links to another website that is even more confusing. Wikipedia is an encyclopedia, not an extensive database for every person who has ever lived. If that what you want to do over at wikidata, by all means, I have no opinion on what goes on there, but I think I speak for most people on wikipedia when I say, I do not want that massive unreliable database spilling into the content here. Reliability issues aside, the fundamental question is does anyone want to see wikipedia get changed from an encyclopedia to a database full of every trivial bit of information that can be found.--Rusf10 (talk) 01:44, 21 May 2018 (UTC)
 * "a table that you have not contributed to" is illegitimate reasoning here, Richard. See WP:OWN and WP:ENC.  Everyone is here to work on content (and its presentation, categorization, policy compliance, and all other facets). It is never, ever required that one has to have previously been an editor at a page before one can have anything to do with its current and future direction. Otherwise WP would have no articles, because no one would have any standing to every write any in the first place.  But this isn't about any particular articles anyway, it's about whether en.WP policies will be respected and enforceable on en.WP or whether WD editors can ignore them with impunity and inject their unvetted content into this site.
 * Or you can stop stalking my edits, and get the same effect. There are 5,650,219 articles in the English Wikipedia you still have not nominated for deletion. By concentrating on one article, you are neglecting all the other articles that can be deleted. Use better time management and maximize you deletions stats. --RAN (talk) 03:25, 21 May 2018 (UTC)
 * You really don't want to go down that road, just think about the last ANI you opened, do I need to keep going? Back on topic, you still haven't explained the value of using the ILL template for articles that do not exist in another language.--Rusf10 (talk) 04:23, 21 May 2018 (UTC)
 * It is irrelevant whether articles exist in another language or not. They may exist and be not notable for our standards, or they may not exist and be notable. What is important here is notability.--Ymblanter (talk) 07:16, 21 May 2018 (UTC)
 * I tend to support the moratorium idea (and have no idea where the suggester of it, Blueboar, stands with regard to which issues raised). This is tedious rehash, and the next round will be, too.  — SMcCandlish ☏ ¢ 😼  23:42, 24 May 2018 (UTC)

Modified Proposal
In an effort to make the RFC come to a clear consensus, I'd like to purpose the following: Wikidata may not be linked to within the WP:BODY of an article with the exception of inline inter-language links (WP:ILL. Inline inter-language links may only be used when an article does not currently exist in en.wikipedia AND an article does exist in at least one other language. The ILL template will be modified to remove the Wikidata table of languages (ex. Jokery) & Reasonator functions (ex. Jokery ))--Rusf10 (talk) 06:25, 24 May 2018 (UTC)

Note: This still has no effect on infoboxes and would not impact other links that are not part of the body such as authority control templates, links on the sidebar, etc.

Survey on Modified Proposal
Support- I'm proposing this as a compromise to gain greater support. Although many have supported the complete ban of wikidata links, a sizable number had indicated they would support the ban if ILL were exempt. However, in order for me to accept ILL links there would have to be some restrictions on them to prevent pages like Mayor of Long Branch, New Jersey where the ILL is being used to link directly to wikidata even though no article exists in any other language and likely never will. I believe that it would not make sense to direct a reader to another language article if an one in English exists (after all this is an English encyclopedia and if they really wanted to find the article in another language all they would have to do is click the link and then look at the side bar). It only makes sense to me to link to another language if we currently do not offer an article about the subject, but another encyclopedia does. Furthermore, it seems most of us are in agreement that we do not want to "dump" the user into the middle of a wikidata page, so they why I proposing the phase-out of the table of languages and resonator links (I doubt many pages are using that function now anyway). I also dropped the ban on wikidata in hidden text from the proposal, although I still do question the wisdom of cluttering the editing screen with extra text that 99% of editors will find useless.--Rusf10 (talk) 06:25, 24 May 2018 (UTC)

What does everyone else think? --Rusf10 (talk) 06:25, 24 May 2018 (UTC)
 * I'm not a fan of any of the links being discussed. Even for interlanguage links to an existing article somwhere, I have concerns about clutter, few readers being able to read them, few readers understanding what the links are unless they blindly click on them, and the open door for promotional or policy-subverting ILLs to non-notable or otherwise problematical cases. If an article or redlinks or red-template-links are being deleted here, we don't want that user trying to manufacture an appearance of legitimacy with ILLs to an unpatrolled microwiki. Alsee (talk) 07:26, 24 May 2018 (UTC)
 * I agree with you, ILLs are a mess and ideally I'd like them banned but I'd prefer this compromise over keeping things the way they are. A majority of people above support restrictions on wikidata links, but what to do with ILLs is what no one seems to agree on.--Rusf10 (talk) 07:31, 24 May 2018 (UTC)


 * I tend to agree with Alsee. It's not actually helpful to our readers in the aggregate (only to some individual readers by the random accident of what other language they're fluent in) to put something like "albondigas" in an English-language article.  Driving them sideways to a WD page full of raw data that isn't subject to our (or any other Wikipedia's) verifiability policy seems even worse.  If it came down to a choice between limiting the WD restrictions to just ILL and a few other exemptions, or having no restriction on WD's use at all at en.WP, I'd side with the former. But I don't think that's where this heading.  The strongest showing for any option, at both RfCs, is in favor of not using WD here until WD has a way to ensure compliance with our policies for material that would be shoehorned into this site from that one.  — SMcCandlish ☏ ¢ 😼  23:50, 24 May 2018 (UTC)

Request to end discretionary sanctions that pertain to MoS
Please see Arbitration/Requests/Clarification and Amendment.

Multiple arbitrators have requested additional input from regular editors here about whether the WP:ARBATC should be lifted from this and related pages. — SMcCandlish ☏ ¢ 😼  13:44, 23 June 2018 (UTC)
 * Well, one anyway :)   —SerialNumber54129  paranoia / cheap sh*t room 08:16, 24 June 2018 (UTC)
 * BU Rob13's opening statement, followed by Newyorkbrad's.  — SMcCandlish ☏ ¢ 😼  11:57, 24 June 2018 (UTC)

Date ranges vs. full birth–death dates in biographical leads
Please see Wikipedia talk:Manual of Style/Biography — SMcCandlish ☏ ¢ 😼  13:39, 25 June 2018 (UTC)

Splitting Infinitives?
I just noticed an editor going through and 'fixing' split infinitives on multiple articles, but I can't find any reference to such an issue in the MOS. Is there a consensus on the topic? Just wondering... WesT (talk) 22:58, 25 June 2018 (UTC) — Preceding unsigned comment added by SMcCandlish (talk • contribs) 21:25, 26 June 2018 (UTC)
 * WP:SISTERMARYCATHERINE. <b style="color: red;">E</b><b style="color: blue;">Eng</b> 00:00, 26 June 2018 (UTC)
 * To WP:BOLDly split infinitives that no man had split before paraphrasing Douglas Adams, who himself paraphrased Gene Roddenberry. -- Red rose64 &#x1f339; (talk) 13:26, 26 June 2018 (UTC)
 * A more serious response is WP:RETAIN. I personally feel that split infinitives should generally be avoided, but also there are times when it seems justifiable.  As such, I think it's not really fodder for an MoS to issue definitive guidance on the writing style.   Sławomir Biały  (talk) 15:37, 26 June 2018 (UTC)
 * Yeah, and the first rule of MoS: rewrite to avoid conflict; there are few such constructions that can't be reworded in other ways, if it comes down to some kind of nasty fight about it at any given page (which would be WP:LAME). I would let it alone, except where the tweaks by this "clean-up artist" produce awkward, stilted results. While all linguists and most modern style guides agree that a "rule" to not split infinitives (or terminate sentences with prepositions) is prescriptive nonsense made up by a handful of Victorian pundits, most of them also agree that the punditry has actually been influential on perception of what's best in formal writing. This view has slacked a bit in the last 25 years or so, toward a preference for doing whatever reads best in the circumstance at hand; while generally leaning away from either informal practice in formal writing, it's fine to veer happily back to it if the result of the more prescriptive style would sound pretentious ("It is something up with which we should not put.") If MoS ever advised anything on this, it should be long these lines: "Split infinitives and sentences ending with prepositions should be avoided by default, but used any time the alternative is confusing or stilted.  The somewhat formal tone of encyclopedic writing is neither obtuse nor pompous." And, yes, that's a little joke. .  Maybe with a footnote that it's not "bad grammar", but rather a matter of register (sociolinguistics).  But I don't know whether this comes up enough we need an MoS line item about it.
 * I see has stopped signing his posts since they're instantly recognizable as his any day of the week. <b style="color: red;">E</b><b style="color: blue;">Eng</b> 21:30, 26 June 2018 (UTC)

Implementing results of RfC on games/sports over-capitalization
Please see Wikipedia talk:Manual of Style/Capital letters.

Gist: The RfC at WP:GAMECAPS produced a clear result, but nothing was implemented. So I implemented a new MOS:SPORTCAPS section; a merger of the sports/games stuff, and the identical dance-related stuff from another MOS:CAPS section. — SMcCandlish ☏ ¢ 😼  06:23, 27 June 2018 (UTC)

Consolidation of MOS:BIO
WT:Manual of Style/Biography – a bullet list of recent merge and cleanup activity (one major to-do item remains). — SMcCandlish ☏ ¢ 😼  21:08, 26 June 2018 (UTC)
 * There's been a minor flare-up about this at Wikipedia talk:Manual of Style/Lead section; it seem to mostly be predicated on the idea that there wasn't discussion/consensus for the merge, rather than any particular content-related objections; but there actually a consensus discussion.  — SMcCandlish ☏ ¢ 😼  06:25, 27 June 2018 (UTC)

Expanded use of code syntax highlighting
Ever since the introduction of syntaxhighlight (and templates that use it, like and ), we've been having the problem that people are trying to expand its use, not just to mark up blocks of code (what it's actually for) but every single inline mention of a code fragment. This result is strange "outbursts" of color in mid-sentence, and which I think are apt to be confusing, because WP uses color in prose for a very limited number of pre-determined things, like indicating a link and whether it goes to a real article. It's even producing oddly conflicting code markup in the same sentence (because the highlighter only recognizes and colorizes some kinds of code). Example: "Lists with are   elements ...". The syntax highlighter is also buggy and sometimes produces misleading output.

When I've tried to address this, I get responses like "I am not aware of any policy, guideline, or essay that discourages such syntax highlighting usage", as if the fact that all of MoS is against all extraneous over-stylization weren't enough. The state of articles like HTML element (from which the above example comes) strongly suggest that lack of an MoS item about this actually is a gap we need to fill, perhaps at MOS:COLOR.

I think we should advise to not use syntaxhighlight except: It should not be used an alternative to <code ></code> in simple cases like "the  element".
 * in a separate block of code;
 * or in an lengthy inline code example, if the highlighting actually helps distinguish between multiple discrete items within the code;
 * but in neither case without checking that the output is accurate not misleading due to syntax highlighter bugs.

— SMcCandlish ☏ ¢ 😼  12:51, 25 June 2018 (UTC); revised 17:38, 29 June 2018 (UTC)


 * Most of those advisings seem reasonable (there's a MOS for comp sci/computing lying around--advise to put it there rather than in accessibility land). However, I think the third bullet might reasonably be tempered, since "inaccurate because the colors don't render" vice "inaccurate because the colors render wrongly" are slightly different issues--the former is fine because it just inherits the <code ></code> CSS; the latter is still questionably fine because the idea is to separate elements, not necessary for all elements to be styled consistently. --Izno (talk) 13:23, 25 June 2018 (UTC)
 * Yeah, I notified WT:MOSCS and WT:MOSCOMP of this discussion (though WP:MOSCOMP was deprecated and slated for partial merge into WP:MOSCS in an RfC about a year ago; no one's gotten around to it yet). I see what you mean on the precision point, and we could wordsmith it to be more detailed if necessary.  What got me onto that point was observing that it does not correctly parse things like a CSS value of  ; it mistakes this for a "-0" (which isn't a real thing) in one color, followed by a ".5em" which it highlights as an alphanum input in another color. Just pretty ucked fup.  I've filed Phabricator bug report T198095 about it.  — SMcCandlish ☏ ¢ 😼  03:59, 26 June 2018 (UTC)

— SMcCandlish ☏ ¢ 😼  03:59, 26 June 2018 (UTC)
 * The example provided is to HTML element. But it seems to me that the color and font of the tags appearing inline should match both the color and font of the tags as they appear in the separate blocks of code.  If we are to recommend something here, perhaps it should be to use syntax highlighting sparingly, even in separate code blocks.  Otherwise, parts of HTML element would be styled one way and other parts another, which I think would detract from its readability.  In any case, I think consistency is the most important thing, not specifically use of color in this context.   Sławomir Biały  (talk) 13:34, 25 June 2018 (UTC)
 * The of syntax highlighting is distinguishing this particular code item from the next (different) kind of code item right next to it, in a block of code. It is not for "establishing" in the reader's mind that, for example, an HTML element is green, and that an HTML attribute is orange (or whatever). The coloration a) serves no purpose in running text, and b) badly interferes with our use of color in running text for very specific and sharply limited purposes – some of which are going to  with colors chosen by the highlighter, such as blue and red.  This is remarkably similar to the MOS:ICONS stuff.  We permit flags and other icons for some specific purposes in specific contexts, but the ca. 2006 "do whatever" approach we had, before that guideline existed (I would know; I wrote most of its key provisions  :-), resulted in WP being festooned with pointless color-spots all over the place, and that's precisely what's happening with . A new version of an old problem. I covered this stuff in considerably more detail at User talk:Nøkkenbuer. A key bit: any time one is trying to impose a "consistency" with style, there's likely to be a conflict with another consistency. WP has very long-established and important consistencies in our encyclopedic prose, and when a tangential new consistency that's a trivial, largely decorative add-on collides with it, the latter loses.  All that said, I'm not totally opposed to the idea that we shouldn't use syntax highlighting in mainspace at all, but as a coder I find it actually helpful (when it's not bugged – see above) in actual code blocks. I seems a throw-the-baby-out-with-the-bathwater solution to discourage or eliminate it even in block, just to avoid the problem of inline, not block, syntax highlighting making a mess of things.  It's much simpler to just advise against inline highlighting except of complex code examples. Even then, we could actually advise instead to move them into discrete blocks, and "ban" syntaxhighlight inline, completely. I'm trying to be agnostic on that kind of stuff. Just want to deal with the "The purpose of the  element is ..." over-stylization problem.
 * I think you miss my point. The article you pointed to should be internally consistent.  In that specific article, it would be needlessly confusing to style things one way if they appear inline, and a different way if they appear in a code block.  In fact, I don't think the way things are currently styled is a big issue there that warrants separate identification in the MoS, especially if that's the only article suffering from this alleged problem.  It seems to me like a reasonable stylistic choice.  Sławomir Biały  (talk) 11:17, 26 June 2018 (UTC)
 * I'm not even slightly missing your point. The syntax highlighting  has nothing whatsoever to do with how to format a single word of code in a running sentence.  By way of direct analogy, the formatting of an interlinear gloss is completely different from that of an inline one (as in Spanish perro, 'dog'); the single quotes are standard linguistic markup style in prose, but never used for the exact same gloss in interlinear format – including on the same page. Similarly, our typical format in a list is [bullet or number] [Capital letter]more text ... [no terminal puncutation unless it's a full sentence], and we use this same format (sans the bullet or numeral) for headings, table headers, image captions, infobox entries, etc., etc.  This format is not used in running prose, which we write in proper sentences not fragments. Another example: In a reference citation, the bibliographic information is presented in a specific order, punctuation style, etc. (which varies by citation style, sometimes radically). The citations form discrete blocks of content, exactly like a code block, or a list, or a table, or an interlinear gloss, but we would never in a million years write in a running sentence, "The next year,, was released, to mostly positive reviews". More to the general point, we have many kinds of consistencies to deal with, and some of them are directly conflicting, and some of them are  to particular contexts. The important consistency wins over the decorative one, especially when the latter is intended for a very narrow context (blocks of code).  — SMcCandlish ☏ ¢ 😼  21:28, 26 June 2018 (UTC)
 * All I'm saying is that the code inline should look the same as the code in code blocks at HTML element. If that's compatible with your point of view, great!  Even better, if you have some other articles to look at for style issues, you can post them here for community input.  But with a sample of one article, I don't see that this is a widespread problem.  Have you tried resolving this at Talk:HTML element?   Sławomir Biały  (talk) 23:35, 26 June 2018 (UTC)
 * All you're saying is you did not absorb a single thing in this thread, all of which directly refutes the idea that inline code should look the same as the code in code blocks (aside from, I would grant, that a long, multi-part example of complex code inline should have syntax highlighting ... but also should not be inline and should be put in a code block). Re: Talk:HTML element – that's where the discussion started, but it is not about that article, it's about a particular editor's desire to wrap every example of inline code in syntax highlighting markup site-wide, so we are at the correct venue now.  — SMcCandlish ☏ ¢ 😼  17:43, 29 June 2018 (UTC)
 * For the record, discussion of this topic has been occurring at my talk page (permanent link) and at the HTML element talk page (permanent link). My rationale and perspective are fully detailed in a series of lengthy replies therein, including responses to the above claims. At this point, explaining any further would amount to repetition, so I will refrain unless clarification is requested. Additionally, whatever decision occurs here will likely have implications for other articles and documentation whose syntax is similarly highlighted, such as HTML (permanent link) and Template:Quote/doc (permanent link), both of whose highlighting I also largely added for the same rationale as I did for the HTML element article. The HTML article's syntax highlighting is incomplete, but I will not be adding any further syntax highlighting of any kind until these discussions are through and unless the result permits my doing so.Lastly, I am sorry if these edits have been inappropriate. Although I am definitely not the first to be adding syntax highlighting (including inline syntax highlighting) in this way, I have definitely been a significant contributor to its recent expansion. It was, and remains, my understanding that doing so is a constructive improvement to the encyclopedia. Others obviously disagree, however, and it turns out these edits are more controversial than I expected. Regardless of what decision is made, I will abide by the consensus. Thank you all for your time and I look forward to further input from others. —Nøkkenbuer (talk • contribs) 02:16, 28 June 2018 (UTC)

Understanding GNL popularity
Look at the article Gender role. Look at the "Model A" and "Model B" table inside it talking about the difference between 2 extreme views of gender stereotypes. I would like to know if anyone can make a similar table except that it deals with language rather than roles. That is, the "Model A" column should be about language that reflects male superiority and the "Model B" column should be about gender-neutral language. Also, read the text below the table saying that the model followed in practice falls in between these poles. I guess this is also true of language. WP has a mention of using GNL in this project page, but it appears that in practice the rule that most Wikipedians prefer is that either GNL or GML (this stands for generic male language) is acceptable and unless there's a real reason not to the variant in the first nonstub version of an article should be kept, just like AE and BE (these stand for American English and British English.) (The source of this information is the section of this talk page just 2 sections above this one for clarification, I suggest anyone who comments on this section should study what's going on in that section.) Georgia guy (talk) 11:54, 1 July 2018 (UTC)
 * I would advise caution. While Pro and con lists is an essay, it's pretty sensible and grounded in WP:NPOV and WP:NOR policy. We really don't do pro and con lists.  In that one case, and a few others here and there, we're using a table to present an attributed notable pro/con model that is well-sourced, and not presenting it as fact.  So, we'd need to find reliable sources for such a model as applied to GNL, from an academic or organization that really matters.  But that's more of a content-guideline issue than an MoS one. If you just mean you think MoS itself should contain such a list/table, based on consensus-argued points, it would be unusual and might be prone to editwarring and PoV pushing. It'd be safer done as an essay page.  Sounds like a good essay, since there really is widespread dispute about this stuff on- and off-site, and people should not only think about it more, they should be more aware of a broader range of rationales on both sides.  But that also makes it seem like poor guideline matter.  It's not MoS's job to "teach the controversy", but to settle disputes firmly and give our readers prose that doesn't look like random half-literate bloggers on crack churned it out. >;-)  — SMcCandlish ☏ ¢ 😼  06:16, 2 July 2018 (UTC)

Single subsections
There has been an extensive discussion taking place at Wikipedia talk:Manual of Style/Film that has covered multiple issues regarding what actually counts as a subsection and whether it is incorrect to have only one. From that discussion, as well as one at Wikipedia talk:Manual of Style/Accessibility, it has become clear that there is no technical issue (either in terms of accessibility or general logic) with having a "single subsection" in cases where a section is divided into general content and a more specific sub-section that both fit under the same general heading. For example:

== Development == General development information. === Writing === Specific writing information.

This format is common in film articles that are structured based on the phases of filmmaking (as laid out in MOS:FILM), where we can end up with a whole lot of different information fitting under one phase (such as "Development") with a significant chunk also fitting under a more specific heading (such as "Writing") and being easier to read that way. To repeat, this is both common and easier for the reader than having all of the content mixed together. Now, the reason this has become an issue at all is has noted that many external style guides specifically state to avoid having only a single subsection and some of that wording has been carried over to places in Wikipedia. Myself and several other editors at the MOS:FILM discussion agree that though this is something good to aim for in terms of professional styling, it should not be a hard-and-fast rule. So in the above situation, if there was an obvious subheading that we could use to cover the non-writing content (such as "Casting" or something along those lines) then we would want to recommend that this be used, otherwise it does not make sense to manufacture a subheading such as "General", which is just unnecessary, only because we want to satisfy this rule.

I am suggesting that any wording that insists Wikipedia not include single subsections be replaced with some more general guidelines making it clear that a second subheading is recommended, but is not required if there is no natural heading apparent. If anyone else is in support of this, or has any comments to add, please go ahead. Thoughts on how this could be worded are especially welcome. If there are any questions, I will do my best to better explain/elaborate and I am sure the other editors involved in the previous discussions will join in here as well. - adamstom97 (talk) 08:43, 1 July 2018 (UTC)
 * What rationale do these external style guides give for avoiding this sort of thing? I've done this on occasion—in certain situations it helps avoid certain problems. Curly "JFC" Turkey 🍁 ¡gobble! 22:44, 1 July 2018 (UTC)
 * It is unclear what the rationale for avoiding single subsections is other than it being more "professional" because that is what has been done in the past, which is a big reason why I think it should not be a strict rule. - adamstom97 (talk) 22:50, 1 July 2018 (UTC)
 * If it solves a problem, that should take precedence over vague aesthetics. Curly "JFC" Turkey 🍁 ¡gobble! 23:02, 1 July 2018 (UTC)
 * I'll go over this again, but in bullet form this time since the original discussion was a trainwreck:
 * We use single subsections in sections for good reasons. Some very obvious ones:
 * The point Adamston.97 makes above about breaking up huge blocks of text for easier digestion.
 * Reader navigation. If a significant subtopic of an article is reached at the article by a redirect, readers should be able to jump right to it. Even if they show up at the top of the page and suspect this is the right one, they should find their subtopic quickly and easily in the table of contents, not have to wonder where it might be and wade through 37 paragraphs of material to find what they're looking for.
 * Avoiding permanent bias, and inspiring breadth of coverage: If you create, say, a geographical section and start it with information on your home country (most often the US, by dint of the number of American editors), if this section has no  subsection heading, it gives a very strong impression that the subject is intrinsic to or dominated by the US. But if you do create that section, it is a key signal to later editors that more such sections should be added ASAP.
 * WP:NOT: Not only does WP not follow external style guides (the first discussion was utterly mired in bible-thumping about The Chicago Manual of Style). We have our own. WP is not a paper publication, nor does it work like one.
 * To wit: the idea of never having a single subsection by itself under a section is a layout idea for . No articles at Wikipedia are finished (though FAs change only slowly being pretty close to finished). It makes some sense in many completed works (especially journalism and essays) because if no more content is ever going to be added to the section, a single subsection doesn't serve much of a purpose.  That just isn't true here. A new subsection can be added at any time.
 * Even in paper works, the pseudo-rule against single subections, as found in some, not all paper style guides, is regularly ignored, most especially in formalized, programmatic material like statutes and regulations, instruction manuals, taxonomic catalogues of creatures/plants, and other material that – like Wikipedia – has a formulaic approach to content presentation.
 * WP:NOT is a policy for a reason. MoS should have no line-item suggesting or demanding that people create a second subheading, i.e. simply because there's a "rule", or people will create ones that do not make sense simply to be in robotic compliance. No heading, subheading, subsubheading, etc. should exist that doesn't make sense in the context and genuinely help organize material for readers.
 * MoS does not address matters that are not important to presenting quality content to the readership and forestalling disruptive style fights amongst the editorship. Otherwise it would be an order of magnitude longer and no one would read or remember any of it.  One user in 17+ years who is doggedly insistent on imposing someone's external subsection "rule" on us doesn't amount to a controversy, just yet another momentary waste of editorial time.


 * That compresses a whole lot of material from the other threads.  — SMcCandlish ☏ ¢ 😼  04:24, 2 July 2018 (UTC)
 * I tend to agree that hard and fast rules are not a good idea here. Not sure on the precise language, but editors should see this as a red flag that might indicate a problem, not a problem in and of itself. If an editor comes across a section with a single subsection, they should probably ask 1) "Do additional subsections need to be included?" and 2) "is the information in this subsection conceptually independent the parent section?". If the answer to both is "no", then it ain't broke.  [[User:Nblund |<span style="background-color:


 * 1) CC79A7; color:white;">Nblund ]]talk 17:26, 2 July 2018 (UTC)


 * The MLA, APA, CMOS and the other less common MOS for writing all indicate that single subsections are to be avoided (sans exceptions that are outlined in the MOS). My argument has always been that Wikipedia is an encyclopedia and specifically strives for professionalism in their articles. All of the main MOSs (MLA, APA, CMOS) have this as a current rule to distinguish professional writings. Why does this rule exist, I don't personally know. I've also never seen us question the philosophy behind a writing rule from one of the major MOSs before either.


 * To quote CMOS who attempted to answer the reason why you should not typically have single subsections: "Say you want to divide something—a book, an article, or a chapter—into chapters, parts, or sections. Note that this is already a matter of plurality. One cannot have a book that contains a part 1 but no part 2 or a chapter 1 but no chapter 2. Subheads are often unnumbered, unlike parts or chapters, but why “divide” a chapter into just one subsection? Similarly, why introduce just one second-level subhead? If you do, you might want to think about inventing a second, complementary subhead. But if this principle of division is a rule, there are exceptions to it. For example, a unique subsection like “Notes” or “References” might be necessary for chapter-ending notes or references. And, especially at the B level or lower, a single subhead in a given section might turn out to make sense—especially if it corresponds to subheads of the same level in other sections within the same work. So, in general, follow the rule for the sake of logic; break it only when you can cite a superior logic."


 * To me, this rings true especially for Wikipedia, which aims to write professional documents about topics, even of those topics are fan based topics (films, comics, etc.). I am NOT saying that if you have a single subsection you MUST create a second when there isn't information to support it. To me, If you have a single subsection, and the rest of the information in not enough or not focused enough (i.e., covers various other topics and not one in particular to justify a second split), then you should take that single subsection and bump it up to its own section where it doesn't disturb the flow of the article. For the example that started this all, Deadpool 2, it was separating out 2 areas: Marketing from Release and then Writing from Development. I'll focus on the writing one. In this case, there was enough unique information solely about "Writing" to warrant separation under "Development", but not enough to separate anything else. Given that, and that the information left under "Development" has nothing to do with writing, but getting the film off the ground, it makes sense to make Writing its own section.


 * At the end of the day, it boils down to professional writing and article organization. If an external MOS says that professional documents typically do not have single subsections, then I would assume that as we strive for professionalism we would follow that basic principle. What should we do? I think we should clearly state (at the subsection guides) that as a general rule of thumb, you should avoid using single subsections. "When you determine that enough information should be separated out as a subsection first determine if there is other information that can be separated out in order to follow this general rule. If there is no logical' division of other content, then assess if the information you want to separate could stand as its own section, including assessing to see if what is left in the divided section can exist without the information being separated (e.g., Creating a single subsection of information that ultimately leaves 2 sentences behind in its division). Failing those situations, a single subsection may be warranted." --   BIGNOLE     (Contact me)  19:35, 2 July 2018 (UTC)
 * This is already addressed in the numbered points above. Not going to repeat it all again. Your personal notion of what's "professional" in some other context doesn't override all other concerns.  — SMcCandlish ☏ ¢ 😼  23:18, 2 July 2018 (UTC)

Expanding the section on Gender-neutral language
This section currently has two very brief paragraphs, one of which exclusively addresses how to refer to ships (!!). Recent experience indicates that clearer guidelines might be helpful, but also that consensus might be difficult to achieve. Any thoughts? Cl ea n Co py talk 06:20, 3 July 2018 (UTC)


 * There is certainly more that could and should be said. The clear risk, to which you allude, is that discussion would spiral out of control (as you can see above, regarding just one word) given likely agendas, on all sides, and of course practice varies, not only around the world, but between sectors - common language in politics or the arts is likely different from that in business or sport.  For these reasons I'd suggest WP would be sensible to stick very closely to guidance drawn from one of the leading English usage style guides; this would also help focus any debate.  The biggest shift, made recently by Chicago, Oxford University and Associated Press, is the acceptance of "they" as a singular pronoun, as a resolution of the 'he v she' debate. MapReader (talk) 06:48, 3 July 2018 (UTC)


 * There is a reason why we don’t have more (expanded) guidance... lack of consensus as to what we should say. What you see now is about all that we have been able reach consensus on... and even that little bit of consensus only emerged after a lot of discussion and debate. Blueboar (talk) 21:14, 3 July 2018 (UTC)

RfC on the treatment of organizational colors
Please see Talk:Milwaukee Bucks

This is really beyond the Milwaukee Bucks or even sports in particular, and relevant to coverage of organizations and their house styles generally. This touches on all of: MOS:CAPS, MOS:TM, WP:NOR, WP:NPOV, and WP:NOT, in various aspects (see the more detailed discussion below the !vote section). — SMcCandlish ☏ ¢ 😼  19:20, 4 July 2018 (UTC)

A consolidated MOS:SPORT?
Things like the "team colors" RfC pointed to just above, and many other recurrent specialized-style fallacies at sports articles (see also recent WP:SPORTSCAPS RfC, among others), strongly suggest that we really need a MOS:SPORTS page.

We could probably start by merging MOS:CUE and MOS:SNOOKER into a single page; much of their advice is generalizable (on purpose; I wrote most of MOS:CUE and had it in mind to broaden it, though it hasn't seen substantive revision in years and a lot of it needs trimming).

What is actually particular-sport-specific could be compressed to a section on the particular sport. Lots of sports wikiprojects have style advice essays. Points from them, that people already follow in writing articles on that sport and which aren't directly in conflict with general MoS stuff, could be merged into new sections.

This really should have happened a decade ago. Back then, it looked like we'd end up with an MoS page for every major sport, but we ended up with just two, the one a subtopic of the other. That's not very practical. — SMcCandlish ☏ ¢ 😼  21:14, 4 July 2018 (UTC)

Merge some fiction stuff, too?
Along similar lines, I think a lot of redundant (and potentially conflicting) material at MOS:TV, MOS:FILM, MOS:ANIME, etc., could be merged into MOS:FICTION.

Have the medium-specific stuff be retained in the separate pages, but centralize the general stuff at the main FICTION page, and treat it in the medium-specific pages only in WP:SUMMARY style with cross-referenced with to the general, main version at MOS:FICTION.

This would help prevent any further "policy-forking" and inconsistent treatment of fictional material just based on it being a TV show versus a film (and what about a television movie?). — SMcCandlish ☏ ¢ 😼  21:14, 4 July 2018 (UTC)
 * Pro wrestling too, since it's a fiction as well. <b style="color: red;">E</b><b style="color: blue;">Eng</b> 21:52, 4 July 2018 (UTC)
 * Them's fightin' words. But then we'd have to agree on who's going to "win". I call dibs on heel.  — SMcCandlish ☏ ¢ 😼  22:02, 4 July 2018 (UTC)