Misplaced Pages

talk:Manual of Style: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 22:58, 7 September 2017 view sourceSMcCandlish (talk | contribs)Autopatrolled, Extended confirmed users, Page movers, File movers, New page reviewers, Pending changes reviewers, Rollbackers, Template editors201,791 edits Extended discussion of obsolescence RfC: yep← Previous edit Revision as of 00:51, 8 September 2017 view source SMcCandlish (talk | contribs)Autopatrolled, Extended confirmed users, Page movers, File movers, New page reviewers, Pending changes reviewers, Rollbackers, Template editors201,791 edits Comics MoS: Not an ENGVAR matter. Some further examination of usage patterns off- and on-site, and addl. sources, including academic ones.Next edit →
Line 27: Line 27:
:::::I think it's a US/UK division. The US tends to use a hash (#), the UK tends to use "no". For instance you would never see a headline "Talks at #10" in the UK, whereas "No 10" is immediately obvious as referring to the Prime Minister's residence. ] (]) 16:13, 7 September 2017 (UTC) :::::I think it's a US/UK division. The US tends to use a hash (#), the UK tends to use "no". For instance you would never see a headline "Talks at #10" in the UK, whereas "No 10" is immediately obvious as referring to the Prime Minister's residence. ] (]) 16:13, 7 September 2017 (UTC)
::::::Yes. That does appear to be the case. And the full point afterwards seems to be heading for extinction. –] ] 19:32, 7 September 2017 (UTC) ::::::Yes. That does appear to be the case. And the full point afterwards seems to be heading for extinction. –] ] 19:32, 7 September 2017 (UTC)
::::::: It's not an ENGVAR matter, because there's neither a "clean break" internationally, nor intra-national consistency. To look at this Downing side matter in detail: No 10 is a proper name in this context, not just an address; it's used as a metaphoric (technically metonymic) stand-in for "the British prime minister, or the collective office thereof", in the same way that "White House" and occasionally "1600 Pennsylvania Avenue" are used to mean "the US President, or the administration thereof". No 10 Downing Street is also sometimes just called "10 Downing Street" or even (mostly in headlines) "Downing Street" , and might even turn up as "10 Downing" or even just "Downing" if the context is clear enough. "Street" is also sometimes abbreviated. If the first bit is included, it would be rendered "No." in US publications, though they're not apt to use it as a PM reference, since it's too opaque to their audience; but it's the typical abbreviation of "number" in American journalism, with capitalization or not being a matter of house style, though it'll always be capitalized for an address. American address style doesn't use "No." or "#" for street addresses, though often uses one or the other (usually "#") for unit numbers if they're not identified more specifically ("Apt. 12", "Suite 200").<p><small>Side comment: (on topic: uses "No 10" by itself in reference to the PM's office) makes me wonder if we can have an encyclopedic article on the ]. People keep writing about them, going all the way back to the early 20th century, as I discovered while working on the article ]. Heh. We have some separate articles on various US presidents' dogs, but I wonder if they wouldn't be better combined into a single piece on presidential pooches. {end whimsy mode}</small></p><p>In more general terms, the supposition that "he US tends to use a hash (#)" isn't accurate, aside from maybe how individuals write online. Some British writers (the ones following Oxford rather than British-press style about when to drop "." from abbreviations) will also spell it "No." or sometimes (not for an address) "no." The British press are not unanimous in their "death to full points" march, anyway; see "No. 1" used by the BBC (pp. 76, 96). One can also find British publications actually using the numero symbol, if you dig around, but it seems to be only as a layout decoration thing, e.g. the front cover of the . You can find American book covers also using the symbol, but it's rare in running prose. There are also weird cases, e.g. "No.1" with no space but they also appear to be marketing layout gimmickery on covers, only (the same book using "No. 1" internally).</p><p>To get back to "#" and comics: RS about comics usually use "#", and the general public does, too. Journalism tends to use "no." or "No.", just because they have house styles against "#" in general, but they rarely write about specific issues of comics, so they don't have a normative effect on the usage in that context. A book entirely about British comics uses "#" throughout (though the publisher is US-based, and the book was actually printed in Canada), for what that's worth. Virtually all books on comics do, even those {{em|not}} produced by comics publishers (e.g. art "coffee table" books from Taschen, etc.). The non-comics-publisher books on comics are probably the most reliable sources from a WP perspective, being independent of the subject and fairly academic in intent and style. Examples: , , , (all from first page of "comics art" Google Books search). Many of them more literally are academic (art history/philosophy works intended for a university audience). WP's allowance of "#" for comics edges toward a ] case only on first glance. It's missing the "violates the ]" criterion of an SSF – it's not confusing to anyone, and doesn't produce a "WTF?" reaction in the minds of readers unfamiliar with the topic, because "#" is one of the long-standing, standardized ways to abbreviate "number" in English. While it's not favored by news publishers, it is actually also fairly common in writing about sports (e.g. league and tournament rankings ) and entertainment (e.g. pop singles charts &#91;see "Discover which song was #1 the day you were born" sidebar&#93;, and movie box office sales ), for example, not just comics. But it's really, really common for comics. Another point against an SSF determination is that there's no hint of a camp of specialists trying to tell WP how it has to write, and tendentiously fighting against resistance from all over WP. WP's been using # for comics all along, and virtually no one has been objecting.</p><p>Having reconsidered it for half a month, I still conclude that we wouldn't gain anything by trying to "ban" the # symbol for comics; it would require a zillion mostly manual edits, would lead to a "wikirevolt" of comics-focused editors, and would provide ammo to anti-MoS editors, who are presently very few in number. Let's not breed more of them. In effect, such a rule would be like telling biology editors they can't italicize the scientific names of organisms here; the style isn't just what they're used to as specialists, it's what everyone's at least a little familiar with, and it doesn't surprise anyone, though you can probably find someone somewhere who doesn't like it. I'm normally "Captain Consistency" (issue #1 out soon!), but I just can't see a good case for hyper-consistency against "#", especially since we actually {{em|don't have}} consistency on "no.", "No.", "no", "No", "number", and "Number" in general, even for things like addresses and rankings. If we were going to get more consistent, start with that mess first.<br /><span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 00:51, 8 September 2017 (UTC)</p>


== Using "Sir" as a pre-nominal == == Using "Sir" as a pre-nominal ==

Revision as of 00:51, 8 September 2017

This is the talk page for discussing improvements to the Manual of Style page.
Shortcut
Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228Auto-archiving period: 7 days 
The contentious topics procedure applies to this page. This page is related to the English Misplaced Pages Manual of Style and article titles policy, which has been designated as a contentious topic.

Editors who repeatedly or seriously fail to adhere to the purpose of Misplaced Pages, any expected standards of behaviour, or any normal editorial process may be blocked or restricted by an administrator. Editors are advised to familiarise themselves with the contentious topics procedures before editing this page.

For a list of suggested abbreviations for referring to style guides, see this page.
? faq page Frequently asked questions

Misplaced Pages's Manual of Style contains some conventions that differ from those in some other, well-known style guides and from what is often taught in schools. Misplaced Pages's editors have discussed these conventions in great detail and have reached consensus that these conventions serve our purposes best. New contributors are advised to check the FAQ and the archives to see if their concern has already been discussed.

Why does the Manual of Style recommend straight (keyboard-style) instead of curly (typographic) quotation marks and apostrophes (i.e., the characters " and ', instead of “, ”, ‘, and ’)‍? Users may only know how to type in straight quotes (such as " and ') when searching for text within a page or when editing. Not all Web browsers find curly quotes when users type straight quotes in search strings. Why does the Manual of Style recommend logical quotation? This system is preferred because Misplaced Pages, as an international and electronic encyclopedia, has specific needs better addressed by logical quotation than by the other styles, despite the tendency of externally published style guides to recommend the latter. These include the distinct typesetters' style (often called American, though not limited to the US), and the various British/Commonwealth styles, which are superficially similar to logical quotation but have some characteristics of typesetters' style. Logical quotation is more in keeping with the principle of minimal change to quotations, and is less prone to misquotation, ambiguity, and the introduction of errors in subsequent editing, than the alternatives. Logical quotation was adopted in 2005, and has been the subject of perennial debate that has not changed this consensus. Why does the Manual of Style differentiate the hyphen (-), en dash (–), em dash (—), and minus sign (−)? Appropriate use of hyphens and dashes is as much a part of literate, easy-to-read writing as are correct spelling and capitalization. The "Insert" editing tools directly below the Misplaced Pages editing window provide immediate access to all these characters. Why does the Manual of Style recommend apostrophe+s for singular possessive of names ending in s? Most modern style guides treat names ending with s just like other singular nouns when forming the possessive. The few that do not propose mutually contradictory alternatives. Numerous discussions have led to the current MoS guidance (see discussions of 2004, 2005, 2005, 2006, 2006, 2007, 2008, 2008, 2008, 2009, 2009, 2009, 2012, 2013, 2015, 2016, 2017, 2017, 2017 (the RfC establishing the present consensus), 2018, 2018, 2019, 2021, 2022). Why doesn't the Manual of Style always follow specialized practice? Although Misplaced Pages contains some highly technical content, it is written for a general audience. While specialized publications in a field, such as academic journals, are excellent sources for facts, they are not always the best sources for or examples of how to present those facts to non-experts. When adopting style recommendations from external sources, the Manual of Style incorporates a substantial number of practices from technical standards and field-specific academic style guides; however, Misplaced Pages defaults to preferring general-audience sources on style, especially when a specialized preference may conflict with most readers' expectations, and when different disciplines use conflicting styles.
This is the talk page for discussing improvements to the Manual of Style page.
Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228Auto-archiving period: 7 days 

Comics MoS

Are you aware of the stupid rule at the comics wiki-project MoS, which states that editors should use a hash rather than the numero sign. Is this not defeating the point of the MoS—consistency across the whole of WP? –Sb2001 19:59, 16 August 2017 (UTC)

It has been this way at WikiProject Comics for about a decade now on perhaps a couple thousand articles, for the same reason Projects devoted to biochemistry or other specialized fields have MOS specifics appropriate to that field. In this case, the vast, vast majority of secondary-source references reporting on comic books, as well as the industry standard itself, uses the number sign (#) rather than "No." — which, it could be argued, is less accessible than # to non-English speakers. To put it colloquially, "If it ain't broke, don't fix it." --Tenebrae (talk) 20:07, 16 August 2017 (UTC)
Yep. This was actually added into the main MoS a few years ago (at WP:Manual of Style#Number sign, maybe at my own prompting, for consistency with MOS:COMICS; I'm not sure at this late date). It should also be mentioned at MOS:ABBR for completeness there; that page doesn't presently cover abbreviations for "volume" and "number" at all. We don't like exceptions, as a general rule of thumb, but permit them when they're strongly reflected in the real-world source materials that aren't just specialist-only insider publications. While news publishers in particular do frequently use "No." or "no." in reference to comics, they're following their own house stylebooks, and news style diverges from other styles and general usage.

Throwing out the "#" style for comics wouldn't seem to buy us anything at all. Everyone understands what "#1" means just as everyone understands what "No. 1" or "no. 1" mean. The "#" style is just a convention with comics. I'm in favor of retaining it, since changing it here would mean many thousands (perhaps tens of thousands) of conformance edits, while comics-oriented new editors would virtually always use # until "corrected", and it would just a pick a fight with a group of specialists when no fight is needed. That last point is why this differs from some previous "gimme an exception" cases, even ones where we did in fact clean up thousands of cases (e.g. capitalization of common names of species). The "specialist style" that comics-oriented editors have been using is not in fact a specialist style but the dominant one in the context, and isn't being fallaciously imposed here, as its use is not confusing, misleading, or otherwise inappropriate for a general audience, unlike so many "WP must write exactly the same way people with my job title do, in the material they write for each other, or I will fight WP consensus unto death" demands we deal with here. WP also doesn't use the "#" glyph in its old role as the "pound sign", sticking by rule with the ISO symbol "lb". So, yeah, "ain't broke".

While yes (and contrary to the belief of some MoS detractors) the general purpose of MoS is cross-article consistency, this is not pursued in a robotic manner against WP:Common sense. We have numerous variances that are field-specific (MOS:NUM has quite a few itself, and all the various topical MoS pages have more, though keeping them from wandering off into specalized-style-fallacy territory is a constant low-key effort. It's sufficient that articles be consistent between each other to the extent practical, within a category. What we don't want is to see half the comics articles using "#" and half of them using "No."/"no.", or worse yet for the style to wander in the same article. A good comparison is the use of v. rather than vs. in a legal context, while we use vs. in all other contexts (when versus is abbreviated at all). The real world (in English, anyway) really does prefer v. in legal cases – including in non-specialist works like newspapers – and writers/editors on things like sports really do prefer vs., even in the same publication as an article using v. for a legal case. While we could impose one spelling for "consistency obsession" reasons – as we could with "No." – that would basically be language-change activism which isn't what we're here for.
 — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  22:54, 16 August 2017 (UTC)

Why would the MOS specify the numero sign in the first place? At least where I'm from that symbol is virtually never seen. --Khajidha (talk) 13:27, 28 August 2017 (UTC)
Agreed. We're actually advising against various other obscure Unicode symbols, e.g. the one-glyph character for ... (), and the pre-superscripted character (²). Most publications that use numero do it as no. or No., not as .  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  08:32, 2 September 2017 (UTC)
Even the abbreviation "No." is pretty rare in my experience. --Khajidha (talk) 15:17, 7 September 2017 (UTC)
I think it's a US/UK division. The US tends to use a hash (#), the UK tends to use "no". For instance you would never see a headline "Talks at #10" in the UK, whereas "No 10" is immediately obvious as referring to the Prime Minister's residence. Martin of Sheffield (talk) 16:13, 7 September 2017 (UTC)
Yes. That does appear to be the case. And the full point afterwards seems to be heading for extinction. –Sb2001 19:32, 7 September 2017 (UTC)
It's not an ENGVAR matter, because there's neither a "clean break" internationally, nor intra-national consistency. To look at this Downing side matter in detail: No 10 is a proper name in this context, not just an address; it's used as a metaphoric (technically metonymic) stand-in for "the British prime minister, or the collective office thereof", in the same way that "White House" and occasionally "1600 Pennsylvania Avenue" are used to mean "the US President, or the administration thereof". No 10 Downing Street is also sometimes just called "10 Downing Street" or even (mostly in headlines) "Downing Street" , and might even turn up as "10 Downing" or even just "Downing" if the context is clear enough. "Street" is also sometimes abbreviated. If the first bit is included, it would be rendered "No." in US publications, though they're not apt to use it as a PM reference, since it's too opaque to their audience; but it's the typical abbreviation of "number" in American journalism, with capitalization or not being a matter of house style, though it'll always be capitalized for an address. American address style doesn't use "No." or "#" for street addresses, though often uses one or the other (usually "#") for unit numbers if they're not identified more specifically ("Apt. 12", "Suite 200").

Side comment: this piece (on topic: uses "No 10" by itself in reference to the PM's office) makes me wonder if we can have an encyclopedic article on the cats of 10 Downing Street. People keep writing about them, going all the way back to the early 20th century, as I discovered while working on the article Manx cat. Heh. We have some separate articles on various US presidents' dogs, but I wonder if they wouldn't be better combined into a single piece on presidential pooches. {end whimsy mode}

In more general terms, the supposition that "he US tends to use a hash (#)" isn't accurate, aside from maybe how individuals write online. Some British writers (the ones following Oxford rather than British-press style about when to drop "." from abbreviations) will also spell it "No." or sometimes (not for an address) "no." The British press are not unanimous in their "death to full points" march, anyway; see "No. 1" used by the BBC here (pp. 76, 96). One can also find British publications actually using the numero symbol, if you dig around, but it seems to be only as a layout decoration thing, e.g. the front cover of the BBC piece already cited. You can find American book covers also using the symbol, but it's rare in running prose. There are also weird cases, e.g. "No.1" with no space but they also appear to be marketing layout gimmickery on covers, only (the same book using "No. 1" internally).

To get back to "#" and comics: RS about comics usually use "#", and the general public does, too. Journalism tends to use "no." or "No.", just because they have house styles against "#" in general, but they rarely write about specific issues of comics, so they don't have a normative effect on the usage in that context. A book entirely about British comics uses "#" throughout (though the publisher is US-based, and the book was actually printed in Canada), for what that's worth. Virtually all books on comics do, even those not produced by comics publishers (e.g. art "coffee table" books from Taschen, etc.). The non-comics-publisher books on comics are probably the most reliable sources from a WP perspective, being independent of the subject and fairly academic in intent and style. Examples: , , , (all from first page of "comics art" Google Books search). Many of them more literally are academic (art history/philosophy works intended for a university audience). WP's allowance of "#" for comics edges toward a WP:Specialized-style fallacy case only on first glance. It's missing the "violates the principle of least astonishment" criterion of an SSF – it's not confusing to anyone, and doesn't produce a "WTF?" reaction in the minds of readers unfamiliar with the topic, because "#" is one of the long-standing, standardized ways to abbreviate "number" in English. While it's not favored by news publishers, it is actually also fairly common in writing about sports (e.g. league and tournament rankings ) and entertainment (e.g. pop singles charts , and movie box office sales ), for example, not just comics. But it's really, really common for comics. Another point against an SSF determination is that there's no hint of a camp of specialists trying to tell WP how it has to write, and tendentiously fighting against resistance from all over WP. WP's been using # for comics all along, and virtually no one has been objecting.

Having reconsidered it for half a month, I still conclude that we wouldn't gain anything by trying to "ban" the # symbol for comics; it would require a zillion mostly manual edits, would lead to a "wikirevolt" of comics-focused editors, and would provide ammo to anti-MoS editors, who are presently very few in number. Let's not breed more of them. In effect, such a rule would be like telling biology editors they can't italicize the scientific names of organisms here; the style isn't just what they're used to as specialists, it's what everyone's at least a little familiar with, and it doesn't surprise anyone, though you can probably find someone somewhere who doesn't like it. I'm normally "Captain Consistency" (issue #1 out soon!), but I just can't see a good case for hyper-consistency against "#", especially since we actually don't have consistency on "no.", "No.", "no", "No", "number", and "Number" in general, even for things like addresses and rankings. If we were going to get more consistent, start with that mess first.
 — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  00:51, 8 September 2017 (UTC)

Using "Sir" as a pre-nominal

Moved to WP:VPPOL#RfC: Should "Sir" and "Dame" be treated as pre-nominals?

For a few weeks now, a few editors have been removing the honorary "Sir" from the |name = parameter of {{Infobox person}} and including it in the |pre_nominal = parameter. Please see example diffs at Nigel Hawthorne, Roger Moore, John Hurt and Sean Connery, all edits without an edit summary. I have reverted 86.2.65.41 (talk · contribs · WHOIS) a couple of times for making such edits, although I have been reverted in turn as well. As far as I am aware, a knighthood is not a pre-nominal (as in The Right Honourable) but part of one's name. Articles such as Sir Winston Churchill, Sir Thomas More and other knighted politician articles are unaffected. I see that there is policy concerning WP:POSTNOM, but is there one that applies to WP:PRENOM too? Thanks.--Nevéselbert 22:40, 16 August 2017 (UTC)

I'm glad I live in the US where we don't have to worry about such folderol. But then we have Trump. EEng 22:46, 16 August 2017 (UTC)
The impetus for removing the "Sir" in the infobox probably stems from our decision to omit the "Sir" from article titles... however, I don't see that infoboxes need to have the same rules as titles. Blueboar (talk) 22:52, 16 August 2017 (UTC)
They probably should. It's surely sufficient to have it in the lead sentence. We're all aware by now that certain British/Commonwealth editors are insistent that such a title "becomes part of the name" in some magical sense, and the rest of us generally aren't buying it. More to the point, and rarely given these titles in material written for a global or even a non-UK audience (this is even more true of long-dead subjects, like Walter Raleigh and Thomas More). We should follow that off-WP trend. Our general rule is to drop any stylization preferred by a particular camp if it is not done with overwhelming consistency off-wiki by reliable, independent, general-audience sources. While this is typically applied to stylistic changes like typeface shenanigans, the principle is general and can be applied to styles and titles. After all, we are not referring to Elizabeth II as Her Royal Highness. We can also see that other sites providing comprehensive information about bio subjects are dropping Sir/Dame as well; see e.g. Judi Dench at IMDb.

Since this keeps coming up again and again, I would suggest an RfC at WP:VPPOL (or at WT:MOSBIO and advertised at VPPOL), with WT:BIO notified, to settle it permanently, or I firmly predict we'll be having this same discussion in 6 months, and 18 months, and 5 years, since we were having it before, that long ago, too.
 — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  23:06, 16 August 2017 (UTC)

As SMcCandlish points out, this discussion belongs at WT:MOSBIO, where it recurred only last month – see Request for changes to "honorific prefixes" in infoboxes there.
Please read MOS:HONORIFIC which gives specific (and correct) guidance for the honorific titles Sir, Dame, Lord and Lady: any other titles, such as Her Royal Highness are irrelevant to this discussion. — Stanning (talk) 10:19, 18 August 2017 (UTC)
Of course it should be part of the name. It's always bolded in the first line; it should be in the infobox as well. And a note to SMcCandlish: Bob Geldof is a very bad example to pick as his knighthood is honorary, so he doesn't have a title in any case! Giving him a title is completely incorrect. Neither would anyone with any knowledge of the subject ever refer to Her Majesty Elizabeth II as Her Royal Highness! Which is an honorific form of address in any case and not a title. British media sources rarely use honorifics when referring to people; they do, however, use titles. -- Necrothesp (talk) 10:39, 18 August 2017 (UTC)
I stand corrected on trivial details, and will restate what you skirted and what actually matters: The real world, outside the UK, is mostly writing Judi Dench and Winston Churchill. We should do likewise.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  18:42, 21 August 2017 (UTC)
The US entries for Judi Dench and Winston Churchill at the online Oxford Dictionary includes both "Dame" and "Sir" as part of the name.--Nevéselbert 21:21, 21 August 2017 (UTC)
Repeat: "The real world, outside the UK ...". Guess where Oxford is? What we're dealing with here is a regional style matter, and not a universally applied one even in the region (and sometimes out of it, in other parts of the Commonwealth). It's clearly optional style.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  21:28, 22 August 2017 (UTC)
Missed the bit where the website says "Home > North American English > Churchill, Sir Winston"? Then again, perhaps the US Congress should have consulted you before passing "H.R. 4374 (88th): An Act to proclaim Sir Winston Churchill an honorary citizen of the United States of America"? It is normal practice to acknowledge honours gained in a citizen's own country even if they would not be recognised in one's own. In the UK we would not strip the "Honourable" from US judges or congressmen, perhaps a little reciprocity is called for.Martin of Sheffield (talk) 22:12, 22 August 2017 (UTC)
Oxford U. Pr. is still a British publisher, one with its own house style (a very well-documented one). The US Congress is apt to use formal titles, especially with regard to foreign dignitaries. That's part of diplomacy. WP is not diplomacy. You're essentially making my point for me: "In the UK we would not strip the "Honourable" from US judges or congressmen", yet WP does so, as does most writing that is isn't diplomacy, a eulogy, a merit citation, or otherwise highly formalized or ceremonial.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  23:50, 22 August 2017 (UTC)
If they were using his full formal title, they would have said The Right Honourable Sir Winston Churchill. Note the part of it they omitted (the honorific) and the part they left in (the title). Which is what we do. It's really very simple. And you've essentially just made our point for us. Even the US Congress was able to distinguish an honorific from a title. Pity some WP editors are incapable of doing so too. -- Necrothesp (talk) 15:37, 23 August 2017 (UTC)
  • As a new editor to this discussion, it would seem strange to ignore the Sir/Dame from a name. SMcCandlish, Neve-selbert specified that it was the US entry at which they were looking. My brief research has failed to recover any results not using Sir as a pre-nominal. I do think—however—that 'Vince Cable' is used more often than 'Sir Vince Cable' (I have some much better names for him ...) on BBC television and radio coverage. I would say to stick with the Sir etc, as it is part of their name. Whilst it may not be my personal preference to allow the monarchy such power, it feels somehow 'wrong' to ignore these as part of a name. That said, I have nowhere near enough royal knowledge to give you an argument which is not largely on a WP:ILIKEIT basis. –Sb2001 23:17, 22 August 2017 (UTC)
    The fact that this keeps turning circular (my repeat rebuttal to this would be that we refer to Elizabeth II as such, not as Queen Elizabeth or Her Majesty; and that the idea "Sir/Dame is part of the name" in some special way that isn't true of other prenominals is a subjective, and primarily British and royalist, feeling, not something which can be demonstrated to be true objectively in overall use of the English language) is why I suggest this should go to an RfC. The debate is not going to end on its own, and has already continued for many years without clear resolution.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  23:55, 22 August 2017 (UTC)
    Again, you demonstrate your lack of knowledge of the subject you're pontificating about. "Queen" and "Her Majesty" aren't titles. The Queen is what she is (just as Donald Trump is the President) and Her Majesty is an honorific, just like The Honorable as applied to US judges (which is why we don't include either of them). -- Necrothesp (talk) 15:28, 23 August 2017 (UTC)
    I'm not unaware of the differences, I'm glossing over them intentionally, because for WP intents and purposes they are the same thing: something honorific prefixed to a name, which we don't do in encyclopedic writing. They're all different categories of this, but are within the category. You keep wanting to split hairs within the category, and I have no interest in doing so, nor is doing so relevant to resolution of the matter.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  20:50, 23 August 2017 (UTC)
    Another great reason to abolish the monarchy ... make life easier for Misplaced Pages editors! –Sb2001 00:06, 23 August 2017 (UTC)
    Oh really, isn't it time to drop prominent mention of "Sir" this and "Lady" that and "Lord" this? Why is WP, a supposedly neutral site, giving succour to an outmoded British class system? It's embarrassing. If you must, a discreet mention of the title somewhere in the main text bio section. Tony (talk) 10:26, 23 August 2017 (UTC)
    Because it's a fact and WP reports facts without a political agenda. It's not non-neutral to report facts or to use names by which people are known. It's a great pity that some don't seem to understand that. -- Necrothesp (talk) 15:28, 23 August 2017 (UTC)
    I cannot say that I am a fan of honours, etc, but we cannot decide when they become out-of-date. As Necrothesp says, we provide readers with factual information. We should not let out own political preferences get in the way of that. It is like we would not provide the alternative name for the health secretary on his page, because it is an opinion. Including Sir etc is not—dropping it would be. Anyway, I support SMcCandlish's proposal for this to go to RfC: we are never going to agree on something like this. And please, for heaven's sake, make it a factual debate, rather than this republican v royalist nonsense that we have going on here (as enjoyable as it may be). If nobody objects, I shall start one at WP:VPPOL; is that OK Neve-selbert? –Sb2001 16:02, 23 August 2017 (UTC)
    Sure, that's a good idea.--Nevéselbert 16:15, 23 August 2017 (UTC)
    Agreed. I would have done it myself, but I've done sufficient numbers of MoS-related RfCs in my time.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  20:50, 23 August 2017 (UTC)

Question about ENGVAR, date formats, and metric vs. imperial

I'm currently working on Children of Llullaillaco, and I just realized that I had been inconsistently using date formats so I decided to standardize on one or the other. According to ENGVAR, when there are no "close national ties" (paraphrased) to a subject, the first major contributor to the article can choose which variety of English to use. Since Latin America has no strong national ties to any variety of English (since English is not a primary language there) I've chosen American English, since I'm American so that's what I'm most comfortable working with. However, Latin America uses dmy date format, and American English uses mdy. Since English is not a primary language in Latin America, there are no strong ties to any English variety - however, am I still required to use dmy date format in this case? And if so, does that mean I cannot use American English due to the resulting internal inconsistency? (I have the same question about metric vs. imperial units - American English uses imperial but Latin America universally uses metric) Thanks, CJK09 (talk) 21:35, 28 August 2017 (UTC)

You do not need both the ENGVAR tag and the MDY tag, as they are the same, making the date tag redundant. As long as you have a {{Use dmy dates|date=August 2017}} tag at the top of the page, you are fine to go with DMY, which you should be doing due to the fact that it is the norm in that particular country. Only include the date tag if there is no ENGVAR which already covers it, ie American English = MDY, British English = DMY, etc. So, keep the ENGVAR tag, but change the date format tag to DMY.
What makes me think that it might be worth removing the Am Eng ENGVAR tag is the metric v imperial business. Articles do not need an attached ENGVAR tag; they are simply there to help editors. The Am Eng tag means that measures come in the format 'imperial (metric)', rather than 'metric (imperial)'. If you want metric on the outside, you should drop the tag. That said, I doubt that anyone will come along and change all of the metric to imperial, but there is a chance. Only worry about this part of the query if you are really bothered. It makes little difference. British articles are pretty random as to whether it is met (imp) or imp (met), as we have different norms for different things, eg miles for roads, etc, but g for weights. –Sb2001 00:21, 30 August 2017 (UTC)
I disagree with Sb2001 about date format. The concept of choosing date format according to strong national ties only applies when the ties are to an English-speaking country. If the ties are to a non-English speaking country, and you are the first major contributor, use whichever of the two formats you wish. Jc3s5h (talk) 00:26, 30 August 2017 (UTC)
I think it is a question of what English speakers in a particular country use. Most non-English speaking countries use DMY, and most transfer this into English when they use it. There are some exceptions, however. I do not have the knowledge on this topic to say what the norm is here. That should be what is applied. I was a little unclear here. –Sb2001 00:30, 30 August 2017 (UTC)
MOS:TIES states "An article on a topic that has strong ties to a particular English-speaking nation should use the (formal, not colloquial) English of that nation." Your thoughts are in conflict with the guideline. Jc3s5h (talk) 00:34, 30 August 2017 (UTC)
I do not think that that applies here, because it is not an English-speaking country. There is nothing to suggest that DMY is not formal in this particular country. I shall leave this now, as I do not wish to engage in a policy debate. I was only trying to offer the editor some help with deciding on where to go next. –Sb2001 00:43, 30 August 2017 (UTC)
I think the preceding comments miss a key point: formatting of dates is a style issue and doesn't come within the ENGVAR guideline because it is not really a component of language. While people generally use MDY in the US, this is not universal and in scientific and military articles, it would be more appropriate to use DMY (as well as 24-hour time). Here's a couple of relevant policies to consider from MOS:DATETIES:
  • Articles on topics with strong ties to a particular English-speaking country should generally use the date format most commonly used in that nation. For the United States this is (for example) July 4, 1976; for most other English-speaking countries it is 4 July 1976
  • In some topic areas the customary format differs from the usual national one: for example, articles on the modern U.S. military, including U.S. military biographical articles, use day-before-month, in accordance with U.S. military usage.
And from MOS:DATEVAR:
  • If an article has evolved using predominantly one format, the whole article should conform to it, unless there are reasons for changing it based on strong national ties to the topic or consensus on the article's talk page.
  • The date format chosen by the first major contributor in the early stages of an article should continue to be used, unless there is reason to change it based on strong national ties to the topic or consensus on the article's talk page.
I think that the quoted guidelines (especially the last one) should answer the question: since the topic has no strong tie to the US, then the existing format should be kept absent a compelling reason to change it. Simply using American English in the article doesn't mandate the use of MDY dates. AHeneen (talk) 02:42, 30 August 2017 (UTC)
Children of Llullaillaco is primarily a science article; while we don't have a formal rule about that, the above reasoning (that science generally uses DMY format) is good logic, about how English is written for a particular context. However, if it's not a primarily scientific or military article, then there is no good reason to have a mismatch between the ENGVAR and the DATEVAR; having one is virtually guaranteed to generate recurrent editwars and other disputes. Much of the purpose of these guidelines is to prevent or at least curtail territorial pissing matches between editors; some of the above reasoning is being used as an excuse to multiply and perpetuate the discord. I doubt many people will agree with the unsupported and linguistically absurd assertion "formatting of dates is a style issue and ... it is not really a component of language"; it's rather like saying that the dachshund is a kind of hound not a dog. I'm getting a strong sense of déjà vu, and believe that we've been over this before.

I'm an American who prefers DMY date format myself, but it's not my or your job or privilege to impose that preference on everyone, especially not by "I got here first" chest-beating. Consistency is preferred over claims of staked-out territory, and it is always sufficient that consensus at a particular article opts for consistency (in one direction or the other) regardless of the preference of first major contributor. None of the *VAR provisions are "thou shalt not change it" rules, just discouragements of making changes without good reason. An ENGVAR mismatch in the same article, commingling one dialect's date format with another's orthography, without some defensible rationale to do so (e.g. it's a science/military topic) is often a good reason. If it were not, then there are many thousands of "enforcements" of DMY date format in BrEng articles that you can go try to revert; good luck with that.

The "no strong ties" argument is weaker for Latin America that it would be for, say, Greece or North Korea; the most common second language learned in most of Latin America is English, and mostly the US variant; US foreign policy has a huge impact throughout the entire region; the majority of English-language reliable sources about the region are published in the US in US English. But there are historical exceptions; e.g., English is an official language in Belize, and it's more strongly British- than American-influenced. The situation is similar to the strength of "there is some connection" TIES arguments between British English and places once under British imperial control (and between American English and American-occupied places like the Philippines and Okinawa). It's a factor, even if it's not an overwhelming one.

Finally, what date format is preferred in a Latin American country that doesn't have English as an official language, or even a large-minority first language, is irrelevant here. WP is written for English-speaking users, not monoglot Spanish speakers in Nicaragua or Cuba. We have these *VAR rules to a) present consistent material to our readers and b) to forestall style fights.
 — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  15:46, 1 September 2017 (UTC)

I agree with SMcCandlish. I also think it silly to mix the DMY date format with Am. English, and vice versa.  – Corinne (talk) 17:33, 1 September 2017 (UTC)
So are you both (SMcCandlish and Corinne) wanting to change MOS:DATEVAR, in particular If an article has evolved using predominantly one format, the whole article should conform to it, unless there are reasons for changing it based on strong national ties to the topic or consensus on the article's talk page? It seems like it. If so, this opens a whole can of worms again. If commingling one dialect's date format with another's orthography is wrong, then so is commingling one dialect's quotation style with another's orthography, or one dialect's dash style with another's orthography, or so it will quickly be argued. (And, yes, I understand that it can be claimed that a date format is different from a style, but it's too fine a distinction for me.) MOS:DATEVAR is fine as it is; there's no need to insist on consistency of date format with orthography. Peter coxhead (talk) 21:04, 1 September 2017 (UTC)
I agree with Peter. Date format and English variety are not so tightly linked as to demand any sort of change. As SMc notes, the Philippines typically uses American English, but also uses DMY dates. Ditto Japan. Frankly, which date format to use has absolutely no dependence on which dialect of English is used and the two are entirely separate decisions in deciding an article's style. oknazevad (talk) 21:25, 1 September 2017 (UTC)
Generally agreed, if the over-the-top statements are removed. We could clarify the wording, but how to do so is a big discussion in and of itself, since doing it concisely and clearly would require considerable wordsmithing. Oknazevad's "absolutely" and "entirely" hyberbole is factually incorrect, but so is the common misconception (even among Wikipedians) that "M D, Y" dates and only those date are "standard", "required", "correct", etc. in American English, and that it's not used by anyone else in the world. It's nationalistic nonsense. But pretense that nationality has no role to play at all is also indefensible. I think generally DATEVAR's reference to "strong national ties" is intended and (probably more importantly) interpreted as a direct reference to ENGVAR, but modulo the fact some places may use one ENGVAR but a different DATEVAR than someone might expect (and a few, like Canada, are just inconsistent). Or more accurately, their ENGVAR (e.g. Philippine English), as whole and including their DATEVAR, is hard to distinguish from another ENGVAR (e.g. American) aside from a DATEVAR difference. But I don't think this gets to the question raised here, which is about a non-English-speaking place. In this exact case, it's an archaeology topic, so science-style DMY has a reason to apply. In the broader class of non-English-speaking-place topics, there's usually no reason (in typical WP thinking) to use DMY dates if the article's already written in American English, and if there's not a good reason to change away from AmEng. (Personally, I wish we'd just throw out "M D, Y" dates entirely, and all other variants except the rare cases we really need ISO Y-M-D dates for a specific reason. DMY is understood just fine by everyone, it's just not everyone's personal preference or what they're most used to, which is true of every single rule in MoS or any other style guide for some subset of people. One standard would make maintenance much easier, and WP has no real reason not to standardize on one specific date format like virtually every other publisher in the world does. The lame-ass reason we haven't is people whine and cry too much any time they don't get to write exactly like they want to. The fact that we have MoS at all borders on miraculous.)  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  08:24, 2 September 2017 (UTC)
Of course this is entirely off-topic, but I am moved to object to User:CJK09's claim that Americans use "Imperial" units. We were the first major party to leave the Empire. We do sometimes call them "English" units, but a more precise name is US customary units. Note that Imperial units and same-named US units are not always the same; the most important example is liquid measure. --Trovatore (talk) 08:31, 2 September 2017 (UTC)
Trovatore, here is a solution for you: in "The Model Engineer" some years ago contributors referred to the two systems as "Christian" and "Napoleonic" units. That'll probably upset a different group though! :-) Martin of Sheffield (talk) 11:30, 2 September 2017 (UTC)
A solution for me? But I don't have a problem to be solved. I am just pointing out the incorrect use of the term "Imperial". As long as people stop using it incorrectly, there is no problem. --Trovatore (talk) 22:41, 2 September 2017 (UTC)
Regardless of the politics of the word "imperial", as Trovatore points out it's important to distinguish between Imperial units and US customary units in some cases, particularly measures of liquid volume. For example, "gallon" applied to gasoline/petrol caused confusion in Canada until they adopted metric litres. "Fluid oz.", particularly in recipes, is another well-known source of problems. Older Britons think of their weights in stones and pounds, whereas stones are not used in this context in the US. Peter coxhead (talk) 08:24, 3 September 2017 (UTC)

Since there seems to be agreement that ENGVAR doesn't apply to date formats, something should be added to the MOS:ENGVAR section to make this clear. There is currently a hatnote in the MOS:RETAIN subsection that links to Misplaced Pages:Manual of Style/Dates and numbers § Retaining the existing format. I suggest adding a "Dates and measures" section with a short paragraph and hatnote pointing to MOS:DATETIES. AHeneen (talk) 17:48, 2 September 2017 (UTC) (edit conflict)

I didn't know that the Philippines and Japan use Am. Eng. but the DMY date format. I've learned something new. I also don't think absolute consistency throughout all of Misplaced Pages's articles is necessary, nor that absolute consistency within an article is required, just as consistent as possible, within the present guidelines, and taking into account those combinations such as those in the Philippines, strong national ties, and, in those articles whose topic does not have any particular tie to the US or Great Britain, the style selected by the first major contributor. I do not understand, though, why articles that have any connection to science necessarily ought to be written using the DMY date format. I can understand articles on military topics ought to use the DMY format, and I can understand why articles on science, particular physics, astronomy, chemistry, and biology, should probably use the metric system, but what is the particular connection between date format and science that would require using the DMY date format?
Regarding your question, Peter coxhead, regarding MOS:DATEVAR, I guess I'm a little puzzled as to what change you think I might be advocating. I think the first bulleted item in MOS:DATEVAR is somewhat unclear. It reads:
If an article has evolved using predominantly one format, the whole article should conform to it, unless there are reasons for changing it based on strong national ties to the topic or consensus on the article's talk page.
By "one format", I'm assuming this means "one date format", since this appears in the section on date format. I think the second part of the sentence – "the whole article should conform to it" – is ambiguous and should be cleared up. I assume the intended meaning is: "this date format should be used throughout the article", but it might be interpreted by some as: "the variety of English that generally uses that date format should be used throughout the article". If it means the former, then I think no one would have a problem with it (but it should be clarified). Until now, I thought the date format should match the variety of English used (and I was not basing it on a misunderstanding of MOS:DATEVAR – I don't think I ever read this part of the MoS before). Though I still think there is a general correspondence between the date format and varieties of English (and I'll keep the exceptions in mind), I am persuaded that there is no need to require that the date format in an article match the variant of English used in the article. SMcCandlish, do American writers and scholars really use the DMY format? If so, that's new to me. However, regarding articles on topics that have no strong national ties to the US or Great Britain, such as an article on archaeology in South America, I think both the variety of English used and the date format should be the choice of the first major contributor to the article. There ought to be some things left to the choice of those who write or expand articles. I think the date format used in the language spoken in a country where English is not the predominant language is irrelevant.  – Corinne (talk) 17:52, 2 September 2017 (UTC)
@Corinne: ok, so we agree; I thought you were arguing for consistency between date format and ENGVAR, at least in the case of US English. Peter coxhead (talk) 17:55, 2 September 2017 (UTC)

Catching up here, and there's a lot to cover:

  • "there seems to be agreement that ENGVAR doesn't apply to date formats" – I don't think we have such a consensus at all. Rather, it is not applied blindly or simplistically.
  • "the Philippines and Japan use Am. Eng" – They don't. The Philippines and Okinawa have their own English dialects that, in written and non-colloquial form, are difficult to distinguish (and are derived) from American, but with DYM dates and some other quirks.
  • "I also don't think absolute consistency throughout all of Misplaced Pages's articles is necessary" – No one made such a hyperbolic argument, though. Increased consistency has proven to be beneficial, even if we make allowances for certain inconsistencies for good reasons. Random desire to do something different, or a less random one to write a date one particular way just because you think it's expected by those who use the ENGVAR you surmise the article is written in, aren't good reasons. The latter one can sometimes be okay as a default (if the assessment is correct), but only in absence of other, countervailing reasons that matter more. I.e., an article's ENGVAR and DATEVAR should match if there's not a Misplaced Pages-good reason for them not to. If there is one, then we're free to be consistent in a different direction (e.g. consistent with other archaeology articles or whatever). There is more than one kind of consistency, and their interplay can result in cross-inconsistencies. It's just the nature of the beast.
  • "nor that absolute consistency within an article is required" – Consensus is against you on that, and has been the entire time. Even MoS's detractors concede that a legit purpose of MoS is intra-article consistency, even when they think inter-article consistency should be completely abandoned (a point on which they also do not and will never have consensus). Any exceptions here will have to have very good reasons, i.e. WP:IAR-level ones, or be drawn from another guideline (e.g. some compressed constructions are permitted in tables but not running prose, etc.).
  • "those articles whose topic does not have any particular tie to the US or Great Britain" – ENGVAR is not limited to those two countries. As a practical matter, there's little discernible difference between US and Philippine and Okinawan written English in a formal register, just as there is little between formal, written British, Irish, and Australian. Where differences do exist we don't ignore them. This entire idea of divorcing DATEVAR from ENGVAR is predicated on the false assumption that there are only two ENGVARs.
  • "I do not understand, though, why articles that have any connection to science necessarily ought to be written using the DMY date format." – That wasn't proposed either, only that the science nature of the topic provides a rationale for arguing for DMY format (a rationale which might otherwise be absent in an AmEng article). The problem here is that people seem to be looking for a table of invariable rules to apply, when the *VAR guidelines all make it clear that the result at a particular article is a matter of a consensus discussion, not a robotic rule application.
  • Yes, "this date format should be used throughout the article" is an improvement over "the whole article should conform to it", and is what is intended. However this doesn't somehow mean that the ENGVAR and DATEVAR should conflict without good reason, because the "strong national ties" standard applies to both. Where some mistakes are made are in assuming that everything that looks like AmEng at first glance is, and is being used because of a strong national tie. Both assumptions can be wrong, one can be right, or both can be right.
  • "do American writers and scholars really use the DMY format?" – Who cares? And it's not a useful conceptual approach anyway. American writers (like British ones and Botswanan ones) follow the style guide of the publisher or intended publisher of what they're writing; it doesn't have anything to with their own individual, personal nationality unless they're self-publishing. And WP has no reason to care anyway. The DMY format is understandable by everyone. Our duty is reader understanding not "reader happy-making by using every stylistic quirk a big knot of them is most likely to prefer at a particular topic". If you're asking whether some American writers prefer DYM format all day every day, the answer is "yes" (I'm among them, so my very existence proves it). We're common in technical professions (where we also use ISO Y-M-D dates frequently, too, usually when machine parsing is expected).
  • "There ought to be some things left to the choice of those who write or expand articles" – They just shouldn't be style things. We've learned through long and consistent experience that permitting (or failing to curtail) random stylistic variation leads to recurrent, productivity-draining WP:BATTLEGROUND behavior over trivia.
  • "the date format used in the language spoken in a country where English is not the predominant language is irrelevant." – Agreed on that much!
  • "both the variety of English used and the date format should be the choice of the first major contributor to the article" – But that isn't the case now and never has been. We look to first major contributor's version if and only if consensus cannot be reached (and it's only about what they did then; they have no "supervote" about what to do now). It isn't some magically WP:VESTED position held in an "I got here first, and am staking a claim" sense, and we would never permit that. The entire concept is fundamentally un-wiki. We have FMC edit history as a last-resort fallback for one reason and one only: to put the dispute on hold unless and until a consensus can emerge that one ENGVAR or DATEVAR or other *VAR is preferable for demonstrable reasons (which may take years, or be never).

    We could and probably should throw out the "first major contributor" rule, because it has caused more problems than it solved. It would make more sense to go with the WP default for everything: when consensus for a change does not emerge, revert to the status quo ante. The "FMC" rule is actually a WP:EDITING policy violation and should never have been put into the guidelines at all, even as a last resort. The fact that it's very frequently misinterpreted as a mysterious WP:OWN exemption is a very good reason to remove it.

 — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  01:06, 4 September 2017 (UTC)

For many articles, perhaps most particularly science-related ones, there's no reason to prefer one variety of ENGVAR to another, so there is no rational way of reaching a consensus, there are no demonstrable reasons. "The first major contributor principle" is the "status quo ante principle"; otherwise how in an article with no ENGVAR ties which has developed a mixed style over time do you decide what the status quo ante is? It's not a question of WP:OWN, but of trying to decide at what point ENGVAR and style are sufficiently established to be maintained. "The consistent ENGVAR at the first major expansion" would probably work equally well, and would avoid the implication of ownership.
With the benefit of hindsight, given that the English Misplaced Pages didn't decide to use US English throughout, it would have been better to have set US English as the default (given its numerical prominence) and require all articles in other ENGVARs to be marked as such at the point of creation (changeable by consensus of course). This would have saved a lot of hassle, but it's too late now, I think. Peter coxhead (talk) 06:33, 4 September 2017 (UTC)
Whatever the article is already written in is the ENGVAR to use if there's no strong national tie. The default DATEVAR to use is the one that matches the ENGVAR, but a case can be argued to use DYM dates in a science article if there is no national tie compelling MDY. That's not a guaranteed-win argument, especially if literature in the field in question isn't actually very consistent on date formatting; but it could be a component of the "what date format should this page use?" discussion at any given science article (proof: it has been in this case). First major contributor and status quo ante are not the same at all. The SQA is what the page had before the dispute erupted (e.g. yesterday). The FMC is what it had with the very first non-stub edit, which might have been in 2004. If the article has really had a mixed style for a long time, then the FMC might be necessary to look at, though this is rare. Most cases of stylistic mixture can be traced to recent edits, and normalized to the style in use before them (which might be from last week, not from the date of the FMC). I agree that "at the first major expansion" is an improved version of FMC, and would support that as a minimum change to the presently very problematic wording. But it still strikes me as an unnecessary divergence from standard WP practice, which is the immediate SQA.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  12:19, 4 September 2017 (UTC) PS: I tend to agree on the last point (both "should have" and "not going to happen" aspects). I'll probably surprise a lot of people in saying (as an American) that I would have voted for British/Commonwealth English for several reasons, including it having numerical superiority by world-wide regions if not by readers head-count; because of its richer history; and because it maintains distinctions lost in AmEng, e.g. practice vs. practise and defense vs. defence. But we'd've had to keep single-then-double quotation marks order, and dots for abbreviations, for clarity/parseability/disambiguation reasons.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  12:26, 4 September 2017 (UTC)

Question about ENGVAR ...  – Arbitrary section break

SMcCandlish I really don't want to get into an argument with you, but I'd like to point out that several times during this discussion you have said what you personally would prefer:

I'm an American who prefers DMY date format myself, but it's not my or your job or privilege to impose that preference on everyone, especially not by "I got here first" chest-beating.

I would have voted for British/Commonwealth English for several reasons, including it having numerical superiority by world-wide regions if not by readers head-count; because of its richer history; and because it maintains distinctions lost in AmEng, e.g. practice vs. practise and defense vs. defence.

are at least two. While of course you are free to do this, I don't think these kinds of comments are helpful to sorting out a multi-faceted discussion, except perhaps in a discussion regarding a specific proposal for a change to the current style guide. This present discussion is actually covering several different things, and has gotten a bit confusing, but I don't think it is on a specific proposal. Also, I don't think saying "especially not by 'I got here first' chest-beating" is helpful, either. I don't see any previous comments that suggested that attitude, and if anyone mentioned "first major contributor", it was because it is in the MoS already, and quoted above.

Several times you have said that it is more logical to use the DMY date format for science articles:

Children of Llullaillaco is primarily a science article; while we don't have a formal rule about that, the above reasoning (that science generally uses DMY format) is good logic, about how English is written for a particular context.

When I asked, "What is the particular connection between date format and science that would require using the DMY date format?", I don't think I got a good answer. "Science generally uses DMY format" isn't enough. If the vast preponderance of sources in science use the DMY format, that may be a sufficient basis to include in the MoS: "The DMY format should be used in all science articles." That is why I asked, "Do do American writers and scholars really use the DMY format?" Your response was, "Who cares?" implying that I was asking about these writers' and scholars' personal writing preferences. I wasn't. I was asking about what they use in published books and articles. If there is a mix in the sources, then I have to agree with Peter coxhead, who wrote, above, "For many articles, perhaps most particularly science-related ones, there's no reason to prefer one variety of ENGVAR to another, so there is no rational way of reaching a consensus." I also think that Misplaced Pages is mainly used by the general public, including young people, and that they ought to be able to find and read at least some articles written in the variety of English they themselves speak, read, and write. That is why I think it is right that some articles are written in British/Indian/Australian/Canadian English and some are written in American (U.S.) English, and that some articles use the day-month-year date format and some use the month-day-year format. For the same reasons, I also don't think that, even if most scientific publications use the day-month-year format, our science-related articles should all be written using that format.

I'm surprised that you would write,

Personally, I wish we'd just throw out "M D, Y" dates entirely, and all other variants except the rare cases we really need ISO Y-M-D dates for a specific reason. DMY is understood just fine by everyone, it's just not everyone's personal preference or what they're most used to, which is true of every single rule in MoS or any other style guide for some subset of people. One standard would make maintenance much easier, and WP has no real reason not to standardize on one specific date format like virtually every other publisher in the world does. The lame-ass reason we haven't is people whine and cry too much any time they don't get to write exactly like they want to.

I don't know about those who "whine and cry too much any time they don't get to write exactly like the want to", but saying that "DMY is understood just fine by everyone, it's just not everyone's personal preference or what they're most used to" is disingenuous. Except for a few writers such as yourself, the month-day-year date format is very much the preferred format for over 250 million American (U.S.) readers. I don't think they should be dismissed so easily.

When I wrote, above,

However, regarding articles on topics that have no strong national ties to the US or Great Britain, such as an article on archaeology in South America, I think both the variety of English used and the date format should be the choice of the first major contributor to the article. There ought to be some things left to the choice of those who write or expand articles.

You made a big point of saying that it is not only the US or Great Britain. Of course I know there are other varieties of English, including Indian, Australian, and Canadian, and the English of the Philippines and Okinawa; I just didn't feel I needed to list them all. When I wrote, "There ought to be some things left to the choice of those who write or expand articles", you responded, "They just shouldn't be style things." I disagree with you. On certain types of topics, and at certain stages in the formation of an article, the choice of ENGVAR is a style choice, and I said this: if there are no strong national ties to a particular place that would recommend one variety of English over another, and if the article is not on a military topic, then the person who starts a new article, or expands a stub, ought to be able to select the variety of English he or she wants to use. I don't think the person should have to gain consensus on this. If, however, an article on such a topic has, over time, developed a mixed style regarding ENGVAR, then discussion may need to take place and a consensus reached. I don't think this is anything new. When I used the phrase "first major contributor", I was merely using the phrase that is in the MoS; if you feel it needs to be changed, then I think it should be a separate discussion following a clearly written proposal. This discussion has been too much all over the place.

I am a copy-editor, and consistency is important to me, and I work to ensure it in articles. I have always believed that the date format should match the variety of English used in an article. To me, it was always pretty clear: use DMY with British, Indian, and Australian-related topics and MDY with American- (U.S.-) related articles. I now understand that there are some other combinations such as articles that use Philipines English. When I wrote, above, "I am persuaded that there is no need to require that the date format in an article match the variant of English used in the article", it was only because I saw several comments that seemed to say there isn't, and shouldn't be, such a requirement to match the date format with the variety of English (even apart from the exceptions to the usual matching). Maybe I'm too easily persuaded. I see now – and I don't know why this wasn't clear to me from the beginning – that you agree with me that there is a correspondence, and that the date format should match the variety of English used. I think it's already in the MoS:

Articles on topics with strong ties to a particular English-speaking country should generally use the date format most commonly used in that nation.

So, regarding allowing editors to select the style they want to use, I want to make it clear that I do not mean that they should be allowed to mix-and-match date format and variety of English as they please.

So, to summarize:

1) We all seem to agree that, in an article about a country where English is not the primary language and there are no strong national ties to a particular English-speaking country, the date format used in the language spoken in that country is irrelevant.

2) MOS:DATEVAR and MOS:ENGVAR are fine as they stand, except perhaps we ought to change "the whole article should conform to it" to "this date format should be used throughout the article" (in the fourth bulleted item in MOS:DATEVAR). I have gone ahead and made this change.

I would like to propose that the fourth bulleted item in MOS:DATEVAR be changed from:

Where an article has shown no clear sign of which format is used, the first person to insert a date is equivalent to "the first major contributor".

to:

Where an article has shown no clear sign of which format is used (i.e., uses both date formats, with neither predominating), and does not meet the requirements specified in MOS:DATETIES, the date format used by the first major contributor, or, if several years have passed, the editor making the most recent major expansion, is to be used.

 – Corinne (talk) 19:37, 4 September 2017 (UTC)

A lot of fair points, though I think you mistake my intent in a few places (or I just made my intent unclear). I really don't want to get into an argument with you, either, and suspect another detailed response would largely restate the same previous points in other wording. Some of them might be interesting discussions, in separate, focused threads about specific issues to solve.

I like the general nature of the change you're proposing, other than we should do as Peter_coxhead suggested, and remove references to first major contributor and instead couch it in terms of edits. The WP:OWNish behavior you say you're not really aware of is very familiar to some of us, and a problem that's been running for a decade or so, and even worsening (and applies to all the *VARs). The insertion of another "magically special party", namely "the editor making the most recent major expansion", compounds the problem. It's adding a new bug while trying to fix an old one. But the approaches will combine well. Moving that to new subthread so people see it.
 — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  00:03, 5 September 2017 (UTC)

Combined DATEVAR revisions

If we combine Peter_coxhead's and Corinne's clarification proposals, something like following seems to emerge (with an additional tweak to tie the last conditional to actual development happening, not just time passing with no development): {{tq|1=

  • The date format chosen in the first major contribution in the early stages of an article should continue to be used, unless there is reason to change it based on strong national ties of the topic, or consensus on the article's talk page.
  • Where an article has shown no clear sign of which format is used (i.e., uses both date formats, with neither predominating), and does not meet the requirements specified in MOS:DATETIES, retain the date format used in the first major contribution, or, if more significant content development has happened, in the most recent major expansion.

I would support that at MOS:DATEVAR, and conforming wording tweaks at the other *VAR / *RETAIN provisions. It clarifies best practice, doesn't substantively change the real intent and meaning of FMC (and preserves the acronym), yet eliminates the OWN/VESTED problem that is an EDITING policy conflict. This might even make happy those who feel that whoever does the most work at an article should have more say, without actually giving them any special power (since it's based on content not editor name – a "major expansion" might be the work of seven editors all building up the article over a month, or whatever). Basically, the more you do the work (and it's real, encyclopedic work), the more likely it is that your version will stick, which is how WP works in general anyway.

@Corinne and Peter coxhead: If this works for you, we can treat this as a proposal and advertise it at WT:MOSNUM, etc. Or just treat it as a draft to work on further, and do a final version as a proposal at WP:VPPOL. Or whatever you like.
 — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  00:03, 5 September 2017 (UTC)

I will read the whole discussion tomorrow, to double-check that I support it; I only have five minutes now. What you have written is fine, but write "national ties with", rather than "national ties to" for point two (first modified). –Sb2001 00:15, 5 September 2017 (UTC)
Revised it to use of, which is what's actually meant here, on a careful re-read. The national ties in question are a quality of the topic, not a relationship between the topic and the date format.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  01:35, 5 September 2017 (UTC)
  • Oppose in part: I see likely problems with or, if more significant content development has happened, in the most recent major expansion. This allows an editor making a major expansion to change the date format. Suppose the first major expansion used date format A. An editor adds an expansion using date format B. Now the article appears to be inconsistent, so the proposed wording allows it to be changed to date format B. This is a recipe for instability, since another editor could now expand using date format C and the date format could be changed again. We need to favour stability. If this part is removed, then I think the proposed wording is an improvement. Peter coxhead (talk) 10:40, 5 September 2017 (UTC)
  • Comments:

(a) Regarding which preposition to use after "strong national ties", to me, neither "of" nor "with" sound right. To avoid having to choose, perhaps we could revise this to:

  • unless there is reason to change it based on a strong tie between the topic and a particular country and thus variety of English...

(b) Regarding this phrase, "retain the date format used in the first major contribution", if, through editing by various editors, the date format has become mixed, "retain" doesn't make much sense to me. I would write:

  • implement consistency by using the date format used in the first major contribution.

(c) Regarding whether to leave off the last part, I understand Peter coxhead's concern. SMcCandlish, I went back and re-read what you wrote earlier, which I'll copy here:

First major contributor and status quo ante are not the same at all. The SQA is what the page had before the dispute erupted (e.g. yesterday). The FMC is what it had with the very first non-stub edit, which might have been in 2004. If the article has really had a mixed style for a long time, then the FMC might be necessary to look at, though this is rare. Most cases of stylistic mixture can be traced to recent edits, and normalized to the style in use before them (which might be from last week, not from the date of the FMC). I agree that "at the first major expansion" is an improved version of FMC, and would support that as a minimum change to the presently very problematic wording. But it still strikes me as an unnecessary divergence from standard WP practice, which is the immediate SQA.

I'm not clear on what your primary concern was here. Do you still think an alternative to "last major contribution" needs to be included? For all: what, if anything, is the concern that makes "the date format used in the first major contribution" insufficient by itself? (I'm not saying it is insufficient; I'm just trying to help the discussion.)  – Corinne (talk) 16:19, 5 September 2017 (UTC)

I'm happy with both of Corinne's suggestions. Peter coxhead (talk) 16:26, 5 September 2017 (UTC)
The (a) revision works for me, too, though I'd prefer "nation", for continuity between the related provisions. As learned the hard way with, e.g., inconsistent wording intended to mean the same thing at WP:PERFNAV and WP:PERFCAT, people will wikilawyer endlessly about the to-the-letter wording and will become resistant to it being normalized once they think they've found something they can leverage.

Agreed entirely with the (b) change.

On (c), I can let that go for now. Would rather get one major improvement than hold out for two, when the second may not be as good as I think/hope.  :-)   However, I'm curious of the exact intent of the earlier "or, if several years have passed, the editor making the most recent major expansion" version, and if Peter has the same concern about it. My own recent-major-expansion material was an attempt to keep something of that, without it just being a time thing, but maybe time makes sense and matters here.

An explanatory bit about (c) – don't let it hold anything up: I agree with Peter's assessment of the version I proposed, but see it as a good thing (i.e., I don't agree with the slippery slope predicted). It's closer to editing policy. If I create a tiny stub, and Corinne works it up to a B-class article (first major contribution), but Peter radically expands the article and works it up to a GA or FA, and is convinced a different date format is more appropriate in the now very different article, why should we go back to the FMC version of the date? One of Peter's primary concerns of late (which I share) is that with our editorial pool shrinking, it's becoming increasingly difficult to actually have and firmly conclude consensus discussions on article talk pages about such things. From my perspective, this means that the "FMC is a last resort, not the first or only choice" intent of these *VAR provisions is eroding, that they're actually on the edge of turning into a VESTED entitlement and an OWN free pass. We may ultimately have to revisit the stringency of the *VARs, to not be so "forbidding" of trying to change things. The WP standard for everything is that anyone is free to try to make almost any change they want to (within policy limits); they're just not free to editwar to get their way – if someone objects, then stop, revert to status quo ante if others want to, and hold a discussion. The *VARs short-circuit this, and tend to be misinterpreted and misapplied as requiring that one get "prior permission" before even attempting the change. But, that's probably too big an issue to deal with at this time. Or maybe I'm just flat wrong; the risk may be much less than I think and less than that of being any more lax about changes to dates or other *VAR things. I'm keeping that possibility in mind, especially given that I resist most MoS change proposals but now am making one or at least suggesting one could become necessary.

New question (d): What about the extant wording's point regarding first insertion of a date (i.e., what about a case in which the FMC doesn't include a date)? I guess for the DATEVAR version of this, that needs to be worked in somehow, probably as "by using the date format used in the first major contribution that included a date".
 — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  19:36, 5 September 2017 (UTC)

Revised point (a) part.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  00:52, 6 September 2017 (UTC)

Just a quick note that US military uses dmy and in milhist for US, this is preferred. It is a bit of a twist on "strong national ties"? FYI Cinderella157 (talk) 01:47, 6 September 2017 (UTC)

Yes, it certainly is, Cinderella157. Though this was briefly touched upon above, I appreciate your mentioning it.
Regarding the third bulleted MOS:DATEVAR item, copied from above, with SMcCandlish's phrase added:
  • Where an article has shown no clear sign of which format is used (i.e., uses both date formats, with neither predominating), and does not meet the requirements specified in MOS:DATETIES, retain the date format used in the first major contribution that included a date, or, if more significant content development has happened, in the most recent major expansion.
If you think about it, the part after "or" will not help much to determine the best date format to use since those recent edits probably played a part in creating the situation of two date formats being present in the article. Other than "the first major contribution that included a date", can you think of any other benchmark to use that would not end up being confusing? How about the toss of a coin?  – Corinne (talk) 05:21, 6 September 2017 (UTC)
The *VAR idea has seemed almost that arbitrary to me the whole time (and a coin toss would actually be less problematic). But given that we're stuck with some version of *VAR/*RETAIN (in at least four places) for now, I concede that the "or, if more significant development ..." part isn't going to fly. Just "the first major contribution" – and, for DATEVAR in particular, "that included a date" – should be sufficient. I'm also glad the US military thing got re-mentioned, since I'd forgotten about it, too, but it's in keeping with what's been said about not over-presuming when it comes to an ENGVAR and DATEVAR connection, even if there being one as default might be reasonable I wouldn't worry about any generality written here somehow creating a problem for MILHIST; their own topical guideline, which does seem to actually be accepted as one unlike some topical WP:PROJPAGE essays on which people have questionably slapped guideline tags, is sufficient good reason in *VAR terms. Military topics were probably better examples than science ones the entire time.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼ 

A Misplaced Pages-irrelevant rule to excise?

After this:

A sentence that occurs within brackets in the course of another sentence does not generally have its first word capitalized just because it starts a sentence.

Comes this:

The enclosed sentence may have a question mark or exclamation mark added, but not a period.: ... Alexander then conquered (who would have believed it?) most of the known world.

It doesn't seem to serve any purpose here, since we would never use a construction like this in our articles (with a question mark or an exclamation point). This appears to be WP:CREEP added by someone trying to make MoS a general-English style guide for the world (i.e., a how-to article) rather than Misplaced Pages's guide to writing Misplaced Pages articles in Misplaced Pages's voice.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  21:58, 28 August 2017 (UTC)

Agreed. A quick search for articles containing "?)" or "!)" returned nought for both. It seems unnecessary. –Sb2001 23:04, 28 August 2017 (UTC)
Deffo. Serves no 'pedia purpose and can only confuse the MOS's role. Primergrey (talk) 23:43, 28 August 2017 (UTC)
I'm moving it to a footnote; the construction could be used in a quotation which we don't want someone to "correct".  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  14:12, 1 September 2017 (UTC)

section length MOS location?

I remember once reading an MOS about the lengths of sections within an article, i.e. that they shouldn't be too short or too long, but I can't find such. Can anyone help me out? — fourthords | =Λ= | 17:29, 30 August 2017 (UTC)

@Fourthords: MoS doesn't seem to have much about it, just some generalities at Misplaced Pages:Manual of Style/Layout#Body sections. One of the content or editing guidelines like Misplaced Pages:Article size might have more.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  19:31, 31 August 2017 (UTC)
Did some digging around in relevant pages:
We don't seem to have any particular rules about this, and the lack of them all along has apparently not been problematic in any way.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  04:10, 5 September 2017 (UTC)

Use of alternative, uncommon spellings

Hi, I don't know if someone can point me in the right direction. I was copy editing a video game article and encountered the word 'mediaeval', in place of medieval. The article also contains 'reflexion' and 'connexion', instead of the more common terms. Now after doing some googling, it appears that these are legitimate, if not very widely used, alternate spellings of words. They are maybe more associated with British English, but I don't believe that any of these spellings are more common than their standard alternatives. Do we have any relevant policies or guidelines that recommend using, all things being equal, a non-archaic spelling when available? Should there be? I understand that in some cases the article content might mean that using a less common form would be less confusing for the reader because it would introduce consistency, but I can't really see the benefit of using weirder spellings just because they exist. On a personal note, I'd never encountered reflexion or connexion before and I'm British and I actually misunderstood what reflexion meant in the context of this article. There are many readers of the English Misplaced Pages with larger vocabularies than mine, but there are also those with smaller ones and I think we should try to write plainly where possible. Apologies if this is a long answered and addressed question, but I find navigating through the MOS a bit of a nightmare. Scribolt (talk) 10:56, 5 September 2017 (UTC)

Those are indeed archaic spellings. They shouldn't be used unless part of a proper name. oknazevad (talk) 11:09, 5 September 2017 (UTC)
'Connexion' is a technical term used in some specialised contexts. See Methodist Church of Great Britain for multiple examples, or for that matter see Connexionalism. Mediæval is an affectation and should use the diphthong. The word is often met in names which are intentionally "olde worlde", such as the Mediæval Bæbes. Reflexion is a borrowing from French (see for example Reflexions sur la question juive) and unless being quoted is only designed to make the writer feel more cultured. Oknazevad's advice is good, though I would keep them in direct quotations as well, other than that ignore them. Regards, Martin of Sheffield (talk) 11:39, 5 September 2017 (UTC)
MOS:COMMONALITY. If that doesn't get you there somehow, WP:JARGON probably should. --Izno (talk) 12:10, 5 September 2017 (UTC)
Thank you all very much, both for the background information and the guidance links. Scribolt (talk) 13:14, 5 September 2017 (UTC)
Agreed with Oknazevad, Martin, and Izno, word for word, and based on previous discussions of these, too .  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  18:44, 5 September 2017 (UTC)\

Adam9007

This discussion has been closed. Please do not modify it.Unproductive and off-topic WP:ASPERSIONS about another editor do not belong here.

If you can diff sufficient evidence to demonstrate a case of actionable disruptive edtiting, the proper venue is WP:ANI.
 — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  23:07, 6 September 2017 (UTC) (non-admin closure)

The following discussion has been closed. Please do not modify it.
Without knowing the article in question, I will confidently bet that the editor responsible will be Adam9007 (intentionally not notifying at this stage), who has been on a one-man quest to restore what he considers "traditional" spellings and meanings to the English language and has chosen Misplaced Pages as his personal battlefield. Be glad the article doesn't refer to one of the characters being happy, or he'd have changed it to "he became gay" and then thrown a temper tantrum at anyone trying to explain that "gay" hasn't had that meaning for decades. (This is not hyperbole.) ‑ Iridescent 18:57, 5 September 2017 (UTC)
How the blue hell has that obvious WP:NOTHERE case not get indeffed? Seriously?!? oknazevad (talk) 00:44, 6 September 2017 (UTC)
Iridescent wins the cookies. I don't know whether to be impressed or slightly horrified that you managed to ID the user based on just that. You get bonus points for an irrelevant gaiety being introduced into another article I just found. I'm usually pretty relaxed about people's idiosyncrasies in articles, I don't change things that I might think weird as long as the text is still clear as to what's meant, but mediaeval had a snotty hidden text next to it with an irrelevant reference to ENGVAR and after I corrected I got reverted with no justification thus far other than there's no rule why it can't be used. Scribolt (talk) 07:25, 6 September 2017 (UTC)
@Oknazevad, he's not a straightforward WP:NOTHERE case, as he does on occasion make genuine (if often misguided) efforts to help. I'd shed no tears over it—he's one of the most arrogant and objectionable people I've ever encountered on Misplaced Pages, and has the dubious privilege of being the only editor I've ever banned from my talk page—but I couldn't justify a WP:NOTHERE block. He's survived being hauled off to ANI in the past (albeit over something different), so any admin action wouldn't be uncontroversial, although to judge by his talk page and recent archives community patience with his "I've made up a rule and I'm going to insist Misplaced Pages applies it" approach is rapidly reaching zero. ‑ Iridescent 19:14, 6 September 2017 (UTC)
Should be a WP:ANI, WP:NPOVN, or other noticeboard matter; this page isn't a disciplinary forum, and people trying to use it as one is apt to lead to problems. Just sayin'. The MoS regulars already get false accusations of being a cabal, and being wannabe "enforcers", so let's not insert any grain of truth to them, lest the grains accrete into lumpy pearls. I will say that permitting long-term "style warrior" behavior that includes revert-warring and self-declared WP:TRUTH / WP:GREATWRONGS manifestoes about style matters has also caused problems, and that the proper noticeboards have (eventually) dealt with the matters before. A first step is making sure that such users receive a {{Ds/alert|mos}} so that they're subject to WP:AE if they get out of hand.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  21:43, 6 September 2017 (UTC)
Irie nailed it. I think it's clear that WP:NOTHERE does not apply - Adam does quite a bit of good work. That said, he sure does find ways to be a complete pain in the ass to many of us and a major resource drain on the project. I lived through the whole CSD#A7 fiasco that resulted in him being defacto banned from participating in patrolling CSD nominations. I suspect it's going to take a similar sanction to stop this nonsense as well. Toddst1 (talk) 22:11, 6 September 2017 (UTC)
You all may have accomplished what you wanted, but in a much smaller and meaner way than ANI or equivalent. He just posted "retired" on his user pages, saying "can't do it any more, I've had enough". Please keep in mind, in the future, that what you post at Misplaced Pages is public and likely to be seen by the person you are talking about - and consider how you would feel if you came across people talking this way about you behind your back. --MelanieN (talk) 22:18, 6 September 2017 (UTC)
I probably should have used {{hat}} instead of just asking the discuss to stop. <sigh> I need to better live up to my "This user is NOT an admin, but acts like one anyway" userbox.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  22:21, 6 September 2017 (UTC)
Melanie - that retired banner on Adam's talk page has been up and down more often than a test elevator in an elevator factory (or some other thing which has been up and down on an alarmingly regular basis). He'll be back just in time for another bollocking over another aspect of his inability to collaborate effectively with the rest of the community, probably by Friday. Nick (talk) 22:57, 6 September 2017 (UTC)

RFC: Obsolescent spellings

Folks, can you please stop bashing the editor and focus on the actual MOS question: whether it is or is not permissible to use spellings like "mediaeval", "reflexion", and "connexion" in articles? How about if no one objects? How about if some other editors do object? As for the person you are talking about, I was just discussing the issue at his talk page and suggested bringing the discussion here (not knowing there was already a discussion here) so you can expect him here shortly. You might keep in mind that he is a human being with feelings. --MelanieN (talk) 22:00, 6 September 2017 (UTC)

  • No: it is not acceptable, unless the context specifically calls for the archaic form. Toddst1 (talk) 22:05, 6 September 2017 (UTC)
  • No (except in proper names that use those spellings like Mediæval Bæbes). Izno's reference to MOS:COMMONALITY is clear enough for me. And the fact that this was raised here by a Brit makes clear that it is not a valid application of WP:ENGVAR. —David Eppstein (talk) 22:07, 6 September 2017 (UTC)
  • No Misplaced Pages is not a playground to try to reintroduce archiac spellings into mainstream English usage. TonyBallioni (talk) 22:13, 6 September 2017 (UTC)
  • No unless it is in a quote or has a technical defined meaning. Titoxd 22:21, 6 September 2017 (UTC)
  • Generally no, but "spellings like" is too vague. We need to add a provision to not use obsolete or archaic spellings outside of a) quotations and proper names, and b) specialist terminology. That will already be consistent with existing rules at MOS:JARGON and MOS:QUOTE. Then provide a list of some plausible examples of archaisms to not use, including "reflexion", "connexion" (outside the specialist meaning in Methodism), "coöperation", "rôle", "Rumania", "Manks", "to-day", "gay" to mean "happy" or "festive" and similar things if not already covered at MOS:WTW, and whatever else comes to mind (should be stuff still used in but abandoned during the 20th century; it's already a given that we're not going to be using "hwæt", "thine", or "an-hungred"). However, I want to point out that not everyone considers "mediaeval" obsolete yet. MoS itself says to use it in place of "mediæval", at MOS:LIGATURE. Given past discussion , it appears that there's enough of a consensus to rule it obsolete for WP purposes, so that example that uses it will need to be replaced (it was only included because someone wanted to be clever and use two examples in the same sentence).  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  22:29, 6 September 2017 (UTC)
  • No unless needed for context/clarity. Flyer22 Reborn (talk) 23:37, 6 September 2017 (UTC)
  • Comment—and who's to determine whether a spelling is "obsolescent"? Why does this even have to be micromanaged by the MoS, rather than leaving it to WP:BRD? Curly "JFC" Turkey 🍁 ¡gobble! 00:01, 7 September 2017 (UTC)
    • RS determine it. That'll mostly be current dictionaries, and N-grams, unless anyone finds any recent linguistic journal material or the like that addresses these words in particular, which is unlikely. It's going to take an aggregated review of all the reputable dictionaries that have editions within, say, the last two decades (or maybe even just one decade; going back to the 1980s or earlier will be a waste of time). That can actually come later; figuring out what to say about the list of words in more important right now that exactly which words to list. It has to be managed here because this is our style guide, and people are engaged in repeated bouts of disruptive disputes about these spellings; the reason we have a style guide is to prevent/stop that waste of productivity and good will (and, of course, to produce a more readable encyclopedia). We already did trying leaving this to BRD and local consensus, and the result has been repeated fights, re-re-re-litigation of the matter at this and other talk pages for years, now an incivil flamewar, and an editorial resignation right on the verge of an ANI. This is a perfect candidate for a line-item in the MoS, and I say that as someone strongly resistant to adding new line-items to MoS. (It might not be best in the main MoS page, but one of its subpages.)  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  03:28, 7 September 2017 (UTC)
  • No with the standard "except in quotations or proper names" caveat. It's not an ENGVAR thing, as the spelling as discussed wre already obscure and archaic in the mid-20th-century in British English. Here in the 21st-century 60 some years later they're out right wrong. And this very much is what "commonality" was meant to address. (Which, to address Curly Turkey's comment, is why it's an MOS-worthy topic; it's already part of the MOS, it's just a matter of clarify how it applies.) oknazevad (talk) 00:33, 7 September 2017 (UTC)
  • Generally no... but in specifics yes. In other words, if someone can explain why an article is using an archaic spelling (in a specific context), we should allow it. Blueboar (talk) 01:46, 7 September 2017 (UTC)
  • No with a possible caveat relating to the context as mentioned by several people above. I would support SMcCandlish's proposal for a simple addition along the lines of: If there is two spellings of the same word with the same meaning, and one is not in common use in any currently used forms of English, the commonly used spelling should be preferred unless the context of the article content blah blah blah something clever. Scribolt (talk) 06:14, 7 September 2017 (UTC)
  • No except with the usual "if the editor can justify it" caveats, which apply to all aspects of the MOS in any case so don't need to be spelled out explicitly. Ironically, I've occasionally caught myself using "mediaeval" and had to go back to fix it, but that's because I tend to work with a lot of 19th-century sources so it no longer triggers my "this looks wrong" filter. "Reflexion", "connexion", "shewed" etc outside of very specific instances are no more appropriate than emoji and should be removed on sight, as should instances of people using archaic terms when there's a globally-understood synonym (at least one FA uses "decollated" instead of "beheaded", for instance). ‑ Iridescent 19:31, 7 September 2017 (UTC)

Extended discussion of obsolescence RfC

  • In general I'd agree with , but claiming "gay" cannot mean happy is political. Possibly because I listen to a lot of folk music, but I always assume "gay" means gay unless used in an obviously sexual sense. For instance from the song "A North Country Maid" the line "The lads and young lassies are pleasant and gay" has no innuendo at all. Martin of Sheffield (talk) 23:05, 6 September 2017 (UTC)
    • That's already covered by both quotations (of lyrics) / proper names (of songs) and jargon usage (the concept of gaeity being retained in still-extant folk music); it's not an adjective that would be used in that sense in WP's own voice (e.g. "After the election results came in, McNabb had a gay party at his campaign headquarters"). Same goes for "queer", which still has some currency in its original sense in colloquial British and Irish usage. But I don't want this to get hung up on any specific word (and both of those are probably WTW matters anyway); I'm mostly trying to get at how to structure the entry in the MoS.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  23:10, 6 September 2017 (UTC)
    • Innuendo? I imagine that that was an ill-thought selection of word. There is no reason to suggest that 'gay' has any sexual connotations as such; not all homosexuals are sexual in a physical sense. I do not like seeing 'gay' being used to mean homosexual, though, eg 'he revealed himself to be gay' is the sort of thing you would read in a tabloid newspaper. But that is another issue. –Sb2001 23:17, 6 September 2017 (UTC)
      • Okay, so that's two completely opposite reasons to consider that one a MOS:WTW matter; I'll strike it from my original comment.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  23:21, 6 September 2017 (UTC) PS: Journalism style guides (for what they're worth) do recommend "gay" (for males) rather than "homosexual", which they variously consider judgmental or clinical. These things are always a moving target. In my own lifetime, for example, the preferred term for African-American has moved from Colored and/or Negro to Afro-American to African-American, with the first two now branded terrible and the third verging on it. A generation from now the fourth will be a bad word, and we'll be using something else.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  03:55, 7 September 2017 (UTC)
  • Comment after a quick search, here are some dictionary entries: Medieval Oxford, Mediaeval MacMillan, Medieval Merriam-Webster, Mediaeval Cambridge Reflexion Oxford Reflexion Marriam-Webster Reflexion Collins Connection Oxford Connexion MacMillan make of these what you will, but only one says anything about any of them being archaic. Adam9007 (talk) 02:15, 7 September 2017 (UTC)
    • Good start. It's important to look for more than just the word "obsolete", though. E.g. Collins (a leading British dictionary) says "reflexion" is the "less common" spelling even in BrEng. More importantly, it has a corpus analysis chart that shows that usage of it died down to nearly nothing ca. 1800, and has been flatlined ever since then. That is, thus, a demonstration of "obsolete", with way more data to back it up than just an old-school dictionary entry. Their similar chart for connexion shows a marked decline ca. 1960, and a usage flatline around 2000. For mediaeval, it shows continually declining usage since the 1910s; for medieval, increasing usage since the same period, stabilizing rapidly thereafter and remaining stable to the present. And so on. I'll bet good money that Google N-grams will also show the same patterns. I didn't know that the online Collins had this kind of data; this is going to prove useful in a lot of future discussions. It's got gaps, though; e.g. it has no separate charts for cooperate, coöperate and co-operate, though Google N-grams does; co-operate has been declining since WWII, and the old-timey British journalese spelling "coöperate" was seemingly never picked up by book publishers at all. (I remember first seeing it as a child in the 1970s when I lived in the UK and practiced reading newspapers, and having to ask what it was.)  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  03:47, 7 September 2017 (UTC)
Having learnt to read newspapers in the early '60s I must be about 10 years older that you and I can only remember seeing "coöperate" very rarely. Co-operative is a lot more common, particularly in its abbreviation. Consider: "I went to the coop to get a chicken". Did I go to the co-operative shop (co-op), or to the chicken's house (coop)? It's easier to read with the hyphen and WP:RF ought to triumph over journalistic imitation. Martin of Sheffield (talk) 08:24, 7 September 2017 (UTC)
Sure, Americans write "co-op", too. (And I don't think anyone's contemplating the idea that WP can't have "co-operate" in it; it seems to be the usual UK spelling, and some Americans use it as well.)
This might be getting a little off-topic, but I don't know that I think "coöperate" is "journalese". In the current day, I strongly associate it with The New Yorker magazine; it's a bit of branding for them. But I've also seen it in old novels. --Trovatore (talk) 09:20, 7 September 2017 (UTC)
Well, I haven't kept track of usage of it in any detail. Regardless, it's just weird. I've seen a handful of other cases of the "Englaut", like "reëlection", but they seem even rarer.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  11:44, 7 September 2017 (UTC)
It seems to be standard and indispensable in Boötes. I can't think of another such example, but there may be some. --Trovatore (talk) 22:14, 7 September 2017 (UTC)
Laocoön, Brontë, but all three of those are proper names; the only word I can think of in English where an umlaut is still regularly used is naïve and even that's dying out. ‑ Iridescent 22:24, 7 September 2017 (UTC)
Yes; we had a thread about that (on one of the MoS talk pages, I think) just last month. Dictionary research showed that the naïve spelling is the secondary spelling choice in every dictionary that includes it, and some no longer include it. So I would list it as obsolescent.  — SMcCandlish ¢ ≽ⱷ҅ⱷ≼  22:57, 7 September 2017 (UTC)