Wikipedia talk:Manual of Style

Measures in support of MOS:CURLY

I was surprised to find in an audit of my recent edits and a sampling of random pages that approximately 15% of articles contain one or more curly quotes or apostrophes. There have been previous discussions (2005, more 2005, 2010, 2016) on the problems with curlies. While promoting curlies has always been rejected I'd like to know how much support there is for MOS:CURLY in discouraging use of curlies or even a partial purge of curlies from mainspace.

Full disclosure: I use dial-up, 20 year old hardware and occasionally use a text-based web-browser. Just to say that editors like myself exist as an active part of the Wikipedia community. Also, I've been doing a lot of apostrophe-related typo fixes.

I would appreciate input on the following approaches:

1. To have a bot convert curly apostrophes and quotes to straight apostrophes and quotes in the mainspace. (It would have to exclude articles belonging to categories like Category:Punctuation where curlies should be preserved, and exclude cases with adjacent apostrophes to avoid italic and bold issues.)
2. To have a bot check recent edits for curlies and, when found, leave a message on the editor's talk page (similar to DPL bot when an editor links to a disambiguation page) alerting them to MOS:CURLY issues and linking to a page with instructions for turning off curlies in popular software packages. (Would have to take measures against spamming.)

Like most, I didn't think that curlies were too big of a problem. However, it could be pervasive, effecting some 700k articles. And it wouldn't hurt to inform the small minority of editors introducing curlies into articles. If it's agreed that there are problems with curlies, why not fix it? I'd appreciate your thoughts. - Reidgreg (talk) 17:22, 26 September 2016 (UTC)

Please, not another bot gnoming about. If this isn't already something AWB raises an alert on, that might be a good idea. EEng 19:03, 26 September 2016 (UTC)

Just to point out the "why" of curliest in the present, it's a combination of lazy copy-and-paste of quotes from websites, and/or editing in a word processor and then copying over to the Wikipedia editing window. In both cases, it's just some careless editing and can easily be done as part of routine gnomish edits. Is it more pervasive that we'd like, sure, but I don't think a bot just for that task is needed. oknazevad (talk) 22:04, 26 September 2016 (UTC)

But who wants somebody constantly looking for curly quotes in articles? Philroc^{My contribs} 13:10, 7 October 2016 (UTC)

The editor says "15% of articles contain one or more curly quotes or apostrophes" which seems pretty high to me. Some (unknown) number of articles must contain no quotation marks, so of articles which contain quotation marks, curlies must appear in over 15%. However, yeah, it's not a big deal; I fix them when I see them (and feel like it) but I don't know if its worth worrying about. And, one small advantage of curlies is they signal a possible copy-paste job which alerts me to look for possible copvio. Herostratus (talk) 22:13, 26 September 2016 (UTC)

Thanks for the replies. The percentage did seem high (15.6% of 500 edits and 14% of 50 random articles)), which led me to believe that AWB editors aren't keeping up. Thus the two-pronged approach to clear the backlog and inform lazy careless unaware editors. Copyvio trumps the curly issues, if they can be used as an indicator, though I imagine (or hope) you get a lot of false-positives that way. - Reidgreg (talk) 16:29, 27 September 2016 (UTC)

I don't think that curly quotes are part of AWB's general cleanup. Mr Stephen (talk) 18:01, 27 September 2016 (UTC)

A somewhat related issue I came across today is AWB, as a part of general clean-up, changing ″ and ′ to ″ and ′ respectively. Since these are hard to distinguish from quotation marks visually (curly or straight, depending on the font) I wonder if AWB should be allowed to do this. Jc3s5h (talk) 17:09, 27 September 2016 (UTC)

I've noticed a correlation between curly quotes and copyvios, so it may not be entirely helpful just to "correct" them blindly. --Mirokado (talk) 18:14, 27 September 2016 (UTC)

Agreed. A large percentage of them are due to copy-pastes from other sources. Only a minority are due to people using external editors that auto-curlyize the quotes.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  10:01, 30 September 2016 (UTC)

::I agree too. What should we make the bot do about a possible copyvio? Philroc^{My contribs} 13:20, 7 October 2016 (UTC) Actually, I agree with @Reidgreg: on the fact that if we use curlies as a copyvio indicator, there will be a lot of false positives. Philroc^{My contribs} 13:25, 7 October 2016 (UTC)

Above: Just to point out the "why" of curliest in the present, it's a combination of lazy copy-and-paste of quotes from websites, and/or editing in a word processor and then copying over to the Wikipedia editing window. / Above: Only a minority are due to people using external editors that auto-curlyize the quotes. Sometimes it's none of these. One article I often edit has had curly quotes since its start. I carefully curlify my quotes when I add them. This change from normal practice amuses me. As far as I know, nobody has objected to either the abundance of curly quotes in that article or to my addition of them. I've never thought either that I ought to decurl the quotes there or that I should curl the quotes elsewhere. Perhaps it would have been better if Mediawiki had provided a preprocessor for the (X)HTML Q tag; it doesn't, and this really doesn't matter, compared with (for example) the endemic PR work that infects articles with "prestigious", "legendary", and similar bullshit. -- Hoary (talk) 00:12, 3 October 2016 (UTC)

Ohconfucius's scripts, which I run, zap the curlies. I think 15% is a conservative estimate. Tony (talk) 00:31, 3 October 2016 (UTC)

If you'd like to zap the curlies within my article, be my guest. But really, why should people bother with this when their intellects are easily up to the removal of "iconic", "is recognized [by whom?] as", and suchlike twaddle? -- Hoary (talk) 01:09, 3 October 2016 (UTC)

@Hoary: Having MediaWiki, or at least en.wp's own site-side CSS and Javascript, do something intelligent with <q>...</q> has been added to my to-do list. I think it would be desirable for numerous reasons to markup up inline quotation with this element and to allow people who insist on curly quotes in their output get them. However, this won't do anything for non-quotation uses of quotation marks, e.g. "scare quotes", song titles, etc.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  07:32, 3 October 2016 (UTC)

@Reidgreg: @EEng: @Herostratus: @Oknazevad: @Mr Stephen: @Jc3s5h: @Mirokado: @SMcCandlish: @Hoary: @Tony1: Hey, maybe we could make the bot put in this template that I made that tells people that there are curlies that need to be replaced, but also says that curlies are an indicator of a possible copyvio, and that the article needs to be checked as well. Philroc^{My contribs} 14:29, 7 October 2016 (UTC)

The template looks good though I'd be concerned about putting it on, potentially, 1 in 6 articles. It seems to me that a particularly clever bot could look for curlified text, google it, and then put up {{copypaste}} or a custom template with its results, though this could generate false-positives from sites that mirror wikipedia. I'll try to investigate more as I'm able. I don't suppose if anyone reading this knows whether there are bots looking for copypaste edits? - Reidgreg (talk) 20:26, 15 October 2016 (UTC)

@Reidgreg: Wow, it took you a long time to respond. Now I think we should make the bot remove the curlies, and then make it put in some sort of template about curlies being an indicator of a copyvio. But what template? Philroc^{My contribs} 13:06, 17 October 2016 (UTC)

No. Use a category or something. We've got enough shrill templates no one heeds. EEng 13:36, 17 October 2016 (UTC)

@Reidgreg: @EEng: How about a template AND a category? Philroc^{My contribs} 16:01, 17 October 2016 (UTC)

@Reidgreg: @EEng: Wait, maybe we could add a parameter to Copypaste for the bot. It would change the template to say that the bot removed curlies, and then say that the curlies were an indicator that what the template says already might've happened. Philroc^{My contribs} 16:34, 17 October 2016 (UTC)

I strongly agree with EEng that a hidden maintenance category should be used instead of a loud template at the top of the article. Given that there are 42,000 articles with prominent templates at the top of unreferenced articles in Category:Articles lacking sources from December 2009, and they have been there for seven years, putting a template at the top of articles with curly quotes is extreme overkill.

Anecdotally, I clean up curly quotes where I see them, and it is rare that I see evidence of copyvio. Do we have evidence for that assertion, made above? I find that they are often scattered through the article without a pattern, or copied into citations from titles of articles on the web. I recommend that we first stop the bleeding by working with the writers of automated tools like reFill, which used to copy curly quotes unmodified into citations (and has since been fixed). – Jonesey95 (talk) 15:51, 19 October 2016 (UTC)

The "evidence" is other editors' good-faith statement that they keep finding copyvios this way. I'm one of them. It is okay that your personal experience differs from that of others. It just means your editing doesn't overlap much.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  09:07, 23 October 2016 (UTC)

As an aside, don't forget that (if you are going to start this) there are several other glyphs that should usually be replaced. We have, in no particular order but starting with the commonest

• ’ right single quotation mark
• ‘ left single quotation mark
• “left double quotation mark
• „ right double quotation mark
• ` grave accent
• ´ acute accent
• ‛ single high-reversed-9 quotation mark
• ′ modifier letter prime
• ‚ single low-9 quotation mark
• ‟ double high-reversed-9 quotation mark
• ″ modifier letter double prime
• „ double low-9 quotation mark

plus at least two Arabic glyphs that look very similar, and the guillemots. Some of these come in from cut-and-paste, but some are added at the keyboard. The primes also have a valid (in the MOS sense) use, of course. Mr Stephen (talk) 22:07, 17 October 2016 (UTC)

@Mr Stephen: I can't really start this until it's clear what the bot is going to do if it finds one of these glyphs. Is there anything that you think the bot should do? Philroc^{My contribs} 22:49, 17 October 2016 (UTC)

Actually, I know what the bot will do if it finds one of those glyphs. It will put in {{Copypaste}} with a parameter which changes the notice to talk about how the bot found curlies and changed them, and it also will say that curlies are the sign that what the template says happened. See its sandbox and its testcases. Also, @Reidgreg:, can you give us a better statistic of how many articles have curlies? When I do a BRFA, I'll need to say how many articles are affected. Philroc^{My contribs} 12:29, 19 October 2016 (UTC)

Sorry, Philroc, for some reason I got a notification from your last ping to me but not the several preceding it. (Drop a note on my talk page if my account is active but I'm not responding.) I was also considering a maintenance category but decided to shelve it until I could investigate more and develop a better proposal. There's no point if this doesn't ultimately make it easier for human editors. I found curlies in 15.6% of 500 edits and 14% of 50 random articles. When I have time I'm hoping to get a bot to investigate a larger random sample and generate some data that I could then follow-up with manual implementation of a fix, and see how it works over time. There has been a bot request on this subject which I added to while opening this discussion - and I'm glad I did, as this is much more complex than I'd first thought. I want to be responsible to the community's concerns, and some significant issues need to be addressed. Discussion of technical implementation might be a conversation for the bot request page or elsewhere, though. I don't want to take up any more time from the busy people here who have already patiently explained their concerns. - Reidgreg (talk) 13:34, 19 October 2016 (UTC)

You don't need a bigger sample. The data you have so far tells us that about 14% of articles have curlies, give or take about 5% or so. I think that tells you what you need to know. EEng 14:24, 19 October 2016 (UTC)

@EEng: That's the problem. I have to get a margin of error less than 5% if I want the BRFA for this to get accepted. Philroc^{My contribs} 15:47, 19 October 2016 (UTC)

I didn't realize you were working against an imposed standard. Sounds like you know how to do these calculations, but in case you don't, if you add 50 more to your sample then the give-or-take figure will be at most exactly 5%, and almost certainly far, far smaller. Just for my curiosity, how do you draw the sample? EEng 17:16, 19 October 2016 (UTC)

@EEng: It's not a standard. In fact, there was no standard in the first place. I just don't want a wildly inaccurate value.

By the way, I'm not the one who made the value, Reidgreg did. Philroc^{My contribs} 17:32, 19 October 2016 (UTC)

You know what, I'll just take the value as it is. Philroc^{My contribs} 17:37, 19 October 2016 (UTC)

• I'd still be interested to know how the sample is drawn -- where did you get the 50 random articles from? EEng 17:44, 19 October 2016 (UTC)

@EEng: As I told you earlier, I wasn't the one who got that value. Reidgreg did that. Anyway, from that percent, I have been able to estimate that about 740,000 articles on all of Wikipedia are affected by curlies. Philroc^{My contribs} 19:40, 19 October 2016 (UTC)

For what it's worth, an insource search shows 14,000 articles with one of the four basic curly quote marks in article space. Insource searches do not always work well, though (and this seems way too low based on my experience), so someone should run a search on a database dump if we want data we can trust. If the true count really is 14,000, a supervised bot run should be able to handle it nicely. – Jonesey95 (talk) 19:48, 19 October 2016 (UTC)

Well, there's a teensy discrepancy between your 14,000 figure and the earlier estimate of 14%*5,000,000=700,000. EEng 20:12, 19 October 2016 (UTC)

@EEng: Yeah. Downloading the latest database dump (it's from October 3rd) to Dropbox right now. It should take maybe 6 hours to get my number. Philroc^{My contribs} 21:00, 19 October 2016 (UTC)

I make it about 15% (316 in 2000 random pages). Mr Stephen (talk) 22:33, 19 October 2016 (UTC)

Well, now I'm estimating 740,000 - 830,000 articles affected by curlies even though the insource search says about 14,000. I decided to not use the database dump since it would take too long. So which source should we trust? Philroc^{My contribs} 00:24, 20 October 2016 (UTC)

Well, if someone would please tell me how the 2000 articles were selected, we could use that figure, but I'm not hearing any answer. EEng 00:32, 20 October 2016 (UTC)

• Again just for my interest, how are you drawing these random 2000 pages? EEng 23:46, 19 October 2016 (UTC)

AWB's 'random pages' option. Regards, Mr Stephen (talk) 07:54, 20 October 2016 (UTC)

@EEng: Try pinging people like how I'm pinging you instead of just asking a question. Philroc^{My contribs} 01:56, 20 October 2016 (UTC)

@EEng: Now you have your information. So which source should we trust, my estimate from AWB or an insource search? Philroc^{My contribs} 12:26, 20 October 2016 (UTC)

Well, I've posted a query at mw:Help_talk:Random_page to see if "random" really means random, but on the assumption that's really true, then based on the 316/2000 sample mentioned, the true proportion is about 16%, give or take about 1% or so i.e. 16%*5,300,000 = 850,000 articles +/- 50,000. (I'm not sure if that was based on just double-quote curlies, or the larger list of curlies Mr. Stephen gives above.) EEng 18:27, 20 October 2016 (UTC)

@EEng: But what about the insource search? Philroc^{My contribs} 18:48, 20 October 2016 (UTC)

@EEng: I think we should just go with the insource search because it actually looks at articles, but what do you think?

I'm note sure how I became the arbiter of this, but anyway... At this point, we don't know the technical details of the operation of insource search, and we don't know the technical details of the operation of the random page function, but if I had to choose I'd believe the random sample. Search machinery often has hidden mysteries (doesn't recognize the search string in certain contexts, limits the size of the result set, ...) but even if there's something hinky to the random sample (skewed toward newer articles, skewed toward popular articles, ...) it's very hard to see how any of that would be hugely correlated with presence of curies.

On the other hand, I have to say that 16% seems awful high. Mr Stephen, did you personally examine the 316 you thought had curlies?

Oh, wait... Mr Stephen, were you looking for your full list of curlies? That might explain the difference in results, since the insource search was only looking for the four basic curlies. I wonder if Mr Stephen's list includes something which is legitimately used in a lot of articles. You'd better go back to your 316 and see exactly what character was being used, and how. EEng 19:49, 20 October 2016 (UTC)

@EEng: Speaking of your query about the random article feature really being random, I found your answer. Here! Philroc^{My contribs} 21:21, 20 October 2016 (UTC)

OK, then, despite the (very surprising) oddities mentioned there, that tells us that the random feature is fine for our purposes, which leads me to want to believe the 316/2000 result which I analyze above. However, I still won't be fully comfortable until I hear from Mr Stephen about whether he was searching his whole long list of curlies, and what can be gleaned from looking at the actual hits to see what characters are being found and how they're used. To repeat, I suspect that one of those characters has some technical use we're not thinking of. That would have implications both for the estimate of # of articles affected, and for the design of the bot. EEng 22:58, 20 October 2016 (UTC)

Let me ask him for you. @Mr Stephen:, EEng wants to know if you used your whole list of curlies to make the article count. Philroc^{My contribs} 23:03, 20 October 2016 (UTC)

@EEng: BUT WAIT. It's 12:09 am where Stephen lives, so he isn't up all night to answers your questions. Philroc^{My contribs} 23:10, 20 October 2016 (UTC)

BUT WAIT... Between us we've pinged him three times, so let's just have a nice break until he gets back to us. EEng 23:19, 20 October 2016 (UTC)

OK. Philroc^{My contribs} 23:36, 20 October 2016 (UTC)

OK, got that. I will not be at my PC until later today. I will have a look. Yes, I used the longer list but in my experience the great majority of curly quote s are the ordinary ones. Mr Stephen (talk) 10:00, 21 October 2016 (UTC)

I've decided to download the database dump, except on a 1TB hard drive. I'll get back to you later after I search for curlies. Philroc^{My contribs} 21:49, 21 October 2016 (UTC)

Here we go then, 25 in 200 pages, so 12.5%. Of those 25, Olia Lialina, Amer Fort and Warren Sonbert used unusual quotes, the rest looked like ordinary curlys to me. Mr Stephen (talk) 22:24, 21 October 2016 (UTC)

• diff: Olia Lialina: clean up, straight quotes,see WT:MOS using AWB
• diff: Warren Sonbert: clean up, straight quotes,see WT:MOS using AWB
• diff: Amer Fort: /* Early history */clean up, straight quotes,see WT:MOS using AWB

• diff: Stanwick, Northamptonshire: clean up, straight quotes,see WT:MOS using AWB
• diff: Edward J. Bles: clean up, straight quotes,see WT:MOS using AWB
• diff: Karl Ludwig d'Elsa: clean up, straight quotes,see WT:MOS using AWB
• diff: The Sims 3: Showtime: clean up, straight quotes,see WT:MOS, typo(s) fixed: carrers → careers using AWB
• diff: Broquiès: /* The seigneurs of Broquiès */clean up, straight quotes,see WT:MOS using AWB
• diff: LSU Communication across the Curriculum: clean up, straight quotes,see WT:MOS, added orphan, underlinked tags using AWB
• diff: Adelaide Hasse: clean up, straight quotes,see WT:MOS using AWB
• diff: Mike McCready: clean up, straight quotes,see WT:MOS, typo(s) fixed: tv → TV using AWB
• diff: John Shepherd (scientist): clean up, straight quotes,see WT:MOS using AWB
• diff: 1962–63 Duke Blue Devils men's basketball team: clean up, straight quotes,see WT:MOS using AWB
• diff: Foster's School: clean up, straight quotes,see WT:MOS using AWB
• diff: Max du Preez: /* Awards */clean up, straight quotes,see WT:MOS using AWB
• diff: Information search process: clean up, straight quotes,see WT:MOS using AWB
• diff: Cair Paravel-Latin School: clean up, straight quotes,see WT:MOS using AWB
• diff: Averruncus: /* top */clean up, straight quotes,see WT:MOS using AWB
• diff: Hitchin: clean up, straight quotes,see WT:MOS using AWB
• diff: Ethnic cleansing in the Bosnian War: clean up, straight quotes,see WT:MOS using AWB

• diff: 2012 Munster Senior Football Championship: clean up, straight quotes,see WT:MOS using AWB
• diff: Phil Brown (footballer, born 1959): /* Preston North End */clean up, straight quotes,see WT:MOS using AWB
• diff: 2013 Bengali blog blackout: /* top */clean up, straight quotes,see WT:MOS using AWB
• diff: Contentment: clean up, straight quotes,see WT:MOS using AWB
• diff: George Lefroy: clean up, straight quotes,see WT:MOS using AWB

Why is this percentage so wildly inconsistent anyway? Philroc^{My contribs} 23:54, 21 October 2016 (UTC)

If what you're saying is that the 316/2000 = 16% and the 25/200 = 12.5% are inconsistent, they're not, because the small sample of 200 has a give-or-take figure of 2.3% "or so", meaning it wouldn't be surprising if it were twice that i.e. 4.6%. And 12.5% + 2*2.3% takes you to 16% and beyond. I conclude that the sample of 2000's estimate of 16% +/- 1% is reliable, and I suspect that there's something hinky about the count returned by the insource search. (All of this, of course, relies on others' actual examination of individual articles for curlies, which I have to take on faith.) EEng 05:14, 22 October 2016 (UTC)

• On the basis of my extensive gnoming, 15% is very believable. The script I use cleans it up. But that's separate to the issue of whether MOS should prescribe curly or straight glyphs. I recall very strong reasons for the rule to use straight. Does anyone have a link to that discussion, which was years ago? Tony (talk) 06:20, 22 October 2016 (UTC)

  Well, you were involved in the discussion back in 2007, but debate goes back to 2005 and 2006. Hawkeye7 (talk) 06:52, 22 October 2016 (UTC)

EEng, if you go back about 9 paragraphs from the top, I started with an audit of 500 edits from my contributions. (I was working on apostrophe-related typos at the time, so I personally checked those). I understand that sample was not totally random (all articles had an obscure typo), so I checked 50 random articles from "Special:Random". I don't know the algorithm, either, but I got consistent results so I felt 15% (or even more roughly, 1/6th) was a good enough figure for discussion. What I wanted from a larger sampling was not to confirm this number, but to generate a list with other fields, personally check for copypaste, and look for any other correlations that might be used as indicators (and possibly also generate a list of editors making the copypaste violations). But before going there I wanted to check with some WikiProjects for issues I may not have anticipated. Tony1, if you look at the first paragraph of this discussion, I linked to four sections of this talk page's archives discussing straight and curly quotes. - Reidgreg (talk) 19:08, 24 October 2016 (UTC)

I reviewed the 25 edits listed above. (I'm not very good at this, still learning how to use the copyvio tools.) I found 3 cases that look like copyvio: Cair Paravel-Latin School appears to be copied from the school's website, and has had copyvio problems in the past; The Sims 3: Showtime has text matching a gaming site, difficult to tell if it's a copypaste or a backwards copy; and Contentment attributes a source but does not indicate a direct quotation. As for typography, in 7 cases the curlies should have been wikified instead of straightened. (For example, in Stanwick, Northamptonshire I believe some of the curly single quotes should have been changed to double quotes and others to italic markup.) I was hoping to treat the disease rather than the symptom, as it were, but curlies are indicators of a lot of different problems, many of these articles having multiple issues. Curlies seem to be an indicator of general unfamiliarity with Wikipedia practices. - Reidgreg (talk) 14:47, 27 October 2016 (UTC)

• I think somebody should search a database dump so we can settle this count problem. Does anybody want to do that? Philroc^{My contribs} 14:59, 3 November 2016 (UTC)
• You know what, screw it. I'll just say 660,000 - 830,000 pages affected on the BRFA. Let's get to getting consensus for this bot (finally). So, does anybody want a bot which looks for curlies, then puts in Copypaste with a change explanation which mentions the bot? Philroc^{My contribs} 15:08, 8 November 2016 (UTC)

Proposal

Create a Bot to automate the looking for and copypaste change of the curlies listed above (right single quotation mark, left single quotation mark, left double quotation mark, right double quotation mark, etc.) following the guideline MOS:CURLY.

• Support as proposer. LK (talk) 02:54, 10 November 2016 (UTC)
• Comment @Lawrencekhoo: Will the bot put the variant of {{Copypaste}} (Template:Copypaste/sandbox) on affected pages? Philroc^{My contribs} 13:25, 11 November 2016 (UTC)

Pronunciations for Latin taxon names

As most biologists will tell you, there is no "correct" pronunciation for Latin taxon names since there is no standardized pronunciation for New Latin. As our article on New Latin states: "New Latin had no single pronunciation, but a host of local variants or dialects, all distinct both from each other and from the historical pronunciation of Latin at the time of the Roman Republic and Roman Empire." Nevertheless, some people still add IPA pronunciations for taxons or {{pronunciation needed}} tags.[1] This is misleading, however, as it implies that there is a "correct" pronunciation. To quote a couple sources:

• "Latin is now a seldom-spoken language, and we do not know precisely how it was spoken in the Roman world. Many scientific names are words that were not a part of ancient Latin and would sound as foreign to the Romans as Latin does to us. Many English-speaking botanists pronounce Latin names as if the words were written in English. This is known as the Traditional English system. There are many variations and these are often passed on from teacher to student… On the other hand, most classicists and many European botanists prefer Reformed Academic Latin in which strict rules govern the pronunciation of particular letters or combinations of letters… Although there is no consensus among botanists of the world regarding the pronunciation of vowel sounds, there are some general guidelines…" — Vascular Plant Taxonomy
• "These rules cannot satisfactorily be applied to all generic names and specific epithets commemorating persons. About 80 per cent of generic names and 30 per cent of specific epithets come from languages other than Latin and Greek. A simple and consistent method of pronouncing them does not exist… Botanical Latin is essentially a written language, but the scientific names of plants often occur in speech. How they are pronounced really matters little provided they sound pleasant and are understood by all concerned." — Botanical Latin: History, grammar, syntax, terminology and vocabulary

With this in mind, I would like to propose adding the following sentence to the Animals, plants, and other organisms section:

Do not include pronunciations for Latin names, as there is no standardized pronunciation for New Latin.

Any thoughts on this? Kaldari (talk) 05:03, 24 October 2016 (UTC)

Oppose Not sure if that's right. Where there's a long name in wide popular use that people find hard to pronounce – as in dinosaurs and some garden flowers – it seems sensible and encyclopedic to inform readers of the most common pronunciations. After all, there's no standardized pronunciation for anything (try "either", "controversy", ...). Chiswick Chap (talk) 08:13, 24 October 2016 (UTC)

Oppose While it might not be common knowledge among biologists, few people are experts in multiple fields, and palaeolinguists have done substantial reconstruction work to discover how Latin was spoken in Roman times. Rhialto (talk) 08:36, 24 October 2016 (UTC)

That's irrelevant, though: taxon names are not in classical Latin; they often feature letters and consonant clusters wholly or virtually unused in classical Latin. AlexTiefling (talk) 08:59, 24 October 2016 (UTC)

The counterpoint to that is that if we are saying these are not classical Latin (or even 'New Latin') but simply modern pronunciations, then pronunciation guides can still be provided on wikipedia using a descriptive approach of examining what is the actual common pronunciation in use. Rhialto (talk) 09:46, 24 October 2016 (UTC)

I don't disagree - I'm simply saying that while I strongly endorse the use of reconstructed classical pronunciation for classical Latin, it can't be relied upon for New Latin, which has its own contexts and standards, not all of which are fully codified or necessarily compatible with each other. Taxonomy is a good example of this - I wouldn't expect taxonomic Latin to be pronounced particularly similarly to, say, the Latin text of papal letters. So there almost certainly are norms of pronunciation, but classical models are no particular guide as to what they might be. AlexTiefling (talk) 10:09, 24 October 2016 (UTC)

Alan's point is entirely correct. There's essentially no connection at all between reconstructed pronunciation of historical Latin, and scientific circles' often conflicting pronunciations of names in ISV ("New Latin" is a misnomer, as ISV terms are often Greek- not Latin-based, or a mishmash). The liturgical Latin of the Roman Catholic Church has of course has some influence on ISV pronunciations, but they're still diverging rapidly.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  03:28, 27 October 2016 (UTC)

"New Latin" is not exactly a misnomer, since although the sources of scientific names for organisms may be Greek, the names have to conform to some degree of Latin morphology – more so in the case of botanical Latin than zoological Latin, it's true. Peter coxhead (talk) 09:30, 27 October 2016 (UTC)

• Comment I agree with Chiswick Chap that in some cases it is both sensible and encyclopedic to inform readers of the most common pronunciations – with the stress on the plural. The problem is that there are many pronunciations of the Latin names of taxa – a discussion of how the ending of plant family names, -aceae, is pronounced came up with four or five commonly used variants, which differ both between and within English-speaking countries. So a properly neutral presentation might have to list what seems to me to be too many alternatives. So although I don't favour a "ban", I don't think we should encourage the addition of pronunciations of scientific names. Peter coxhead (talk) 12:36, 24 October 2016 (UTC)
• Comment - I have to agree with comments above, that although a ban seems excessive, opening cans of worms is also not an attractive prospect. There is some discussion of pronunciation at Botanical Latin, with scholarly source. New Latin is not the best reference for how taxon names are pronounced. Botanical Latin, as has been pointed out above, has some peculiarities, particularly in the naming of taxa. If any pronunciations are to be added, I would like to see sources, but I doubt that there are many good sources, and know that there are some that I would not wish to emulate, since they reflect the peculiarities of exactly one author. Sminthopsis84 (talk) 23:34, 24 October 2016 (UTC)
• Oppose Bottom line is people will naturally want to know how to pronounce (or one way of pronouncing) a name. If editors of a given article can figure out a way of doing that selecting a usable pronunciation from available sources, let them. EEng 00:00, 25 October 2016 (UTC)

If editors of a given article can figure out a way of doing that, let them – no, there needs to be a source for each and every pronunciation; it's not for editors to generate pronunciations. Peter coxhead (talk) 07:51, 25 October 2016 (UTC)

I've modified my comment to avoid the potential misreading that I meant editors would devise the pronunciations themselves. EEng 08:33, 25 October 2016 (UTC)

• Oppose. While there may be no one true way to pronounce such terms, we can still provide the most common one (or ones, where several variants are frequent), as most dictionaries and other such works already do.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  03:28, 27 October 2016 (UTC)

Provided that an appropriate range of dictionaries are consulted, fine, but what I often see is one dictionary based on one ENGVAR used to add one pronunciation that is not in widespread use, which is not helpful. Peter coxhead (talk) 09:33, 27 October 2016 (UTC)

@Peter coxhead: Isn't that already covered by WP:UNDUE? Wondering what MoS is supposed to say that wouldn't be redundant. Serious question: Is it a problem that editors are trying to prevent the later inclusion of additional, also reliably sourced, pronunciations that are more or equally common? Or is it just that some obscure articles have only minority pronunciations in them, for a while, until someone notices? As for the thread as a whole, I don't like the "let's suppress verifiable information" approach taken by the proposal, though I understand that's probably not the conscious thought behind it, nor your idea; I just see it as a not-well-thought-out solution to what looks like an illusory problem. That said, in editing biology-related articles (especially domestic animal breeds) I've encountered information inclusion resistance that is senseless and would be surprising to anyone who hadn't seen it with their own eyes, so that's why I'm asking the question I asked. :-)  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  11:47, 3 November 2016 (UTC)

@SMcCandlish: I don't think the MOS needs to say anything, one way or the other. I'm all in favour of properly sourced pronunciations being included if it can be done in a way that is sourced, accurate and avoids favouring one ENGVAR over another. I've tried to do it myself for the Latin names of plants that are well-known to non-specialists. The problem I find is that it's mostly older sources that give pronunciations, including some very old and out-of-copyright sources that have been digitized; a lot of modern botanical and horticultural works seem to have given up. So properly sourced pronunciations often aren't the ones I hear people using now, because they are more based on classical Latin. Peter coxhead (talk) 12:13, 3 November 2016 (UTC)

Ah, yes. I guess that's in the "treat 100-year old sources as primary and weak" bucket.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  16:17, 3 November 2016 (UTC)

• CommentThere are two separate issues in sourcing pronunciations that may require editorial decisions: 1. Published pronunciations being sourced may have been derived from historic convention, including rules of prosody and transliteration when Romanizing Greek such as if sourcing from “The Naturalists Lexicon” or “Birds of North America.” For example the letter “e” in Australopithecus is a transliteration of the Greek letter “eta”, thus creating a paroxytone, meaning the accent is placed on the second to last syllable (the penultimate law). 2. Published pronunciations may reflect estimates of apparent usage, for example many anthropologists treat Australopithecus as a proparoxytone (accent on the third to last syllable) likely through lack of awareness of classical phonology, and that is the only pronunciation given in WP. Similarly, modern typography omits the ligature in the digraph “ae” as in Canidae, which can result in pronunciation of “ae” as the “a” in “day” rather than the Anglo-Latin “ee” sound as in “anaemia.” In sourcing a pronunciation it may be desirable to indicate whether the source is usage-based or rule-based. Ecol53 (talk) 19:48, 3 November 2016 (UTC)
• From a linguistic and encyclopedic perspective, only the usage-based pronunciations matter to our audience (and arguably at all). This is not a new problem; Google turns up dozens of earnest, handwringing discussions about this (a typical and illustrative one is here). It is clear that there are regional variances in how this is generally pronounced (e.g. ae or æ tends mostly though not always to be pronounced /i/ to rhyme with 'see' in British English, but varies in North American English from /i/ to /ei/ as in "hay" to /ai/ as in "high" to (in some positions) /ɪ/ as in "kit", or even a schwa). But it also varies by specialty, with mathematicians, dentists, anthropologists, botanists, etc., all taking different approaches that are often not even internally consistent within the field. Then it can vary by age of the speaker, due to changes in how Latin is taught; by religion (or lack of one) due to exposure level to heavily Italianized church Latin; and by other influences, like knowledge of how Classical Latin in various stages was pronounced (e.g. one may prefer /k/ over /s/ for any c including before a vowel; and inconsistent "grandfathering" of common pronunciations of more assimilated words (e.g. "see-zer" for Caesar, when German Kaiser is actually much closer to the original pronunciation in multiple ways), even by people who may be sticklers for a more Old Latin or Late Latin pronunciation otherwise; and so on. There's no one "right" way to do it. All we have to go on is how RS tell us people actually do it (in modern usage). To return to your example, virtually no one (in English) pronounces Australopithecus with stress on the penultimate syllable (the "e" before "cus"), though exact stress varies from "au-stral-o-PITH-e-cus" with secondary stress on the "stral" (mostly North American, I think), and "AUS-stral-o-pith-e-cus" with secondary stress on the "pith", which mostly seems to be a British/Commonwealth usage. The difference isn't marked, compared to *"aus-tral-o-pith-E-cus" in English (I have a degree in anthropology and have never in my life heard that pattern from an English speaker, though a Spanish speaker would default to it, following Spanish rules).

  Short version: If modern dictionaries (including dictionaries of science, etc.) provide one or more pronunciations we could offer it/them as a/some pronunciations, and should note their distribution if possible. Century-old books are not reliable for this, since they'll be giving "do it this way because ancient Romans [or mediaeval priests] would" Victorian prescriptivist dogma, not linguistic description.

  Alernative approach: Create an article along the lines Pronunciation of New Latin in English (or perhaps a Help:-namespace page) that explains the various quasi-systemic approaches to this, and their irregularities. Then just always link to that article for pronunciation. We have Help:IPA for English and Help:IPA as used by IPA templates; kind of similar in concept.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  03:45, 4 November 2016 (UTC)

MOS:LQ is self-contradictory

Source text:

Bierstadt Lake is surrounded by a thick pine forest, and is ringed by sedges that give it a very serene appearance.

Wikipedia prose:

A dense pine forest encircles Bierstadt Lake, and the lake "is ringed by sedges that give it a very serene appearance."

This MOS:LQ statement says to put the period inside: "Include terminal punctuation within the quotation marks only if it was present in the original material, and otherwise place it after the closing quotation mark."

This MOS:LQ statement says to put the period outside: "If the quotation is a full sentence and it coincides with the end of the sentence containing it, place terminal punctuation inside the closing quotation mark. If the quotation is a single word or fragment, place the terminal punctuation outside."

Give-and-take is a good thing at Wikipedia, but useful compromise does not mean creating self-contradictory guidelines. How would you go about resolving this problem? RfC? ―Mandruss ☎ 19:40, 29 October 2016 (UTC)

This might be just me, but I would prefer to avoid this sort of quote altogether. Either quote or don't. Preferably don't in this case; just paraphrase the whole thing. --Trovatore (talk) 19:49, 29 October 2016 (UTC)

Yeah, my concern is more for the guideline than for the article. I'm not here for article help or writing advice. The point is that we have a self-contradictory guideline, and that does more harm than good. ―Mandruss ☎ 19:55, 29 October 2016 (UTC)

Well, but it might be self-contradictory only in a case that shouldn't happen at all, which isn't so much of a problem. It's true though that I wouldn't want to actually ban that sort of quote, so sure, I'll buy that there might be at least a theoretical problem. --Trovatore (talk) 21:51, 29 October 2016 (UTC)

@Mandruss: the two extracts are confusing when read together, I agree. I don't think they are strictly logically contradictory if you pay careful attention to the only in the first of your extracts from MOS:LQ. It does not say "Include terminal punctuation within the quotation marks if it was present in the original material". It is attempting to impose a condition, namely that only if the terminal punctuation was present in the original material should it be included within the quotation marks. It would be better to word the first extract in the negative: "Do not include terminal punctuation within the quotation marks if it was not present in the original material; if it was not, place it after the closing quotation mark."

There's also an issue as to what is meant by "fragment" in the second extract; does it mean that removing any number of words from a sentence always leaves a fragment, or (as I interpret it) does "single word or fragment" imply that the fragment is a small part of the sentence, e.g. just a few words. I'd place the period/full stop inside in your example, but outside in Bierstadt Lake has been described as having "a very serene appearance". But whether this is what was intended or not is another matter! Peter coxhead (talk) 21:48, 29 October 2016 (UTC)

Thanks. Perhaps we can all agree that a guideline is not effective if its application requires close study, parsing, and analysis on its talk page. That would be a good starting point. ―Mandruss ☎ 21:55, 29 October 2016 (UTC)

• I have every confidence you guys will work this out. I just want to say two things:

• This LQ stuff is certainly one of the most effective uses of editor time anywhere on Wikipedia. Millions of articles have been immeasurably improved by the guidance it gives. Really. I really mean that. No kidding. Seriously.
• Trovatore's idea that "this sort of quote" should be avoided is nonsense. And that I really do mean. I don't want to sound harsh, but I'm constantly amazed by the narrow ideas people have about what constitutes good formal writing.

EEng 23:23, 29 October 2016 (UTC)

Re bullet 1: For Pete's sake, how is it helpful to be sarcastic and then state unequivocally that you are not being sarcastic? Either the guideline is important enough to be made more helpful than harmful, or not important enough to exist. I don't really care which, but I do feel strongly that one or the other needs to be chosen. ―Mandruss ☎ 00:51, 30 October 2016 (UTC)

I was being sarcastic when I implied I wasn't being sarcastic. LQ was devised by people who mistake English punctuation for a programming language. But since we seem stuck with it I hope you guys iron this wrinkle out. EEng 03:24, 30 October 2016 (UTC)

LQ was devised by people who value accuracy - what's inside the quotation marks, including punctuation, should match the original text. If it were devised by programmers we'd have punctuation inside and outside the quotation marks:

Did Darla say, "There I am?"?

No, she said, "Where am I?". — Preceding unsigned comment added by Mitch Ames (talk • contribs) 04:08, 30 October 2016 (UTC)

No, LQ was devised by obsessives whose preoccupation with an imaginary problem has put them on a crusade against forms every good publication uses, and with which everyone is familiar e.g.

"I like vanilla," she wrote.

-- instead insisting on idiocy like

"I like vanilla", she wrote.

or maybe (for all I know)

"I like vanilla.", she wrote.

Every reader understands that punctuation at the boundary of a quotation might be modified in certain standard ways as part of the transition to the non-quoted material. LQ doesn't promote "accuracy" but rather turns the familiar and attractive into the unfamiliar and ugly, for no reason. EEng 07:23, 30 October 2016 (UTC)

When you say "everyone" and "Every reader", perhaps you mean "everyone in the US". Quotation marks in English#British practice suggests that the rest of the world might think differently. Mitch Ames (talk) 08:40, 30 October 2016 (UTC)

I gather you've never actually read Fowler, which the article you link draws on. And as that same article makes clear, British usage embraces both "British" and "American" styles in various contexts, so my original statement stands: readers understand that punctuation at the boundary of the quote might not be exactly as in the original. EEng 17:41, 30 October 2016 (UTC)

@EEng: commenting on your post is, like your original comment, just adding to the time that has been wasted on this issue, but since you set the example, I'll join in. Suppose she actually wrote "I like vanilla." Then, in some versions of LQ, it's correct to write "I like vanilla," she wrote. The comma inside the quotation marks replaces the full stop that was there in the original. Suppose instead she actually wrote "I like vanilla but not in coffee." Then, again in some versions of LQ, it's correct (although misleading as a quotation) to write "I like vanilla", she wrote." Obsessive? Sure. Irrelevant to 99.9% of Wikipedia editors? Sure. Should we waste time arguing about it? No. It's not the issue Mandruss raised, which is lack of clarity. Peter coxhead (talk) 10:42, 30 October 2016 (UTC)

I wasn't suggesting anyone argue about it. See [2]. EEng 17:41, 30 October 2016 (UTC)

• I agree with Peter Coxhead. There's no contradiction. It's just a case where things could be made clearer. Jimp 03:04, 30 October 2016 (UTC)

• I agree with Mandruss, and I remember raising this issue here twice, starting in mid 2014. The point about LQ is not clear, so it's hardly a surprise to see that MOS:LQ is rarely adhered to. JG66 (talk) 03:35, 30 October 2016 (UTC)

I'd change MOS:LQ to: Include terminal punctuation within the quotation marks only if it was present in the original material and is grammatically required by the quoted text; otherwise place it after the closing quotation mark. So I'd write:

A dense pine forest encircles Bierstadt Lake, and the lake "is ringed by sedges that give it a very serene appearance".

The full stop is outside the quotes because all though it is present in the original text it is not grammatically part of or required by the quote - the quoted text is not a full sentence, so does not require a quoted full stop. This is consistent with Keep them inside the quotation marks if they apply only to the quoted material and outside if they apply to the whole sentence. In this case the full stop terminates the entire Wikipedia prose sentence, not "only the quoted material". Mitch Ames (talk) 04:24, 30 October 2016 (UTC)

I would tend to go the other way and include the period in the quote. Maybe it's not "required", but putting it outside suggests to me that the quoted sentence did not end there; and it did. In any case, I think what we have here is an option to do it either way, neither of which is incompatible with the principle of LQ. Maybe we can express it in a way that removes the contradiction, without necessarily being more prescritive than necessary to keep it "logical". Dicklyon (talk) 05:16, 30 October 2016 (UTC)

The correct way to show an option either way is: "The period may be placed inside or outside the quotation mark, at the editor's discretion." Or just say nothing at all. ―Mandruss ☎ 05:50, 30 October 2016 (UTC)

The point of the guideline is not to "show an option either way", but to specify a single consistent way of doing it. If you wanted to change the guideline to "at the editor's discretion" that would be a separate proposed change to the guideline. Mitch Ames (talk) 05:58, 30 October 2016 (UTC)

I agree, and I was not and am not proposing that. I was replying to Dicklyon's comment. As I said, my only concern is eliminating the apparent contradiction to avoid AT conflict and circular editing, both of which are wastes of editor time. Alternatively, scrap the guideline, but that would be a harder sell I think. ―Mandruss ☎ 06:03, 30 October 2016 (UTC)

putting [the period] outside suggests to me that the quoted sentence did not end there" — On the contrary, the point of LQ is that the absence of the period inside the quote does not imply anything about the original text other than what is actually quoted. The source text could have been "... and is ringed by sedges that give it a very serene appearance, reminiscent of ..." and it would not matter; the Wikipedia prose would be just as correct and have exactly the same meaning. Mitch Ames (talk) 05:55, 30 October 2016 (UTC)

• Comment - In my opinion, people who oppose the existence of a guideline should initiate an RfC for its removal. Otherwise they should refrain from disrupting discussions about its improvement. ―Mandruss ☎ 06:13, 30 October 2016 (UTC)

To respond to this entire thread at once:

I'll collapse-box it, so incoming peeps can focus on the proposal below

The 'Do an anti-LQ RfC if you want but stop disrupting improvement discussions' sentiment: Or they could just give it a rest, since launching anti-consensus "challenges" every six months or year in hopes they eventually WP:WIN is tendentious. I think that's finally been sinking in, given what happened in Feb. after someone's seven-year campaign on this non-issue finally worse out community patience. Our Quotation marks in English article is a counterfactual OR trainwreck (see previous sentence for a hint as to why). I've been meaning to rewrite it for months, but half the source materials I need are in boxes due to my landlord starting construction and not finishing it yet (and to me procrastinating before that because of the drama surrounding the topic). Even "everyone in the US" [likes typesetters' quotation, TQ, falsely labeled "American style"] would be dead wrong, since it's been Americans who have most promulgated LQ as preferable, not just acceptable, in precision writing. These days, American professors in multiple articles on the topic admit they can't get American students to revert back to TQ unless they directly punish students by assigning bad grades to papers with LQ, which many of them use now as their automatic, natural preference. When a "tradition" has to be coerced it is no longer a tradition but reactionary indoctrination. As for "readers understand that punctuation at the boundary of the quote might not be exactly as in the original" [in TQ]: Readers also understand that in LQ the punctuation inside the quote will be found in the original, removing all doubt. The second option is objectively better practice for a project like WP. It's why LQ was adopted here, and why it has stuck for over a decade in the face of recurrent but misinformed fist-shaking by a few who incorrectly see this as some platform for nationalistic campaigning. They're invariably unaware of LQ's actual history. There is no single British/Commonwealth/International/non-US quotation style, and while most of them were inspired initially by LQ around a century ago, they cannot be equated with it, and they drift further and further apart (most of them are promulgated by competing news organizations that like to set themselves apart from each other, much as the New York Times still maintains its own style guide against the Associated Press Stylebook that dominates North American news publishing). They all have differing rationales for their variances from LQ and from each other. Of all major UK publishers with public style guides, only one actually matches LQ's output, and it does so accidentally, because its rules have nothing to do with LQ's reasoning. '"I like vanilla," she wrote. The comma inside the quotation marks replaces the full stop that was there in the original.' That's a rule from a couple of the British/Commonwealth quotation styles, and has nothing to do with LQ. LQ is just one actual rule: Except for truncation, "..."-indicated elision, and square-bracketed interpolations/alterations, do not change a quotation by insertion into or replacement of its content, including punctuation. Converting a period/stop to a comma inside the quote isn't LQ at all, it's a UK/Commonwealth news thing. The "obsessive programmers invented LQ" fairytale is patently false. LQ was a gradual evolution in the 19th century, in linguistics, philosophy, textual criticism, and other fields with a need for content accuracy. It was adopted (with modifications for expedience over precision, which keep drifting) by publishers pretty much everywhere but the US throughout the late 19th and early 20th centuries. This was followed by subsequent further promulgation in the 20th century by technical and legal writing in the US (the legal situation reversed itself by ca. the 1960s, when the courts started mandating a consistent style and going with TQ because it matched what they were used to in older documents). Quite late came LQ's totally dominant position in online writing, before the Internet was even broadly open to the general public. Programmers did having something to do with that, but it was also advanced by people in many other disciplines, and the basic fact that only some of them were American. More recently, even the last several editions of Chicago Manual of Style, the last bastion of TQ in nonfiction book publishing, have specifically recommended LQ for "computer writing" (on the strength of the same work that popularized LQ as "the Internet style" since the 1980s), without even narrowing what "computer writing" might mean, reinforcing its online use as "sanctioned" by a leading US style guide. CMoS also recommends LQ for several other things, including quoted material in textual analysis and criticism (see if anyone can guess what direct quotation in an encyclopedia often qualifies as), and linguistic glosses (which WP uses literally millions of times), as well as conceding its use in writing about philosophy (see if you can guess what a lot of other encyclopedia material is). It would be nuts for WP to bounce back and forth between multiple quotation styles in the same article, especially when the only "reason" to do so would be to introduce less accuracy and precision, all just because someone wants to argue subjectively about whether a particular segment is philosophical, linguistic, technical, or text-analytical "enough", or because "gimme muh 'Merican quotes". Never going to happen. "If [LQ] were devised by programmers we'd have punctuation inside and outside the quotation marks." There is actually a British journalism quotation style that requires exactly that, I kid you not. It's rare, probably limited to a single publisher. (SlimVirgin first mentioned it here, and I doubted her, but I ran across it in style-guide research back around March, I think.) And, yeah, it has nothing to do with LQ. It is further proof, as if any were needed, that there is no equating LQ and "British quotation", TQ and "American", or making any kind of nationalist pseudo-ENGVAR case. There are at least 10 different British/Commonwealth quotation styles, with different rules and reasons but with mostly similar end results and lot of overlap with LQ. As for the "oh yeah, well there's not 10 American styles, so Americans should get their one style" complaint: Aside from the fact that lots of Americans use LQ when not forced to use TQ, I think a common-sense way to look at this would be: What if tomorrow the Canadian government and various major .ca publishers said "We're going to use French guillemets instead of English quotation marks, in English, just to be Canadian and different; it will be our new national tradition." Would WP adopt that usage here in articles tagged as Canadian English? Not on your life. It wouldn't serve overall reader interests, only a WP:NOTHERE nationalism agenda, and simply lead to complication, confusion, and dispute. If we actually made some "use TQ in American English articles" rule, there would be a massive land-grab by a small number of virulently anti-LQ people to stake US ENGVAR claims on as many articles as possible. I'm hard pressed to think of anything more disruptive and corrosive to collaboration but we all know that's exactly what would happen. LQ is "ugly and unfamiliar". It's been familiar to all English-speakers but Americans for generations, was familiar to well-read Americans that entire time, and now is familiar to all Americans who use the Internet, thus it's familiar to everyone WP reaches. It just may not be preferred by all of them. It's physically impossible for one style guide to please everyone all the time; there are competing would-be rules for virtually every minute aspect of written English, even the most basic matters like whether sentences must start with a capital letter. "Ugly" is just subjective handwaving. For every American who thinks LQ is "ugly" (by no means all of us), there's someone else who thinks TQ is subjectively ugly as well as objectively a constant source of doubt about quotation veracity, the second point obviously being more important. The hand-waving claim that LQ is mostly not complied with has already been disproven. This was actually researched in Jan. this year, or late last year (I forget – check the archives) by LQ's staunchest opponent (the one now not in our company) and by myself. Compliance is actually much higher for MOS:LQ than for many other MoS line-items, even basic stuff like consistent date formatting. A large percentage of "non-compliant" articles are actually mostly compliant, and were formerly compliant, but were just made inconsistent by later additions by new editors who weren't familiar with MOS:LQ (and perhaps a few who know it but refuse to follow it?), so compliance is actually much higher than it looks at first, especially the higher the quality level of the article (= higher likelihood of MoS awareness and gnoming). And it would have to be, for reasons that should be obvious by now.

 — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  15:43, 3 November 2016 (UTC)

Hard to see how some people think MOS is a massive and pointless timesink. If only you would put a fraction of that effort into getting the links-in-quotes reform, which would be a real accomplishment, back on track. EEng 16:38, 3 November 2016 (UTC)

The endless stream of sarcasm from you about how time-wasting MoS is suggests taking a break from it. :-) I said what I needed to (and supported your last proposal) at links-in-quotes, though not in as timely a fashion I would have liked, due to overwork in Real World Land. The entire thing has stalled with too many competing proposals. I don't think anything will come out of it this time; all commentary on it stopped something like a month ago. I would let it archive, then re-open the topic after a break, picking up with proposals that had some support, and try to merge them.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  17:20, 3 November 2016 (UTC)

I appreciate your contribution re links-in-quotes, but I was hoping you could do more to prod the other participants to return. But what you suggest now seems like a good plan. EEng 17:33, 3 November 2016 (UTC)

Proposal

Let's not start the whole argument about LQ itself again. (EEng is quite right to be sarcastic about the time that has been wasted on this.)

Mandruss has identified a lack of clarity in MOS:LQ. It arises for two reasons which require two changes:

1. In English, constructions with "only if" are hard to understand unless the context is clear, and the "only" is easily missed. ("It rains only if it is cloudy" does not mean "It rains if it is cloudy". Translating to logical symbols, the first means "rain → cloudy", the second "cloudy → rain".) So I suggest changing Include terminal punctuation within the quotation marks only if it was present in the original material, and otherwise place it after the closing quotation mark to Do not include terminal punctuation within the quotation marks unless it was present in the original material; if it was not, place it after the closing quotation mark.
2. The word "fragment" is unclear in If the quotation is a single word or fragment, place the terminal punctuation outside. I'd like to change it to short phrase and then add When longer terminal parts of sentences are quoted, editorial judgement should be used.

Peter coxhead (talk) 10:26, 30 October 2016 (UTC)

I don't think "short phrase" is appropriate, because that part of the guideline may apply to longer phrases as well. However the existing instances of "fragment" should probably be "sentence fragment".

I think that instead of "... editorial judgement" we should specify that trailing punctuation should be included inside the quotation marks if ... it was present in the original material and is grammatically required by the quoted text. — Preceding unsigned comment added by Mitch Ames (talk • contribs) 14:07, 30 October 2016 (UTC)

• I concur strongly with four things here:
  1. Agree with inverting the main passage to remove the confusing "only if". I would suggest this:
     "Do not include terminal punctuation within the quotation marks unless it was present in the original material and is needed grammatically or for clarity; otherwise, place it after the closing quotation mark".
     This solves three closely related problems at once:
     • The "if" versus "only if" confusion goes away.
     • Editorial judgement (per Dicklyon and several others above) is retained: If it was in the original, you can include it if it's grammatically needed, or if the meaning might be harmed or dubious without it (e.g. because the phrasing ambiguously seems to indicate a truncation that wasn't one). The "British" (international, Commonwealth, non-American, whatever) systems of quotation that are most similar to LQ also permit this flexibility, naturally.
     • We bury the silly but not infrequent false assumption that if it was present in the original it must be included no matter what. There is no LQ principle that material cannot be removed, only that material cannot be falsely inserted. So, requiring that something be included in "LQ at WP" would not be LQ at all, but WP inventing some new LQ-related style out of thin air. It would also mean nonsensically insisting that a comma or whatever in the original "must" be retained at the end of a quoted bit, even if it mangles the overall sentence quoting the fragment. Self-evidently goofy, yet I keep encountering incorrect assumptions like this about LQ (mostly from people who oppose LQ, which may either explain their opposition, or explain their misinterpretation, or both, since it's a self-reinforcing negative feedback loop based on an error).
  2. Agree that "fragment" should be clarified as "short phrase", "fragmentary phrase" or something similar; that's sufficient clarification, especially if the "and is needed grammatically ..." bit above is also present. It's not really about "sentence fragments", since almost all quotes that are not self-contained, quoted full sentences, without added editorial intros or tails, are fragments (when they're not, it's just accident that they were truncated in a way that happens to still form a grammatical complete sentence that is not the original longer sentence).
  3. Agree it was not at all MOS:LQ contradicting itself, just sub-optimal wording that led a few editors to misinterpret it; and that, regardless, clarifying it is a good idea since it should reduce such confusion and prevent much further disputation.
  4. Agree that MOS:LQ needing a handful of wording tweaks is in no way grounds for re-opening yet another tendentious "challenge" against a decade+ consensus. Someone who wouldn't drop that stick has already been indeffed. The last thing WP needs is to lose even one more editor over "style wars".

 — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  14:08, 3 November 2016 (UTC)

@SMcCandlish: I agree with your proposal except for "or for clarity", which I think will lead to editors unnecessarily including terminal punctuation. Could your provide an example or two where the terminal punctuation is need for clarity but not grammatically? Mitch Ames (talk) 07:07, 5 November 2016 (UTC)

Well, see the entire discussion basically. The concern is quoted statements that do not necessarily appear to be full sentences and which strongly imply editorial truncation but were not actually subject to any. E.g., anything ending in "just because.", as an obvious example. Maybe there's another way to get at this. LQ is "do not falsify quotations", in its shortest encapsulation. Insertion and in-place alteration is not permitted aside from "..." and [bracketed]. Truncation is permitted, and people have leeway in exactly how they do it. For some reason, some people don't think they do, and incorrectly insist that if I say "Chocolate is good", that the only permissible way under LQ to punctuate a sentence-ending partial quotation of this is in the form "SMcCandlish said 'chocolate is good.'", when of course "SMcCandlish said 'chocolate is good'." is also permissible, is less prone to error, and arguably more sensible, since the period is terminating the surrounding sentence and the quoted part is fragmentary. But the "inside" way is permissible, and opposition to it is hair-splitting (i.e., it's a matter of editorial judgement about clarity, not something we need a "rule" about). The only "risk" with the "...'...is good.'" version it is if a later editor expands it, it might come out as "SMcCandlish said 'chocolate is good,' in a Wikipedia talk page post in 2016." – that's an error under LQ, falsely indicating that my original contained a comma and continued with additional detail. Anyway, another example of the "it really is better inside" case is something like: "Johnson stated, "I deny any wrongdoing, malfeasance." Without the period/stop inside the quote, the unusual "and-less" construction would otherwise make it look like a partial quotation of something that continued: "I deny any wrongdoing, malfeasance, ...".

I don't understand your "will lead to editors unnecessarily including terminal punctuation" concern. Can you provide examples of that?  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  12:47, 5 November 2016 (UTC)

anything ending in "just because." — OK that make sense. My main concern is that - given the option - some editors might simply put the terminating punctuation inside the quotes because it seemed clearer to them because they were used to American style. Being "clearer" might be a subjective thing. Mitch Ames (talk) 13:12, 5 November 2016 (UTC)

Well, it is subjective. Everything that MoS leaves to editorial discretion (explicitly or by simply not saying anything about it, which is often a virtue) is subjective by definition. What I'm getting at is, what harm is there in including internal-to-the-quote punctuation if a) it was present in the original and b) makes sense in the context of the larger sentence? I would prefer to leave it on the outside when it's not needed grammatically or for clarity on the inside, especially if the quoted bit is very short, but that's really just a preference.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  12:22, 7 November 2016 (UTC)

ENGVAR and national varieties of English

This one comes up from time to time and I was wondering whether it was worth dealing with it once and for all. The problem is that the value of WP:MOSTIES as currently written and of having individual templates for so many purported sub-types of English is not clear. Yes all these varieties of English (and more) exist when it comes to informal spoken English and dialect, but there are only a limited number of "types" of standard English when it comes to the formal, written language. The main distinction understood across the world is between "British" and "American" English and mostly relates to not much more than a few minor spelling, grammar and vocabulary differences, as well as date formatting (and with vocabulary, WP aims to find common ground anyway; plus the occasional presense of a "foreign" term – or local term, depending on your perspective – doesn't suddenly mean we are dealing with a whole new variety or style of English, just as the presence of the occasional technical term doesn't). The purpose of these templates should be simply to explain what style readers can expect to see and what style editors need to follow when adding content.
However, they seem to be more about declaring national ownership of topics and creating multiple walled gardens within WP than helping with the above; indeed they arguably add confusion, because on seeing them, people might wonder whether there are further differences that they are not aware of between "XX English" and a more familiar standard (per the above, invariably there are not anyway). Equally, several of them talk about the article using "XX dialect", which is completely misleading, suggesting as it does that the page should use local slang or informal terms.
In actual, practical terms, all that are really needed are the Engvar A, B, C and O templates, perhaps with a couple of additional ones and some variation to the text, eg to say probably at most three or four templates which say something like: " .. uses American-style spelling (labor, traveled etc), grammar (write me) and date formatting (mdy), and sometimes vocabulary (sidewalk etc)" and " .. uses British/Commonwealth-style spelling (labour, travelled), grammar (write to me) and date formatting (dmy), and sometimes vocabulary (pavement etc)" etc. The rest of these can probably be deleted, and WP:ENGVAR amended accordingly, as all of them are, in effect, covered under one or other of the composite ones. I guess this might require an RFC here and a TFD debate as well but would be interested in others' thoughts first. Just to repeat, this is about the practical issues involved when it comes to formal writing, not some kind of crusade to deny the existence of other variations in English. N-HH talk/edits 10:12, 31 October 2016 (UTC) Wording amended post-discussion to make point clearer for posterity, FWIW. Relying on Engvar A, B etc to make point caused distraction, not least because it's not 100% clear what they mean currently. N-HH talk/edits 09:50, 3 November 2016 (UTC)

TLDR: are 20-odd different "national" templates really needed to explain to readers and contributors what spelling etc rules a page is following? N-HH talk/edits 10:19, 31 October 2016 (UTC)

• They're not needed but they certainly are useful, and I think we should be a lot more conservative than we sometimes are when applying TIES. If we have an article on a Mainland Chinese actress who sometimes works in Hong Kong, and the user who originally wrote the article wrote in American English, then "ties" to Hong Kong English should not overrule PRESERVE. TIES should not even apply. I think marking one's own work as being written in the variety of English you were using is a good idea. This doesn't apply to "national varieties" specifically, mind you. I write articles using Oxford spelling, and having a template to tell later editors that this is not "American spelling" or "British spelling" or a random mixture of both is nice. I am assuming the Oxford template would be among the "20-odd different national templates" being referred to. And of course WP:FORMAL bans the use of informal spoken dialect words and grammar when writing Wikipedia, so these templates do not create a problem on that front. Hijiri 88 (聖やや) 12:19, 31 October 2016 (UTC)

OK, but you haven't explained why they might be "useful". My whole point is that people are taking that for granted when, in actual fact, they don't flag up any actual differences anyway. Hence they are arguably, by definition, very much useless, and if anything distracting and confusing. As for Oxford spelling, that's included broadly under Engvar O, which I said should stay – again, the point is not to remove options but to remove different and confusing ways of flagging up what is, in practical terms, exactly the same option. As for dialect, some of these templates create a problem precisely in that their wording contradicts the expectations expressed in WP:FORMAL. If they're not deleted, that wording has to change at least. N-HH talk/edits 12:37, 31 October 2016 (UTC)

I said I think marking one's own work as being written in the variety of English you were using is a good idea. That is how the templates are useful. Hijiri 88 (聖やや) 13:06, 31 October 2016 (UTC)

I agree entirely with Hijiri88. If more editors marked pages they created with the ENGVAR in use, a lot of time and hassle could be avoided. Peter coxhead (talk) 13:13, 31 October 2016 (UTC)

I know what you said Hijiri88; just like I know that I have said, twice now, that it makes no actual difference whether someone thinks, for example, they are writing on WP in "Indian English" or "British English", or "American English" or "Israeli English", since each pair have the same style conventions in formal writing. As I said at the start, this seems to be more about declaring something for the sake of it rather than about any practical benefit or clarity. I also agree pages should be marked – it's a question of what with. Multiple, variant templates which essentially say the same thing, but still lead to arguments because people want the "right" flag on something, or a limited number of templates which consolidate identical options under one clear, consistent and discrete, but flag-less, heading? N-HH talk/edits 13:21, 31 October 2016 (UTC)

Except that words are spelled differently even within so-called "national varieties" in formal writing. If you have some specific templates that should be deleted (and I think I might agree with you on Indian and Israeli English), that discussion is for TFD, mos MOST. Hijiri 88 (聖やや) 21:16, 31 October 2016 (UTC)

Agreed, there are always quirks and alternatives within otherwise standard types (eg burned vs burnt), if that's the kind of thing you mean, but we're slightly stuck with that. The point is about the broad principles where there are pretty fixed (and limited) differences, eg -our vs -or and -ise vs -ize. Anyway, I plumped for here for the discussion as ENGVAR sets the basic principles, and refers explicitly to the various "types", and the templates ultimately follow from that. I posted a note on the talk page for the template category, but didn't want multiple fora at once. TFD may be the next step. N-HH talk/edits 13:01, 1 November 2016 (UTC)

• Comment: the {{EngvarA}}, {{EngvarB}}, {{EngvarC}}, {{EngvarO}} templates have terrible, opaque names. {{Use Canadian English}} is crystal clear to any editor who may stumble across it, even if they aren't aware there was something called "Canadian English" in the world. If we want to cull EngVar templates (on which I have no comment), let's not replace them with these awful ones. Curly "the jerk" Turkey 🍁 ¡gobble! 21:31, 31 October 2016 (UTC)

Just to comment, briefly, I'd say that all of those are new creations, except 'EngvarB'. EngvarB was created for the purpose of tagging articles that used spellings that were obviously not American, but not identifiable as being specifically British, Canadian, &c., and so hence could not be tagged as 'use British English', &c. These new 'EngvarC' and 'EngvarO' templates, created in September, should be deleted. They serve no purpose and directly defy the existence of EngvarB. RGloucester — ☎ 23:38, 31 October 2016 (UTC)

From the descriptions I note that:

• A - "articles that have American English spelling"
• B - "articles that have non-specific spelling that cannot be identified as American English or Canadian English spelling"
• C - "articles that have Canadian English spelling"
• O - "articles that have generic Oxford spelling"

so it appears that British spelling is a "non-specific" usage defined by being not American. Hmmm. Martin of Sheffield (talk) 09:45, 1 November 2016 (UTC)

The ones I was looking at are the ones linked from the Varieties of English templates page, which seem to be slightly different, eg this one. They explicitly refer to American, British/Commonwealth, Canadian and Oxford (although not by name in the latter case) spelling. As I say, they may need some tweaking or even renaming, but I like the way they refer to "spelling" – rather than "[type of] English" or, worse, "dialect" – and don't have flags. Plus as I say, they would limit the proliferation of nation-based templates, in that "Indian English", "British English" etc would all fall under what is currently called "B"; "Israeli", "Philippine", "American" English etc would fall under current A and so on. N-HH talk/edits 12:53, 1 November 2016 (UTC)

Have you noticed though that the first sentence of Template:EngvarB_spelling is "This template may be included on talk pages or edit notices to alert other editors that the associated article is written in EngvarB spelling." where EngvarB spelling links to {{EngvarB}}, that is "non-specific". The whole issue is a minefield though, terming English-English as British-English to appease the Americans is a sure fire way to upset the Scots and Welsh who have their own distinct dialects (and indeed languages). :-o Martin of Sheffield (talk) 15:04, 1 November 2016 (UTC)

As a Scot, I can say with absolute force that standard written English as a written in Scotland is not in any way different from standard written English as written in England, Wales, or Ireland. We are not talking about spoken 'languages' and 'dialects', only standard written forms. Encyclopaedias are not written in dialect. This is beyond the pale. EngvarB, once again, serves to identify articles that use spelling that is identifiably not American, i.e. rooted in British usage, but not clearly British, Irish, &c. It has a separate purpose from the likes of the Use British English template. The other brand new templates DO NOT MAKE sense for that reason, as they duplicate existing templates and defy the purpose of EngvarB. RGloucester — ☎ 19:28, 1 November 2016 (UTC)

Agreed on the first point, and that's part of the reason for my original suggestion: the proliferation of "national" templates and the declarations sometimes found in them that a particular page is written in "dialect" are at best confusing and at worst misleading, in practical terms if nothing else. See this one, for example. As for issues with the A, B etc ones, as I have said from the outset, and again just now, "they may need some tweaking or even renaming" but the broad principle underlying them and the idea of using them as a basis for a rationalisation – which is what I was suggesting we look at – seem sound to me. That said, we're not really getting anywhere, perhaps inevitably in situations like this, where it's always hard to get agreement – but also partly because the usual nationalist considerations are creeping in and partly because people aren't even reading what others are actually saying properly. I'm resigned to this one remaining the usual confusing mess. N-HH talk/edits 10:07, 2 November 2016 (UTC)

• Let's have U and non-U. EEng 14:38, 1 November 2016 (UTC)
• {{EngvarB}} is inserted by a bot. It should be removed wherever found and replaced with the appropriate national template. Hawkeye7 (talk) 12:21, 2 November 2016 (UTC)
• We need to get rid of most of the ENGVAR templates. They're keep multiplying off into the land of pointlessness and divisiveness, asserting silly fine-tooth-comb distinctions (like Jamaican, Barbadian, etc.) that simply do not exist in written, formal-register English. These hair-splits are really just a major written variety (usually British, though a handful are American-derived) with some minor local vocabulary differences (most of which should be studiously avoided as colloquialisms), and zero grammar or inflectional morphology differences of any kind at the encyclopedic prose level. While I think we'd be okay with retaining an ENGVAR-recognized distinction between US, British, Canadian, Australian, Irish, New Zealand, South African, Indian, and a catch-all Commonwealth, we can probably dispense with the others, and we might even be able to compress this to US, Canadian, and British/Commonwealth, unless we're certain that in encyclopedic writing there's going to be a marked and important distinction between all these slight variants of British/Commonwealth English. I've been warning for some time that we'd start seeing demands for Scottish English, etc., and here we are already. Next it'll be Philadelphia English, and California English, and U.S. Virgin Islands English, and British Virgin Islands English, and "German English" as picked up from NATO air force bases, etc., etc. This has jack to do with writing an encyclopedia; it's indistinguishable from demanding a set of templates like a badge to collect, and special "territorial rights" over articles and topics for nationalist, local, or ethno-cultural pride reasons. I think it is running in close parallel to various other bouts of territorial article-control chest beating WP has been beset with over the last couple of years. Enough already.

  PS: If anyone thought I was making a fallacious slippery-slope argument, they'd be wrong, since we already have templates of all the sorts I just provided hypothetical examples of, including city (Hong Kong), subnational (Scottish), small island (Barbados), and unofficial ESL (Israel, which has only 2% of its population as native speakers of English, mostly recent American emigrés). For starters, any such templates used on less that 100 articles already should just be WP:TFDed as pointless. If a combined British/Commonwealth one isn't practical, they can at least be compressed regionally, e.g. Au/NZ, and the three or four African ones. Even the articles on things like Nigerian English indicate no difference from other dialects other than absorption/invention of some local vocabulary, which is true of all, even very local, dialects. WP needs to delete most of these, and consolidate the remainders in ways that discourage the creation of more territoriality-forking. A side problem we tried to resolve about 2 years ago, and got consensus for here, but then a canvassing effort derailed it later, was to combined the various different sorts of these templates into a single one for each Eng. var., and lower-key than the present huge banners which just seem to serve a "only editors from X are welcome at this article" claim-staking purpose.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  09:54, 3 November 2016 (UTC)

I think I'd go for the narrowest option: are there really any practical differences that go beyond US vs British/Commonwealth, plus maybe Oxford-style and Canadian (which, in effect, can be seen as hybrids of the initial two)? Spelling etc in formal writing in Ireland and India for example almost certainly follows the same rules as standard B/C. I'd happily limit it to those four, and then require evidence of genuine difference before any more are added. N-HH talk/edits 10:32, 3 November 2016 (UTC)

If we separate orthography from word choice, then it would be possible to combine the templates as you say, into broad categories of 'British/Commonwealth' (including the Oxford variant), 'American', and 'Canadian'. Of course, New Zealand and Australia have vocabulary differences, likewise with all the various countries lumped under 'Commonwealth'. For example, 'Lorry' is no longer used in Australia, for example, but is still used in the likes of Hong Kong. But as I say, if we narrow down ENGVAR to orthographical differences like '-ise/-ize' and 'centre/center', which seems logical, this may be a solution. RGloucester — ☎ 13:19, 3 November 2016 (UTC)

Sure. I'm not meaning to suggest there should be no way to flag an ENGVAR-recognized issue like Oxford spelling, but that can be done with a template parameter. As for word choice, there are differences at least as large, I would think, between Califoria, Texas, and New Hampshire English as between .au and .nz, but we don't need templates about it. It's surely enough to say "the term 'lorry' isn't right for an Australian article; use culturally appropriate terms per WP:TIES" on the talk page or an edit summary. The ENGVAR problems are when someone comes along and says "WTF is all this -ise and -our stuff?" and makes it all Yankeetalk or vice versa. So, agreed we only need templates (if we really need them at all) for that sort of orthography and grammar thing, not vocabulary.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  16:03, 3 November 2016 (UTC)

I agree that the odd word difference is secondary to the systemic spelling differences. Often the boundaries are quite fuzzy there anyway: eg "truck" is more American than "lorry", but it's not a forbidden word in the UK (although something like "sidewalk" for example might jar more, which is why my suggestion for template wording did refer to vocabulary too, albeit slightly more weakly and as the last category, way after spelling; it probably is worth mentioning, as a note to people unaware of such things). Especially when we are often talking about only one or two words in some cases, and often in a specialist context, I certainly can't see the need to create a separate new template each time for a wholly discrete "type" or "variety" of English simply on that basis. Are Irish and British English wholly different things simply because one uses "Prime Minister" both locally and generically, and one uses Taoiseach when referring to the local one? Or Scottish and British because of "outwith" and the slightly different legal terminology? As noted, when that kind of thing does come up, the wording can easily both be switched to the correct term in context, and be glossed if necessary, without great debate anyway, just as we would with a technical term. It doesn't require flags and templates. N-HH talk/edits 14:59, 4 November 2016 (UTC)

• Why is there a template for Israeli English when there isn't even an article on Israeli English? The way the template's written, is certainly seems like it's meant as a dispute weapon. Curly "the jerk" Turkey 🍁 ¡gobble! 10:33, 3 November 2016 (UTC)

Because people have taken ENGVAR as a licence to create such territorial templates, without regard for the purpose of ENGVAR. We need to reign this in, as SMcCandlish says above. There is no 'Israeli English'. RGloucester — ☎ 13:21, 3 November 2016 (UTC)

And, yes, it's a dispute weapon. The rationale behind the canvassed thwarting of the deprecation of the worst of these templates back-when was, essentially, "we keep having to fight people at these articles, so we need these giant, stern banners to whack them with."  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  16:03, 3 November 2016 (UTC)

• In Australia, we have our own style guide for English, which covers a variety of things, including spelling, grammatical issues like the placement of commas, words and units used, and date formats. It's not just for spelling, and I get people fiddling with commas and the like. Hawkeye7 (talk) 21:10, 3 November 2016 (UTC)
  • If you're referring to the AGPM, also known as "the Snook book", puhlease, let's take a rain-check on it. Parts of it are quite good, but it's got some shocking ly bad advice; more importantly, it's not recognised as an authority beyond the civil service. Tony (talk) 04:14, 4 November 2016 (UTC)
    • And I agree with the angle above that favours international cohesion and simplicity (RGloucester et al.). This practice of stamping disparate and less-well-known local varieties of English on articles needs to be minimised, although with a little senstivity where necessary. The strongest argument for privileging a small group of standard, homogenous varieties (largely binary US–UK) is that it makes WP more accessible worldwide, and I mean to second-language speakers as well as native-speakers. For example, writing an article on an Indian town in uncompromising Indian English (itself not a single variety) disadvantages many readers who don't know the variety. If that choice were prompted by the notion that such an article is only read by locals, we've lost the key battles of "anyone can edit" (and of course, reaching out to the world). Tony (talk) 04:25, 4 November 2016 (UTC)

      Yep. I've long had this concern about the "branding" of numerous Caribbean articles as various things like "Barbadian English", "Jamaican English", etc., sometimes with a self-conscious attempt to sprinkle them with colloquialisms that mean nothing to anyone but locals. It's probably the same pattern as you observe in India articles.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  05:28, 4 November 2016 (UTC)

I think that many editors forget WP:COMMONALITY, and that it is high time that we give this principle a more prominent position. The guidelines, as written, already discourage such nonsense as described by SMcCandlish above. As an example, in past attempts to justify the creation of a 'Scottish English' template, editors have used the dialectal word 'outwith' as the prime justification. As I said then, 'outwith' is, first of all, not limited to a so-called 'Scottish English', and, second of all, is a dialectal term that should not be used per WP:COMMONALITY, as the standard 'outside' is also present in the usual Scottish lexicon. RGloucester — ☎ 15:18, 4 November 2016 (UTC)

• Some meta-analysis on nationalistic style books, colloquial and formal registers, vocabulary versus grammar distinctions, slow-down of dialectal divergence, and what we need ENGVAR templates for:

Extended content

The Australian government has published a style guide, Style Manual for Authors, Editors and Printers. Wikipedians (or anyone else) aren't required to follow it, and MoS isn't likely to be changed by it, any more than it is by The Canadian Style and other "nationalist" guides. The principal value in these is identifying spelling and vocabulary differences, not trying to derive grammatical or punctuation "rules", which are more dependent on target publishing market than anything else. Actual Australians' opinions on the merits of the government book, and their willingness to go along with it, vary widely. There are also alternatives, e.g. The Cambridge Australian English Style Guide, adapted from the UK one by its original editor, and diverging very little between these versions. I have a copy of the most recent editions (that I'm aware of) of both of these, at painful shipping expense (exceeded the cover price of the books). Nothing in them that I've seen suggests .au English is so different from .uk English in formal, written form that they're incompatible enough to warrant big template warnings about which ENGVAR is used, so that British people don't accidentally to Briticisation violence to an Australian article or vice versa. To the extent any non-vocabulary-trend differences can be identified at all, they're actually all covered by the divergences between various competing British style guides. That is, the .au ones do not seem to have hit upon anything "uniquely Australian". If they have, it's so minor and obscure it's unlikely to affect WP editing. Any fiddling with commas and such is much more likely to be either a) editorial judgement based on writing preferences that pre-date the .au govt. book, or b) MoS compliance. The important dialectal differences between Commonwealth varieties (aside from Canadian, which is a mish-mash of American and British with some French influences) are mostly a matter of regional-culture vocabulary, and most of those are colloquial. Same goes with divergence of Irish English and whatnot from English English. If any group of dialects was poised to take off in its own direction (in a formal not just colloquial register) any time soon, it was probably the South Asian cluster, since there are actual grammatical differences that seem to be evolving, though these too are widely regarded as colloquial at present (e.g. "The software allows to edit PDFs.", a dropping of the verb's object with which we're all familiar via Asian-sourced technical documentation). But a written divergence on the scale of the historical US<UK split is not likely to happen to South Asian English in our lifetimes after all. Nor is the already-wide colloquial split between British English proper and the English of the British and formerly-British Caribbean likely to transform into a clearly distinct formal Caribbean English. The Internet has not only slowed dialectal divergence, it's erasing some bits of it, and is even increasing cross-dialectal assimilation of innovations at all levels. For example, aside from noting that British slang like "gingers" for "red-haired people" sometimes becomes assimilated almost overnight into US English via easy availability of popular UK TV shows over the Internet, I've also observed a sharp increase in object-free "allows to" in American and British technical writing, inherited directly from South Asian material over just the last five years or so [the vector probably being "app markets"], though still largely confined to product documentation and marketing. But neither "gingers" nor "allows to" are encyclopedic writing matters, being too colloquial. The real ENGVAR disputes on WP are usually around mass-conversion (or proposed conversion) of American -ize / -or / -er / -ile / Dr. patterns to or from Commonwealth/British -ise / -our / -re / -ilst / Dr (or Oxford-variant -ize / -our / -re / -ilst / Dr ), and similar "you're doing it all wrong" dialect whitewashing. I think this still gives us basically three global dialect clusters we need concern ourselves about at the templating level: 1) US; 2) British/Commonwealth [ignoring the exact politico-legal definition of Commonwealth of Nations membership], with Oxford variant, and 3) Canadian, to the extent that .ca usage has finally more-or-less settled on an -ize / -our / -re / -ile / Dr. hybrid after numerous national surveys have brought about increased consistency in .ca style guides over the last generation, though not without controversy (especially over Dr. versus Dr and -ize versus -ise, but with near unanimity on how to spell colour and theatre, and no preference for whilst).

 — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  05:28, 4 November 2016 (UTC)

Possessives of scientific Latin names

I notice that some Wikipedia articles attempt to apostrophize Latin taxonomic names (e.g., "Salix alba's leaves" rather than "the leaves of Salix alba.") The latter is favored by scientific literature (e.g., Animal Diversity Web). The apostrophe creates a conflict between English and Latin syntax (alba is an adjective) and can result in absurd constructions such as Rattus osgoodi's where osgoodi is already a possessive (Osgood's rat). If there is agreement that such a guideline is desirable, where in the style manual could it be placed?

Ecol53 (talk) 02:44, 3 November 2016 (UTC)

• I support discouraging English-style possessive form on Latin words. Where it goes, I have no opinion. Dicklyon (talk) 03:07, 3 November 2016 (UTC)
• As usual, I'd like to see evidence that this is an actual problem in actual articles, and that editors have not been able to work this out for themselves without additonal MOSBLOAT. EEng 03:18, 3 November 2016 (UTC)

• Consensus formation on common-sense matters of encyclopedic writing doesn't require "proof" of some serious, widespread problem, only agreement that an idea is poor (or good) and should be mentioned. Either high-quality sources do or do not avoid English possessives tacked onto Latin names as a best-practices matter. That is the point to which evidence applies, and evidence has been provided both above and below that they do avoid it. What is your counter-evidence?  :-)  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  09:18, 3 November 2016 (UTC)

• Support discouraging English possessive suffixes on New Latin taxons, when used as such: of [the] felidae not feldae's. Does not apply when the common name in regular English coincides with it (gorilla, mastodon, lynx, caracal, etc. – there are many in all branches of biological taxonomy) if the name is being used in that spot in the plain-English way. Also does not apply to Latin-derived English words: since felids' divergence from canids.

  Source: I've pored over Scientific Style and Format (8th ed.), our go-to source off WP for scientific writing rules.

  • It has this to say (§ 22.2.3.1): "Genus names and specific epithets and names may not actually be Latin words, but they are treated as if they were and they have Latin endings. [Capitalization stuff elided] Apply these conventions wherever a species name is used, including running text, titles, tables, indexes, and dictionary entry terms." Throughout, it illustrates the "of X" form, never "X's". Hint: 's is not a "Latin ending", it's an English one.
  • It also does not permit English plurals to be tacked on (§ 22.2.3.6): "Names of genera do not have plural forms. If reference is made to a group of species in one genus, write the genus name followed by the abbreviation for 'species' (spp.): ... Iris spp. not Irises ... Similarly, the binomial name is always singular: Escherichia coli was ... but E. coli strains were" (that last illustrating an add-on modifier alternative to the "of X" style. I also comments that some object to this adjectival use of a binomial (i.e., would prefer "strains of E. coli"), but says the adjectival use "seems to be gaining acceptance".
  • I see no evidence in SSaF that it has any problem with English suffixes added to Latin- or Greek-derived words that have been assimilated into English (e.g., it would not formally object to "her tibia's unusual growth", though I can't find any examples of such a construction in there, probably because it's sloppy-looking writing, of the kind even our own editors would usually avoid. It does use Latin plurals for Latin technical terms, e.g. "supernovae", not "supernovas", but does not appear to push this to extremes, and it always says to follow the style guide of the publisher. So, if a journal expected "indexes" instead of "indices" then SSaF would have nothing to say about that. Likewise, if our own MoS guidelines have some rules that don't agree with that style manual, its authors' heads would not explode.
  • SSaF is consistently applying the "of X" style (or modifier circumlocutions) rather than possessive suffixes to: a) taxonomic terms, and b) things that would be awkward when read aloud (e.g., use "of Dr. Cruces" not "Dr. Cruces's" and definitely not "Dr. Cruces' "), and, from what I can tell, c) technical terms generally where something like "her tibia's unusual growth" seems amateurish. It also recommends d) abandoning possessives for eponymic names, e.g. preferring "Crohn disease" and "the Newtonian laws of motion" rather than "Crohn's disease" and "Newton's laws of motion", but it recognizes that this is an uphill attempt to change a lot of pre-established usage (what WP could call the WP:COMMONNAMEs) to a better, less ambiguous practice.
  • SSaF is also clearly drawing the same distinction I just did above about use of a name as a taxon and use of the same name as a vernacular term (§ 22.2.3.6), in reference to the "Iris spp." versus "Irises" material just quoted above: "note that Iris here is a genus name, not a common name, as indicated by the italic and capitalized first letter".

 — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  09:18, 3 November 2016 (UTC)

• This is the handbook of the US-based Council of Science Editors. I have a copy of the 8th ed. It's very good. Tony (talk) 06:59, 4 November 2016 (UTC)
  • It's international, just US-published. Previous editions were published in the UK (and it was originally the Council of Biology Editors before they expanded and included the physical sciences). I don't want anyone to think it's some "American thing"; we've had too much nationalistic punditry here over the last couple of years.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  12:26, 7 November 2016 (UTC)

Minor error in MOS:DASH

When one of the elements in a construction divided by an en dash contains a space, the en dash is spaced: Christmas Day – New Year's Eve. We borrowed this rule directly from Chicago Manual of Style and other academic style guides, and CMoS says this explicitly. We didn't quite integrate it clearly, since we're not consistently applying this throughout, and later provide incorrect examples: New York–Los Angeles and Seifert–van Kampen. These should be corrected to New York – Los Angeles and Seifert – van Kampen, and the note about spacing made more general. It's presently worded as if it only pertains to temporal ranges, but that cannot have really been the intent, since it's confusing in both being inconsistent and in being hard to parse. I don't know anyone who actually treats it the New York–Los Angeles way, and it becomes clear why when you see a complex example with less universally recognizable parts as major cities, e.g. a melodic punk – progressive rock fusion band, which would be hard to parse as a melodic punk–progressive rock fusion band, which implies a direct relationship between just the "punk" and "progressive" elements, and suggests an incorrect meaning of "a melodic, rock fusion band with a punk–progressive sound" (it's wrong twice over because a) punk and melodic punk are not the same thing, b) progressive applies to multiple genres, e.g. progressive metal, and c) it's not WP's place to declare a band to be melodic). The relationship is actually between "melodic punk" and "progressive rock", which are discrete entities (well-defined genres) with compound but non-hyphenated names, a fact not apparent to those who are not popular music experts. The point becomes even clearer with a more complex example: a futurepop – techno-industrial – goa trance album which is rendered into confusing gibberish as a futurepop–techno-industrial–goa trance album. PS: I think this incomplete integration of the rule happened because it was first introduced into MOS:NUM, where only numeric uses were under consideration, and then back-ported to MoS-main without sufficient integration work.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  07:52, 3 November 2016 (UTC)

I completely disagree with what you're saying. I don't anyone who would treat it the New York – Los Angeles way; to me, that's an eyesore and hard to parse. Also, I can't see any sense in your point(s) about those musical descriptions. The use of an unspaced en does not imply a direct relationship between just the "punk" and "progressive" elements in that example – a hyphen would do that. In this and other examples, the solution could well be to reword the description and so avoid a truckload of compound adjectives. Your alternative, to introduce spaces around the en, translates to a regular dash, making it utterly confusing. Similarly, a futurepop – techno-industrial – goa trance album reads to me as if "techno-industrial" is in some way an alternative term or a definition of futurepop. I'm sorry but many of us here do not live in the world of the Chicago Manual of Style or "other academic style guides", and nor should Wikipedia adopt something that's quite alien to English speakers/writers who never see those style points in action. JG66 (talk) 08:21, 3 November 2016 (UTC)

'Use of an unspaced en does not imply a direct relationship between just the "punk" and "progressive" elements in that example – a hyphen would do that.' Nope. Please actually read MOS:HYPHEN and MOS:DASH, then revisit this discussion when you've absorbed it better. Hyphens do not indicate such a relationship at all. (See in particular: "In some cases, like diode–transistor logic, the independent status of the linked elements requires an en dash instead of a hyphen.") Hyphens used with non-fused prefixes/suffixes ("Franco-Italian", "techno-industrial", "Kafka-esque"), to link compound modifiers ("a well-behaved child"), and for double-barreled surnames (one entity with a complex name, not a relationship between two or more entities).

Whether you prefer and "live in the world of" CMoS and other academic style guides is of no concern here; you can write any way you want on your own blog. WP has its own style manual, based almost entirely on academic and book-publishing style guides (because an encyclopedic is an educational mega-book). It is a guideline with which you're expected to comply [or at least not monkey-wrench its application by others ^*], just as you would comply with that of the New York Times if you wrote an article for them. [^* Actually, no one cares if anyone complies with MoS when they add content, since we want content more than we want consistency, and consistency can be worked in later by editors who care about that aspect of WP's quality. MoS is principally for cleanup editing, and new editors generally do not, and are not expected to, read all of it. It's a reference work, primarily for avoidance and resolution of style disputes, not a law book.]  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  10:12, 3 November 2016 (UTC)

Oh stop being such a pompous dickhead. To repeat: Your alternative, to introduce spaces around the en, translates to a regular dash, making it utterly confusing. Similarly, a futurepop – techno-industrial – goa trance album reads … as if "techno-industrial" is in some way an alternative term or a definition of future pop.

Yes, I or anyone can write any way we wish to on a blog. But you could get your kicks compiling and safeguarding your own, private manual of style elsewhere, instead of attempting to own this one and constantly encouraging a division between its contents and what editors are actually using across the encyclopaedia. There is no need for this document at all but for the articles. You'd have to do some writing (rather permanent sentry duty here) to appreciate that. JG66 (talk) 11:25, 3 November 2016 (UTC)

"Someone pointed out I was wrong about hyphens, so I'm going to throw a tantrum, call names, and make accusations that don't even make sense given that my target has been almost entirely absent from this page since September, working on articles, templates, and RfC resolution". [clap, clap].  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  15:54, 3 November 2016 (UTC)

No, more like: "Someone pointed out I was wrong about hyphens and then, conveniently, completely ignored the majority of what I was saying, and has continually demonstrated himself to be a control freak regarding this Manual of Style …" JG66 (talk) 16:07, 3 November 2016 (UTC)

Not taking the bait. Please see WP:CIVIL, WP:NPA, WP:ASPERSIONS. More substantively, when all we have is a handful of glyphs, and all of them are operator-overloaded for multiple purposes, no solution can be 100% perfect for every possible construction, as far as ambiguity-free interpretation goes. The best we can do is have it make the most sense to the most people the largest percentage of the time, and having a consistent approach is the main way to do that. A "space it this time, but not that time" pair of conflicting rules, when the two circumstances are functionally identical, is a very unhelpful form of inconsistency.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  16:09, 3 November 2016 (UTC)

S, I think that if you go back to the 2011 big dash discussion, you'll find that this was explicitly considered and rejected; not an oversight. Style guides differ on this. Dicklyon (talk) 15:26, 3 November 2016 (UTC)

Well, style guides differ on everything. What's the actual rationale for approaching this so inconsistently? If there's a good one, I might agree with it, but if there's not, we generally get rid of the inconsistencies since they just lead to squabbling and confusion.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  15:54, 3 November 2016 (UTC)

@Dicklyon: Would you mind providing a link to the 2011 discussion. I'm sure that if it's so abhorrent to a certain "editor" here to return to past MoS issues, such as consensus regarding MOS:LQ, that any 2011 discussion on this use of ens will also suffice. JG66 (talk) 16:07, 3 November 2016 (UTC)

Please drop the childish public [member]-waving. I get it; you don't like me. You don't need to reiterate this in different words every time you reach for the keyboard. You're just acting obnoxious and illogical now (and hopefully it due to lack of coffee or something and not your usual approach to anyone disagreeing with you). When I ask Dicklyon for the rationale(s), I'm obviously meaning with particular reference to the 2011 discussion he's thinking of.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  16:26, 3 November 2016 (UTC)

Well, you just beat me to it: I was about to strike part of/reword that comment of mine above. I apologise for my tone here, but I have seen you consistently batting away productive editors and article writers on this talk page as if they're flies. I should say also, I did like – I was relieved by – much of what you've suggested in response to the MOS:LQ issue raised again recently, because it's long been a darn nuisance trying to apply LQ on Wikipedia but finding that wording in the MOS link is inadequate.

But look, are you really saying you're not attempting to overturn or skirt around the rejected spaced-en usage that Dicklyon mentioned? I'm sorry, but in your reply to him, it most definitely appears that you are. JG66 (talk) 16:42, 3 November 2016 (UTC)

@JG66: Thanks, and sorry if I came off as dismissive. Overturn? Skirt around? I'm asking to revisit the rationale for some fine details in the wording in this section because it appears to have cognitive dissonance and we haven't looked closely at its wording in a long time, and this dissonance has caused an issue at an ongoing RM. It's actually very much like the LQ discussion above; we had not closely examined the exact wording in a years, only dealt with perennial ranting to delete the guideline in question, and the same pattern has been around MOS:DASH, which various editors also like to rattle swords at. In both cases, some wording tweaks may resolve the issues.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  18:08, 3 November 2016 (UTC)

• I largely agree with SMcCandilish's line, I think, but I'm in a rush right now for Signpost publication (the usual pain), and need to read the long thread later. But what I can say is that there was strong agreement at the original RFC on spacing the dash in internally spaced dates; a few scientists strongly objected to the open spacing of Seifert – van Kampen (not often seen in the literature was their point – maybe they have a point – although one reason we have MOS is that the outside literature is usually chaotic WRT such matters, and might I say, CMOS doesn't always obey its own rules, sigh). Another issue raised was the potential for confusion with the spaced en dash as interruptor on clause/phrase level, which I have some sympathy for. I recall arguments objecting to the glueing together of internal elements only, where either or both sides of the dash have multiple (spaced elements); I have sympathy for that too, and it certainly won the day WRT dates. We should consider this matter further. Tony (talk) 04:07, 4 November 2016 (UTC)

Review the 2011 discussion starting here. You might need to do more searching to find exactly how this was resolved, but it certainly did get discussed in depth. I don't see SMcCandlish there, so it's not surprising that he was unaware of it, or that there would be a strong other side to his point. And I have no particular objection if people want to re-open this question and maybe decide differently. I just don't want it to be seen as an oversight; it was deliberate. Dicklyon (talk) 04:17, 4 November 2016 (UTC) And reviewing that, I must say that I really do miss Noetica, Kwami, and JeffConrad. Great editors. Dicklyon (talk) 04:21, 4 November 2016 (UTC)

I'll definitely raise a glass to our missing friends! Anyway, I think that discussion must have taken place during one of my extended wikibreaks.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  05:42, 4 November 2016 (UTC)

• Ah, the edit conflict saved me from stating a few (now) redundant points. Thanks – everyone – for the above. I am concerned about the potential for confusion between this use of spaced ens and when an article already uses spaced ens as dashes. When ems are the chosen type of dash, this wouldn't be much of an issue, of course. JG66 (talk) 05:28, 4 November 2016 (UTC)

We would definitely need to cover that if we did anything here. Might even need to cover it anyway, since the use of spaced en dashes in temporal and numeric ranges can still have the effect JG66 is concerned about. Then again, the ambiguity is most likely to arise in tripartite constructions (foo bar – baz bar – quux bar), and these are quite uncommon. I'm skeptical any instance of one cannot be written to not use a dash-based construction in the first place. If it came to it, we could simply say outright to rewrite such constructions to not use dashes, because of the ambiguity issue.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  05:42, 4 November 2016 (UTC)

Use of en dashes in the Bibleverse template

Regarding a specific example in MOS:ENDASH:

Do not change hyphens to dashes in filenames, URLs or templates like {{Bibleverse}}, which formats verse ranges into URLs.

(Emphasis added.) In my experience with {{Bibleverse}}, en dashes have no effect on the URLs because the URLs only link to the first verse in a range. E.g., there is no effective difference between Genesis 1:1–2 and Genesis 1:1–2—the same URL (https://en.wikisource.org/wiki/Bible_(King_James)/Genesis#1:1 ) is generated in each instance. I’m not familiar with other templates, but this may also be the case elsewhere.

May we reword the example to allow en dashes with {{Bibleverse}}, and any other templates that are unaffected by the inclusion of en dashes? —DocWatson42 (talk) 05:50, 4 November 2016 (UTC)

Just as long as the output/display is en dashes for those ranges. Tony (talk) 06:57, 4 November 2016 (UTC)

Right. That template-specific note was about template output breakage. We should not delete the note, but replace it with an example to which it still applies.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  12:28, 7 November 2016 (UTC)

And when someone does that, they need to say something clearer than "templates like foo, which does bar". How is someone supposed to know which templates are "like" the example template? Like how? EEng 01:53, 8 November 2016 (UTC)

The template documentation says "Use a hyphen, not a dash, to separate ranges. The dash does not work in all operating system and browser combinations." Is the second sentence correct or not? Mr Stephen (talk) 08:48, 8 November 2016 (UTC)

One template that the use of an en dash does break is {{Convert}}, but in that case the hyphen used to indicate a range of values is automatically (ahem) converted to an en dash in the output.—DocWatson42 (talk) 03:29, 10 November 2016 (UTC)

Page move discussion

There is a relevant style/title discussion @ Talk:Mk 14 Enhanced Battle Rifle. Primergrey (talk) 02:16, 7 November 2016 (UTC)

An MoS talk page has been redirected to a wikiproject

I just noticed that Wikipedia talk:Manual of Style/Military history is redirecting to Wikipedia talk:WikiProject Military history. This strikes me as wholly inappropriate for something that has been designated a site-wide guideline and part of MoS. As far as I know it is the only MoS talk page to which such a thing has been done. I would propose that it be given its own actual talk page, per standard operating procedure. (An alternative would be considering the Wikipedia:Manual of Style/Military history page itself to be a wikiproject advice essay and moving it to something like Wikipedia:WikiProject Military history/Style advice, but I doubt that would be a popular option.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  12:56, 7 November 2016 (UTC)

PS: The guideline also opens with the wording "The Military history WikiProject's style guide is ..." which is also inappropriate. Either it's a Wikipedia guideline, or it's a wikiproject advice essay. There is no such thing as a wikiproject-controlled page that's a guideline. Even WP:BLP, WP:BIO, and MOS:BIO are not "claim-staked" by WP:WikiProject Biography, other than having a declaration by talk-page banner that they're within that wikiproject's scope of interest. Other more topical MoS pages like MOS:JAPAN, MOS:ISLAM, etc., also make no such wikiproject "ownership" claims. [I did find one other that does, MOS:COMICS, but it has been slated for revision and cleanup for over a year, because it has naming convention stuff commingled into it, needs to split into separate MOS and NC pages, and has been the subject of a lot of back-and-forth squabbling on its talk page about its specifics, probably more so than any other topical MOS page in recent memory. The MOS:MIL page is under no such cloud of "how do we fix this thing?" turmoil.]

I would suggest that the compromise for the latter issue is to take the approach used at MOS:CUE, which begins with "This is a style guide for articles that come within the scope of WikiProject Cue sports". This clarifies the scope of the guideline, "advertises" the wikiproject to potentially interested editors, yet makes no inappropriate insinuation of special authority imbued in a particular topic interest group of editors.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  13:33, 7 November 2016 (UTC)

Agree on both counts: MoS talk page ought not redirect to WikiProject talk page, and MoS guidelines ought not declare themselves as "WikiProject's style guide".

The wording used in MOS:CUE is OK, but not ideal. MOS ought not depend on WikiProjects to define the scope of a particular guide. I suggest: This is a style guide for articles that come within the scope of WikiProject Cue sports about cue sports. The talk page includes a link to the WikiProject. Mitch Ames (talk) 01:39, 8 November 2016 (UTC)

I also agree that MOS talk pages should not just redirect to a WikiProject. One reason being, while members of a WikiProject doubtless have a lot of useful knowledge, they may be too close to the subject to be the only arbiter of style and need to work things out with regular editors. For instance, if you are well versed in subject X (as most members of WikiProject X probably are) there may well be certain style conventions, used when knowledgeable people write about the subject, that are second nature to you, but which are not necessarily best for our general readership. It's now 3-0 against the redirect so I went ahead and deleted it. Herostratus (talk) 16:22, 10 November 2016 (UTC)

I've also edited MOS:CUE per my suggestion above. Mitch Ames (talk) 01:05, 11 November 2016 (UTC)

G'day, I had a go reworking the military history MOS page. This is my edit: [3] Please let me know if there are any concerns and suggestions for further improvements. Regards, AustralianRupert (talk) 01:14, 11 November 2016 (UTC)

Display Resolutions

Would it be possible to add a specific clause addressing the notation for display resolutions? There are some editors arguing that the only acceptable forms are the following:

• 1920x1080 (letter x unspaced)
• 1920 pixels × 1080 pixels (multiplication sign with spacing and units)

and that any other forms, such as:

• 1920 x 1080 (letter x with space)
• 1920 × 1080 (multiplication sign with space)
• 1920×1080 (multiplication sign unspaced)
• (I don't agree that all three of these should be accepted, I'm just giving examples of alternate styles people have used on here which have all been declared as a violation of the MOS by some)

are in fact all prohibited by the MOS, due to the following clauses:

• "The letter x should not be used to indicate multiplication, but it is used (unspaced) as the substitute for "by" in terms such as 4x4."
• "When dimensions are given, each number should be followed by a unit name or symbol (e.g., write 1 m × 3 m × 6 m, not 1 × 3 × 6 m)."

I would like to note a reminder at this time that I am not arguing about what the MOS currently says, I am asking for a change to the MOS to address this topic specifically. Since "1920x1080" is read aloud as "1920-by-1080" and represents the dimensions of a display (in pixels, generally), I am forced to agree the MOS does currently endorse only those two forms explicitly. However, these are essentially the two least readable forms. Either using a multiplication sign or adding spaces (or both) improves readability, but neither is explicitly allowed unless units are also included, which decreases readability again, is cumbersome when discussing many resolutions in a sentence, and is not consistent with real-world usage of these terms (it is rare for one to state the units when writing a resolution).

My personal feeling is that the multiplication sign with spaces, but without units (i.e. 1920 × 1080), should be explicitly allowed for display resolutions. The combination of spaces and multiplication sign is the most readable and most professional form in my opinion. The spaces are also consistent with the style set by the MOS for mathematical usage of the multiplication sign, just without the requirement for units after the numbers when dealing with display resolutions (which is consistent with how resolutions are written and encountered normally). I don't think that the "1920x1080" unspaced letter x form should be explicitly prohibited for resolutions (though I would not mind), I just think this alternative more professional form should be explicitly allowed by the MOS for resolutions. It would allow a more readable style without resorting to the cumbersome "full form" with both spaces and units. GlenwingKyros (talk) 05:39, 9 November 2016 (UTC)

I tend to agree that "the multiplication sign with spaces, but without units (i.e. 1920 × 1080), should be explicitly allowed for display resolutions". Dicklyon (talk) 05:48, 9 November 2016 (UTC)

• Can I suggest you take this to Wikipedia_talk:MOSNUM? Somewhere in its archive (within the last four years) is a huge discussion of this. EEng 06:41, 9 November 2016 (UTC)

Is this what you are thinking of? (Other options.)—DocWatson42 (talk) 03:36, 10 November 2016 (UTC)

No, not those. It went on interminably about screen resolutions, pixels, and whatnot. It was YUGE (to quote Herr Trump). I spent a little time looking but couldn't find it. and finally found it: Wikipedia_talk:Manual_of_Style/Dates_and_numbers/Archive_146#Revisit:_the_use_of_.22.C3.97.22_and_.22x.22_for_indicating_.22by.22_in_arrays_and_dimensions. Success! Bow down to me!

Again, if this thread is to go on it should be transferred to Talk MOSDATE. EEng 06:56, 10 November 2016 (UTC)

Proposal to stop supporting pull quotes

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.

(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 WP:MOS page, change 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 {{quote}} template, or between a pair of <blockquote>...</blockquote> HTML tags. The template also provides parameters for attribution. Do not enclose block quotations in quotation marks (and especially avoid decorative quotation marks in normal use, such as those provided by 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 {{Pull quote}} to {{Cquote}} to and {{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 is meant for pull quotes, the visually distinctive repetition of text that is already present on the same page. In most cases, this is not appropriate for use in encyclopedia articles. The Manual of Style guidelines for block quotations recommend formatting block quotations using the {{Quote}} template or the HTML <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, {{Pull quote}} 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, {{Rquote}} (with decorative quotation marks) or {{Quote box}} (framed) can be used to set the quote off to either the right or left as in a magazine sidebar. This can be effective on essay pages and 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}}: 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)

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" 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)

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)