Misplaced Pages

Revision as of 05:40, 6 January 2013

This is the talk page for discussing improvements to the Manual of Style page.

Put new text under old text. Click here to start a new topic. New to Misplaced Pages? Welcome! Learn to edit; get help. Assume good faith Be polite and avoid personal attacks Be welcoming to newcomers Seek dispute resolution if needed Shortcut WT:MOS

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

Template:MOS/R

For a list of suggested abbreviations for referring to style guides , see this page.

This is the talk page for discussing improvements to the Manual of Style page.

Put new text under old text. Click here to start a new topic. New to Misplaced Pages? Welcome! Learn to edit; get help. Assume good faith Be polite and avoid personal attacks Be welcoming to newcomers Seek dispute resolution if needed

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

WP:NCCAPS → "shorter than five letters" rule

With regards to this and this, and in general, isn't this whole "shorter than five letters" notion leading to inconsistent, illogical results? And where does it come from? (like, what's the reference work for title capitalization out there?)

I mean, as is, when in mid-title, it produces things like this:

"than", "from", "till", "Until" – ... from ... Until... looks weird, does it not?

To conform to this, From Dusk Till Dawn had just been changed to From Dusk till Dawn – problem is, it seems to be spelled From Dusk Till Dawn virtually everywhere else (a similar case would be Stranger than Fiction vs. IMDb's Stranger Than Fiction);

also, it's still Wait Until Dark, although "until" is just a one-letter-longer variant form of "till".

But if "till" were changed to "Till", we'd still have the lowercase "from", making for constructions like ... from ... Until... and ... from ... Till....

Changing "Until" to lowercase in turn would then be at variance with a whole host of other five-letters-or-longer prepositions and conjunctions.

Seriously, what the heck? I'm confused out of my mind...

As a followup, more contradictory examples:

My Bonnie Lies over the Ocean

vs.

Someone to Watch Over Me

Somewhere Over the Rainbow

One Flew Over the Cuckoo's Nest

Frost Over the World

Please, someone knowledgeable (What's the basis for the"shorter than five letters" rule? Where does it come from? Sources?) comment. While I do have a preference

– Honestly, don't the lowercased variations look downright weird to you, too? Like, did you ever see "One Flew Over the Cuckoo's Nest" given as "... over ..."? –,

I'm ready to put that aside if presented with logical and consistent guidelines. As is, it's confusing (I didn't change My Bonnie Lies over the Ocean to ... Over ... out of spite, but simply because I had its spelling elsewhere and entries like One Flew Over the Cuckoo's Nest in mind) and handled inconsistently. – ὁ οἶστρος (talk) 19:46, 10 December 2012 (UTC)

The correct approach is to defer to common usage, and spell things the way the rest of the world spells them. Anything else is original research and is prohibited in wikipedia. Apteva (talk) 20:03, 10 December 2012 (UTC)

We've always imposed local capitalization rules, regardless of how they are capitalized in the original or other sources. That's what MOS:CT is about. I tend to agree wth this editor (whose name I can't type) that this particular rule is on shaky ground.—Kww(talk) 20:10, 10 December 2012 (UTC)

I'm in favor of styling the caps consistently, but yeah, I think the 5-letter rule needs to be improved. Either an explicit list of words (and usages, for words that might be prepositions sometimes and other parts of speech others), or an explicit list of exceptions to the 5-letter rule, if the first list is unwieldy. -- JHunterJ (talk) 20:50, 10 December 2012 (UTC)

House style guidelines are not original research. -- JHunterJ (talk) 20:51, 10 December 2012 (UTC)

I for one will not wilfully go directly against the MoS in its current form (though, I might again by mistake). However, if the powers that be are insisting on sticking to that rule, I think the uninformed readers and editors deserve an explanation as to why the Encyclopædia Britannica, IMDb, AllRovi, Rotten Tomatoes, blu-ray.com, IGN, NNDB, Amazon, cduniverse.com, The New York Times, the Washington Post, the L.A. Times, Time magazine, the marketing divisions of film studios and countless others supposedly have got it so wrong. – ὁ οἶστρος (or, romanized, "ho oistros") (talk) 21:05, 10 December 2012 (UTC)

It's possibly a British/American English thing. All those sources are American, but the British Film Institute opts for lower capitalisation: BFI. Betty Logan (talk) 21:15, 10 December 2012 (UTC)

Variations in style need not be explained as errors. Dicklyon (talk) 21:25, 10 December 2012 (UTC)

Styles vary. Among guides that resemble ours on this four-letter rule are this and this and this. Dicklyon (talk) 21:13, 10 December 2012 (UTC)

Thanks for the links. However, two weren't searchable and within the excerpts of the third that were accessible I couldn't find any pertaining sections. There certainly must be a stronger case for that choice, right? How was it arrived at in the first place? Was it ever properly hashed out with broad participation?

The first gives the rule

Capitalize the main words in a title and the first and last word, but do not capitalize a, the, to, or prepositions and conjunctions of fewer than five letters when they occur in the middle of the title.

It goes on to say that "The Moon is Down" is wrong because is, though a short word is an important word, and that "Travels With Charley" is wrong. I would hasten to add that the advice, though, is to Hemingway or Steinbeck and to the publisher - were they to have chosen a capital letter, we would be constrained to report that error, in my opinion, although we would not be constrained to use all capitals, as many books do for their titles.

The second uses the rule to "Capitalize significant words in titles", and here the advice given is to people like wikipedia editors, where the advise is not on how to construct a title, but how to report a title, although the advice on "importance" I would say is more easily determined by the creator of the work. It says

The classic system is to capitalize the initial letters of the first and last words of a title or subtitle, as well as all major (or "significant") words. Do not capitalize articles (a, an, the), conjunctions (and, but, if) or short prepositions (at, in, on, of) unless they begin the title.

The third gives the sage advice that

The use of capital, or uppercase, letters is determined by custom. They are used to call attention to certain words, such as proper nouns and the first word of a sentence.

and goes on to say

Capitalize the initial letters of the first and last words of the title of a book, an article, a play, or a film, as well as all major words in the title. Do not capitalize articles (a, an, the) or coordinating conjunctions (and, but, for, or, nor, yet, so), unless they bigin or end the title (The Lives of a Cell). Capitalize propositions within titles only when they contain more than four letters (Between, Within, Until, After), unless you are following a style that recommends otherwise.

This advice appears to apply both to originators and reports of works. Apteva (talk) 23:10, 10 December 2012 (UTC)

Down in "The Moon is Down" is an adjective, not a preposition. I.e., down is serving the same function as red in the construction the moon is red. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 01:18, 28 December 2012 (UTC)

Betty Logan, the BFI is an interesting find. On the other hand, a quick perusing of other British organs – such as The Daily Telegraph, Financial Times, The Guardian and The Independent – showed no support for the "shorter than five letters" rule. – ὁ οἶστρος (talk) 22:00, 10 December 2012 (UTC)

Where the MOS can become OR is if no one writes "Somewhere over the Rainbow", and only Misplaced Pages writes it that way, that clearly is OR. Ditto if no one changes all caps in RUBBER SOUL to Rubber Soul, that is also OR. WP reports what the world does, and is, without making things up, which is what OR is. Apteva (talk) 22:38, 10 December 2012 (UTC)

It would be best not to keep confusing the content policy WP:NOR with styling guidelines; and this song is an odd case, since its actual title is Over the Rainbow. And it does appear in some sources with lower case "over", not rarely. And you're not seriously proposing that we use all caps in Rubber Soul, are you? Dicklyon (talk) 23:26, 10 December 2012 (UTC)

The thing to do when you find such inconsistencies is just to work on them. It is not surprising that WP still has lots of style inconsistencies. The MOS provides the guidance for which way to go to make things better. For example, Gerschwin's Someone to Watch over Me can be moved to lower-case over, which is not rare in reliable sources. See the first sentence of MOS:CAPS, which is what distinguishes our style from some others. Dicklyon (talk) 23:34, 10 December 2012 (UTC)

There are two problems with that though - first does it appear to accurately represent the actual title, and second while some books use "over" instead of "Over", "Over" is the preferred choice. But that is misleading because Someone to Watch Over Me is a popular book title, used by perhaps dozens of authors. Click on the Ngram links at the bottom, and try to even find references to Gershwin in any of the more recent citations. Apteva (talk) 01:00, 11 December 2012 (UTC)

Since Google Ngram Viewer is all about quantity (not quality), I don't see how this would be a suitable tool for establishing guidelines. Like, there are also significant instances of

"Neandertal" (treacherous, as the eponymous German valley actually is spelled "Neandertal")

vs.

"Neanderthal" or

"miniscule"

vs.

"minuscule".

The BFI, the lonely major source brought up that seems to use lowercasing for prepositions such as "over", also is not consistent with Misplaced Pages's MoS; e.g.,

Wait until Dark

vs.

Wait Until Dark. – ὁ οἶστρος (talk) 12:57, 11 December 2012 (UTC)

What I find interesting about all these style guides is that the question isn't really what to do with four character prepositions, it's what to do with five-and-longer ones. I think all of them would have "over" be in lower case, but some of them simply say that prepositions should be in lower case, and give no different rule for longer ones.—Kww(talk) 15:13, 11 December 2012 (UTC)

The more important rule is to capitalize "significant words" in a title. As to NGRAMs, that is a title issue, not a MOS issue. Apteva (talk) 05:22, 12 December 2012 (UTC)

While I personally think we should just go the IMDb way (as ungainly as some of the titles there look) and style everything according to the guidelines used there, to take JHunterJ up on his proposal, how about modifying WP:NCCAPS to accommodate for these spelling versions?:

• From Dusk till Dawn (covered by current policy)
• Wait until Dark (not covered by current policy)
• Stranger than Fiction (covered by current policy)
• My Bonnie Lies Over the Ocean / One Flew Over the Cuckoo's Nest (not covered by current policy)
• 20000 Leagues Under the Sea (covered by current policy)
• Once Upon a Time in America (not covered by current policy)
• Girl Walks into a Bar (covered by current policy) – not sure it shouldn't be "Into", though (even if it looks as ugly as "Is")
• The Englishman Who Went Up a Hill But Came Down a Mountain (not covered by current policy)
• It Came from Outer Space (covered by current policy)
• From Russia with Love (covered by current policy)

• Blue Like Jazz (not covered by current policy)
• Bridge Over Troubled Water (not covered by current policy)
• Alternate From Dusk Till Dawn (not covered by current policy)
• 33⅓ Revolutions Per Monkee (not covered by current policy)
• Star Trek Into Darkness (not covered by current policy)

Would be a compromise / hybrid of "both worlds": even more lowercasing but at the same time allowing for some exceptions to avoid counter-intuitive "butt-ugliness". – ὁ οἶστρος (talk) 12:49, 12 December 2012 (UTC)

The proper title of the last is logically Star Trek: Into Darkness (regardless what IMDb says - it is not a reliable source), so the "into" would be capitalized regardless of this debate (first or last word of a title or subtitle). 01:22, 28 December 2012 (UTC)

Added an alternate result for From Dusk Till Dawn, and added Bridge Over Troubled Water, Blue Like Jazz, and 33⅓ Revolutions Per Monkee. We can sort the List of English prepositions into "capitalized (when used as a preposition, as long as it's not the first or last word in a title or subtitle)" and "uncapitalized (unless it's either not used as a preposition or the first or last word in a title or subtitle)" -- JHunterJ (talk) 12:40, 12 December 2012 (UTC)

Seems to me you're advocating the IMDb model. I'd be all for that, the only constructions looking rather weird there that I can think of off the top of my head would be

... from ... Until... and

... from ... Till....

(as already mentioned in my very first post). Also, there's the question of "into" vs. "Into". Case for the former: it's just "in" and "to" put together; case for the latter: "Upon" and the like (but then, at IMDb, it's "Up" vs. "in"). Good idea about using that list. – ὁ οἶστρος (talk) 14:29, 12 December 2012 (UTC)

Thanks. I don't mean to advocate for deferring all of our titles to the IMDb's choice of caps. If we coincidentally land there, that's fine though. I don't think we should worry about which tiny words were assembled into which short words; the short words are now different enough and can't be simply replaced with their bits. Added one more: "Into Darkness" appears to be a subtitle in the new Star Trek film, even if they've made the weird call to omit a colon or hyphen or anything else. -- JHunterJ (talk) 14:58, 12 December 2012 (UTC)

I would not prefer IMDb's capitalization because it's IMDb, but because that seems to be the standard used, well, almost everywhere (if someone has the answer, I'd still like to know where they have borrowed it from).

Under Getting Started > Submission Guides > Title Formats (section Capitalization and character sets), they merely state:

"English language words which must begin with a lower-case letter are: an and as at by for from in of on or the to with".

It doesn't get simpler than that. Granted, it's a bit nonchalantly / loosely worded, omitting clarifications such as "unless they begin or end a title" (although that's implicitly taken into account), but I'm sure there are some Wikipedians who could elegantly and comprehensively incorporate the principles behind it into the existing MoS, while keeping it clear and readily accessible for everybody.

I suggest either adopting that approach in whole (which would cover everything JHunterJ would like to see) or amending it by adding

till,

until,

into,

onto and

than (but not Then)

to their list and be done with it (good-bye, "shorter than five letters" rule).

(By the way, browsing the database, you will find that IMDb is not always applying their own compass consistently, either, but in virtually every case that's just a matter of erroneous submissions that are open for correction – in the few cases where it's deliberate, then that's because they also do respect how the creators want their work spelled.) – ὁ οἶστρος (talk) 19:31, 12 December 2012 (UTC)

I see; I had misunderstood the IMDb suggestion, sorry! Yes, I'd be fine adopting their list, or adopting a similar list (such as your additions). I think I'd capitalize Till and Until and Than, but I've got no heartburn if WP decides to lowercase them. -- JHunterJ (talk) 19:33, 12 December 2012 (UTC)

That's the way I saw it, too. Actually, that's the reason all this started, as I – unwitting of the "shorter than five letters" rule – wanted to move From Noon till Three to From Noon Till Three. Meanwhile (primarily because of the unsightliness of "... from ... Till/Until ...", as in Lora from Morning Till Evening), I'd lowercase those few words. But crossing a Bridge over Troubled Water? I don't see that. – ὁ οἶστρος (talk) 20:09, 12 December 2012 (UTC)

Commment. This discussion seems to be quite film-centric, and maybe isn't taking fully into account the requirements of other projects that have prominent usage of composition titles, but surely we should be discussing any changes in terms of published style guides, and which we should take our lead from, rather than in terms of what other websites do. --Rob Sinden (talk) 13:49, 19 December 2012 (UTC)

But surely we are not restricted to published styles guides as the only input to this discussion. -- JHunterJ (talk) 13:52, 19 December 2012 (UTC)

I'm not sure. Isn't there an element of making up our own rules for the English language if we just copy what others do (or seem to do), rather than following established guidelines for usage? I guess it could be seen as WP:SYNTHESIS. --Rob Sinden (talk) 13:58, 19 December 2012 (UTC)

Establish guidelines contradict each other, so we'll have to "make up our rules" (or make up our minds) regardless, no one's suggesting we "just" copy what others seem to do, and style guidelines are not encyclopedia articles, so it can't be seen as WP:OR. Also, the problems above also include musical compositions/ -- JHunterJ (talk) 14:50, 19 December 2012 (UTC)

Yes, but we should be debating this in terms of the contradictions between the style guides and which established style we should adopt, not look to other websites to see what they do, without knowing their reasoning behind it (unless of course they have a published style guide). We don't know why the BFI or IMDB make the decisions they do. For all we know they could use a completely arbitrary system, so we shouldn't be following them. --Rob Sinden (talk) 15:29, 19 December 2012 (UTC)

I disagree. We should be debating this in terms of what makes the most sense (or best improvement) for Misplaced Pages. If a hypothetically arbitrary system makes the most sense for WP or results in the most improvement, we should use it. -- JHunterJ (talk) 15:49, 19 December 2012 (UTC)

That's just anarchy!  :) Should we start using arbitrary systems of punctuation and spelling too? We need to ensure our style guide has some basis in established usage. Whether that proves to be slavishly following one manual, or cherrypicking between different manuals, that's fine by me, but we shouldn't be inventing our own rules without seeking a precedent. --Rob Sinden (talk) 15:58, 19 December 2012 (UTC)

I doubt any system (capitalization, spelling, or punctuation) that makes sense for WP will be arbitrary, and none of the systems under discussion are arbitrary or without precedent. -- JHunterJ (talk) 16:18, 19 December 2012 (UTC)

Well, there is a suggestion above to copy what IMDB do, but also to add a few four letter prepositions, but not all of them, and there is no mention of phrasal verbs (which is what brought me to this discussion!). This seems pretty arbitrary and doesn't seem to follow any of the accepted precedents for title capitalisation. I wasn't party to earlier discussions regarding the current style guideline, but they seem to have been well considered, and to me, the proposed changes seem whimsical. Any changes should be considered more widely, and we should seek broad input from other projects, particularly literature and language projects, rather than base the changes on what an internet movie database (that we don't even trust as a reliable source) use for their criteria of titling films, then adding a few arbitrarily chosen prepositions of our own. --Rob Sinden (talk) 16:40, 19 December 2012 (UTC)

No one's suggesting any change to the way we handle phrasal verbs (we continue to capitalize them in all cases). This discussion is just around prepositions, but without any arbitrariness (no one's suggesting we cast lots to see which prepositions are capitalized). -- JHunterJ (talk) 17:21, 19 December 2012 (UTC)

To respond to the original post, I have no idea where the "five letter" so-called rule came from, and disagree with it (and wonder who added it, with what supposed consensus), but it's a moot point. We don't change the titles of published works, last I looked, if they are consistently done a particular way. Now, if movie posters for From Dusk Till Dawn sometimes spelled it "till", we'd have a case for applying MOS's lower-casing rule, but otherwise we don't. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 02:25, 24 December 2012 (UTC)

Actually, we ignore the capitalization used in the work and all reliable sources in favor of our own MOS, and not doing so would be an even harder change to get through.—Kww(talk) 02:52, 24 December 2012 (UTC)

I think SMcCandlish's point is that we typically do something like what MOS:TM makes explicit: editors should choose among styles already in use (not invent new ones) and choose the style that most closely resembles standard English. It makes as much sense for composition titles as for trademarks, perhaps. Dicklyon (talk) 05:46, 24 December 2012 (UTC)

Read again. He's saying we wouldn't apply our MOS rule to write "Dusk till Dawn" unless the movie posters used it inconsistently. That's just not the case.—Kww(talk) 06:17, 24 December 2012 (UTC)

Well, I won't try to speak for him. But I'm unclear on what you're saying. Are you stating your opinion of what we should do, or an interpretation of what we do do? In terms of "styles already in use", "till" is certainly out there, though maybe not in movie posters, which isn't were MOS:TM would suggest we look. If he really meant we should restrict to what we find on movie posters, I'd say, no, that's not what MOS suggests, nor what we do. Dicklyon (talk) 06:38, 24 December 2012 (UTC)

I was using posters as an example (add in press releases, reviews, IMDb listing, DVD cover, etc., etc.) If the title of the work is consistently spelled/capitalized/punctuated one way, why would we change it? I haven't seen anyone move Inglourious Basterds to a "correctly spelled" article name. On this micro-issue, I can only speak to what I do personally, which is name a work according to how it is spelled, if that's consistent, but if it hasn't been consistent and thus there is no "official" name, change it to what MOS prefers. I have not paid any attention to what others have been doing with such titles. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 01:15, 28 December 2012 (UTC)

Spelling and styling are two different issues. Of course we shouldn't change a spelling, but as far as style goes we follow our own MOS for capitalisation of composition titles per MOS:CT, regardless of the published capitalisation. --Rob Sinden (talk) 11:45, 28 December 2012 (UTC)

Not everyone entirely agrees that they are different issues. If you look at our most noisy and fractious perennial disputes here, you'll see that quite a few of them (most recently dashes vs. hyphens) come about because not everyone agrees they're distinguishable concerns in all cases. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:30, 1 January 2013 (UTC)

What multiple reliable sources explicitly say - continuing

Continuing from Misplaced Pages talk:Manual of Style/Archive 133#Three corrections, with permission from closing admin (User_talk:Nathan_Johnson#closure_of_rfc).

As I was saying, the IAU is the authority to be followed in comet names, it has prescribed hyphens, and a personal email has confirmed that they don't want dashes used as a replacement for hyphens. Waiting for a comment from Peter Coxhead. --Enric Naval (talk) 18:49, 19 December 2012 (UTC)

It seems to me that all of these punctuation/capitalization arguments for named things (comets, airports, works of art, trademarks) boil down to a choice among three possibilities:

A. Authoritative – As published by the naming authority, inventor, etc.

• What if the authority is typographically unreliable, routinely using all-caps, inconsistent style, or doesn't seem to know that there's a difference between a dash and a hyphen?

B. WP:COMMONNAME – The way it is usually seen by the general public in print.

• How do we filter out the sources that don't know the difference between a dash and a hyphen, or have inconsistent editing/styles (creeping into even the most well respected of pubs)?

C. Misplaced Pages style – According to WP:MOS, using "proper English grammar and punctuation", ignoring that it is a given name.

• MOS doesn't actually say anything about "proper English grammar and punctuation". MOS, determined by consensus, makes no pretense that it has discovered what is "proper", but rather MOS has selected, from many possibilities, a set of simple rules that editors can follow for consistency. The argument presented here also fails to understand that a proper name and how we choose to punctuate it are severable issues. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 04:59, 28 December 2012 (UTC)

I'm pretty sure I don't like C, but the other two are problematic in their own ways, and I'm not sure there can be a one-fits-all rule for when they disagree or do not yield clear majorities after filtering (not that it even seems reasonable to do that much work in each case). I'm leaning towards B in the hope that reasonably typographically and editorially reliable sources still predominate. —— 20:11, 19 December 2012 (UTC)

I've clarified C so that the straw man fallacy in it is important, and suggested alternative wording, in bold. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 06:08, 28 December 2012 (UTC)

For years A and B were the only options. When C was introduced last year it wrecked havoc, causing things to be very oddly named. Choosing between A and B is a constant theme at WP:RM, and there will never be any option of not doing so (William Jefferson Clinton vs. Bill Clinton). Apteva (talk) 21:01, 19 December 2012 (UTC)

No havoc was wreaked. Editors who disagree with the consensus disagree, and a small subset portray that disagreement in apocalyptic terms. -- JHunterJ (talk) 21:27, 19 December 2012 (UTC)

That is obviously disputed. Creating names that do not exist for hundreds of items is in my view clearly havoc. Apteva (talk) 01:50, 20 December 2012 (UTC)

It's not clear what you mean by "creating names that do not exist". Personally, when choosing styling for article titles, I follow the advice in MOS:TM, and choose from among styles used in reliable sources. I'm pretty sure that of all of the articles with en dashes that you have complained about and challenged, all are found with the same en dash styling in reliable sources. I'm not saying the MOS requires this (except for trademarks), just that I restrict my moves to such cases, to avoid controversy. I can't recall the last time anyone challenged such titles with sensible en dashes backed up by sources (besides you and now Enric who has joined you). I agree that "Creating names that do not exist for hundreds of items" might be a bad idea, but it's nothing like what's happening that you're bitching about. Your claim "This is obviously disputed" is just more whining. Cut it out. Dicklyon (talk) 07:38, 20 December 2012 (UTC)

Exactly. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 05:15, 28 December 2012 (UTC)

Also, this idea that styling of titles like text per the MOS is something that started last year is wrong. We've been doing that for all the years I've been at WP, at least since 2005 (like these hundreds on Sept. 30 2005), and I've seen some en dash titles go back to even earlier. Most do not provoke any controversy. Dicklyon (talk) 07:54, 20 December 2012 (UTC)

As far as I could tell, without checking them closely, all of those are pedantically correct, but annoying to anyone who does not like dashes in titles. But prior to 2008 there were technical restrictions on using dashes in titles anyway. None of those were proper nouns as far as I could tell. While it is annoying to me to see dashes used for something like the Michelson-Morley experiment - something that is rarely spelled with a dash, it is the proper nouns that are of more concern. But strictly speaking all should be named following common usage and not try to be pedantically correct. It is pretty easy to form an analogy between learning a little bit about something and then going out and applying that knowledge in areas that it no longer applies, which is exactly what was done. Show me one style guide that has an example of a bridge, war, airport, comet, or any other proper noun spelled with a dash. I can not find any in New Hart's Rules. I think we just made that up, and it just is not justifiable. Apteva (talk) 08:32, 20 December 2012 (UTC)

That's the crux of the matter: "anyone who does not like dashes in titles". That's a baldfaced WP:IDONTLIKEIT argument, and no basis for a change in MOS. There is probably no one on WP who can't think of something they don't like in MOS, but they deal with it and don't throw months-long, forum-shopping, disruptive hissy fits about it. And this "rarely spelled with a dash" crap is nonsense and you know it. It's been explained to you dozens of times that dashes are somewhat uncommon in news and other run-of-the-mill prose, simply for expediency reasons: keyboards don't have dash keys, and people on deadline won't bother to figure out how to insert one. You know this is true, but you just pretend you don't because it's inconvenient to your ridiculously tendentious argumentation. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 05:15, 28 December 2012 (UTC)

@ Alan: COMMONNAME governs names, the MOS the formatting of those names. Trying to follow COMMONNAME for stylistic choices and punctuation results in all sorts of inconsistencies, which is why print publishers drew up MOS's in the first place. — kwami (talk) 21:51, 19 December 2012 (UTC)

And we are not a print publisher. Apteva (talk) 08:32, 20 December 2012 (UTC)

This is not a WP:NOT#PAPER matter; as usual, you do not appear to have understood the policy you are making reference to. There is no conflict between what WP is doing and what a print encyclopedia would do on this issue. In actuality, WP needs an MoS even more than a print publisher would, because we have orders of magnitude more writer-editors and readers, facing orders of magnitude more subjects, the specialists in all of which would blissfully impose their own style on "their topic" and its articles, regardless of the effects this might have on non-specialists (and on specialists in other fields). Until you actually absorb and understand WP policies and guidelines better, you'd do well to steer clear of trying to cite them in arguments on which almost everyone is disagreeing with you (hint: you're probably making a mistake if this happens), especially ones you're already being RFC/U'd for. You should not even be squabbling here about this at all, unless your intent is to further convince people that your purpose here is to singlemindedly push this issue at all costs, until you get WP:ARBCOMed. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 04:49, 28 December 2012 (UTC)

B is often the worst of all possible choices, it seems to me. It will often lead to inconsistency and dispute, especially in an international encyclopaedia, since what is "common" in a topic area in one country is often not in another.

I strongly support following internationally recognized authorities whose remit is nomenclature, where these exist. Where they don't, Misplaced Pages is entitled to draw up its own guidance, but this must be based on consensus not the dictatorship of the majority.

If the IAU explicitly mandates hyphens rather than dashes in comet names, then this style should, of course, be followed. Peter coxhead (talk) 23:11, 19 December 2012 (UTC)

But they don't mandate anything about, or even recognize the existence of, en dashes. Enric didn't ask about en dashes, and the response didn't say; the guy interpreted the question about "dash" to be about the sentence punctuation dash, not the en dash, as his response makes clear: "Dashes are marks like semi-colons, commas, and periods, used grammatically in sentence structure. Hyphens link words together, not dashes." He thereby declared himself ignorant of the concept of an en dash, which is not so unusual. He did say "It is strictly not correct to write 'Comet Hale-Bopp'", which I assume applies also to the form with an en dash. But that's not so useful here, since Comet Hale–Bopp is what it's commonly called, and we use COMMONNAME (option B) for titles, not official designators (option A) like his suggestion "Comet C/1995 O1 (Hale-Bopp)". Styling is a different matter. Option C is not an alternative to A or B, but goes along with either or both; perhaps better with B. On whether the IAU mandates, or even recommends, a typographical styling, one could ask them if Nature always gets it wrong; or Icarus; or Earth, Moon, and Planets. They probably won't understand the question, just as they didn't understand Enric's. Dicklyon (talk) 00:44, 20 December 2012 (UTC)

(I mean to respond to AlanM1, not Dicklyon, but couldn't figure out how to do so with the out-dent.) I don't really think it matters what the IAU thinks is the best name. Even leaving aside the possibility of a gramatically-ignorant official source – which seems to possibly be the case here – I nonetheless think that "C" is the best option of these. Are we really going to create a whole list of exceptions to the en-dash formatting rules for particular situations where "official" sources disagree with us? What if there are multiple competing "official" sources with different rules? Or what if common usage is ambiguous? Do we discount sources that appear not to distinguish between hyphens and dashes? Personally I think that the MOS' rules about dash use are confusing enough without a laundry list of particular exceptions for instances where the "official" or common name uses a hyphen rather than a dash. AgnosticAphid talk 01:05, 20 December 2012 (UTC)

How about another email, this time asking explicitly for en dashes?

@Agnosticaphid. In this case there is only only one naming authority and only one rule, just like the case of the cultivar names. --Enric Naval (talk) 13:19, 21 December 2012 (UTC)

I just meant that the MOS would have to say, "instead of an en dash to link these independent elements, comets use hyphens per the IAU," and then presumably there are other instances where the "official" source uses a hyphen, so we'd have to add whatever those things are, and to me it all seems a bit unmanageable and inconsistent with the purpose of the MOS which I think is to ensure stylistic consistency.AgnosticAphid talk 15:30, 21 December 2012 (UTC)

Well, this is an encyclopedia, it should write hyphenated names with a hyphen. It shouldn't force dash usage to enforce stylistic consistency. I can't imagine Britannica or Merriam-Webster writing Hale-Bopp with a dash just to enforce some internal style rule. They write it with a hyphen.

The Chicago MOS 16 th edition defers to external naming authorities in several places:

• 8.118. Scientific terms–additional resources. (...) The ultimate authorities are the International Code of Botanical Nomenclature (ICBN), whose guidelines are followed in the botanical examples below, and the International Code of Zoological Nomenclature (ICZN) (see bibliog. 5). Note that some fields, such as virology, have slightly different rules. Writers and editors should try to follow the standards established within those fields.
• "8.136. Astronomical terms–additional resources. The following paragraphs offer only the most general guidelines. Writers or editors working in astronomy or astrophysics should consult Scientific Style and Format (bibliog. 1.1) and the website of the International Astronomical Union."
• "10.66 Naming Conventions for Chemical Elements. 'he International Union of Pure and Applied Chemistry (IUPAC) is the recognized body that formally approves element names. (...)"

--Enric Naval (talk) 12:51, 22 December 2012 (UTC)

That's their option. Most of CMoS consists of points on which they do not defer to anyone, but insist on their own prescriptive rules. MOS happens to do this more than CMoS does on certain points (and less on others). Oh well; live with it and move on. You're also confusing names with how they are styled. This is like confusing the content of this page with the font styles in which you are viewing it (hint: they can vary from browser to browser, be modified by CSS, and even be inapplicable, e.g. in a screen reader for the visually impaired). Information on a topic is severable from the style in which that content is marked up, online or offline. Fighting over en dashes (being used as long hyphens, as pointed out below) is not like trying to contradict ICBN or ICZN on what the actual name of a species is. Again, see the logic in WP:SSF: A source being reliable on what the name or other underlying facts are about something in a particular field does not somehow make it a reliable source for how to punctuate English-language prose in a general-purpose encyclopedia. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 04:40, 28 December 2012 (UTC)

• Please focus. The only option under discussion is including C. A and B always exist, and are not the issue. Apteva (talk) 01:50, 20 December 2012 (UTC)

As I was saying, the opponents of the MOS dash guidelines (consensually derived in 2011 by 60 contributing editors, under ArbCom supervision) need to read something systematic and enlightened on the topic under dispute. Then, and only then, can they engage meaningfully in dialogue with editors who do know the theory behind these things, and do understand the difference between content and the styling of content.

I referred earlier to CGEL's chapter on punctuation. Any takers? Any interest? Or should we tightly restrict deliberations, so that off-the-cuff responses from such non-style "authorities" as IAU (to leading questions) will determine style on Misplaced Pages? Note, of course, that the vice-president of IAU evinces no acquaintance with the en dash at all. Contrast the major guides that inspire the best-practice guidelines consensually presented in MOS. Those major guides discuss naming of comets and the like also, remember.

Please: just let me know. I can help. But if editors prefer to remain beyond help, inform me so I can do something less futile – instead of attempting to engage people who are fanatically committed to ignoring how hyphens and en dashes actually work, in actual high-quality publication.

♥

Noetica 03:54, 20 December 2012 (UTC)

Thanks. Please do a careful read of the entire CGEL (Cambridge Grammar of the English Language ISBN 978-0521431460}, and tell me if there is an example of an airport, bridge, war, comet, or any other proper noun spelled with an endash anywhere in the entire book. I am pretty much up to speed on knowing how to correctly use endashes, emdashes, and hyphens in sentences, but see no reason to extend dashes to named items, which, by definition have a specific name. Apteva (talk) 08:06, 20 December 2012 (UTC)

But what difference could that make, Apteva? If I pointed out that nowhere in CGEL is there any support for your wild surmise that proper names never have an en dash, how would that move things along? If I did present such an example from CGEL, what difference would that hard evidence make? To you, I mean. Would it terminate or even shorten your ridiculous campaign?

Very well, let's see. From CGEL, p. 1762:

the Lewis–Jones Company

Nor is CGEL idiosyncratic in this. From The Penguin Dictionary of Proper Names (revised edition, 1991; my usual underlining for emphasis), on p. 230:

Hitler–Stalin Pact ("sometimes called the Ribbentrop–Molotov Pact")

And on the very next page:

Hoare–Laval Pact

That dictionary of proper names does not apply distracting title case to its entries; there are plenty in which main words are in lower case, like "Hobson Memorial lectures" and "Odder–Neisse line". Not everyone thinks that every construction functioning as a proper name has its status marked by capitalisation. One more for good measure:

Panhard–Levassor ("French firm of car manufacturers")

So will you stop now, please? Can we all stop, in fact? The RFC has ended, remember. So have most of the other drawn-out diatribes over en dashes, in scattered theatres of conflict where editors' reserves of time and patience are squandered.

The community has spoken, as it did in 2011. Live with it – as we all must live with not getting our way in an imperfect world.

Noetica 11:34, 20 December 2012 (UTC)

Noetica, welcome back! I'm glad you've got that fat book! Dicklyon (talk) 16:07, 20 December 2012 (UTC)

Thanks, and it is correct that even if it had a list of all the comets in the world with endashes it would not change the fact that the preferred spelling is with a hyphen. And if it had no proper nouns with an endash that also would not change anything, but it does confirm that one book on grammar, not style, but grammar, does have some examples of using an endash in a proper noun. The acid test still is, is that the most common spelling of Panhard–Levassor, Hoare–Laval Pact, and Hitler–Stalin Pact, and is the official or most common spelling of Lewis–Jones Company (likely a made up example - there are lots of Lewis Jones Companies but they all use a space, and of course Mcgraw-Hill uses a hyphen). I will also note that CGEL does not attempt to be representative, but calls pronouns nouns, and explains the reasoning, though that falls on deaf ears of every teacher teaching grammar, and so should we turn a deaf ear. So no, it does not change anything, and no there is still not any consensus on hyphens and dashes, although it would be trivial to reach consensus if everyone was interested in finding out which areas there is consensus and which there is not. For example, it is pedantically correct to write Michelson–Morley experiment, but that is not the way most people write it, so that is out. No one writes comets or airports with an endash so that is out, and ditto for wars and bridges. And as to the places that dashes are correctly used - in sentences like this one, what is all the fuss about, the sentence does not change its meaning because of three missing pixels. Apteva (talk) 11:04, 21 December 2012 (UTC)

So why make this request at all:

"Tell me if there is an example of an airport, bridge, war, comet, or any other proper noun spelled with an endash anywhere in the entire book." – Apteva

Why did you waste my time, and everyone else's, yet again? I answered your challenge. But why did you make it?

If you are immune to evidence, don't ask for it. If you do not believe in rational dialogue that can change opinions, don't pretend to engage in it.

(Hence the RFC/U.)

Noetica 12:59, 21 December 2012 (UTC)

It was not a waste of time and I am appreciative of the effort it took. The question was did WP editors make this up or did any of them see it in a book somewhere. Clearly it is not a standard interpretation, as few books are published using an endash within a proper noun, and is not an appropriate interpretation for wikipedia. I knew that some books do but none of the style guides that I have access to suggest doing so. I have tried isolating the anomalies to publishers but have not done a rigorous analysis. It seems more random than anything else - for example the paper that used endashes for everything, and a minus sign for a range. Apteva (talk) 05:21, 22 December 2012 (UTC)

One problem here may be that the words dash and hyphen are both used with different meanings.

• On the one hand, we have the terminology (used, for instance, by the CGEL - and apparently by the IAU) where
  • dash is used to designate (syntactically) a punctuation mark that can be represented typographically by a spaced en rule or an unspaced em rule (for instance to indicate parenthetical information) and
  • hyphen is used to designate a mark that is used to connect two words and takes the typographic form of an (ordinary) hyphen or a long hyphen (represented by an en rule), depending on the relationship between the two words thus connected.
• On the other hand we have the terminology - which may risk a conflation of the syntactic and typographic roles - where
  • dash is used for various types of horizontal rule, including
  • the "en dash" and
  • the "em dash".

--Boson (talk) 12:34, 22 December 2012 (UTC)

Good way to look at it. Apteva, Enric and Wikid: Misplaced Pages uses a normal (short) hyphen most of the time. When juxtaposing two separate entities (Mexican–American War, Seattle–Tacoma Airport) in a name or title, Misplaced Pages uses a longer hyphen, to distinguish such a case from the case of a two-part hyphenated name (Lord Baden-Powell. This longer hyphen incidentally uses the same glyph as the en-dash that is sometimes (when the unspaced em-dash is not used) used as a spaced indicator of a parenthetical. The long hyphen is a simple disambiguator. You are free to not bother with it; someone else will correct it if you use the short hyphen where MOS wants a longer one. Now please back away from the horse carcass and drop the bludgeon. Please get over your unreasonable and obsessive fits of rage about the matter. It doesn't really matter, and you need to internalize that fact. If you won't, then you are clearly not here to write an encyclopedia, but rather to push an agenda and engage in bitter argument for its own sake. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 04:25, 28 December 2012 (UTC)

Many books do look at it that way. The glyph is known to many as the "en rule", and the function as "long hyphen". Others merge these into "en dash". Dicklyon (talk) 05:04, 28 December 2012 (UTC)

I propose we adopt this in MOS to reduce confusion and strife. Immediately. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 06:27, 28 December 2012 (UTC)

Short version: Read WP:SSF. Summary: Reliable sources on astronomy are not reliable sources on English language usage, and on style matters do not trump our in-house style (likewise MOS doesn't dictate how people stylize and punctuate in astronomy textbooks and journals). PS: Atpeva, when you're being RFC/U'd for disruption and tendentiousness on this issue, it's probably not wise to bring it up yet again. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 01:27, 28 December 2012 (UTC)

Let's point out please that that is your personal essay, not something that has consensus, though no doubt there are other MOS regulars who agree with it. --Trovatore (talk) 01:32, 28 December 2012 (UTC)

I never claimed it was anything but an essay. It's not whether it has a special tag on it declaring it a guideline, it's the fact that it has logic in it that no one has been able to refute. The argument that an astronomy source is automatically a reliable source on how Misplaced Pages should style English writing in a general purpose encyclopedia just because astronomy is involved is absurd on its face. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 01:37, 28 December 2012 (UTC)

The difference between an essay and a guideline (well, the difference relevant in this case, anyway) is not a tag; it's consensus. As for it being a matter of "logic", that's just not so. You have a normative view that there should be a centralized style; others have a normative view that style should follow the usage of the field of study. Each view has merits and demerits, but neither is a matter of logic. --Trovatore (talk) 01:42, 28 December 2012 (UTC)

I never asserted the essay had consensus; if it did, it would be a guideline. I'm not sure what point you think you're making, but it's not working. You keep basically rebutting the idea that WP:SSF has the force of a policy or guideline, but no one has made any such claim, and mistaking that as being the central issue means you are not understanding what WP:SSF is, why it exists or why what it says matters. You can keep telling yourself it's all just a matter of opinion, but the essay completely shreds the "follow the usage of the field of study" argument on logical grounds, demonstrating its numerous fallacies. The essay has its own talk page; feel free to take up any issues you have with it there. The short version of why it matters is that virtually every single specialty, vocational and avocational, in the world has stylistic nitpicks used within its own specialist publications that conflict with general English usage and even more directly conflict with in-field usage by specialists in other fields. Even aside from the fact that no one can be expected to remember the weird style bugbears of every field there is, the fact that they conflict with each other, and most importantly with normal English usage, logically means we cannot kowtow to every stylistic whim of specializations, but have to stick to general English usage, as we have codified it at MOS, or the encyclopedia's writing will have a confusing lack of consistency that makes it harder to read and understand, and even worse to edit. More detailed discussion of WP:SSF is rather off-topic at WT:MOS; it has its own talk page for a reason. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 04:09, 28 December 2012 (UTC)

You have not made any such claims explicitly. In my opinion it is — or at the very least, risks appearing &mdash disingenuous, to answer a question by giving a link that looks guideline-like, without mentioning that this thing is almost entirely your work and can be assumed to be mainly your personal opinion (though, as I say, there will of course be others who agree).

I completely disagree with you, of course, as to the success of the essay, at least the parts of it I've read (you do tend to go on a bit, frankly). My basic analysis is that you treat the argument of your opponents as identifying the use of reliable sources for content with copying their style, as though no distinction could be made between the two things. If that were the actual argument, it would still not be a mistake of logic, but it would be a pretty obvious mistake.

But almost no one, I think, takes that actual position. The strongest real position along that lines that your are likely to encounter is that it is not desirable to make such a distinction. That, clearly, cannot be refuted as matter of logic, though you might certainly attempt to refute it on other grounds.

It may be that people sometimes say that there is no distinction between using reliable sources for content, and copying their style. It is generally polite, when people say things they obviously cannot literally mean, to address what they probably meant, while pointing out gently that it isn't what they said. --Trovatore (talk) 05:06, 28 December 2012 (UTC)

I'm not aware of anyone, major author of it or not, who prefaces or postscripts their links to any essay with something like "by the way, this is an essay not a guideline or policy". Editors can read, and the page clearly has an essay tag on it. I don't like to insult other editors' intelligence. I never tell people they have to do this or that based on WP:SSF; I ask them to see WP:SSF for why a particular argument is fallacious and unhelpful on WP. As for the substantive matter, I would love to be able to agree with you, but the fact of the matter is that most of the cases of SSF that arise are in fact people asserting that WP "must" do it the same way as journals or newsletters or whatever in field X simply because that's how they do it, that it is "wrong", not just undesirable, to separate content and style when it comes to their particular peccadillo. Proponents of SSF-inflected arguments usually cannot at all see any difference between citing facts from their favored sources and aping the style of those sources when it comes to those facts, and see the two as utterly non-severable. They do "take that actual position", and will sometimes defend it to the point of WP:DIVA threats to quit WP if they don't get their way. I wouldn't have needed to write WP:SSF otherwise. Apteva is doing this right now. He does not believe that how the name comet Hale–Bopp is styled can legitimately be done, in any publication of any kind, other than how the IAU does it in astronomy journals. He's fought half way to death over the issue, with no signs of letting up, despite the RFC/U. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 06:08, 28 December 2012 (UTC)

Pretty much any specialty tends to capitalize their own important terms, and they tend to drop hyphens from compound modifiers that are familiar within their specialty (like the AMA guide that in recent years changed to recommend dropping the hyphen from small-cell carcinoma). Both of these specialist tendencies are contrary to what makes sense for a general readership, and contrary to what our MOS should recommend (in my opinion). Some of these ideas should propagate from the essay to the guidelines, I think. Dicklyon (talk) 04:18, 28 December 2012 (UTC)

I think you overestimate how much of the capitalization thing is about importance. Sometimes it serves some quite distinct function (as in American Robin versus American robin, to take an emotionally charged example). But in any case I am happy to agree that we should not slavishly copy every minuscule detail of style from specialist usage (though I think we owe a certain amount of deference to reasonably founded claims that some details serve a purpose). My beef here with SMcC is that he thinks he's identified a basic flaw of logic, and I say he has not, at least not with the serious arguments for following usage in the field. --Trovatore (talk) 05:11, 28 December 2012 (UTC)

More people than WP:BIRDS will admit simply don't buy that that this supposed American Robin vs. American robin distinction is actually special or linguistically necessary. "Importance" is probably the wrong word; "emphasis" is more accurate. People in all fields, from academics to hobbyists, like to use capitalization as a form of emphasis, and it's usually not questioned in their in-field publications. Most of them also have the sense to not try to port their field's stylistic quirks to more general publications. Even ornithologists know not to capitalize bird common names when writing for more general zoology or science journals. (It's a shame that around a dozen of them on WP don't and refuse to acknowledge this.) Capitalizing "American Robin" to distinguish it from "American robins", in the "robins of the Americas" (or of the US or of North America, whatever) sense, is also simply a form of emphasis, whether birders want to admit it or not. The proof is in the fact that you can simply word more precisely: "The American robin is easily confused with several other species of robins found in North America", for example, in place of the bollocksy "The American robin should not be confused with other American robins" pseudo-example that birders like to trot out as why they "need" capitalization, when in reality no one but a moron would write that. Virtually no other field of zoology or botany has relied on such a lame excuse, and they all do just fine without capitalizing common names of species.

As I've pointed out before, the birders' solidarity on this issue (aside from being illusory - most members of WP:BIRDS simply don't care and refuse to participate in such arguments) is based on a misunderstanding of the factual history of the issue to begin with. Birdwatching field guides do not capitalize bird species common names because this is an ornithological standard. They do it for blatant emphasis. Virtually all field guides about everything do it, from wildflowers to amphibians, because it makes it easier to quickly scan species names in the prose when you are in the field trying to ID something. They've been doing this since at least the 19th century, long before the IOU came up with an academic standard calling for capitalization. It's pure coincidence.

Regardless, MOS says do not use capitalization as a form of emphasis. WP is not a field guide or an academic journal. MOS actually gives a lot of deference to specialist styles, from how measures and units are written to how royal and noble styles are presented to how mathematics are represented – as long as it doesn't conflict with basic expectations about English grammar and usage. If it would produce a "WTF? I should fix that typo..." reaction in the average editor, MOS deprecates it. I'm not going to debate WP:SSF in any detail here. (And, yes, it is too rambling.)

— SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 06:12, 28 December 2012 (UTC)

I'm not quite sure how this turned into yet another discussion of the merits or otherwise of capitalizing common names (it might suggest that SMcCandlish is as obsessed with this issue as he claims his opponents are). However, it's a bit off the point. If anyone has claimed that the styles which happen to be used in specialist sources should be copied in articles concerned with that specialism solely because they are used in specialist sources, then they have put forward a weak argument (if not necessarily an illogical one). However, if an authoritative body explicitly specifies preferred styles for its specialist area, then there is nothing illogical about choosing to follow these styles. If the IAU explicitly recommended the use of hyphens rather than en-dashes in the names of comets, then it would be no more illogical to adopt this style than it is to italicize the scientific names of organisms at the genus level or below (but not above) based on the IC(B)N or the ICZN. (As it happens, the evidence that the IAU does this is at present not very convincing.) Peter coxhead (talk) 01:34, 1 January 2013 (UTC)

Trovatore brought up the birds, not me. And it was germane anyway, since we were talking about WP:SSF, which was written largely in response to the birds debate (though has proven applicable to many, many others, clearly including this "must use a hyphen because my preferred sources use one, and I am making wild assumptions about why, yet insisting my interpretation is righteously correct and going on a holy war about it" case). Capitalizing the common names of species just because journals in a particular field mostly do so is, for better or worse, the establishing and "canonical" example of the specialist style fallacy on Misplaced Pages. I already acknowledged the sub-thread was off the point, and have twice pointed to WT:SSF as where to talk about it. Any other things you want to whack me for that I didn't actually do or which aren't my fault? The (very) weak argument you point to, that the style from a type of specialist source "must" be used in WP articles on the same topic because of its use in those specialist sources, demonstrably is put forth by proponents of SSF arguments; that's the entire point of that essay existing. WP:SSF is not a mischaracterizing straw man, it's based on direct, long-term observation of the irrational arguments made by those advocating specialist style fallacies, which are always based in a faulting understanding of "follow the sources", and contingent upon browbeating, incessant assertion that because reliable sources in that field/on that topic use style quirk X, WP must follow suit. It is this argument that makes it the SS fallacy to begin with. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:47, 1 January 2013 (UTC)

O, this goes on and on! How can it be? There was an RFC; it was closed. And then the discussion rises with new heads like the Hydra. We need to decide: do RFCs settle matters here, or not?

About IAU:

• They are unaware of the existence of en dashes, let alone the use of en dashes to serve as substitutes for an ordinary hyphen when certain semantic distinctions are to be made (the "long hyphen" function, which Dicklyon and Boson have mentioned on this page following CGEL, and which SMcCandlish has enthusiastically embraced).
• Other respected style authorities flatly disagree with IAU's style-ignorant rulings. NHR and its associated publications – like Oxford Dictionary for Scientific Writers and Editors (ODSWE), to say nothing of OED – give style-aware rulings, for general publication for ordinary real readers. Like ours. They do distinguish ordinary hyphen and its variant: the "long hyphen", realised by en dash and frequently referred to by that name. And they rule differently from IAU.
• Our style choices are nearly always based on NHR, CMOS, OED, and such best-practice, industry-standard, widely subscribed and reliable sources.
• If nothing else will decide the matter, we are entitled to spurn IAU's blinkered ways when we see that they want the hyphen removed from the double-barreled surname of a discoverer of a comet. However well that works for the comet-spotting community, it blends like oil in water on Misplaced Pages. It does not accord with any other MOS recommendations; and it is bound to confuse our readers.

I propose that we drop this topic for the new year. An RFC has run its long winding course; another, similarly long, has snaked to a similar hole of oblivion at the Village Pump; the community has dismissed the alternative view at several polemical and time-consuming RMs; MOS editors who care and who worked tirelessly to settle all of this in 2011 are all but pilloried for continuing to defend a consensus that proves its robustness again and again; and we are waiting on a formal conclusion to a decisive RFC/U for the editor who did most to make clear waters turbid yet again.

Drop it. Next topic, please?

Noetica 04:39, 1 January 2013 (UTC)

I submit that it is more likely to confuse Misplaced Pages's readers when the Misplaced Pages MOS mandates spellings that aren't found in the vast majority of our sources. It puts Misplaced Pages in the position of promoting idiosyncratic spellings not favored by most reliable sources. It astounds me that people simultaneously hold that most Misplaced Pages readers are completely blind to the distinction between hyphens and dashes and yet at the same time stridently maintain that failure to strictly hew to a very complex and intricate set of dash rules will cause endless and widespread confusion. Logically there's no way that both of these things can be true, but I've seen this argument made here over and over again. I don't think there's any evidence that hyphens in place of dashes cause any confusion in actual practice. I do think there's ample evidence that en-dashes are strongly preferred for some uncontroversial uses such as date and numeric ranges. Quale (talk) 05:34, 1 January 2013 (UTC)

What the heck are you going on about? Where does the MOS have anything to say about spelling? Only in MOS:ENGVAR, MOS:QUOTES, and MOS:FOREIGN. None of these mandate unusual spellings. And who are you talking about that holds that "most Misplaced Pages readers are completely blind to the distinction between hyphens and dashes" and/or that "maintain that failure to strictly hew to a very complex and intricate set of dash rules will cause endless and widespread confusion". I haven't seen either of those positions espoused here. The MOS is flexible in what it allows from editors, and makes no real mandates. It does provide guidance toward what would be considered an improvement, however, and we wouldn't bother if we thought nobody would notice. Dicklyon (talk) 05:50, 1 January 2013 (UTC)

Quale, I do wonder sometimes. Did you read what I wrote about those appeals to conform with the style-blind content experts at IAU? They actually want to remove the hyphen from the surname of a comet-discoverer, contorting it to fit with their strange rules. You come here with a claim that MOS is against common, readable forms? "Most reliable sources", of which you speak, style their productions in all sorts of weird ways. The role of WP:MOS and its subpages is to sort that out in the interests of the general reader. Do you really think IAU does a better job? Note, for a start: IAU never set out to meet the needs of the general reader. NHR, OED, CMOS, and the other genuine authorities on language and style do set out with that purpose. So does Misplaced Pages; and therefore, MOS adopts and adapts the best guidance chosen from them. And from high-quality publishers, who typically follow one or other of them. The decisions here are made consensually. I'm sure most editors here fervently hope that will continue. (Most, not all.) We have a firm consensus about use of en dashes. It has lasted well. Accept it, or challenge it as not a genuine consensus, because consensus has changed since it was tested in mid-2011, somehow. Do not challenge it with spurious arguments that have been traversed again and again, and that bring even the responsible editors here into disrepute when we resist die-hard partisans who will not drop the stick.

Guilt by association is grossly unfair; and we have a right to be fed up with it.

Time to close this thread. It will get us nowhere.

Noetica 07:21, 1 January 2013 (UTC)

Strange rules? You mean IAU's prerogative to spell and capitalize names in whatever manner they find adequate? Oh, you have no idea....:

• Singer-Brewster - - > Singer Brewster
• 't Hooft - - > Thooft
• Pan-STARRS - - > PANSTARRS
• Bally-Urban + Clayton - - > Bally-Clayton (ironically, it's because the hyphen in Baly-Urban could be confused with the hyphens that separate discoverer names...)

--Enric Naval (talk) 00:15, 6 January 2013 (UTC)

What do you mean by "you have no idea"? Since you seem determined to stop this thread getting archived by replying to me four days later, I will respond: IAU, as consenting adults, can do what they damn well like. But then so can OED, NHR, ODSWE, and WP:MOS. Get it, and move on. Some scholarly sources speak of "Comet Singer Brewster", some of "Comet Singer-Brewster" – a comet discovered, after all, by Stephen Singer-Brewster. The major style guides that have heard of en dashes generally use them, enabling preservation of the universally accepted styling of the discoverer's name. WP:MOS is that sort of major style guide. Biggest, most comprehensive, most nuanced on the web, yet with consensually developed guidelines. Now can we stop? Noetica 00:55, 6 January 2013 (UTC)

I hadn't noticed this was 4 days old. I just wanted to point out the glaring error in your argument: Misplaced Pages doesn't follow style guides or grammar rules when naming comets and minor planets. Instead, Misplaced Pages follows IAU's "strange rules":

• Aaron Burrows - - > Aaronburrows
• Alena Šolcová - - > Alenašolcová
• Schärding - - > Schaerding
• Zashiki-warashi - - > Zashikiwarashi
• Shen Chun-shan - - > Shenchunshan

There are even weirder names, all of them following IAU's rules. Except, of course, 79360 Sila–Nunam. And all comets with multiple discoverers. And all because some people think that astronomical names need to follow English grammar rules in order to be correct. (Why not read "10 Weird Rules That Control How We Name the Planets" and its helpful advice: "do not question the IAU about its rules" in all caps.) --Enric Naval (talk) 03:07, 6 January 2013 (UTC)

Which argument are you talking about? And how have you pointed out a "glaring error" in it? Wait, let me preempt you so we can just wrap this up, OK?
Misplaced Pages articles have all sorts of irregular and inconsistent titles. Some conform to the consensual guidelines at WP:MOS (the central source of Wikipedian style recommendations, which trumps all others when there is a conflict). You cite this, from an external source that has no authority over Misplaced Pages and no assent in any consensus here: "do not question the IAU about its rules". O yeah? Sorry, Misplaced Pages will question what it damn well wants to question. IAU can do what they like. Publishers inclined to follow them are free to do so. Some do, some do not. Misplaced Pages's style guidelines do not. Live with it.
Now can we stop?
Noetica 03:38, 6 January 2013 (UTC)

Your argument is that WP:MOS regulates comet and minor planet names in wikipedia. But the truth is that they are regulated by IAU's "strange rules". Misplaced Pages writes Singer Brewster without a hyphen because the IAU says so, and the MOS doesn't have any say on it. --Enric Naval (talk) 04:08, 6 January 2013 (UTC)

In the article's context, "DO NOT QUESTION THE IAU ABOUT ITS RULES" was of course a joke. Art LaPella (talk) 04:16, 6 January 2013 (UTC)

• Enric, no. My argument is that MOS can be applied in the styling of article titles, any time. That is part of its role. But do not take this as an opportunity to continue your old dispute about that, yet again. MOS is applied to the article Comet Hale–Bopp, according to strong consensus recognised by ArbCom. MOS has not yet been applied to all such titles, but it could be. WP:MOS, as I have said, is recognised as the main style resource, and in cases of dispute we default to its recommendations. Again, this not an invitation to recycle your dissent from consensus and ArbCom's view on that topic, either.
• Art, yes. It's a joke here too. Who could take it seriously? (That's a rhetorical question. Can we stop now?)

Noetica 05:00, 6 January 2013 (UTC)

• Ah, the vague assertions that MOS applies to all articles, even in articles where it clearly doesn't, like Singer Brewster.... OK, no point in continuing this. I'll end up thinking of an email for the IAU, and I'll post their reply. Who knows, maybe they will tell me that en dashes are acceptable, I have no idea. --Enric Naval (talk) 05:24, 6 January 2013 (UTC)

The IAU guy has no idea what an en dash is. When we use one where they use a hyphen, it does not introduce any ambiguity, and clarifies the relationship for normal English readers who are not aware of the IAU convention to use a hyphen. If we were to put a hyphen into 105P/Singer Brewster, there would be a bit of problem, however, for those readers familiar with the IAU conventions, who might interpret it as referring to two people. For normal English readers it would refer to a person Singer-Brewster, unless they didn't know that we use en dashes for two names, in which case it would again be ambiguous. Just like the hyphen in Hale-Bopp would make it ambiguous to some readers, and wrong to others, depending on what conventions they think are in use. The only way to keep Hale–Bopp unambiguous is to stick with the typographical convention we use elsewhere for pairs of names. There is no way to keep Comet Singer Brewster unambiguous, since most people are unaware of the IAU's odd conventions, and doing it normally would make it wrong for the astronomers. Yes, the IAU has made a mess; but that's not a reason to mess up Hale–Bopp. And if we decide by consensus to say "Comet Singer-Brewster", that won't be a disaster either; but for now, we don't do that, we just style the hyphen in Hale–Bopp as a "long hyphen" or en dash. Dicklyon (talk) 05:40, 6 January 2013 (UTC)

Can we dial this back? There is no question this section could be improved—there is always room for improvement—but there is no point in continuing until the current pattern of disruptions has been resolved. WP:Requests for comment/Apteva has been going since Nov. 30, with endorsement from 18 editors (in addition to the two editors who initiated it) and a motion to close has been endorsed by 28 editors. Yet, the editor who is the subject of this RFC/U is still on this MOS page, inserting the same remarks. Neotarf (talk) 09:14, 1 January 2013 (UTC)

No, we cannot "dial this back". Enough is enough. Of course the provision under "discussion" here could be improved! Every section could be improved; and I have just negotiated with Peter Coxhead that we should consider a fresh draft of one portion, for clarification. But this campaign from Enric Naval and Apteva is not about improvement (that is, moving closer to consensus). It is about overturning decisions for which consensus has not changed (at least, there is no evidence that it has changed). For reasons that have no force here on Misplaced Pages.

Apteva is the subject of that RFC/U mentioned above, where "18 editors" + 2 misrepresents the strong consensus regarding his conduct, by the way. (Look again at the opinions of almost all 36 who contributed there.) Apteva and Enric Naval persist no matter what evidence is presented, what arguments are produced, what broad consensus is shown, what pointy RM discussions they initiate and fail at, or what sprawling RFCs (initiated in several forums) bring disrepute on all editors associated with MOS, and then fail anyway. We saw all this in the past, when admin Sandstein tried to clobber everyone with blocks and bans at WP:AN because banned sock-puppeteer and anti-MOS activist PMAnderson got everyone tarred with the same brush, and we're seeing it again now. Learn from history, and let's say now: enough is enough.

Time for genuine and definite decisions, without the niceties, caveats, and qualifications that are appropriate in civil collegial dialogues, in the normal and productive business of this talkpage.

Time to close this thread. It will get us nowhere.

Noetica 11:09, 1 January 2013 (UTC)

I concur. Also, for the record, the disruptive, will-not-drop-it-until-they-die editors on this topic are a triumvirate, not a duo: Apteva, Enric Naval, and Wikid77. On at least some points they also have support from Blueboar, which kind of surprises me, and LittleBen, which does not, since he has been WP:AN/I'd for similar patterns of disruption before, blocked for it, and eventually topic-banned for it, on diacritics. A grand total of five editors whose heads asplode when they encounter dashes is certainly not enough to produce some kind of sea change in consensus. I'm beginning to see that these things tend to run in threes; the main "warrior" on such a topic will seek out two sidekicks, as just enough voices to convince some onlookers that there may be some real issue, instead of just a crank making noise. LittleBen did this, too, recruiting the aid of two other editors in his failed campaign against diacritics in article titles and text. KimvdLinde was also aided principally by two like-minded "warriors" in her WP:IDIDNTHEARTHAT-based, unsuccessful campaign to change MOS to actively endorse capitalization of bird common names, in which AN/I found that she had canvassed to disrupt a poll on the matte. Like LittleBen and Apteva, KimvdLinde also forum-shopped her pet issue all over the place, even highjacking WP:DRN for that purpose. And so on. Other random people may chime in favoring the (inaccurately described) non-majority side of any given style "war" (as KimvdLinde termed it), but it seems to require three dedicated partisans to be genuinely disruptive about it on a large scale. I wouldn't be surprised if some of PMAnderson's quixotic quests show a similar triadic pattern. — SMcCandlish  Talk⇒ ɖכþ Contrib. 23:35, 1 January 2013 (UTC)

Why the exception?

It's well established that the first and last words of names should be capitalised - be it those of books, films, songs, plays, paintings, whatever. But - and apologies of this is the wrong place to ask this - why are band names considered the odd ones out? It seems that a lowercase "the" is preferred, even if it's indisputably part of the band name, and I've never read a good reason why this should be. Even if it's historical, there must have been some sort of consensus to keep it up here on Misplaced Pages. This is a genuine question. It just seems rather arbitrary an exception to have become the norm. 86.4.242.105 (talk) 19:39, 23 December 2012 (UTC)

It's not just band names. The New York Times refers to itself with an italic capital 'T' in the "The", and the same capital 'T' is in the company's trademark, but the Chicago Manual of Style says to write it in running prose as "the New York Times", the initial word written without italics and without caps. Similarly, the Beatles are given the same style guideline. Binksternet (talk) 20:03, 23 December 2012 (UTC)

Well, that's fair enough - though it seems that The Times (of London) and The Daily Telegraph (for instance) don't adhere to that same style. It could also be argued that the "The" is being dropped from the name in your example all together, so any article (definite or indefinite) that's subsequently added belongs to the prose rather than the title (if you see what I mean). But the question remains: why these exceptions? It seems arbitrary, and is something I've never heard properly explained. 86.4.242.105 (talk) 23:43, 23 December 2012 (UTC)

It is also customary to lowercase the with political entities (the Phillipines, the United Kingdom, the European Union) with conventional exceptions (The Hague, The Gambia). --Boson (talk) 00:03, 24 December 2012 (UTC)

True, but we're no nearer to answering the question of why bands follow different capitalisation rules from songs, films, books, plays, paintings, poems... Doesn't it seem arbitrary to anybody else? When the Misplaced Pages MOS was drawn up, there must have been some reason for this - or was it simply because other style guides take this route (in which case it's a chicken/egg situation)? Does it perhaps go back to the days when "the" was rarely the first word in the name of the act, as in Buddy Holly and the Crickets or Cliff Richard and the Shadows (in which case it's an anachronism)? Anyone? 86.4.242.105 (talk) 01:02, 24 December 2012 (UTC)

I don't see why you expect band names to follow the rules for titles of works, rather than names of other organizations. --Boson (talk) 01:50, 24 December 2012 (UTC)

I'm not really expecting anything - I'm just trying to find out why the rules of capitalisation have these exceptions (and by extension, whether they ought to or not). As far as I'm concerned, a name is a name, and first and last words should be capitalised. If the first word is the definite (or indefinite) article and indisputably part of that name, I can see no good reason for it to be in lower case - can anyone provide me with one? Many thanks in advance. 86.4.242.105 (talk) 19:13, 24 December 2012 (UTC)

Your "a name is a name" assumption is the source of the confusion. Names of organizations, including bands, are handled differently from titles of published works. The Lord of the Rings is always The Lord of the Rings, even in mid-sentence or when preceded by a possessive ("J. R. R. Tolkien's The Lord of the Rings"), but not so with orgs, incl. bands ("Best and Sutcliffe's Beatles had a more bluesy, less poppy sound than the later 'Fab Four' we're more familiar with"). — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 06:24, 28 December 2012 (UTC)

Well, I'd make the case that you could describe a Tolkienesque piece of hackwork as "a Lord of the Rings rip-off" - no definite article, even though it's indisputably part of the name. Of course, it would be better to refer to it as "a rip-off of The Lord of the Rings", but never "a The Lord of the Rings rip-off". By the same token, the sentence you quoted would more properly start with something like "The Best and Sutcliffe incarnation of (t/T)he Beatles...", but never "Best and Sutcliffe's (t/T)he Beatles..." Very similar. So should there be a difference if the definite article is indisputably part of the name of an organisation or band? Or does it depend on the band in question? Try your example (with suitable alterations so that it makes sense, of course) with (t/T)he Who or (t/T)he Knack - do band names which aren't plurals require different rules?

The way to avoid the problem with the Tolkien example, where some might feel that "a The Lord of the Rings rip-off" seem awkward, would be to reword: "a rip-off of The Lord of the Rings", just as you did with that Beatles example, though it's less important to do something like that with that example, because "The Beatles" isn't the title of a published work, and it's normal to drop the article in mid-sentence (as I did when I wrote "that Beatles example"). I would say generally, no, there is not a special difference if the article is part of the official band name (which is the case with The Beatles), but as with everything in every guideline, there are always exceptions. The The pretty much always has to be written as such, because it's just too confusing otherwise. You can't really get away with "the critical reception of the third The album". — SMcCandlish  Talk⇒ ɖכþ Contrib. 23:46, 1 January 2013 (UTC)

On a slight tangent, since you brought up books, are both of these correct? (Note the capitalisation of the definite article):

- The first book in the series is Harry Potter and the Philosopher's Stone.

- The first book in the Harry Potter series is The Philosopher's Stone. 86.4.242.105 (talk) 23:57, 29 December 2012 (UTC)

No; the second is a misstatement of fact. It is common to truncate titles like this after the first instance, but the way to do that would be Philosopher's Stone, I would say, because it's not a subtitle, but part of a longer unitary title: Harry's age in Philosopher's Stone was..." Contrast Star Trek: The Next Generation, which is often shortened to The Next Generation or TNG; it's a self-complete subtitle. It's such fine hair-splitting that an editwar would be incredibly WP:LAME. However, you still wouldn't write "the first book in the Harry Potter series is Philosopher's Stone", because that's still a misstatement of fact, not being the actual title. — SMcCandlish  Talk⇒ ɖכþ Contrib. 23:39, 1 January 2013 (UTC)

Space between consecutive headings

Under "Section Headings", the MOS says: "...Include one blank line above the heading...." This is a good idea, as it makes the headings easier to find on the edit screen. However, I think there should be an exception where there are two headings in a row, as above. There is no difficulty seeing that there is a level 3 heading immediately after the level 2 heading. Separating them by a blank line looks the same as no blank line in the article itself, but is less convenient to work with on the edit screen, because it fills up the edit screen with unneeded empty spaces. Can we add this exception, please, to make it at least optional? Thanks! -- Ssilvers (talk) 00:22, 24 December 2012 (UTC)

• i agree with Ssilvers here; such a move makes total sense. Jack1956 (talk) 06:01, 24 December 2012 (UTC)

I'd rather go the other way, and recommend also a blank line AFTER each heading. Headings are often hard to spot when scrolling through long articles, and this makes it a lot easier. And it's simpler than adding an exception. Dicklyon (talk) 06:06, 24 December 2012 (UTC)

Yes, we'd still need to keep the one before the heading, too. I also think we want both (and this appears to be the norm, anyway):


 
==Heading==
 
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.While the following is not optimal, it's not exactly unbearable (and is very common):

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.


 
==Heading==
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

What we really, really do not want to see is this:

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.


==Heading==
 
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

or this:

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.


==Heading==
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

NB: It's also common for people to use the space between the heading and the text for hatnote templates; I do this myself, and don't see it as problematic.
— SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 22:54, 24 December 2012 (UTC)

Clarifying one issue concerning the use of hyphens

This is emphatically not an attempt to change the current advice re hyphens and en-dashes, and I hope no-one will hijack the discussion to this end.

The MOS currently has a short section containing the following text (I've removed the parts which aren't relevant to the point I want to make):

A hyphen is used by default in compounded proper names of single entities.

• Wilkes-Barre, a single city named after two people ...
• John Lennard-Jones, an individual named after two families
• McGraw-Hill, a publishing house named after two founders

I see what is being attempted here, but it doesn't really work. Theorems and comets are named after the people who discovered them, and follow the logic of the approach currently adopted in the MOS of using an en-dash, although they are clearly "compounded proper names of single entities". It may be that the cases where hyphens are used cannot be covered by a general rule. Double-barrelled surnames are one special case; long-established names of firms where the sense of distinct founders has been lost are another; and so on. The nature of natural languages is such that there are always oddities and exceptions. Either a more convincing explanation is needed or we should just say that there are special cases such as those below. What is clear is that the "rule" as given here isn't useful to editors seeking guidance. Peter coxhead (talk) 01:55, 25 December 2012 (UTC)

A fair question, Peter. When WP:ENDASH was ironed out last year, the consensual draft accepted by ArbCom had this wording:

By default, follow the dominant convention that a hyphen is used in compounded place names, not an en dash.

• Guinea-Bissau; Bissau is the capital, and this distinguishes the country from neighboring Guinea
• Austria-Hungary; the two are judged to be merged as one political and cultural entity

A few place names are exceptional, with components that refer to independent parts of a larger political or cultural whole.

• Poland-Lithuania; an en dash is used: Poland–Lithuania (see Polish–Lithuanian Commonwealth)

This all came after provisions that included examples of proper names with en dash: "the Roman–Syrian War"; "Comet Hale–Bopp or just Hale–Bopp". The provision was intended to give a default ruling for cases not otherwise covered, and in which the separateness of entities was not relevant.

Later A di M broadened the scope to include McGraw-Hill; and he therefore put "proper name" instead of "place name".

It is important to note what has remained constant: the provision "by default". Where any more focused provision applies, the default advice is overridden.

Does that help? I agree: that part of the guidelines is not optimally expressed; but it does seem necessary. 60 interested and active editors laboured for weeks to forestall time-wasting confusion, and to counter opportunistic attacks on MOS that capitalise on any point of omission or weakness. In any consensually developed set of guidelines, perfection is impossible. But if anyone knows of a more subtle and robust set of guidelines to deal with dashes (committee-designed or not, on the web or not), I want to see it. Please! ☺

Incidentally, there is another account to give of "John Lennard-Jones". I think Kwami added that example, and that explanation. Anyway, both abstracted explanations converge on the same almost universal ruling for compounded surnames.

Noetica 02:31, 25 December 2012 (UTC)

I think it's confusing, too. I was thinking about this the other day, but I gave up. What exactly is the difference between Wilkes-Barre and Hale–Bopp? Aren't they both compound names of a single entity that is named after two people? I suspect there is some difference that I'm overlooking, but maybe it could be made a little bit more clear to make it easier to figure out which mark to use when. AgnosticAphid talk 05:15, 25 December 2012 (UTC)

The town of Wilkes-Barre is not thought of as commemorating two people. Comets, however, are normally named after their discoverers, who sometimes have hyphenated names. There isn't always a clear line: punctuation is always going to be inadequate to convey all aspects of language. You see something of the distinction in Austria~Hungary, which is sometimes written with a dash as a dual monarchy, and sometimes with a hyphen as a unitary state. — kwami (talk) 07:24, 25 December 2012 (UTC)

I agree with Kwami. In addition, when you're not sure, sources can often be illuminating. You won't find McGraw-Hill or Hewlett-Packard or Wilkes-Barre with an en dash in reliable sources, I bet; certainly less than 1 in 1000. But Hale–Bopp with en dash is at least 20%, which is nearly as high as you'll find en-dash-based styles in books and scholarly papers. Any object commemorating two people will typical be found with en dash in at least a few percent of sources, indicating that it is the type of thing that our style would use an en dash for. Stadiums, airports, bridges, buildings, comets, theorems, diseases, algorithms, laws, etc. Looks for articles like List of eponymous X for lots of examples. The styling is mostly fairly consistent and uncontroversial in WP. The airport situation was a bit of a mess because lots of airport names were formed with city names attached to airport names with spaced hyphens, which DashBot changed to spaced en dashes, which were wrong as often as not. I've tried to work through those and figure out the various names and what they should really be, based on information in sources. It was made more difficult by a certain anti-en-dash attitude of one editor. Dicklyon (talk) 07:43, 25 December 2012 (UTC)

I like those responses well enough. I will contribute more on this tomorrow (Australian time), when I will be able to see better what more is called for. Noetica 10:55, 25 December 2012 (UTC)

Agree with Kwami. Tony (talk) 13:00, 25 December 2012 (UTC)

Although I see where Kwami's logic is coming from, it seems a little subjective really. When does one thing pass from being named after its separate inspirations to gaining a status of its own? I would also, despite the encouragement to do otherwise, take this opportunity to again wonder why we don't simply revert to doing to what most publishers – print and online – do, what most keyboards make it easy to do and what we used to do here on WP for a long while AFAICT, and simply use hyphens for all joins of whatever sort, from prefixes and suffixes to compound names of all varieties and, even, dare I say it, date ranges. It won't kill anyone, it won't lessen clarity of content and will save hours of debate and hours of gnoming. And no, again, it is no less "correct" than the alternative of insisting on making a distinction and agonising over when and where exactly we need to do that. N-HH talk/edits 17:53, 25 December 2012 (UTC)

I think the reason is that most editors agree that it will lessen the clarity to give up on the distinctions of meaning that en dashes convey relative to hyphens. That's why they're used, when they are. The fact that there are grey areas where the best choice is not obvious doesn't make it any more of problem than choosing capitalization, or disambiguation, or other things that editors usually agree on but sometimes disagree on. These things only become annoying problems when someone refuses to acknowledge consensus. Dicklyon (talk) 21:04, 25 December 2012 (UTC)

Rather like hyphenation itself. — kwami (talk) 22:10, 25 December 2012 (UTC)

The choice of a hyphen, space (open), or closed is somewhat determined by Am/Brit - British English prefers "end point", American English prefers "endpoint". Consulting a dictionary reveals that double-breasted and good-looking are hyphenated. So basically, look it up in the dictionary, and if it not there, use what reliable sources use. Not really something that even needs to be in the MOS. Apteva (talk) 22:43, 25 December 2012 (UTC)

Consulting a dictionary will resolve few cases. Dictionaries list words, not phrases. As for RS's, that's what the MOS guidelines we based our MOS on are. — kwami (talk) 22:56, 25 December 2012 (UTC)

I asked people not to hijack this section. Please don't. Here I am asking those who understand the "60 editor consensus" to clarify a small part of the explanation of that policy. We can continue discussing elsewhere whether that policy is the right one. Peter coxhead (talk) 00:52, 26 December 2012 (UTC)

Fine, Peter. Do you think things have been dealt with adequately now? I am ready to discuss refinements to that catch-all provision. What remains uncertain (if anything), and how might it be fixed?

Noetica 22:14, 27 December 2012 (UTC)

Despite having had a strong opinion about this before, I'm less certain now that for comets it shouldn't be a hyphen (except in cases where one of two or more parties a comet is named after has a "double-barreled" surname). The logic seems to be difficult to distinguish from that of "Wilkes-Barr" and "McGraw-Hill" other than the (weirdly archaic, reversed) adjectival form of the "Comet Hale-Bopp" (would we write "Wilkes–Barr City" with a dash if the place used this longer name?). I don't buy that no one thinks of Wilkes-Barr as commemorating two people; of course they do, and it was named that way specifically to do so! I do see a difference in that comets are named for their discoverers, but how would we codify such a distinction? But it's also at least reasonably likely that direct descendants of Hill and McGraw are still on the board of that company, and obviously would think of it as named after these founders (directly analogous to discoverers). Airports named after two cities, however, are directly comparable to wars named after two countries. It's "Seattle–Tacoma Airport", not "Seattle-Tacoma Airport". The difference between this and Wilkes-Barr or potentially Hale-Bopp is that in these latter cases they're honorary, abstract references, while in the case of wars and airports, they are references to palpably involved entities. Mexico and the United States of America actually fought the Mexican–American war; Sea–Tac airport actually does serve the communities of Tacoma and Seattle. By contrast, Bopp and Hale are never going to set foot on that comet; Barr and Wilkes did not live in that city, just in the area where the city was eventually founded after they were gone. Is there a simple way to distinguish between the "Mexican–American War" and "Wilkes-Barr" cases? PS: I'm also a little skeptical about this reasoning: "Austria-Hungary; the two are judged to be merged as one political and cultural entity", since they're both clearly "components that refer to independent parts of a larger political or cultural whole" as in Poland–Lithuania. At very least I'm tempted to use a dash in "Austro–Hungarian Empire". — SMcCandlish  Talk⇒ ɖכþ Contrib. 04:36, 31 December 2012 (UTC)

“Austro-Hungarian” is a very different animal from “Austria-Hungary”; because “Austro-” is a combining form that can’t stand alone, I would never use anything but a hyphen. Likewise for “Franco-Prussian War”, “Sino-Syrian relations”, &c.—Odysseus1479 (talk) 06:07, 31 December 2012 (UTC)

Right! I momentarily "spaced" that. — SMcCandlish  Talk⇒ ɖכþ Contrib. 23:59, 1 January 2013 (UTC)

SMcCandlish, I respond to you with details that newcomers can follow also:

1. I agree with Odysseus. Guides and dictionaries are almost unanimous in realising ~ in forms like Austro~ with a hyphen (or with null, to make a closed-up word). I recall seeing one exception; and in about 2004 I briefly supported en dash myself, before I checked the sources and analysed the reasoning.
2. Again in the cases of comets, we look to the sources (for MOS, that means specialised and general guides and dictionaries in particular) and to best practice in publishing; and we analyse the reasoning. The sources differ; so the burden is shifted to our analysis. We compare what various sources suggest, for various contexts of use, and we evaluate how the alternative proposals fit with choices that have already been settled here on Misplaced Pages.
3. Comets are not exactly aligned with surnames or with geographical placenames (including names for streets, lakes, mountains, and the like), though there are resemblances. Placenames and surnames are common linguistic currency; we all use them everyday. By widespread convention in English publication, almost all placenames do without the apostrophe. By almost universal agreement, surnames are formed only with letters, apostrophes, and ordinary hyphens. There is no such universal agreement for comets, companies, airports, political borders, structures like bridges, historical events like wars, and other items beyond surnames and plain geographical placenames.
4. Surnames and plain geographical placenames are coordinates on our shared map, and we demand consistency in their styling so that society can function. So that we can find each other, even. Subject to those forces and that pressure, essential consistency of styling has been achieved. Not so with comets, wars, airports, and all those other miscellaneous features of the world.
5. Moving to particulars, Wilkes-Barre is an ordinary, everyday, gazetted placename; so regardless of its etymological origins, it has an ordinary hyphen. No dispute, anywhere. Similarly, Klimpschs Lane (note the nine-letter word with just one vowel, discovered in the wild in New South Wales) has no apostrophe. No dispute. Contrast Comet Hale–Bopp (disputed in sources) and Barnard's Star (not disputed?).
6. Where guides, dictionaries, and other sources disagree, we weigh their relative importance and their relative competence. We assess any arguments they present, and we see how the alternatives fit with Misplaced Pages's established style guidelines. For en dashes contrasting with ordinary hyphens, this was done with great elaboration in 2011. Consensus can change. But not through chaotic or capricious activism; not through partisan campaigning that refuses to appreciate others' contributions or that disregards new evidence no matter how powerful it may be.
7. I defend the current guidelines for en dashes, though I think the hyphen guidelines need some refinement (as many of us agreed, in 2011). I track this issue carefully, and I have seen no compelling argument for substantial change. One consideration, though it must be balanced against others, is stability. We are talking about guidelines for 6,930,122 articles, in the world's most consulted and most comprehensive encyclopedia.

I hope that answers some of your concerns. I would prefer to leave the topic alone for a while now, because the community grows intolerant of us all on account of disruption from a very small minority – currently under consideration at an RFC/U. Unfair? Sure! That's the nature of communities. Those who maintain style guidelines to promote excellence in the articles have a thankless task. It is a specialised, demanding, applied intellectual exercise; but unlike most others, this field is one in which everyone feels like an expert. We have to respect that, of course. In a certain way, there's truth in it. Myself, I always want as much community participation as possible in the development of Misplaced Pages's manual of style. That's what will keep it the best of its kind on the web – and among the best anywhere, for punctuation at least.

Noetica 00:00, 1 January 2013 (UTC)

1. Me too; I was just having a momentary brain-fart.
2. I agree this is the process, and not just for comets, but generally. The WP:SSF essay I'm the principal author of hinges on it, in fact.
3. Agreed, though I have raised before a point that seems really obvious to me: Comets, like "seas" (craters) on the moon, the moon itself, and other astronomical places are in fact places. I dislike inconsistently treating a place simply because it's on a different chunk of rock in space than where my bed is.
4. Okay. My take is that part of MOS's purpose is to impose a (sometimes rather arbitrary) similar consistency on these other features of reality, to make it easier on our editors and readers.
5. It is certainly not undisputed that placenames have no apostrophe. Most British/Commonwealth ones do not (because they are, or in the British diaspora areas derive from, placenames that predate standardized spelling and punctuation in English), but apostrophes are actually fairly common in North American placenames, and even a British example with one (done in archaic KJV style) was given by someone else above. Another Commonwealth example is Van Diemen's Land, now Tasmania, Australia. There are others. I think we can say that it is undisputed on Misplaced Pages that we do not change what the official or conventional "apostrophization" of a placename just to be consistent with how MOS would otherwise treat apostraphes. I have not (and likely will not, because most of my books are still in storage, post-move) done enough research to be certain that the claim that a placename like Wilkes-Barr is never done with a dash, but concede that if it is, it's probably rare. I've never in my life see "Barnards Star" and would never expect to. If a place was named after me, in awkward possessive form, I would expect it to be "McCandlish's Point" or whatever, not "McCandlishs", since it would not go back to the Elizabethan or earlier periods of English.
6. Agreed entirely, but this is not really addressing my question about how we distinguish a comet (or theorem or whatever) in which MOS wants us to use a dash to separate the names of parties for whom the topic was named, from cases where MOS does not want us to do that, e.g. Wilkes-Barr. "It's a placename" does not strike me as a strong argument, for more than one reason (the most obvious being that there's nothing magically special about placenames). I'm intelligent and am not going to have a psychotic break over intense confusion on the matter if we simply declare that placenames, of a single place, are conventional exceptions, but we need to just declare them as such, and not try to make really tortured pseudo-logical arguments to "explain" the exception.
7. Agreed as well, except on stability; I do what MOS says even when I disagree with it, unless it raises a problem that triggers WP:IAR in a particular case (as it sometimes does); if it's something that really bugs me, I raise the issue here and try to shift things a bit. I don't agree that stability is a compelling argument for much of anything on WP. If it were, many quite major changes, e.g. date unlinking, would never have happened. The WP community absorbs such changes with remarkable facility, rapidly and with a comparative minimum of fuss. Partly for WP:DGAF reasons and partly because bots and AWB runs can fix so many of these things en masse. I think the stability argument is akin to the "server load" argument that the developers tell us is almost always not one to bother making.

And I agree with your closing statements. This issue does need to be dropped for a while. There is clearly no consensus generated by the tendentious campaigning of Apteva and friends to change this section. But I'm still not sure there's a clear rationale to distinguish between "Wilkes-Barr" with a hyphen and "comet Hale–Bopp" with a dash (or "Comet Hale–Bopp" as I would prefer to write it, with a capital C, for the same reason I'd write "Mount Rushmore" not "mount Rushmore". — SMcCandlish  Talk⇒ ɖכþ Contrib. 00:43, 2 January 2013 (UTC)

Returning to Noetica's question to me (do I think things have been dealt with adequately now), the answer is that I'm clearer but perhaps not quite there yet. Is the following accurate for words to be joined by either a hyphen or an en-dash?

1 If all (or virtually all?) sources use a hyphen, as with Wilkes-Barre or McGraw-Hill or double-barrelled surnames, then we accept this, regardless of the etymological origin.

2 Otherwise we apply the analysis in the MOS.

2.1 If one of the specific cases in the MOS applies then we use a hyphen or an en-dash as per that case.

2.2 Otherwise the default of a hyphen applies.

Peter coxhead (talk) 02:15, 1 January 2013 (UTC)

Peter! After all my labours to produce a manifesto for new year – stamped 00:00, 1 January 2013 (UTC), though I swear that was accidental – you ignore my impassioned rhetoric and return to the topic? Tsk!

Seriously now, I think your reading of the provision you earlier queried is about right. It was drafted in difficult circumstances: on one side editors wanted brevity, on another side editors wanted watertight and comprehensive guidelines; and some editors were calling for both, without suggesting how that could be achieved. All under the watchful eye of ArbCom. Interesting times; but the outcome has been peace. Yes, believe it or not: these are days of peace at WT:MOS. It's all relative.

We are now in a position to clarify the wording, without changing the substance. Since I am used to all this and know the topic intimately, I can draft a new version of the provision for editors to comment and vote on. Would you like me to do that?

Noetica 04:10, 1 January 2013 (UTC)

Yes, that would be an excellent idea. Peter coxhead (talk) 04:28, 1 January 2013 (UTC)

Right, I will then. Give me a day or two (during which we might get more input anyway), and I'll start a new section with a clear proposal for comments and voting. Noetica 04:46, 1 January 2013 (UTC)

Sounds good to me. I think Peter's outline is sufficient as a flowchart. However, I also think it is going to be extremely prone to "Aptevizing", with hell-bent editors claiming incessantly that something like "comet Hale–Bopp" must instead use a hyphen because virtually all the sources they know of do so (as noted above, A. this is mainly due to expediency, and B. IAU in particular has proposed typographical weirdness of even weirder proportions yet, like dropping the hyphen from double-barreled surnames, so they are essentially proof that WP:SSF is founded on very sound reasoning – specialist publications reliable for style-independent facts about their speciality cannot be relied upon for style advice.) — SMcCandlish  Talk⇒ ɖכþ Contrib. 00:43, 2 January 2013 (UTC)

Those who aren't prepared to abide by the current MOS aren't the target audience here. My concern is solely with those who want to go along with the MOS (whether they think it best practice or not), and who need clearer guidance. Peter coxhead (talk) 01:45, 2 January 2013 (UTC)

Peter, I wrote above: "Give me a day or two (during which we might get more input anyway), and I'll start a new section with a clear proposal for comments and voting." I'm going to have to delay that. There's simply too much going on; and problems of conduct affecting the development of MOS are not yet dealt with (at an RFC/U). Mind if we leave it till things settle down? The background work is all done in the discussion above, of course.
Noetica 02:18, 4 January 2013 (UTC)

Modifying quotes

It is not standard practice to make any modifications to a quote without noting that the quote has been modified. I would recommend removing the following

However, trivial spelling and typographic errors should simply be corrected without comment (for example, correct supercede to supersede and harasssment to harassment), unless the slip is textually important.

If a quote is modified, it is not a quote. Trivial misspellings etc., though, do not need to be marked with . --Apteva (talk) 22:27, 25 December 2012 (UTC)

Not according to the RS's we based that statement on. What you've described is a grammar-school simplification (one which I believed myself before getting into this). You need to base an argument on something more than just your own understanding. — kwami (talk) 22:57, 25 December 2012 (UTC)

I agree. Sometimes the mistake is on the source that reproduced the quote. For instance a politician makes a statement to the press and the a news agency reproduces it with a typo. In that case no "" is needed.

I also think that punctuation in quotes should follow the generic Manual of Style unless the quote is strongly related with its punctuation. Same holds for non-breaking spaces. -- Magioladitis (talk) 23:33, 25 December 2012 (UTC)

Some examples given in New Hart's Rules include changing endashes to emdashes and archaic f to s, or vv (two v's) to w, and close unclosed quotation marks, but in an encyclopedia it does not seem warranted to make any changes without noting them, at least in the reference. The question is is the intent to convey the meaning of the quote or to convey the quote. Those are two different things. Without the sentence anyone is free to treat any changes as an exception, with the sentence it seems as though people should be making typographic and spelling corrections. Frankly if the source misspells a word I would rather know that instead of it being corrected. For example, if someone spells supercede with a c I would rather see it left that way, but only because this is an encyclopedia. Apteva (talk) 04:27, 26 December 2012 (UTC)

JFTR what you call “archaic f” is actually a variant form of s, called the long s: look closely at an authentic example (as opposed to a jocular faux-archaism) and you’ll see it has no crossbar.—Odysseus1479 (talk) 06:34, 30 December 2012 (UTC)

One of various problems with that is that people will see the typo and correct it anyway; this is a wiki. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 01:47, 28 December 2012 (UTC)

Edit warring over passive voice

Could someone review this edit? I've hit 3RR in an edit war there over an ungrammatical avoidance of the passive voice. (IMO the topic should be the subject, per the normal rules of English discourse.) — kwami (talk) 23:54, 25 December 2012 (UTC)

• Classic example of trying to sneak something in to MoS to retrospectively legitimise bad behaviour. I oppose any such additions; especially in this case, where the aim is to perpetuate a paragraph with six consecutive instances of the passive voice. --John (talk) 17:14, 27 December 2012 (UTC)

• Actually, we have often discussed discouraging the passive voice, and decided not to. Art LaPella (talk) 23:52, 27 December 2012 (UTC)

Since has deleted the link I placed on his talk page, I will place it here, for the benefit of anyone following the active/passive discussion. Linguist Geoffrey K. Pullum's passive tutorial. Also worth looking at is the WP link that Kwami added to the page, also deleted: English_passive_voice#Reasons_for_using_the_passive_voice. Neotarf (talk) 01:16, 28 December 2012 (UTC)

Passive voice is often actually useful in an encyclopedia, because active voice can very often lead to WP:NOR and WP:V problems (namely, asserting positive agency in the cause of something, without sufficient evidence of the alleged causality). — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 01:55, 28 December 2012 (UTC)

Passive voice can be useful in an encyclopedia if carefully used. In general, there is far too much passive voice on Misplaced Pages, and it results from too many writers who think it sounds more "educated" to use it. I often (as in the case in point) encounter articles which are essentially written in passive voice from start to finish. This looks stupid and works against clarity and ease of understanding. Any change to the MoS which encourages this sort of pretentious, unclear, constipated writing is to be deplored. --John (talk) 13:24, 28 December 2012 (UTC)

No one's made any such proposition. The one I made (new section) specifically talks about the V and NOR issues, nothing more. — SMcCandlish  Talk⇒ ɖכþ Contrib. 04:16, 31 December 2012 (UTC)

Similar prescriptionist disputes

Should we add a section for silly shibboleths such as final prepositions, split infinitives, which/that, etc? We occasionally have editors "fixing" hundreds of articles in an attempt to follow such fallacies, often creating awkward or even ungrammatical prose in the process. — kwami (talk) 00:45, 26 December 2012 (UTC)

Maybe something like,

Common grammatical disputes

Style guides sometimes advise against common grammatical constructions such as passive voice, split infinitives, restrictive which, and ending clauses in a preposition. However, such advice goes against centuries of literary practice, and even proponents seldom follow it. For Misplaced Pages, decisions on such points should be based on tone, style, and clarity, rather than on an absolute rule.

Those are the main examples I can think of; singular "they" might be added (per Shakespeare etc), but I'm not sure how relevant it would be for WP, so we might not want to mention it specifically. — kwami (talk) 01:44, 26 December 2012 (UTC)

The "even proponents seldom follow it" bit is an unsupportable assertion, and appears to be a mild ad hominem attack on critics o passive voice, split infinitives, etc. It's probably actually true, but that's beside the point. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 02:20, 28 December 2012 (UTC)

Um, yeah, totally supportable, those who object to the passive often cannot even identify it. Much has been written about this on Language Log. I'll see if I can find something more specific. Neotarf (talk) 02:29, 28 December 2012 (UTC)

Okay, here's "50 Years of Stupid Grammar Advice", Pullum's takedown of Strunk and White's Elements of Style. The premise: "What's wrong is that the grammatical advice proffered in Elements is so misplaced and inaccurate that counterexamples often show up in the authors' own prose on the very same page." Neotarf (talk) 02:40, 28 December 2012 (UTC)

Does not support your claim. That Strunk and White themselves were bad writers, 100-odd years ago, does not mean that current WP editors who care about this distinction cannot identify it or regularly violate or (or even that offline modern writers who care about the distinction do so either). This isn't a huge issue, it's just that your wording is effectively making an attack, for no reason, that it can't support anyway. The solution is not to bend over backward to trying find some tenuous support for the attack, it's to stop attacking. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 03:06, 28 December 2012 (UTC)

Actually, if you read it, Pullum regards E. B. White as quite a good writer. He did write Charlotte's Web, after all. But Pullum points out that 3 out of 4 of the "passive" examples in the book are not really passives. They are:

There were a great number of dead leaves lying on the ground" (no sign of any passive); "It was not long before she was very sorry that she had said what she had" (again, no sign of the passive); "The reason that he left college was that his health became impaired" (here became impaired is an example of the adjectival, not passive, use of the past participle). Source.

Here's more from Pullum about the general inability to distinguish passive, along with several dozen links to other pieces. Apparently it's an epidemic. But of course I agree that any WP advice for editors should be couched in positive terms that builds on knowledge they already have, while making the reasoning self-evident. Neotarf (talk) 03:49, 28 December 2012 (UTC)

Sounds good to me, as long as we can outlaw the singular they in article space. Happy holiday be had they with. Dicklyon (talk) 02:36, 26 December 2012 (UTC)

Won't mention it then. It's not common in academic writing even if it is in literary English. — kwami (talk) 03:00, 26 December 2012 (UTC)

Yes, please do add such a section; we've had problems for years with users trying to remove the passive voice whether or not it was appropriate. But I hope you do include the singular they. SlimVirgin 19:18, 27 December 2012 (UTC)

A lot of people support singular they, though. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 02:20, 28 December 2012 (UTC)

That's why I suggest it be included. SlimVirgin 02:23, 28 December 2012 (UTC)

Ah, I see what you mean; I mistook you for supporting someone's notion above to "forbid" it. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 02:33, 28 December 2012 (UTC)

I have reverted Kwami's addition of the following subsection. Apart from having an edit summary that is practically useless for documentation of changes to this core MOS page, it followed minimal discussion between just two editors:

Common grammatical disputes

{shortcut|MOS:PASSIVE|MOS:WHICH|MOS:SPLITINFINITIVE|MOS:PREPOSITIONS}

Style guides sometimes advise against common grammatical constructions such as passive voice, split infinitives, restrictive which, and ending clauses in a preposition. However, such advice goes against centuries of literary practice, and even proponents seldom follow it. For Misplaced Pages, decisions on such points should be based on tone, style, and clarity, rather than on an absolute rule.

Myself, I agree with the basic idea. But that's not the point. There is no rush, and we definitely do not want to encourage ill-documented changes to this core MOS page. Let any such substantive changes be prefigured here on the talkpage – preferably with a draft, and long enough for editors in all time zones to comment. (Meanwhile I have reworked the lead of the article Kwami mentioned above.)

Noetica 04:32, 26 December 2012 (UTC)

An excellent suggestion, Kwami(kagami). Editors shouldn't force compliance with "rules" fantasized by Strunk, White, and similar language ignoramuses. -- Hoary (talk) 15:00, 26 December 2012 (UTC)

Or in Latin, of course, lingua ignorami. :P EEng (talk) 16:19, 29 December 2012 (UTC)

This page routinely features strong passion over arcane minutia, so I couldn't decide if that was intended as an attack on Strunk and White, or sarcasm against Kwami. Art LaPella (talk) 20:56, 26 December 2012 (UTC)

(That's minutiae, Art. ☺!)

Be assured: Hoary is a knowledgeable linguistic type, and no doubt approves of Kwami's addition.

Noetica 22:07, 26 December 2012 (UTC)

I agree with the spirit of this proposal, but I think the best way to ensure that people don't spend time arguing over it is to not have a policy on it.Grandiose (me, talk, contribs) 21:09, 26 December 2012 (UTC)

It does not take a position on whether we should or should not use the passive voice, etc. When we do get grammar warriors (not terribly common, but sometimes quite prolific when they do appear), it would be nice to be able to quickly point out that they do not have consensus. Not that consensus is against them in any particular case, only that the MOS does not support blanket "correction" of such things. The MOS does not support them anyway, of course, but currently there's no one place to direct them to prove it. I think this will prevent more arguments than it will cause: When the grammar warrior has their style guide, and the MOS is silent, it's easy to argue that a published source should trump what doesn't exist. — kwami (talk) 21:24, 26 December 2012 (UTC)

I should have checked better, Kwami. Your edit was hasty, but I did not examine how well you did prefigure it here.

No objection from me, if people really want such an inclusion. I tend to agree with Grandiose, though: silence on this issue is eloquent. If we do want it, I'd like consistency mentioned as a desideratum. And I would like to see less polemic content. There is no justification here for railing against more nuanced advice that does not make the clumsy mistakes of Strunk, White, and their ilk. Sufficient that MOS does not give style advice of that sort, and that it is not a matter of grammar, as many have thought. For example, linguist supremo Geoff Pullum is a polemicist on a crusade against distinguishing relatives that and which; but he is plain wrong in claiming that all who favour the distinction do so on grammatical grounds. We don't need to buy into those wars. So I suggest this:

Perennial style disputes

{shortcut|MOS:PASSIVE|MOS:WHICH|MOS:SPLITINFINITIVE|MOS:PREPOSITIONS}

Some style guides have advised against common grammatical constructions such as passive voice, split infinitives, restrictive which, and ending clauses in a preposition. But advice on those points has no place in Misplaced Pages style guidelines. Style decisions should be based on tone, clarity, and consistency, not on ill-founded prejudice.

Noetica 22:07, 26 December 2012 (UTC)

I'd have two objections to that. First, as far as I know, no one advises against the passive voice in the same blanket way some people advise against split infinitives, restrictive "which"es, and stranded prepositions; everyone agrees the passive voice has its place. Second, some people consider that restrictive "which", in particular, is less clear than restrictive "that" and always inappropriate to an encyclopedic tone just as "ain't" is, though not as jarringly. The proposal offers no reason that restrictive "which" is allowed here but "ain't" isn't. I assume it's because restrictive "which" is common in edited formal English, but if the MOS is going to be explicit about allowing this construction and calling opposition to it "ill-founded prejudice", the MOS should be explicit about the reason. —JerryFriedman (Talk) 22:36, 26 December 2012 (UTC)

I have never seen anyone go on a crusade to convert "isn't" to "ain't". I have seen people removing passives just because they're passive. — kwami (talk) 22:45, 26 December 2012 (UTC)

I think you mean converting "ain't" to "isn't". :-) —JerryFriedman (Talk) 23:11, 26 December 2012 (UTC)

The style guides are probably unanimous in stating "ain't" shouldn't be used except colloquially. Not so with that/which. — kwami (talk) 01:59, 27 December 2012 (UTC)

So the criterion is unanimity? I didn't use that in my example a minute ago, but it could probably work. I'm just saying the MOS should say what the criterion is. —JerryFriedman (Talk) 14:39, 27 December 2012 (UTC)

I think the criterion should be things people have been crusading for when there's no consensus for the change. Eliminating passives even when appropriate is one of the major ones; there aren't too many others, I don't think. "Ain't" isn't an issue because hardly anyone uses it on WP, and if someone did, I doubt anyone would object to it being replaced. — kwami (talk) 02:57, 28 December 2012 (UTC)

I think the semi-obsolete "whom" is a better example. Art LaPella (talk) 05:11, 28 December 2012 (UTC)

(edit conflict) How about "grammatical style"? Also, I don't think the MOS should be overtly spelling out what should be in the MOS; that's more at home on the talk page.

I completely agree with the second sentence there (whoever wrote it – you didn't sign). It'd be really weird for MOS to say what should be in MOS. The "ill-founded prejudice" wording wouldn't be guideline material either. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 02:13, 28 December 2012 (UTC)

Perennial grammatical style disputes

{shortcut|MOS:PASSIVE|MOS:WHICH|MOS:SPLITINFINITIVE|MOS:PREPOSITIONS}

Some style guides advise against common grammatical constructions such as passive voice, split infinitives, restrictive which, and ending clauses in a preposition. However, this advice goes against centuries of literary practice. Such decisions should be based on tone, clarity, and consistency.

— kwami (talk) 22:43, 26 December 2012 (UTC)

It depends on what you mean by "centuries". Split infinitives were very rare 200 years ago, especially in literary prose.

Maybe the point to address is the "perenniality".

Some editors automatically change certain grammatical constructions such as passive verbs, split infinitives, restrictive uses of which, and clauses that end in prepositions. However, those constructions are all common in edited formal English. Changes to them, and to other constructions that meet that criterion, should be considered case by case according to tone, clarity, and consistency.

—JerryFriedman (Talk) 14:36, 27 December 2012 (UTC)

Active/passive and similar disputes (continued)

There's an ENGVAR factor here: restrictive which is not a issue in British English, whereas the others (passives, split infinitives, preposition stranding) are argued over in many variants of English. Peter coxhead (talk) 16:35, 27 December 2012 (UTC)

I would support Jerry's suggestion (though please include starting sentences with "But"). Is there an ENGVAR factor, Peter? For example, I was taught never to use restrictive "which," though it seems others were taught that it's okay. The point is that these are all preference issues, so people shouldn't go around changing them automatically. SlimVirgin 19:24, 27 December 2012 (UTC)

Sure, 'but' is fine IMO – do we have an article that discusses this point so we can link to it? I didn't include it because I wasn't expecting it to be an issue. — kwami (talk)

Has someone been accused of changing them "automatically"? How would that work, exactly? --John (talk) 19:33, 27 December 2012 (UTC)

I've seen people going around replacing 'which' with 'that' on multiple articles, with a stock edit summary suggesting they are engaged in a general hunt for restrictive 'which'. (IMO, this is often an improvement, but not always, and some of these weren't.) And in the edit-war alert at the top of this section, the editor justified it as 'active over passive' in the edit summary, and at talk with 'We prefer the active over the passive voice', 'So you guys know better than me, know better than respected style guides, and know better than Misplaced Pages's own quality control processes' in response to comments that the passive is appropriate in that case, and 'it consists of keeping the article in a shit state through ignorance of basic English,' all suggesting that he's guided by advice to avoid the passive even if that means distorting the text.

For Jerry's wording, do we really want to address the editors making the changes, rather than the style guides that they learned from? How about:

Perennial grammatical style disputes

{shortcut|MOS:PASSIVE|MOS:WHICH|MOS:SPLITINFINITIVE|MOS:PREPOSITIONS}

Some style guides advise against common grammatical constructions such as passive voice, split infinitives, restrictive which, beginning a sentence with 'but', and ending clauses in a preposition. However, these are all common in formal English publication. Changes to such constructions should be based on tone, clarity, and consistency.

— kwami (talk) 20:46, 27 December 2012 (UTC)

MOS doesn't always care what "some style guides" do; it is its own style guide. If it uses wording like this elsewhere, that should be removed. Re: "Changes to such constructions should be based on tone, clarity, and consistency." – that's just generally true of all edits that aren't simply correcting/adding facts, though. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 02:08, 28 December 2012 (UTC)

Suggestions for that latest draft:

• Drop style from the header. No longer needed.
• Drop the first use of common; the second is better placed to do all the work.
• A link to Conjunction (grammar) for the point about but (it's in the lead there).
• Replace in formal English publication with in high-quality publications.
• Fix the last sentence (as below).

The result:

Perennial grammatical disputes

{shortcut|MOS:PASSIVE|MOS:WHICH|MOS:SPLITINFINITIVE|MOS:PREPOSITIONS}

Some style guides advise against grammatical constructions such as passive voice, split infinitives, restrictive which, beginning a sentence with but, and ending clauses in a preposition. However, these are all common in high-quality publications. Attempts to improve the language of an article should be based on tone, clarity, and consistency.

It's a delicate matter. Preferences differ even among those who have joined this discussion. I am a strong advocate of distinguishing the relatives. It has been proposed as a stylistic principle since at least mid-19C (by such theorists as Alexander Bain). I would not want anyone to be able to cite MOS either for or against making the distinction, to improve an article; I am happy that the wording here is neutral and effective.

I am definitely against setting this up as an ENGVAR matter. Inaccurate at best, and unhelpfully divisive at worst.

Noetica 22:38, 27 December 2012 (UTC)

I have no desire to be divisive, in this or other matters of style. Let me give an example. I greatly expanded Cactus, which by consensus is written in American English. I can happily use American spelling, but grammatically it's almost impossible for me not to write in my usual rather academic British English style. A number of people have since copy-edited my text; a significant proportion of these edits related to my use of that and which. I was grateful for these copy-edits, since they resulted in a style which is certainly less "British", whether or not it is authentically "American". However, if someone copy-edited in the same way an article which was agreed to be in British English, I would object. Am I wrong in making this distinction?

Using the same article as an example, several editors changed passives to actives, sometimes improving the text, but more often pointlessly in my view. So I strongly support the proposal to discourage purely opinionated copy-editing. Peter coxhead (talk) 00:35, 28 December 2012 (UTC)

Hi Peter, that/which isn't an ENGVAR issue that I'm aware of. SlimVirgin 01:34, 28 December 2012 (UTC)

Yeah, I can't see it that way either (and I learned to read and write in England, lived mostly in the US but also lived in Canada). Perhaps the extent to which the distinction is maintained in informal spoken and written communications varies geographically, but if so, I've never noticed. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 02:06, 28 December 2012 (UTC)

Well, English relative clauses#That or which says it is a dialectal matter, with reliable sources. They say that American English has no truck with restrictive which, but that British English accepts it, even in formal writing. Well, whaddayaknow? — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 02:33, 28 December 2012 (UTC)

This corresponds to my experience: I use that or which indifferently in restrictive relative clauses (tending perhaps to which in formal writing). So I'm happy for my uses of which in this context to be changed to that if the article should be in American English. What is slightly more problematic sometimes is the zero relative pronoun, which can make sentences hard to parse. Peter coxhead (talk) 22:05, 28 December 2012 (UTC)

Include the crap caused by FrankenStrunk (Passive voice, conjunctions, preposition endings). The others are not so settled upon. To boldly split infinitives can be done as naturally as writing in the passive. Or starting a sentence with a conjunction, for that matter. The "no split infinitives" rule can be elegantly broken by those who carefully consider the relationships between words. But 99% of the time it makes for clunky prose, and I worry that future copy-editing will be hurt by this addition. Same goes for that/which. PhnomPencil (✉) 00:32, 28 December 2012 (UTC)

OPPOSE adding anything about active/passive to MOS, more or less per WP:BEANS. There are plenty of editors who instinctively write clear prose without being at all aware of the existence of passive voice or other matters of grammar, and this would just be a confusing and useless tangent for them. Where would it stop? Instructions about there and their? Admonishments about i and ur? Many of us never heard of Strunk and White at all before coming into contact with the linguists who find it so irritating. MOS should be clear and positive, and a true help to editors, not merely a negative reaction in response to some linguists' peeve. Neotarf (talk) 01:33, 28 December 2012 (UTC)

• I also oppose such an addition, for essentially the same reasons. And these are not issues which arise often enough or divisively enough to warrant MOS's attention anyway, as well as the fact that ENGVAR is bound up in some of them. In general, cleanup of this sort is not harmful. Where it is (e.g. tortured constructions like the classic "Ending a sentence with a preposition is something up with which I will not put.", or use of active voice that implies causal agency without a reliable source for it), just revert and discuss on the article's talk page if necessary. WP:BRD exists for a reason. Ultimately virtually all copyediting is "purely opinionated", because God did not come down from heaven to hand us style commandments. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 01:55, 28 December 2012 (UTC) I've changed my mind on this (not on the issue I raise elsewhere that a whole section of stuff like active/passive, which/that, etc. will be a magnet for MOS disruption), and formally proposed adding passive voice back in, in a new section below. — SMcCandlish  Talk⇒ ɖכþ Contrib. 04:10, 31 December 2012 (UTC)

• It would be helpful to have a section here to point to. We used to have one advising that the passive was fine, but it was removed. Without it, we have to argue the issue every time it comes up. SlimVirgin 02:14, 28 December 2012 (UTC)

The problem with a section like this is that everyone who disagrees with anything in MOS is going to try to shoehorn their pet bugbear into this section and remove MOS's long-consistent advice about it. Don't like logical quotation? Put it in this section as something we no longer have a rule about. Don't like dashes? Put them in that section. Don't like spacing between initials or between measure and unit? Put them in that section. Ad nauseam. MOS itself could be whittled down to nothing but a skeleton. There's nothing particularly different about, say, split infinitives and our captalization-of-titles rules – they're all just arbitrary rules we've selected out of various possibilities available, and asked people to follow them for consistency's sake. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 02:26, 28 December 2012 (UTC)

The difference is that we have established conventions for those other things, so any such additions would be reverted as against consensus. The point here is to clarify that we intentionally don't have conventions for everything. We should probably limit the list to things that people have actively pushed. My motivation was the same as SlimVirgin's: I don't want to have to relitigate every time someone wants to delete all passives. So much easier to respond with "See MOS:PASSIVE". — kwami (talk) 02:39, 28 December 2012 (UTC)

Yes, what happened on the thread above was unfortunate. Harsh words were exchanged, and a user has backed off from the thread. But from what I can see, this user is far from unintelligent, having studied some languages, and is actively involved in copyediting. This is exactly the kind of editor these pages should be reaching out to. Active/passive is an advanced topic and many courses that cover grammar give only a cursory introduction to it. So even the average person who has taken university level composition courses has probably only done a few exercises in changing passive to active, without really going into the reasons. (A serious university-level composition handbook--Little Brown?--should have it, though.) Can you believe, I once heard someone declare that passive voice was to be preferred over active, as a higher and more educated sounding register of English -- not a native speaker, to be sure, but someone who had supervisory responsibility over nearly 80 English instructors. This is the sort of mentality that the exercises in changing passive to active is meant to counter. But it fails as instruction, as it starts from the standpoint of assuming something is broken, and ends up creating its own set of problems. Neotarf (talk) 03:07, 28 December 2012 (UTC)

Kwami, have you not noticed that everyone with a problem with something MOS says claims there is no real consensus for it, and many of them campaign incessantly to get what they want? A section like this will make it trivially easy for someone to post some rant at WP:VP/P about "OWNership of MOS" and rile up a bunch of yahoos who agree with whatever ungrammatical or questionably grammatical thing the activist wants to do, and overwhelm MOS with an "invasion" of people who want to change it (cf. earlier this year with capitalizing bird species common names, as just one of many examples). Such a section will create a "loop black hole" into which any style point can be sucked as long as someone can make enough noise about it to get some non-trivial percentage of editors to wonder about consensus on the issue. It would be safer for MOS's integrity to individually address each of these issues (passive voice, trailing prepositions, etc.) in their own sections, widely separated. We basically can't "limit the list to things that people have actively pushed" because there is virtually no point in MOS that someone hasn't done this with. The solution is to not have any such list. If you really, really, really need a MOS:PASSIVE, then make it, but separately from MOS:PREPOSITION, etc. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 03:18, 28 December 2012 (UTC)

I'd have no problem separating them. My main concern is with passives, as 'fixing' them can really screw up a text. (So can 'fixing' prepositions, but I haven't noticed that being a problem.) — kwami (talk) 08:01, 28 December 2012 (UTC)

We used to have a sentence about the passive being okay, but it was removed. See here. SlimVirgin 17:09, 28 December 2012 (UTC)

I've proposed re-adding it (and possibly clarifying it) in a new section below. — SMcCandlish  Talk⇒ ɖכþ Contrib. 04:08, 31 December 2012 (UTC)

There's also this editing guide. Does anyone ever look at these? Maybe a "things not to fix" is also in order. Neotarf (talk) 04:07, 28 December 2012 (UTC)

Yes, maybe that's a better place for it.

But the word don't "must" be "fixed"? Really? — kwami (talk) 08:01, 28 December 2012 (UTC)

That contradicts WP:CONTRACTIONS. Art LaPella (talk) 17:44, 28 December 2012 (UTC) Resolved since then. Art LaPella (talk) 22:23, 28 December 2012 (UTC)

Added a "things not to be fixed" section to that guide. — kwami (talk) 02:53, 29 December 2012 (UTC)

Also contradicts Contraction (grammar) (which is not exactly sourced). I don't agree. I also see it's been taken out before (by SlimVirgin)(a Canadian?) and keeps getting put back in. Is this some EngVar thing? The last I heard, contractions are standard; the main reason for not using a contraction where one is available is for emphasis or to display anger. Neotarf (talk) 13:43, 29 December 2012 (UTC)

Yes, that's my impression as well. However, I have seen style guides which say that contractions are unprofessional, much as they advise against these other things. Certainly we shouldn't use "gonna" or "it'll" in an encyclopedia, but there's nothing wrong with "isn't". — kwami (talk) 20:01, 29 December 2012 (UTC)

If we have any pretence of maintaining a professional encyclopaedic tone, we need a degree of formality, and such contractions are incompatible with that goal. Outside of direct quotations, I find it difficult to imagine what the MoS means by "occasionally contractions provide the best solution anyway" if formal tone remains the way to write better articles. Kevin McE (talk) 20:23, 29 December 2012 (UTC)

Completely agreed, and "isn't" isn't some mystical exception; it's precisely as informal as "it'll". I expand these contractions, every single time I encounter them in non-quoted article prose, without fail, and (as far as I've noticed) in over 7 years I've never been reverted on that even once. I think about 95% of our editors understand that contractions are not in the encyclopedic register or tone, and avoid them. Those who do not, seem to understand why their contractions get expanded by other editors (whether or not it "educates" them to actually stop using contractions when they write articles here). — SMcCandlish  Talk⇒ ɖכþ Contrib. 04:06, 31 December 2012 (UTC)

WP is meant to be written in Plain English, in order to avoid ambiguity, jargon, and vague or unnecessarily complex wording. I have heard people intentionally speak without contractions to non-native speakers, dumbing down the language in order to be understood. For example, what is the difference in pronunciation between "you are done" and "you aren't done"? In my idiolect at least, it is mostly a matter of emphasis, and very hard for a non-native speaker to pick up on. Better to say "you are not done" to a non-native speaker, and be understood, even if it sounds like pidgin English. But in written English there is less opportunity for contractions to cause confusion. Neotarf (talk) 04:56, 31 December 2012 (UTC)

No one involved has made such an argument that contractions are confusing; that's not why we avoid them. They're simply not part of the formal register. Even newspaper and serious magazine journalism avoid them, as does (usually) academic writing, to which encyclopedic writing is close kin. Even non-dialogue prose in fiction avoids contractions mostly. You have to get into personal editorials, which are intentionally only semi-formal, and what I call "dumbass journalism" like Maxim and People magazines, and hipster articles in city weeklies, which are all attempting to appeal to the lowest-common denominator and sound "cool" and "friendly", before you start seeing non-dialogue/non-quotation contractions in print. WP is nothing like that. — SMcCandlish  Talk⇒ ɖכþ Contrib. 05:26, 31 December 2012 (UTC)

I have never seen this documented, only the bit about emphasis, but I am more likely to see grammar stuff published in the U.S. or for the American market. Neotarf (talk) 05:44, 31 December 2012 (UTC)

I'm not sure what you mean by "documented". Publications are self-documenting – just pick up a mainstream daily newspaper and see how many contractions you can find that are not in quotations or in one-author editorials/reviews written in a less formal register. No one is likely to get a grant to do a linguistics journal research piece on the topic, since it's simply not interesting to much of anyone. — SMcCandlish  Talk⇒ ɖכþ Contrib. 01:16, 2 January 2013 (UTC)

The usual is to post some link to n-grams or some particular style manual, especially when there seems to be some difference in experience between several editors who speak different varieties of English. Anyone can make assertions here, and many do. Neotarf (talk) 02:13, 2 January 2013 (UTC)

As someone else pointed out here recently, n-grams are an overused tool that provide quantity data without any quality analysis. They're a hammer, and this is not a nail. (For one thing, there would be no way to distinguish in n-grams between different types or "qualities" of source material, but doing so would be required to test the hypothesis!) This is a bolt, and I've already handed you a ratchet wrench: Pick up a newspaper and read. Try some magazines of different sorts too, and some books. — SMcCandlish  Talk⇒ ɖכþ Contrib. 11:06, 2 January 2013 (UTC)

Consecutive punctuation marks

My question is prompted by this revision of Misplaced Pages:Misplaced Pages Signpost/2012-12-24/Technology report at 07:41, 26 December 2012. What guidelines or policies does Misplaced Pages make in regard to a full stop (period) followed by a comma in a sentence?

• The company operated in Washington, D.C., New York City, and Los Angeles.
• The company operated in Washington, D.C, New York City, and Los Angeles.

—Wavelength (talk) 20:57, 27 December 2012 (UTC)

We would never write *"Washington, D.C, New York", but we might write "Washington, DC, New York". (Either drop all full stops or none.) The edit in question looks like it might be analogous to the latter. — kwami (talk) 21:18, 27 December 2012 (UTC)

It's perfectly fine to drop the periods (stops) from "D.C." The US postal system has not used periods in state/territory abbreviations in two generations. Some (mostly older) people still use them out of habit, but MOS has no reason to care. It's "Washington, DC", and many even write it "Washington DC", especially in constructions that are otherwise using commas to separate placenames. If you don't drop the comma, the wording above would have to read "Washington, DC; New York City; and Los Angeles", with semicolons. Otherwise it implies Washington state as whole, the District of Columbia as a whole, New York City and Los Angeles (4, not 3, geographic entities)! — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 02:01, 28 December 2012 (UTC)

I think he's asking about replacing one stop with a comma, but keeping the other, which would be weird. — kwami (talk) 02:40, 28 December 2012 (UTC)

I understand that, and it would obviously be weird and nonstandard. I'm making points far beyond that. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 03:08, 28 December 2012 (UTC)

After consulting Misplaced Pages:Manual of Style/Abbreviations#Widely used abbreviations in Misplaced Pages (version of 10:34, 12 December 2012), I have composed a better example to illustrate the two consecutive punctuation marks (.,).

• The project was developed by a consortium of representatives from Apple Inc., Microsoft, and Google.
• The project was developed by a consortium of representatives from Apple Inc, Microsoft, and Google.

—Wavelength (talk) 03:52, 28 December 2012 (UTC)

The first is still correct, including even in the section you link to (which is not authoritative). I'm not sure where the idea came from that we can't have two consecutive punctuation marks; it's actually entirely routine. I would remove the serial comma, though (the one after Microsoft), since it isn't necessary. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 06:39, 28 December 2012 (UTC)

Despite the section heading "Consecutive punctuation marks", my question was and is about this particular sequence of these two punctuation marks—a full stop (period) followed by a comma—and not about two consecutive punctuation marks in general. (Serial commas are discussed at MOS:SERIAL.)

—Wavelength (talk) 17:35, 28 December 2012 (UTC)

• First of all, I support the serial comma by default, and for me the argument "it isn't necessary" is not at all compelling. Let's leave that aside.
• Second, a full point functioning as a mark of abbreviation may be immediately followed by any sentence punctuation, with one exception: a period (full stop), which is also realised by a full point. In such a case one full point serves both functions, by well-settled convention. Now, the edit that prompted Wavelength's post was by Tony, who removed the full point from "DaB." (a German Misplaced Pages username). Some remarks:

• The case is cross-linguistic, so there is potential for the interaction of differing punctuation protocols. But however things might work in the source language (German), I say that practice in the destination language (English) should dominate.
• By normal English practice, this sort of thing would be fine: "other Toolserver supporters, DaB., and ..."; "Though DaB. later shared his ongoing doubts ..." (excerpts of text before Tony's edit).
• I take abbreviation in usernames as subject to the same styling revision as in other contexts; so I support Tony's edit. I do the same with the username "A. di M.", which I render as "A di M". Just as the title "Mr." can be adjusted to the far more rational and typist-friendly "Mr", whatever the preferences of the gentleman in question, so can abbreviations of names – without regard for the style choices of their bearers. Yes, usernames are borderline; but they are often chosen and detailed without regard for the convenience of other users (Greek letters, mathematical symbols, and so on). Myself, I am not interested in meeting the expectations of users by strict compliance with such foibles.
• Often enough, keeping a full point that marks abbreviation causes more serious disruption for the reader than we see in the text that Tony edited. Consider: "We met DaB. A. di M., if he had been there, would have wanted to meet him also." It takes some analysis to sort that out, and intractable cases could be constructed. It is all much easier if full points are kept to serve as periods only: "We met DaB. A di M, if he had been there, would have wanted to meet him also." But that is not the American way. Unfortunately.

Noetica 22:55, 28 December 2012 (UTC)

Thank you, Noetica, for your reply. For a while, I had some difficulty in reconciling your subpoint 2 ("… this sort of thing would be fine …") with your subpoint 3 (… "so I support Tony's edit."), until I decided that you evidently meant that you "take abbreviation in usernames" as being exceptions to "normal English practice".

—Wavelength (talk) 03:30, 29 December 2012 (UTC)

Comment: there would be no ambiguity in your final example if we used two spaces after full stops. But I doubt this narrow situation warrants making such a change. AgnosticAphid talk 07:44, 29 December 2012 (UTC)

A large number of editors – anyone used to typing manuscripts of any kind – do use two spaces after the end of a sentence. It greatly aids readability of the wikicode (i.e. the manuscript) of an article here. Aside: I really do wish British editors commenting on issues like this would learn the difference between a "stop" (the character Americans call "period" traditionally, and that geeks around the world call "dot"), and a "full stop" which is a period/stop/dot at the end of a sentence. It's a usage that derives from telegraphy, if you're wondering. It's absurd to say something like "Initials should be spelled with full stops and spaced, as in 'J. K. Rowling'." Those are not full stops. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:20, 30 December 2012 (UTC)

Meh. Usage is variable. I have used "full point" (following NHR), and distinguished that mark from two of its functions: mark of abbreviation, and period (full stop). But many do not bother to make such distinctions, and those that do differ among themselves. As an aside, there is nothing more rational about either "period" or "full stop" for the mark itself. Each term is flawed in its own way. "Period" borrows its name from the stretch of text of which it marked the end (roughly, a sentence: anciently called a "period"). Compare "comma" and "colon", which originally meant certain kinds of smaller stretches of text. (SOED, at "comma n.": "1 In Class. Pros. & Rhet., a phrase or group of words shorter than a colon (COLON n.2 1); loosely (now rare or obs.) a short clause or phrase within a sentence. L16.") And "full stop", of course, conflates a function and a mark that serves that function.
Noetica 01:03, 31 December 2012 (UTC)

Yes. I'm asking that MOS regulars stop engaging in that particular conflation here because it confuses matters for too many (especially non-regulars). MOS itself needs to be checked for this conflation, and where "full stop" or "period" is used incorrectly (e.g. in reference to abbreviations) it should be replaced with, say, "full point (dot)" or "dot (full point)". — SMcCandlish  Talk⇒ ɖכþ Contrib. 04:00, 31 December 2012 (UTC)

The period in an abbreviation is really called a dot? Not usually, in my experience. Wiktionary:period says "5. (now chiefly North America) The punctuation mark “.” (indicating the ending of a sentence or marking an abbreviation)." Other dictionaries say something similar. So what am I missing? Art LaPella (talk) 07:14, 31 December 2012 (UTC)

Wavelength:

Your take on what I wrote is understandable. But in fact I meant that both practices are normal: using the full point to mark abbreviation, and not doing so. As WP:MOS explains, the difference is correlated with the US–British divide, though it does not follow it accurately. I strongly favour omitting that mark of abbreviation, finding it almost always redundant. Confusion is unlikely. There can hardly ever be a problem with Mr, Mrs, Dr, Prof, A J Cronin (or AJ Cronin for that matter), PhD, US (in most contexts), UK, UN, or USSR. But US English must have its way, even though it brings confusion of roles for the full point. Hence the rather balanced treatment we find in the current WP:MOS. I wish WP:ABBR were as balanced and as subject to careful scrutiny. Things are not looking good there.

AgnosticAphid:

Well, an extra space would have to be implemented using a hard space ( ) for one or other of the two spaces (or some equally grotesque expedient). Even this would be no use if the period were to fall at the end of a line, right? Unless both spaces were hard spaces, avoiding perfectly natural linebreaks. So the idea is a complete non-starter. Far better for US English to fall into line with international usage here (and with LQ, and with the metric system, and with avoidance of MDY date formatting, and so on). But life is not like that – a grim fact that MOS and Misplaced Pages simply have to live with. Some British preferences are silly too. Some comfort.

♥

Noetica 10:03, 29 December 2012 (UTC)

North Americans do not find anything "confusing" about the roles played by the period/dot/stop. It's simply a matter of familiarity and expectations. Many things in our language (and others, of course) are operator overloaded, serving multiple functions, and heads do not seem to explode about it. I certainly haven't proposed forcing British English articles to use "Dr.", etc., and I haven't seen anyone else do it in a long time. NB: I have attempted to revise MOS:ABBR to better represent Commonwealth as well as North American style. Not really done there yet, either. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:52, 30 December 2012 (UTC)

I'm Usonian, but I find the period in abbreviations to be annoying. IMO it shouldn't be used unless necessary – too easy to mistake it for the end of a sentence. I didn't realize it was an ENGVAR thing; I thought it was simply modern typography. — kwami (talk) 20:05, 29 December 2012 (UTC)

I've never in my semi-long life ever heard anyone claim that they could not tell the difference between an abbreviation and the end of a sentence. I think this would have to be classified as an extreme minority viewpoint. I don't know what "Usonian" means, but it probably doesn't matter. If it were simply "modern typography" you wouldn't see periods after abbreviations much any more, even in North American English (Canadian still uses them, too), just like (in reality) we don't see them in acronyms much any longer. I use a PIN at the ATM, not a P.I.N. at the A.T.M. But also if I want to abbreviate a shopping list, I'm looking for chk. soup, t. paper and apl. juice at the groc. store, not chk soup, t paper and apl juice at the groc store. It's especially important in WP articles that we are clear on the difference between conventional abbreviations (the few that are appropriate in articles; cf. MOS:ABBR), which take periods/stops/dots, and regular words (which aren't abbreviated), and units of measure (which are abbreviated but do not take dots). Misplaced Pages is not a text message. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:20, 30 December 2012 (UTC)

SMcCandlish, even if most Vespuccians do not ever have trouble because of the default use of full points to mark abbreviation (an empirical question, and a matter of degree because reading and comprehension can be slowed or impaired rather than simply disabled, and this would need measurement), the story doesn't end there. Compare US pronunciations of "can't", which many non-USards have great difficulty distinguishing from "can", though it never seems to trouble Americans. This is an international encyclopedia, and the needs of all readers count. But again, no point discussing the points! No change will result.
Noetica 01:03, 31 December 2012 (UTC)

I can guarantee you that deleting the dots from abbreviations has a slowing and impairing effect on reading comprehension, and ability to focus on the content, for readers who are used to them. They mark something as an abbreviation, just as all-caps marks acronyms as such, and if you are used to them you parse them instantaneously and automatically; their absence means we have to examine the unfamiliar string to try to figure out if it is an abbreviation missing its dot, an English word we don't know, a foreign word that should have been italicized, some kind of code that should have been marked up as such, a unit of measurement, a typo, or what (we'll usually conclude the first and the last simultaneously). I would bet good money that the amount of reading impairment to people used to them when they are absent exceeds that to people not used to them when they are present, because even people who don't use such dots know what they mean in this context, and they do not have to wonder any of that long list of stuff I just gave, only "is this an abbreviation or the end of the sentence?", and context will tell them the former in the vast majority of cases. I've never heard anyone say that American "can't" is hard to distinguish from "can" (if it is, it would probably also be true of any dialect that did not pronounce them as differently as UK "received pronunciation" does, which is something like Cannes vs. "cawn't"). But it's not relevant on WP, since it's a written medium, and blind people who use them control their own screen readers. So I'm not sure what you're getting at with that. It doesn't affect the needs of any readers at all. On a more constructive note, I think the eventual solution to this and several other ENGVAR issues is going to be templates and a new Preferences widget that interacts with particular templates to show a particular variant of material marked up with such a template. Something like {{engvar|us=tire|uk=tyre|ca=tire}} with Commonwealth countries defaulting to UK if not overridden, as Canada is in the example here, and places with a strong US influence on their English (Puerto Rico, Liberia, US Virgin Is., etc.) defaulting to US. There could be shorthand syntax for abbreviations, like {{engvar|abbr=Dr}} that would be equivalent to {{engvar|uk=Dr|us=Dr.}} And that's only one way to approach this technically; MediaWiki could be modified to add some kind of feature for this, but that might take 5 years. — SMcCandlish  Talk⇒ ɖכþ Contrib. 03:49, 3 January 2013 (UTC)

Thank you, Noetica, for your clarification.

—Wavelength (talk) 20:11, 29 December 2012 (UTC)

It's better to look a little awkward than to punctuate incorrectly. The period is part of the abbreviation and should not be omitted solely because it looks funny. I always leave them in when a comma follows. However, it shouldn't matter what I or anyone happens to prefer. What do the sources say? Darkfrog24 (talk) 03:56, 30 December 2012 (UTC)

I did a brief Google search. While I did not find many style guides that discuss the issue of periods followed immediately by commas, I did find several that use that construction: (L.L.C.) (Mo.) (p.m.) Darkfrog24 (talk) 04:08, 30 December 2012 (UTC)

MOS doesn't necessarily care "what the sources say", since paper style guides frequently conflict about almost everything. Our in-house style guide is not tied to New Harts's Rules, Chicago Manual of Style, etc., though we try to agree with them when this is both a) possible (i.e., they agree with each other), and b) it is actually helpful to the encyclopedia and its editors and readers to do so, without serious negative side effects. — SMcCandlish  Talk⇒ ɖכþ Contrib. 23:00, 30 December 2012 (UTC)

We have two choices, SMC, either hold the MoS to a standard at least as high as the requirements for ordinary articles and base its contents on reliable sources or base it on the whims and pet peeves of the few Wikipedians who contribute to this talk page. There's far too much of the second in the MoS already. Of course you prefer your own conclusions to those made by others; most people do, but that does not mean that other people should have to follow rules based on what you, I or anyone else does or doesn't happen to like. Darkfrog24 (talk) 15:53, 31 December 2012 (UTC)

We absolutely do not hold MOS to the sourcing standards of an article. You and several other people who come by now and again here make this assumption, but it's patently false, and by design. It's not based on "whims and pet peeves" of a "few Wikipedians". It's based on consensus of innumerable editors on what makes the best sense for this project and its readers (and editors). I repeat that we try to agee with CMoS and Hart's when this is practical on two different levels, but sometimes it is not and sometimes there are better options. An everchanging pool of editors who really care a lot become regular editors for a time on this page, and that is precisely how all other editing on WP works, whether it be at Siamese (cat) or Albinism or Firefly (TV series). Your WP:CABAL conspiracy theory about WT:MOS is basically just a bunch of "I didn't get my way on one of my pet peeves, so I'm going to lash out at those who are in my way" whining. It's childish and beneath your dignity. PS: Your "we have two choices" is a false dichotomy. MOS is actually a mixture of doing what other major style guides do, doing what various standards bodies recommend, doing what we have figured out by trial and error works best in our unique medium, compromising on something enough editors can live with that fighting dies down, and, yes, sometimes someone works in a pet peeve that few others agree with and which bugs people until it eventually gets removed. — SMcCandlish  Talk⇒ ɖכþ Contrib. 03:52, 3 January 2013 (UTC)

Oh I agree that we don't. We should. You see an "ever-changing pool of editors." It's more accurately called a clique.

You may call my preference for American punctuation a peeve if you like. Technically, a fondness for correct spelling, consistent capitalization, and lowercase common names for animal species are all peeves. However, the sources all agree with me. Forcing other editors do use incorrect English just because British punctuation has gotten fashionable is, to put it kindly, extremely inconsiderate. Darkfrog24 (talk) 15:28, 3 January 2013 (UTC)

Darkfrog, what do you mean by "punctuate incorrectly"? The punctuation we are talking about is a matter of style, and therefore it is variable. There is no "correct" alternative among those that are under consideration.

NHR (10.2.1 "Full points", pp. 169–170) treats this topic. For discussion right here, see this in Archive 127. I have edited for publications that prefer no full points in any kind of shortening. I like it. The points against such a simplification are few; but tradition dies hard, especially in the US.

Much of NHR can be seen on Google books, including the passage I mention above.

Noetica 05:04, 30 December 2012 (UTC)

In American English, "Dr." with a period is correct and "Dr" without a period is incorrect. That's what I mean by correct and incorrect. Leaving something out because you don't like it is one thing when writing for yourself, but we're talking about making rules that other people must follow.

In New Hart's Rules, page 169, last lines: "If an abbreviation ends with a full point but does not end the sentence, then other punctuation follows naturally: Gill & Co., Oxford."

So, according to British English source NHR, yes we should keep the period even though the comma comes right after it. Thank you for providing a source that spells this issue out for us so clearly. Darkfrog24 (talk) 18:13, 30 December 2012 (UTC)

(Fine Darkfrog. Thanks. I wasn't sure what you meant. Noetica 00:39, 31 December 2012 (UTC))

I can't believe we're still talking about this. There is no grammar/style guide anywhere, ever, that would recommend something like "Washington, D.C, Boston...". Anyone who can competently read English at all already intuitively knows that such a construction is non-standard. Let's just drop this and move on. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:20, 30 December 2012 (UTC)

In response to Noetica, further above with the bullet points, I generally have to concur with much of that, especially that "the destination language (English) should dominate" here. However, there is nothing "irrational" about "Dr." vs. "Dr". Also, when there's a profusion of dots, the solution, as with most editing problems on WP, is to rewrite slightly: "We met DaB. A. di M., if he had been there, would have wanted to meet him also." ⇒ "We met DaB; A. di M., if he had been there, would have wanted to meet him also." Aside: Note that I wrote that "I would" not use the serial comma there; I didn't tell anyone else not to, and MOS largely dodges this issue because there's so much disagreement about it. There are even competing userboxes about this. :-) — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:20, 30 December 2012 (UTC)

Well, we do disagree then. You and I agree that LQ is more rational than the alternative, which dominates in American usage. I argue from generally similar premises that a profusion of semantically redundant full points (to use a British term) is irrational. Similarly, I judge that the US preference for fewer hyphens and more closed-up forms is more rational than the British preference. But let's leave it, since nothing in WP:MOS will change as result of any deliberations on such matters.

As for rewriting, I do not agree that we should promote that as a first recourse, or even as an early one. Many competing pressures join to produce elegant solutions in writing; but it not healthy when sentence punctuation is hostage to oddities in the styling of abbreviations (a kind of word punctuation, as some call it).

As for the serial comma, sure: we disagree about that. I would argue at length for its default use, but not here. Again, nothing on the topic is relevant to improvement of WP:MOS. Unlike Darkfrog (in earlier discussions), I do think that treatment of the serial comma in MOS ought to be shortened.

Noetica 00:39, 31 December 2012 (UTC)

Unless someone has published a solid study showing that the presence or absence of a dot in an abbreviation aids or impedes reading comprehension, then it's just taste and personal preferences in various wrappers. The same goes for British vs. American punctuation. Darkfrog24 (talk) 01:07, 31 December 2012 (UTC)

Darkfrog24: True enough. Noetica: Cases like the "Dab. A. di M." example are so infrequent that it's a non-issue in my view, and certainly doesn't rise to the hyperbolic heights of "hostage"-taking. It's comparable to "don't begin a sentence with 'iPhone' or '4chan'", really; just an occasional inconvenience to work around. Not everone, including me, agrees that dots at the end of abbreviations are "semantically redundant" at all, and that's not an irrational position (unlike the position that LQ is "stupid" or "wrong", which is irrational). No real opinion on US vs. UK hyphenation, or at least not one easily expressed here; I've touched on it, in a non-ENGVAR-tinged way, at WP:MODENG. I don't follow you on your opposition to rewriting. We do this for just about everything that is problematic when we write. A large percentage of MOS is specific instruction on what to rewrite and how. Agreed that serial comma treatment can probably be shortened here. — SMcCandlish  Talk⇒ ɖכþ Contrib. 05:18, 31 December 2012 (UTC)

"See also" section and navigation boxes

Editors may wish to comment at Misplaced Pages talk:Manual of Style/Layout#See also section (version of 00:50, 29 December 2012). See also Misplaced Pages talk:Manual of Style/Archive 130#Position of navigation boxes (September 2012).
—Wavelength (talk) 03:52, 29 December 2012 (UTC)

Thanks. I actually like the Alternative proposal there for several reasons. There's a related, but less well-thought-out, RfC happening at Misplaced Pages talk:Categories, lists, and navigation templates#RfC: Section headings for horizontal navigation templates (to add a new heading like ==Related information== above navboxes). The two ideas are mutually exclusive, yet the "Alternative" proposal at the first link (move "See also" to bottom of page) would effectively give proponents of the second what they want by merging navboxes and "See also", which serve the same basic function, and fix the problem that "See also" items, like navboxes, are the least relevant things on the page, even counting external links usually. (The non-"Alternative" proposal at the first page is just more "doesn't really understand style issues" noise from Apteva, in this case a call to put redundant links in both "See also" and navboxes.) — SMcCandlish  Talk⇒ ɖכþ Contrib. 01:29, 31 December 2012 (UTC)

I have recently been re-ordering sections according to WP:ORDER—see my contributions—and these changes to the guidelines could complicate my work. (When will there be stable versions of WP:MOS and its subsidiary pages?)

—Wavelength (talk) 17:58, 31 December 2012 (UTC)

Yes, it would change the order of the sections. It's something a bot can fix, trivially, for sections that have standard names. "It will take a long time for the change to propagate through articles" has never been a reason to not make a change in MOS or any other guideline that is for the better; WP adapts rapidly. There will probably never be entirely stable versions of MOS and subpages, judging by MOS's ongoing history. — SMcCandlish  Talk⇒ ɖכþ Contrib. 01:25, 2 January 2013 (UTC)

Large-scale bug?

In recent times, two bots and one AWB user have, in the article Richard Wagner, changed "1862–1902" to "1862 – 1902" (example). Misplaced Pages:Manual of Style#En dashes: other uses seems clear enough to me, so what is going on? Toccata quarta (talk) 10:19, 29 December 2012 (UTC)

Take it up with AWB on their bug page. It didn't used to do that. The spaced dash is used when there are full dates. Perhaps someone screwed up when revising the replacement rules. — kwami (talk) 20:26, 29 December 2012 (UTC)

I filed it as a bug report over there (to the extent possible – Toccata, you need to go there and add more info to the bug report, such as AWB version number, etc.) — SMcCandlish  Talk⇒ ɖכþ Contrib. 23:32, 30 December 2012 (UTC)

 Done Bug reported and fixed. Check Wikipedia_talk:AutoWikiBrowser/Bugs/Archive_21#Large-scale_bug.3F -- Magioladitis (talk) 23:52, 30 December 2012 (UTC)

Italic titles with parentheses?

Hello. I recently created the article Così è (se vi pare). When I added the template to italicize the title, it did not italicize the part of the original title in parentheses. I assume this is built in to assist with disambiguation, but is there an override for when the work's title has parentheses in the title itself? Feel free to fix the linked article if you know the workaround, or leave a message on my talk page. Thanks. Jokestress (talk) 11:15, 29 December 2012 (UTC)

Done by using displaytitle: manually. — Edokter (talk) — 13:02, 29 December 2012 (UTC)

Another solution is to use the HTML character entity codes for the parentheses (round brackets, whatever): Così è (se vi pare), which renders as: Così è (se vi pare). I bet you could get way with just escaping the ( as ( and leave the ) alone. — SMcCandlish  Talk⇒ ɖכþ Contrib. 02:29, 31 December 2012 (UTC)

What's wrong with linking from within quotations?

I've always been puzzled by the following provision:

As much as possible, avoid linking from within quotes, which may clutter the quotation, violate the principle of leaving quotations unchanged, and mislead or confuse the reader.

How do the links in the (hypothetical) quotation given here clutter it, change it, or mislead or confuse?

According to the prosecutor, "The defendant, armed with a MAC-10, robbed a liquor store in Cooperstown. Though no shots were fired the felony murder rule makes the defendant responsible for the security guard's death from cerebrovascular accident brought on by stress-induced hypertensive crisis. We disagree with the amicus brief filed in this case by the NRA."

Why should (as MOS currently seems to demand) these handy links be replaced with a lot of awkward footnotes and surrounding verbiage? I propose that all that need be said is that links must not inappropriately color the meaning of the quoted material. Thoughts? EEng (talk) 14:03, 29 December 2012 (UTC)

That may not be bad, but suppose the prosecutor has misused hypertensive crisis (not in the sense of being incorrect, but of meaning something else, entirely). Then it shouldn't be linked. And how are we to know?

For that matter, he could have misused felony murder rule, although I'm almost sure he didn't. — Arthur Rubin (talk) 14:34, 29 December 2012 (UTC)

Edit conflict with Arthur Rubin's additional comment below, but I don't want the end-with-preposition joke waste go to. How are the points you raise dependent upon the fact that the article directly quotes the prosecutor instead of paraphrasing him (or her)? The MOS provision I've brought up for discussion implies it matters somehow, and that's the question I'm concerned with (not to reignite the terminal debate , I hope). EEng (talk) 16:06, 29 December 2012 (UTC)

It is a crazy rule. If Alex Ferguson says that he is "considering using Valencia as left back in this weeks match", we can be absolutely confident that he means the only footballer of that name employed by his club, not the city, community, historic kingdom, football club, motor racing circuit, song, ship, book, lingerie model, citrus fruit, toothcarp, film, fictional island, university or video game character of the same name. Suggest rephrasing as Links should only be used within quotes where the intended meaning of the linked term is beyond reasonable dispute. Kevin McE (talk) 15:13, 29 December 2012 (UTC)

I hadn't realized the rule was so strict; the last time I looked at it in detail, I thought I saw an exception if the intended meaning was clear in context, and would not be clear standing alone, without the context of the article. — Arthur Rubin (talk) 15:40, 29 December 2012 (UTC)

Surely it is up to the editor who is doing the linking to en sure that the links are appropriate, is is the case for any other Wikilinking - as regards Alex Ferguson - he woudl almost certainly be talking about Valencia, not Valencia - it makes no difference whether the link is inside a quote or not. Martinvl (talk) 16:17, 29 December 2012 (UTC)

Nope(@Arthur Rubin after ec): full text of the linking section within MoS#Quotations is:

As much as possible, avoid linking from within quotes, which may clutter the quotation, violate the principle of leaving quotations unchanged, and mislead or confuse the reader.

Two alternatives are available:

• You may add a sentence in a ref element, that is not in a quotation and mentioning the subject to be linked to, and link there. For example, you may add <ref>Misplaced Pages has an article on ].</ref> or <ref>''History'', p. 79. (Misplaced Pages has an article on ].)</ref>
• You may bracket within the quotation and put the link text within the brackets. The bracketing may not include internal quotation marks. The link text may not be identical to the adjacent wording. For example, you may write "The City of New York <nowiki></nowiki> has boundaries set by law."

The second of these alternatives makes an absolute nonsense of the proposed goal of leaving the quotation unchanged and uncluttered: the first still changes and clutters the quote, although not as much, but makes the relevant information less easily accessible to the reader.

I can foresee no instance where it is impossible to avoid linking, so this amounts to an absolute ban on giving the reader simple and unobtrusive clarification. For an encyclopaedia to prohibit itself from this is a ridiculous position to take. Kevin McE (talk) 16:24, 29 December 2012 (UTC)

Agreed. Misinterpreting a direct quotation is not much different from misparaphrasing it. In fact, it may be better to have a bad link in a direct quote, because it will be obvious to knowledgeable readers that a mistake has been made. A bad job in paraphrasing, on the other hand, may go unnoticed for much longer. As for Arthur's objection that jargon may be misused, if that is the case we certainly need to point it out! A mistake is a mistake whether we link to the article or the reader has to type it into the search box.

I do think, however, that we should discourage links within quotations. It is quite annoying to read a quotation with links for every word beyond a sixth-grade reading level. That's a general problem we have with over-linking, but somehow it seems more obnoxious in quotations. Perhaps we could have milder restrictions, such as only linking ambiguous items like Valencia above? — kwami (talk) 20:23, 29 December 2012 (UTC)

Overlinking is a separate issue that has its own guideline. There is no need to duplicate it in MoS#Quotations#Linking. Are you seconding my proposed alternative text above? Kevin McE (talk) 20:32, 29 December 2012 (UTC)

Yes, that seems reasonable. — kwami (talk) 22:44, 29 December 2012 (UTC)

In that case, let's formalise it. I add a warning based on most apposite part of previous ban, but remove the two suggested workarounds as redundant, unused (in my experience), and contray to their stated purpose. Kevin McE (talk) 23:02, 29 December 2012 (UTC)

Linking within quotations: Proposal 1

Replace existing text at MoS#Quotations#Linking with this text:

Links should only be used within quotes where the intended meaning or referent of the linked item is beyond reasonable dispute. Particular care should be taken that the principle of leaving quotations unchanged, in meaning or content, is not violated.

Kevin McE (talk) 23:02, 29 December 2012 (UTC)

• Support, pending further discussion. I think your warnings should be enough to cover the problems mentioned above. I'd still like to see a word on avoiding frivolous links, but not enough to quibble over it. (I'm adding 'referent' above, and changing 'term' to 'item', since in general we wouldn't be linking to dictionary definitions, but to people, places, historical eras, etc.) — kwami (talk) 23:37, 29 December 2012 (UTC)
• Procedural comment. Having seen some discussion at Kwami's talkpage between him and Kevin, I endorse Kwami's addition of "referent"; but I have removed the square brackets that made it seem like a gloss on "meaning" rather than a genuine addition. I have also boldly reformatted, and removed some striking-out.
  Editors: please do not now make alterations to the proposal. I did so only because no one uninvolved had yet expressed an opinion, or voted. If there is disagreement here, an advertised RFC would be needed. This is no trivial change. Noetica 03:03, 30 December 2012 (UTC)
• Oppose as an incompetently drafted proposal. I tried to disambiguate the intent for the proposer (and sought clarification at his talkpage), before anyone else commented while the meaning was uncertain. I got no answer from the proposer, who instead substituted new wording, restoring the ambiguity. Sorry! Not good enough, for a discussion of major change to the core of Misplaced Pages's manual of style. ♥ Noetica 10:57, 30 December 2012 (UTC)

You changed my input on a talk page in a blatant breach of the guideline: I restored the original meaning (yes: I used "new" wording in as much as I used existing rather than the original current: that, unlike your change, is not substantive, and I have the right to change my contributions anyway, you do not.) You did so after reading my message on Kwami's talk page which had the main purpose of asking him not to change my signed comment. At least he had the dignity to specify what change he had made to the proposal, which you did not. Whether my word was current or existing (the change came about through editing from memory of my intention, without bothering to look at past diffs), it is unequivocal and unqualified, and can only be read as meaning the whole subsection, which is linked. I had already made my opinion on, and intention to excise, the workarounds clear. Your change introduced uncertainty, and speculation as to what the extent of the "relevant" text. Your edit note states, "otherwise it could seem that the entire text of the linked location is to be replaced, but it is not clear that this is intended"; if I say replace current/existing text, without qualification, it is evident that I mean the whole of current/existing text. How can an unspecified value judgement as to what is to be deemed relevant be a clarification upon that? And yet it is on that basis that you dismiss the proposal as "incompetently drafted." This strikes me as a very bad faith comment. Kevin McE (talk) 11:39, 30 December 2012 (UTC)

Inaccurate throughout, Kevin. But please do not continue the side discussion here. This page is for improving WP:MOS, by means of orderly and clear dialogue. See your talkpage for continued treatment of the lesser issue. Noetica 11:47, 30 December 2012 (UTC)

If you are going to publicly denounce my statements as inaccurate, you need to be willing to publicly justify that. Either retract, or present your justification (at my talk page if you prefer). Kevin McE (talk) 12:02, 30 December 2012 (UTC)

Don't worry about it, Kevin. Everyone sees what's going on here. EEng (talk) 21:10, 30 December 2012 (UTC)

What do you mean, EEng? (If your answer to this question is not relevant to improvement of WP:MOS, please answer me at my talkpage.) ♥ Noetica 00:20, 31 December 2012 (UTC)

I meant that, to the extent Kevin was concerned about other editors' views of your recent interactions with him, it was my belief that further interaction between you two was unlikely to enhance the fidelity of such views to the ultimate truth of the situation (if you will forgive my Platonism). EEng (talk) 02:34, 31 December 2012 (UTC)

Orright Bruce, save it for round the sheep-dip. Just let's have unambiguous proposals (unlike the present one), and discuss them in a way that everyone can follow. Noetica 02:49, 31 December 2012 (UTC)

What do you think of SMcC's multipoint analysis (under Proposal 2 below)? EEng (talk) 14:11, 31 December 2012 (UTC)

I think it's acute and useful, as expected from SMcCandlish. I agree with his oppose vote. (No more here, please. Stay on topic.) Noetica 22:09, 31 December 2012 (UTC)

• Oppose per Noetica. This is perennial rehash, and a not very well informed approach to it. You need to do a lot more homework on this issue if you want to re-raise it. For the record, I'm generally in support of the idea that we can link from inside quotations, when doing so helps prevent gross redundancy, but that it should otherwise be avoided because it is very easy to stumble over WP:NPOV and WP:NOR problems by making WP:POINTy or just accidentally inappropriate links. I have to concur with others that this is a content editing matter, not a style matter, so it's off-topic here anyway. — SMcCandlish  Talk⇒ ɖכþ Contrib. 21:55, 30 December 2012 (UTC)

  PS: My second "Oppose", to Proposal 2 below, and in particular the commentary following that !vote, has considerably more detail about what I think is wrong with the current wording. Though I don't support either of these particular proposals, the current section is quite problematic. — SMcCandlish  Talk⇒ ɖכþ Contrib. 06:10, 31 December 2012 (UTC)

• Oppose deleting the entire exiting text. I don't see why the existing suggestions deserve to be deleted and the proposal doesn't address that issue at all. Perhaps it would have been a better proposal if it said "relevant" rather than "existing." ><

Substantively, I am sympathetic with the clutter argument; I don't really like wikilinks and if a topic is that important to an article, what are the chances that it was first mentioned within a quote? But I don't see how adding the link is confusing. Obviously the person being quoted did not include a wikilink in his or her actual statement. I kind of doubt that readers would assume otherwise. Similarly, is it really OR or NPOV to wikilink the actual term used in the quote? Suppose, for example, that the person above really did misuse "hypertensive crisis" and he actually meant some other heart-related problem. Wikilinking does not make the statement any more or less accurate; it would simply make it easier for readers to figure out what hypertensive crisis is. Readers can draw their own conclusions on whether it's accurate, or maybe we could find a secondary source that says he used it incorrectly and probably meant something else. It would, of course, be OR for us to just wikilink some topic other than "hypertensive crisis" that we assume he or she intended, and I wholly support a prohibition on such linking.

Finally, I can't say that I think this should be addressed somewhere other than the MOS. The MOS seems like the first place you would look for a rule like this if it existed. While it's true that the line between style advice and substantive advice is a little blurry here, that is the case for many aspects of the MOS and I feel that except for cases where advice is clearly related to substance only that the MOS and its talk page are not an inappropriate place for discussion. AgnosticAphid talk 23:39, 31 December 2012 (UTC)

Linking within quotations: Proposal 2

As the editor who initiated this discussion by supplying the subtly beautiful and breathtakingly comprehensive example seen at the start of this thread -- an example which (I have no choice but to reveal) has brought me laudatory letters and telegrams of congratulation from heads of state on four continents, noted philosphers and, yes, even His Holiness Pope Benedict, for its almost magical power of stimulating intelligent and civil debate on this critical topic -- I'd like to jump in for a second. (deep breath)

I too strongly dislike overlinking, hate "easter egg" links, and despise misleading or inappropriate links -- whether inside or outside direct quotations. But why do we need a new, hard-to-interpret level of scrutiny ("beyond reasonable dispute") especially for links within quotations? As someone pointed out, you can overlink or mis-link in a paraphase just as easily, so what does this achieve? So here's my proposal (if it's inappropriate for me to offer an alternative this way someone please tell me what to do instead):

Replace current text at MoS#Quotations#Linking with...

nothing. Eliminate it.

I realize there's no instance on record of a MOS issue being resolved by reducing complexity and eliminating text, rather than larding more text and rules and exceptions on top of what's already there, and it's only fair to remind everyone that some physicists believe that doing so could, under some theories, act like the collision of Universe with Anti-Universe, bringing to an end all Time and Existence as we know it, but I for one am willing to take the risk. EEng (talk) 03:29, 30 December 2012 (UTC)

Yes, actually. An inappropriate link would be bad anywhere in the article. We do need to be especially careful with quotes, but WP:QUOTE is probably the place to cover this, since it's not a stylistic issue. Currently we just say, The quotation should be representative of the whole source document; editors should be very careful to avoid misrepresentation of the argument in the source. Perhaps we might want to clarify that an improper link can cause that misrepresentation. — kwami (talk) 04:00, 30 December 2012 (UTC)

Kwami, I think you've hit on an important point. Once we decide links are OK from within quotes, it ceases to be a MOS issue. I think it's fine to mention at WP:QUOTE that linking can mislead readers just like improper context and other things can, without necessarily trying to create magic litmus paper that bursts into flames when you've done it wrong -- anyway, that can be taken up at QUOTE. I'm not sure what you mean by "Yes, actually" -- what are you supporting? EEng (talk) 04:31, 30 December 2012 (UTC)

Support. I'd support either proposal as an improvement. I'm not sure complete silence is the way to go, but I don't think the MOS is really the place for whatever needs to be said. — kwami (talk) 05:43, 30 December 2012 (UTC)

• Support. Personally I would not use links inside a quote - ever, but if there are those who disagree, there is obviously no consensus that this should be in the MOS. Apteva (talk) 04:03, December 29, 2012‎ (UTC)

• Oppose a messily presented proposal, followed so far by ill-structured commentary. The issue is important, and the matter has been discussed here at length before – with far better structure and consideration for editors who want meaningful dialogue. Do better, please. Note that the page is subject to unusually close scrutiny, for a reason. ☺ Noetica 11:03, 30 December 2012 (UTC)

• Perfectly happy with this (can't quite bring myself to fully support a counter-proposal to my own, but that is as much due to hubris as to commitment) and fully aware that my own proposal is essentially true of any link anywhere, and not specific to links within quotes, as would be any note warning about overlinking. I note that WP:QUOTE (an essay, not an adopted guideline) is already totally silent on the matter. Maybe I thought that total elimination was a step further than I was brave enough to propose: maybe it is worth retaining a non-restrictive warning. Kevin McE (talk) 11:13, 30 December 2012 (UTC)

• Oppose: Deleting material from MOS and other major guidelines generally does not work well, because it was added for specific anti-editwarring, dispute-resolving reasons. — SMcCandlish  Talk⇒ ɖכþ Contrib. 21:57, 30 December 2012 (UTC)

Can you give an example of the kind of problem the existing text (proposed for deletion) might prevent -- and why that problem is more likely to arise with links inside quotes any more than with links outside quotes? EEng (talk) 23:11, 30 December 2012 (UTC)

That's already been adequately covered by previous discussion in this thread, and isn't even particularly responsive to what I wrote anyway. I have a lot on my wikiplate today, and don't feel like reiteration is a good use of my time, honestly. — SMcCandlish  Talk⇒ ɖכþ Contrib. 23:21, 30 December 2012 (UTC)

Now that I'm caught up on pressing things, I can address this. I'm not sure what to say other than to ask what objections you have to what parts of "As much as possible, avoid linking from within quotes, which may clutter the quotation, violate the principle of leaving quotations unchanged, and mislead or confuse the reader." It seems mostly clear cut to me. I don't like the "As much as possible" wording, because it's silly hyperbole – it is of course possible to never, ever link inside a quotation. So it does not get its point across properly. The rest of it makes perfect sense to me. It just needs to be flexible enough that people can link in quotations when this is the best option for the article. To that end, I might favor removal of the "violate the principle of leaving quotations unchanged" part (an argument can be made that adding a link does not qualify – the link is metadata, not data). To me, "mislead or confuse the reader" is the most important factor to watch out for, since inappropriate or "leading" links can be a serious WP:NPOV issue (attempting to link the quoted statement to something positive or negative that the editor wishes readers to associate with the quoted party, where there is actually no such association) and WP:NOR (novel synthesis, by the same mechanism) problem. — SMcCandlish  Talk⇒ ɖכþ Contrib. 05:55, 31 December 2012 (UTC)

To directly address your original question, "How do the links in the (hypothetical) quotation given here clutter it, change it, or mislead or confuse?" They cluttered it, in the view of some, by festooning it with bluelinks. I don't feel that this is true if and when our general principles about what to link and not link are applied (i.e., avoid overlinking); your legal case example was fine, to me. They changed it, in the view of some, by adding links that were not present in the original. I see this argument as childish and silly, honestly; it will almost never, ever be the case that we'll quote something in an article and preserve links in the quote (due to WP:EL concerns for starters), and everyone who's been on WP more than 2 minutes immediately figures out that links are metadata, not data. They can mislead or confuse in ways I've already discussed, immediately above (your example, again, did not exhibit this problem). Hope that helps. To me, only the last issue (NPOV and NOR "mislead or confuse" problems) are a legit concern. — SMcCandlish  Talk⇒ ɖכþ Contrib. 06:08, 31 December 2012 (UTC)

I appreciate your thoughtful comments and agree on every point, including that the single valid issue with linking from within quotations is the danger that an inappropriate link will mislead or distort. So what I need to understand is: since this precise problem arises, in precisely the same way, outside of quotations (in, say, a paraphrase of a quote), why aren't these issues dealt in a discussion of link selection in general (not a MOS issue) instead of the current guideline's implication that particular formatting of links (shifting them into footnotes or bracketed asides) magically makes them all OK? EEng (talk) 13:58, 31 December 2012 (UTC)

Probably because some editors object to links in quotations for other reasons and, not realizing as you have that the misleading-links problem is not limited to quotations, they have shoehorned it into the section on links in quotations. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:12, 1 January 2013 (UTC)

• support the concept of linking withing quotes, oppose the idea of just blanking Misplaced Pages:Manual_of_Style#Linking. I think linking withing quotes is fine, as long as overlinking is avoided. Greengreengreenred 22:29, 30 December 2012 (UTC)

• Oppose all proposed changes (although the wording could be cleaned up a bit). If the original quotation doesn't have a link or some footnote, why should WP add one? If the material is that ambiguous, the link should be placed in the supporting text, not the quotation itself. Neotarf (talk) 05:04, 31 December 2012 (UTC)

  It's often about redundancy, not ambiguity. In a complex quote with a lot of jargon or terms-of-art, one will essentially have to reiterate most of the quotation in order to link to the articles on the concepts in the quote, and this is often almost painfully redundant and repetitive. — SMcCandlish  Talk⇒ ɖכþ Contrib. 05:44, 31 December 2012 (UTC)
  PS: To be clear, when a case like this arises, I will definitely link in the quotation, citing WP:IAR if it comes to that. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:14, 1 January 2013 (UTC)

• Support I had little trouble getting to grips with the proposal (although I was shocked by some of the phrasing of those involved here in these discussions e.g. in the first proposal, a response including "an incompetently drafted proposal", probably why the majority of editors swerve discussions here, to avoid being cut down, belittled and trampled over by so-called "experts". Such self-declared "experts" need to think again, this Misplaced Pages relies on volunteers, not "experts"). I think removing any quote-specific format regulation and relying on the rest of MOS (and of course, common sense) is an obvious step forwards. Many quotes will contain the odd word or phrase which needs to be explained. Making those phrases the odd ones out, in our normal prose rules, by enforcing a regime where footnotes (or other methods) should be used to help the reader understand the meaning and context of certain phrases is absurd. On the odd occasion that these links are deemed incorrect, or potentially ambiguous, let's talk about it. The Rambling Man (talk) 18:43, 31 December 2012 (UTC)

I can understand that, because I was shocked also. Shocked that a fundamental ambiguity has been allowed to remain in that first proposal. I took the issue to the proposer's talkpage, which is appropriate. I suggest you do similarly. The present subsection (which I have refactored, so yes: you can follow it with "little trouble") is for the second proposal. Please stay on topic. ☺ Noetica 21:59, 31 December 2012 (UTC)

Please try not to be so condescending. It's little wonder so few real content editors bother here. The Rambling Man (talk) 11:14, 1 January 2013 (UTC)

Please try to stay on topic. It's little wonder these proposals get nowhere if people don't care about clarity and removal of ambiguity. A reminder: this talkpage is for discussion toward improving Misplaced Pages's manual of style. ☺ Noetica 11:36, 1 January 2013 (UTC)

So it's not for being condescending to other editors then as you seem appear magically able to do with alarming regularity? Okay, thanks for your clarification. The Rambling Man (talk) 11:43, 1 January 2013 (UTC)

• Oppose if I correctly understand that the proposal is to delete the section Misplaced Pages:Manual_of_Style#Linking. I could understand wanting to shorten or simplify that section, but not why we would want to remove it. I also agree with Noetica that a clear proposal would have a better chance, and after looking at the talk page where he discussed the ambiguity, I am flummoxed about why it was allowed to stand that way, and then made worse in proposal 2. Dicklyon (talk) 22:15, 31 December 2012 (UTC)
• Oppose I oppose deletion of the entire section for the reasons I discuss above. It does not seem to me that the justifications that originally prompted this advice have been either debunked or shown to be wholly unpersuasive. I think that deleting the text is the same as allowing wikilinks in quotes, but there is inadequate justification and consensus for such a major change. So, I think the text should stay, even though I have some problems with it. AgnosticAphid talk 23:42, 31 December 2012 (UTC)

Plural titles with 'the'

Our naming guidelines advise against plurals and 'the' in article titles, but sometimes they're appropriate, IMO. Because of the guideline, however, people have repeatedly tried to move the Dakotas, the Maritimes, the Carolinas, etc., and they have moved Americas. If you have any wisdom to impart, see Misplaced Pages talk:Naming conventions (definite or indefinite article at beginning of name)#Plural names. — kwami (talk) 20:10, 29 December 2012 (UTC)

Yeah, these are all conventional exceptions, like The Hague and Cue sports. Some things need a "the" (or "The", very rarely except in the common case of titles of published works), and some need to be plural for logical reasons. — SMcCandlish  Talk⇒ ɖכþ Contrib. 21:49, 30 December 2012 (UTC)

Clarification to "Scrolling lists and collapsible content"

This section currently reads:

Scrolling lists, and boxes that toggle text display between hide and show, should not conceal article content, including reference lists, image galleries, and image captions. They especially should not be used to conceal "spoiler" information (see Misplaced Pages:Spoiler). Collapsible sections or cells may be used in tables that consolidate information covered in the main text, navboxes, or chess puzzles. When scrolling lists or collapsible content are used, take care that the content will still be accessible on devices that do not support JavaScript or CSS.

This is genuinely problematic, as people have been using one particular omission as an excuse to add collapsed lists of content to articles, as at http://en.wikipedia.org/search/?title=Detroit_Zoo&oldid=522128534#Animals and a number of similar articles. I fixed the Oaklawn Farm Zoo#Animals piece by converting it to a normal list (and de-capitalizing the animal common namees), while at Detroit Zoo#Animals I converted the list to a paragraph, as a different demo of how to fix this (and de-capitalized again). Whether or not such a list is useful in such an article at all – note that Bronx Zoo, etc., do not have such a section – is irrelevant to the wider issue; lists of content are appropriate in some articles, and this is about people forcing them to be collapsed by default. I propose the following re-wording:

Scrolling lists, and boxes that toggle text display between hide and show, should not conceal any article content by default, including embedded lists of content, reference lists, image galleries, image captions, etc. They especially should not be used to conceal "spoiler" information (with the exception of chess puzzles). Collapsible sections or cells may be used in tables that consolidate information already covered in the main text, both in the article body (uncollapsed by default), and in navboxes and infoboxes (may be collapsed by default). When scrolling lists or collapsible content are used, take care that the content will still be accessible on devices that do not support JavaScript or CSS.

I separately and severably propose removal of the chess puzzle exception, because a) in looking over all the chess puzzle and chess problem articles, I can't find a single case(!) that still uses a collapse box to hide the solution, and b) it's simply a variant of spoiler-hiding to begin with – if a magical exception is made for WikiProject Chess, everyone's going to want one (cf. rampant animal common name capitalization all over Misplaced Pages, stemming directly from the WP:BIRDS project insisting on doing it in ornithology articles; some "slippery slope" arguments are demonstrably valid). — SMcCandlish  Talk⇒ ɖכþ Contrib. 21:45, 30 December 2012 (UTC)

Any objections? — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:19, 1 January 2013 (UTC)

Pending discussion of the main proposal, I'm at least going to remove the chess exception because it is no longer relevant; zero articles use it any longer (i.e. it's a clear case of WP:CREEP and arguably now WP:BEANS, in an invert way, because we already have a general prohibition against spoiler-hiding). — SMcCandlish  Talk⇒ ɖכþ Contrib. 01:29, 2 January 2013 (UTC)

Minor BLP issue in MOS

As a WP:BLP matter, we really should not use the names of living people, public figures or not, in examples like "The author thanked her father, President Obama, and her mother, Sinéad O'Connor." — SMcCandlish  Talk⇒ ɖכþ Contrib. 23:05, 30 December 2012 (UTC)

Change them to Robin Hood and Little Bo Peep then. Rich Farmbrough, 03:02, 3 January 2013 (UTC).

Bolding of major roles

Please consider joining the feedback request service. An editor has requested comments from other editors for this discussion. This page has been added to the following list: Misplaced Pages style and naming When discussion has ended, remove this tag and it will be removed from the list. If this page is on additional lists, they will be noted below.

Well, here it goes. In the Anime and Manga WikiProject, it is established practice to bold major roles (for examples, see Rie Kugimiya, Tomokazu Sugita, Aya Hirano and Yui Horie). However, this is not one of the uses of bold listed at MOS:BOLD (for examples of articles not using bold, see Aki Toyosaki , Mamoru Miyano , Haruka Tomatsu and Maaya Uchida ). I'm requesting comment because this could potentially affect hundreds, even thousands, of articles about voice actors. So this RfC is about if there is consensus to continue bolding major roles in articles, and thus proposing that the practice be added to MOS:BOLD, or if we shouldn't bold major roles. In a nutshell: should bolding major roles be included in MOS:BOLD or not? Narutolovehinata5 23:50, 30 December 2012 (UTC)

• Wrong venue: That comment applied to the original posting at the Wikiproject talk page. Comment:This obviously should be taken up at WT:MOS, since it really has nothing at all to do with anime in particular, but all voice acting, possibly even all acting across the board! Stuffing it into a page no one but project members pays any attention to is only going to result in a WP:LOCALCONSENSUS that won't override WP:MOS, as a matter of policy. This should be either voluntarily moved by the proposer, or procedurally closed by an admin and re-opened. — SMcCandlish  Talk⇒ ɖכþ Contrib. 23:18, 30 December 2012 (UTC), updated 00:04, 31 December 2012 (UTC)

Ok, I'm moving this to WT:MOS (I was going to bring it there anyway.) Narutolovehinata5 23:46, 30 December 2012 (UTC), updated 00:04, 31 December 2012 (UTC)

Comments after the move

Per the comments made by SMcCandlish, I've moved the discussion to here. Further comments can be made below this line. Narutolovehinata5 23:50, 30 December 2012 (UTC)

• Question: What is the supposed point/justification in all this boldfacing, which at some of the examples you provide is both excessive (to me) and inconsistent even within the same article. — SMcCandlish  Talk⇒ ɖכþ Contrib. 00:04, 31 December 2012 (UTC)

Before I answer your question, I'll give a little background on this. I decided to start this discussion because of this discussion on my talk-page. You see, I had been de-bolding roles from a number of articles because it was not listed in MOS:BOLD. However, as pointed out by Leofighter (talk · contribs) on my talk-page, bolding roles is useful because it allows users to see which roles are major ones. However, Lucia Black (talk · contribs) states that, bolding of roles without giving a reliable source counts as original research.

Personally, I have no problems with bolding roles in articles, but I want to see if there is consensus to include this in MOS:BOLD or not. While I'm not proposing that it should be done, I can sort of see Leofighter's point. It would be convenient for those interested in learning the person's major roles. The problem with this is, without a reliable source confirming that the role is "major," then this counts as original research. And the reason why it's rather inconsistent is that only major roles are bolded. Narutolovehinata5 00:28, 31 December 2012 (UTC)

Thanks for the explanations. — SMcCandlish  Talk⇒ ɖכþ Contrib. 00:36, 31 December 2012 (UTC)

• Oppose: It's too inconsistent and convoluted for anyone (like, um, our readers) to intuitively understand without being members of some such WikiProject and following their discussions in detail. Most readers, like I did, are going to simply think "WTF? Why on earth is this so sloppy, with some stuff boldfaced for no apparent reason?" And Leofighter is correct that Wikipedians deciding, willy-nilly, what is and isn't a "major" role is blatant original research. This might (arguably not) be appropriate on some fandom wiki, like Battlestar Wiki or whatever, but it's not an encyclopedic practice in WP terms. — SMcCandlish  Talk⇒ ɖכþ Contrib. 00:36, 31 December 2012 (UTC)

• Oppose per SMcC, and on the general principle that the use of typographic effects to convey information should be kept to a minimum—and should follow only well-established conventions. If a role is really important it should probably have its own subsection heading.—Odysseus1479 (talk) 02:03, 31 December 2012 (UTC)
• Oppose per SMcCandlish. I've said the same thing while maintaining Aki Toyosaki. It isn't immediately obvious why a role is bolded (though many like to add "Lead roles in bold," which I think is silly.) And I see potential for arguments over whether a role is major or not, and oftentimes it's OR. ~Cheers, TenTonParasol 02:07, 31 December 2012 (UTC)
• Oppose per SMcC. Bolding in running text is too disruptive and vies with the titles for our attention, too. Tony (talk) 02:11, 31 December 2012 (UTC)
• Oppose I can totally see this as WP:OR, having major roles being handpicked by people based on what they think and feel is not a good thing. - Knowledgekid87 (talk) 03:05, 31 December 2012 (UTC)
• Oppose per SMcCandlish. Tdslk (talk) 19:37, 31 December 2012 (UTC)
• Oppose, as (1.) bolding major roles does not make them recognizable as major roles easier (you need to know the code), (2.) I remember a guideline on german WP that says to only put the lemma of an article in bold and not to use bold font for emphasis. Jesus Presley (talk) 11:18, 2 January 2013 (UTC)
• Oppose project specific standards for non-project specific items are bad for the coherence of both encyclopaedia and community. Rich Farmbrough, 02:24, 3 January 2013 (UTC).
  
• Oppose There is no need to modify MOS:BOLD which is sufficiently clear, and aligned with consensus and best practice. The unorthodox manner of emphasizing with boldface, in contravention of mos:bold, is problematic and should be corrected to accord with policy. If it is desired to emphasis these "major roles" with boldface, place them under an appropriate sub-header where boldface is standard. --My76Strat (talk) 19:33, 4 January 2013 (UTC)

A new suggestion (bolding of major roles)

Per the comments above, I have a new suggestion. Should the bolding of major roles be listed in MOS:BOLD as an example of what should not be bolded? As in, should it be stated at MOS:BOLD that "major roles of actors in media should not be bolded, since..." or not? Narutolovehinata5 01:33, 5 January 2013 (UTC)

Possible issues in "Possessives" section

The WP:Manual of Style#Possessives section includes the following, which looks to me like WP:BOLLOCKS: "Some possessives have two possible pronunciations: James's house or James' house..." I'm skeptical that anyone who is a native English speaker, in any dialect/variety, would sound that out as if it read "Jaim's house". I suspect this is a disingenuous ploy by haters of the "James's" construction to make it seem like there are more people in support of "James'" than there really are. I've lived in England, Ireland, both US coasts and the US Southwest, and Canada, and I've never heard anyone do that, with the sole exception of TV preachers who tend to say "Jeeeeezuz", possessive or not, but they theatrically mispronounce all kinds of things, e.g. "God" as "GO-wə-də" in three syllables). — SMcCandlish  Talk⇒ ɖכþ Contrib. 00:00, 31 December 2012 (UTC)

PS: I think it's also a curious that the logic in Chicago Manual of Style is nowhere to be found here: Use the contruction "James's", except for names from antiquity – "Jesus'", "Zeus'". CMS arrived at that clearly because of the widespread influence on both sides of the Atlantic of the King James version of the Bible, which uses that now-archaic construction. I'm not sure I support this distinction, but it's a widely known and followed one (at least in North America, but I would be surprised if no UK style guides mention it). — SMcCandlish  Talk⇒ ɖכþ Contrib. 00:00, 31 December 2012 (UTC)

Here's a James' with the Jaim's pronunciation, at least locally: St James' Park. That maybe also gives an indication where it occurs: when the possessive usage becomes not just common but the only one. When talking about the football stadium or the nearby Metro station, St James Metro station, no-one is thinking of the saint who is the implied possessor of both properties. In such cases the possessive is grammatically correct but largely redundant, so the apostrophe and the pronounced 's' can be dropped without ambiguity.--JohnBlackburne_deeds 00:15, 31 December 2012 (UTC)

I suspected someone might bring up an example like this. It's a poor one, because place names, especially those named after saints and other biblical figures, are handled with a ridiculous level of inconsistency and outright ungrammaticality by modern standards (witness "St James Gate, Dublin", which doesn't even bother with an apostrophe anywhere). They've also been named the way they've been named for centuries in many cases, going back to before there were any standardized grammar and punctuation rules in English. Furthermore, St cases like this in the UK and US derive directly from the KJV biblical writing style (already addressed separately) which always does this, but which dates to 1611 and does not reflect the patterns of Modern English (remember, this is the same Bible that says in Late Middle English that Jesus was an hungred (in Early Modern English that would be "a-hungered", like "Froggy Went a-Courtin'", and today it's "hungry"). — SMcCandlish  Talk⇒ ɖכþ Contrib. 03:14, 31 December 2012 (UTC)

SMcCandlish:

• Pronunciation of those possessives without the added /s/ or /z/ are very well attested, especially in more formal registers – the ones that might be considered in determining encyclopedic usage. I say James's, as you do. But do you say Bill Gates's? Steve Jobs's? John Cassevetes's? See, by the way, our article John Cassavetes, and note the wavering over possessive forms. Note also the absence of discussion to resolve this issue at the talkpage. Question for everyone: How would the issue there be resolved using the current WP:MOS guideline? (My answer? With huge difficulty, or not at all.)
• The "ecclesiastical" pronunciation suggested by Jesus' is established far beyond and before TV evangelists' usage. It's like heav'n and a few other exceptional cases, which are well settled in liturgical use, religious vocal settings, and many more contexts.
• CMOS16's treatment of possessive forms is even worse than their earlier treatments. (Quite an achievement.) They have changed particular decisions without any apparent justification, and they advocate a principle only to rule contrary to that principle a little further on.
• The fundamental question: do we want spelling to follow dominant pronunciations, or not? Those who disregard pronunciation and who like the shorter singular possessive forms for nouns ending in "s" (or "z", or "ce", etc.) must favour boss' over boss's. Butt ugly? I think so. And this must be a rational possessive form for them: anyone else'. (Rules for pronouns and the like that take an apostrophe in their possessive forms are the same as the rules for nouns.) Those who disregard pronunciation and who like the longer forms must favour Davies's over Davies', along with the singular possessive forms congeries's, Piscies's, molasses's, species's, and series's. If we aim for natural use of language, acceptable and understandable to all readers, disregarding pronunciation doesn't cut it.
• I think the possessives section is seriously flawed, in the ways I hint at above. I did my best for it a few years back. The stupid three-practice approach is almost useless, and can resolve almost nothing.
• Good luck!

Noetica 02:26, 31 December 2012 (UTC)

The -'s possessive tends to be used with animate nouns, which may be why molasses's, species's, and series's sound so odd. — kwami (talk) 02:48, 31 December 2012 (UTC)

Agreed, but they don't look odd, except perhaps to someone who cannot read but by sounding things out, syllable by syllable, in their heads. I honestly don't think that MOS needs to care about that condition. Anyone who is like that is already entirely used to possessives not looking the way they'd prefer them to look. It's not something we rationally can, or should attempt to, compensate for. It's not a legit accessibility issue at all. This is a written medium, and "molasses's" is the normal, globally-recognized way to form the plural of "molasses" in written English, even if some people would quirkily write it as "molasses'". There is not a single competent reader of the English language who will not instantly understand the proper, unambiguous, standard spelling "molasses's". This is emphatically not an ENGVAR issue, it's just convenient for fans of the truncated, sub-standard style to pretend that it is. — SMcCandlish  Talk⇒ ɖכþ Contrib. 03:06, 31 December 2012 (UTC)

Noetica: Yes, I do say "Bill Gates's", etc., with a pronunciation like "bil GAYTsəz" (3 syllables total); enunciating the possessive clearly is often important to conveying meaning correctly. I remain highly skeptical that this "drop pronunciation of the possessive" thing, to the extent it exists in the real world, is anything but a fey affectation. I've lived in too many places and I watch/listen to too much media from too many places around the world to believe that a non-trivial percentage of people would consider it especially "encyclopedic" rather than a dialectal quirk, like pronouncing "Texas" as "Texez" or "Manchester" as "Manjezdah". WP does not need to account for vagaries of spoken accents like this, especially not with grossly ambiguous written punctuation changes. People who would actually say "Bill Gates'" are not morons and know full well what "Bill Gates's" means and when they read it aloud they'll pronounce it as "Bill Gates'" the way they always do. They don't somehow rate their own version of English with different punctuation rules! I agree that people who would write "Jones'" for "Jones's" would logically have to write "boss'" for "boss's" and "else'" for "else's", but they don't, generally (and most editors would correct them if they did), which points out that it's not really a rational position to take. That said, I do not agree that this is "the fundamental question". It really has nothing to do with sounding out, except maybe on the Simple English Misplaced Pages. This is a written medium and needs to reflect that in our prose. "Jones'" is not semantically equivalent to "Jones's"; the former is a plural possessive referring to two or more parties called "Jone". That is the real issue. And it's not trivial. It can seem silly with most names that native English speakers recognize, but both "William" and "Williams" are valid British surnames, and the issue gets thick fast with foreign names (e.g. Macia and Macias are both valid surnames in Spanish, among many similar examples). The truncated usage is substandard and confusing. There are only limited conventional exceptions, like "men's", "oxen's", "bacteria's" and "children's", and they're all based on irregular plurals from Anglo-Saxon, Latin, etc. I agree that the current 3-prong approach is pointless. We need to standardize on "Jones's", for basic logic and unambiguous parseability reasons, and maybe allow for the "names from antiquity" exception, to keep KJV fans from blowing a gasket about their favored "Jesus'" construction. I'd actually rather see it limited to biblical names, and in the context of Anglican/CoE and related Protestantism specifically, not antiquity or even Christianity generally (this would permit "Moses'", in Protestantism but not Catholicism or Judaism articles, and not "Zeus'" anywhere). PS: I agree that CMoS 16th ed. badly needs to be replaced immediately with a corrected 17th ed., and I rely on the 15th because it doesn't contradict itself as much. I'm kind of pissed off that I can't get a refund for ed. 16 or a coupon to get ed. 17 for free or a steep discount. — SMcCandlish  Talk⇒ ɖכþ Contrib. 03:00, 31 December 2012 (UTC)

I made some related comments in previous discussions.

• Misplaced Pages talk:Manual of Style/Archive 125#Possessive apostrophes (section 28; August 2011)
• Misplaced Pages talk:Manual of Style/Archive 108#Recent changes to the "Possessives" section (section 112; August 2009)
  • especially Misplaced Pages talk:Manual of Style/Archive 108#Let's start anew and solve this? (section 112, subsection 1; August 2009)

—Wavelength (talk) 17:49, 31 December 2012 (UTC)

• Go with Chicago pending something better coming up. --John (talk) 08:19, 31 December 2012 (UTC)

• I hear a one-syllable "James'", and I don't think it's an affectation. I would hesitate to say what the dominant pronunciation is. So many rules are in use, and so many people are sure their favorite rule is the only correct one, that I'd say we should allow either form for all singular words ending in the letter S, with standardization in individual articles depending on the first use or the majority use at the time the question is addressed. The only rule I'd favor for singular nouns is that those that don't end in "s" get an apostrophe-s. ("He borrowed Max's tie for appearance's sake.") —JerryFriedman (Talk) 17:12, 1 January 2013 (UTC)

I think this is the most practical suggestion and the one least likely to lead to edit wars. Peter coxhead (talk) 17:15, 1 January 2013 (UTC)

Again, it does not matter what someone's favored pronunciation is. Written English is not tied strongly to spoken English or thousands of words would have different spellings. It's important in encyclopedic prose to be very clear about possessives and plurality, and the only way to do that is to recognize that "Macias'" and "Williams'" are not equivalent to or substitutable for "Macias's" and "Williams's", respectively. It would be better for a few edit wars to break out and the issue turn into another RfC or whatever until people got the point, like the do about everything MOSish, from date linking to logical quotation, than for us to continue using a substandard and ambiguous written style that randomly apes people's conversational speech for no encyclopedic reason. Writing it in a way that prevents confusion is not tantamount to telling people how to pronounce it, any more than spelling a word as "heroic" is telling people from a silent-initial-h dialect that they have to pronounce the "h". In other words, I'm strongly arguing that where MOS says that basing the spelling on your favored pronunciation is okay, it needs to stop saying that and favor the clearest standard. This is the same logic we bring to most issues here. — SMcCandlish  Talk⇒ ɖכþ Contrib. 21:22, 1 January 2013 (UTC)

I tend to agree. I've always done it according to CMOS (use the 's except for special cases like Jesus'); some guides allow more flexibility, especially for the multisyllabic names like Williams', but that always seemed painfully wrong to me. We had a big argument at the Steve Jobs article, where the monosyllabic Jobs's should have been a no-brainer, but several editors who misremembered what they had been taught in school couldn't believe one could ever use 's after an s. To leave the article styling up to such illiterates seems like a bad idea. The point is, though variations are allowed by some styles and guides, it makes sense in encyclopedic writing to use the more rigorously clear and precise style. Dicklyon (talk) 21:44, 1 January 2013 (UTC)

Exactly. — SMcCandlish  Talk⇒ ɖכþ Contrib. 01:52, 2 January 2013 (UTC)

Calling people who use a different style "illiterates" is not helpful, although respectful debates seem all too rare here. Peter coxhead (talk) 21:53, 1 January 2013 (UTC)

My illiterates was not in reference to people who use a different style, but rather to people who misremember the basics of English grammar that they were taught in school. Comments like this one and this one exhibit the degree of illiteracy based on faulty memory of teachings that I'm talking about. They claim they were taught something about possessives that there is no evidence of anyone ever teaching. I've encountered a lot of this particular illiteracy; or maybe something like agrammaracy would be a better term for it. Dicklyon (talk) 23:27, 1 January 2013 (UTC)

A quick Google search found several pages which advise against "s's", so it's quite conceivable that some people are taught this "rule". But even if people have misremembered and are mistaken, calling them "illiterates" is unnecessary. Peter coxhead (talk) 23:55, 1 January 2013 (UTC)

So? MOS regularly picks one of several options that various style guides recommend and doesn't offer all of them. This case is not special, and there's a real reason I've iterated several times already that it's important to do so here. — SMcCandlish  Talk⇒ ɖכþ Contrib. 01:52, 2 January 2013 (UTC)

@SMcCandlish: I never mentioned pronunciation, which is a red herring. We had this discussion at Linnaeus. In that case the Google n-gram shows that "Linnaeus' " and "Linnaeus's" are about equally common, with a tendency since 1900 to favour the former. Misplaced Pages can decide to use one form rather than another, but since both are common in written English, I predict it will just cause unnecessary edit wars. Both styles are clear; specifying anything other than consistency within an article is just another form of instruction creep. Peter coxhead (talk) 21:53, 1 January 2013 (UTC)

If you think it's just instruction creep, you have not been following my actual reasoning. You definitely did mention pronounciation, at #pcpron. But I did not say you personally had brought up pronunciation, anyway; it has simply been a consistent theme throughout the debate every time the possessives issue comes up, and I'm specifically addressing the wishy-washy "do whatever you feel like" #3 option presently in MOS's text for no real reason. MOS quite regularly takes one of multiple options, often not even the majority one, and insists on it when there's a consistency, clarity, logic, parseability, disambiguation or factuality reason to do so, as there is in this case. This is actually important: "the Williams'" and "the Williams's" have a different meaning, and this will always be the case for any name (or whatever) with a viable form without the plural (or sometimes just plural-looking) -s. Since the average reader is not a human Misplaced Pages, they cannot be expected to know for certain whether any form "Xs" is a also valid without the s, WP obviously should not ever use "Xs'" to mean "Xs's", even if some editors would prefer to because of they way they would pronounce it when read aloud. This seems like crystal clear reasoning to me. What fault are you finding with it? — SMcCandlish  Talk⇒ ɖכþ Contrib. 01:52, 2 January 2013 (UTC)

The last time we discussed this, in Oct. 2011 at Misplaced Pages talk:Manual of Style/Archive 126#MOS:POSS broken, the discussion devolved to disagreement on what pronunciations sound better. Apparently this carries more weight than the best grammar and usage guides do. Dicklyon (talk) 00:22, 2 January 2013 (UTC)

As I've labored to illustrate here, this pronunciation thing is the real red herring, and is ultimately completely irrelevant to what MOS should recommend we do with possessives in writing. — SMcCandlish  Talk⇒ ɖכþ Contrib. 01:52, 2 January 2013 (UTC)

• Both forms are acceptable, except with names such as Jesus and Moses, where the apostrophe alone should be used. The question of whether we should select one style, and if so which is not one I would swish to express a preference on. Rich Farmbrough, 03:09, 3 January 2013 (UTC).
  

Proposal to restore and improve "Passive voice" section

I propose that the "Passive voice" section be restored, immediately below the WP:Manual of Style#Grammar heading, where it was originally. The deleted wording read:

Passive voice

Whether to use the passive voice (this was done) or the active (he did this) depends entirely on the context, and is left to the discretion of editors.

It's been demonstrated above, and in previous discussions, that people changing passive to active willy-nilly is a genuine problem.

I further and severably propose that this be expanded and clarified as follows:

Passive voice

Whether to use the passive voice (this was done) or the active (he did this) depends entirely on the context, and is left to the discretion of editors. Incautiously changing passive to active voice can introduce verifiability, original research and neutrality problems, by implying causality or action where we do not have reliable sources for it. While encyclopedic writing often sometimes requires the use of passive voice, it should not be used to mask causation where it is reliably sourced, another neutrality issue. Passive voice may also safely be replaced when the facts are sourced and the construction is simply awkward: The Lord of the Rings was written by J. R. R. Tolkien is usually better as J. R. R. Tolkien wrote The Lord of the Rings.

— SMcCandlish  Talk⇒ ɖכþ Contrib. 00:21, 31 December 2012 (UTC)

Note: I concede the criticism below that adding specific examples like the Tolkien one (which could be replaced with anything; The Hobbit film was just fresh in my mind) may not be helpful, so it could be removed. I've struck it.— SMcCandlish  Talk⇒ ɖכþ Contrib. 03:46, 31 December 2012 (UTC)

I also moderated "often" to "sometimes" to mollify a concern (about "encouraging" passive voice) raised in the original thread above. — SMcCandlish  Talk⇒ ɖכþ Contrib. 05:40, 31 December 2012 (UTC)

• Oppose Rather as I conceded higher up this page that my suggested rephrasing of the rules on linking within quotes, which amounted to "If you link within quotes, follow good practice for linking anywhere else" could easily be substituted by removal of the text altogether, so here the proposal seems to be replacing nothing with "You can choose A or B, but choose well." Bad writing is bad writing, and should be edited because it is bad writing, not because it is in the passive or active voice. This is a manual of style, not a grammar text book: this seems to be legislation for common sense in the absence of a house style, not identification of a house style

  Apart from anything else, if the main subject of a passage is Tolkien, or authorship, then it could very easily be more appropriate to write your example in the active voice. Given that the choice between active and passive is generally dependent on the wider context, selecting any example will be fraught with complexities. Kevin McE (talk) 00:44, 31 December 2012 (UTC)

  It's not the same kind of case, though. Here, there are specific reasons to use passive voice sometimes (e.g. lack of a reliable source for the alleged agency/action/cause). MOS, like all style guides, is also in part a grammar guide. That's why there's a section called WP:Manual of Style#Grammar. Characterizing this as "legislation" is non-responsive to anything relevant; every single point in MOS could be pejoratively labeled as such. Of course it would be more appropriate to write my Tolkien example in the active voice; that's precisely what I said. :-) You may be right, though, that giving specific examples isn't helpful. — SMcCandlish  Talk⇒ ɖכþ Contrib. 03:44, 31 December 2012 (UTC)

• Support the short version (if we need anything at all) but oppose the long version, as an incorrect understanding of what the passive does. — kwami (talk) 02:43, 31 December 2012 (UTC)

  "Incorrect" in what sense? I did not write anything at all about the function of the passive, only about the hazards of imposing the active without a source that supports the implications it brings with it. — SMcCandlish  Talk⇒ ɖכþ Contrib. 03:50, 31 December 2012 (UTC)

You said quite a bit, actually: that the passive is used to mask causality and that it is awkward, both myths. The active can just as easily be used to mask causality, and can be just as awkward. Such things have little to do with voice. By mentioning them, we'd give credence to them. It'd be like saying that, although ending a clause with a preposition is ungrammatical, sometimes it's necessary. — kwami (talk) 07:44, 31 December 2012 (UTC)

Masking causality: Consider the sentence "Taxes were raised." In the U.S. at least, people will want to know WHO raised taxes. But whether this is a bug or a feature of the passive is a matter of value judgment. Neotarf (talk) 08:13, 1 January 2013 (UTC)

It's simply a fact about passive vs. active voice, not a "value judgment". Sometimes the causality-establishing active voice is appropriate (when we have reliable facts to support it) and sometimes it isn't (when we don't). — SMcCandlish  Talk⇒ ɖכþ Contrib. 21:47, 1 January 2013 (UTC)

Kwami, I did not say either of those things. I said that editors can use active voice to imply causality without a source for it, with is true, and which is nothing like saying that masking causality is the function of passive voice. I also said that passive constructions can be awkward (I've already given the canonical "up with which I will not put" example), which is a true statement. Please stop throwing blatant straw man arguments at me. I know you know better. — SMcCandlish  Talk⇒ ɖכþ Contrib. 21:46, 1 January 2013 (UTC)

• Oppose as a matter outwith the remit of the MoS. Good writers tend to use the active voice more than the passive but this cannot be mandated and is best left to high school teachers, literacy coaches and peer reviewers. --John (talk) 07:58, 31 December 2012 (UTC)
• Oppose. The correct use of passive depends neither on context nor on editorial whim. There are specific situations where the passive is the most correct usage, notably where the doer of the action is either not known or not important. Your high school coach and your third grade teacher are unlikely to have given you any useful information about passive: such things are not being taught to those responsible for teaching grammar, and anyway, teachers the world over just follow whatever textbook is chosen by the school district or administration. Linguists have done enough bellyaching about ignorance of the passive, but until someone addresses the issue of education on a meaningful level, WP will be left trying to educate people willy-nilly, with spotty results. Neotarf (talk) 08:07, 1 January 2013 (UTC)

There are school districts and administrations the world over that dictate which textbook must be used??? You have evidence for this??? Kevin McE (talk) 15:17, 1 January 2013 (UTC)

Wise words, Neotarf (such as many have come to expect from you). Still, I say that context can be relevant. Agency may be less important in scientific articles, and more important in historical or biographical articles. Contrast two sentences: "The synthesis is accelerated under pressure in the presence of certain metallic catalysts." "Napoleon struggled to quash the rebellion, and eventually succeeded." Passive is better in the first, but active is better in the second. And I think no one has suggested that "editorial whim" should be in play. Let's distinguish whim and discretion. Noetica 08:28, 1 January 2013 (UTC)

Let's not distinguish at all, this is a matter of grammar, not style. Anyone who wants to go further with the grammar can look it up in their university composition handbook....you know, the big thick expensive one that no one buys once they find out it's not covered in the syllabus.... Neotarf (talk) 08:45, 1 January 2013 (UTC)

Not quite sure I follow. No one disputes, as far as I know, that both active voice and passive voice are correct grammar. As I understand it, SMcC would like to say more about which one might be better style, in what circumstances. I agree with you, if I've understood the positions expressed (which is not certain as I haven't spent much time trying to make sure), that it's probably not useful to do so. But I don't understand what you mean by it being a matter of grammar. --Trovatore (talk) 09:02, 1 January 2013 (UTC)

Trovatore, see the above section on "Edit warring over passive voice". Neotarf (talk) 09:23, 1 January 2013 (UTC)

Can't find anything relevant. Let me put my point this way: Someone could say, "some producer produced West Side Story, for the first time anyone produced it, in New York". That would be entirely in active voice, and it would be terrible style, but it would be correct grammar, in the sense that no linguist would be tempted to put an asterisk in front of it. --Trovatore (talk) 09:33, 1 January 2013 (UTC)

I would. There are levels of grammar beyond the clause. (I'd like to say, 'see discourse analysis' at this point, but that article is undeveloped.) There are seldom absolute 'rules' at this level, but there are strong grammatical tendencies, and ignoring these results in awkward or incoherent text. (Such things are called "style" by those who do not recognize that grammar operates here.) One of them, as Jerry notes below, is that the topic, which ties the text together, threads its way through the text as the subject of subsequent clauses. When the topic is the semantic agent, we use active voice; when the patient (object role), we use passive voice. This actually is the definition of "subject" among linguists who work on grammar at the discourse level. Thus the grammatical subject should reflect the topic of the text. Using active clauses where the passive would be natural is an ungrammatical use of the subject. (Such linguists are unlikely to put a star before your sentence mainly because once you start working with actual language, such artificial exercises seem silly.) It is true that in "active" texts like dime-store Westerns, which tend to be about people and other animate things, most clauses are active, because active things tend to be agents rather than patients. (This may well be the historical origin of subjects in languages which have them: People tend to talk about people doing things.) However, the opposite is true in many scientific publications, where one is studying inactive things, or reporting on what has been done to otherwise active things. In such cases the passive is often more appropriate. (There's also an entrenched stylistic preference for researchers to never refer to themselves in the first person, as if they were objective observers rather than active participants, and this ups the number of passive clauses considerably, but IMO that's just as silly as the highschool-English idea that passive clauses are 'weak' or 'unaccountable'. And indeed I've started seeing more academic text acknowledging the obvious by using the first person where a normal person would.) — kwami (talk) 17:30, 1 January 2013 (UTC)

The phraseology these days tends to be "One of us (Pierson) had earlier established...." which I find unexceptional. But I agree a lot of the tension is between people who learned from Micorsoft's grammar checker, and the fact that we are writing entirely the type of work which benefits from widespread passivation. Rich Farmbrough, 04:08, 3 January 2013 (UTC).

• Comment: In addition to suppressing the agent (because it's unknown or unimportant or obvious or one wants to hide it), the other main use of the passive voice is to make the patient (grammar) the subject of the sentence because it's the topic in the linguistic sense, and in English the topic is typically the subject and typically goes early in the clause. —JerryFriedman (Talk) 16:16, 1 January 2013 (UTC)

Exactly. There are solid reasons for using passive over active. The proposed language makes it sound like you can toss a coin. There is plenty of consensus that WP needs to educate editors about this subject, rather than dealing with the issue on an individual basis over and over. The only question remaining is whether it belongs in MOS. Has anyone written a useful essay about it? Neotarf (talk) 02:26, 2 January 2013 (UTC)

• Return to proposal The original proposal was in two parts: (1) return to having some comment on the use of the passive (2) expand the comment, e.g. based on SMcCandlish's text. There does not seem to be a consensus for (2). However, there does seem to be a consensus for (1). There is, in my experience, a genuine problem with some copy-editors changing passives unnecessarily. I strongly support putting back something like:

Passive voice

Whether to use the passive voice (The Adventures of Tom Sawyer was written by Mark Twain) or the active (Mark Twain wrote The Adventures of Tom Sawyer) depends entirely on the context, and is left to the discretion of editors. Changes should not be made merely because of a general preference for one over the other.

Could we agree on this? Peter coxhead (talk) 17:12, 1 January 2013 (UTC)

Support. That addresses both the knee-jerk opposition to passives and the academic over-preference for passives. Though I'd remove the word 'entirely' as unhelpful. — kwami (talk) 17:44, 1 January 2013 (UTC)

Agreed re "entirely". Peter coxhead (talk) 18:43, 1 January 2013 (UTC)

Support, per Kwami and Peter. However, I would add something like "categoric" or "general" before "preference"; in any given instance, whether to use passive or active is going to be an in situ "preferences for one over the other", so the wording here isn't clear. — SMcCandlish  Talk⇒ ɖכþ Contrib. 21:40, 1 January 2013 (UTC)

Yes, "general" clarifies. Peter coxhead (talk) 22:52, 1 January 2013 (UTC)

No, the main issue of educating editors has not been addressed. There are reasons other than "preference" for making active/passive choices. Given the perennial confusion on the subject, this language is not nearly explicit enough. Why gloss over it or dumb it down. Neotarf (talk) 02:35, 2 January 2013 (UTC)

It's not a question of dumbing down, it's a question of succinctness. The MoS is over long already. Rich Farmbrough, 04:08, 3 January 2013 (UTC).

• I am sorry, I still think it is a terrible (if well-intentioned) idea. --John (talk) 19:53, 4 January 2013 (UTC)

The trunk (boot) of a car

At present the MOS gives the following example: "the trunk (UK: boot) of the car was ...".

The term "boot" for the luggage compartment of a motor car is also used in Australia, so it's not an exclusively British term. In addition, I would think that the confusion about usage would be more likely to go the other way. I therefore propose to change the example this way:

• the boot (trunk) of the car was ...

How do other editors feel about this proposal? Michael Glass (talk) 03:16, 31 December 2012 (UTC)

I would just drop the "UK: " part. There's no compelling reason to invert the order. (I would say that if the original order had been what you propose and someone wanted to flip it; it really doesn't matter what order these ENGVAR things go in). — SMcCandlish  Talk⇒ ɖכþ Contrib. 03:48, 31 December 2012 (UTC)

Based on ENGVAR, surely the version in main prose should be the version as determined by WP:TIES or WP:RETAIN, and the alternative is bracketed. In the interests of retaining natural uninterrupted prose, I would rather see the referent linked so that users of another version can check the meaning if they are uncertain. While I acknowledge the principle behind WP:overlink, it is far less intrusive to the readers' experience to come across blue text than bracketed insertions, and if the linked term is familiar (ie, the reader is conversant with the ENGVAR in which the article is written) it is an easy choice not to follow the link. Kevin McE (talk) 12:04, 31 December 2012 (UTC)

It's a toss-up between WP:EGG and WP:ENGVAR. I remember this being a problem at Concorde; seemingly some American editors could not stand seeing tyre unless it was linked as tyre. --John (talk) 12:16, 31 December 2012 (UTC)

Yeah, "UK" is distracting. Better just trunk (boot) or boot (trunk). As for linking tyre, it's overlinking per WP:NOTADICT. — kwami (talk) 03:18, 1 January 2013 (UTC)

OK. I'll drop the 'UK' Michael Glass (talk) 13:29, 1 January 2013 (UTC)

Foreign-language quotations

MOS:QUOTE currently says that foreign-language quotations should appear in translation. It's not clear to me how this should work in practice. Who should do the translation? What I suggest is:

• If a reliable source has published an English translation of the foreign quotation, then we can use it.
• If the quotation is only published in its original (or other foreign) language, then we must not directly quote it, but we can explain what was said outside of quotes. So Pierre a dit "J'aime le fromage" could be written as Pierre said that he liked cheese but not as Pierre said "I like cheese".
• We must not use Google Translate (or similar) to create a quotable English-language translation. These automatic translators are not usually accurate enough.
• I'm not sure whether we can allow Wikipedians who fluently speak both English and the quoted language to produce their own quotable translations.

Does this seem sensible? What do you think about the fourth point? Thanks, Bazonka (talk) 10:32, 1 January 2013 (UTC)

• In practice the fourth point is often used, as we shouldn't expect every foreign-language quote to have been translated in a secondary source. — Crisco 1492 (talk) 10:45, 1 January 2013 (UTC)

As for how it can stay reliable and not OR: provide the original as well, as a footnote. See, for example, the FAs Sudirman and Albertus Soegijapranata. — Crisco 1492 (talk) 10:47, 1 January 2013 (UTC)

That's fine, but sometimes the third point is used instead, which is often dreadful. I think the guidelines about this need to be clarified. Bazonka (talk) 11:14, 1 January 2013 (UTC)

I am in favour of permiting "Pierre said "J'aime le fromage" where apppropriate. Martinvl (talk) 11:30, 1 January 2013 (UTC)

I think in that case the quoted foreign text would need to be very short, and also in the language that was actually used. Bazonka (talk) 11:41, 1 January 2013 (UTC)

I agree. How about this Afrikaans phrase "Ek het met my neef samm geloop" - the Afrikaans word "neef" can mean either "male cousin" or "nephew". Martinvl (talk) 11:53, 1 January 2013 (UTC)

• Wouldn't it have to be clear from context in that case? — Crisco 1492 (talk) 13:23, 1 January 2013 (UTC)

There's a possible conflict between our desire to use sourced translations and our desire to respect the translator's copyright. Also, when the original is under copyright, I believe translation is a separate issue from quotation, and I have no idea whether the same fair-use guidelines apply to both. I don't remember any WP guidelines on these subjects—which isn't to say that I've looked everywhere. Despite the fourth point above, I've felt free to translate myself and to improve others' translations where I'm confident (and to let improvements to my translations stand). I've put the original in a footnote, as Crisco 1492 mentions. —JerryFriedman (Talk) 16:42, 1 January 2013 (UTC)

I don't see how copyright is a problem. As long as we reference the translation, then it's no different from quoting any other English-language text. Or if a Wikipedian has done the translation, then Creative Commons applies. Bazonka (talk) 17:18, 1 January 2013 (UTC)

No, it wouldn't, because the translation is a derivative work. You can't impose CC or GPL on a work derived from another work not subject to such a license. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:02, 1 January 2013 (UTC)

But an English-language quotation can often be included per WP:FUC, as long as it is properly referenced. So surely a translation can also be included as long as we reference a) the source we have taken the translated text from, or b) the source of the original untranslated text that we have ourselves translated. Bazonka (talk) 22:12, 1 January 2013 (UTC)

After looking into this a bit further... it would seem that fair use does apply to derivative works. So if we can include a quote (under fair use), then we can include a translation of the quote. Bazonka (talk) 22:22, 1 January 2013 (UTC)

Yes, of course. I was just addressing the legal issue; you can't translate something, like a non-English song, subject to someone else's all-rights-reserved copyright, then publish that derivative work under CC or GFDL. Material quoted (translated or not) per fair use is not problematic in a WP article covered by CC/GFDL, since it's just a small portion and isn't independent of the article; i.e., it's not a stand-alone derived work, just fair use of a portion of a work for "criticism and commentary", etc. Overquotation of large swaths of a work is forbidden on WP because it would not qualify as fair use. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:26, 1 January 2013 (UTC)

Hmm, I'm not a lawyer, but my guess would be that you can apply CC or GFDL to such a derivative work, and the license would then bind whatever copyright interest you have in the derivative work, but would not of course encumber that of the original copyright holder. So if someone makes a second derivative work from yours, and distributes it subject to the terms of your free license, he is protected against any action on your part, but will still have to gain permission from the original copyright holder, or argue fair use, or hope not to be sued, or.... But as I say I'm not a lawyer. --Trovatore (talk) 22:32, 1 January 2013 (UTC)

You can't legally publish a derivative work without the original copyright holder's permission at all, generally, so you would not be able to release your derivative under a CCL (GFDL, whatever) unless the original copyright holder agreed (which is tantamount to them changing their own license to you to a CCL). There are always fair use exceptions for reproducing portions of works, or even entireties of very short works, and the music industry has carved out its own extralegal "sample clearances" system, and so forth – real life is usually more complicated than any generality. But if I publish a poem, all rights reserved, and you adapt it into a song and then publish that, even with credit, I could sue you for copyright infringement, regardless what license you slapped on your derivative adaptation. Hope that's clearer. — SMcCandlish  Talk⇒ ɖכþ Contrib. 02:25, 2 January 2013 (UTC)

You can "legally" publish it and see if you get sued. If you don't get sued, it's not illegal. (Not clear that it's "illegal" in any event — the copyright holder may have a cause of action against you, but that's not quite the same thing.) Caveat: There is theoretically such a thing as criminal copyright infringement, but it doesn't seem to come up much and I doubt it's relevant here. --Trovatore (talk) 02:10, 2 January 2013 (UTC)

This is getting rather off-topic for MOS, I guess, so I won't go into more detail after this. Getting away with it doesn't make it legal or lawful, it just means you didn't get caught or sued. Note also that the copyright holder has plenty of time to bring suit. If your garage band puts out a self-produced CD and folds a year later, you probably would not get sued for adapting someone's poem into a song, because the cost of the suit would probably outweigh any damages that could actually be collected in real life. If your single was a huge hit, you'd almost certainly be sued, for all the profits from it and for punitive damages. You're correct that it's not a matter of being illegal in the case of a civil suit; the term is unlawful. Criminal copyright is not "theoretical" at all, comes up quite a lot with regards to digital media, and is relevant. It's simply unlikely that a prosecutor would actually take action on a trivial case like this, vs. going after something like ThePirateBay.org in response to entertainment industry pressure. (PS: I am also not a lawyer, but I have a professional level of experience with intellectual property law and policy. I was a digital IP and civil liberties policy analyst, among other roles, for nine years at the Electronic Frontier Foundation, a nonprofit law firm and public-interest advocacy organization, specializing in Internet and digital media law. While that doesn't magically make me correct about everything that wanders into that topic-space, I'm not guessing or making assumptions of any kind here. I'm writing from direct knowledge of this field from having worked sided-by-side with, and interpreted for public consumption the output of, some of the best legal minds in this area – ones whose specific focus, to boot, was maximizing the "you can do this" not "you can't do this" interpretation of the relevant laws.) — SMcCandlish  Talk⇒ ɖכþ Contrib. 02:25, 2 January 2013 (UTC)

Moving on from the copyright question, which I think is really just a side-issue, I propose the following replacement for the current foreign-language quotations text:

Foreign-language quotations

Quotations of words originally written or spoken in a foreign language should normally appear translated into English. Where a reliable source is available that contains such a translation (and it was not first published within Misplaced Pages), it should be cited, with an indication of the original language (if that is not clear from the context).

Where no translation is already available, a Wikipedian who is fluent in both English and the foreign language may translate the text, and include this translation with a reference to the original wording (which may also be included in a footnote), indicating the original language.

Short foreign-language passages or statements can be included, followed by the English translation in square brackets.

It is not appropriate to directly quote translations created by automatic translation software (such as Google Translate) because these are often inaccurate or not of adequate quality. Similarly, quoting a translation of a translation should be avoided. In these cases, if it is not possible to give a professional translation, indirect quotations could be used, paraphrasing the wording without using quotation marks. For example, Pierre a dit, "J'aime le fromage" can be given as Pierre said that he liked cheese.

What do you think? Bazonka (talk) 20:54, 2 January 2013 (UTC)

I'm a little wary on this. The appropriate degree of caution is dependent on context. "Nyet! Nyet! Nyet!" for example can be readily translated by people fluent in neither English nor Russian, and also by google. Some years ago I had to work with a paper written in French - my French is terrible, but I translated it well, because I knew the subject matter. Rich Farmbrough, 04:25, 3 January 2013 (UTC).

I've had similar experiences, and given enough time can handle almost any Germanic or Romanance language. E.g., I translated the article Five-pins from its Italian equivalent, and even went directly to the Italian and Spanish sources for more material to improve the article beyond the translation; I've never studied Italian at all. — SMcCandlish  Talk⇒ ɖכþ Contrib. 04:33, 3 January 2013 (UTC)

I share Rich Farmbrough's concern, and would add one: We need not mandate order and formatting. Sometimes it makes more sense to give the English first, the foreign later. Many, including linguists, prefer to use 'single quotes' for glosses, and even aside from that there is no reason to mandate square brackets in particular. Maybe give them as an example of one way to format a gloss, but give single quotes, too, which is the standard in linguistics as I've mentioned here before. MOS needs to at least explicitly permit it if not recommend it outright. For large blocks, I wouldn't use either, I'd simply use blockquote and introduced each paragraph, e.g. "In Dante's original period Italian:...", and "A liberal English translation renders this:..." — SMcCandlish  Talk⇒ ɖכþ Contrib. 04:33, 3 January 2013 (UTC)

What would a sample good format look like? Here is a real life example: This edit is not correct, and I will have to do something with it, because a "whiskería" is literally an establishment that serves whiskey; they don't call it a brothel because brothels are illegal in Argentina, hence the euphemism.

The search was given another lead when the alleged madame of a whiskería (a term used to describe undercover brothels), called Lidia Medina, was heard to say, "Those fools are looking for her, and she's in Spain."

I don't want to do a simple revert, because it's evident from the edit that the current wording can be misunderstood. Neither do I want to make it so wordy that it disrupts the flow of the text. (This is my own translation, based on information from an Argentinian native speaker.) Brackets, yes, and they will need some kind of special markup, yes? Are there a couple of sample formats, to see how others have handled this?

Neotarf (talk) 06:18, 3 January 2013 (UTC)

Here are some formats I have used. For text within the article:

The Telefé series Vidas Robadas ("Stolen Lives") was inspired by this case.

For a translation of one of the foreign language references:

"Marita Verón, a 10 años de su secuestro y desaparición", TN, Martes 3 de Abril del 2012

Neotarf (talk) 06:40, 3 January 2013 (UTC)

As far as the wording about "indicating the original language", if the entire article is a translation, the original language would appear on the talk page.

Neotarf (talk) 06:54, 3 January 2013 (UTC)

I'd leave out "Translation" in the reference above.

I don't agree with Bazonka that the copyright is a side issue. Long copyrighted translations are clearly a violation of our copyright policy, so the MOS can't reflect them. Short copyrighted translations seem to be accepted as fair use under the current policy—there could be an interesting argument about that somewhere else.

I'd say there are two questions here: how foreign-language quotations should be presented, and if translations are used, whether they should be sourced or made here (or both). The first is appropriate for the MOS; I'm not sure the second is, but others here will know the answer to that.

Here's a possible revision of Bazonka's proposal:

Foreign-language quotations

Quotations of words originally written or spoken in a foreign language should normally appear translated into English. They may be followed by the original in the text or in a footnote or in square brackets inside the quotation marks. For instance,

According to Suetonius, when Augustus heard the news he cried, "Quintilius Varus, give back the legions! "

When the original is in a script other than the Roman alphabet, a romanized version should usually be given in addition or instead. The original of Biblical quotations is seldom given unless the quotation is the subject of discussion.

Short foreign-language passages or statements can be included, followed by the English translation, possibly in square brackets or parentheses (round brackets). One might want to use this method if the original is known to many English speakers, or if the article discusses some feature of it that doesn't appear in the translation (such as wordplay), among other reasons. In linguistics, the translation is usually given in single quotation marks.

Foreign words and phrases in English-language quotations should usually be left as they are. Unless they're very well known to English speakers, they should be translated immediately afterwards in square brackets. Any explanation may be added in the brackets or a footnote.

When words in a third language appear in foreign quotations, they should be treated the same way. For instance,

In Spain every traveler who does not lug around samples of calico or silk passes for an Englishman, Inglesito. It is the same in the East. At Chalcis I have had the honor of being introduced as a Μιλόρδος Φραντζέσος ." (Prosper Mérimée, "Carmen", translated by Louise Guiney.)

The original of this is probably too long to be given in the text but might appear in a footnote.

As always, an editor thinking of including a quotation must decide whether to replace it with a paraphrase. If the fact that the quotation is in a foreign language introduces many complications and causes difficulties for readers, that is a reason to prefer a paraphrase.

I'm not sure what to say when the original contains an English word or phrase. —JerryFriedman (Talk) 18:47, 5 January 2013 (UTC)

Application of MOS:COMMONALITY to the MOS page itself

Per MOS:COMMONALITY I changed the word "favor" (which is US spelling) to "prefer" throughout Misplaced Pages:Manual of Style. User:Noetica then reverted this stating: no improvement: "favor" is more accurate, and at least one substitution (in an example) is decidedly unidiomatic. I concede that perhaps a better word than "prefer" could perhaps have been used in some cases, but still think that the change was mostly an improvement. To me, "favor" seems at first glance to be a spelling mistake and therefore the text is not as easily readable as it should be. Surely MOS should practice what it preaches, and should adhere to the commonality guidelines. Bazonka (talk) 11:11, 1 January 2013 (UTC)

Indeed it should conform to itself, Bazonka. But that does not mean it should use a less accurate word simply because the spelling of the better word looks odd to some people. "Favor" looks strange to me too, as an Australian; but WP:MOS happens to be written with US spelling, and with the US-preferred em dash. But your interest in MOS is appreciated, I'm sure. The more editors involved and contributing to its development, the better. ☺ Noetica 11:44, 1 January 2013 (UTC)

I know that MOS is written in US spelling. However, the intention of MOS:COMMONALITY is not to stop articles from being written in one particular variety of English, but to reduce the impact of it. (You'll note that I did not attempt to change "color" to a common term, such as "hue", because this would obviously have been less clear.) But I fail to understand how "prefer" is less accurate than "favor"; Wiktionary defines Wikt:favor as "To look upon fondly; to prefer", and Wikt:prefer as "To be in the habit of choosing something rather than something else; to favor; to like better", so the two words seem to be synonymous.

The word favor appears four times in MOS:

• "Misplaced Pages favors no national variety of English"
• "...a practice favored in science writing"
• "Some major American guides to style ... now deprecate U.S. and favor US"
• "We should note that some critics have argued in favor of our proposal"

I can see no problem whatsoever in changing the first three of these to "prefers", "preferred" and "prefer". To me, the meaning stays exactly the same. Changing the fourth to "...argued in preference of our proposal" does seem a bit clumsier, but I think it still works. In any case, this one is just an example sentence and could be easily reworded to "...argued against our proposal" which would still demonstrate the inappropriate use of "our" in the sentence. Bazonka (talk) 12:40, 1 January 2013 (UTC)

I think the meaning actually does shift a bit in the first two. "Favor" in the first case does not mean "prefer" it means "show favoritism toward", and that distinction is actually very important. In the second, the difference is one of agency; "favored in science writing" means that science writing leans in that direction; "preferred in science writing" implies that a written, formal preference has been established and published, which is not the case. The third example would work fine with "prefer", because style guides are in fact formal, established, published preferences. And of course the substitution would no work in the fourth case, even with a weird construction like "argued in preference to our proposal", or whatever. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:07, 1 January 2013 (UTC)

OK. The distinction must be a bit too suble for me, but I shall take your word for it. As alternatives, how about:

• "Misplaced Pages does not follow any specific national variety of English"
• "...a practice usually adopted by science writing", or "...usually followed in science writing"

The third sentence can use "prefer", and meaning of the fourth can change entirely because it's just an example of misuse of "we" and "our", so change "in favor of" to "against". Bazonka (talk) 22:39, 1 January 2013 (UTC)

1. I'm not sure everyone will follow what is meant by "follow" here. :-) I would retain the existing language, for a good reason: I repeat that the word "favors" in "Misplaced Pages favors no national variety of English" does not mean "prefers", it means "shows favoritism toward", and that distinction is actually important. WP could easily not have an express preference for American English yet still favor it anyway. This was actually long the real-world case, due to the dominant percentage of editors being Americans, and is why that passage was added in the first place!
2. We don't actually have any evidence that dotless abbreviations, aside from unit symbols and other special cases, are the dominant practice in science writing, so only saying "a common practice in science writing" is a viable replacement (and is actually more accurate than the "favored" version, which implies dominance almost as strongly as "prefered" or "usually adopted" does).
3. "Some major American guides to style ... now deprecate U.S. and prefer US" is actually a correct statement and more accurate, because the guides are published preferences, not vaguely defined favoritism.
4. The example text does in fact work just fine as "We should note that some critics have argued against our proposal".
   — SMcCandlish  Talk⇒ ɖכþ Contrib. 02:47, 2 January 2013 (UTC)

I was interested to see this discussion as I was considering the wording of the very same passage. I, too, would prefer the word "prefer" to "favor" as it is more common and down to earth than the more literary "favor." I would also suggest a change from the formality of "Although Misplaced Pages favors no national variety of English..." to "While Misplaced Pages does not prefer any national variety of English..." which is the more usual way to put it. What do others think? Michael Glass (talk) 01:56, 2 January 2013 (UTC)

I think, honestly, that this is both a mountain-out-of-a-molehill nitpick, and an exercise near-pointless political correctness to mollify some British/Commonwealth readers who are unhappy that MOS was launched, and thus has stayed in, American English. Not to put too fine a point on it. >;-) That said, see above; I think that three of these cases can be changed in various ways with no harm done, and two will actually be clearer, but it's not just by willy-nilly swapping of "prefer" for "favor". — SMcCandlish  Talk⇒ ɖכþ Contrib. 02:47, 2 January 2013 (UTC)

How very rude. I don't have any problem with what version of English the MOS is written in. MOS:COMMONALITY is not a procedure for scoring points against another version of English; it is a way of making articles more readable. People find it easier to read articles written in their own variety of English because they are not distracted by the spelling differences, etc. So from my selfish personal point of view, as a native BrE speaker, yes I would prefer it if all of Misplaced Pages was in BrE. But of course it's not all about me - there are readers of all backgrounds here, and we must try to find a balance for everyone. This is where COMMONALITY comes in. It's not about changing the language variety, but simply ironing out those unnecessary creases of language difference, and improving readability for everyone. I could have tried to change "color" to a common word "hue", but no I did not, because "color" is such a powerful word without any equally powerful synonyms - its use is not unnecessary. However "favor" is not so strong, and there are viable alternatives (though not as simple as I first thought). If the MOS was written in BrE I would similarly argue about moving away from the use of "favour" (although to be fair, I may not have picked up on it as I wouldn't have been distracted by the word when reading). If MOS doesn't follow MOS then we might as well all give up now. I am quite insulted that you think my raising of this point was an "exercise near-pointless political correctness" because MOS is in AmE. That is just so wrong. Bazonka (talk) 19:42, 2 January 2013 (UTC)

WP:CIVIL doesn't require twee niceness or pretense that one thinks a pointless proposal is just fine. I moderate WP:CIVIL with WP:SPADE, as do many of us. I'm glad you are not proposing things like this just to push Briticisms, but I don't feel bad for making you aware that it was coming off that way. Color and hue are not synonyms (at least not in any field that regularly deals with color, such as art, printing, digital video mastering, etc., etc.). I already agreed with you that three of these four cases of "favor" could be changed with no problem; are you so upset that it's not all four that a rant is necessary?  :-) MOS is written to govern style in articles (and by extension output of templates that appears in articles). It's nice when WP's own internal projectpages can follow it, too, but it is not a requirement. WP guidelines regularly use contractions – lots of them – and articles do not, for example. I apologize for genuinely offending you; my goal was to suggest "you're being nit-picky and this comes off as simply anti-Americanism". — SMcCandlish  Talk⇒ ɖכþ Contrib. 04:49, 3 January 2013 (UTC)

I'm afraid my suggestion about wording got lost in a spat about favor and prefer. Personally, I'm untroubled by the US spelling "favor" but I do think that the wording could be made more user-friendly by a slight change in wording. At the moment, Mos reads

• "Although Misplaced Pages favors no national variety of English..."

How about changing to this:

• "While Misplaced Pages does not favor any national variety of English..."

The proposal is simply to use plain, common English at this point. Nitpicking, maybe, but getting rid of the nits is the way to make the writing clearer, cleaner and more attractive. Michael Glass (talk) 07:46, 3 January 2013 (UTC)

That seems better to me too. Bazonka (talk) 18:03, 3 January 2013 (UTC)

If there's no objection in the next 24 hours I'll go ahead and make this change. Michael Glass (talk) 01:41, 4 January 2013 (UTC)

RfC: Should lines be used between a template and text above it?

Please consider joining the feedback request service. An editor has requested comments from other editors for this discussion. This page has been added to the following lists: Misplaced Pages style and naming Misplaced Pages policies and guidelines When discussion has ended, remove this tag and it will be removed from the lists. If this page is on additional lists, they will be noted below.

This is an RfC to establish wider community input on whether this formatting should apply to all articles. This issue was discussed in the past: Misplaced Pages talk:Manual of Style/Archive 129#Spacing and Using the hidden comment function to create space between a template and text above it.

The Manual of Style states: "Check that your invisible comment does not change the formatting, for example by introducing white space in read mode." (WP:COMMENT)

Does this mean that the above formatting should be used? That is, Should white space be introduced between the last line of text and the top of a footer-(navigational) template?Curb Chain (talk) 07:57, 21 December 2012 (UTC)

Discussion

I don't think that Hidden Comments should be used to introduce white space because the simple enter-key will suffice. Secondly, using the enter-key to make lines to make white space is arbitrary and is not used.

• Misplaced Pages:Manual of Style/Layout#Headings and sections says "Between sections (and paragraphs), there should be a single blank line; multiple blank lines in the edit window create too much white space in the article." which is saying that hidden comments are not to be used to create white space, and not to create white space.

Specifically, the vast majority of pages do not have the formatting as I presented.Curb Chain (talk) 07:57, 21 December 2012 (UTC)

• Curb Chain has been on about this for quite a while now, to the extent of following me around and reverting my edits. He really needs to chill out and realize that the Manual of Style is not policy, it is not something that has to be followed slavishly, and it is certainly not a straightjacket preventing any of us from improving the encyclopedia. Indeed, it cannot be that, because that would, in itself, emasculate the entire purpose of WP:IAR.

  I've explained to Curb Chain many, many times, the purpose of the edits he objects to, and I'll do so once again for the benefit of othere. Please bear in mind that Curb Chain has brought this to AN/I on several occasions, and has been told by numerous editors there that his complaint is among the lamest thinsg anyone has ever come across. Also, please consider that his compaign of harrassment and annoyance is all about a single blank line.

  OK, here's the explanatuon. If you take a look at any decent-sized article, you'll note that the system, when it renders the page, provides a bit of spacing before every section header. This is to help the header stand out and be separated from the section above it. Unfortunately, the system does not do this at the bottom of the page, where any navboxes follow the External links section. Because of this, it's visually unpleasant that the new section (the navboxes) is so close to the text of the external links section, so I've been inserting a blank line to seperate them, to make it easier on the eye tosee the end of the external links and the beginning of the navboxes.

  That's it, that the sum total of what Curb Chain objects to, that he's started two RfCs to try to eliminate, that's he's brought to AN/I on at least two occasions, and that he's followed me around with no other purpose than to delete ,y edits. (Bear in mind, I don't travel around Misplaced Pages inserting this single blank line of space, it's part of my normal editing of articles, which is often quite extensive.) That he's fixated on this is, to say the least, rather bizarre. That his campaign is getting rather disruptive is a matter of opinion - but I think he's gone off the rails a bit. In any event, my purpose in making this edits is solely and entirely to make our articles just a little bit easier to use for our readers. Thanks. Beyond My Ken (talk) 08:23, 21 December 2012 (UTC)

  While I can't say that I find this a compelling disagreement or one to get worked up over, I am kind of inclined to agree with the person in the other discussion who said it'd make more sense to figure out if the extra space is something the whole site needs rather than to go around making impromptu additions of blank space to single articles on a haphazard and case-by-case basis. AgnosticAphid talk 08:47, 21 December 2012 (UTC)

  I would be more than happy if the system could be adjusted to provide the necessary spacing, but no one has ever indicated that this was possible to do. Since that's the case, this is the next best thing. Beyond My Ken (talk) 08:51, 21 December 2012 (UTC)

This is a technical issue and you can ask the developers to do this. You will probably need to get consensus for it.Curb Chain (talk) 01:49, 22 December 2012 (UTC)

• I would recommend against making additional space before a template at the end of the article, but it is not something that should be added to the MOS. The correct way to fix that sort of thing is to edit the template. Apteva (talk) 10:23, 21 December 2012 (UTC)
• I'm puzzled. I think I know what the question is asking, but I'm wondering about an exact offending edit. What is the problem, precisely? Where is a diff that I could use to judge? Is this one? If so, I would oppose the mass addition of spacing. The spacing (or lack of it) between template and text currently is, from what I can remember, deliberate, and if this is the kind of edit that that is offensive, I would oppose both the edit itself and the addition of text describing it to the MOS. --Izno (talk) 15:50, 21 December 2012 (UTC)

Yes, it adds an extra space. We are talking about whitespace, so lines without a hidden comment would be included in the RfC question. And I see that the editor who added the line has just reverted you.Curb Chain (talk) 01:44, 22 December 2012 (UTC)

• This isn't really something MOS needs to address. There may be particular reasons in a particular article to do this (with HTML comments, with <br />, etc.), e.g. to work around misbehaving templates, or because of image spacing or whatever. We generally let editorial discretion reign when it comes to things like that. See also WP:CREEP. — SMcCandlish   Talk⇒ ɖ∘¿¤þ   Contrib. 02:04, 24 December 2012 (UTC)
• I'm pretty sure that the "blank line" for navboxes is supposed to be inserted by some clever CSS, which was added a good few years back. We tried to get the same thing done for stub tmeplates, but I don't think it ever happened. Rich Farmbrough, 04:33, 3 January 2013 (UTC).
  

Why was it removed?Curb Chain (talk) 20:00, 3 January 2013 (UTC)

At long last, WP:Manual of Style/Organisms

I've been working on this, off and on, for over four years. I think it is ready for prime time now. I've researched this so much I feel like I could teach a class about it. I'm not proposing it formally yet, just asking for MOS regulars' input for now. When I formally propose it, it'll be advertised via WP:VP/P and WP:CENT, and the relevant projects invited to comment, of course. Please discuss suggested changes or any concerns/issues at Misplaced Pages talk:Manual of Style/Organisms. I've covered things that have never been touched on in MOS before like how to handle hybrids, greges, landraces, natural breeds, etc., etc., etc. It's a one-stop shop for all scientific and vernacular naming questions, including animals, plants, bacteria and viruses. (And yes, it includes the MOS position that capitalizing bird common names is controversial, and why, but I've tried not to be inflammatory about it.) — SMcCandlish  Talk⇒ ɖכþ Contrib. 10:53, 2 January 2013 (UTC)

My first thought: "Hoo boy. What are we going to do about the species capitalization issue?" Darkfrog24 (talk) 15:22, 3 January 2013 (UTC)

ENGVAR examples

Discussion following several reverts today. I think Kevin McE and I are essentially making the same point, which Kevin McE explained well: "If it is not clear cut and unambiguous, and adhered to, it is not worth citing as an example". For the examples to be educationally useful, it should be possible for an editor to go to the article and find it tagged exactly as we say here in the example. Sure, it is true that "close national ties" indicates that Institutions of the European Union could theoretically be written in British or Irish English, but also we have to be consistent within the article. Evidently, British English was chosen and the article has been tagged accordingly. It's confusing to just say "(British or Irish English)" in the example without giving further explanation. (It could be done: we could separate out that example and say theoretically this could be either British or Irish, but British was chosen and now we stick to that.) With respect to Taj Mahal, I can't disagree with Dodger67's comment that the "Use British English" tag was wrong. However, I don't think it's helpful to say "(Indian English or British English)" in the example quoted here. Further, if we want to use it as an example for "Indian English", it would be helpful if the article were tagged "Use Indian English". – Wdchk (talk) 15:24, 3 January 2013 (UTC)

There is very little difference between Irish and British English, so an ambiguous description is probably good enough. And regarding Taj Mahal, WP:MOSIN states that Indian English should be used. Whilst this is largely the same as British English, it's not identical. Bazonka (talk) 18:01, 3 January 2013 (UTC)

Institutions of the European Union: you are right, there is little difference between Irish and British English, but I think we need to remember this is an instruction manual. So, we could separate out that example and say theoretically this could be either British or Irish, there is little difference between Irish and British English, British was chosen and now we stick to that. But if we just say "(British or Irish English)" and leave it hanging, how does that help an editor who doesn't already know what we mean? • Taj Mahal: I agree, Indian English should be used in the article. So why do we say "(Indian English or British English)" here in the MOS? – Wdchk (talk) 12:36, 4 January 2013 (UTC)

"Indian English" alone should be preferred: Taj Mahal relates to India, not the UK. Institutions of the European Union relates equally to Ireland and the UK. SSR (talk) 07:33, 5 January 2013 (UTC)

(The Taj Mahal discussion appears to have separated, so I suggest we continue it at #Taj Mahal and British English.) – Wdchk (talk) 17:44, 5 January 2013 (UTC)

Institutions of the European Union could have been written in either British or Irish English, but once an article exists with some degree of stability, it is no longer appropriate to say that it "should use" one of two variants. MOS:RETAIN clearly dictates that British English is now the only appropriate version for that article, as re-inforced by the presence of the Template:British English, and it is wrong for MoS to contradict that. Kevin McE (talk) 09:49, 5 January 2013 (UTC)

Institutions of the European Union could also have been written in Maltese English. Just throwing that one out there... Bazonka (talk) 10:40, 5 January 2013 (UTC)

The EU is suprannational, so it has no strong national ties. Therefore it could even have been written in American English. Wasn't, but could have been. --Trovatore (talk) 10:43, 5 January 2013 (UTC)

The previous 3 paragraphs all contain very good points. So, to come back to my original question, is it appropriate to use Institutions of the European Union as an example in the MOS, stating "(British or Irish English)" without further explanation? Should we use it as an example of "no strong national ties", with added explanation? Or is it just a bad example, because of complexity, and we should remove it? (One editor already made a case for removal, but the removal was reverted, which is why we are discussing here.) – Wdchk (talk) 18:16, 5 January 2013 (UTC)

I'd lean towards "bad example". --Trovatore (talk) 18:23, 5 January 2013 (UTC)

Should ENGVAR extend to spinout articles?

ENGVAR currently calls for consistent usage within a given article. Over at Talk:Strained_yoghurt#Motion_to_start_an_RM:_Redux, the issue is essentially whether it should also apply to spinout articles of a given article. Since a spinout article is a virtual extension of its parent, this makes sense to me, but it's not what ENGVAR currently states. Is that intentional?

I think it's likely that nobody really considered this case when writing ENGVAR, because spinouts were simply overlooked, and they normally naturally follow the usage of their parents, since they are usually formed largely with copy/pasting from the parent. The practical impact of extending ENGVAR to apply to spinouts too would be very minimal, since the English variety is already consistent with the parent for almost all spinouts, and English variety is changed very rarely. But in the rare cases where consensus decides there is a good reason to change the English variety of an article, doesn't it make sense to make the same change in the spinouts of that article?

Does anyone know of any examples, outside of the yogurt "family" of articles, where the English variety of a spinout differs from its parent?

To clarify with an example, I'm not suggesting all articles that refer to "color" use color because Color is not at Colour - this is limited strictly to true spinouts (like Color blindness, which is a spinout of Color, but not Colours, standards and guidons, which is not a spinout of Color - there is no section in Color that links to Colours, standards and guidons).

I'm not suggesting a change to ENGVAR right now, as that would be inappropriate while this issue is being debated at that RM discussion, but thought folks following this page, with an interest in ENGVAR, might want to weigh in, here, at the RM, or both! Thanks! --Born2cycle (talk) 17:02, 3 January 2013 (UTC)

This is just another tool that Born2cycle can use to argue to try to get his way, improving title stability by moving articles. If you look at the particular spinoff in question, it has been pretty stable at Strained yoghurt since it started in 2007. It spun out from Yoghurt during a multi-year stable period that commenced after a lot of title thrashing in 2006 (much of it driven by B2C). If article families are to have consistency of ENGVAR (which many don't), why was this not brought up to resist B2C's efforts to change the ENGVAR of Yoghurt back to a vestigial pre-2006 original, after years of relative stability? A little more respect for WP:RETAIN would be in order if stability is actually valued. I have no attachment to either spelling, but I really don't like these disingenuous tactics that characterize B2C's campaign of "stability". Dicklyon (talk) 17:57, 3 January 2013 (UTC)

Indeed, stability ultimately comes from consistency with unambiguous rules, and getting there ironically often requires change (as well as improving the rules by making them less ambiguous).

Suggesting that the goal of consistency in article families is a valid argument to oppose changing usage in a parent article, because that would make the main article inconsistent with usage in its spinouts, is like saying a title should not be changed because the article content uses the name that is the current title. Spinouts naturally follow the lead set by the main article, not the other way around.

WP:RETAIN deserves due respect, but not to the extent of using it to stonewall against any change no matter how strong the arguments in favor of change are. The last year of unprecedented stability and quiet at Yogurt/Talk:Yogurt confirms the strength of the many practical reasons cited for moving that article as we did, reasons that outweighed WP:RETAIN considerations. That done, it only makes sense to bring the title and usage in spinouts like Strained yoghurt in line with Yogurt. --Born2cycle (talk) 19:15, 3 January 2013 (UTC)

I'd be interested in cross-article consistency. -Kai445 (talk) 03:41, 4 January 2013 (UTC)

I can't see that the differences in spelling are worth fighting over. Salt has American spelling while Iodised salt has British spelling. I think we can live with that. However, I think we should give the alternative spelling where this is necessary. One interesting case came up in the article on English landscape gardens, where the first major contributor was American but the subject itself would appear to be essentially British. So which spelling convention should prevail? The discussion http://en.wikipedia.org/Talk:English_landscape_garden#Spelling_conventions apparently left the question up in the air, with a mixture of American and British spellings (center but modelled). So there are occasions when the guidelines clash, but with a bit of give and take, this shouldn't be too much of a problem. Michael Glass (talk) 03:57, 4 January 2013 (UTC)

• My reading of the consensus application all along is that ENGVAR only applies to any given article. Consistency within a given article has always been the key driver. If an article is a genuine spin-off – ie that the content originated from within a 'parent' article – then it ought naturally to already possess the "correct" spelling variant. Clearly related articles, such as works created by a given author or musician, would adopt ENGVAR by virtue of WP:TIES. So I don't see any issue. -- Ohconfucius  04:22, 4 January 2013 (UTC)

• Comment: I support the main article being titled yogurt and in fact I briefly participated in that discussion. But this proposal seems to raise all sorts of problems. Why is it, exactly, that strained yoghurt would become strained yogurt to achieve consistency rather than yogurt being changed (back?) to yoghurt to achieve consistency? Is it based on the relative age of the two articles or because of the perceived importance of the two subjects? What would happen in the future if the topic with the longer name was created before the topic with the shorter name?

It seems like to be consistent with ENGVAR that the rule would always have to be that whichever article was created first would prevail. But ferreting out, for example, all the different articles you deem sufficiently related to color – color blindness, but not True Colors, and who knows about true colors – to determine which was created first, or which was first expanded past stub form, seems like kind of an intense exercise for not much actual consistency benefit. AgnosticAphid talk 07:43, 4 January 2013 (UTC)

Having pondered this for all of an additional five minutes, I'd like to say one more thing. It does seem appealing in the abstract to achieve consistency; encyclopedia brittanica certainly wouldn't have an article about yogurt and an article about a specific type of yoghurt. But really, it seems to me that the whole idea behind ENGVAR is that we're going to subsume encyclopedia-wide spelling consistency beneath other goals like, I guess, harmony, less pointless argument about mutually intelligible spelling differences in an ostensibly worldwide encyclopedia, and other goals that I can't think of off the top of my head because I'm no expert. Nobody is going to decide that all of the articles in the encyclopedia must use "yogurt" in article text because of this discussion, so why should we enforce consistency with the article titles themselves?

That's why I think that changing an ENGVAR-compliant article title (strained yoghurt) just to achieve arguable ENGVAR-consistency with a separate article (yogurt) seems a bit hostile to the idea behind ENGVAR. AgnosticAphid talk 08:04, 4 January 2013 (UTC)

I think that each article should be considered individually. It should not have to match its parent or what people think its parent might be. For example, should "color blindness" be considered a spinout of "color" or of "blindness"? Darkfrog24 (talk) 15:51, 4 January 2013 (UTC)

I agree with Darkfrog24. Every article should be considered individually. However, when one article links to another, then the spelling of the link (even if used in a Main template) doesn't need to match the spelling of the article, and a redirects can do the rest. Bazonka (talk) 18:00, 4 January 2013 (UTC)

• In my opinion, treating each article individually is a far more consistent, simple, and uncontroversial approach. Trying to define "parents" and "spinouts" looks like a minefield. I'd favour keeping WP:ENGVAR ("Although Misplaced Pages favors no national variety of English, within a given article the conventions of one particular variety should be followed consistently.") and, more generally, WP:MOS ("Style and formatting choices should be consistent within an article, though not necessarily throughout Misplaced Pages as a whole.") as they currently exist, without exceptions. SSR (talk) 07:29, 5 January 2013 (UTC)

Ligatures (in English, outside quotations)

The MOS mentions that "disused ligatures" are routinely replaced by other works (not WP), as part of its justification of WP's cautiously replacing ampersands in quotations. I continually see editors work in the other direction, however, adding ligatures, not just into quotations but into articles, as here, here and here. Should a sentence be added to the MOS to clarify whether such edits are OK or not, and more generally whether articles should use such ligatures or not? If this has been discussed before, I apologise that I was unable to find the past discussion. (If there was a past consensus, I still think it would be useful to mention it in the MOS: "Ligatures like "mediæval" are discouraged..." or "Ligatures like "mediæval" are allowed..." or "There is no consensus on whether to use ligatures like "mediæval" in articles.") -sche (talk) 11:02, 4 January 2013 (UTC)

A good question. The spirit of MOS has been against the use of those old ligatures, but the particular provision was edited out at some stage. At the section called "Typographic conformity", these changes within quotations are explicitly mentioned: "Normalizing archaic glyphs and ligatures, when doing so will not change or obscure the meaning or intent of the text. Examples include æ→ae, œ→oe, ſ→s, and y→the." It is reasonable to read this as a recommendation against introducing such ligatures in article text. Otherwise, what sense do we make of "normalizing"? The whole section is about making text in quotations conform, in accord with all publishing practice, with the house style used in the surrounding article.

So I would support a change, to state this positively. There are good reasons for avoiding these characters, similar for those for straight apostrophes and against curly ones.

Important exceptions that used to be mentioned in MOS, I think:

• æ in Anglo-Saxon names and text (but not in such modern words as "mediæval", "encyclopædia"). It was a distinct letter in Anglo-Saxon, but not in later English or in Medieval Latin.
• œ in French words used as French text, such as quoted French text that include such words as "œuf" and "sœur" (but not the British spellings "œsophagus" and "manœuvre"; use "oe" in those).

Those are standard principles in major guides.

Other thoughts?

Noetica 11:25, 4 January 2013 (UTC)

I agree that both of those are necessary exceptions, though I wonder if it would make sense to subsume them into—or make examples of—a general rule that ligatures are acceptable in any languages in which they are standard, hence Old English, French, Icelandic, Norwegian, Faroese...but not English.

In your experience, how much must the MOS spell out, and how much can be left up to common sense? I guess the fact that I see people changing "medieval" to "mediæval" answers that question to some extent!

What do you think of wording like:

• Ligatures should be used in languages in which they are standard, hence The meaning of Moreau's last words, clin d'œil, is disputed. is preferable to The meaning of Moreau's last words, clin d'oeil, is disputed.. Ligatures should not be used in English outside of names, hence Æthelstan was a pre-mediaeval king, not Æthelstan was a pre-mediæval king.

-sche (talk) 04:51, 5 January 2013 (UTC)

check out NOK

on disambiguation pages, is it necessary that the disambiguated term be used in the target article? an editor has been removing dab entries from NOK on the basis that "usage is not supported by the linked article". This is obviously nonsensical since it implies that, for example, Houston (disambiguation) would not include an entry for Houston Astros. Or am I mistaken? --NReTSa (talk) 02:44, 5 January 2013 (UTC)

I found the guideline: WP:DABABBREV. "Do not add articles to abbreviation or acronym disambiguation pages unless the target article defines the acronym or abbreviation ..." And I don't understand the Houston example. "Houston" isn't an abbreviation or acronym, and anyway the word "Houston" occurs once in the title "Houston Astros", and 118 times in the Houston Astros article. The article occasionally uses the word "Houston", without the word "Astros", as a shortened form of the name "Houston Astros". So a sports announcer mentioning "Houston" could mean the Astros. It turns out NOK can mean New Orleans/Oklahoma City Hornets, but the linked article doesn't say so. Art LaPella (talk) 03:19, 5 January 2013 (UTC)

MOS issues in naming Pondicherry, Orissa

Move requests on these talk pages debating competing sections of the MOS. I tried adding a section a year or so ago on why we prefer Ganges over Ganga, despite ENGVAR, but the response was that it was too obvious to bother with. Well, it's back: Since Pondicherry is in India, the argument is we should use the local Indian English name regardless of what is the common name over all. Do we have a clear answer one way or the other? — kwami (talk) 04:03, 5 January 2013 (UTC)

The principles seem pretty clear to me and always have done, that we should be looking to: "The most common name for a subject ... as determined by its prevalence in reliable English-language sources". WP is a global encyclopedia and that means all such sources. We don't simply, necessarily, go with the local, "national" or official name. I get the point about local varieties of English and WP:ENGVAR, but I'm not sure how relevant it is. We are not talking about either spelling (eg favour vs favor) or different words for generic terms (eg pavement vs sidewalk) – where the different varieties of English have relatively fixed and clear rules and where ENGVAR clearly comes into play – but proper names. It seems doubtful whether one can say that there are "Indian English" versions of placenames in any real sense; especially with these changing ones, even if a majority of Indian English sources have started to use the new official form, other Indian sources will continue to use the former one. Until we have clear unanimity within Indian sources, I can't see that we have an ENGVAR issue to override COMMONNAME when global majority use genuinely remains at the old official name. N-HH talk/edits 15:00, 5 January 2013 (UTC)

That's always been my understanding. Can we add something explicit to that point to head off some of these chronic disputes? — kwami (talk) 03:10, 6 January 2013 (UTC)

N-HH, what happens when we do get clear unanimity within Indian sources on a spelling reform but British Australian and American sources continue to use the old spelling for another 5 years. Since this is what happened with e.g. Kolkata. What then? In ictu oculi (talk) 04:39, 6 January 2013 (UTC)

Taj Mahal and British English

On a related point to the above .. maybe I'm being thick, but I don't quite see why British English would be an equal option to Indian English for a page about a Mughal monument in India? The example was included I think with both options listed and now we have the British option being reinserted after it was removed. N-HH talk/edits 15:13, 5 January 2013 (UTC)

Maybe OhConfucius' edit was because Talk:Taj Mahal doesn't actually have the tag/banner. To me it would seem like a no brainer, but maybe there's something in the archive? In ictu oculi (talk) 04:48, 6 January 2013 (UTC)

I agree. The British didn't build the Taj Mahal. The "strong national tie" to the Taj Mahal is India's tie. Otherwise, you might as well put British English as an option on the American Civil War (civil war in a former British colony) and Vancouver B.C. (named for an English officer, and it's even British Columbia, right?). -- JHunterJ (talk) 15:23, 5 January 2013 (UTC)

Would use of Indian rather than British English actually make much difference in the Taj Mahal article other than use of Indian-style numbering (i.e. Lakhs and Crores) which would have to be appropriately linked and or explained anyway?Nigel Ish (talk) 15:57, 5 January 2013 (UTC)

Not sure it would really in practice – I'm not an expert on the differences and peculiarities (other than a slightly odd, to these eyes, use of the word "mishap" on occasion in such a way that it understates the gravity of an event) but I'm not aware of such wide-ranging and obvious differences as there are between, say, US and British English in terms of words, spelling etc. Either way though, the assertion of equivalence matters as an issue of principle here surely, if nothing else. N-HH talk/edits 16:06, 5 January 2013 (UTC)

Little or no difference in Taj Mahal (few if any textual changes), big difference in Misplaced Pages:Manual of Style (one is right and the other is wrong). -- JHunterJ (talk) 16:23, 5 January 2013 (UTC)

In that case, is it appropriate as an example to use in MOS - shouldn't we use examples where using different variants of English will make a difference?Nigel Ish (talk) 16:30, 5 January 2013 (UTC)

Different varieties of English will make a difference at Taj Mahal. I suspect it would read differently using American English, Australian English, or Jamaican English. But I have no objection to replacing it with a different example of an article that should use Indian English. -- JHunterJ (talk) 17:32, 5 January 2013 (UTC)

I think Taj Mahal is as good an example as any. The only problem for me is where we suggest it could be written in British English or Indian English, which goes against WP:CONSISTENCY. Also, let's remember we're not discussing the Taj Mahal article. The discussion is whether Taj Mahal should be used as an example in the MOS of which variety of English to use. As a MOS example, we need to make an unambiguous statement. – Wdchk (talk) 17:58, 5 January 2013 (UTC)

I think Taj Mahal is unambiguous. It's in India, built by Indians, owned by Indians. Nothing British at all. But another example could be used if necessary. And whilst there aren't many practical differences between British and Indian English, there are some differences, so it is not correct to conflate the two. Bazonka (talk) 18:06, 5 January 2013 (UTC)

Clarification about my use of the word "unambiguous": what I am saying is it's ambiguous to continue to say "(Indian English or British English)". Based on the discussion here, I'm fine with saying "Taj Mahal (Indian English)". – Wdchk (talk) 18:22, 5 January 2013 (UTC)

Apologies btw for opening up this semi-duplicate thread; I hadn't noticed it was already part of the wider ENGVAR thread a couple of sections up, and only started it in response to the main page edit noted in my opening comment. Anyway, between the two discussions, we seem to be fairly much in agreement that the Taj Mahal would work as an example for India and nonetheless nearly 100% in agreement that it should say "Indian English" not – as it does currently following the edit in question – "British or Indian English". Even if the argument is that they are more or less the same, and that there isn't a substantively distinct thing as "Indian English", then we have tautology as well as a confused point being made. N-HH talk/edits 18:26, 5 January 2013 (UTC)

Do we need 5 new shortcuts into MOS:NDASH?

I've reverted this addition of many shortcuts pending discussion of why we would want them. The MOS and other pages are already overloaded with too many shortcuts, I think. Dicklyon (talk) 18:15, 5 January 2013 (UTC)

WP:Manual of Style #Anglo- anchor

Useful or not, but it is the target for redirects I currently use in discussions. Dicklyon, I hate your attitude to push the "undo" button when you see something which cannot promptly explain. Put my anchor back, please, I need it now. Incnis Mrsi (talk) 19:57, 5 January 2013 (UTC)

It's called WP:BRD. Is it such a bad process? If you really need an anchor, just put an anchor; but say why. Dicklyon (talk) 00:21, 6 January 2013 (UTC)

• Misplaced Pages requests for comment