Wikipedia talk:Manual of Style/Archive 188

Parentheses usually look right to me.  SchreiberBike | ⌨  00:32, 2 December 2016 (UTC)

Whether parens or commas, I'm OK, but but the italics seem unusual and wrong to me. Are there guides that suggest italics? Dicklyon (talk) 01:55, 2 December 2016 (UTC)

• Before we get too far into this, where's the evidence that MOS needs to opine on this? If not, we should leave this to the editors of individual articles. I feel strongly that making up guidelines in the abstract, without actual parties, to actual article disputes, who have actual opinions and reasons for them, is a bad idea. EEng 02:08, 2 December 2016 (UTC)

The OP used italics, and that got reverted, so it does seem like an actual dispute. I don't necessarily think the MOS needs to say anything, if we mostly agree already that there's no good basis for using italics. I tried book searches such as this looking for examples; found one using bold, none using italics. Dicklyon (talk) 02:11, 2 December 2016 (UTC)

MOS:ITAL list the cases in which italics are used, and stage directions is not one of them. By implication, then, italics ought not be used. Mitch Ames (talk

) 02:13, 2 December 2016 (UTC)

MOS isn't a Talmudic text and is incomplete in many ways, and one reversion does not mean MOS needs to step in. Let's see multiple articles where editors have been unable to work this out for themselves. EEng 02:19, 2 December 2016 (UTC)

Italics are used an alternative to parentheses (round brackets). I would say we should admit both styles and probably prefer the latter usually, as clearer, for the same reason that we permit both italics and quotation marks for

MOS:ABBR saying to avoid randomly abbreviating things.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  09:05, 2 December 2016 (UTC)

The cramped confines of captions are a great example of a place in which the balance shifts toward using an abbreviation where we wouldn't otherwise. EEng 09:27, 2 December 2016 (UTC)

Captions are not so "cramped" that dropping a handful of characters from a single word makes any practical difference in length, yet doing so makes a major (negative) intelligibility difference, especially for non-native speakers.

I agree with SMcCandlish that we should admit both styles, italics, or regular font in parentheses (round brackets). (I prefer italics if there aren't other italics nearby; I think it reduces attention to the words "left", "right", and "foreground", or at least makes it clear the words are not part of the thought of the caption, while parentheses are distracting, but that's just my preference.) So, if it is agreed that both are acceptable, then are we saying that regular font without parentheses, like this ..., right. or ..., right,... is not acceptable?  – Corinne (talk) 01:28, 4 December 2016 (UTC)

...makes it clear the words are not part of the thought of the caption... — But the words are explicitly part of the thought of the caption. The caption describes the picture, and the positions of the people in the picture are a legitimate part of the description. Mitch Ames (talk) 05:24, 4 December 2016 (UTC)

And the point of bracketing parentheticals is to minimize their impact, by framing them out of the central flow of the sentence. This is literally the function of parentheses/brackets in natural language. By contrast, italics have the exact opposite primary function, indicating emphasis. (The fact that they're also used for many Latinisms and other non-English insertions, and that these are often editorial in nature (cf., ibid., etc.) is probably why anyone wants to italicize left and right in captions at all.) It's probably the less practical of the two common approaches. We don't need to explicitly try to "ban" not using one style or other and just using plain style. There's not anything intrinsically wrong with something like "Nixon, right, shaking hands with Mao, left". It should be enough to generally recommend the use of parentheses or italics, whichever works better in the context. There are cases (especially increased specificity), when using either style (especially italics) may not be the best idea, e.g., "Salamanders of the eastern United States: Notophthalmus viridescens (eastern newt), top right; ...", where both parentheses and italics are already being used for something else, too, and in a collage of 6 images or whatever, the locators may be things like "second row, right" or "middle right", and so on.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  11:37, 4 December 2016 (UTC)

Is there any reason for me to stop using italics with parentheses, as I've consistently been doing for probably a few years now? Somehow I'd gotten it in my head that that's how we were supposed to do it, and it seems to avoid some of the problems some folk have brought up above. Curly "the jerk" Turkey 🍁 ¡gobble! 11:44, 4 December 2016 (UTC)

Seems redundant and likely to inspire someone to remove either the italics or the parentheses (as they would if you simultaneously italicized and quoted a words-as-words case, or both italicized and boldfaced something for emphasis). But, if that's all that happens, no big deal I guess.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  12:20, 4 December 2016 (UTC)

A comment from S. McCandlish so uncharacteristically laissez-faire that we should notify the media! EEng 16:40, 4 December 2016 (UTC)

I actually oppose most ideas for additions/changes to MoS as unnecessary or unhelpful. This thing has been here for 15+ years. It's pretty solid. The two major bits I've been working on for an extended period of time that are still nominally drafts (

MOS:NUM. Virtually every case they'll ever need to cover is already covered.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  10:49, 8 December 2016 (UTC)

MOS:ORGASMS??? Is there no limit to MOS overreach? EEng 18:24, 8 December 2016 (UTC)

@EEng: That would be MOS reach-around.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  09:48, 12 December 2016 (UTC)

I'm sorry -- come again? EEng 13:14, 12 December 2016 (UTC)

Best avoid italics, I think. Martinevans123 (talk) 15:14, 12 December 2016 (UTC)

As mentioned above, italics are for emphasis, and so personally I think it is unusual to emphasize a position indicator. isaacl (talk) 16:23, 4 December 2016 (UTC)

No, italics are for distinguishing something, often (but not always) for emphasis. When a dictionary says –

I·tal·ic (ĭ-tăl′ĭk, ī-tăl′-) adj. 1. Of or relating to ancient Italy or its peoples or cultures.

– it's not emphasizing that the word is an adjective. EEng 16:40, 4 December 2016 (UTC)

Yeah, I was trying to get at that when I said "italics have the exact opposite primary function, indicating emphasis. (The fact that they're also used for many Latinisms and other non-English insertions, and that these are often editorial in nature (cf., ibid., etc.) is probably why anyone wants to italicize left and right in captions at all.)" Because they're "operator overloaded" for emphasis and some other functions, they tend to be parsed as emphasis until the reader figures out they're something else – an unnecessary, distracting "time out" for the reader. Meanwhile, parentheses/brackets have the opposite function, which is why I would suggest they be preferred for this by default, though I don't care all that much, for reasons Herostratus gets into below. I agree we need not have MoS say anything like this, unless the issue comes up repeatedly and wastes more editorial time than it will take to get consensus to add it.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  10:49, 8 December 2016 (UTC)

This is certainly something that should be left up to the individual editor, for various good reasons. One good reason is that (as we can see above) there is no one clear correct or better way. A second good reason is that adding another needless rule bogs down the MOS with more detail and makes it harder to learn and harder to use. A third good reason is that creating a rule means enforcement, it puts interactions about the matter into an enforcement mode where editors are playing rules cop with other editors and this is not as functional as peer-to-peer interactions. A fourth good reason is that there's zero evidence that it matters to the reader.

A fifth good reason is that micromanaging editors to this level is demoralizing and not how you attract and nurture a staff of volunteer editors (for instance we have a stupid micromanaging rule that I have to write "in June 1940" and not "in June of 1940" which is how I naturally write, and every stupid micromanaging rule like this is just another reason to just say screw it. As the Bible says "Thou shalt not muzzle the ox that treadeth out the corn" (1 Timothy 5:18, paraphrased from Deuteronomy 25:4) which updated means "Let the editor who did the actual work of looking up the refs and writing the friggen thing -- you know, the actual work of the project -- be at least allowed the satisfaction of presenting it as she thinks best, within reasonable constraints".

That's five and that ought to be enough although I'm sure I can come up with more if pressed.

If you run into a situation where (as the OP noted) "In this edit, Mitch Ames removed the italics from "right" that I had just added" then play it as it lays, guided by

Conversely, if the italics had been there for a while (sufficient to be part of the stable version of the article) then the removal of the italics would be subject to rollback per

This means different articles will do it differently. This annoys a certain type of editor. Oh well. Herostratus (talk) 17:10, 4 December 2016 (UTC)

Herostratus, that's possibly the most beautiful and powerful indictment of MOScreep/overreach I've ever read. Here's what I always trot out in these cases:

A. It is an axiom of mine that something belongs in MOS only if (as a necessary, but not sufficient test) either:

• 1. There is a manifest a priori need for project-wide consistency (e.g. "professional look" issues such as consistent typography, layout, etc. -- things which, if inconsistent, would be noticeably annoying, or confusing, to many readers); OR
• 2. Editor time has, and continues to be, spent litigating the same issue over and over on numerous articles, either

• (a) with generally the same result (so we might as well just memorialize that result, and save all the future arguing), or
• (b) with different results in different cases, but with reason to believe the differences are arbitrary, and not worth all the arguing -- a final decision on one arbitrary choice, though an intrusion on the general principle that decisions on each article should be made on the Talk page of that article, is worth making in light of the large amount of editor time saved.

B. There's a further reason that disputes on multiple articles should be a gating requirement for adding anything to MOS: without actual situations to discuss, the debate devolves into the "Well, suppose an article says this..."–type of hypothesizing -- no examples of which, quite possibly, will ever occur in the real life of real editing. An analogy: the US Supreme Court (like the highest courts of many nations) refuses to rule on an issue until multiple lower courts have ruled on that issue and been unable to agree. This not only reduces the highest court's workload, but helps ensure that the issue has been "thoroughly ventilated", from many points of view and in the context of a variety of fact situations, by the time the highest court takes it up. I think the same thinking should apply to any consideration of adding a provision to MOS.

See [12] and [13]. Perhaps we should collaborate on an essay.

EEng 04:29, 6 December 2016 (UTC)

Generally agreed with both of you, and these are among the reasons I so strongly resist changes to MoS, which can affect literally millions of articles. That said, two quibbles:

1) There is no "stupid micromanaging rule that [you] have to write 'in June 1940' and not 'in June of 1940'"; there's just a rule that you can't editwar tendentiously to prevent others from removing the unnecessary "of", or to force the "of" into existing content. This applies to similar guidelines, too; e.g. no one has ever been banned or blocked for adding bare URLs as citations despite

WP:COMPETENCE problem.

Making editors happy is a bottom-rung WP goal to the extent it is one at all; satisfying readers is the main public one, and being successful as a project is the main internal one; both of these require a minimization of strife so the work can continue, through compromise, i.e. through editors learning they cannot always get what they want and that their individual wants take a back seat. Those who refuse to write any way but their way should go be bloggers or novelists. MoS is not micromanaging editors, only content. This is necessary to a limited extent, and participation in that nit-pick management is optional, just as are all the other forms of chrome-polishing around here, from GAN and FAC, to categorization details, to filling out infoboxes and navboxes, etc. We resist willy-nilly expansion of MoS's extent, for all the reasons you two just outlined. A personal feeling of micromanagement can, in my experience, be traced directly to over-identification with the content (a failure to actually release it to the community except in name), and over-investment in winning style-related disputes (as some kind of sport debate or holy war), or both of those issues at once. (I initially arrived at WP and MoS exhibiting both, and had to unlearn those approaches.) MoS's stability and its conflict-reduction effectiveness are more important than its line-item details.

2) The "demonstrate that it's a real problem" process only applies to adding something new. It's fallacious reasoning when applied in an attempt to remove something long-standing from MoS (or any other policy, guideline, etc.); the very existence of the rule makes the incidence low or non-existent. "I want to delete the rule to not capitalize for emphasis because people aren't capitalizing for emphasis" is invalid logic. We do sometimes remove a rule, but it's almost always on the basis of obsolescence, or it being an implausible addition no one bothered to question back when it was added (especially on some of the more nit-picky subpages that aren't watchlisted enough).
 — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  10:49, 8 December 2016 (UTC)

I agree with the point of view that says this isn't something the MoS needs to concern itself with. As long as the result is clear to the reader, the exact format can be left to the editors working on the article. Mike Christie (talk - contribs - library) 18:51, 4 December 2016 (UTC)

I was specifically describing the use of italics within a sentence in prose. Italics in this situation is for mild, local emphasis, whereas bold within a sentence is for stronger emphasis. isaacl (talk) 03:52, 5 December 2016 (UTC)

Bold is specifically discouraged except for special cases such as the title in the lead. Just as in most external styles, italics is preferred for emphasis, not bold. Dicklyon (talk) 06:28, 6 December 2016 (UTC)

Yes, in case there was any confusion, I wasn't providing any guidance on the use of bold but simply describing a high-level view on how its role differs from italics. As stated, bold is used very sparingly in published material (much like how in speech, shouting for emphasis is best saved for very specific circumstances). isaacl (talk) 06:53, 6 December 2016 (UTC)

I appreciate all the comments here. Everyone is right – the best formatting for the position-indicating words ("left", "right", etc.) may depend upon the formatting of the rest of the caption; the question of whether one is justified in reverting a change in formatting may depend upon how long a particular format has been in the article; since various formatting styles seem to be acceptable, there is no good reason to require one style over another in the MOS, and doing so may cause more problems than it is worth; and finally, it is not important enough of an issue to spend a lot of time on, including reverting and arguing about it. Thanks again.  – Corinne (talk) 17:26, 5 December 2016 (UTC)

It's worth noting that, while MOS silence may be deliberate, there is no way to make that apparent to future editors. We should consider which is worse: Adding a sentence to indicate that this is up to editorial discretion, or having the issue brought up from time to time, possibly without awareness of previous discussions by any of the participating editors, to eternity or the end of Wikipedia, whichever comes first. ―Mandruss ☎ 07:00, 6 December 2016 (UTC)

The "it keeps coming up at WT:MOS" thing hasn't usually proven all that problematic, though it is the reason a few "it's up to discretion" statements have been added here and there, and the reason for

MOS:FAQ, which needs expansion. When it keeps coming up in the talk pages of articles is usually when we add something to MoS itself about it.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  10:49, 8 December 2016 (UTC)

As always, I'd like to see diffs of actual problems that have arisen that your proposal would have avoided. EEng 09:44, 10 December 2016 (UTC)

Can I point out that the link to protologism redirects to neologism where the only mention is a see also for protologism. Could spend a long time on that if ones short term memory is failing. SpinningSpark 18:30, 10 December 2016 (UTC)

It was recently redirected. Then it was un-redirected. And now it's at AfD.

talk

) 09:46, 12 December 2016 (UTC)

Very interesting indeed. Andrewa (talk) 16:59, 17 December 2016 (UTC)

In reading

In reading

The text already says Straight quotation marks are easier to type. As for single vs. double, please search the archives for what the enormous discussion on this, then come back here if you have something new to offer. EEng 01:33, 18 December 2016 (UTC)

Searching previous discussions would not be productive.

MOS:SINGLE now says, editors may happily choose to use double quotes within singles as long as this is consistent within an article. Bjenks (talk

) 02:11, 18 December 2016 (UTC)

If you favor disregard for SINGLE as to quotemarks, what do you seek on this MoS talk page? Permission? ―Mandruss ☎ 02:20, 18 December 2016 (UTC)

Yes, I'd like to know that too. COMMONALITY is about diction, and as a professional proofreader you don't need to be told what a house style is. Stuff like this has been an enormous time sink for literally a decade. EEng 03:12, 18 December 2016 (UTC)

Please don't go there. If you want to disregard SINGLE, or re-open a discussion about whether it's a good idea, you'll waste a lot of everyone's time and end up back in the same place. Dicklyon (talk) 04:28, 18 December 2016 (UTC)

Thanks, DL—I hear you and promise to desist from further discussing here the questionable wording of SINGLE. Bjenks (talk) 06:00, 18 December 2016 (UTC)

RGloucester reverted what is supposed to be the shortcut to the section about English varieties. If that is not a suitable shortcut, where else? --George Ho (talk) 18:38, 20 December 2016 (UTC)

We already have the universally used

MOS:CITEVAR. There is no justification for using the bare 'VAR' as a shortcut to ENGVAR. It ought be deleted. RGloucester — ☎

18:42, 20 December 2016 (UTC)

I created it as far as I did. I don't want to delete it. What if I can turn this into a disambiguation page? Would that help? --George Ho (talk) 18:44, 20 December 2016 (UTC)

I suppose that redirecting it to the same place as

MOS:STYLEVAR might make some sort of sense. RGloucester — ☎

18:49, 20 December 2016 (UTC)

 Done. --George Ho (talk) 19:16, 20 December 2016 (UTC)

You are invited to join the discussion at Talk:Unknown Pleasures#RfC: Italics for Pitchfork (website) magazine?. — JJMC89 (T·C) 04:42, 26 December 2016 (UTC)

Regarding this edit: the link prefixed with an unadorned section symbol, §, is an indication that the link is an internal link. From my writing experience, positional indicators such as "above" and "below" are discouraged, and with the specificity now available through hyperlinks, readers can easily locate the appropriate section by following the link. I appreciate, though, that some people may be accustomed to these indicators. Does anyone have any other views? isaacl (talk) 15:53, 27 December 2016 (UTC)

Then convert the "above" and "below" to [[#Whatever|above]], etc., as appropriate (and it would not be useful if it's in the same section, of course). Tony1 is correct that "above" and "below" are important cues that the material is on the same page, even as your own point is valid, that the material can be directly linked to.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  23:15, 27 December 2016 (UTC)

Does this mean that if our article quotes a portion of text from a religion's scriptures that does so, we should use square-brackets to decapitalize the "He" in "but He did not have regard for Cain and his offering". Hijiri 88 (聖やや) 02:22, 25 December 2016 (UTC)

No; see

MOS:ISMS to indicate not to make such changes in directly quoted material, but I'm skeptical this is necessary, since the question is rarely raised (this may be a first, in fact).  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  23:35, 27 December 2016 (UTC)

That came in with this diff on a particularly busy editing day many years ago, with edit summary indicating that "The Ohio State University" is the only institution he knows of that it would apply to. So, should this institution get a capitalized "The"? If so, doing so as an exception might be a better idea than writing it into the MOS such that we turn over the style to arguments about editors' opinion of what institutions want, sort of like what we backed away from in cleaning up

MOS:JR. Just undo it. Dicklyon (talk

) 05:07, 28 December 2016 (UTC)

I already have, putting it in line with the three other guidelines.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  08:15, 28 December 2016 (UTC)

And as the article says, the basis for the cap The is actually pretty sketchy; essentially just a logo. See this ref. Seems overblown, or over-interpreted, to interpret that the institution cares much about the caps on "the". Dicklyon (talk) 05:20, 28 December 2016 (UTC)

I.e., it's precisely what's addressed already at the other guidelines. We just need to cross-reference them with a note at MOS:TM that "The" isn't capitalized in the name of organizations even if their own materials style it that way. It's just a missing line-item at that page, that you have to look in MOS:THECAPS or MOS:CAPS#Institutions to find. (Publications are an exception, per

MOS:THECAPS.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  08:58, 28 December 2016 (UTC)

I think it's important to make clear what we mean by "publication". Thus there are websites and online databases that are effectively "publications", such as The Plant List. Peter coxhead (talk) 08:25, 28 December 2016 (UTC)

I would think

MOS:TITLE would cover that. I agree that we do need to clarify (because it keeps coming up again and again – just saw it early today in an RfC, and people keep trying to re-litigate it article by article by article) that an e-publication is still a publication, and receives the same capitalization and italicization as a dead-trees one, when it's being addressed as a published work not as an organization (my go-to example for this: "She had an article published in Salon", versus "He left his job as the webmaster at Salon.com in 2009". This is the same distinction as The New York Times (the publication) and The New York Times Company (the legal entity). For one thing, our citation templates are always going to italicize it when cited as a work, and for another it just doesn't make sense that an online publication is less of a publication and doesn't get the same stylistic treatment as one printed on wood pulp. What next? Does my song not get "The Conventional Song Quotation Marks" because I released it online instead of on a CD?  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  08:58, 28 December 2016 (UTC)

Regarding this edit: note the link that was removed pointed to additional details on a separate page. I feel it is more appropriate for a manual of style to give a link to the appropriate guidance, rather than just saying "the usual way". Would anyone else like to weigh in? isaacl (talk) 15:43, 27 December 2016 (UTC)

The solution is to either link to #Titles on the same MoS page (which does not cause a confusing reload of the same page), or to Wikipedia:Manual of Style/Titles#Italics, a more detailed drill-down on the same topic.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  23:13, 27 December 2016 (UTC)

The removed link was to Wikipedia:Manual of Style/Text formatting#Italic type, which does not cause a reload of the same page. isaacl (talk) 14:01, 28 December 2016 (UTC)

A return to shared and neutral principles is long overdue. We have just seen fruitless discussion of provisions in the lead under the dubious and concealed title "WP:STYLEVAR", and the addition of a new section called "Retaining existing styles".

What and where is

WP:STYLEVAR

?

My inquiry addressed to SlimVirgin on this talkpage yielded no answer:

... this mysterious WP:STYLEVAR. You say it has always been around, pretty well; and that it once had a section of its own. But I do not find "WP:STYLEVAR" anywhere on this main page of MOS. Please help us here. Where did that name come from? In what edit was the name invented? Who made the redirect that takes us there, and for what purpose? What documentation and discussion accompanied those actions? I ask you, because you seem to be the main supporter (and certainly the main protector and user) of that invisible location in MOS and the seemingly "official" redirect that you present as a documented and consensually settled feature of MOS.

So I went looking for an answer myself. Slim Virgin turns out to be responsible for attempting to make that shortcut a "thing", in this edit to MOS on 31 August 2015. Among the addition and shifting of other stuff, note the insertion of "STYLEVAR". SV's two-word edit summary was "per talk". But there was no discussion of that insertion here at

With an edit summary reading "+ red", SV minutes before had created the redirect called "WP:STYLEVAR". Such an "official" WP shortcut is normally subject to scrutiny and discussion; this one never was discussed, anywhere by anyone.

The new section "Retaining existing styles"

Apparently because WP:STYLEVAR was nowhere to be seen, though SV often referred to it, someone added a new section in MOS with the shortcut

My own edits: back to transparency and shared principles

This sort of to and fro has been going on for far too long: SV removes wording from the lead that has stood for about 12 months; others restore it; SV or someone else reverts, appealing to "consensus" and using a spurious WP shortcut that was never anything like consensual.

I've removed contested material from the lead altogether. It was never consensual, and it is now redundant given the new section "Retaining existing styles". I've put WP:STYLEVAR among the shortcuts to that section, so at last it is visible to everyone (not just those who edit the lead).

I've shortened that new section, reducing it to something minimal we can all accept. Perhaps that is enough; but if anyone wants to add content, let them justify it here. This page is still under ArbCom sanctions, and we are quite rightly required to get consensus for the provisions of MOS.

Looking forward to that discussion, and to no insertion of controversy again.

Tony (talk) 10:18, 24 December 2016 (UTC)

I have never in my life heard of the priniple that shortcuts should be discussed beforehand. Perhaps you can link to it? A shortcut is just a shortcut; in itself, it says nothing at all about policy or anything else. The page loading issue is easily dealt with. No need to remove anything to achieve that.

The purpose of the section was merely to gather together in one place links to places where the MOS has specific guidance on style variation. It also notes that there is a common thread running through this guidance, and that people shouldn't edit war over style issues. None of that invents anything new, nor was it intended to. It links to existing guidance, the existing lead establishes a general principle, and edit warring is against existing policy.

On arbcom, I don't think that arbcom should be mentioned at all in the text. It should be reworded so that it does not sound like a threat to editors, with the arbcom ruling relegated to a footnote. SpinningSpark 11:01, 24 December 2016 (UTC)

I was the one who added (or rather transcribed) the reference to Arbcom from the lede to the section. Before I got there, it read like the rule applied only to those four specific areas. Better not to leave the point open to debate: it applies across the board to any style choice where different options are available. Don't matter if it's variety of English or infobox styles or whatever else. If there are multiple options, people shouldn't be changing between them unless there's a good substantial reason (beyond personal preference) to do so.

This is per the existing guideline. The general principle has been at the top of

WP:MOSNUM. Whether we mention Arbcom in the text or a footnote, I'm not overly bothered. But I would be very concerned if the general nature of the rule were to be downplayed or removed. Kahastok talk

11:22, 24 December 2016 (UTC)

I wasn't suggesting that the principle shouldn't be stated (don't think we should call it a rule though). My point was we can state it without invoking the threat of arbcom. SpinningSpark 11:40, 24 December 2016 (UTC)

...and ha ha, an IP has just reinstated Tony's edit. How convenient. SpinningSpark 11:40, 24 December 2016 (UTC)

• Tony, I have a question for you. As far as I can see, you are the originator of the modern form of what we are now calling 'STYLEVAR'. At the time of its introduction, in 2007, it read:

In June 2005, the Arbitration Committee ruled that, when either of two styles is acceptable, it is inappropriate for an editor to change an article from one style to another unless there is a substantial reason to do so (for example, it is acceptable to change from American to British spelling if the article concerns a British topic, and vice versa). Edit warring over optional styles is unacceptable. If an article has been stable in a given style, it should not be converted without a style-independent reason. Where in doubt, defer to the style used by the first major contributor. See Wikipedia:Requests for arbitration/Jguk.

This piece of the lead has continued on since then in various forms, and I believe it should stay. It has been an important principle, and I believe that consensus supports it. I do not think that it was wise of you to remove it, and can't understand why, given that it seems to have originated with you. Prior to that edit, various forms of the same passage had been part of the MoS from 3 March 2006, with an addition by the above mentioned party following an arbitration case. In any case, I do think it is important that editors are made aware of the fact that ArbCom has issued multiple rulings on this matter, and that discretionary sanctions have the potential to apply. Furthermore, anything we can do to discourage edit-warring, whilst also maintaining the primacy of the MoS, should be done. RGloucester — ☎ 16:57, 24 December 2016 (UTC)

Where is your question, RGloucester? I don't see one.

You point out that SV first inserted a version of the contested wording. She started a new section for it: "Disputes over style issues". Back before we suspected what use SV would make of her text, all I did was to trim the version I found and join it into a tidier lead. Note my clear edit summary, inviting discussion. Just two weeks ago we find Slim wishing it back into its own section: "This used to have its own section within the MoS, but it was moved to the lead. Perhaps we ought to move it back so that it's clearer as a principle".

I agree. Given the use her wording has been put to over the years (most often by SV herself), the surreptitious addition of "WP:STYLEVAR" (which took the hapless reader merely to the top of the MOS page), and the fact that there is now a separate section (called "Retaining existing styles"), I've done what SV has wanted. I've also removed SV's extra provision: "Where in doubt, defer to the style used by the first major contributor. See

MOS:LQ, which has always enjoyed sturdy consensus despite all attempts against it from SV and others.

Does anyone think ArbCom is happy for an editor to alter style that Wikipedia does mandate? ("As for punctuation, I don't use LQ ...".) Hmm.

Have I answered your implicit question, RGloucester? Your last sentence: "Furthermore, anything we can do to discourage edit-warring, whilst also maintaining the primacy of the MoS, should be done." This is what I've done, in my minimalised common-ground text. For which I invite further discussion—and any additions that are demonstrated, here at talk, to be necessary and to reflect current consensus.

Tony (talk)

01:59, 25 December 2016 (UTC)

My question was about the reason for your surprise at the nature of the so-called 'STYLEVAR', despite your having edited said passage as far back as 2007. In any case, you've answered the question. And, I agree whole-wholeheartedly with the ArbCom principle as you've recounted it, and I would like some form of the above passage to remain in the lead (not in a separate section), with that principle as a basis. The recent revisions on both sides have created a mess. RGloucester — ☎ 08:46, 25 December 2016 (UTC)

Five steps toward stability: fixing "Retain"

RGloucester, I'm glad that's sorted out. We agree: many recent revisions have created a mess. So have several that are not so recent, as I have shown. It's time for a collegial effort to bring about stability. Let's all work together. That's what I propose, starting from the simple shared foundation I've now put into MOS.

Best-practice Wikipedian procedure, in such a case:

1. We focus first on the section itself: "Retaining existing styles".
2. When there's been proper discussion and review of that section here, we insert the new version into MOS.
3. We consider just how much of its content should go into the lead. (No content belongs primarily in a lead, as
   WP:LEAD
   makes clear: "The lead serves as an introduction to the article and a summary of its most important contents.")
4. We make sure that all internal and external links are correct, visible, up to date, and stable, and generally tidy the workshop once the job is done.
5. We place a note (an "advertisement") that the work is completed here on the talkpage, and appeal for any future changes to the lead, and to the crucial "Retain" section, to be discussed here first. A hidden note or two in MOS would help.

Kahastok, and everyone else here who cares about MOS as a core resource for Wikipedia, let's insist to everyone that good intentions are not enough. This has been a perennially difficult area to get right. Despite claims that one or another version is time-honoured and stable, no version ever has been. Can we all move forward cautiously, with respect for views held on all sides? (Better, let there be no "sides".) If anything is inserted in the absence of well-conducted dialogue, and without good notice in edit summaries, the same old problems will return. Could be days, weeks, or years: but as we have seen, they will come back to bite us.

As I see it, keeping things short and simple is the best default strategy. What we have right now can be accepted by everyone, right? Some will think X is missing, some will clamour for Y instead. So a basic version lacking both X and Y may be best.

I suggest a completely new talkpage section below (referencing this one), for orderly discussion toward stability in "Retaining existing styles" and the all-important lead. Step by systematic step.

Tony (talk) 07:44, 26 December 2016 (UTC)

Thanks for taking the lead on this, Tony. I'll be happy to help with the calm approach you propose. Dicklyon (talk) 22:45, 26 December 2016 (UTC)

Sounds reasonable to me, as well.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  23:18, 27 December 2016 (UTC)

wp:TLDNR Though I tried. Not even certain what the issue is. Executive summary and a new section sounds good. Cinderella157 (talk

) 09:09, 28 December 2016 (UTC)

I appreciate this approach, as well. The most important thing, for me, is to see that some form of the above passage be reinstated. RGloucester — ☎ 16:07, 28 December 2016 (UTC)

I'm citing a webpage whose title is simply and exactly "2010-Present". When I cited that page using {{cite web}}, I used that just as presented. Another editor, referring to Wikipedia's standards for dashes, changed it to "2010–Present". Is there an SOP for making or not making such a change? — fourthords | =Λ= | 23:21, 20 December 2016 (UTC)

That's purely a style issue, and there is a guideline somewhere that says we should convert source's style to Wikipedia's style, or some such thing. I ran across it the other day but I doubt I could put my finger on it now. For example, we don't preserve a source's curly quotes/apostrophes but rather convert them to straight quotes/apostrophes, and we would generally convert "AN ALL CAPS NEWS ARTICLE TITLE" to "An All Caps News Article Title" or "An all caps news article title". ―Mandruss ☎ 20:43, 21 December 2016 (UTC)

You're thinking of WP:Manual_of_Style#Typographic_conformity. EEng 20:51, 21 December 2016 (UTC)

Agreed that is within the normal typographic conformity range, as it's just a style matter. Contrast this sharply with the similar question about changing "He" to "he" in direct quotations of religious scripture, which is not okay because it changes the meaning and intent of the material being quoted.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  23:33, 27 December 2016 (UTC)

That's exactly what I was looking for! Thanks, EEng! — fourthords | =Λ= | 22:27, 28 December 2016 (UTC)

Can

Regardless of what some list article may say, the Wikipedia:Manual_of_Style/Dates_and_numbers#Formats doesn't provide for a MMMMDDYYYY date format to be used in articles, and I don't see it used, for example, in Philippines or History_of_the_Philippines. EEng 06:04, 30 December 2016 (UTC)

• It's
  talk
  ) 14:36, 30 December 2016 (UTC)

PROPOSAL ACCEPTED

I had a read through this RfC and the previous one. I also sampled where people are using the template. The support for reducing the use of pull quotes is strong (most of the objections in the previous RfC seemed to be either procedural or wanting something stronger). In my quick survey of the quote template, pull quotes were a bit more common than I'd have expected from the discussion, but I don't think that's hugely relevant.

The only real issue IMO is one of quorum (numbers are small compared to the previous RfC). However, the primary objector to the last RfC did participate in this one and notices were placed on the relevant template talk pages (Ideally this would also have been mentioned at the TfD talk page and I personally would have preferred at the FAC page though I can see arguments against on that one). There may be some objection over this not being at TfD, but given the nature of the issue, MOS makes a lot more sense.

In any case, we seem to have a fairly clear consensus for this change and I think rejecting this proposal on the basis of no quorum would be overly bureaucratic, so the proposal is accepted. I will leave it to the relevant editors to make the proposed changes. Hobit (talk) 12:11, 25 December 2016 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Moved from archive for closing

The general proposal is: Shall we stop implying support for pull quotes in our documentation, yes or no. The specific proposal doesn't include text to flat-out forbid pull quotes, they are just no longer mentioned. Herostratus (talk) 17:27, 11 November 2016 (UTC)

Specifics, and examples

(A "pull quote" repeats text that is also in the main body of the article, typically in a box or highlighted in some other way, to emphasize it and/or for page layout enhancement. This RfC devolves from a long discussion, here, which indicated very little use of or support for pull quotes in the Wikipedia.)

The suggested specific edits are shown below. Deletions are showed as bolded struckthrough and additions or changes are shown underlined

Specific changes

1) At this MOS:BLOCKQUOTE as shown: Format a long quote (more than about 40 words or a few hundred characters, or consisting of more than one paragraph, regardless of length) as a block quotation, indented on both sides. Block quotations can be enclosed in the {{ pull quote}} a.k.a.{{cquote }} template, which are reserved for pull quotes). Block quotations using a colored background are also discouraged. 2) Move {{ Reduced pull quote}} to {{Rquote }} (these already exists as redirects; this is simply to remove any reference to pull quote from the template name). 3) {{ Pull quote/boilerplate}} is transcluded into the documentation for {{Quote box}}, {{Quote frame}}, {{Cquote}}, and {{Rquote }}. Rename this page and edit it as follows: This template should not be used for block quotations in article text. This template is meant for blockquote > element, for which that template provides a wrapper. Pull Quotes work best when used with short sentences, and at the start or end of a section, as a hint of or to help emphasize the section's content. * For typical pull quotes, especially those longer than the rest of the paragraph in which they are quoted, {{Cquote}} provides a borderless quote with decorative quotation marks, and {{Quote frame}} provided a bordered quote. Both span the article width. * For very short pull quotes, {{ WikiProject homepages. 4) Edit the "Usage" sections of {{Quote box}}, {{Quote frame}}, {{Cquote}}, and {{Rquote}} (which comes just below the above text) as appropriate to remove mentions of pull quotes. For instance, the edit for {{Cquote}} would be For actual pull quotes, this template provides a centered, borderless pull quote, with scalable decorative quotation marks... 5) If we've missed any other mentions of pull quotes in any documentation, remove those also. IMPORTANT NOTE: This leaves the following warning at the top of {{Quote box}}, {{Quote frame}}, {{Cquote}}, and {{Rquote}}: This template should not be used for block quotations in article text. Which leaves these templates with little function (technically, although editors may continue to use them in defiance of the warning template). This is intentional. Removing the template, which amounts to formally permitting the templates to be used for regular quotes, is a contentious question and will be part of a separate RfC down the line. Herostratus (talk) 17:27, 11 November 2016 (UTC)

Also, just FYI, here is an example of how pull quotes work and look

You don't need to read all this text. Just scan the page with the realization that all of the text in the little boxes repeats text found in the main body of the article. That is what pull quotes do. “ Pull quotes are a technique used by magazines as a layout device. ” Pull quotes are a technique used by magazines as a layout device. The make the page layout sportier and more inviting to the eye, or are supposed to. They also emphasize and highlight some passage. This may interest the reader (who may be just scanning through the magazine's pages) and draw her into the article. In the opinion of most – really, virtually all – editors, this is not really an appropriate device for an encyclopedia. We are not eyeball bait. We aren't paid by how many views our articles get. We have no need to or interest in drawing the reader into the article in this way. In fact, use of pull quotes would, in this writer's opinion, serve only to confuse the reader. [P]ull quotes are never used here – virtually never. This is why pull quotes are never used here – virtually never. Some editors claim they see them from time to time. I've been here eleven years and I've only seen one use of a pull quote, and that was because someone pointed one out to me in a discussion of pull quotes. So whether its "virtually never used" or "almost actually never used", they are very rare. “ [W]e aren't a top-down hierarchy and fail if we try to be, we can crowdsource format as well as content to arrive at best solutions, and it's better for morale to give editors as much creative control as is consistent with good layout. ” — Herostratus, This talk page At the same time, this writer is not an advocate of straitjacketing the editors. There are good reason for this – we aren't a top-down hierarchy and fail if we try to be, we can crowdsource format as well as content to arrive at best solutions, and it's better for morale to give editors as much creative control as is consistent with good layout. As a volunteer organization, morale is very important. At the same time, we aren't an anarchy. But in my experience our current rules can be used to make a bad layout – too many images, or conversely walls of text, and so forth – and these are best handled by correcting and educating editors on an article-by-article basis. I'm tired of talking about pull quotes. Herostratus, This talk page And, to be honest, I'm tired of talking about pull quotes. We don't use them, they don't help us in our mission. This really ought to be unanimously accepted RfC. We shouldn't even need an RfC, but an editor objected to the proposition, and so here we are; getting anything done here is like pulling teeth, it seems sometime. But OTOH, democracy. As you see all of the quotes above are pull quotes. If you like what I've done here you can vote against the proposal, I guess. As to the larger question of how strict we should be about whether or not a quote can have a box around it – which is not at issue in the RfC, but indirectly affects it – for my opinion I'll drop a real (non-pull) quote: Consistency is often overrated. — Ralph Spoilsport, Essays About Stuff That quote above was a real quote, not a pull, quote, just as an example of that. It's formatted with {{ Quote}}, which is basically HTML <blockquote>...</blockquote>, and is the only formally permitted way to show a quote in an article, although in real life editors use the boxed and big-quote templates above (which are supposed to only be used for pull quotes) for regular quotes. Herostratus (talk ) 16:09, 13 November 2016 (UTC)

Survey

• Support as proposer. Pull quotes are (virtually) never used in articles, and a good thing too: they are a format useful for magazine articles but no good for an encyclopedia, where they would only confuse. So this is just cleaning up artifacts; it's time and past time to stop having templates and documentation all over the place implying that pull quotes are used or useful. It's silly that RfC even has to be run on this question; this should be unanimously supported (Wikipedia talk:Manual of Style/Archive 184 shows zero support for pull quotes). Herostratus (talk) 18:04, 11 November 2016 (UTC)
• Support Not that I follow all the technical steps above, but if the effect is to simply remove all reference to "pull quotes" (which certainly do have a place – if limited – in articles) in template names and documentation, with the understanding that the generic concept of "quote boxes" is not being affected, that's fine with me. EEng 18:38, 11 November 2016 (UTC)

That's the intent, yes. Herostratus (talk) 16:02, 12 November 2016 (UTC)

• Support Are you saying that if pull quotes are not mentioned in template names and documentation, they will cease to be used? What about all the editors who already know how to format pull quotes? Some editors love to highlight a favorite quote like that, paying little attention to guidelines in the MOS. I still come across them. I suppose if they are not mentioned in template names and documentation, they will become less likely to be used.  – Corinne (talk) 18:54, 11 November 2016 (UTC)

This RfC is only against formally supporting pull quotes by inference (which is the current situation). If editors want to put in pull quotes (using an existing quote template or hand-writing the format) this RfC does not forbid them. I (the RfC initiator) am personally skeptical that pull quotes are ever useful, but I don't like to straitjacket other editors with absolute provisions; a little humility and a little leeway in telling editors how to design their pages, within reasonable limits, makes for a better project IMO. Also: in my eleven years here I've only seen pull quotes used once so I don't consider it an issue, and flat-out forbidding use of pull quotes is a side issue which would make this RfC more difficult to pass, which is a second reason I didn't propose it. Herostratus (talk) 16:00, 12 November 2016 (UTC)

• Oppose: ″Pulling″ is content reuse, which is much more favorable than duplication at any rate. Duplication leads to avoidable errors, multiplication of maintenance efforts etc.--*thing goes (talk) 17:22, 12 November 2016 (UTC)

Actually, I would support providing even better and more prominent means for excerpting and reusing parts (e.g. for "pulling").--*thing goes (talk) 17:30, 12 November 2016 (UTC)

I have no idea what you're saying. EEng 23:54, 12 November 2016 (UTC)

I also cannot make head nor tail of this. I've asked the editor to clarify. Herostratus (talk) 02:53, 13 November 2016 (UTC)

What I am trying to express is, that

1. referring to existing text as kind of quote ("pull-quote") is valid, as it is readily accessible, while cross-references are not so much: Ever tried reading through your car's manual? It is filled with references to look up. This has its justification in print for reducing the amount of pages required etc., but this limitation does not exist in the digital world of Wikipedia.
2. (more off-topic) editors should be given better tools to reuse content in and across pages without producing a textual duplicate, which has no connection to the original text.

I hope, that this made my points a little more clear.--*thing goes (talk) 11:04, 13 November 2016 (UTC)

In all seriousness, no. I still have no idea what you're trying to say. EEng 15:44, 13 November 2016 (UTC)

Same here. I've created a whole section, "FYI" (above). Look at that section. You are saying "Yes! This is what we ought be doing more of in our articles!", is that correct? Herostratus (talk) 16:17, 13 November 2016 (UTC)

• Support the first part, but the third is broken. MoS has already deprecated both pull quotes and abuse of pull quote templates (to over-emphasize block quotes) for years. Pull quotes are deprecated because its not an encyclopedic style, but a reader-browbeating journalistic style. Aggrandizing block quotations is deprecated because it runs afoul of
  WP:TFD has for years been moving us away from obscure template names like "rquote", this move would still remove "pull quote" from the wording, and it would also clarify what these templates are and suggest by inference why they are not used in mainspace but are kept for project and user space.

  The changes in #3 are not really necessary and kind of miss the point. The note about Rquote in it would, if changed as above, just introduce a new conflict with MoS by suggesting that short quotes (which MoS says to do inline, as do all style guides except when addressing pull quotes) be put in a decorative template. We do not want people using Rquote to format short quotations. The FAC crowd raised hell about this stuff a few months ago because several of them like to include documentary excerpts in sidebars. So, we should create a template for this purpose called something like {{Document excerpt sidebar}}, and sharply limit it, both in its documentation and in MoS, to be used for nothing but excerpts from cited sources. Not for quotation emphasis, not for pull quotes, and not for anything that is a WP:UNDUE problem, like giving excessive attention to primary sources that are dubious or one-sided. That should be enough of a compromise to get past this "our faction versus your faction" stuff that mired the last version of this discussion.  — SMcCandlish ☺ ☏ ¢

   ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  20:27, 18 November 2016 (UTC)

• Support per EENg - as long as this doesnt affect the use of quote boxes removing the wording regarding pull quotes is fine.·maunus · snunɐɯ· 22:15, 18 November 2016 (UTC)

Threaded discussion

One question is where this will leave {{Quote box}}, {{Quote frame}}, {{Cquote}}, and {{Rquote}}. Technically they wouldn't have any function anymore. But in real life 1) nobody has been using them for pull quotes anyway (since nobody uses pull quotes) and 2) some editors use them for regular quotes (in defiance of the documentation). This is all discussed in exhaustive detail at Wikipedia talk:Manual of Style/Archive 184.

My expectation is that, if this proposal is adopted, nothing about actual usage will change (people will continue to not use pull quotes, and some editors will continue to use {{Quote box}}, {{Quote frame}}, {{Cquote}}, and {{Rquote}} for regular quotes). Based on the discussion at Wikipedia talk:Manual of Style/Archive 184, there is some support for formally permitting {{Quote box}} (but maybe not the others) for regular quotes (by changing the documentation, e. g. by removing the "{{warning|This template should {{strong|not be used}} for block quotations in article text.}}" warning etc.). But of course a separate RfC would have to be run on that question. Herostratus (talk) 17:50, 11 November 2016 (UTC)

The MOS is supposed to document actual practice. If the MOS differs from what the editors do, then the MOS is wrong and will have to be changed. Hawkeye7 (talk) 04:18, 13 November 2016 (UTC)

Well I agree with you; many editors do, although editors editors favor a prescriptive MOS. In point of fact {{Quote box}}, {{Quote frame}}, {{Cquote}}, and {{Rquote}} are used for regular quotes in (what strikes me as) high numbers, considering that their documentation absolutely says not to do that; and they are almost literally never used for their putative function, pull quotes.

So yes, any editor that believes that the MOS should follow practice would definitely vote for this proposal, I would think. Down the road, and based on the earlier discussion (here), there ought to be an RfC on whether or either "legalize" the use of {{Quote box}} etc. for regular quotes, or abolish {{Quote box}} etc., or leave the situation nebulous. Herostratus (talk) 04:44, 13 November 2016 (UTC)

I'd like to notify editors who frequent

WT:FAC about this discussion, since I think it's a good idea to let editors who focus on content know about suggestions that can change the format of articles, but the last time I posted a note there at least one editor here considered it to be canvassing. Before I post a note there, can I get input on how to make sure those editors are aware of this discussion? SMcCandlish, you felt it was canvassing; what should I do? I'm happy to post to multiple areas to ensure a neutral notification if that's the best approach. I'd like opinions from others too; Herostratus

, anyone else?

Also, I'd like to make sure I understand the intent of this suggestion, as I'm not really a MoS aficionado. Pull quotes are quotes that are both in the article text and in a separate highlit quote box of some kind, and regular quotes are quotes that are not in the article text, and only appear in a separate box. What this proposes is to remove mention of pull quotes without changing what MoS says is permitted. Is that all correct? Mike Christie (talk - contribs - library) 11:53, 13 November 2016 (UTC)

That is correct. Your description of the difference between pull quotes and regular quotes is correct.

The intent here is simply to clear away an old cobweb, the support of (and therefore implicit suggestion for) pull quotes.

However, editors should be aware of this fact: in about 27,000 articles {{

quote}} or just raw <blockquote>...</blockquote>; thus about 18% of our quotes are formatted "illegally", which IMO is testimony to the high value that editors place on {{Quote box

}} etc.)

So while the intent here is just to clear away a cobweb, an effect will probably be to create a climate a little bit more favorable to more use of {{Quote box}}, {{Quote frame}}, {{Cquote}}, and {{Rquote}} for regular quotes -- in that the prescription "Use these only for pull quotes!" is removed. (Nowhere are they recommended for regular quotes (they are not mentioned here in the MOS at all), and the banner saying "This template should not be used for block quotations in article text" remains in the templates, for now, so the barrier to formally allowing these for regular quotes remains; a separate RfC will be required to discuss whether we want to remove that barrier.)

For this reason User:SMcCandlish will certainly oppose this proposal. He greatly loathes the idea of anyone ever putting a box around a quote, and will fight like the devil on all fronts and in all ways to for anything that makes that less likely. IMO you can't worry about that too much; he holds his beliefs very strongly, and it's just politics. One has to carry on and do what seems best despite politics. Herostratus (talk) 15:19, 13 November 2016 (UTC)

Thank you; that's clear, and I'll wait for SMcCandlish to comment. Do you have any advice on my first question above? Mike Christie (talk - contribs - library) 15:24, 13 November 2016 (UTC)

Well if I understand your question: I'm OK with this RfC being advertised as widely as possible in a neutral manner. Why not? I can't imagine any objection to that, save for political reasons as I mentioned.

But Featured Article solons might have little interest in the proposition, as the number of Featured Article candidate that have ever included a pull quote is certainly at or very near zero, so there's little practical effect on FA. On the other hand, since the effect is to indirectly somewhat lighten the proscription against using boxes (or big quote marks) around regular quotes, if a FA solon was of the mind that such an article could never pass FA, a word to that effect might be called for. Herostratus (talk) 17:45, 13 November 2016 (UTC)

I think "solon" is a little grand a title for FA writers! More to the point, there might be more pull quotes around than you realize. Take a look at Courtney Love, which I've just supported at FAC; the third quote box is a pull quote. I don't dislike pull quotes. I think they should be up to editor discretion; I've seen the arguments against them and there's some risk of inappropriate emphasis, but editorial discussion seems the right way to handle that, not a MoS prescription. I'll have to think about this RfC; my preference would be to move the MoS in the direction of less instruction in this case, so I'll probably end up supporting.

Do I also understand that there was never a close of the discussion under the heading "Permit Template:Quote box for regular quotes" that SMcCandlish and a couple of others objected to as being a hijacking of the RfC? I don't see any sign of a close in archive 184; what happened? Mike Christie (talk - contribs - library) 20:47, 13 November 2016 (UTC)

I do dislike pull quotes, but I'm with you: I think they should be up to editor discretion (and discussion). Note that this proposal, while it (purposely) doesn't ban pull quotes, does end all documentation support for them. This I think will have the net effect of "burying them deeper in the toolbox" -- editors will have to extrapolate from examples, or just use their own judgement, in figuring out whether and how to use pull quotes. This is not necessarily a bad thing, as you say, but it might be.

The Wikipedia talk:Manual of Style/Archive 184 discussion, that was intended to be a true "discussion" with no close, just a chance to talk about various issues and maybe come up with some action items for future RfC; this RfC is the first fruit of that.

Within that RfC an editor created a vote-yes-or-no subsection on a sub-issue (it is "Permit Template:Quote box for regular quotes", here. This is pretty unusual for an RfC, and maybe for that reason it was never closed (despite a request at

quote}} you can put a line around the quote with {{quote box}}". That's a contentious separate question from this RfC, and is another action item to come out of the Archive 184 discussion, and I intend to run a separate RfC on that question presently. Herostratus (talk

) 22:09, 13 November 2016 (UTC)

The politicized canvassing was probably why it was archived without closure. No sane admin would have touched that, since any result other maybe "no consensus" would have produced another wave of side-taking and accusations. It's best to just leave it for a considerable time until tempers cool.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  20:05, 18 November 2016 (UTC)

@Herostratus: stop putting words in my mouth and casting aspersions about my mental processes, which you clearly do not understand and badly mischaracterize.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  20:07, 18 November 2016 (UTC)

Well, this RfC is still active, and though I can see why you suggest the issue be left to cool for a while, we have to deal with the RfC in front of us. Are you saying we should agree to stop the RfC without prejudice to restarting it or something similar later? I don't think that's likely. And though I didn't feel there was politicized canvassing last time, I understand that you did think that, and I want to avoid that this time -- so what is an appropriate method to notify others of this RfC? Mike Christie (talk - contribs - library) 20:15, 18 November 2016 (UTC)

Just let it run. People who care about this will already notify their "camps" one way or another, and far more importantly

WP:FRS exists for a reason: it will bring in fresh eyes and minds that are not already dug into trenches.  — SMcCandlish ☺ ☏ ¢

 ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  20:29, 18 November 2016 (UTC)

So in your eyes there is simply no way to evenhandedly notify any other groups of the existence of this RfC? I understand the concern about canvassing, but I would like to post a neutrally worded note to a group I think may be interested. (And in this case, unlike the previous one, I hope you find it easier to believe that I'm really not canvassing for or expecting a particular position; I haven't even made my own mind up as to which way I want to !vote.) The strictures against canvassing are against soliciting !votes for one side or another; surely there's an acceptable way to neutrally notify others who might be interested? Mike Christie (talk - contribs - library) 20:47, 18 November 2016 (UTC)

I took this to your talk page, but the short version is there is no reason to do this (people who care will show up anyway), and it is only likely to have a polarizing and factionalizing effect again, exactly as it did last time. "The definition of insanity is doing the same thing over and over and expecting different results." <;-) (Variously attributed to Albert Einstein, Benjamin Franklin, and Fred Zamberletti, among others.) Quotation formatting is not an intrinsically FA-related subject, so it would be taken as canvassing of a special interest group regardless, by various participants.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  21:16, 18 November 2016 (UTC)

I'm going to post a query at

WP:VPM since I think your preference for not posting notices is not the same as the requirement not to canvas, and I'd like to get other opinions. Mike Christie (talk - contribs - library

) 13:12, 19 November 2016 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

• I've been trying to think of a suitable chump patsy fall guy editor of sufficient esteem and stature to actually implement this. I've hit on it: The Blade of the Northern Lights. EEng 02:24, 31 December 2016 (UTC)