Misplaced Pages talk:Manual of Style: Difference between revisions

Browse history interactively ← Previous edit Next edit →Content deleted Content addedVisual WikitextInline

Revision as of 07:46, 20 July 2011 editDiego Moya (talk \| contribs)Extended confirmed users, Pending changes reviewers, Rollbackers29,467 edits →Identity ← Previous edit		Revision as of 10:42, 20 July 2011 edit undoNoetica (talk \| contribs)Extended confirmed users12,370 edits →Summary; final request to complete discussion; and notice of a final draft: Answering all points, and a new subsection: === Final draft 1: please endorse, or comment ===Next edit →
Line 1,237:		Line 1,237:
	*'''Disagree''' The length is excessive. Kotniski's draft is much shorter, and could be shortened further - yet it covers more ground. ] <small>]</small> 18:07, 19 July 2011 (UTC)		*'''Disagree''' The length is excessive. Kotniski's draft is much shorter, and could be shortened further - yet it covers more ground. ] <small>]</small> 18:07, 19 July 2011 (UTC)
	* '''Agree''' if that means the current length is OK. Brevity that results in ambiguity is of little benefit. As I discuss under ''Spacing in ranges'', I erred in providing far too few examples, including one that eluded me until this afternoon when I actually had to use it. The proposal concentrates more on examples than abstract descriptions, which is as it should be. ] (]) 04:29, 20 July 2011 (UTC)		* '''Agree''' if that means the current length is OK. Brevity that results in ambiguity is of little benefit. As I discuss under ''Spacing in ranges'', I erred in providing far too few examples, including one that eluded me until this afternoon when I actually had to use it. The proposal concentrates more on examples than abstract descriptions, which is as it should be. ] (]) 04:29, 20 July 2011 (UTC)

			;Response in the final draft
			* No specific actions were called for. I added a couple ''more'' examples, to satisfy other requests below. <font color="blue"><big>N</big><small>oetica</small></font><sup><small>]</small></sup> 10:42, 20 July 2011 (UTC)

	=====2. Content and layout of examples=====		=====2. Content and layout of examples=====
Line 1,251:		Line 1,254:
	* '''Comment''' I would like to see all examples of ranges of dates (and perhaps of physical quantities with appended units) include nonbreaking spaces where appropriate, as called for in ] (e.g., between date numbers and month names, as in <code>1790&nbsp;&ndash; 1&nbsp;December</code>); new editors often learn by looking at the code. ] (]) 04:51, 20 July 2011 (UTC)		* '''Comment''' I would like to see all examples of ranges of dates (and perhaps of physical quantities with appended units) include nonbreaking spaces where appropriate, as called for in ] (e.g., between date numbers and month names, as in <code>1790&nbsp;&ndash; 1&nbsp;December</code>); new editors often learn by looking at the code. ] (]) 04:51, 20 July 2011 (UTC)

			;Response in the final draft
			* I have managed to satisfy Jeff's request regarding the order of texts and examples.
			* Several examples already show adjectival use; I have added two more, if we include {{xt\|ex–prime minister Thatcher}} (Jeff accepts that as adjectival below, but I don't). It is important to show ''non''-adjectival uses also; they can be trickier in their way. This suggestion would have been better made during the last week, while the now superseded draft was on the table.
			* It was discussed earlier that the issue of hard spaces would be removed, for enhanced general treatment elsewhere in MOS. Again, it is awkward to have to revisit this issue at the last minute (beyond my 24-hour period of notice, and four days after ArbCom's deadline). For every reader of MOS who is helped by seeing &nbsp; in examples, there will be another is flummoxed and alienated by it. Best treated specially elsewhere; and best to revisit this issue another time. <font color="blue"><big>N</big><small>oetica</small></font><sup><small>]</small></sup> 10:42, 20 July 2011 (UTC)

	'''B.''' A di M commented: "I'd use examples like the current ones for the dash (with such über-familiar noun phrases as prime minister or World War II), and then after '... is possible and better' show seriously abstruse examples in red followed by a suggested rephrasing in green," and later: "... if we say that rewording is sometimes (but not always) better, I think we ought to include both examples of when it's better than when it isn't." My own view is that the present examples work well to make their points. I put a lot of thought into their selection. And we don't want ''more'' examples, surely.		'''B.''' A di M commented: "I'd use examples like the current ones for the dash (with such über-familiar noun phrases as prime minister or World War II), and then after '... is possible and better' show seriously abstruse examples in red followed by a suggested rephrasing in green," and later: "... if we say that rewording is sometimes (but not always) better, I think we ought to include both examples of when it's better than when it isn't." My own view is that the present examples work well to make their points. I put a lot of thought into their selection. And we don't want ''more'' examples, surely.
Line 1,260:		Line 1,267:
	*'''Immaterial'''; but I'd like to see what A di M has in mind before deciding. ] <small>]</small> 18:07, 19 July 2011 (UTC)		*'''Immaterial'''; but I'd like to see what A di M has in mind before deciding. ] <small>]</small> 18:07, 19 July 2011 (UTC)
	*'''Agree''' with current examples, but might consider a few specifics ''if'' they would illustrate points that would otherwise be lost. ] (]) 04:51, 20 July 2011 (UTC)		*'''Agree''' with current examples, but might consider a few specifics ''if'' they would illustrate points that would otherwise be lost. ] (]) 04:51, 20 July 2011 (UTC)

			;Response in the final draft
			* I believe I have understood A di M's suggestion; I have added an example in response. <font color="blue"><big>N</big><small>oetica</small></font><sup><small>]</small></sup> 10:42, 20 July 2011 (UTC)

	=====3. Expository points=====		=====3. Expository points=====
Line 1,271:		Line 1,281:
	*'''Disagree'''. The explanation is that compounds normally take hyphens (or spaces, or nothing). We do not need to deal with exceptions to exceptions. ] <small>]</small> 18:07, 19 July 2011 (UTC)		*'''Disagree'''. The explanation is that compounds normally take hyphens (or spaces, or nothing). We do not need to deal with exceptions to exceptions. ] <small>]</small> 18:07, 19 July 2011 (UTC)

			;Response in the final draft
			* Despite PMAnderson's dissent, the request appears reasonable. I have satisfied it. <font color="blue"><big>N</big><small>oetica</small></font><sup><small>]</small></sup> 10:42, 20 July 2011 (UTC)

	'''B.''' Dicklyon was "a little bothered by the statement 'These can be quite similar to uses of the hyphen; or less often, the slash.' " (See details above.) I accept this, and will make a change that expresses things better.		'''B.''' Dicklyon was "a little bothered by the statement 'These can be quite similar to uses of the hyphen; or less often, the slash.' " (See details above.) I accept this, and will make a change that expresses things better.
Line 1,279:		Line 1,291:
	* '''Agree''' – Thanks for hearing me; I'll trust that you'll improve it a bit. ] (]) 14:58, 19 July 2011 (UTC)		* '''Agree''' – Thanks for hearing me; I'll trust that you'll improve it a bit. ] (]) 14:58, 19 July 2011 (UTC)
	*'''Let's see what happens'''. ] <small>]</small> 18:07, 19 July 2011 (UTC)		*'''Let's see what happens'''. ] <small>]</small> 18:07, 19 July 2011 (UTC)

			;Response in the final draft
			* Done. Explained. More needs to be said about these combining forms (''Franco'', ''Sino''); but to get things concluded now, I'll hold back my concerns till the next time we visit the dash section. <font color="blue"><big>N</big><small>oetica</small></font><sup><small>]</small></sup> 10:42, 20 July 2011 (UTC)

	=====4. Spacing in ranges=====		=====4. Spacing in ranges=====
Line 1,298:		Line 1,313:
	:Perhaps it could be said that these issues should have been raised earlier; if so, as the person who did the breakout, I must take much of the responsibility for failing to better separate some of the usages. Though some of my differences here are a matter of personal preference, I say once again that the sources agree with me. To the anticipated rejoinder that “we have moved beyond the guides”, I would say that I have a bit of a problem with summarily ignoring the “quality of the arguments” element of ], especially since I raised it in polling. If we really feel that “I like it” sometimes carries the day, we should revise ] accordingly. If we simply ignore it, I fail to see how we could chide anyone for ignoring this guideline as well. Again, please take my comments here in perspective—recall that my first words were “It looks pretty good”, and the cases here are relatively few. Nonetheless, my disagreement remains strong on a few of them. ] (]) 04:22, 20 July 2011 (UTC)		:Perhaps it could be said that these issues should have been raised earlier; if so, as the person who did the breakout, I must take much of the responsibility for failing to better separate some of the usages. Though some of my differences here are a matter of personal preference, I say once again that the sources agree with me. To the anticipated rejoinder that “we have moved beyond the guides”, I would say that I have a bit of a problem with summarily ignoring the “quality of the arguments” element of ], especially since I raised it in polling. If we really feel that “I like it” sometimes carries the day, we should revise ] accordingly. If we simply ignore it, I fail to see how we could chide anyone for ignoring this guideline as well. Again, please take my comments here in perspective—recall that my first words were “It looks pretty good”, and the cases here are relatively few. Nonetheless, my disagreement remains strong on a few of them. ] (]) 04:22, 20 July 2011 (UTC)
	:* OK. Well, why not try working offline (backchannel, on your talk pages, whatever) with Noetica to hammer out a better solution. None of this stuff is locked in stone. Consensus can change. This is a complex package of changes and consolidations and there are bound to be points that can be modified or added. In that spirit, I hope one or both of you come back with a tweak you can accept in the spirit of compromise so you, Jeff, can be a member of an across-the-board consensus. ] (]) 05:04, 20 July 2011 (UTC)		:* OK. Well, why not try working offline (backchannel, on your talk pages, whatever) with Noetica to hammer out a better solution. None of this stuff is locked in stone. Consensus can change. This is a complex package of changes and consolidations and there are bound to be points that can be modified or added. In that spirit, I hope one or both of you come back with a tweak you can accept in the spirit of compromise so you, Jeff, can be a member of an across-the-board consensus. ] (]) 05:04, 20 July 2011 (UTC)

			;Response in the final draft
			* Dick, and Tony want to move on; PMAnderson wants silence; Jeff wants to expatiate at the eleventh hour; and Greg wants Jeff and me to get a room, where he can talk the legs off a chair and I can talk them back on again (count them at the end: there'll be five by then). Let's see what I can do ...
			* Jeff, your vote was a compromise? Fine. So was mine (I'd want certain headings to have been in this fold also, agreeing with at least five major style guides and de facto practice at OUP). The majority appears to be happiest with spaced en dashes for ranges when either component has a space; so we meet in the middle, with them. Now, you say that {{xt\|Christmas Day – New Year’s Eve}} is not a range of dates? I say it is; and that its similarity to {{xt\|New York–London flight}} is as superficial as the similarity of {{xt\|blue~green algae}} and {{xt\|red~green colorblindness}} (which we distinguish with "-" and "–"). We need to ''identify'' {{xt\|Christmas Day – New Year’s Eve}} as a range of dates in the examples, to make a robust, simple guideline that anyone can understand. It does no more harm to space this one than it does to space any other date example (with spaces in it). For that reason I have added a ''further'' example: {{xt\|Christmas 2001 – Easter 2002}}. ''That'' is a date range, surely. The user gets the idea, and can remember and apply it. Bear in mind that these date ranges typically occur in parentheses, where they can do no harm to the enclosing sentence. As for your highly unusual and recently discovered example Jeff ({{xt\|the 20 kHz – 20 Hz propagation delay}}), remember that hard cases make bad laws. There will always be rare, fluky situations that call for creative solutions; we soon get entangled if we make ourselves hostage to them.
			* Finally Jeff, you have misunderstand me if you think that I interpret consensus as only a matter of counting votes. I ''wish'' you had not raised this right here; but since you did, I will answer. I wrote of the "practical necessity" under which I operated, given Casliber's requirement they we vote clearly, to "quantify" the consensus. Take him to task, not me. It was extraordinarily hard to work up a draft drawing on every last eddy of opinion, in those two subpages crammed with comment. Luckily, the voting corresponded pretty well with the weight of argument and evidence (sign of a thoughtful group). I suggest that ''you'' revisit the top few sentences of ], yourself. Take PMAnderson along with you. I quote: '''"Consensus is not necessarily unanimity. Ideally, it arrives with an absence of objections, but <u>if this proves impossible, a majority decision must be taken</u>. More than a simple majority is generally required for major changes."''' We have every reason to believe that this is such a case. Practical necessity, once more. But still, who is ''not'' trying for something better, by reason, compromise, and consultation? I know ''I'' have been, for the last several months. <font color="blue"><big>N</big><small>oetica</small></font><sup><small>]</small></sup> 10:42, 20 July 2011 (UTC)

	=====5. En dash with spaced components=====		=====5. En dash with spaced components=====
Line 1,314:		Line 1,334:
	* '''Agree''' – This works for me.--] (]) 20:32, 19 July 2011 (UTC)		* '''Agree''' – This works for me.--] (]) 20:32, 19 July 2011 (UTC)
	* '''Agree''' Like Dick, I think it adds clarity in some cases, and probably more so than with prefixes. And as I’ve said, if a hyphen is OK here, it’s OK in many other cases where we call for an en dash. Be assured, though, that I won’t be running around looking for uses of the hyphen here to correct. I would, however, have the examples show adjectival use (e.g., {{xt\|ex–prime minister Brown}}) because I think the benefit is more obvious}} (and how should “former prime minister Brown” be handled?). ] (]) 05:02, 20 July 2011 (UTC)		* '''Agree''' Like Dick, I think it adds clarity in some cases, and probably more so than with prefixes. And as I’ve said, if a hyphen is OK here, it’s OK in many other cases where we call for an en dash. Be assured, though, that I won’t be running around looking for uses of the hyphen here to correct. I would, however, have the examples show adjectival use (e.g., {{xt\|ex–prime minister Brown}}) because I think the benefit is more obvious}} (and how should “former prime minister Brown” be handled?). ] (]) 05:02, 20 July 2011 (UTC)

			;Response in the final draft
			* My analysis of the voting differs from PMAnderson's. Analysing the votes ''with their associated comments'' (as everyone accepts that we should), and seeing what the voters were willing or unwilling to accept, I count it this way. Of the 29 who voted on this principle (including PMAnderson, though he did not vote outside the navbox):
			** '''7 rejected it outright''' (SarekOfVulcan, Powers, Hullaballoo Wolfowitz, SJ, Headbomb, Nageh, Telpardec)
			** '''7 accepted it, but asked that it be optional''' (WFC, A di M, Powers, Enric Naval, Ozob, JN466, PMAnderson)
			** '''15 accepted it, and did not ask that it be optional''' (JeffConrad, Kotniski, Armbrust, Dabomb87, Tony, Kwami, ErikHaugen, Dicklyon, CWenger, Jenks24, Courcelles, macwhiz, Finell, InverseHypercube, Noetica )
			::That's a simple majority (15–14) accepting it without any option; and that's a ''clear'' majority accepting it in one way or another (22–7). Only 7 out of 29 favour giving a choice. Nothing in ] obliges us to accommodate every minority preference in a manual of style. That's not what manuals of style are for. Last, we don't know what those 7 would say to this question: "Do you want a manual of style to set a simple uniform guideline for everyone?" That number would have been 8, remember: but I gave up my opposition to the principle for the larger good: consistency of style on Misplaced Pages. In fact, I would have held out and maintained opposition; but Jeff was so adamant, and the principle ''is'' so widely accepted in America, that I yielded.
			* I have amended the heading for the section; we voted on prefixes, and it is confined to prefixes.
			* By an extreme act of contortion, I have amended the guideline in the final draft so that it applies in an acceptable, well-delimited set of cases, and recasting is to be clearly preferred in all other cases. I submit that this is an optimal solution. <font color="blue"><big>N</big><small>oetica</small></font><sup><small>]</small></sup> 10:42, 20 July 2011 (UTC)

	=====6. In lists=====		=====6. In lists=====
Line 1,328:		Line 1,357:
	* '''Agree''' – This also works for me, for the moment, and agree that further changes could be considered at a later point.--] (]) 20:32, 19 July 2011 (UTC)		* '''Agree''' – This also works for me, for the moment, and agree that further changes could be considered at a later point.--] (]) 20:32, 19 July 2011 (UTC)
	* '''Agree''' that because the proposal includes examples, it’s a big improvement, provided that we don’t see it as precluding other punctuation. I still have doubts about whether this is a distinct usage, but this is a minor issue that can be dealt with later if it’s felt necessary. ] (]) 05:06, 20 July 2011 (UTC)		* '''Agree''' that because the proposal includes examples, it’s a big improvement, provided that we don’t see it as precluding other punctuation. I still have doubts about whether this is a distinct usage, but this is a minor issue that can be dealt with later if it’s felt necessary. ] (]) 05:06, 20 July 2011 (UTC)

			;Response in the final draft
			* Nothing to do; nothing done. <font color="blue"><big>N</big><small>oetica</small></font><sup><small>]</small></sup> 10:42, 20 July 2011 (UTC)

	=====7. Points to deal with elsewhere, outside the dashes guideline=====		=====7. Points to deal with elsewhere, outside the dashes guideline=====
Line 1,339:		Line 1,371:
	*'''Agree''' ] ] 12:34, 19 July 2011 (UTC)		*'''Agree''' ] ] 12:34, 19 July 2011 (UTC)
	* '''Agree''' – Image filenames are not part of "style", but I don't care if they're in or out at this point. ] (]) 14:58, 19 July 2011 (UTC)		* '''Agree''' – Image filenames are not part of "style", but I don't care if they're in or out at this point. ] (]) 14:58, 19 July 2011 (UTC)

			;Response in the final draft
			* Done. We must follow up with changes elsewhere in MOS, for this and the other points that were to be moved outside the dash guideline. <font color="blue"><big>N</big><small>oetica</small></font><sup><small>]</small></sup> 10:42, 20 July 2011 (UTC)

	=====8. Any points that have been missed in the above=====		=====8. Any points that have been missed in the above=====
Line 1,354:		Line 1,389:
	::::It’s time to stop dumping on PMA. His style tends to be a hard-to-ignore one-man band. We all know that. In the past, too much has been made of his opposition and he has—in my opinion—had influence wildly in excess of head count. There’s been back & forth finger pointing and accusations that the other side has been operating… uhm… ''cheatfully''. The Good Ship Major Malfunction has sailed. PMA is ''just one voice.'' He’s stated his opinion: fine, thank you very much; time to move on. If a consensus can’t be made here despite his opposition, then there one or more shortcomings in Noetica’s proposal that need to be ironed out in order to get more editors singing from the same sheet of music. Noses back to the grind stone please. ] (]) 05:16, 20 July 2011 (UTC)		::::It’s time to stop dumping on PMA. His style tends to be a hard-to-ignore one-man band. We all know that. In the past, too much has been made of his opposition and he has—in my opinion—had influence wildly in excess of head count. There’s been back & forth finger pointing and accusations that the other side has been operating… uhm… ''cheatfully''. The Good Ship Major Malfunction has sailed. PMA is ''just one voice.'' He’s stated his opinion: fine, thank you very much; time to move on. If a consensus can’t be made here despite his opposition, then there one or more shortcomings in Noetica’s proposal that need to be ironed out in order to get more editors singing from the same sheet of music. Noses back to the grind stone please. ] (]) 05:16, 20 July 2011 (UTC)
	* Though I still have a couple of very strong disagreements about a few points (and possibly the procedure at arriving at them), I stress again that the overall effort is a great job. ] (]) 05:10, 20 July 2011 (UTC)		* Though I still have a couple of very strong disagreements about a few points (and possibly the procedure at arriving at them), I stress again that the overall effort is a great job. ] (]) 05:10, 20 July 2011 (UTC)

			;Response from Noetica
			* Thanks! Now can we just ''settle'' this damn thing? It's been going for months. I don't know about others, but I'm exhausted. Just ''compromise'', yeah? '''I myself have strong disagreements with the draft I have made.''' But it works. You will not find a more considered, more complete, more sensitive solution to this hardest of problems in modern punctuation. Not on the web; not anywhere. And we did it together. <font color="blue"><big>N</big><small>oetica</small></font><sup><small>]</small></sup> 10:42, 20 July 2011 (UTC)

			=== Final draft 1: please endorse, or comment ===
			I present what I am calling "Final draft 1" for the dashes section. It responds to suggestions made in the preceding subsection, where I have now enumerated the changes and responded to all concerns. Changes are marked in this new draft by underlining, and in one case by striking through. '''To see the new draft, click on "Show", at the right:'''
			{\| class="navbox collapsible collapsed" style="text-align: left; border: 0px; margin-top: 0.2em;"
			\|-
			! style="background-color: #aaffaa;" \| '''Final draft 1'''
			\|-
			\|
			<big><big><big>'''Dashes'''</big></big></big>
			{{shortcut\|MOS:DASH\|WP:DASH}}

			Two forms of dash are used on Misplaced Pages: ''']''' (–) and ''']''' (—). Type them in as <code>&ndash</code> (–) and <code>&mdash</code> (—); or click on them to the right of the "Insert" tab under the edit window; or see ].
			*<s>Use hyphens, never dashes, in filenames of images, sounds, or other included media.</s>
			*When a dash is used in the title of an article (or any other page), there should be a ] from a hyphenated version: {{xt\|]}} redirects to the article {{xt\|]}}.

			Sources use dashes in varying ways, but for consistency and clarity Misplaced Pages adopts the following principles.

			<big><big>'''Punctuating a sentence (em or en dashes)'''</big></big>
			{{shortcut\|MOS:EMDASH\|MOS:SENTENCEDASH\|WP:EMDASH\|WP:MDASH\|WP:SENTENCEDASH\|}}

			Dashes are often used to mark divisions within a sentence: in pairs (''parenthetical dashes'', instead of parentheses or pairs of commas); or singly (perhaps instead of a colon). They may also indicate an abrupt stop or interruption, in reporting direct speech.

			There are two options. Use one or the other consistently in an article.

			;1. Unspaced em dash
			*{{xt\|Another "planet" was detected—but it was later found to be a moon of Saturn.}}

			Or:

			;2. Spaced en dash
			*{{xt\|Another "planet" was detected – but it was later found to be a moon of Saturn.}}

			Do not use spaced em dashes.
			{{!xt\|Another "planet" was detected — but it was later found to be a moon of Saturn.}}

			Dashes can clarify the sentence structure when there are already commas or parentheses, or both.
			*{{xt\|We read them in chronological order: Descartes, Locke, Hume—but not his ''Treatise'' (it is too complex)—and Kant.}}

			Use dashes sparingly. More than two in a single sentence makes the structure unclear; it takes time for the reader to see which dashes, if any, form a pair.
			*{{xt\|The birds—at least the ones Darwin collected—had red and blue feathers.}}
			*{{xt\|"Where is the—", she said, but then realized she held it in her hand.}}
			{{!xt\|First in the procession—and most spectacularly—came the bishops—then the other clergy.}}

			<big><big>'''En dashes: other uses'''</big></big>
			{{shortcut\|MOS:ENDASH\|MOS:NDASH\|WP:ENDASH\|WP:NDASH}}

			<u>The ] (–) has other roles, beyond its use as a sentence-punctuating dash (see immediately above). It is often analogous to the hyphen (see the section ]), which ''joins components'' more strongly than the en dash; or the slash (see the section ]), which ''separates alternatives'' more definitely. Consider the exact meaning when choosing between these three. En dashes are used in four ways.</u>

			;1. In ranges that might otherwise be expressed with ''to'' or ''through''
			*{{xt\|pp. 211–19}};   {{xt\|64–75%}};   {{xt\|the 1939–45 war}}
			Do not mix en dashes with prepositions like ''between'' and ''from''.
			*{{xt\|450–500 people}}
			{{!xt\|between 450–500 people}}; {{xt\|between 450 and 500 people}}
			{{!xt\|from 450–500 people}}; {{xt\|from 450 to 500 people}}
			<u>If negative values are involved, an en dash might be confusing. Use words instead.</u>
			{{!xt\|−10–10}}; {{xt\|−10 to 10}}
			{{!xt\|the drop in temperature was 5°–−13°}}; {{xt\|the drop in temperature was from 5° to −13°}}
			The en dash in a range is always unspaced, except for times and dates (or similar cases) when the components already include at least one space.
			{{!xt\|23 July 1790–1 December 1791}};    {{!xt\|*14 May–2 August 2011}}
			*{{xt\|23 July 1790 – 1 December 1791}};    {{xt\|14 May – 2 August 2011}}
			*{{xt\|10:30 pm Tuesday – 1:25 am Wednesday}};   {{xt\|Christmas Day – New Year's Eve}};   <u>{{xt\|Christmas 2001 – Easter 2002}}</u>
			*{{xt\|1–17 September}};   {{xt\|February–October 2009}};   {{xt\|1492? – 7 April 1556}}
			*{{xt\|Best absorbed were wavelengths in the range 28 mm – 17 m.}}

			;2. In compounds when the connection might otherwise be expressed with ''to'', ''versus'', ''and'', or ''between''
			Here the relationship is thought of as parallel, symmetric, equal, oppositional, or at least involving ''separate or independent elements''. The components may be nouns, adjectives, verbs, or any other <u>independent</u> part of speech. Often if the components are reversed there would be little change of meaning.
			*{{xt\|boyfriend–girlfriend problems}};   {{xt\|the Paris–Montpellier route}};   {{xt\|a New York–Los Angeles flight}}
			*{{xt\|iron–cobalt interactions}}; the components are parallel and reversible; iron and cobalt retain their identity
			{{!xt\|an iron–roof shed}}; ''iron'' modifies ''roof'', so use a hyphen: {{xt\|an iron-roof shed}}
			{{!xt\|the poet's mentor–muse}}; not separate persons, so use a hyphen: {{xt\|the poet's mentor-muse}}
			*{{xt\|red–green colorblind}}; red and green are separate independent colors, not mixed
			{{!xt\|blue–green algae}}; a blended, intermediate color, so use a hyphen: {{xt\|blue-green algae}}
			{{!xt\|Franco–British rivalry}}; <u>"Franco", is a ''combining form'', not independent; use a hyphen: {{xt\|Franco-British rivalry}}</u>
			*{{xt\|France–Britain rivalry}};   {{xt\|French–British rivalry}}
			*{{xt\|a 51–30 win}};   {{xt\|a six–two majority decision}};   <u>{{xt\|the Lincoln–Douglas debates}}</u>
			*{{xt\|an Italian–Swiss border crossing}}; but {{xt\|an Italian-Swiss newspaper}}, for Italian-speaking Swiss
			*{{xt\|the Uganda–Tanzania War}};   {{xt\|the Roman–Syrian War}};   {{xt\|the east–west runway}}
			*{{xt\|diode–transistor logic}};   {{xt\|the analog–digital distinction}};   {{xt\|a carbon–carbon bond}}
			*{{xt\|a pro-establishment–anti-intellectual alliance}}
			*{{xt\|Singapore–Sumatra–Java shipping lanes}}
			*{{xt\|the ballerina's rapid walk–dance transitions}};   {{xt\|a male–female height ratio of 1.2}}
			A slash or some other alternative may occasionally be better to express a ratio, especially in technical contexts (see ] below).
			*{{xt\|the protein–fat ratio}}  or  {{xt\|the protein/fat ratio}},  or even  {{xt\|the protein-to-fat ratio}}
			An en dash is not used for a hyphenated personal name.
			*{{xt\|Lennard-Jones potential}} with a hyphen: named after John Lennard-Jones
			An en dash ''is'' used for the names of two or more people in a compound.
			*{{xt\|the Seifert–van Kampen theorem}};   {{xt\|the Seeliger–Donker-Voet scheme}};   {{xt\|the Alpher–Bethe–Gamow theory}}
			*{{xt\|Comet Hale–Bopp}} or just {{xt\|Hale–Bopp}} (discovered by Hale and Bopp)
			Following the dominant convention, a hyphen is used in compounded place names and language names, not an en dash.
			*{{xt\|Guinea-Bissau}};   {{xt\|Austria-Hungary}}
			*{{xt\|an old Mon-Khmer dialect}};   {{xt\|Niger-Congo phonology}}

			The en dash in all of the compounds above is unspaced.

			;3. <u>Instead of a hyphen, when applying a prefix to a compound that includes a space</u>
			*<u>{{xt\|ex–prime minister Thatcher}}</u>;   {{xt\|pre–World War II aircraft}}
			<u>Use this punctuation when the construction must be retained—for example in a transcription of a speech, or in a heading that is already chosen as optimal. Otherwise recasting is better.</u>
			*<u>Keep: ] (a Misplaced Pages article)
			*Best to recast the two examples above: {{xt\|former prime minister Thatcher}}; {{xt\|aircraft before World War II}}</u>
			<u>Very awkward: {{!xt\|the mother had post–difficult birth health problems}}; recast as {{xt\|the mother had health problems after a difficult birth}}</u>

			The en dash in all of the compounds above is unspaced.

			;4. To separate items in certain lists
			Spaced en dashes are used within parts of certain lists. Here are two examples:
			* Pairing performers with instruments.
			**{{xt\|James Galway – flute; Anne-Sophie Mutter – violin; Maurizio Pollini – piano.}}
			* Showing track durations on a CD.
			**{{xt\|The future – 7:21; Ain't no cure for love – 6:17; Bird on the wire – 6:14.}}

			----
			\|}
			<font color="blue"><big>N</big><small>oetica</small></font><sup><small>]</small></sup> 10:42, 20 July 2011 (UTC)

			==== Suggested procedure ====
			# Editors, please review the draft, comparing it with the previous one and checking the comments I make above about changes.
			# Consider carefully the need to yield on some points; we ''all'' have had to do that. Consider the value of this draft for the Project.
			# Note errors, omissions, or ''final small fixes'' in the subsection below, in orderly and considerate brevity.
			# If you absolutely must object to anything, do so ''soon'' and ''clearly'', proposing a ''precise solution'', rather than calling vaguely for something to be redrafted.
			# Remember that we have been at this for months, and that we are four days overdue already. Eight weeks (effectively) ought to have been enough time to settle all the issues.
			# Please have your say within 24 hours from now. After 24 hours, I will take whatever next step is appropriate (since I am used to dealing with this, I might as well be the one to carry it through). And we can get a completed version incorporated into WP:MOS.

			==== Endorsements, and final points to fix ====


	== Dash confusion ==		== Dash confusion ==

Revision as of 10:42, 20 July 2011

Skip to table of contents

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.

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

Discussions on this page often lead to previous arguments being restated. Please read recent comments, look in the archives, and review the FAQ before commenting. Restarting a debate that has already been settled constitutes disruptive editing, tendentious editing, and "asking the other parent", unless consensus changes.

view · edit Frequently asked questions

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

Why does the Manual of Style recommend straight (keyboard-style) instead of curly (typographic) quotation marks and apostrophes (i.e., the characters " and ', instead of “, ”, ‘, and ’)‍? Users may only know how to type in straight quotes (such as " and ') when searching for text within a page or when editing. Not all Web browsers find curly quotes when users type straight quotes in search strings. Why does the Manual of Style recommend logical quotation? This system is preferred because Misplaced Pages, as an international and electronic encyclopedia, has specific needs better addressed by logical quotation than by the other styles, despite the tendency of externally published style guides to recommend the latter. These include the distinct typesetters' style (often called American, though not limited to the US), and the various British/Commonwealth styles, which are superficially similar to logical quotation but have some characteristics of typesetters' style. Logical quotation is more in keeping with the principle of minimal change to quotations, and is less prone to misquotation, ambiguity, and the introduction of errors in subsequent editing, than the alternatives. Logical quotation was adopted in 2005, and has been the subject of perennial debate that has not changed this consensus. Why does the Manual of Style differentiate the hyphen (-), en dash (–), em dash (—), and minus sign (−)? Appropriate use of hyphens and dashes is as much a part of literate, easy-to-read writing as are correct spelling and capitalization. The "Insert" editing tools directly below the Misplaced Pages editing window provide immediate access to all these characters. Why does the Manual of Style recommend apostrophe+s for singular possessive of names ending in s? Most modern style guides treat names ending with s just like other singular nouns when forming the possessive. The few that do not propose mutually contradictory alternatives. Numerous discussions have led to the current MoS guidance (see discussions of 2004, 2005, 2005, 2006, 2006, 2007, 2008, 2008, 2008, 2009, 2009, 2009, 2012, 2013, 2015, 2016, 2017, 2017, 2017, 2018, 2018, 2019, 2021, 2022). Why doesn't the Manual of Style always follow specialized practice? Although Misplaced Pages contains some highly technical content, it is written for a general audience. While specialized publications in a field, such as academic journals, are excellent sources for facts, they are not always the best sources for or examples of how to present those facts to non-experts. When adopting style recommendations from external sources, the Manual of Style incorporates a substantial number of practices from technical standards and field-specific academic style guides; however, Misplaced Pages defaults to preferring general-audience sources on style, especially when a specialized preference may conflict with most readers' expectations, and when different disciplines use conflicting styles.

Template:MOS/R

Manual of Style

	This page falls within the scope of the Misplaced Pages:Manual of Style, a collaborative effort focused on enhancing clarity, consistency, and cohesiveness across the Manual of Style (MoS) guidelines by addressing inconsistencies, refining language, and integrating guidance effectively.Manual of StyleWikipedia:WikiProject Manual of StyleTemplate:WikiProject Manual of StyleManual of Style
	This page falls under the contentious topics procedure and is given additional attention, as it closely associated to the English Misplaced Pages Manual of Style, and the article titles policy. Both areas are subjects of debate. Contributors are urged to review the awareness criteria carefully and exercise caution when editing.
	For information on Misplaced Pages's approach to the establishment of new policies and guidelines, refer to WP:PROPOSAL. Additionally, guidance on how to contribute to the development and revision of Misplaced Pages policies of Misplaced Pages's policy and guideline documents is available, offering valuable insights and recommendations.

Suggested abbreviations for referring to style guides User:Noetica/StyleGuideAbbreviations1

editSee also
Misplaced Pages talk:Writing better articles
Misplaced Pages talk:Article titles
Misplaced Pages talk:Quotations
Misplaced Pages talk:Manual of Style (dates and numbers)
Misplaced Pages talk:Manual of Style/quotation and punctuation

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.

Compromise on WP:REFPUNC?

Misplaced Pages talk:Manual of Style (footnotes)#Compromise on WP:REFPUNC? -- Jeandré, 2011-03-21t12:46z

RFC: Should all subsidiary pages of the Manual of Style be made subpages of WP:MOS?

Resolved – Noetica 08:10, 6 July 2011 (UTC)

The proposal in this widely advertised RFC has received solid support. There have been only 2 votes against, arguing 1) that the initiative would not be worth the effort, and 2) that WP:ACCESS should not be a part of the Manual of Style – a matter that may be pursued independently. There have been 21 support votes. Discussion should therefore focus on implementation, to be followed by action. Noetica 08:10, 6 July 2011 (UTC)

Misplaced Pages's Manual of Style (MOS) has one central page (Misplaced Pages:Manual of Style, or WP:MOS). But there are other pages: Misplaced Pages:Manual of Style (dates and numbers), Misplaced Pages:Manual of Style (footnotes), Misplaced Pages:Manual of Style (Hawaii-related articles), and many more.

Should all of those other pages be moved so that they are subpages of Misplaced Pages:Manual of Style? An example, after the proposed change: Misplaced Pages:Manual of Style/Hawaii-related articles. The question has come up at the central talkpage (WT:MOS). This would be a large structural change; so it needs thorough examination with wide participation from the Community.

NOTE: The RFC remains open, but there is now a new section on the page:

Subpage structure for the Manual of Style: implementation.

Submissions are requested there also.

Noetica 03:49, 13 June 2011 (UTC)

Resources for this RFC

Links to earlier discussions
#Sub-pages (on the present page) Misplaced Pages talk:Manual of Style/Archive 115#Rationalizing MoS page titles (section 96) Misplaced Pages talk:Manual of Style/Archive 95#Style Rationalisation Project (section 14) Misplaced Pages talk:Manual of Style/Archive 110#A proposal (section 4) Misplaced Pages talk:Manual of Style/Archive 53#Requested moves of subtopics (section 3) User talk:Wavelength/Archive 3#Hi—WT:MOS/x and WT:MOS(x) (section 25) User talk:Wavelength/Archive 3#A robust index for the MoSes? (section 34) Misplaced Pages:Village pump (proposals)/Archive 50#Move all Misplaced Pages: namespace pages in (disambiguation) format to /subpage format

Links to earlier discussions

#Sub-pages (on the present page)
Misplaced Pages talk:Manual of Style/Archive 115#Rationalizing MoS page titles (section 96)
Misplaced Pages talk:Manual of Style/Archive 95#Style Rationalisation Project (section 14)
Misplaced Pages talk:Manual of Style/Archive 110#A proposal (section 4)
Misplaced Pages talk:Manual of Style/Archive 53#Requested moves of subtopics (section 3)
User talk:Wavelength/Archive 3#Hi—WT:MOS/x and WT:MOS(x) (section 25)
User talk:Wavelength/Archive 3#A robust index for the MoSes? (section 34)
Misplaced Pages:Village pump (proposals)/Archive 50#Move all Misplaced Pages: namespace pages in (disambiguation) format to /subpage format

Links to 82 affected pages

Example of full title: Misplaced Pages:Manual of Style (abbreviations)

57 pages with "Template:MoS-guideline" at the top

________________________________________

(abbreviations) talk

(accessibility) talk

(anime- and manga-related articles) talk

(article message boxes) talk

(biographies) talk

(Canada-related articles) talk

(capital letters) talk

(captions) talk

(chemistry) talk

(comics) talk

(command-line examples) talk

(dates and numbers) talk

(disambiguation pages) talk

(embedded lists) talk

(film) talk

(footnotes) talk

(France & French-related) talk

(Hawaii-related articles) talk

(icons) talk

(infoboxes) talk

(Iran-related articles) talk

(Ireland-related articles) talk

(Japan-related articles) talk

(Latter Day Saints) talk

(lists of works) talk

(mathematics) talk

(medicine-related articles) talk

(military history) talk

(music) talk

(music samples) talk

(novels) talk

(Philippine-related articles) talk

(Poland-related articles) talk

(pronunciation) talk

(proper names) talk

(record charts) talk

(road junction lists) talk

(self-references to avoid) talk

(Singapore-related articles) talk

(snooker) talk

(spelling) talk

(stand-alone lists) talk

(stringed instrument tunings) talk

(tables) talk

(television) talk

(text formatting) talk

(titles) talk

(trademarks) talk

(trivia sections) talk

(visual arts) talk

(words to watch) talk

(writing about fiction) talk

25 other pages (miscellaneous; some inactive)

________________________________________

(Arabic) talk

(British Isles-related articles) talk

(Computer articles) talk

(diagrams and maps) talk

(Ethiopia-related articles) talk

(glossaries) talk

(Iceland-related articles) talk

(images) talk

(India-related articles) talk

(Islam-related articles) talk

(Korea-related articles) talk

(Kosovo-related articles) talk

(Malaysia-related articles) talk

(MUSTARD) talk

(national varieties of English) talk

(Persian) talk

(philosophy) talk

(photography) talk

(Portuguese-related articles) talk

(Psychology) talk

(superscripts and subscripts) talk

(Thailand-related articles) talk

(U.S. legal citations) talk

(United Kingdom-related articles) talk

(Misplaced Pages books) talk

Summary of the case for subpages

There are very many pages in the Manual of Style, making it extremely difficult to find or survey particular guidelines – to consult them, let alone edit them. Even with tailored search options that we now have (see at the right side of WP:MOS), it is hard to find everything one needs, or to know where to contribute in talkpages.
Making all subsidiary pages strict subpages of WP:MOS has technical advantages. For example, with subpages it is much easier to find text using Google's highly refined searches. At present this can only be achieved in a limited and unreliable way using a combination of Google (or other external search facilities) and Misplaced Pages's internal search utility.
The change would capitalise on the underlying file structure. Just one simple example: it automatically provides a link at the top of each subpage back to WP:MOS itself – helping everyone, especially editors unfamiliar with the workings of the Manual of Style.
The use of subpages in WP project pages is permitted by WP:Subpages, and subpages are already used successfully in the RfC pages, Arbitration pages, and Reference Desk pages.
The unmonitored spread of guidelines can be efficiently checked in the course of this structural reform. See discussion of implementation, below on this page.
The implementation will provide an opportunity to review and refactor existing subpages (old drafts, misplaced discussions, surveys, or disused extensions of MOS pages). They can be relocated appropriately, by consultation. This will keep the overall structure rational and clear. Searches currently pick up material from those non-guidelines; in the new structure, they would not.

Summary of the case against subpages

The convention established in WP article space is that subpages are prohibited. The primary reason is that many pages belong to two or more categories, and hence multiple "parent pages" exist for any given article. The article space relies on (in lieu of subpages) Categories, Lists, and NavBoxes to implement hierarchical organization. WP project pages should conform to that convention (prohibiting subpages) for the sake of consistency throughout WP.
Unlike navigation by template, navigation by subpage will mean that rejected, proposed, and {{historic}}, pages will be a permanent part of this structure. For example, without subpages, if Misplaced Pages:Manual of Style (national varieties of English) is rejected, we take it out of the navbox and forget about it. With subpages, Misplaced Pages:Manual of Style (national varieties of English) will be permanently found on any search of subpages, forever more. There are already approximately 25 such rejected/proposed/historic MOS pages.

Votes for subpages

Support as RFC proposer (acting on the initiative of User:Mclay1). Noetica 04:03, 13 June 2011 (UTC)
Support. WP's software provides for a hierarchy of pages, and the MOS structure is a natural fit for that. The breadcrumb at the top of each sub-page makes for a more consistent navigational aid. WP:Reference desk uses the mechanism well, and as long as we don't use a forward-slash in any sub-page name, I don't have a problem with the MOS using sub-pages. GFHandel ♬ 04:44, 13 June 2011 (UTC)
Support as original proposer. Renaming to the standard format of sub-pages will provide a nagivational link back to the main MOS page at the top and has no drawbacks. McLerristarr | Mclay1 05:34, 13 June 2011 (UTC)
Support. Per GFHandel. Having thought about it for a while, I see significant advantages. The MoS subpages tend to be sprawling and poorly coordinated, and we owe editors and readers better. Tony (talk) 16:11, 14 June 2011 (UTC)
Support: McLerristarr | Mclay1 above took the words right out of my mouth. –CWenger (^ • @) 19:59, 14 June 2011 (UTC)
Support. Per discussion below (under NavBox topic). WP project space already does use subpages for RFC, etc, and it is useful. --Noleander (talk) 15:29, 20 June 2011 (UTC)
Support absolutely, as I've said prior to this. There are a ton of benefits to organizing these pages in a manner in which the MediaWiki software is able to recognize them as sub-pages to the main MoS page.— V = IR (Talk • Contribs) 01:02, 22 June 2011 (UTC)
Support - I proposed it a while ago, and my reasoning can be found at Misplaced Pages:Village pump (proposals)/Archive 50#Move all Misplaced Pages: namespace pages in (disambiguation) format to /subpage format. There was a small consensus, but I guess I got bored or distracted. I would really love to see this happen. ▫ JohnnyMrNinja 04:26, 22 June 2011 (UTC)
Support per what I said the last time. ― A. di M._plé 16:52, 22 June 2011 (UTC)
Why not? Although Special:PrefixIndex works either way. /ƒETCH COMMS / 03:20, 23 June 2011 (UTC)
Support - Better search suggestions in search box. Marcus Qwertyus 04:02, 23 June 2011 (UTC)
Sure If someone wishes to make these changes... Doc James (talk · contribs · email) 00:50, 25 June 2011 (UTC)
Yes, sure, fine, sounds reasonable. Herostratus (talk) 03:25, 25 June 2011 (UTC)
Yes, please. Imho this is a great idea, for the reasons laid out above, and also because even though it may seem like just a technicality, I'm convinced that having the subguidelines as subpages would automatically translate into greater efforts of streamlining it into one coherent guideline system (which it still isn't, quite), and an overall much less scattered perception. --87.79.230.11 (talk) 12:11, 25 June 2011 (UTC)
Support, as it will make it easier to browse the manual of style sub-pages. Thus improving usability. Dodoïste (talk) 13:26, 25 June 2011 (UTC)
Week support. Not a huge change and I'm quite partial to it; but the positives (which over-exaggerate search benefits) seem to slightly outweigh the negatives (which over-exaggerate the impairments from confusion). I guess WP won't fall apart either way, but having sub-pages is a little neater. — HELLKNOWZ ▎TALK 14:32, 25 June 2011 (UTC)
Support. Guidance has grown like a coral. A good review is needed so it can be made coherent and easier to access for users. Lightmouse (talk) 15:10, 25 June 2011 (UTC)
Support Greg L (talk) 18:11, 25 June 2011 (UTC)
Support —James • 3:16pm • 05:16, 26 June 2011 (UTC)
Support. A sensible fix. Neutrality 22:15, 27 June 2011 (UTC)
Support. Seems like a better way to keep things in order. --Coemgenus (talk) 11:22, 29 June 2011 (UTC)

Votes against subpages

Is it really any easier to manage or find text in subpages than it is the current way? Explain and I'll reconsider. Probably this all came out in the previous discussion, but I wasn't following it; someone needs to make a more convincing case before I would support such a disruptive change. Surely having a link back to the main page is easy to implement in the current scheme, without this change. OK, I'm semi-convinced that it might help, so I withdraw my vote against. Dicklyon (talk) 04:12, 13 June 2011 (UTC)
I sympathize with the proposal: I've been lost in MOS hell, stumbling around in a maze, annoyed and confused. Reform is sorely needed. But - speaking as a WP user - I expect important pages to have NavBoxes at the top, and I expect those NavBoxes to contain a comprehensive list of all related articles. A hierarchy can be clearly shown in the NavBox. We even have a format choice of either upper-right corner, or a full-width Navbox (such as at the top of WP:AN). The current MOS NavBox is (no offense to those who have worked on it) could be improved quite a bit. Shouldn't we work on improving the NavBox first and see if it can address the needs? And if it fails, then resort to subpages? Following a discussion (below) I've become convinced that the subpages may provide some searching benefits; plus the hierarchical organization is a natural way to organize data, so I'm withdrawing my Opposition. --Noleander (talk) 17:49, 16 June 2011 (UTC)

Can see no practical benefit: surely vast majority of navigation is by links, searches and categories, not by guessing an address to type into address box. Probably little real harm in it, just seems pointless. Kevin McE (talk) 07:32, 13 June 2011 (UTC)
The Manual of Style, in spite of what I think of it in practise, is perfectly titled. It's compiled in the wiki-equivalent of an instruction manual, and is intended to increase internal stylistic consistency. But there is one page that does not fit under that umbrella. WP:ACCESS is primarily focussed on making sure we don't discriminate against the visually impaired; to treat, or give the impression that it should be treated as supplimentary stylistic guideline would be entirely wrong. Equally significantly, ACCESS itself being the trunk of a hierarchal structure makes a lot of sense: the trunk itself should be easy for a novice to understand, and where appropriate there should be more detailed how-to subpages, such as the data table tutorial. There are several other pages that could be consolidated into ACCESS subpages, if that's the direction of travel. If this does go ahead – and I certainly see the overall merit – ACCESS should be removed from the MoS, and revert to being a stand-alone guideline. —W F C— 16:47, 25 June 2011 (UTC)

Neutral statements

Haven't really thought it through and have no strong opinion. Will let you all decide. I thnk my only take was to have subpages of article space content (as daughter articles feel too disconnected from mother articles...and the rest of the web has subpages of content...look at any corporate site). That said there were arguments that a daughter might have two mothers or whatever...plus I guess wiki is harder to be structured with than a thought out integrated website.TCO (talk) 06:50, 22 June 2011 (UTC)
Perhaps this is addressed somewhere in the voluminous discourse, but I think what a fuller reorganization is needed more than simply moving pages about. 1) I have no objection in principle to the core MOS pages being moved to be sub-pages of MOS. 2) I think there are many specialized MOS pages where the scope is limited to articles within the purview of a Wikiproject. I think this pages should be considered as supporting documentation for that Wikiproject rather than subpages of the core MOS. A consistent naming convention for such project-specific style guides might help to clarify both the scope of application and the relation with the core MOS (i.e., in cases of conflict , the core MOS takes precedence). older ≠ wiser 00:57, 25 June 2011 (UTC)
My only concern is that we not try to shoehorn a "one size fits all" approach to every disparate subject. From archaeology to comic books to Olympic swimming to what-have-you, I believe we need to retain the flexibility that we now have to address the unique specifics of each general topic.--Tenebrae (talk) 03:00, 25 June 2011 (UTC)
It really doesn't matter... (Also, there's an identical issue with notability guidelines, for what it's worth.) ╟─Treasury Tag►Subsyndic General─╢ 13:21, 25 June 2011 (UTC)
Why not? In fact, since these pages don't follow any of the other customs of Misplaced Pages space, give them a separate MOS namespace - it will make it even easier to know what to ignore. Making it easier for careless dogmatists to watch these pages would ordinarily be a disadvantage; but with luck this will make MOS even less functional; and so less harmful. Septentrionalis PMAnderson 00:29, 26 June 2011 (UTC)
I'm tending towards older/wiser and Tenebrae's comments 2 and 3 above. Something like Text Formatting or Dates & Numbers is really part of the M of S's core, and you'll often find similar clusters of editors discussing them, so it's probably best to make them slashed sub-pages. Even though different editors discuss Accessibility, that's also a core topic that might benefit from being attached as a sub-page . Style guides for things like naval topics, heraldry & vexillology, railways, royal & noble titles, comic books, Hawai'i, and French-related articles, on the other hand, inhabit a kind of limbo between general style guidance and the WikiProjects to which they're most closely allied. While I'm not sure what convention or even category would best suit them, I'm leaning against making them subpages of an already-huge set of general guidelines. —— Shakescene (talk) 00:47, 26 June 2011 (UTC)
MediaWiki pages are organized based on a flat hierarchy, though it has the functionality (via features such as Special:PrefixIndex) to organize pages as anything except. However, I won't complain if it ultimately serves as a better method of organization, so I'm not going to oppose at this time. –MuZemike 04:24, 27 June 2011 (UTC)

Discussion and replies

Dicklyon, how is moving the pages disruptive? We're not going to delete the resultant redirects so no links will be broken. Can you actually see any drawbacks to this move or are just opposing it because you don't see enough positives? McLerristarr | Mclay1 06:24, 13 June 2011 (UTC)

Maybe disruption is the wrong way to characterize it. It seems like a lot of work and churn. So explain what it buys us. Dicklyon (talk) 14:47, 13 June 2011 (UTC)

Is that list intended as an alternative to summarizing the case above? Doesn't work for me. Dicklyon (talk) 23:22, 13 June 2011 (UTC)

For clarity, I am revising my (unindented) message of 19:26, 13 June 2011 (UTC).—Wavelength (talk) 23:48, 13 June 2011 (UTC)

This is an extract of what I said at User talk:Wavelength/Archive 3#Hi—WT:MOS/x and WT:MOS(x) (section 25) .

The "Misplaced Pages talk" namespace has many pages beginning with "Misplaced Pages talk:Manual of Style (". Apparently some of those are subpages of "Misplaced Pages talk" pages, whereas others are talk pages of "Misplaced Pages" subpages.

—Wavelength (talk) 15:07, 14 June 2011 (UTC)

Noetica, I wish that I could be more definite about supporting your proposal, but the time that I have spent in pondering it has not fully cleared away my uncertainties about all the ramifications. Nevertheless, if one or more of the supporters is or are prepared to move (rename) all of the pages (including talk pages) affected by a supportive decision, and to update all incoming links to those pages (except those on archived talk pages), then I have no objection to the changes. Therefore, I am abstaining from expressing either support or opposition. Please consider the (possible) ramifications of the extract which I posted in my message of 15:07, 14 June 2011 (UTC). Also, what counts as consensus remains to be seen.
—Wavelength (talk) 19:35, 14 June 2011 (UTC)

Heavens, that's all right! Who knows? I might change my mind also. But so far just new benefits from this idea keep occurring to me. I intend to say more later on; I'm too busy to give it my full attention right now. Noetica 01:04, 15 June 2011 (UTC)

Is there any mechanism that makes subpages easier to find than what we have now? Something like a dir (ls) command? Dicklyon (talk) 01:46, 15 June 2011 (UTC)

Sorta kinda, apparently; prefix:WP:Manual of Style/ seems to do it. If the Search box had a nearby Help link, one would not need to guess at Help:Searching or Help:Search to find the search help. This would seem an easy thing to add . . . It’s hard to say how much of an advantage this would be over prefix:WP:Manual of Style with the current setup, but it’s hard to see how it would make things harder—hierarchical namespaces seem to have proven more effective than linear namespaces in many applications. JeffConrad (talk) 03:20, 15 June 2011 (UTC)

And I'm not saying it makes things harder; I just don't see how it makes things any easier. It's not different from a linear namespace if that's all the mechanism we have. Hierarchies are better when there are tools for navigating them. Where's the Finder? Dicklyon (talk) 06:20, 15 June 2011 (UTC)

Finder??? Misplaced Pages is not a Mac . . . I’m not sure the hierarchical namespace would make things easier to find via search, but it could make things easier for those who maintain the files. One of the great features of Unix (which actually runs Macs) was the hierarchical file system, copied by most OSs that still survive. I could scarcely imagine trying to keep track of files on my computer with a linear namespace. I’ve avoided comment on this so far because I haven’t been following the discussion, and recognize that a little knowledge can be dangerous. JeffConrad (talk) 08:42, 15 June 2011 (UTC)

I am not sufficiently familiar with the Misplaced Pages MOS to make specific suggestions, but I am, however, very familiar with the Associated Press Stylebook, and I think they've established an effective organizational system in their MOS for journalists, and this stylebook has pretty much become the industry standard for journalism. I believe they also have electronic/web/iPhone editions. It might be appropriate to look to these for ideas on organization. --Jp07 (talk) 15:41, 30 June 2011 (UTC)

Here is a list (from here) of subpages of talk pages in a form similar to that of talk pages of subpages.

Subpages of talk pages
Misplaced Pages talk:Manual of Style/Alpha Archive 1 Misplaced Pages talk:Manual of Style/Alpha Archive 2 Misplaced Pages talk:Manual of Style/Alpha Archive 3 Misplaced Pages talk:Manual of Style/Alpha Archive 4 Misplaced Pages talk:Manual of Style/Alpha Archive 5 Misplaced Pages talk:Manual of Style/Archive ("See also") Misplaced Pages talk:Manual of Style/Archive ("U.S." or "American") Misplaced Pages talk:Manual of Style/Archive (Poll: always use "U.S." and Oxford commas?) Misplaced Pages talk:Manual of Style/Archive (abbreviations and acronyms) Misplaced Pages talk:Manual of Style/Archive (capitalization) Misplaced Pages talk:Manual of Style/Archive (chemical names) Misplaced Pages talk:Manual of Style/Archive (citing references) Misplaced Pages talk:Manual of Style/Archive (external links) Misplaced Pages talk:Manual of Style/Archive (foreign languages) Misplaced Pages talk:Manual of Style/Archive (gender-neutral pronouns) Misplaced Pages talk:Manual of Style/Archive (jguk's changes) Misplaced Pages talk:Manual of Style/Archive (names) Misplaced Pages talk:Manual of Style/Archive (numbers) Misplaced Pages talk:Manual of Style/Archive (places) Misplaced Pages talk:Manual of Style/Archive (punctuation) Misplaced Pages talk:Manual of Style/Archive (quotes and quote marks) Misplaced Pages talk:Manual of Style/Archive (quotes and quote marks 2) Misplaced Pages talk:Manual of Style/Archive (sexuality) Misplaced Pages talk:Manual of Style/Archive (ships as "she") Misplaced Pages talk:Manual of Style/Archive (spaces after a full stop/period) Misplaced Pages talk:Manual of Style/Archive (style guide errata) Misplaced Pages talk:Manual of Style/Archive (visual design) Misplaced Pages talk:Manual of Style/Archive 1 Misplaced Pages talk:Manual of Style/Archive 2 Misplaced Pages talk:Manual of Style/Archive 3 Misplaced Pages talk:Manual of Style/Archive 4 Misplaced Pages talk:Manual of Style/Archive 5 Misplaced Pages talk:Manual of Style/Archive 6 Misplaced Pages talk:Manual of Style/Archive 7 Misplaced Pages talk:Manual of Style/Archive 8 Misplaced Pages talk:Manual of Style/Archive 9 Misplaced Pages talk:Manual of Style/Archive 10 ... Misplaced Pages talk:Manual of Style/Archive 50 ... Misplaced Pages talk:Manual of Style/Archive 100 ... Misplaced Pages talk:Manual of Style/Archive 122 Misplaced Pages talk:Manual of Style/Archive Box Misplaced Pages talk:Manual of Style/Archive Directory Misplaced Pages talk:Manual of Style/Dashes Misplaced Pages talk:Manual of Style/Dashes archive 1 Misplaced Pages talk:Manual of Style/Draft Trim Misplaced Pages talk:Manual of Style/Draft Trim/Archive 1 Misplaced Pages talk:Manual of Style/FAQ Misplaced Pages talk:Manual of Style/Proposed MOS talk page standards Misplaced Pages talk:Manual of Style/quotation and punctuation

Subpages of talk pages

...

Misplaced Pages talk:Manual of Style/Archive 50

...

Misplaced Pages talk:Manual of Style/Archive 100

...

—Wavelength (talk) 16:18, 20 June 2011 (UTC)

How searching would be improved with subpages

Let's suppose I want to find guidelines that mention hard spaces; so I set out to search with this string (just to pick one way, not the best!):

"hard space" OR " " OR "nonbreaking space" OR "non-breaking"

How do I get all the guidelines I'm after? Let's try four ways:

Reports of four searches
1. Do this search using Misplaced Pages's internal utility (the parentheses make no difference; just for clarity): ("hard space" OR " " OR "nonbreaking space" OR "non-breaking") prefix:Misplaced Pages:Manual of Style Try it. It yields 17 hits; they are all in WP:MOS, another page with the prefix "Misplaced Pages:Manual of Style", or a subpage of any of those pages. Two problems: first, we weren't after pages like these: Misplaced Pages:Manual of Style/Register Misplaced Pages:Manual of Style/Draft trim (November 2004) Misplaced Pages:Manual of Style (dates and numbers)/Three proposals for change to MOSNUM Misplaced Pages:Manual of Style (dates and numbers)/Date Linking RFC And second, the search finds pages that don't meet the criteria, like Misplaced Pages:Manual of Style (road junction lists) which includes none of the search terms. (The search seems to have captured a use of ` ` in the code for that page.) 2. Do this search using Misplaced Pages's internal utility (that is, just add " (" at the end of search 1): ("hard space" OR " " OR "nonbreaking space" OR "non-breaking") prefix:Misplaced Pages:Manual of Style ( We now get just 12 hits, all of them Manual of Style pages other than WP:MOS. That's the first problem: we wanted WP:MOS also. The second problem is that we get subpages like this: Misplaced Pages:Manual of Style (Ireland-related articles)/Ireland disambiguation task force The third problem: once again, that page does not include any of the search terms anyway. 3. Do this search using Misplaced Pages's internal utility (that is, just add "/" at the end of search 1): ("hard space" OR " " OR "nonbreaking space" OR "non-breaking") prefix:Misplaced Pages:Manual of Style/ We now get just 4 hits: Misplaced Pages:Manual of Style/Register (section Non-breaking spaces) Misplaced Pages:Manual of Style/Draft trim (November 2004) (section Spaces after a full stop/period) Misplaced Pages:Manual of Style/(dates and numbers)/proposed revision Misplaced Pages:Manual of Style/proposal (section Spaces after the end of a sentence) That's not going to help much. 4. Do this search using Google: ("hard space" OR " " OR "nonbreaking space" OR "non-breaking") site:http://en.wikipedia.org/Wikipedia:Manual_of_Style We get 5 hits: Misplaced Pages:Manual of Style Misplaced Pages:Manual of Style/Register Misplaced Pages:Manual of Style/(dates and numbers)/proposed revision Misplaced Pages:Manual of Style/proposal Misplaced Pages:Manual of Style/Draft trim (November 2004) This Google search is both good and bad. Each of the hits includes one of the desired terms, but only WP:MOS and its strict subpages are searched.

Reports of four searches

1. Do this search using Misplaced Pages's internal utility (the parentheses make no difference; just for clarity):

("hard space" OR " " OR "nonbreaking space" OR "non-breaking") prefix:Misplaced Pages:Manual of Style

Try it. It yields 17 hits; they are all in WP:MOS, another page with the prefix "Misplaced Pages:Manual of Style", or a subpage of any of those pages.

Two problems: first, we weren't after pages like these:

Misplaced Pages:Manual of Style/Register

Misplaced Pages:Manual of Style/Draft trim (November 2004)

Misplaced Pages:Manual of Style (dates and numbers)/Three proposals for change to MOSNUM

Misplaced Pages:Manual of Style (dates and numbers)/Date Linking RFC

And second, the search finds pages that don't meet the criteria, like Misplaced Pages:Manual of Style (road junction lists) which includes none of the search terms. (The search seems to have captured a use of   in the code for that page.)

2. Do this search using Misplaced Pages's internal utility (that is, just add " (" at the end of search 1):

("hard space" OR " " OR "nonbreaking space" OR "non-breaking") prefix:Misplaced Pages:Manual of Style (

We now get just 12 hits, all of them Manual of Style pages other than WP:MOS. That's the first problem: we wanted WP:MOS also. The second problem is that we get subpages like this:

Misplaced Pages:Manual of Style (Ireland-related articles)/Ireland disambiguation task force

The third problem: once again, that page does not include any of the search terms anyway.

3. Do this search using Misplaced Pages's internal utility (that is, just add "/" at the end of search 1):

("hard space" OR " " OR "nonbreaking space" OR "non-breaking") prefix:Misplaced Pages:Manual of Style/

We now get just 4 hits:

Misplaced Pages:Manual of Style/Register (section Non-breaking spaces)

Misplaced Pages:Manual of Style/Draft trim (November 2004) (section Spaces after a full stop/period)

Misplaced Pages:Manual of Style/(dates and numbers)/proposed revision

Misplaced Pages:Manual of Style/proposal (section Spaces after the end of a sentence)

That's not going to help much.

4. Do this search using Google:

("hard space" OR " " OR "nonbreaking space" OR "non-breaking") site:http://en.wikipedia.org/Wikipedia:Manual_of_Style

We get 5 hits:

Misplaced Pages:Manual of Style

Misplaced Pages:Manual of Style/Register

Misplaced Pages:Manual of Style/(dates and numbers)/proposed revision

Misplaced Pages:Manual of Style/proposal

Misplaced Pages:Manual of Style/Draft trim (November 2004)

This Google search is both good and bad. Each of the hits includes one of the desired terms, but only WP:MOS and its strict subpages are searched.

Results like this weigh heavily in favour of our proposed restructuring. If all of the Manual of Style were in Misplaced Pages:Manual_of_Style or a subpage of that, a Google search would retrieve all the target guidelines. (I would also want all the present overgrowth of subpages moved aside, so that only actual style pages were subpages of WP:MOS.) At present, all the guidelines dealing with hard spaces can be found only by painstaking and error-prone composite searching. What's more, Google searches are far more powerful than internal Misplaced Pages searches in other ways, beyond what we can explore here.

So the proposed change would make development far easier; and we could customise far better search boxes for users wanting to consult the Manual than we can now. If that involves using Google, so be it. In any case, it's time we recognised the larger potential of Misplaced Pages's style guidelines. They are useful (and beginning to be used) offsite as well. Google already loves Misplaced Pages! Let's harness Google to be an even better resource for retrieving material on Misplaced Pages.

I may have missed something; and my searches might be inept! But in that case, searching currently requires considerable sophistication. Under the proposed change, it would not. All of the above applies (with changed details) to Manual of Style talkpages too. Subpages, properly regimented, would make it much easier to track down previous discussion, no matter what corner of what talkpage or archive it might have fallen into – without false positive hits.

Noetica 10:44, 15 June 2011 (UTC)

Were I doing such a search with Unix-like utilities, I would probably try something like

grep -lE "(hard space| |nonbreaking space|non-breaking)" Manual_of_Style/*

More complex approaches could be used for more complex directory hierarchies if the volume of data was sufficient to warrant the added complexity. Knowing nothing about the internals of the wiki search engine, I’m reluctant to suggest that this example is directly applicable, but it does seem reasonable.

Ultimately, it’s a matter of what is required to find the desired information. That several of us with considerable experience on Misplaced Pages have had to think about this suggests that it’s just too darn hard to find many things, including help and general policies as well as items in the MOS. If it’s challenging for veterans, imagine what it’s like for newbies. Reorganization of the MOS hierarchy may be only one part of a possible solution, but if it really would make a significant improvement, it’s something that can be done without much help from others (e.g., changes to mediaWiki). JeffConrad (talk) 00:57, 16 June 2011 (UTC)

Question Under the current categories I can't see any MoS which is in two categories, however what would happen if such a situation was to arise? Gnevin (talk) 23:39, 21 June 2011 (UTC)

NavBox improvement

Above, I make the argument that the MOS Navbox Template:Style could be vastly improved, and would help address some of the concerns that gave rise to this proposal. I'm willing to make some of the improvements to the NavBox. But, I'd also like to hear from the "supporters": What issues will a great NavBox not resolve? In other words, assuming that the MOS NavBox and MOS Categories were excellent in their design and scope, what benefits - if any - would subpages bring to readers? --Noleander (talk) 17:57, 16 June 2011 (UTC)

FYI: I've solicited comments at the template Talk page regarding the proposal to add more detail/depth to the MOS NavBox. --Noleander (talk) 18:06, 16 June 2011 (UTC)

Good that you've joined the discussion, Noleander. I've explored your draft of an improved template. Just now I can't see how it conflicts with the RFC proposal here. Wouldn't these reforms work well together? The conversion to subpages is a partial solution, enabling efficient and rational searches. But so, I think, is what you put forward just a partial solution, addressing a different feature of a complex problem (with no improvement toward rationalising searches, per se). Is it just that you prefer consideration of one idea at a time, or is there some other reason for your present opposition? I'm inclined to support both initiatives. Noetica 22:44, 16 June 2011 (UTC)

Yes, perhaps the two proposals (NavBox expansion & supages) would work well together. It may be that they are entirely orthogonal and complementary. To be candid: I'm a bit fuzzy on the search benefits that the subpage proposal provides (I read some of the search examples above, but I could not see the point the examples were making). Can you (or anyone) provide a very specific example of how the subpages would improve the search capability for a typical user? (a user that is not a black-belt in search syntax). After I get clarity, I may retract my "Oppose" !vote. --Noleander (talk) 23:54, 16 June 2011 (UTC)

Long discussion of Noleander's question
Sure, Noleander. Just look at the search I introduce in the subsection before this one, and how it is handled by four currently available options. None works well. Each picks up, or misses, all sorts of things. The Google option (search 4) would work perfectly: if we implemented subpages (and cleared away ad hoc proposal subpages and the like – separate provision could easily be made for those). Any questions? Just ask, here. Noetica 00:00, 17 June 2011 (UTC) Okay ... I tried #4 in Google, and got the indicated results. But what I'm missing is: What is the scenario that a typical WP user/editor would benefit? Is this benefit only available within Google? Or would the WP "Search" field at the top of WP pages also benefit? Or is this benefit aimed primarily at black-belt WP editors that are searching for very specific data? (contrasted with novice editors just trying to get MOS guidance without leaving WP to go to Google). Or am I just backwards because I use WP "Search" field rather than Google (I must have missed the memo :-) --Noleander (talk) 00:05, 17 June 2011 (UTC) Three points in response to Noleander: 1. The needs of "black-belt" editors are important in their own right. For example, when they want to track down earlier discussion of guidelines (in any talkpage for the Manual of Style); or fine details of the existing guidelines that are spread across 57+ pages. Accurate searching is essential to efficient development of guidelines – including especially any effort to reduce their chaotic expansion. Editors who are advanced in these things will quite happily resort to Google, which is very powerful. 2. A reformed file structure will mean that "white- and yellow-belt" editors can more easily find things too. Try this simpler search within Misplaced Pages, if you can't see yourself looking for mentions of hard space: capitals prefix:Misplaced Pages:Manual of Style That gives you 11 hits, but 3 of them are drafts or other offshoots: not style guidelines. (For many searches the proportion would be worse, with false positives too.) Now try the nearest equivalent search on Google: capitals site:http://en.wikipedia.org/Wikipedia:Manual_of_Style That gives you 4 hits, but 3 are mere drafts and offshoots. If we had subpages for all pages of the Manual of Style (and only for those), Google would let us find things accurately. With substantial improvements to Misplaced Pages's own system, we might also get the same benefits as Google offers: but as a prerequisite, we'd still need a reformed file structure. Either way, even for simple searches the subpage proposal paves the way for better things. And if the change were managed with care, there would be no loss of present capabilities. 3. Since non-black-belt editors may not feel comfortable even with the simpler searches, we make customised search boxes (like at the top of this talkpage, and in the template you are working on). But we can't do that effectively without the reforms proposed here (along with some collateral fixes). Noetica 01:15, 17 June 2011 (UTC) Okay, I'm getting swayed. Just a few more questions: (1) are there any other project pages in WP that already use this subpage convention (e.g. all pages related to, say, Mediation, are subpages of some top-level Mediation page); and (2) assuming the answer to (1) is "no", then would this proposal also be appropriate for other project pages within WP? Or is "Manual of Style" the only topic that this subpage proposal is sensible for? (3) Would this subpage proposal also be beneficial for all the pages listed in Template:naming conventions (that is, they would be under the top-level Naming page)?--Noleander (talk) 02:21, 17 June 2011 (UTC) In the most general sense, very many subpages of project pages can be found in http://en.wikipedia.org/search/?title=Special%3AAllPages&from=%21&to=&namespace=4. —Wavelength (talk) 03:16, 17 June 2011 (UTC) 1. Misplaced Pages:Reference desk has no activity in itself, but has one subpage for each specific reference desk, like Misplaced Pages:Reference desk/Language for Language. Archives are another branch, to contain huge numbers of daily archives for all the desks, like Misplaced Pages:Reference desk/Archives/Computing/2007 July 9. There is one central talkpage, with redirects from each desk's talkpage: Misplaced Pages talk:Reference desk/Language redirects to Misplaced Pages talk:Reference desk. There are a few add-ons that I have not discussed. It works! And it's easily searchable. I don't know about other areas of the Project. Anyone know? Wavelength's link gives a way to search for such things; for example, you can see the first of the zillions of Reference desk pages here. 2. 3. I thought a little about Naming conventions. I suspect something like this RFC proposal would help there; and possibly other areas could benefit too. Here and everywhere, the details should be worked out by experts – that includes some of us, and a few technical types (some of whom walk in our midst!). Of course, it should all happen with open scrutiny and consultation. This has not been the case with other technical developments, I fear. Be swayed! Noetica 03:36, 17 June 2011 (UTC)

Long discussion of Noleander's question

Sure, Noleander. Just look at the search I introduce in the subsection before this one, and how it is handled by four currently available options. None works well. Each picks up, or misses, all sorts of things. The Google option (search 4) would work perfectly: if we implemented subpages (and cleared away ad hoc proposal subpages and the like – separate provision could easily be made for those). Any questions? Just ask, here. Noetica 00:00, 17 June 2011 (UTC)

Okay ... I tried #4 in Google, and got the indicated results. But what I'm missing is: What is the scenario that a typical WP user/editor would benefit? Is this benefit only available within Google? Or would the WP "Search" field at the top of WP pages also benefit? Or is this benefit aimed primarily at black-belt WP editors that are searching for very specific data? (contrasted with novice editors just trying to get MOS guidance without leaving WP to go to Google). Or am I just backwards because I use WP "Search" field rather than Google (I must have missed the memo :-) --Noleander (talk) 00:05, 17 June 2011 (UTC)

Three points in response to Noleander:

1. The needs of "black-belt" editors are important in their own right. For example, when they want to track down earlier discussion of guidelines (in any talkpage for the Manual of Style); or fine details of the existing guidelines that are spread across 57+ pages. Accurate searching is essential to efficient development of guidelines – including especially any effort to reduce their chaotic expansion. Editors who are advanced in these things will quite happily resort to Google, which is very powerful.

2. A reformed file structure will mean that "white- and yellow-belt" editors can more easily find things too. Try this simpler search within Misplaced Pages, if you can't see yourself looking for mentions of hard space:

capitals prefix:Misplaced Pages:Manual of Style

That gives you 11 hits, but 3 of them are drafts or other offshoots: not style guidelines. (For many searches the proportion would be worse, with false positives too.) Now try the nearest equivalent search on Google:

capitals site:http://en.wikipedia.org/Wikipedia:Manual_of_Style

That gives you 4 hits, but 3 are mere drafts and offshoots. If we had subpages for all pages of the Manual of Style (and only for those), Google would let us find things accurately. With substantial improvements to Misplaced Pages's own system, we might also get the same benefits as Google offers: but as a prerequisite, we'd still need a reformed file structure. Either way, even for simple searches the subpage proposal paves the way for better things. And if the change were managed with care, there would be no loss of present capabilities.

3. Since non-black-belt editors may not feel comfortable even with the simpler searches, we make customised search boxes (like at the top of this talkpage, and in the template you are working on). But we can't do that effectively without the reforms proposed here (along with some collateral fixes).

Noetica 01:15, 17 June 2011 (UTC)

Okay, I'm getting swayed. Just a few more questions: (1) are there any other project pages in WP that already use this subpage convention (e.g. all pages related to, say, Mediation, are subpages of some top-level Mediation page); and (2) assuming the answer to (1) is "no", then would this proposal also be appropriate for other project pages within WP? Or is "Manual of Style" the only topic that this subpage proposal is sensible for? (3) Would this subpage proposal also be beneficial for all the pages listed in Template:naming conventions (that is, they would be under the top-level Naming page)?--Noleander (talk) 02:21, 17 June 2011 (UTC)

In the most general sense, very many subpages of project pages can be found in http://en.wikipedia.org/search/?title=Special%3AAllPages&from=%21&to=&namespace=4.

—Wavelength (talk) 03:16, 17 June 2011 (UTC)

1. Misplaced Pages:Reference desk has no activity in itself, but has one subpage for each specific reference desk, like Misplaced Pages:Reference desk/Language for Language. Archives are another branch, to contain huge numbers of daily archives for all the desks, like Misplaced Pages:Reference desk/Archives/Computing/2007 July 9. There is one central talkpage, with redirects from each desk's talkpage: Misplaced Pages talk:Reference desk/Language redirects to Misplaced Pages talk:Reference desk. There are a few add-ons that I have not discussed. It works! And it's easily searchable. I don't know about other areas of the Project. Anyone know? Wavelength's link gives a way to search for such things; for example, you can see the first of the zillions of Reference desk pages here.

3. I thought a little about Naming conventions. I suspect something like this RFC proposal would help there; and possibly other areas could benefit too. Here and everywhere, the details should be worked out by experts – that includes some of us, and a few technical types (some of whom walk in our midst!). Of course, it should all happen with open scrutiny and consultation. This has not been the case with other technical developments, I fear.

Be swayed!

Noetica 03:36, 17 June 2011 (UTC)

See Misplaced Pages:WikiProject Council/Guide/Task forces.

—Wavelength (talk) 06:31, 17 June 2011 (UTC)

Fair enough. I've struck-out my Oppose !vote. My final comment is: If this is implemented, it should be widely publicized at the Village Pump, etc so that others could consider implementing it in other realms within WP (e.g. the naming conventions articles). Consistency is a good thing, and it's just not right for a couple of areas to use subpages (Reference desk & MOS) and others to not use it. --Noleander (talk) 13:31, 17 June 2011 (UTC)

Subpages of project pages are already widely implemented (Misplaced Pages:Subpages) and widely known (http://stats.grok.se/en/latest/Wikipedia:Subpages).

—Wavelength (talk) 15:01, 17 June 2011 (UTC)

Thanks for that link ... I see that now (for instance, specific RfC subgroups are subpages of the main RfC page, as in Misplaced Pages:Requests for comment/History and geography). But subpages are prohibited in article space, so they are a bit alien to many editors: it is a bit peculiar that they are prohibited in article space, but permitted in project space: but I can see the reasoning (the key distinction is that many articles belong in 2 or more hierarchies, but project pages often belong to just one). In any case, I like hierarchical organizations, and using subpages for MOS is sensible. --Noleander (talk) 15:23, 17 June 2011 (UTC)

Fine, Noleander. I hope you will stay with this and contribute as we proceed. I want to look at your work on the template; it seems that several coordinated efforts are best. Somehow we have to manage this inevitable spread of guidelines – for those developing them as well as for those using them. See the list of affected pages (in a navbox above). Even that took some work to establish. We cannot easily be sure that it covers all pages of interest, or when new pages will need to be added to to it.

Now, are you inclined to modify the "Case against", since your change of heart? I suppose it could stay, until someone opposing comes along and works on it. (You might consider a support vote, of course ☺.) Noetica 00:01, 18 June 2011 (UTC)

Thanks for the reminder: I've rewritten the "Case against" to capture the only sensible argument against I can think of ... mostly for the sake of justice and balance :-) But I do support it, and will so !vote. Indpendently, the MOS Navbox improvement is still a good idea, and (baring any objections) I'll implement that in a day or two. --Noleander (talk) 15:28, 20 June 2011 (UTC)

Navigation by address box

In his vote against subpages, Kevin McE said the following.

Can see no practical benefit: surely vast majority of navigation is by links, searches and categories, not by guessing an address to type into address box. Probably little real harm in it, just seems pointless.

As I understand the proposal, it does not require "guessing an address to type into address box". However, one who knows the name of a subpage could add to what is already in the address box, for example, by adding /dates and numbers to Misplaced Pages:Manual of Style, and producing Misplaced Pages:Manual of Style/dates and numbers. That option constitutes one more benefit to from the ~~proposal~~ proposed changes.
—Wavelength (talk) 18:22, 17 June 2011 (UTC)

Technically, spaces are converted to underscores in the address bar, but the procedure can be used for navigation.
—Wavelength (talk) 19:01, 17 June 2011 (UTC)

Can we have a new namespace? MOS:Chemistry for example. The Chemistry MOS has numerous sub-pages already, and it seems a mouthful to have WP:MOS/Chemistry/Compound classes , for example. --Rifleman 82 (talk) 06:23, 25 June 2011 (UTC)

Rifleman, the issue of what to do about "legacy" structuring, such as the Chemistry MOS subpages you mention, would be better dealt with in Implementation, below. The reworking will have to take account of all such local solutions, in setting up an overall structure that can be navigated and searched by all. There are probably lessons to learn from what editors have done before. I note that some of the Chemistry subpages are genuine components of that MOS; but some of them are mere drafts, right? That may need sorting out, for reliable searching at least. Noetica 04:33, 26 June 2011 (UTC)

Thanks for getting back. To my knowledge, only Misplaced Pages:Manual_of_Style_(chemistry)/Elements/draft is a draft. We never got around to integrating WP:ELEMENTS' work. All the other level 1 subpages have been discussed and ratified by the current members of WP Chemistry/Chemicals before going live. --Rifleman 82 (talk) 04:26, 27 June 2011 (UTC)

Comments on neutral statements

Here are some remarks about neutral statements (see above) made so far. I hope this will encourage others to address them if they see the need. In some cases we can clear up misconceptions, or answer the inevitable concerns that have arisen. I would like to thank the editors for their generally constructive observations; we do need to take note of them. Noetica 04:21, 26 June 2011 (UTC)

On Statement 1

TCO seems to favour this sort of exercise, but expresses some general reservations about the details of the structure. I think we have to get on with filling out the details (see Implementation, below), so that such concerns can be allayed. Noetica 04:21, 26 June 2011 (UTC)

On Statement 2

Older ≠ wiser wants "a fuller reorganization than simply moving pages about", and fills in some details, while thinking that "perhaps this is addressed somewhere in the voluminous discourse." I think it is addressed to some extent. We certainly need to keep our dialogue clearly signposted, so newcomers can follow the trend. The need for some sort of hierarchy is noted; but I would add that nothing in this proposal seeks to overwhelm or diminish the needs of special areas. It's basically a very rational restructuring, one of whose benefits is that we can harmonise existing guidelines for the Project. Harmony is not hegemony! Noetica 04:21, 26 June 2011 (UTC)

On Statement 3

Tenebrae raises a similar and perfectly understandable concern: "that we not try to shoehorn a 'one size fits all' approach to every disparate subject". Again I would stress that the aim is to restructure, rationalise, and review. Many editors are worried about the unmanaged spread of guidelines; some speak of "instruction creep". They can be reassured that this initiative will counter that tendency, if we keep focused as we proceed. Noetica 04:21, 26 June 2011 (UTC)

On Statement 4

TreasuryTag reminds editors that "it really doesn't matter." Myself, I will concede that the heat death of the universe is a larger problem; but we must choose our battles, right? Enough people can see the merit of this restructuring for us to take it seriously – and to spend time getting it right. Noetica 04:21, 26 June 2011 (UTC)

On Statement 5

Noetica 04:21, 26 June 2011 (UTC)

On Statement 6

Shakescene resumes some themes from 2 and 3. At least initially, though, the pages targeted are the 57 advertising themselves as part of the Manual of Style (see the left column of the Links to 82 affected pages). There are further questions about the rest, and about naming conventions for example. I think the restructure provides an opportunity to examine these issues progressively and methodically, with the fullest consultation. Sure, some pages will clearly cohere, and make up the Manual of Style; and the Manual should be rationally organised and consistent. That does not deprive special areas of their special provisions; nor does it deny non-Manual pages their own role in the Project. Noetica 04:21, 26 June 2011 (UTC)

Procedural points

As proposer of this RFC I have refactored subsections for clarity and order. And I have moved material – putting some into well-labelled navboxes where this will keep things readable, especially for anyone coming new to the discussion. I have assumed that no one minds; and others can do the same, of course. Please raise any concerns in this subsection. Noetica 23:50, 17 June 2011 (UTC)

Noetica, if you still wish to convert the subsidiary pages of WP:MOS to subpage format, and if you do not see any problem involving subpages of talk pages, then please do proceed with the conversion at your convenience (possibly with the assistance of one or more helpers), because there seems to be no substantial objection from anyone at this time. If the proposal languishes without implementation, then this will have been another case of time and thought expended, perhaps wastefully. Let us declare consensus for this proposal.

—Wavelength (talk) 19:37, 21 June 2011 (UTC)

Agreed, Noetica. I assume that you are unfamiliar on a previous proposal on this topic (Misplaced Pages:Village pump (proposals)/Archive 50#Move all Misplaced Pages: namespace pages in (disambiguation) format to /subpage format) which went the same way. I believe all points to the negative have been soundly addressed, and general opinions range from "great" to "no clear benefit", which is as good as you can get on EN. ▫ JohnnyMrNinja 12:15, 22 June 2011 (UTC)

Very well, I have set up a new section below on this page: #Subpage structure for the Manual of Style: implementation.
Go to it! Keep it active but orderly, and let's work out how best to do this thing. Noetica 04:33, 23 June 2011 (UTC)

We have fairly clear guidance against refactoring without consent; I do not consent. This practice inhibits discussion, and prevents agreement on anything than simple accept/decline. If this practice continues, as here, I shall ask that Noetica be blocked. Septentrionalis PMAnderson 13:52, 28 June 2011 (UTC)

Our "fairly clear guidance" says "Relocation of material to different sections or pages where it is more appropriate", and in this case, the appropriate material for each section was labeled. You may debate those labels, but I can't imagine Noetica being blocked for his paragraph organization, and I can't imagine how suggesting a block can even be considered constructive. One would ordinarily leave alone material accompanied by a threat like "explain themselves to an admin", but such language is getting to be a habit. Art LaPella (talk) 22:08, 28 June 2011 (UTC)

Separate namespace is a much better idea

Apologies for the new section: this is a huge RFC and it's difficult to know where to put it. PMAnderson is the only person so far to have suggested simply co-opting ] as an entirely new namespace for these pages. I think this is fundamentally the best solution by far:

Searching is even easier (search by namespace is trivial)
A clear sign that the MoS is a fundamental part of Misplaced Pages
Far shorter full page titles
All the benefits of the sub-page approach as well

Am I missing a reason why this has apparently not been raised more often? Are there any drawbacks to this approach?

Chris Cunningham (user:thumperward) - talk 10:52, 28 June 2011 (UTC)

I like the idea too, CC. I guess I'm not alone in being put off by the motivation offered for it by PMAnderson!

I see no drawbacks; but I had thought it would be difficult to get accepted. In some quarters the Manual is not well received. Some of the mud sticks, and unfair as that is, it is a reality we must contend with.

Now, given the huge support we see for the present RFC, we could simply close it now as resolved in favour of the proposal. We could suspend the separate Implementation discussion for now (see below), while someone starts a similar RFC testing the namespace proposal. If you want to do that, I would certainly want to assist. I DO propose a structured, orderly approach like the one I instituted for the present RFC. "Huge" it may be; but far easier to navigate than the usual, I submit. Noetica 11:28, 28 June 2011 (UTC)

For the record, I also support the idea of creating a new namespace specifically for the MoS. However, that's for later on. In the meantime, we should do this proposal.
— V = IR (Talk • Contribs) 21:31, 8 July 2011 (UTC)

Subpage structure for the Manual of Style: implementation

The subpage RFC currently under discussion on this page has overwhelming support. No one speaks strongly against it so far, and some editors urge that we go ahead and do it. I agree that we should press on with this valuable reform; but we need to discuss the details of its implementation. So here I sketch a systematic way to proceed, taking full advantage of what the change will allow.

Proposed stages

(Stages 1 and 2 can be undertaken at the same time; but the elements of Stage 2 will require careful sequencing.)

Stage 1: clear the way

Existing miscellaneous subpages of Misplaced Pages:Manual_of_Style (hereafter called WP:MOS) to be relocated

This is a necessary step in the overall process, since the present structure is a mess. See this list of current subpages:

Many are simple redirects, like Misplaced Pages:Manual_of_Style/(mathematics) which redirects to Misplaced Pages:Manual_of_Style (mathematics).
Some are vestiges of defunct discussions or initiatives: Misplaced Pages:Manual_of_Style/(biographies)/Survey_on_Style-Prefixed_Honorary_Titles/Ratification.
Some have a vital role to play, and should be preserved in a suitable location: Misplaced Pages:Manual of Style/Register.
At least one is a current draft of guidelines for consideration: Misplaced Pages:Manual of Style/Dash draft.

I propose that we discuss options for relocating all such non-guideline subpages, both existing and future.

Discussion of Stage 1

The discussions should be moved to Misplaced Pages talk:, where they will supplement the talk archive searches (they should have been there in the first place). Redirects cause no harm, provided they point to the correct source. Some might find them annoying when looking at list of subpages, so they can be deleted (provided all inbound links are edited). Pages such as Misplaced Pages:Manual of Style/Register are merely an index of decisions made by consensus in relation to the MoS. These serve as a supplementary index of sorts, so I don't think the current location is inappropriate, even if it is slightly inconsistent. Drafts should be located at either the future title and marked as "proposed", or in user-space. If editors wish community involvement with their draft then it should be in the logical proposed location, so that everyone can easily guess its location, can easily stumble across it, and can automatically understand its purpose. If the proposer does not wish outside involvement, then standard practice is to keep it in user space until it is ready. So Misplaced Pages:Manual of Style/Dash draft should be at Misplaced Pages:Manual of Style/Dashes. ▫ JohnnyMrNinja 05:24, 23 June 2011 (UTC)

For clarity, this is the list of all pages beginning with "Misplaced Pages:Manual of Style". This includes current subpages and (proposed) future subpages. ▫ JohnnyMrNinja 05:31, 23 June 2011 (UTC)

Johnny, the matter may not be entirely straightforward. (See a related concern I have just added about exact naming, for Stage 2 below.) We need to think through how Misplaced Pages searching will work, using the prefix system. And also web-searching (such as with Google), which is only going to get more important, given Misplaced Pages's preeminence on the web. Did you mean exactly what you wrote: "Misplaced Pages:Manual of Style/Dash draft should be at Misplaced Pages:Manual of Style/Dashes"? Please amend for accuracy, or clarify.

Your list is handy. See also Links to 82 affected pages in the RFC above.

Noetica 07:56, 23 June 2011 (UTC)

About Dashes, what I meant exactly was that it should be at the proposed title, whatever that ends up being in future. Worst case you could have "/Dashes (draft)", but I still think the exact proposed title is ideal. Are you questioning me about Dashes specifically, or about formatting of all MoS titles? BTW, in contrast to the link I posted above, this is all pages beginning with "Misplaced Pages:Manual of Style/". The ending "/" makes a big difference, and this is what we can base the pre-built searches off of. ▫ JohnnyMrNinja 17:02, 23 June 2011 (UTC)

To minimise possible ructions with local editors, could the moves be preceded by a notice on the talk pages? Tony (talk) 12:01, 23 June 2011 (UTC)

Stage 2: progressively move Manual of Style pages

Existing pages to be moved one by one, with full consultation, and checked for consistency in the process

As a great advantage of the subpage proposal, we can take the opportunity to check each new candidate subpage for internal consistency (and general quality), consistency with WP:MOS itself, and consistency with others that have already been brought in as subpages. This was not proposed in the RFC; but it was always clear that the proposal was part of a larger purpose: to contain the unexamined and disorderly proliferation of guidelines. I am proposing that we set up that reform now, while there is an opportunity. We can take our time. Reform has been tried before, but too hastily and without a clear enough mechanism. Along the way it may be found that pages can be merged (mutually, or into WP:MOS); or that some can be abandoned. I suggest we start with WP:MOSNUM, because it is obviously of major importance. WP:MOS itself, and all other pages of the Manual, must be in accord with its provisions.

We also need to discuss the exact form that titles of subpages should have, to keep things absolutely clear and simple, and especially to optimise searching under both Misplaced Pages- and web-searching.

I propose that we discuss an order of procedure for these careful progressive moves; or if people take a different view, for alternative ways to implement the proposal approved in the RFC.

Discussion of Stage 2

Support. Consistency between the main MoS and subpages/subsections actually strikes me as more important than the subpage/subsection issue itself. We should plan to do this regardless of the outcome of the rest of the current proposal. Darkfrog24 (talk) 13:43, 23 June 2011 (UTC)

Well, because of the political turbulence affecting this page it's hard for people to focus on practical details. Unfortunately WP:MOS is yet again under protection. We can't easily adjust pages for consistency under such conditions. I suppose it's a matter of "watch this space", for now. Noetica 22:24, 30 June 2011 (UTC)

Deferring implementation

We have achieved consensus for the proposal to convert subsidiary pages of the Manual of Style to subpages of WP:MOS (see details of the RFC above), but the implementation has not been thoroughly discussed. I now suggest that we defer it for a short time, until the state of WP:MOS and conditions on this talkpage are suitable. I intend soon to post a suggested schedule for this. Noetica 09:01, 6 July 2011 (UTC)

What are we waiting for?
— V = IR (Talk • Contribs) 21:36, 8 July 2011 (UTC)

I have suggested that we wait a short time "until the state of WP:MOS and conditions on this talkpage are suitable". As I suggest above, that may mean:

WP:MOS (as hub of the new structure) is unprotected and conveniently editable.
Conditions on this talkpage are suitable: that is, it is not embroiled in perennial politics over the basics (what is a manual of style? should we have one?), and it is somehow relieved of personal animosity.

That's what I'm waiting for, and I will soon propose a schedule for moving things forward. What are you waiting for, and what are you proposing to do? ☺ Noetica 23:56, 8 July 2011 (UTC)

Well... that's kinda what I wanted to know. If you feel that you're too embroiled in politics to be comfortable doing this, then someone else should step up. I'd be glad to do it myself, but I don't want to step on any toes in the process. Incidentally, the idea that we need to wait for unprotection of this page strikes me as being kinda silly, if only because this proposal really has nothing to do with changes to this page (but, maybe that's just my view).
— V = IR (Talk • Contribs) 01:09, 9 July 2011 (UTC)

Ohms (V = IR), I have said that the page is embroiled in politics; I do not say that I am. My being portrayed that way, and indeed named as an arch-villain ripe for the pillory and a perpetual ban, has little to do with reality. I structured the RFC, and saw to it that the underlying consensus could emerge clearly, all without politics spoiling things, and I would like to continue now with implementation.

No one has objected – or could reasonably object, I think – to progressively monitoring for consistency as pages are brought in as subpages of WP:MOS. But to achieve that, it will be necessary for editors to collaborate in making technical adjustments (at least) to WP:MOS and to the added pages. There is no rush; and we should get it right. That's why I suggest a delay while present large issues are sorted out. (I could point to a problem from inattention in last year's efforts to coordinate MOS pages; it has repercussions even now.)

If you favour a different approach, by all means get editors together, and get on with it! I have no ownership, of course.

Noetica 04:02, 9 July 2011 (UTC)

I don't see what the point of waiting is. This is a fairly simple but long process. I'm going to start moving pages now. McLerristarr | Mclay1 03:57, 11 July 2011 (UTC)

Comment Misplaced Pages's motto is "Be Bold" but not "Be reckless". I would recommend that those undertaking this proposal proceed slowly. Start with just a few pages and look carefully for problems. If no issues are seen, the process can be accelerated. I am concerned about categories mostly. I don't understand exactly how Mediawiki handles parents and children categories for subpages of pages. I hope that those wanting to start this move figure out exactly how Mediawiki does that. Jason Quinn (talk) 12:53, 13 July 2011 (UTC)

Jason, I agree that caution and close scrutiny are needed; and also I suggest monitoring pages for consistency as part of the process (see earlier comments). I see that McLay1 has already moved some pages, including miscellaneous subpages of the sort that I thought we could look at removing altogether, or systematically relocating. And then McLay1 stopped, without reporting to this page. A pity. Still, that's Misplaced Pages! At least there is an unambiguous consensus, and it can be acted upon when editors are interested in addressing implementation more attentively. Just now there is too much other action, so I have not even posted the schedule that I promised. Later, when the weather is more agreeable. Noetica 05:27, 15 July 2011 (UTC)

The hardest part is moving all the talk page archives. As far as I can tell, that's the only thing we have to watch for. McLerristarr | Mclay1 10:46, 19 July 2011 (UTC)

Logical punctuation

I just learned today about the Misplaced Pages style convention for logical punctuation, per MOS:COMMA and MOS:LQ. Could someone please explain the logic behind this rule?

Why is the American-based Misplaced Pages using British punctuation rules? Not only does America have a significantly larger population size (which leads one to logically infer that it also has many more writing professionals), but the American style for commas and quotation marks is also endorsed by the Modern Language Association, the Associated Press, and I believe several other notable organizations (but I don't want to assume and be incorrect).

Correct me if I'm wrong, but the way I see it, we've adopted an uncommon rule -- I had no idea that this comma philosophy even existed -- when I think it's safe to say that a large portion of our writers and editors are Americans who are going to follow the American style, and we're going to have rampant inconsistency as a result.

Perhaps my thoughts make me a close-minded American, but I just don't really see the logic behind it.--Jp07 (talk) 16:17, 30 June 2011 (UTC)

As I said in response to your question on my talk page, logical punctuation has been part of the MOS since it was first put together in 2002. There are other things in the MOS that follow American convention over the British, such as the strong preference for the double quotation mark rather than the single.

In terms of grammar and spelling, by widespread consensus, any of the major national variants of English are acceptable in articles. This has also been in the MOS since the beginning. There are obvious caveats to this (the spelling needs to be consistent within the article, common ground should be sought where possible, words that would be confusing in other dialects should be avoided, etc.) and it's worked fairly well for the last nine years.Cúchullain /c 16:38, 30 June 2011 (UTC)

Sure, I'm not trying to question you at all, and I appreciate your help; I agree that it's best to follow the stylebook as long as that convention is a part of the stylebook, but I think it's also important to note that organizations bound by a stylebook (like the Associated Press) publish new versions. The AP publishes a new stylebook every year to make improvements and changes. I don't think tradition alone is a good reason to follow a rule.

I did review those articles, and I guess I sort of understand the desire to avoid changing an author's content, but can someone give me an example where it would be necessary or even beneficial to know that the author placed a comma or a period at the end of the quote? Do those ever add meaning? I can see it in poetic verse, maybe, but otherwise I can't think of a situation where that's important.

I think it requires a decision between whether it's more important to know where the author placed his punctuation -- I honestly don't think that's important -- or for Misplaced Pages to be consistent. I think it's going to be a battle to be consistent if we stick with logical punctuation.--Jp07 (talk) 16:43, 30 June 2011 (UTC)

Don't try comparing the population of the US to the UK. Many countries in the Commonwealth have English as an official language and many of those use "British" usage rules. For example, India has a lot more people than the US and English is an official language there. Just thoughts. --Airborne84 (talk) 18:04, 30 June 2011 (UTC)

Precisely. We already have agreement on this, at WP:ENGVAR. Septentrionalis PMAnderson 18:11, 30 June 2011 (UTC)

I'm asking for details because I'm not very familiar with this convention, as I've pointed out. As a career writer and editor, I believe that it's best to question the logic behind the conventions that we use, and we should use those conventions that best preserve clarity and consistency. I used to manage a publication, and when a consensus of editors came to the conclusion that a convention needed to be changed, it was, effective immediately.

I have pointed out my bias, and that is why I'm seeking outside input in this forum for discussion.--Jp07 (talk) 18:47, 30 June 2011 (UTC)

Because this page was written by a small coterie of those who want to use it as a tool to make Everybody Do It MY Way.

Logical punctuation has a minor advantage for some readers who do not realize that ," and ." are compound signs in American punctuation - and who care about de minimis details; it has a significant disadvantage in that it is harder to do accurately, and impossible to proof-read.

It would be a great improvement to the encyclopedia to acknowledge that there are two systems, that they both have advantages, and that articles may use either consistently.

Pending agreement on this, we should at least mark that the present text is (as it has been every three months or so since its imposition) disputed. Septentrionalis PMAnderson 18:11, 30 June 2011 (UTC)

I don't think we should look at it as a desire to impose control over other writers and editors. I suppose this "control" is a side effect of a stylebook, but that's not the end goal. The goal is to maintain consistency, which is the only way to achieve a professional product. And although inter-article consistency is definitely a must, best practice is really to maintain the same rules throughout the publication (i.e. all of Misplaced Pages). Whatever is decided, it really would be best to use it all the way throughout.

I think we're trying not to step on toes here, but there is such a thing as too much political correctness. When it interferes with the project's perceived professionalism, and hence its credibility (which is at stake), I think we need to get tough and get over our sensitivities.--Jp07 (talk) 19:15, 30 June 2011 (UTC)

Oh, power shouldn't be the goal; but for a small and turbulent minority, it is.

Nor does MOS achieve professionalism by universal consistency: it doesn't do that now. See WP:CONSISTENCY: we seek consistency within articles, as other publishers do within individual contributions to an anthology; but for some of the most notable differences in English (favor/favour; red, white and blue/red, white, and blue) our guidance is for inconsistency.

Our road to professionalism is accuracy, verifiability, neutrality, clarity; achieving uniformity on quotation marks does little for these, and is at best false advertising without them. Septentrionalis PMAnderson 19:26, 30 June 2011 (UTC)

Um... does anyone else see the inconsistency of talking about achieving a "professional" product when everyone involved in creating it is a volunteer? As long as "anyone can edit" (which is a core concept behind Misplaced Pages) it is unrealistic to kid ourselves about achieving a professional product. Our goal is (and should be) to achieve the best amateur product that we can. Blueboar (talk) 23:00, 30 June 2011 (UTC)

There's a very significant difference between "professional" and "professional standard". Malleus Fatuorum 23:11, 30 June 2011 (UTC)

Still, I don't think an article with major WP:NPOV/WP:OR/WP:V problems but a professional-looking style would be better than the same article with a crappy style. If anything, the latter is less likely to deceive readers. (This is why I don't usually copy-edit articles unless I have at least a vague idea of what they're talking about and know that what they say is at least vaguely plausible.) ― A. di M._plé 23:51, 30 June 2011 (UTC)

And both styles here are professional - they're used by professional proofreaders. Septentrionalis PMAnderson 23:59, 30 June 2011 (UTC)

I was commenting on what Blueboar and Malleus Fatuorum said on a general level, not on this issue in particular. (FWIW, I prefer “logical” quotation myself, but I think both should be allowed, and if the article I'm editing uses traditional American quotation consistently, I leave that alone.) ― A. di M._plé 00:10, 1 July 2011 (UTC)

Thank you.

But does it also hold as a general point? We are rarely dealing with a controversy between professional style and crappy style; we are dealing with points on which there are several professional styles, and some self-appointed maven wants everybody to use only his choice. (Sometimes his choice appears to be something he's made up, but that's another question; even then it's often a rational but unattested invention.) Septentrionalis PMAnderson 00:31, 1 July 2011 (UTC)

I agree with you that both styles are equally professional. The majority of writing professionals, however, look for and expect pervasive consistency in any product. I don't think we should relegate the principle of consistency when it comes from the writing industry.--Jp07 (talk) 03:59, 1 July 2011 (UTC)

We'vw already done so; on spelling, which is far more visible, we've actively rejected consistency; see WP:ENGVAR. On other points where there are two reasonable and wisely used alternatives, we've abandoned it. We're a collaboration. Septentrionalis PMAnderson 23:43, 1 July 2011 (UTC)

I'm an American, and I prefer logical punctuation... This isn't so much of a regional variation as it is a profession one, in my opinion. People in the sciences and engineering tend to use logical punctuation, whereas those in the humanities and the arts seem to prefer more traditional punctuation. Misplaced Pages has a fairly strong foundation in the tech world, so it really shouldn't be that surprising that we seem to prefer logical punctuation.
— V = IR (Talk • Contribs) 23:09, 30 June 2011 (UTC)

Then use it, and let others do otherwise. Septentrionalis PMAnderson 23:59, 30 June 2011 (UTC)

The American style guides were largely constrained by the Network effect, and couldn't change away from the illogical style. Misplaced Pages had a "clean" start, and could get away with adopting its own practices, obviously within reason. It would have been silly to decide that three quote marks was the right way to do quotations. However, given that it is the English Misplaced Pages, rather than the American Misplaced Pages, when confronted with a choice between one rule that made sense, and another rule that made absolutely no sense, and had nothing going for it other that "that's the way we've always done it", deliberately chose to go with the logical rule.

Works for me. If you are a professional writer not at Misplaced Pages, and want to continue using the illogical rule, go for it. I don't.--SPhilbrick T 02:05, 1 July 2011 (UTC)

I don't think the comma rule name calling is really necessary. All I did was ask for a justification, and as far as I see it, I still haven't really got one. Give me a specific justification for this rule aside from Misplaced Pages tradition and the (seeming) desire to deviate from American writing industry tradition simply because it was the tradition.

Thing #1: Just because it's called logical punctuation doesn't necessarily make it more logical than any other rule. You can label anything in the world "logical," but to assume that the label makes it logical is a fallacy. In fact, I see "logical" punctuation as very illogical from a copy editing perspective because it's impossible to maintain consistency, it's (nearly) impossible to check correct usage, and readers are going to perceive errors (real or imagined).

Thing #2: Maybe this is just my perception, but I feel like we're fighting "the way we've always done it" because we can. Is that and should that be a goal of Misplaced Pages?

Thing #3: I would like to see more solid facts in this discussion. I don't have many; that's why I'm here.

I'm not trying to be inflammatory; given my background, I'm simply questioning a policy that I feel could be improved. Please consider my ideas.--Jp07 (talk) 04:01, 1 July 2011 (UTC)

This is my understanding of why logical punctuation is superior (and has nothing to do with my nationality or the way I was taught in school): If the name of a song is in quotation marks (e.g. "Let It Be"), then in a list ("Let It Be", "Here Comes the Sun" and "Hey Jude") it makes more sense to put the comma outside the quotation marks because the comma is not part of the name of the song. In a quote: John Smith stated that "there are not enough bananas". makes more sense if the full stop is not part of the quoted material, otherwise you are altering the quote. Logical punctuation is clearer and cannot be misunderstood, unlike the other system. In my opinion, logical punctuation also looks better. I can't see any advantages to illogical punctuation, unless you personally think it is more aesthetically pleasing, which isn't really important. McLerristarr | Mclay1 05:10, 1 July 2011 (UTC)

Thank you for trying to explain it. My initial point was about copy editing, though -- how would you like to try to copy edit logical punctuation? You would have to look up every single piece of quoted material to check for usage. That is so beyond practical that it's not even funny.

And aside from that "illogical punctuation" isn't illogical simply because the punctuation is inside of the quotation marks; commas don't come at the end of a complete string in English because that's inappropriate usage. And with your quote example, it's not really altering the content by putting a period inside because you can't pronounce the period symbol. It has no sound and no meaning. It is simply present in writing to establish and clarify syntax. There is no period in spoken language. By saying that it changed the quotation, we would have to think that he said "there are not enough bananas period." In which case, we would write that he said "there are not enough bananas PERIOD." The ." means "quote and sentence over; expect a new thought to come at you." It neither contributes to nor detracts anything from the content of the quoted material.

I think it would be best to stop arguing, however, which is most logical (because that could go on forever); we should rather argue which is most useful in practice. I think I have a valid, indisputable point on the copy editing.--Jp07 (talk) 05:34, 1 July 2011 (UTC)

The difficulty of copy-editing is why the Chicago Manual of Style recommends against "logical" punctuation. Septentrionalis PMAnderson 23:43, 1 July 2011 (UTC)

I disagree. We could easily say that if someone writes John Smith stated that "there are not enough bananas". we would also need to check if there is part of the quote or not so it would be easier to just get rid of the quotation marks. However, that would be silly. Why bother checking whether the punctuation was part of the quote or not? Do it if you're putting the quote into the article, that's not hard, but why check if someone else was right? It doesn't really matter. Another distinction is made with logical punctuation in the case of a broken quote: "There are not enough bananas", stated John Smith, "We need to grow more". (I don't know if I followed all the MoS rules in that example but the point is about the punctuation). Putting the comma inside the quotation marks would imply that the comma separated the two statements in the original quote, which is incorrect. Another case is if a song contained a full stop: John Smith wrote the song "Full Stop.". Although that looks a little odd, I would say that is the correct way of writing it, since the first full stop is just part of the name, not the sentence punctuation. John Smith wrote the song "Full Stop.." looks a lot worse. McLerristarr | Mclay1 05:49, 1 July 2011 (UTC)

Actually, in U.S. English, if the period was part of the song, you wouldn't need the second period. The one inside the quotation marks does double-duty. Darkfrog24 (talk) 11:57, 1 July 2011 (UTC)

OK, this is painful, but at this point I say let's agree to disagree on logic. That's going to become a circular argument. Let's talk about practice exclusively. Which is more practical? See my comments on copy editing. Accuracy and consistency are important, so if we're going to go with a style, we need to do our best to follow it or we might as well have no style at all. And in the publishing world, it is an editor's job to check areas where errors commonly pop up, and this would definitely be one of those areas. Who wants to be in charge of checking quoted material?

I'm willing to estimate that about 50 percent of editors don't even know about this MOS rule, so they're not going to know that they need to maintain original punctuation when they pull the quote. Who wants to go back and check the quotes, particularly those pulled from protected databases and hard copy-only resources?--Jp07 (talk) 06:06, 1 July 2011 (UTC)

Like I said, it really doesn't matter if the punctuation is slightly off with quotes. I'd rather have a logical system with some errors than an illogical system which is immune to errors because the system is to deliberately use what others would consider errors. McLerristarr | Mclay1 07:03, 1 July 2011 (UTC)

JP07, you are right to think that this is strange. The bottom line is that WP:LQ is here solely because most of the contributors to this talk page just (WP:IDONTLIKEIT/WP:ILIKEIT) prefer it to American English punctuation. You're also right that many Wikipedians don't know about this rule. The fact that a disproportionate number of Wikipedians were programmers might also have something to do with it. There is exactly one time when British vs. American punctuation actually makes a non-aesthetic difference, and that's when dealing with raw data strings. (Type in "enter.doc/qr". etc.) WP:LQ has been challenged many times. Some of its supporters claim that it is, as the MoS says, less prone to ambiguity and subsequent errors, but no one has ever provided even one example of American English causing even one error on Misplaced Pages, ever. This isn't because American punctuation isn't used here. It is. There are even front page featured articles that have used American punctuation on their big day. I don't know if you know this, but almost every single American English style guide treats American punctuation as correct and LQ as incorrect in formal American English writing. If WP: MoS were held to the same standards as regular articles, those for reliable sources and no original research, then WP:LQ would have been changed long ago. I 100% support changing the Misplaced Pages punctuation policy to follow ENGVAR. Use British/LQ when it is correct to do so and, at the absolute least, allow correct American punctuation on articles that are on clearly American topics. Darkfrog24 (talk) 11:55, 1 July 2011 (UTC)

Yeah... thanks for the backup. I kind of gave up, though. I got tired of asking for justifications and getting the "logical"/"illogical" appellations and tradition. And I do think it is odd that the writing prescriptivism seems to be coming mostly from computer programmers, and from what I can tell (i.e. per user pages and comment content), those who do not have experience as professional writers. I don't quite understand that. I do completely understand why the period and comma placement is important in programming, as I have a programming background as well... but programming and writing are two totally different things. The human mind does not process syntactic symbols in the same way that a computer does. And yeah, that's about what I thought with the style guides. I'm most familiar with AP and MLA, so I didn't want to make any more assumptions, but I had never heard differently on comma/period placement until yesterday.

I think this is a losing battle, though. Even if you win this one, there's WP:IAR. I think it's more important to take on the battle for consistency before taking on specific rules. It seems like non-writers typically don't find consistency valuable in their writing, but both expert writers and novices will notice a lack of consistency and will critique it. Strange.

Maybe it's just me, but I would think it would be wise for the predominantly programmer-run project to seek out the advice of writers...--Jp07 (talk) 12:33, 1 July 2011 (UTC)

You would think IAR would apply, but nope. I actually got brought up on AN/I for using American punctuation in articles that already had it. If we can get enough people, though, we might be able to modify or replace WP:LQ with something more sensible. Maybe the pro-LQ crowd would accept just allowing American punctuation (as opposed to requiring it) on American-subject articles. Darkfrog24 (talk) 12:49, 1 July 2011 (UTC)

I've privately softened a little bit on this one over the years; but what I really can't abide by is "this," where the inclusion of the comma within the word-as-word or the quotation jars with its very obvious identity as part of the main sentence. Also, I'm concerned that within-article consistency really could be achieved if the guideline is looser. Tony (talk) 14:16, 1 July 2011 (UTC)

Wow, Tony. I guess I shouldn't be surprised that a reasonable person can change his opinions over time by continual observation of the situation to which they are relevant. However, I'd like to say that what people do and don't find jarring is in the eye of the beholder. If anything, the use of American style in words-as-words situations is even less likely to cause real confusion than with quotes from sources. Darkfrog24 (talk) 14:24, 1 July 2011 (UTC)

And we recommend presenting words-as-words in italics, which removes the problem; both systems recommend this, because italics have no visible closing marker. Septentrionalis PMAnderson 23:30, 2 July 2011 (UTC)

I wouldn't think that IAR would apply. Despite its name, it doesn't literally mean you can ignore any rule. I prefer to think of it as "yes, there's technically a rule that covers this, but when the rule was codified, they didn't really consider this situation, and had they considered it, they would have accepted that this situation is different. That might mean the general rule needs modification, or it might simply mean that this situation should be considered a one-off exception". However, when we have rules that squarely apply, and have been repeatedly discussed and consensus is that they do apply to this situation, you don't get to use IAR.--SPhilbrick T 16:39, 1 July 2011 (UTC)

What I'm most concerned with is pervasive consistency. Most people who read Misplaced Pages will read more than one article. So if one article is consistent but there are multiple variants elsewhere, I see intra-article consistency as moot. But I appreciate your diplomacy.--Jp07 (talk) 14:27, 1 July 2011 (UTC)

I am of the opinion that inter-article consistency is not necessary or at least more trouble than it's worth on Misplaced Pages. To effect it, we'd have to go all the way, pick just one national variety of English and use it on every single article for punctuation, spelling and all other considerations. Choosing American English punctuation to the exclusion of British/LQ wouldn't solve our problem; it would just reverse it. Darkfrog24 (talk) 14:45, 1 July 2011 (UTC)

Yeah... J-school might have made me a stickler for consistency.--Jp07 (talk) 14:50, 1 July 2011 (UTC)

Always ignore the Manual of Style; everybody else does. But thanks for trying to fix it. Septentrionalis PMAnderson 23:43, 1 July 2011 (UTC)

It would be nice to have inter-article consistency, but that would force us to say things like "The American flag is coloured red, white, and blue" or "The English flag is colored white and red". In a publication requiring editorial approval, that's possible and even preferable. On Misplaced Pages, it's untenable.

Regarding punctuation: I've never understood why anyone uses traditional American punctuation. I remember being in sixth grade and learning the rules for commas and periods in quotation marks, and I remember asking the teacher why in the world would we do that, it makes no sense! I've since realized that it has its own internal logic (as PMAnderson noted, comma-quote and period-quote are always read together even though they are two glyphs), but I still don't like it (I don't think you shouldn't put glyphs between quotation marks unless those glyphs can be attributed to the source you are quoting). My own preference is to leave punctuation outside quotation marks. This has the same copyediting advantages as traditional American punctuation while, in my opinion at least, being more accurate and prettier.

I agree with you that so-called "logical quotation" offers huge copyediting difficulties, and the name isn't very good. It might be possible to change to the system I mentioned above where punctuation is always outside the quotation marks, since that's already quite similar to what the MoS requires (and in fact you sometimes see people moving punctuation outside the quotation marks in the mistaken belief that it's an MoS requirement). But you seem to be advocating traditional American punctuation, and I don't think the politics of that will work: The non-Americans will protest, the Americans aren't nationalist and traditionalist enough to think that the way they were taught in school is necessarily better, and the result will likely be no consensus. You certainly won't change this rule by bringing it up here, where it's been talked to death. If you really want to change it, then you'd need to start an RfC on this topic here and advertise it very widely to pull in editors who aren't MoS regulars; and you'd have to do a very good job of convincing them. Ozob (talk) 17:54, 2 July 2011 (UTC)

Yeah... I will actually receive an American license to teach English and journalism in August, and I am of the thought that some of the lacking nationalism in America has to do with the way that we teach the English language in schools. I have yet to decide whether more nationalism would be a good or a bad thing, but there seems to be a movement among language arts educators away from teaching grammar; they often explain this by saying that grammar instruction "doesn't improve writing skills." I would agree with this sentiment -- writing content will not improve with greater understanding of grammar rules, but perceived credibility among readers definitely gets a boost when you demonstrate a mastery of the English language, and sometimes grammar and punctuation are important for clarity (so I guess in those situations this knowledge would improve writing skills). An ability to follow grammar and punctuation rules is also necessary for anyone who is interested in pursuing a career in writing, and it also helps with a number of other careers where writing is used.

But I think we often characterize the English language as illogical and silly despite the fact that it really isn't, and this damages the relationship that Americans develop with their own tongue. True, it is a mutt of a tongue, and it is difficult for people of other languages to learn, but there is some logic behind every language rule. It would probably be a little more... unified if it wasn't for Roman, French, and Nordic invasions of England, but what can you do.--Jp07 (talk) 11:31, 3 July 2011 (UTC)

Oh, and on the nationalism, it doesn't help that America still doesn't have a legally recognized official tongue. --Jp07 (talk) 11:52, 3 July 2011 (UTC)

I have long thought that the movement away from teaching grammar was a terrible idea. I receive, on a regular basis, emails from people who ought to be able to write better but can't. It makes them look bad. I've often wondered why the movement away from grammar started. Do teachers not teach grammar because they genuinely believe that, say, not recognizing misplaced modifiers doesn't improve writing skills? (On the other hand, Norman Mailer got away with it in the infamous opening line of Harlot's Ghost.) Is it because grammar is objective and doesn't allow the favoritism games that provide some with such perverse pleasure? I wonder if it's now because they don't know anything about grammar themselves.

I agree that English isn't as illogical as it's made out to be. But I think that reputation is a symptom of the lack of English grammar instruction. English teachers will tell their students not to write in the passive voice, and they consider this a vitally important rule, but they can't give a precise description of what the passive voice is. If they could, they would realize at once how silly the rule is. I think more harm has been done to English grammar by reformers than by all the the invasions of England, because the reformers moved the emphasis away from how real people write and speak and placed it on trivialities like passive voice or which versus that. Now all anyone knows are these incorrect trivialities, and they can't write a single clear sentence.

I'm ranting again... Oh, well. Ozob (talk) 13:42, 3 July 2011 (UTC)

@Ozob: People use "aesthetic" punctuation because it's almost as easy as the system you outline and a large number of anglophones will understand it: all those who use it, and a large body of those who don't but have heard of it.

Ozob's punctuation would not be a bad system; it works oddly for quoting full paragraphs, where everything but the final period will be inside quotes; both existing systems tuck the closing period inside. Septentrionalis PMAnderson 22:19, 2 July 2011 (UTC)

I would be behind an RFC, actually. There are several good reasons for removing the ban on American punctuation.

1. The overwhelming majority of reliable sources on American English actively prefer American punctuation for general writing—which is what encyclopedia articles are.

2. The idea that American punctuation causes misquotation, ambiguity or errors in subsequent editing is original research.

3. American punctuation is already used on Misplaced Pages, despite the ban, and has not been found to cause misquotation, ambiguity or errors in subsequent editing to any detectable extent. (Also original research, admitted.)

4. Taking 3 into account, the ban only serves to punish and insult writers trained to use American punctuation and to please people who (WP:IDONTLIKEIT) just don't like American punctuation or who (WP:NOTACRYSTALBALL) think that "this is where English is going," etc. If American English ever changes to the British/LQ style, we can just change the MoS then.

5. Using punctuation that is correct relative to its context would make Misplaced Pages look more professional and precise.

6. ENGVAR is already a proven policy and it is reasonable to believe that extending it to punctuation would work well. Darkfrog24 (talk) 03:02, 3 July 2011 (UTC)

I, too, think an RfC would be a good idea because our discussion here seems to be a bit cyclical.--Jp07 (talk) 16:46, 4 July 2011 (UTC)

I too would approve of extending ENGVAR to punctuation. I see no reason to mandate one punctuation style over another on a Misplaced Pages wide scale when both are valid and acceptable styles. Blueboar (talk) 13:37, 3 July 2011 (UTC)

Though it’s not high on my list, I also would permit “aesthetic” punctuation here, and second Blueboar’s comment about ENGVAR; we could argue forever about which practice is better and get nowhere—AmE and BrE sometimes differ, and one is no better than the other. I would like ENGVAR to include a recommendation that the combination of grammar, spelling, and punctuation be at least plausible to one accustomed to the particular ENGVAR; in many cases, this would allow some flexibility (e.g., some British publishers such as OUP use unspaced em dashes, and the BBC web site uses “aesthetic” punctuation), but the combinations should not be such that a British reader of an article supposedly in BrE thinks “this is whacked”.

Incidentally, I certainly have not found US technical publications to favor “logical” punctuation here. I guess it just depends on one’s field and the particular publications. JeffConrad (talk) 04:12, 4 July 2011 (UTC)

It's funny to see its being called "aesthetic punctuation". It looks quite ugly to me but that's in the eye of the beholder. I would oppose a change to the guideline on this not just because I don't like it but because it changes the quote. JIMp_talk·cont 08:46, 4 July 2011 (UTC)

Jimp, in all the times we've debated this issue, no one has yet provided even one example of American punctuation ever changing even one quotation on Misplaced Pages. (There have been a few "it changes the quote if you also remove half the words," though.) In American English, the closing periods and commas are understood as part of the quotation process, just as "centre" is understood as being pronounced "sen-ter" rather than "sen-treh" in British spelling. Can you show me a time when American punctuation changed a quotation on Misplaced Pages? Darkfrog24 (talk) 12:26, 4 July 2011 (UTC)

It changes the quote only in terms of punctuation. Jim said "I like frogs." No, he didn't, he said "I like frogs". It's a very minor point but because American punctuation makes no distinction between punctuation that existed in the original quote and punctuation that was added by the next writer, it makes it ambiguous and against the general principle of not changing quotes. Yes, in nearly all cases it won't change the meaning and it will be completely understandable but it's an unnecessary change to a quote nonetheless. McLerristarr | Mclay1 14:56, 6 July 2011 (UTC)

But because the final period or comma is understood to be part of the quotation process and not part of the quoted content, it is not the quoted content that is changed. In all the times we've discussed this, no one has ever brought up even one instance of an actual problem, confusion or misquotation that could be attributed to the use of American punctuation. We shouldn't go banning things because of imaginary problems. Darkfrog24 (talk) 03:20, 7 July 2011 (UTC)

To be clear, when we speak of “American punctuation”, we should say North American punctuation, because Canadian practice follows that of the US. As for “the general principle” of not changing quotes, it’s application here is not a general principle in the US and Canada. JeffConrad (talk) 00:37, 7 July 2011 (UTC)

I've looked around a little and I've found one or two sources on Canadian English that preferred the British form. It seems that Canada can go either way, though I'd like to see a reputable print source on the subject. Darkfrog24 (talk) 03:20, 7 July 2011 (UTC)

The Canadian Style. For the most part Canadian punctuation is similar to that in the US, though there are a few things that seem unique to Canada. Spelling is somewhat of a hybrid, but looks mainly British to me. JeffConrad (talk) 04:25, 7 July 2011 (UTC)

There are two types of quotation mark styles: traditional quoting and logical quoting. Neither one is "American rules" or "British rules". They are simply two different styles, both used in both places, it's just that one of them happens to be more common in America, and the other more common in Britain.

As far as why logical quoting should be used? There are any number of reasons:

1) Logical quoting has been used on Misplaced Pages since its inception.

2) Logical quoting is simply logical... it makes sense for quote marks to contain only that which is part of what is being quoted. It makes no sense to include in quotes punctuation that doesn't belong there.

3) Since the dawn of the computer age, especially with the arrival of command-prompt-based operating systems such as DOS, logical quoting has become accepted as common practice in America, and, although it wouldn't be entirely accurate to say that traditional quoting has quite fallen out of favour yet, it looks like it is set to in the very near future.

Reason #2 is really the only important, and the only necessary, reason to use logical quoting. It couldn't make more sense. If something belongs in the quote marks, put it there; if it doesn't, don't. If you actually did ride on something called a "bicycle,", then, by all means, include the comma with it. But I don't know what a "bicycle," is.-=( Alexis 03:53, 13 July 2011 (UTC) )=-

The sources refer to them as "American" and "British." They might also have other names but yes, they really are American and British. Proponents of LQ might wish that I were making it up, but if I am, so are Chicago and these guys: .

1) Just because a mistake is long-standing doesn't mean it shouldn't be corrected. I strongly suspect that the preference for British/LQ was present on early Misplaced Pages because its founders were disproportionately people with programming backgrounds as opposed to writing backgrounds.

2) In the absence of any actual effect, "This is more logical" is just another way of saying, "I personally prefer this more." It might be more logical to spell "caught" as "kot," but it's both wrong and sloppy. Using punctuation that is correct relative to its context makes Misplaced Pages look precise and professional.

3) Maybe it's become common practice among computer programmers but not in general-audience writing, and Misplaced Pages is a general-audience publication.

I would be extremely surprised if you or any of our readers didn't know what a "bicycle," however it was punctuated, is. The real logical way to write is the way that will be understood and appreciated by one's readers. British and American styles are about the same with respect to being understood, and people tend to appreciate the style with which they are more familiar. Darkfrog24 (talk) 11:16, 13 July 2011 (UTC)

According to Darkfrog24 "just because a mistake is long-standing doesn't mean it shouldn't be corrected", but it is not a mistake for a publication like Misplaced Pages to have its own manual of style which chooses among reasonable alternatives. So there is no mistake. Even if the conjecture that the founders were Americans with programming backgrounds who defied the style used by American professional writers is true, so what? It was their publication and they adopted a reasonable style. No consensus has formed to change the choice. Jc3s5h (talk) 12:14, 13 July 2011 (UTC)

This isn't like the serial comma, where either way can be considered correct so long as the piece is consistent—and, if you'll notice, the MoS permits both these forms; it doesn't ban one or the other for arbitrary reasons. Almost every single source on American English says that placing periods and commas inside closing quotation marks is correct and placing them outside is incorrect. To use a type of punctuation that is incorrect relative to its context, and to require others to do so, is not reasonable. It's a mistake. That's actually the most polite of many words for what it is. Using British/LQ in articles that are supposed to be in American English is like spelling "caught" k-o-t. Yes, it's logical. Yes, it can look cool or trendy in the eyes of certain beholders. It's also wrong. Darkfrog24 (talk) 15:18, 13 July 2011 (UTC)

Spelling caught as "kot" makes no sense whatsoever to me since I pronounce "o" and "or" as different sounds but that's beside the point. Logical punctuation is not incorrect. It's only "incorrect" if a style guide recommends traditional punctuation but it's only "incorrect" for the sake of consistency rather than "correctness". However, to proponents of logical punctuation, traditional punctuation is incorrect for the constantly repeated reasons above. Our MoS has picked a system and for the sake of consistency we should stick to it. Besides, the MoS is only a guideline; it's not necessary to follow it. You can go around writing with illogical punctation if you want as long as you don't change punctuation that complies with this guideline. McLerristarr | Mclay1 10:56, 19 July 2011 (UTC)

What you're saying about style guides is true, and the style guides all say that, in American English, placing periods and commas outside adjacent punctuation is incorrect. If the MoS does not require inter-article consistency for spelling or the serial comma, then why require it here?

You know what? We should do this RfC. Unless someone can provide at least a couple of examples of American punctuation causing miquotations or errors—or let's make it easier, problems of any non-imaginary kind—on Misplaced Pages, not "it looks like it would cause misquotations" or "gosh it really looks funny," but "here's the page history; it caused this problem," then it should no longer be banned. Darkfrog24 (talk) 12:30, 19 July 2011 (UTC)

Alt attribute

Hi all

The last bulleted sentence in the images section reads:

"Images should have an alt attribute added to the |alt= parameter."

It is a little confusing as the alt attribute is indeed |alt= and would mean we get |alt=alt= ??

I believe it should probably read more like:

"Images should have the alt attribute |alt= added to the image parameters." or
"Images parameters should have an alt attribute added as the |alt= parameter."

Chaosdruid (talk) 00:09, 10 July 2011 (UTC)

This is quote an important question, anybody not too busy on dashes, hyphens and commas to comment? Chaosdruid (talk) 13:17, 14 July 2011 (UTC)

I got it before, but if you want to write it clearer go ahead.TCO (reviews needed) 14:06, 14 July 2011 (UTC)

I do not want to write it any more clearly than I have already suggested, I just want someone to change it to "Images should have the alt attribute |alt= added to the image parameters." as it seems like no-one is objecting. They can even add "to prevent speech reader from reading out the file name." if they want

As we are not admins we cannot very well do it ourselves now, can we? If I could have, I already would have :¬) 19:23, 14 July 2011 (UTC)

Dash guidelines: toward a conclusion

The long process of finding or confirming consensus for the dash section (WP:DASH) of WP:MOS is drawing to a close. ArbCom, through admin and ArbCom member Casliber, has set 16 July 2011 as the date to finish up and to review consensus.

The evidence at the voting subpage is clear, with a huge response from the community to a poll that was advertised at many forums and talkpages, over the weeks since that page was started (11 May 2011).

60 editors have contributed at the voting page, with 687 edits.
The content of the consensus, along with further development of the guidelines, has been discussed at the discussion subpage: 15 editors contributed, with 265 edits.
Kotniski made an "exploratory redrafting" of the dash section: 3 editors contributed, with 10 edits.
Kotniski's draft has been discussed by 4 editors, with 49 edits. There has been no discussion there for two full weeks (since 28 June).

Given that voting and discussion have been so comprehensive (but practically at a standstill now), and development of the exploratory draft so limited, I intend to initiate discussion right here, by way of summarising and reporting back the main talkpage. Building on Kotniski's valuable work, in a few hours I will post a more developed draft for the dash section, and suggest a framework for concluding discussion – at this central forum for MOS development.

Noetica 04:38, 12 July 2011 (UTC)

Yes, let's do something. Art LaPella (talk) 04:47, 12 July 2011 (UTC)

I agree, too. I had made a suggestion or two for where to go from Kotniski's good start (see my comments and his at Wikipedia_talk:Manual_of_Style/dash_drafting/discussion#A_draft). I think he has incorporated many of the suggestions from the lengthy discussion, but there is further we can go to simplify and clarify the structure. If I recall correctly, there was considerable support for more and better examples, broad enough to clarify the range of uses described for the en dash, and fewer and simpler "cases" or "rules". If you're willing, go for it. Dicklyon (talk) 05:03, 12 July 2011 (UTC)

It is not consensus. It ignores strong disagreement on the issues at hand, as usual. Septentrionalis PMAnderson 02:09, 13 July 2011 (UTC)

Pmanderson, obviously some people disagree - if there had not been disagreement, this case wouldn't have been placed before the arbitration committee. Casliber (talk · contribs) 19:42, 14 July 2011 (UTC)

That appeal was started and populated by those who disagree with the present text; which is why I dispute restating the present text, and claiming it to be consensus. Septentrionalis PMAnderson 22:03, 14 July 2011 (UTC)

What's wrong with this

This utterly ignores the absence of consensus on the points at issue.

1 is a useful section; emphasis on the primary meaning of the dash is always welcome; but the parenthetical use of dashes is not distinct from the abrupt change in meaning or construction – it's a special case in which the original intent of the sentence is resumed.

4 and 5 ignore the strong disagreement in the poll on those points; sections 5b and 6c (about a third of the comments). This also ignores the several recommendations to strengthen the recommendation to avoid compounded compounds, including Tony's (section 5c).Septentrionalis PMAnderson 01:49, 13 July 2011 (UTC)

Majority vote?

If more people support it than oppose it, of course we should ignore the opposition. Why should opposition outweigh support? If the majority of users think that the guidelines are fine and think the opposition is wrong, then, sorry, but that's just tough luck. It's impossible to please everybody. McLerristarr | Mclay1 11:00, 19 July 2011 (UTC)

Well, that's frank. No wonder MOS has so much turbulence; just because you ignore the opposition does not mean they cease to oppose. Who else agre4s with this? Septentrionalis PMAnderson 18:50, 19 July 2011 (UTC)

Dashes: a new draft

Having considered the voting and the long discussion (see some details above), I offer a new draft for consideration at this central forum for MOS, now that business appears almost complete at the dedicated subpages. Noetica 03:05, 13 July 2011 (UTC)

Suggested procedure

It is essential that our concluding discussion be kept orderly, focused, and respectful. With this in mind I am suggesting a framework. I urge editors to use this framework, or alternatively to propose rational variations of it. I urge all editors to work to keep the discussion easy to follow, and to refactor if that will help.
I request that no changes be made to the draft during discussion of it. Please instead propose new versions for parts of it, with localised discussion. Again, it will be easy for the process to disintegrate if we are not vigilant to stay on track.
I propose that we rule out certain distractions especially, and that editors join in removing such distractions to a special subsection I have set up to receive them:
• personal attacks or innuendos

• threats, or expressions of intent to take admin or ArbCom action against any editor

• political statements and manifestos

• unnecessary reference to past conflicts

• insistence that the Manual of Style be something other than just that (its status is definitely not our present topic)

• reflections on the role of MOS generally within Misplaced Pages

• other obvious irrelevancies or contention
I suggest that there be no voting at this stage; let's see how things take shape.
If any editor wants to propose a rewritten whole draft, please bear in mind the consequences. Discussion should have one overall focus at a time, and we can all end up confused and directionless. Therefore: Just as I gave 24 hours' notice before posting a whole draft, please give similar notice of any further whole draft.
The single question we face is this: What dash guidelines will best reflect the clear results of the voting?

Notes on the draft

The draft does not reflect my own preferences as its proposer; it will not satisfy any individual's preferences fully, nor should it aim to.
As a practical necessity, I have assumed that consensus means clear majority assent.
Some preferences in the voting are for more than one recommendation (for en dash or hyphen, in a given situation). This is heeded where it is a majority preference; but if the majority accepts a guideline simply as given, that simple endorsement has been respected as best reflecting consensus.
Some matters have been set aside (partly or wholly) as better treated in general sections of WP:MOS, since they apply beyond the guidelines we deal with here. They include:
• the desirability of recasting (needs a new section of its own)

• the fact that exceptions are sometimes in order (already thoroughly covered)

• use of hard spaces (already covered in WP:MOS, but it may need adjusting)
The draft is much longer than the existing section. It has to be, since this, along with hyphens, is one of the most difficult areas in modern punctuation. Editors will suggest ways to shorten it; but the voting has shown how easily brevity leads to entirely wrong interpretations. We need to guard also against intentional misconstrual.
Cases like a pro-establishment–anti-intellectual alliance are not treated with their own special principle. I found that they were covered by another more basic guideline that is included. This requires discussion. Can anyone think of a case that warrants, in the MOS context, a separate provision for such cases?
As an aside, we need to revisit the colors used in the {xt} and {!xt} templates (for readers unable to distinguish red and green). Meanwhile, I have preceded all red examples (of what not to do) with an asterisk:
*−10–10; −10 to 10

The draft itself (click on the "show" link in the green bar)

Proposed draft for a new dash section
Dashes Shortcuts MOS:DASH WP:DASH Two forms of dash are used on Misplaced Pages: en dash (–) and em dash (—). Type them in as `&ndash` (–) and `&mdash` (—); or click on them to the right of the "Insert" tab under the edit window; or see How to make dashes. Use hyphens, never dashes, in filenames of images, sounds, or other included media. When a dash is used in the title of an article (or any other page), there should be a redirect from a hyphenated version: Eye-hand span redirects to the article Eye–hand span. Sources use dashes in varying ways, but for consistency and clarity Misplaced Pages adopts the following principles. Punctuating a sentence (em or en dashes) Shortcuts MOS:EMDASH MOS:SENTENCEDASH WP:EMDASH WP:MDASH WP:SENTENCEDASH Dashes are often used to mark divisions within a sentence: in pairs (parenthetical dashes, instead of parentheses or pairs of commas); or singly (perhaps instead of a colon). They may also indicate an abrupt stop or interruption, in reporting direct speech. There are two options. Use one or the other consistently in an article. 1. Unspaced em dash Another "planet" was detected—but it was later found to be a moon of Saturn. Or: 2. Spaced en dash Another "planet" was detected – but it was later found to be a moon of Saturn. Do not use spaced em dashes. Another "planet" was detected — but it was later found to be a moon of Saturn. Dashes can clarify the sentence structure when there are already commas or parentheses, or both. We read them in chronological order: Descartes, Locke, Hume—but not his Treatise* (it is too complex)—and Kant. Use dashes sparingly. More than two in a single sentence makes the structure unclear; it takes time for the reader to see which dashes, if any, form a pair. The birds—at least the ones Darwin collected—had red and blue feathers. "Where is the—", she said, but then realized she held it in her hand. First in the procession—and most spectacularly—came the bishops—then the other clergy. En dashes: other uses* Shortcuts MOS:ENDASH MOS:NDASH WP:ENDASH WP:NDASH Apart from its use as a sentence-punctuating dash (see above), the en dash (–) has four other roles. These can be quite similar to uses of the hyphen (see Hyphens above); or less often, the slash (see Slashes below). 1. In ranges that might otherwise be expressed with to or through pp. 211–19; 64–75%; the 1939–45 war Do not mix en dashes with prepositions like between and from. 450–500 people between 450–500 people; between 450 and 500 people from 450–500 people; from 450 to 500 people Use words, not en dashes, if negative values are involved. An en dash might be confusing. −10–10; −10 to 10 the drop in temperature was 5°–−13°; the drop in temperature was from 5° to −13° The en dash in a range is always unspaced, except for times and dates (or similar cases) when the components already include at least one space. 23 July 1790–1 December 1791; 14 May–2 August 2011 23 July 1790 – 1 December 1791; 14 May – 2 August 2011 10:30 pm Tuesday – 1:25 am Wednesday; Christmas Day – New Year's Eve 1–17 September; February–October 2009; 1492? – 7 April 1556 Best absorbed were wavelengths in the range 28 mm – 17 m. 2. In compounds when the connection might otherwise be expressed with to, versus, and, or between Here the relationship is thought of as parallel, symmetric, equal, oppositional, or at least involving separate or independent elements. The components may be nouns, adjectives, verbs, or any other part of speech. Often if the components are reversed there would be little change of meaning. boyfriend–girlfriend problems; the Paris–Montpellier route; a New York–Los Angeles flight iron–cobalt interactions; the components are parallel and reversible; iron and cobalt retain their identity an iron–roof shed; iron* modifies roof, so use a hyphen: an iron-roof shed the poet's mentor–muse; not separate persons, so use a hyphen: the poet's mentor-muse red–green colorblind; red and green are separate independent colors, not mixed blue–green algae; a blended, intermediate color, so use a hyphen: blue-green algae France–Britain rivalry; French–British rivalry; *Franco–British rivalry; Franco-British rivalry a 51–30 win; a six–two majority decision; an Obama–Palin debate an Italian–Swiss border crossing; but an Italian-Swiss newspaper, for Italian-speaking Swiss the Uganda–Tanzania War; the Roman–Syrian War; the east–west runway diode–transistor logic; the analog–digital distinction; a carbon–carbon bond a pro-establishment–anti-intellectual alliance Singapore–Sumatra–Java shipping lanes the ballerina's rapid walk–dance transitions; a male–female height ratio of 1.2 A slash or some other alternative may occasionally be better to express a ratio, especially in technical contexts (see Slashes below). the protein–fat ratio or the protein/fat ratio, or even the protein-to-fat ratio An en dash is not used for a hyphenated personal name. Lennard-Jones potential with a hyphen: named after John Lennard-Jones An en dash is used for the names of two or more people in a compound. the Seifert–van Kampen theorem; the Seeliger–Donker-Voet scheme; the Alpher–Bethe–Gamow theory Comet Hale–Bopp or just Hale–Bopp (discovered by Hale and Bopp) Following the dominant convention, a hyphen is used in compounded place names and language names, not an en dash. Guinea-Bissau; Austria-Hungary an old Mon-Khmer dialect; Niger-Congo phonology The en dash in all of the compounds above is unspaced. 3. Instead of a hyphen, where at least one component includes a space an ex–prime minister; pre–World War II aircraft In many cases, recasting the phrase is possible and better. a former prime minister; aircraft before World War II The en dash in all of the compounds above is unspaced. 4. To separate items in certain lists Spaced en dashes are used within parts of certain lists. Here are two examples: Pairing performers with instruments. James Galway – flute; Anne-Sophie Mutter – violin; Maurizio Pollini – piano. Showing track durations on a CD. The future – 7:21; Ain't no cure for love – 6:17; Bird on the wire – 6:14.

Proposed draft for a new dash section

Dashes

Shortcuts

Two forms of dash are used on Misplaced Pages: en dash (–) and em dash (—). Type them in as &ndash (–) and &mdash (—); or click on them to the right of the "Insert" tab under the edit window; or see How to make dashes.

Use hyphens, never dashes, in filenames of images, sounds, or other included media.
When a dash is used in the title of an article (or any other page), there should be a redirect from a hyphenated version: Eye-hand span redirects to the article Eye–hand span.

Sources use dashes in varying ways, but for consistency and clarity Misplaced Pages adopts the following principles.

Punctuating a sentence (em or en dashes)

Shortcuts

Dashes are often used to mark divisions within a sentence: in pairs (parenthetical dashes, instead of parentheses or pairs of commas); or singly (perhaps instead of a colon). They may also indicate an abrupt stop or interruption, in reporting direct speech.

There are two options. Use one or the other consistently in an article.

1. Unspaced em dash

Another "planet" was detected—but it was later found to be a moon of Saturn.

Or:

2. Spaced en dash

Another "planet" was detected – but it was later found to be a moon of Saturn.

Do not use spaced em dashes.

*Another "planet" was detected — but it was later found to be a moon of Saturn.

Dashes can clarify the sentence structure when there are already commas or parentheses, or both.

We read them in chronological order: Descartes, Locke, Hume—but not his Treatise (it is too complex)—and Kant.

Use dashes sparingly. More than two in a single sentence makes the structure unclear; it takes time for the reader to see which dashes, if any, form a pair.

The birds—at least the ones Darwin collected—had red and blue feathers.
"Where is the—", she said, but then realized she held it in her hand.
*First in the procession—and most spectacularly—came the bishops—then the other clergy.

En dashes: other uses

Shortcuts

Apart from its use as a sentence-punctuating dash (see above), the en dash (–) has four other roles. These can be quite similar to uses of the hyphen (see Hyphens above); or less often, the slash (see Slashes below).

1. In ranges that might otherwise be expressed with to or through

pp. 211–19; 64–75%; the 1939–45 war

Do not mix en dashes with prepositions like between and from.

450–500 people
*between 450–500 people; between 450 and 500 people
*from 450–500 people; from 450 to 500 people

Use words, not en dashes, if negative values are involved. An en dash might be confusing.

*−10–10; −10 to 10
*the drop in temperature was 5°–−13°; the drop in temperature was from 5° to −13°

The en dash in a range is always unspaced, except for times and dates (or similar cases) when the components already include at least one space.

*23 July 1790–1 December 1791; *14 May–2 August 2011
23 July 1790 – 1 December 1791; 14 May – 2 August 2011
10:30 pm Tuesday – 1:25 am Wednesday; Christmas Day – New Year's Eve
1–17 September; February–October 2009; 1492? – 7 April 1556
Best absorbed were wavelengths in the range 28 mm – 17 m.

2. In compounds when the connection might otherwise be expressed with to, versus, and, or between

Here the relationship is thought of as parallel, symmetric, equal, oppositional, or at least involving separate or independent elements. The components may be nouns, adjectives, verbs, or any other part of speech. Often if the components are reversed there would be little change of meaning.

boyfriend–girlfriend problems; the Paris–Montpellier route; a New York–Los Angeles flight
iron–cobalt interactions; the components are parallel and reversible; iron and cobalt retain their identity
*an iron–roof shed; iron modifies roof, so use a hyphen: an iron-roof shed
*the poet's mentor–muse; not separate persons, so use a hyphen: the poet's mentor-muse
red–green colorblind; red and green are separate independent colors, not mixed
*blue–green algae; a blended, intermediate color, so use a hyphen: blue-green algae
France–Britain rivalry; French–British rivalry; *Franco–British rivalry; Franco-British rivalry
a 51–30 win; a six–two majority decision; an Obama–Palin debate
an Italian–Swiss border crossing; but an Italian-Swiss newspaper, for Italian-speaking Swiss
the Uganda–Tanzania War; the Roman–Syrian War; the east–west runway
diode–transistor logic; the analog–digital distinction; a carbon–carbon bond
a pro-establishment–anti-intellectual alliance
Singapore–Sumatra–Java shipping lanes
the ballerina's rapid walk–dance transitions; a male–female height ratio of 1.2

A slash or some other alternative may occasionally be better to express a ratio, especially in technical contexts (see Slashes below).

the protein–fat ratio or the protein/fat ratio, or even the protein-to-fat ratio

An en dash is not used for a hyphenated personal name.

Lennard-Jones potential with a hyphen: named after John Lennard-Jones

An en dash is used for the names of two or more people in a compound.

the Seifert–van Kampen theorem; the Seeliger–Donker-Voet scheme; the Alpher–Bethe–Gamow theory
Comet Hale–Bopp or just Hale–Bopp (discovered by Hale and Bopp)

Following the dominant convention, a hyphen is used in compounded place names and language names, not an en dash.

Guinea-Bissau; Austria-Hungary
an old Mon-Khmer dialect; Niger-Congo phonology

The en dash in all of the compounds above is unspaced.

3. Instead of a hyphen, where at least one component includes a space

an ex–prime minister; pre–World War II aircraft

In many cases, recasting the phrase is possible and better.

a former prime minister; aircraft before World War II

The en dash in all of the compounds above is unspaced.

4. To separate items in certain lists

Spaced en dashes are used within parts of certain lists. Here are two examples:

Pairing performers with instruments.
- James Galway – flute; Anne-Sophie Mutter – violin; Maurizio Pollini – piano.
Showing track durations on a CD.
- The future – 7:21; Ain't no cure for love – 6:17; Bird on the wire – 6:14.

Discussion of the draft

At first reading, this looks pretty good. I still think we need to mention the use of the en dash (or em dash??) as a separator when it's neither in a sentence nor in a list, as in the Harry Potter and the Deathly Hallows – Part 1 case we discussed – this seems to come up from time to time, in article titles at least, and people usually seem to opt for a spaced en dash (or some alternative other than a horizontal line) when the matter is considered.--Kotniski (talk) 04:07, 13 July 2011 (UTC)

Thanks, Kotniski. And thanks for breaking the ice with your draft, which influences the one I offer here. I agree that more work needs to be does on the point you mention. Luckily, it is self-contained and probably not a major cause of difficulty. Why not propose a neat modification to cover it? Noetica 06:23, 13 July 2011 (UTC)

Noetica, I've looked only cursorily through your draft, and I must say that it's impressive. (Kotniski's was impressive too, but I believe this more recent draft takes the ball and runs with his improvements.) I was slightly concerned at the length of Noetica's draft, and we need to scrutinise it for "trimming opportunities"; but then, putting myself in WP editors' shoes, I learn something from every example, and examples are the key to conveying professional-standard typography. When this is tweaked, the final version might well be worth printing out and distributing to my clients. I'm most interested in the opinions of other editors. Thank you indeed, Noetica. Tony (talk) 06:43, 13 July 2011 (UTC)

I think it looks pretty good, but a few comments:

The order of the recommended/not recommended practice in the examples should match that in the text that precedes it, rather than the opposite, as in
Use words, not en dashes, if negative values are involved. An en dash might be confusing.
*−10–10; −10 to 10
Spacing of range dashes where one or more elements contains a space: either spaced or unspaced use should be allowed. The polling seems to indicate considerable support for allowing both, and the support for closed-up usage in US, Canadian, and British style guides (APA, CMOS, MWM. TCS, OSM, and NHR; the last two do mention that many British publishers space the en dash) is overwhelming. Like CMOS, I would usually prefer to or through for a complete date, but I certainly see no problem with Christmas Day–New Year's Eve when we can use New York–Chicago flight—there’s little ambiguity with either.
Under (2), it might help to explain why Franco-British rivalry takes a hyphen rather than an en dash—perhaps something to the effect of “the order of Franco and British cannot be reversed”, or “Franco is a prefix than cannot stand alone”, or “Franco is not lexically independent”. The last would be my last choice, because although its meaning may be obvious to most of us here, it may not be to others, and searching for the meaning is no simple task.
Under (3), I would add one example in which the first component contains a space (e.g., Chuck Berry–style lyrics, New Zealand–style clothing, golf ball–sized brain.
The usage within items in a list (which I’m still not convinced is a distinct case) should not lend itself to be read as precluding alternatives, of which the unspaced em dash is the most obvious, but not the only possibility. If a style has been established for a specific class of articles (e.g., Days of the year), that style should be followed. For articles on discography, the format is not nearly so uniform, so any reasonable alternative should be acceptable. I don’t think we should give alternatives any more than a brief mention, and even then, it should only serve to indicate that there are alternatives. JeffConrad (talk) 07:15, 13 July 2011 (UTC)

Thanks Jeff. On each of your points in order:

I understand about keeping a uniform order of presentation. The trouble is this. It's good to keep the order wrong–right, consistently in the examples (as I have done). But the explanation may be shorter and easier to follow in the reverse order. I don't see a difficulty in the case you exhibit above: the examples almost stand alone to make the point. Anyway, sure: such a refinement can be flagged for incorporation.
On the spacing of range dashes, the task is to interpret the voting and associated discussion, not to return yet again to the style guides. We have moved on from that, and must stay moved on if we want to make genuine progress and reach a conclusion. On the specific point you raise, though, about Christmas Day—New Year's Eve being justified by analogy with New York—Chicago flight, note that the sense of the dash differs. In one it shows a range, in the other it shows a relationship between two elements. Given that difference in meaning, it is well that the dash should at least behave differently with respect to spacing. That is at least as arguable. In the end, I believe the position I have incorporated reflects the clear majority in the voting.
For the prefix element "Franco", I agree entirely that things should be made explicit for it. I did that, then trimmed it out in pursuit of less wording. It can easily be put back, if people want that.
You write: "I would add one example in which the first component contains a space (e.g., Chuck Berry—style lyrics, ...". But that was not put to a vote, so we have no evidence of consensus for it. These differ considerably from prefix cases, and they are treated differently by various style guides (for what that's worth).
I have little to say about dashes in those lists. For me it's pretty arbitrary, and a much easier thing to sort out than the other principles. Let others have their say: but let it be efficient and conclusive dialogue.

Noetica 09:22, 13 July 2011 (UTC)

I tend to prefer “right/wrong”, but don’t have strong feelings, and would not even insist that the order be consistent overall if variations would make the individual points more clearly. But I would urge consistency between the text and any specific examples; either order would probably work, as long as the order of the example matches that of the text that describes it.
On spacing of range dashes, it obviously depends on how one interprets the voting. Though there seems to be more support for spacing, I obviously do not interpret the voting as clearly precluding closed-up use, as is supported by the overwhelming preponderance of widely respected style guides. I once again urge correct use of the singular and plural: you clearly speak for yourself and a fair number of others, but you definitely do not speak for everyone here, as the use of we would seem to imply. I am quite honestly baffled by “We have moved on from that”; if this is to say that we care not about widely accepted practice, it is almost as if we have extracted a position from a region in which the “sunny 16 rule” is inapplicable, and the position accordingly is little more than WP:ILIKEIT. I agree that there may be a difference in the sense of the two examples, but the difference is slight, and in any event, the mere existence of a difference does not in itself justify differential treatment. The issue is rather, I think, one of whether the closed-up usage leads to ambiguity—and it does not. As I previously indicated in my comment on the voting, we have essentially an issue of operator precedence, in the order of hyphen, space, and en dash. If we accept this, there is no ambiguity; if we do not, much of the overall rationale for using en dashes is weakened. Lest I be thought a pusillanimous pussyfooter, I can assure you that I will oppose a draft that proscribes the closed-up use.
As for golf ball–sized brain, I agree that we did not vote on the specific example, but we did previously vote on the more general case of compounds that contain hyphens or spaces, and, by implication, that golf ball–sized brain would be preferable to golf ball-sized brain, even if the endorsement of the former was tepid at best. JeffConrad (talk) 10:23, 13 July 2011 (UTC)

Jeff, on the order of "right" and "wrong" examples and all that: no big deal. I suggest we defer adjusting such things, till weightier matters are dispatched.

On your remarks concerning the spacing of range dashes: For the third time, please desist from critique of my use of "we", which I have explained elsewhere. Stay with content, not its expression (on whose analysis we disagree). It seems that you refer to this statement of mine: "... the task is to interpret the voting and associated discussion, not to return yet again to the style guides. We have moved on from that, and must stay moved on if we want to make genuine progress and reach a conclusion." If you think our present task is different, please raise that matter in the subsection below: #Discussion of procedure. Meanwhile, a close quantitative and qualitative analysis of the voting and comments on the point at issue would be relevant and valuable. I hope you will undertake that, and report it here. Finally on this, you say: "I can assure you that I will oppose a draft that proscribes the closed-up use." Please note that if we all take such stands even before such shared examination of voting, and also elevate clearly minority positions to sub-guideline status, we will end up with unmanageable complexity. The guidelines will be unworkable: they will fail to guide. With that in mind, I have suppressed my own strong disagreement with ex–prime minister, though dissent from that in the voting would support my acting on that disagreement here. We must all be careful not to fall victim to WP:ILIKEIT. Everyone must compromise; that's how it is, with manuals of style.

On forms like golf ball–sized brain, if you thought the community should consider those, the time to raise it was six weeks ago when the points for voting were settled. We have moved on! :) Noetica 22:48, 13 July 2011 (UTC)

The points for voting were "settled" overnight without discussion from a list intended for a different purpose. They omitted much; this is one point that was omitted. As for we, Noetica does not speak for anyone but xemself; ~~unless this is a case in which Mark Twain is correct.~~ ;} Septentrionalis PMAnderson 23:04, 13 July 2011 (UTC)

I don’t necessarily object to we; I use it here myself, but not in the sense of purporting to speak for Misplaced Pages when that is not necessarily the case. You feel that we have “moved on” from widely recognized sources, but clearly not everyone agrees (though I would certainly not go so far as to say that you speak only for yourself). You’ve also offered a definition of “consensus” that differs markedly from WP:CONSENSUS. I don’t necessarily see a “clear majority”, and it’s never been been strictly a matter of numbers, anyway—we seem to be missing the “quality of arguments”. If practice supported by the preponderance of quality guides is to be blown off, especially without any real reason for doing so, what then constitutes “quality of arguments”?

If you’ve followed my comments, I’ve generally been very supportive of what’s been proposed, but I now find myself almost to the point of clearly recognizing that the MOS is a guideline, and using my own judgment for recommendations are little more than dogged insistence on WP:ILIKEIT, especially when they represent minority practice. I assure you that I shall not be writing golf ball-sized brain (though I concede the opportunity to do so may never arise). JeffConrad (talk) 02:35, 14 July 2011 (UTC)

My comments:

I like Kotniski's draft more. (This one is a bit too wordy.) :-)
I'd always use {{xt}} and {{!xt}} in ways that it is obvious from the surrounding texts which are the right examples and which the wrong ones, even without relying on the colour or on symbols such as asterisks, as in “right, not wrong”, or “avoid wrong; prefer right”. But then, I once proposed for {xt} to have a tick and underlining and {!xt} to have a cross and strike-through, but it was opposed as too much clutter. A darker red and a paler, more bluish green (e.g. maroon and teal) would be easier to tell apart for colour-blind people, but for readers with non-standard display gammas the former might be too dark (harder to tell from regular black text) or the latter too pale (harder to read against the background).
IMO, image filenames are even less relevant than recasting or hard spaces or exception would be (for these reasons).
As I already said elsewhere, I'd suggest the advisability of recasting the phrase using different examples than the ones where a dash is suggested. I'd use examples like the current ones for the dash (with such über-familiar noun phrases as prime minister or World War II), and then after “... is possible and better” show seriously abstruse examples in red followed by a suggested rephrasing in green.

― A. di M._plé 11:38, 13 July 2011 (UTC) ― A. di M._plé 11:38, 13 July 2011 (UTC)

Examples of what you have in mind for the last point would be helpful. Septentrionalis PMAnderson 21:55, 13 July 2011 (UTC)

A di M:

I like Kotniski's draft too; and Kotniski likes the present draft (too). On wordiness, please specify which words you would remove from the present draft. In introducing it, I predicted that editors would make such suggestions. But again: we have seen how brevity is misread in this most complex of punctuation topics; and we must preempt abuse of MOS guidelines that would capitalise on lacunae.
On the practical red–green issue, it may be best to deal with that another time. I like your comments. Meanwhile, we have a simple solution with "*" to get us through the present business.
On image filenames and the like, thank you for attending to this matter of general provisions versus local provisions. I'm not convinced yet on this one; I had thought that hyphens and dashes in filenames was a pretty confined issue. I wonder what others think?
On recasting, I strongly suggest that we stick with rewordings of the actual examples given; but I also strongly favour using less familiar examples to start with. I did not include those for this point, because I wanted editors to recognise the examples – for continuity with earlier versions of the guideline, for this discussion. Let's alter them later, sure.

Noetica 23:15, 13 July 2011 (UTC)

Answering the points in order: 1. I'm not sure exactly what words are the culprit, but I'm under the impression that Kotniski's version manages to say pretty much the same things more concisely and no less clearly (though a couple extra examples might be added); 2. I still think that not would be a lot clearer than an asterisk, though it works better if right examples are before wrong ones (“foo, not bar” vs “not bar, but foo”); 3. I think whatever argument for or against the avoidance of dashes in file names would apply to pretty much all other hard-to-type characters; anyway, I think it's pointless as most files are hosted on Commons so the uploader might have never even heard of en.wiki's MOS; 4. if we say that rewording is sometimes (but not always) better, I think we ought to include both examples of when it's better than when it isn't. As for the former, I recall someone asking on this talk page how to punctuate some very complicated technical term itself including a several-word technical term as a modifier, and someone else (IIRC either you or Tony) suggested a recasting. ― A. di M._plé 14:59, 14 July 2011 (UTC)

Thanks, Noetica, it looks like a good step, very clear and logical, lots of on-point examples. A few comments:

I am a little bothered by the statement "These can be quite similar to uses of the hyphen; or less often, the slash." The "quite similar" doesn't quite capture the right relationship. As one commenter pointed out in the voting or discussion, "interpretation is needed" in deciding whether some of the described roles are applicable in a particular case. Your examples make it clear that to decide which punctuation is needed in something like "blue–green", one has to consider the role, which requires interpretation; the process is not mechanical, because it signals the writer's intent; and that's why it's useful. Anyway, "quite similar" seems to sweep that point away. It would seem important to point out that the en dash roles differ from the roles of a hyphen; maybe something like "These are analogous to uses of the hyphen, which binds more strongly than the dash; or the slash, which separates alternatives."

Another point: I still think the item "4. To separate items in certain lists" is not a separate role, but just another case of using spaced en dash as a dash; same idea in Kotniski's point.

I'm surprised the "ex–prime minister" item causes trouble, but on review I see that several people had various problems with it. I note that it's taken directly from this guide by a Canadian, along with the "anti-xxx–pro-xxx" example, which would certainly not be OK with a hyphen, but for other reasons as you note; it's similarly expressed in lots of other guides, though often as an option for improving clarity "when needed." And this Adobe (American) book suggests "pre–World War II", and states that the hyphen is "incorrect" in that context; and on "post–World War II" and "San Francisco–based," we have the word of Chicago; many more books say similarly. So is this one more optional than most? If some editor changes "ex–prime minister" back to the hyphen version, should we complain and fix it back? I still think we should, since if an editor finds it useful to use punctuation to signal the structure more clearly, we ought to let them. In that sense, I don't see the point of trying to make this one more optional than most, as some are suggesting. On the other hand, I don't have strong feelings about it, and would be willing to go with adjustments if there's a consensus to do so.

I would support the idea of removing mention of filenames, since it is not a style issue, just a source issue.

On the spaced vs. closed-up en dashes, I'm happy to see that there's less of the spacing suggestion than before, and I agree that it should stay in the case of the date phrases with spaces in them, as it appears in every WP bio article. It's a step in a good direction (away from "too British for some"), and stops short of going too far; it's exactly as I would have interpreted the discussion.

Generally, I think you addressed most of the disagreements – even the "facepalm" one. It would be hard to address the issues of the two guys who disagreed with most of the en dash roles, and still call it a consensus result. A few more may show up now, like the one who complains that he can't tell a hyphen from an en dash in a typewriter font, so it doesn't matter what you use; but I agree it's time to try to adjust the dash section as constructively as we can given all the constructive feedback that has come out. Thanks again for this draft, building on Kotniski's. Dicklyon (talk) 03:54, 14 July 2011 (UTC)

North American and British practice differ on spacing, and on use in spaced compounds—NHR states that there is no satisfactory way of dealing with “ex-Prime Minister”, and notes (but does endorse or reject) the US practice (which would be “ex–Prime Minister”). The recasting seems preferable for a nominal (as shown), and I don’t really have a problem with “former Prime Minister Gordon Brown”, though I might just as likely write “former–Prime Minister Gordon Brown”. Though I have a bit of an issue with “San Francisco-based company”, the caps do help (if not as much as in “ex-Prime Minister Brown”). I probably can also sort out “pre-World War II technologies”; here, I think the major issue is how many words an open compound can contain before it becomes unmanageable (and where, if at all, might we want a nonbreaking space. I think it’s a bigger issue without the caps, as in “pseudo-page transition” or “golf ball-sized brain”. With the latter, I can sort out what’s meant, but not without a double take; because the former is nor written in English anyway, it takes several double takes (but perhaps this would be true for any concept with which a reader is unfamiliar). In short, I think the dash vs. hyphen a fairly big deal when there are no caps.

TCS does not seem to address the issue of open compounds, though they suggest an entirely different approach in some cases (e.g., red colour-filter , apparently with the assumption that colour filter is a noun phrase).

I agree that it′s sometimes a matter of eye rather than rote; for example, I would probably write high school student, even though I’m unaware of a closed-up form of “school student” such as there is with “schoolteacher”. It may also be worth noting that some guides (e.g., APA and CMOS) do not use hyphens or dashes with ethnic identifiers (e.g., African American Student rather than African-American student. But this is an issue for WP:HYPHEN rather than here; I assume that we would prefer African–American relations regardless of how the ethnic association is handled. JeffConrad (talk) 05:59, 14 July 2011 (UTC)

@Dicklyon: I've heard that using dashes in compounds which would normally use hyphens when one of the words has a space is uncommon in BrE. If that's the case, the fact that it “signal the structure more clearly” isn't enough to deprecate hyphens in this situation throughout en.wiki. For example, spelling the method of payment as ‹cheque› is clearer because it signals that you don't mean any of the other meanings of check, but you don't want to recommend that in articles written in AmE. ― A. di M._plé 11:16, 15 July 2011 (UTC)

It finds support in OSM (at 5.10.9), though the support is tepid at best. OSM does not endorse the hyphen as an alternative. As is discussed under What consensus means, the Fowler brothers saw the problem with using hyphen as early as the beginning of the 19th century (and had no solution by 1931, either).

One approach would be to permit either usage, possibly encouraging consistent use of either North American or British practice, though this could be tricky because some practices may be chiefly (but not exclusively) North American, and others may be chiefly (but not exclusively) British.

I can’t say whether the fact that one construction may indicate the structure more clearly is sufficient to deprecate an alternative construction, but it seems to me that the point of en dashes in nearly all cases is to more clearly indicate what is meant than would a hyphen. So if it doesn’t matter here, it arguably doesn’t matter anywhere. JeffConrad (talk) 22:39, 15 July 2011 (UTC)

Though Noetica and I seem to differ fairly strongly on what has been concluded with regard to spacing of range dashes, it should be clear that this is the only point in the draft on which we really differ. Though I’m not sure we really differ on the task that remains, we do appear to differ a bit on how this is to be done. I begin by looking at WP:CONSENSUS:

In determining consensus, consider the quality of the arguments, the history of how they came about, the objections of those who disagree, and existing documentation in the project namespace. The quality of an argument is more important than whether it represents a minority or a majority view. The argument “I just don't like it”, and its counterpart “I just like it”, usually carry no weight whatsoever.

I don’t mean to dwell too much on the IDONTLIKEITs, but do maintain that given this framework, what RSs have to say is very much relevant in determining what may have been concluded. I agree that more people seem to prefer spacing; whether it’s a “clear majority” is more subjective, but there certainly is some significant opposition. Accordingly, I again turn to the quality issue, and suggest that given the great number of RSs that support closed-up usage, it does not seem reasonable to proscribe that practice. I do not recall a single source being cited as the basis for requiring the spaced usage, though Butcher may have been mentioned earlier in the discussion. I think it helpful to review what she has to say on the subject:

En rules meaning ‘to’ and ‘and’ are usually unspaced: theocratic–military, chapters 11–9, 101–10. However, spaced en rules may be used between groups of numbers and words to avoid implying a closer relationship between the words or numbers next to the en rule than between each of these and the rest of its group:

6.6–8	but	6.6–7.8
September–January		18 September–19 January
1215–1260		c. 1215–c. 1260

But these spaced en rules should be used cautiously, especially if there are also parenthetical dashes, as the reader may not be able to tell one from the other; and it may be better to substitute ‘to’ in such cases.

Under “Parenthetical dashes”, she continues, “Spaced en rules are now most often used”, so it apparently is assumed that the parenthetical dash is indistinguishable from the spaced range dash.

Though I probably have more British style guides than the average Brit, I’m certainly not as familiar with them as I amd with the American guides. But of all the guides with which I am familiar, Butcher seems one of the most favorable to spacing range dashes. And the recommendation is far less than what’s current or proposed here. In particular, I simply do not see why a problem would arise with “Christmas Day–New Year’s Eve” when there is not a problem with “New York–Chicago flight”. In both examples, the dashes in both examples seem to me to be in the sense of to. And isn’t the association addressed by using the en dash rather than a hyphen? If not, much of the rationale for using en dashes elsewhere would seem to break down.

A possible compromise would be to include wording similar to that above, perhaps adjusting the sense of the dashes to match whatever may be agreed to. Clearly it’s impossible to arrive at formulaic guidance on when association implied by the en dash might misleading, and the same is probably true for any possible confusion between range dashes and parenthetical dashes. Practically, the choice would be a matter of personal choice—British practice aside from OUP is apparently to prefer the spacing, while North American practice is usually to prefer closed-up usage. The case for spacing is probably strongest with full dates and with instances similar to the last example above. Even so, NA seem to prefer closed-up usage. The most common instance of full dates is arguably in obituaries, and unfortunately, they aren’t always much help. If my local newspapers are any guide, the copy editing is invariably done by the deceased. JeffConrad (talk) 09:38, 15 July 2011 (UTC)

Though my main issue here is with Christmas Day–New Year’s Eve (it’s really not different from New York–London flight, and calling a range of dates is stretching things to the limit), I overlooked another: 28 mm–17 m. The en dash could initially be confused with a minus sign. There really is no ambiguity, just as there isn’t with closed-up dashes in most date forms (at least for North Americans), but the reader may need a double take to see what’s really meant. The implication of minus is far less with closed-up usage, but since there seems to be reasonable consensus against closed-up usage when both ends of a range of dates, times, or similar contain spaces, closed-up usage probably is not an option. It would be better to write 18 mm to 17 mm. This is consistent with CSE6:

When expressing a range of numbers, use the word “to” or “through” to connect the numbers. Alternatively, an en dash, which means “to”, may be used but only between 2 numbers that are not interrupted by words, mathematic operators, or symbols to avoid confusion with the minus symbol.

This is stated somewhat better in the Alaska Department of Fish and Game Writer’s Guide (which cites CSE). Perhaps Ms. Palin could in turn cite it in her debate with President Obama when mixing units in a range (“3 moose to 4 caribou”).

This usage really wasn’t put to a vote (and got little discussion there aside from A. di M.’s comment), which is perhaps why the potential confusion wasn’t noticed. Incidentally, I would replace Obama–Palin debate with something else, because it quite likely will not happen, and consequently might confuse some readers. I’d return to Lincoln–Douglas debates, the stature of which Nixon–Kennedy debates cannot come close to matching. There is no potential confusion with a style if the plural is used. JeffConrad (talk) 01:40, 16 July 2011 (UTC)

Dunno, a sane person would typically write that as −(17 m − 28 mm) if that's what they mean. Also, in most cases it will be completely obvious from the context that you're looking at a range of positive numbers (so long as you don't use en dashes and minus signs in the same phrase, as in the red examples currently in the MOS). ― A. di M._plé 12:13, 16 July 2011 (UTC)

A slightly different issue, I think. The spaced en dash in most cases is not obviously different from a minus sign, and the first-impression interpretation of a spaced minus is subtraction, in this case “28 mm minus 17 m”. The context will usually prevent ambiguity (I don’t think we normally add or subtract wavelengths), but comprehension may require slight additional processing—the first impression I have is that of an operation involving units of length, which is plausible. The claim of real ambiguity is in most cases nonsense; no one is likely to mis-associate the numbers and words in something like “24 June–17 July”, though again, perhaps a brief rescan may be needed. One could also maintain that “3 June 1970–9 September 1971” is potentially ambiguous because of implied subtraction “1970 − 9”, but at least for me, that first impression is less likely because I don’t normally think of subtracting dates. To me, the most jarring unspaced construction of dates would be something like “3 June 1970–9 September 1971”; the first thing I see is “1970–9″, which could mean “1970–1979”. Again, I quickly sort it out, but would prefer not to need to do so.

Incidentally, spacing en dash in dates in at least one construction introduces genuine ambiguity. Consider “18 July–3 September 2012” does this mean “18 July 2012 through 3 September 2012” (the dates of the Obama–Palin debates) or “18 July 2011 through 3 September 2012” (the time between now and when these debates are behind us)? Without the spacing (“18 July–3 September 2012”) the close association of the months strongly suggests the former meaning. Though it’s hardly possible to definitively conclude that North American practice is “better” or “worse” than that elsewhere, I think it’s worth noting that with the former, there is little chance of confusion among the em dash, unspaced en dash, and (spaced) minus. JeffConrad (talk) 07:19, 18 July 2011 (UTC)

I definitely agree that the example Obama–Palin debate is unacceptable. And use the Lincoln–Douglas debates to clarify that you don't mean some generic Lincoln–Douglas debates. Dicklyon (talk) 04:51, 18 July 2011 (UTC)

What consensus means

Consensus does not mean "a clear majority"; if we ran by majority vote, we would say so. Please see WP:CONSENSUS for how we do run; we do not use the proper meaning of consensus as "unanimous consent", which frequently causes difficulties over international treaties, whem a handful of states decline to join an overwhelming majority. (For more on this, see Law of the Sea Treaty, and others.)

Even on Misplaced Pages, "he goal of a consensus discussion is to reach an agreement about page content, one which may not satisfy anyone completely but which all editors involved recognize as a reasonable exposition of the topic."

This is not a reasonable exposition; a third of us object to requiring ex–prime minister, ranging from those like me that would permit it, to those who would recommend against it. There is also strong sentiment against the anti-conscription–pro-conscription debate; the weakly supported (but unopposed) recommendation of stronger language to avoid all such forms is omitted. Septentrionalis PMAnderson 16:45, 13 July 2011 (UTC)

Which is why I keep harping on the idea of phrasing things as "preferences". When there is disagreement among Wikipedians over a style issue ... (and a third objecting is definitely a "disagreement") we should not impose the majority view... instead we should present the options, indicate that all are "allowed"... however, we can then note that one style is preferred (to put this another way... a "preference" can be determined by a majority vote, a "rule" needs clear and solid consensus). Blueboar (talk) 17:02, 13 July 2011 (UTC)

Would you care to do a draft? Septentrionalis PMAnderson 17:43, 13 July 2011 (UTC)

Actually, no... I have never pretended to fully understand the specifics of the endash vs emdash vs a hyphen debates (hell, I am still not sure I completely understand what the difference between them is). Because of this, I am not really focused on what the MOS should say, but rather on how the MOS should say it.

I have been trying to find ways to break the "my way or the highway" deadlocks that those of you who do understand the nuances of dashes and hyphens keep getting into. Looking at the AfD, it is clear (even without fully understanding what is being discussed) that, on some points, almost everyone agreed. I think that consensus would justify presenting these items in terms of being accepted "rules"... conceptually telling readers: "this is how it should be done". However, it is also clear that on other points there was significant disagreement. I think that lack of consensus indicates presenting these points in terms of "preference"... conceptually telling the reader: "here are the options... all are allowed, but we prefer X". Blueboar (talk) 20:05, 13 July 2011 (UTC)

I'll see what I can do in 24 hours. Septentrionalis PMAnderson 20:24, 13 July 2011 (UTC)

The claimed majority is not merely not consesuus, but false. The discussion or ex–prime minister is at Wikipedia_talk:Manual_of_Style/dash_drafting#In_compounds_whose_elements_themselves_contain_hyphens_or_spaces; section 5b. At most 10 support requiring the dash, and of those Jeff, Tony, Kotniski, and MacWhiz are doubtful; 14 (including Ozob) would make it optional or deprecate it. Septentrionalis PMAnderson 23:53, 13 July 2011 (UTC)

To clarify my position on the use in compounds: as Fowler notes (TKE, under HYPHEN)

It is good English usage to place a noun or other non-adjectival part of speech before a noun, printing it as a separate word, and to regard it as serving the purpose of an adjective by virtue of its position . . .

He then proceeds to review the problems that arise with compound modifiers (mentioning his whimsical Anglo-SouthAmericans that he realizes is doomed before even being proposed). I think the en dash is a much better solution, but it can only correct so much of a mess—there is some practical limit to the number of these non-adjectival parts of speech that can reasonably be employed. But like consensus, I don’t think it’s strictly a numbers game. I would prefer recasting quasi-legislative–quasi-judicial to quasi-legislative, quasi-judicial, partly because of its length, but also because nothing is lost in recasting—in fact, I think quite the opposite obtains.

With the anti-conscription–pro-conscription debate, the choice is not so obvious, and as it stands may well be the least of evils. An option might be volunteerism—conscription debate, but this is somewhat less clear because the nouns are different (I had to think about the meaning for a moment). I think the main reason for my tepid support is that it’s less easy for me to quickly distinguish en dashes from hyphens than to distinguish en dashes from spaces. But perhaps this is just a personal quirk.

As for the prescriptivism–descriptivism debate, it should be clear that I lean toward the former (especially for en dashes), but recognize that when well-established alternatives exist (especially when they reflect ENGVAR or its equivalent), I might allow any of them, possibly preferring one, if that alternative would normally reduce ambiguity. Like Blueboar, I might prescribe (or at least strongly recommend an approach if it’s one on which we clearly agree (e.g., parenthetical dashes and en dashes in ranges of numbers), especially when that practice finds nearly universal acceptance outside of WP. One always must be careful about claims of universality, of course; some guides (SP 811) deprecate range dashes for numbers in technical contexts, and some organizations (ASTM) proscribe them. In some cases (unspaced em dashes vs. spaced en dashes), an expressed preference would clearly not find any traction, and probably should not. And finding a justification other than WP:ILIKEIT would be almost impossible. One thing I certainly would not do without a mighty good reason is proscribe a common practice (e.g., closed-up use of range dashes) that finds broad support in the guides—it is difficult for me to see doing so as other than utterly capricious. The more such provisions we include, the more likely are editors to ignore the MOS (assuming they don’t already). JeffConrad (talk) 09:13, 14 July 2011 (UTC)

Thank you for reminding me of TKE, although I would ascribe it to both Fowlers. The section is available on line, and it is more concise that MEU in saying that there are only three forms of composition (closed up; spaced; hyphenated) and that the only call for a fourth is Anglo-South-Americans, where there is are different levels of composition. They recommend, as we should, Warsaw and Brest-Litovsk railway line instead of playing with hierarchy. Septentrionalis PMAnderson 02:19, 15 July 2011 (UTC)

Indeed, that 1908 Fowler's "King's English" predates any guides that I am aware of that talk about en dash usage. And it recommends things like "Covert-Garden-Market salesman" that modern guides eschew; the insertion of hyphens into compounds used as adjectives is deprecated when the compounds are proper names (not "Golden-Gate Bridge", but just "Golden Gate Bridge"). Dicklyon (talk) 02:31, 15 July 2011 (UTC)

Yes, the Fowlers call a hyphen a regrettable necessity; more were necessary in 1908 than are now (and more seem to have been necessary in Oxford than in San Francisco, even then); a compounding dash is equally regrettable and much less necessary. Septentrionalis PMAnderson 02:44, 15 July 2011 (UTC)

I have the 3rd ed. (1931), which ponders Anglo-SouthAmericans—progress of sorts, I suppose. Though it was completed after F.W.’s death, much of the content obviously derives from his efforts. As many have correctly observed, the Fowlers were fighting some battles that have long since been resolved. But it remains a valuable work, even one makes it only through the five principles that being Chapter 1. Unfortunately, even in the 3rd ed., TKE is of no help on en dashes—I mentioned it simply to show that the Fowlers were well aware of the problem. That we′re still having difficulty finding consensus on some issues suggests that even with dashes, the problem remains vexing.

As regards Warsaw and Brest-Litovski railway line: for a reference to the railway, this works. But a Warsaw and Brest-Litovski trip works less well, and clearly, Warsaw-Brest-Litovski trip does not work at all. What the Fowlers did not propose was Warsaw–Brest-Litovski trip, which seems to me to do the job. I concede that this usage wasn’t as enthusiastically embraced as some of the others, and it’s not the prettiest construction, but what are the alternatives? I suppose we could resolve it the way a mathematician would resolve default operator by using parentheses, as I have done in a few examples—namely Warsaw-(Brest-Litovski) trip. I somehow don’t see this getting very far. JeffConrad (talk) 06:56, 15 July 2011 (UTC)

The proper rewriting of Warsaw–Brest-Litovsk trip is trip from Warsaw to Brest-Litovsk, which offers no problem.

As a minor detail, the press report the Fowlers are criticizing seems to have confused the name of the latter city with its adjective; if we use this example, we should amend it.

But this presents another reason not to use such compounds where they can be avoided; they are inherently vague. Septentrionalis PMAnderson 18:35, 15 July 2011 (UTC)

If one is willing to forgo the adjectival usage, then of course this rewrite works. And it may be just as good. But were it unquestionably the “proper” rewrite, the Fowlers would probably not have bothered trying to deal with the adjectival form.

I guess the vagueness is in the eye of the beholder—I see no ambiguity in the form with the en dash, though I agree with many who though recasting may often be better. But in some contexts, recasting may not be practical, so it’s nice to have a way of handling the adjectival form. JeffConrad (talk) 22:06, 15 July 2011 (UTC)

The dash in Warsaw–Brest-Litovsk can mean several things, depending on context; the Fowlers dealt with a case where it did mean and; they recommended (as the surviving Fowler continued to recommend) abandoning the effort to pack it into a single adjective. Where's the profit in it?

But the fact that the dash can mean almost anything means it is inherently vague. Sometimes the ambiguity is settled by context; sometimes it isn't. Septentrionalis PMAnderson 23:18, 15 July 2011 (UTC)

Here's something that's just occurred to me. For prescriptivism vs. descriptivism, if prescriptive points must be supported by reputable sources, such as style guides, then descriptive points must be supported by sources of similar reliability, such as sociolinguistic studies. (Come to think of it, many of the style guides cited as prescriptive have passages that describe actual use, so perhaps they'd be usable for both.) Personal observations of "what people do" should be dismissed as OR unless also so supported.

And Noetica is a dude. He says so on his talk page or at least he did when I made a two-second pronoun check three years ago. It's not the most relevant of issues, but can we stop asking about it now? Darkfrog24 (talk) 02:49, 15 July 2011 (UTC)

I would happily defer to "sociolinguistic studies" if that means a controlled experiment to determine whether typical readers, not just punctuation mavens, understand material more quickly when dash rule number 89-4C-6 (f) is followed. But only if such studies exist. Art LaPella (talk) 04:16, 15 July 2011 (UTC)

Darkfrog, I largely agree. I clearly lean toward style guides, more out of practicality than ideology. It’s usually a fairly deterministic process to find (and perhaps cite) what Guide A recommends. There is of course the problem that Guide B may recommend something different, but at least is also fairly straightforward to find the differences and decide to prefer one or just allow both if A and B are widely respected. We can always argue whether a given guide is “widely respected”, but most of the guides provide help by listing most of the other major guides in bibliographies. Now perhaps this is all just a vast conspiracy, but the guides listed by the other guides seem to correspond well to measures such as ASR (Amazon sales rank). Perhaps this is a sort of descriptive prescriptivism.

The alternative is far less straightforward. As Art indicated, a study relevant to a particular issue would need to exist, be discovered, discussed, possibly interpreted as to how well it relates to the issue at hand and as to what it actually concludes, as opposed to differing WP:ILIKEITs. This seems to me a tall order, and arriving at a conclusion could make the discussion on dashes seem brief and trivial by comparison.

That’s why I look to the guides—though this may not be a perfect solution, it seems simpler, faster, and less subjective than the alternative. JeffConrad (talk) 07:20, 15 July 2011 (UTC)

So do I; most guides do not recommend most of this, and the exceptions have low ASR.

I guess we’d need to focus on specifics, but between APA and CMOS, most seem to be covered. And in the UK, NHR has reasonably high ASR. JeffConrad (talk) 22:13, 15 July 2011 (UTC)

Procedural subsection

¿There is still only halting progress because there’s complaining about what “consensus” means? The need to dwell on this point on Misplaced Pages is typically borne out of a minority side’s disputing that a consensus exists. Believe me—I know. I was exposed to a metric butt-load of Iranian-centrifuged, weapons-grade bullonium with complaints about how “There is no consenus!!!” over date de-linking and deprecating routine use of the IEC computer prefixes like “kibibytes”. In the end, the hold-outs lost because fighting against the consensus view is futile. What we need is the following:

All parties stipulate that Misplaced Pages:Consensus discloses all that is known and needs to be known about the subject.
Establish a clear consensus.
Find an uninvolved, respected admin who has huevos.
Have said admin rule on the consensus (win, lose, no consensus for the change).
Decisively deal with the holdout who has been giving you grief.

Greg L (talk) 22:39, 14 July 2011 (UTC)

The funny thing about consensus though is that it doesn't actually require anyone to "rule" on anything, "huevos" or not. Regardless... there is a well trod path through Misplaced Pages's dispute resolution process, what there is of it, which does utilize "finding an 'uninvolved' admin with 'huevos'" in order to adjudicate a ruling. I guess that it's just a pet peeve of mine that people refer to that (mistakenly) as "consensus", but... meh.
— V = IR (Talk • Contribs) 01:49, 15 July 2011 (UTC)

The sign of having achieved consensus is that you don't need an admin, nor huevos; nobody objects. That's what WP:CONSENSUS says; who objects to it?

Shouldn't this thread be under Procedure, the next section down? Septentrionalis PMAnderson 02:07, 15 July 2011 (UTC)

Note, I said thread, not section; I have made it a subsection. Septentrionalis PMAnderson 02:41, 15 July 2011 (UTC)

What consensus means

In the arbcom motion that led to this dash discussion, we were instructed "The discussion should be of sufficient structure to allow easy quantification of consensus rather than a large amount of poorly-framed debate." Casliber structured the discussion to make it easy to quantify agreements and disagreements with the various detailed provisions of the dash section. The result was that most sections had overwhelming support and agreement, but there were also a few less certain provisions and some constructive ideas for improvements. People who offered ideas and disagreements should check what they said, compare what ended up in Noetica's draft (the only currently active proposal, I think, since it has been largely accepted as an improvement on Kotniski's), and see if they're happy with it, and speak up one way or the other, so we can get the consensus finalized.

Jeff Conrad and I and a few others have weighed in above. I pretty much agree with Jeff that spaces around connective en dashes are rare (esp. in AmE), so I'm glad that the new draft backed off some from what the old one said. And I'm OK with the present compromise ("always unspaced, except for times and dates (or similar cases) when the components already include at least one space") as being motivated by the discussion (see 6b), even if it's hard to see exactly how far it should be changed from the votes at hand (PMAnderson is correct that the voting did not address this question, and the expressed disagreements leave a range of possible changes, of which Noetica's is somewhere in the middle); tweaking it can be left for a later round. At this point, I think minimal changes from the stable version, as motivated by a great discussion with wide participation, plus better clarifying examples, is what we can call consensus based on the discussion. Going further will require more work and more discussion to get to a consensus to do more, unless someone soon suggests specific changes that get little pushback. I made a few suggestions myself, but am content to let them slide to a later discussion, or forever. Let's get this done. Am I right? Or do we have to discuss a lot more first? Jeff? A. di M.? Kotniski? Tony? Anyone else who wants to comment on the new draft? Dicklyon (talk) 04:45, 18 July 2011 (UTC)

Discussion of procedure

I know probably no-one will like it, but here's my idea:

From Day 1 to Day 7, whoever can be bothered to shall review all recent discussion about this topic, write a draft in their own userspace reflecting the consensus as well as they can, review and comment other people's drafts, and tweak their own draft addressing other people's comments.
By the end of Day 7, I guess there will be a few such drafts (probably less than half a dozen); the drafts shall be locked down, and a new subpage shall be created where as many people as possible (through WT:MOS, WP:VP, WP:CENT, WP:RFC/STYLE, WT:WPMOS, maybe WT:GOCE, WT:TYP, WT:LANG, Talk:Dash, and possibly a watchlist-notice) shall be asked to review the drafts and sort them in order of preference, from Day 8 to Day 14.
At the end of Day 14, the ‘ballot’ page shall be locked down and the preferences evaluated according to the Schulze method or similar. The ‘winning’ draft shall then be copied and pasted, verbatim, replacing the entire current Section 8.9 “Dashes” of WP:MOS.
After that, tweaks to the guideline can be discussed and implemented through the normal WP:EDITREQ mechanism for protected pages.

(Of course, the better a drafter is at reflecting the community consensus, the more likely their draft is to win.)

― A. di M._plé 16:16, 13 July 2011 (UTC)

The Schulze method is contrary to our stated goals: to select the policy which as many people as possible can tolerate. Septentrionalis PMAnderson 16:28, 13 July 2011 (UTC)

I have been reviewing Noetica's draft, with respect to how well it incorporates fixes to all the disagreements that came up in the extensive discussions; I intend to recommend a few tweaks, but I think things would get out of control if I tried to make my own competing version; I don't think you'd find many editors with the patience to dig into differences and rank them at this point. But if someone thinks it is far enough off-base that they want to do a whole new one, I guess we'll look at that, too. As Noetica suggests, some notice of such an intention would help us keep our work in order. Sounds like there's some sentiment for a more "watered down" version from a few editors. Dicklyon (talk) 18:43, 13 July 2011 (UTC)

Only a few editors have commented on any draft.... Septentrionalis PMAnderson 18:54, 13 July 2011 (UTC)

Refactoring remains unacceptable; if Noetica repeats it, he or she (I don't know whicn) may explain that action elsewhere. Septentrionalis PMAnderson 23:53, 13 July 2011 (UTC)

Removed discussion (see preliminaries, above)

We now have an edit war over whether "What consensus means" should have === or ====. Would === = be an acceptable compromise? Another hot issue is Noetica's gender. See the top of his user talk page. And break your eggs on the big end only! Art LaPella (talk) 00:38, 14 July 2011 (UTC)

<chuckle> Fine; I was taught that gender should not matter; but Noetica was fiercely inovolved with the gneder-specific language movement. So rather than guess, I was non-specific.

What I object to, however, is having my comment refactorsd. That's obnoxious, and we have politcy against it. Septentrionalis PMAnderson 00:47, 14 July 2011 (UTC)

You presumably meant to say that only some comments should be refactored according to WP:TALKO (whether this is one of those times is an issue that you and Noetica can surely debate for weeks.) Art LaPella (talk) 01:17, 14 July 2011 (UTC)

No, I have never had a productive debate with Noetica (a neuter plural where I come from); I'd take him to ANI first. He does not have my consent. Septentrionalis PMAnderson 01:22, 14 July 2011 (UTC)

I did mis-guess Noetica's gender; this may (or may not) have to do with the fact that in my native language nouns such as matematica are feminine singulars. (But then, where I am from Andrea and Nicola are men's names, so I shouldn't use that as an excuse.) :-) ― A. di M._plé 14:45, 14 July 2011 (UTC)

WTF, nearly two days and neither of you guys has commented on whether it makes sense to call a girl Andrea given its etymology... :-) ― A. di M._plé 12:13, 16 July 2011 (UTC)

PMAnderson, you write: "Noetica was fiercely inovolved with the gneder-specific language movement ." That is a coloured characterisation ("fiercely") of an involvement that I have no recollection of. Please retract it. Your irrelevant asides focusing on me are a distraction. You have failed to retract all your pointed innuendos. Please remedy that. And striking out text will not be enough; I would like to participate in the important discussion above without attacks and provocations, whether they linger in the text or are perpetuated in edit summaries. I'm confident that other editors would take this to be a perfectly reasonable request. Noetica 03:07, 17 July 2011 (UTC)

I'm more inclined to assume good faith this time. I said "Another hot issue is Noetica's gender." That implied accusation entitles Septentrionalis to explain his half of that distraction. If, and only if, "Noetica was fiercely involved with the gender-specific language movement" is true, and if he has never been told Noetica's gender (although I've seen it repeatedly over the years by clicking Noetica's user name), then that is his explanation. Perhaps the most "inflammatory" comment above is my own: "... an issue that you and Noetica can surely debate for weeks", but somehow people seldom aim their best insults at me, on this page or any other battleground page. Art LaPella (talk) 06:13, 17 July 2011 (UTC)

Art, I admire your trust. But if you were as familiar with the relevant history as I am, that trust would melt away. PMAnderson knows exactly what he's doing. From one point of view, all of this is trivial. From another, it is of prime importance that we observe civility and work harmoniously. ArbCom has made the point explicitly. From the injunction under which we are currently working:

All discussions on the subject of En dashes in article titles discussion (interpreted broadly) are subject to civility and 1RR restrictions. Administrators are urged to be proactive in monitoring and assertive in keeping debate civil.

When PMAnderson acts and posts as he has, that is uncivil. When PMAnderson makes an edit summary that accuses me of "positive falsehood", that is uncivil; in fact, what he referred to in that summary represented merely a different take on certain voting, aided by a careless and slanted reading of what I had earlier said. You must know that I can look after myself in a street-fight, and have all sorts of tricks at my disposal if I choose to answer an assault with humour, incisive point-scoring, or ridicule. But the present matter is too serious for that. On the other hand, if people want to vary the framework and the suggestions I have made for the civil conduct of the discussion, sure: we could loosen up. Then we could have some real fun and fireworks. I'd rather we not do that; and I ask again that I be treated civilly (as the proposer of this move toward a resolution, with all of the difficult drafting that preceded it), as I treat others civilly also. I am keen to resume my involvement in the discussion; I'm waiting for conditions to be as ArbCom has said they should be.

Noetica 06:47, 17 July 2011 (UTC)

Your sentence about "accuses me of 'positive falsehood'" is a legitimate complaint to the extent you explained it. But for those of us less able to comprehend the "relevant history" and all the "tricks at disposal", you often seem to take offense at a long list of trivialities most of us wouldn't mention. In that case, emphasizing the need for civility counts against you. Art LaPella (talk) 15:45, 17 July 2011 (UTC)

So my insistence on the need for civility, which was also especially highlighted in an active ArbCom injunction, "counts against me"? I note your opinion, Art; others will agree with you, and others have agreed with me already. If I were to give the history that led us to this point, and has wasted weeks if not months of real time in people's real lives, you might find that uncivil of me. Hmmm. I say it would reveal incivility elsewhere; and it would reveal gross and sustained disruption to prove a point. I do not want to dwell on history, as I made clear in starting this whole section. Nor do I want to use kick-boxing techniques against unfair attacks. I can, but will not.

I am still waiting for a positive move toward respect and due process. Others may want to see the last several weeks' work dissipated; I do not.

Noetica 22:21, 17 July 2011 (UTC)

Civility complaints are the last refuge of those with no case on the merits. Septentrionalis PMAnderson 23:15, 17 July 2011 (UTC)

I expected my carefully hedged suggestion that "you often seem to take offense at a long list of trivialities" might get an angry outburst, although that suggestion was a natural response to a demand for civility. But instead I got an objection to the hint that such an offense-taking tendency is in itself a kind of incivility, thus aggravated by demanding civility of others. Oh well. Finish the dash draft? Art LaPella (talk) 00:27, 18 July 2011 (UTC)

No need to hedge anything with me, Art. If you want to accuse me of incivility, do so directly so that we can settle things briskly and move on. You say: "instead I got an objection to the hint that such an offense-taking tendency is in itself a kind of incivility." But I was not hedging anything, and I did not mean or wish to hint anything beyond what I said: "I note your opinion, Art; others will agree with you, and others have agreed with me already." I want to avoid innuendos. Let's all do that. And let's be definite about all the issues here. Since my last post here, PMAnderson has come in with the gratuitous suggestion that in calling for ArbCom's injunction to be respected and enforced (for civility), I show that I have "no case on the merits". That would be laughable, if this were at all a laughing matter. I could respond in the same vein, and we would all get nowhere.

I have nothing to apologise for. Others do have something to backtrack on, and I am still waiting for the air to be cleared so we can continue our work without threats, arch attacks, or wanton misrepresentations.

Noetica 00:52, 18 July 2011 (UTC)

I see no hope of re-explaining the re-explanation, so I'm giving up. Art LaPella (talk) 01:17, 18 July 2011 (UTC)

Art: If you take a little time away and then give the content of this section a detached reading, you may come to understand why I too have a feeling of the futility of it all. Then again, you may not. It's your call.

For my part, I am not giving up. Still just waiting. Noetica 01:56, 18 July 2011 (UTC)

Summary; final request to complete discussion; and notice of a final draft

ArbCom's deadline (16 July) has passed. The only task now is to finalise a draft for the dash guidelines. Since it is imperative to conclude things in a collegial way and to bring this protracted matter to an end, I am setting aside my concerns over civility. I simply call once more for good will, restraint, and focus on the task as we wrap things up.

I propose to post a final draft, 24 hours from now. Someone has to, and since I have become intimately familiar with the task and its details, I propose to do this myself. I continue, of course, to suppress my own personal preferences in style; I hope that others will do the same.

Below is a summary of editors' points about the present draft, with provision for brief discussion. I really hope that editors will not prolong discussion unreasonably. There will be opportunities in future, to revisit any guideline. Simple, short statements like "Agree", or "I can live with that for now", would be extremely helpful at this stage. This is not the place for deep analysis, generalities, politics, or digressions. Please keep comments neat and suitably indented, and do not start or continue lengthy exchanges. I will consider everything in this new final stage of discussion, as I prepare a final draft. Again, someone has to. ☺

Noetica 03:06, 19 July 2011 (UTC)

1. Length

Tony and A di M have taken up the matter of length that I raised. (I had written: "Editors will suggest ways to shorten it; but the voting has shown how easily brevity leads to entirely wrong interpretations. We need to guard also against intentional misconstrual.)" No one has suggested what might be taken out. A di M wrote: "I'm not sure exactly what words are the culprit, but I'm under the impression that Kotniski's version manages to say pretty much the same things more concisely and no less clearly." (I set aside the question of Kotniski's draft; I am among those who have thanked him for that effort; but the newer draft takes things further than his did.) It seems to me that if this were so, editors could find ways to trim the present draft. Let's have short, definite suggestions now, if anything is redundant and unhelpful in the draft.

Brief discussion

Agree Fine, brevity. No brainer. Greg L (talk) 05:37, 19 July 2011 (UTC)
Agree. Having read through it again, I'm impressed with the logic and efficiency of the examples. I learned from them, and other editors who want to should find them helpful and instructive. Editors who don't want to read them? Fine, others will be happy to fix. Tony (talk) 12:34, 19 July 2011 (UTC)
Agree – The length is OK; lots of examples good; more examples not really needed; no problem if you make minor adjustments one way or the other. Dicklyon (talk) 14:58, 19 July 2011 (UTC)
Disagree The length is excessive. Kotniski's draft is much shorter, and could be shortened further - yet it covers more ground. Septentrionalis PMAnderson 18:07, 19 July 2011 (UTC)
Agree if that means the current length is OK. Brevity that results in ambiguity is of little benefit. As I discuss under Spacing in ranges, I erred in providing far too few examples, including one that eluded me until this afternoon when I actually had to use it. The proposal concentrates more on examples than abstract descriptions, which is as it should be. JeffConrad (talk) 04:29, 20 July 2011 (UTC)

Response in the final draft

No specific actions were called for. I added a couple more examples, to satisfy other requests below. Noetica 10:42, 20 July 2011 (UTC)

2. Content and layout of examples

A. Jeff Conrad commented: "The order of the recommended/not recommended practice in the examples should match that in the text that precedes it." I argued that this was not essential, thinking that the order among examples (wrong version, then right version) trumped other considerations. It's hard to meet both requirements and maintain clarity.

Brief discussion

Agree Seems to be sensibly laid out. Greg L (talk) 05:37, 19 July 2011 (UTC)
Agree, although I see Jeff's point. Tony (talk) 12:34, 19 July 2011 (UTC)
Agree – the order is OK, and it would be hard to make it as consistent as Jeff suggests. Dicklyon (talk) 14:58, 19 July 2011 (UTC)
A matter of rhetorical choices at each juncture; if the examples are clear without being made into a French garden, who cares? Septentrionalis PMAnderson 18:07, 19 July 2011 (UTC)
Comment Recall that my suggestion was only that specific examples match the order of the text that describes them; It’s not a killer issue, but it would make it a bit easier on the reader. I see no need for overall consistence.
Comment Unless there is good reason to do otherwise, I would like to see the examples show adjectival usage, because these are the more challenging usages. I give the example of the 20 kHz–20Hz propagation delay, which fooled me until I just had to use it.
Comment I would like to see all examples of ranges of dates (and perhaps of physical quantities with appended units) include nonbreaking spaces where appropriate, as called for in WP:Manual of Style (dates and numbers)#Non-breaking spaces (e.g., between date numbers and month names, as in 1790 – 1 December); new editors often learn by looking at the code. JeffConrad (talk) 04:51, 20 July 2011 (UTC)

Response in the final draft

I have managed to satisfy Jeff's request regarding the order of texts and examples.
Several examples already show adjectival use; I have added two more, if we include ex–prime minister Thatcher (Jeff accepts that as adjectival below, but I don't). It is important to show non-adjectival uses also; they can be trickier in their way. This suggestion would have been better made during the last week, while the now superseded draft was on the table.
It was discussed earlier that the issue of hard spaces would be removed, for enhanced general treatment elsewhere in MOS. Again, it is awkward to have to revisit this issue at the last minute (beyond my 24-hour period of notice, and four days after ArbCom's deadline). For every reader of MOS who is helped by seeing   in examples, there will be another is flummoxed and alienated by it. Best treated specially elsewhere; and best to revisit this issue another time. Noetica 10:42, 20 July 2011 (UTC)

B. A di M commented: "I'd use examples like the current ones for the dash (with such über-familiar noun phrases as prime minister or World War II), and then after '... is possible and better' show seriously abstruse examples in red followed by a suggested rephrasing in green," and later: "... if we say that rewording is sometimes (but not always) better, I think we ought to include both examples of when it's better than when it isn't." My own view is that the present examples work well to make their points. I put a lot of thought into their selection. And we don't want more examples, surely.

Brief discussion

Agree They look like good examples. Greg L (talk) 05:37, 19 July 2011 (UTC)
Agree—No longer if possible, please. Very well laid out, IMO; it contains some tips for updating the rest of MoS in the future along these lines. Tony (talk) 12:34, 19 July 2011 (UTC)
Agree – a few more or less examples won't bother me, but I see no problem big enough to get hung up on. Dicklyon (talk) 14:58, 19 July 2011 (UTC)
Immaterial; but I'd like to see what A di M has in mind before deciding. Septentrionalis PMAnderson 18:07, 19 July 2011 (UTC)
Agree with current examples, but might consider a few specifics if they would illustrate points that would otherwise be lost. JeffConrad (talk) 04:51, 20 July 2011 (UTC)

Response in the final draft

I believe I have understood A di M's suggestion; I have added an example in response. Noetica 10:42, 20 July 2011 (UTC)

3. Expository points

A. Jeff Conrad thought "it might help to explain why 'Franco-British rivalry' takes a hyphen rather than an en dash." Agreed. I can do that, and had simply omitted the explanation to get fewer words. Any similar points, anyone?

Brief discussion

Agree Jeff gets his suggestion adopted. Greg L (talk) 05:37, 19 July 2011 (UTC)
Agree Tony (talk) 12:34, 19 July 2011 (UTC)
Agree – I'm OK with a bit more explanation, but don't see it as necessary really. Dicklyon (talk) 14:58, 19 July 2011 (UTC)
Disagree. The explanation is that compounds normally take hyphens (or spaces, or nothing). We do not need to deal with exceptions to exceptions. Septentrionalis PMAnderson 18:07, 19 July 2011 (UTC)

Response in the final draft

Despite PMAnderson's dissent, the request appears reasonable. I have satisfied it. Noetica 10:42, 20 July 2011 (UTC)

B. Dicklyon was "a little bothered by the statement 'These can be quite similar to uses of the hyphen; or less often, the slash.' " (See details above.) I accept this, and will make a change that expresses things better.

Brief discussion

Agree Dick made a good point. Greg L (talk) 05:37, 19 July 2011 (UTC)
Agree Tony (talk) 12:34, 19 July 2011 (UTC)
Agree – Thanks for hearing me; I'll trust that you'll improve it a bit. Dicklyon (talk) 14:58, 19 July 2011 (UTC)
Let's see what happens. Septentrionalis PMAnderson 18:07, 19 July 2011 (UTC)

Response in the final draft

Done. Explained. More needs to be said about these combining forms (Franco, Sino); but to get things concluded now, I'll hold back my concerns till the next time we visit the dash section. Noetica 10:42, 20 July 2011 (UTC)

4. Spacing in ranges

Both Jeff Conrad and Dicklyon had things to say about this. (So did A di M, but it seems to me that his concern over confusion with minus signs was adequately addressed. I am ready to be corrected, of course.)

Jeff wrote, for example: "Spacing of range dashes where one or more elements contains a space: either spaced or unspaced use should be allowed. The polling seems to indicate considerable support for allowing both." And later: "Though Noetica and I seem to differ fairly strongly on what has been concluded with regard to spacing of range dashes, it should be clear that this is the only point in the draft on which we really differ." And again: "Clearly it's impossible to arrive at formulaic guidance on when association implied by the en dash might misleading, and the same is probably true for any possible confusion between range dashes and parenthetical dashes. Practically, the choice would be a matter of personal choice—British practice aside from OUP is apparently to prefer the spacing, while North American practice is usually to prefer closed-up usage. The case for spacing is probably strongest with full dates and with instances similar to the last example above. Even so, NA seem to prefer closed-up usage."

Dick wrote: "I pretty much agree with Jeff that spaces around connective en dashes are rare (esp. in AmE), so I'm glad that the new draft backed off some from what the old one said. And I'm OK with the present compromise ("always unspaced, except for times and dates (or similar cases) when the components already include at least one space") as being motivated by the discussion (see 6b), even if it's hard to see exactly how far it should be changed from the votes at hand (PMAnderson is correct that the voting did not address this question, and the expressed disagreements leave a range of possible changes, of which Noetica's is somewhere in the middle); tweaking it can be left for a later round."

My own view, after careful consideration of this vexed issue: Jeff's concern is perfectly understandable. I had incorporated a "marginal" case of a compound date range (Christmas Day – New Year's Eve); strictly, it is such a case, and it would be a denial of the responsibility for a manual of style simply to exclude it as "too hard". People look to a manual to decide difficult cases. We could argue forever over this one, and about the principle as a whole; but in the end, we would still have to settle on a compromise. Dick is "OK with the present compromise", and "Noetica's somewhere in the middle". Finally, I agree with Dick that "tweaking it can be left for a later round"; and that applies to a number of finer points. Let's settle things for now, not for Doomsday or the afterlife.

Brief discussion

Agree A sensible amalgam of all input. Greg L (talk) 05:37, 19 July 2011 (UTC)
Agree. This is one of these cases where no "solution" can satisfy every fiddly case. Noetica's compromise is appropriate. Tony (talk) 12:34, 19 July 2011 (UTC)
Agree – It's OK, and I won't object if it changes a bit, now or later. Dicklyon (talk) 14:58, 19 July 2011 (UTC)
Disagree The way to settle it for now, not for Doomsday, is to be silent. The only thing that can be said definitively out of this is that there are several ways to space here; we don't need to say even that unless there is some reason to "extend our legislative hand" (and so breach policy). Septentrionalis PMAnderson 18:07, 19 July 2011 (UTC)
Partially Disagree. Though I, like the vast majority of guides, clearly prefer closed-up usage in all cases, my vote was a compromise, especially where we have a long-established practice of spacing the dash in complete date ranges in biographies. I still take issue with a few of the examples, however. In some cases, it is impossible to assess consensus because I don’t think we really voted on the issues; in a couple of others, spacing the dash creates real ambiguity rather than “initial ambiguity”, so it becomes far more than a matter of personal preference. Some specifics: I fail to see how different treatment of New York–London flight and Christmas Day–New Year’s Eve can be justified; there’s certainly no difference in “initial ambiguity”, and the latter is simply not a range of dates. The genuine ambiguity is more serious, as arises from 18 July – 3 September 2012. Even worse is ambiguity that arises spacing the dash in a range of quantities with repeated units. I just encountered a real-world example for which even my suggestion to use to would not work: I had need to refer to “the 20 kHz–20 Hz propagation delay”. Had I used the 20 kHz – 20 Hz propagation delay, I’d had have left the strong impression of subtraction, which would have been dead wrong because the actual difference here was one of time, not frequency. Now perhaps the reader would have sorted it out, but doing so would have required unnecessary effort. And I don’t think my suggestion of using to (the 20 kHz-to-20 Hz propagation delay) really works here, either. This example raises another point: unless there is good reason to do otherwise, I think the examples should show adjectival use, because it is usually the most challenging case.

Perhaps it could be said that these issues should have been raised earlier; if so, as the person who did the breakout, I must take much of the responsibility for failing to better separate some of the usages. Though some of my differences here are a matter of personal preference, I say once again that the sources agree with me. To the anticipated rejoinder that “we have moved beyond the guides”, I would say that I have a bit of a problem with summarily ignoring the “quality of the arguments” element of WP:CONSENSUS, especially since I raised it in polling. If we really feel that “I like it” sometimes carries the day, we should revise WP:CONSENSUS accordingly. If we simply ignore it, I fail to see how we could chide anyone for ignoring this guideline as well. Again, please take my comments here in perspective—recall that my first words were “It looks pretty good”, and the cases here are relatively few. Nonetheless, my disagreement remains strong on a few of them. JeffConrad (talk) 04:22, 20 July 2011 (UTC)

OK. Well, why not try working offline (backchannel, on your talk pages, whatever) with Noetica to hammer out a better solution. None of this stuff is locked in stone. Consensus can change. This is a complex package of changes and consolidations and there are bound to be points that can be modified or added. In that spirit, I hope one or both of you come back with a tweak you can accept in the spirit of compromise so you, Jeff, can be a member of an across-the-board consensus. Greg L (talk) 05:04, 20 July 2011 (UTC)

Response in the final draft

Dick, and Tony want to move on; PMAnderson wants silence; Jeff wants to expatiate at the eleventh hour; and Greg wants Jeff and me to get a room, where he can talk the legs off a chair and I can talk them back on again (count them at the end: there'll be five by then). Let's see what I can do ...
Jeff, your vote was a compromise? Fine. So was mine (I'd want certain headings to have been in this fold also, agreeing with at least five major style guides and de facto practice at OUP). The majority appears to be happiest with spaced en dashes for ranges when either component has a space; so we meet in the middle, with them. Now, you say that Christmas Day – New Year’s Eve is not a range of dates? I say it is; and that its similarity to New York–London flight is as superficial as the similarity of blue~green algae and red~green colorblindness (which we distinguish with "-" and "–"). We need to identify Christmas Day – New Year’s Eve as a range of dates in the examples, to make a robust, simple guideline that anyone can understand. It does no more harm to space this one than it does to space any other date example (with spaces in it). For that reason I have added a further example: Christmas 2001 – Easter 2002. That is a date range, surely. The user gets the idea, and can remember and apply it. Bear in mind that these date ranges typically occur in parentheses, where they can do no harm to the enclosing sentence. As for your highly unusual and recently discovered example Jeff (the 20 kHz – 20 Hz propagation delay), remember that hard cases make bad laws. There will always be rare, fluky situations that call for creative solutions; we soon get entangled if we make ourselves hostage to them.
Finally Jeff, you have misunderstand me if you think that I interpret consensus as only a matter of counting votes. I wish you had not raised this right here; but since you did, I will answer. I wrote of the "practical necessity" under which I operated, given Casliber's requirement they we vote clearly, to "quantify" the consensus. Take him to task, not me. It was extraordinarily hard to work up a draft drawing on every last eddy of opinion, in those two subpages crammed with comment. Luckily, the voting corresponded pretty well with the weight of argument and evidence (sign of a thoughtful group). I suggest that you revisit the top few sentences of WP:CONSENSUS, yourself. Take PMAnderson along with you. I quote: "Consensus is not necessarily unanimity. Ideally, it arrives with an absence of objections, but if this proves impossible, a majority decision must be taken. More than a simple majority is generally required for major changes." We have every reason to believe that this is such a case. Practical necessity, once more. But still, who is not trying for something better, by reason, compromise, and consultation? I know I have been, for the last several months. Noetica 10:42, 20 July 2011 (UTC)

5. En dash with spaced components

Jeff Conrad wrote: "I would add one example in which the first component contains a space (e.g., Chuck Berry–style lyrics ...". And further on this matter: "One approach would be to permit either usage, possibly encouraging consistent use of either North American or British practice, though this could be tricky because some practices may be chiefly (but not exclusively) North American, and others may be chiefly (but not exclusively) British. / I can’t say whether the fact that one construction may indicate the structure more clearly is sufficient to deprecate an alternative construction, but it seems to me that the point of en dashes in nearly all cases is to more clearly indicate what is meant than would a hyphen. So if it doesn’t matter here, it arguably doesn’t matter anywhere."

Dick wrote: "So is this one more optional than most? If some editor changes 'ex–prime minister' back to the hyphen version, should we complain and fix it back? I still think we should, since if an editor finds it useful to use punctuation to signal the structure more clearly, we ought to let them. In that sense, I don't see the point of trying to make this one more optional than most, as some are suggesting. On the other hand, I don't have strong feelings about it, and would be willing to go with adjustments if there's a consensus to do so."

Myself, I articulated my objections to this principle in the voting. I think it is quite unnecessary; but I put it in the draft because including it seemed more acceptable to more people than leaving it out. More importantly, I think, a substantial majority have expressed a wish for a simple principle, here and throughout the voting: either explicitly, or more often by their simple "agree". That is my view also: I don't like it, but stability and consistency on this particular principle is important in article titles especially, so let's go for the dominant way to lessen discord in future, and also possible searching problems. I also pointed out to Jeff Conrad that cases like Chuck Berry–style lyrics were not voted on. Again, the present round of discussion need not be final; but it ought to be finalised. If anyone feels strongly about this in the future, let it be raised when the present work is behind us.

Brief discussion

Agree Good analysis on how to handle en-dashes. Greg L (talk) 05:37, 19 July 2011 (UTC)
Agree—No strong feelings, but I'm more used to it now, and have even introduced it in a recent FAC lead, because it seemed more elegant than a triple hyphenated unit. While I think some readers may not be familiar with the usage, it's intuitive enough. Tony (talk) 12:34, 19 July 2011 (UTC)
Agree – I like this Americanism, but I won't object later if we want to adjust it to be more optional. Dicklyon (talk) 14:58, 19 July 2011 (UTC)
Disagree. There was a majority against requiring ex–prime minister; there was a majority to perfer it; neither was consensus. Any draft which requires it deserves dispute resolution. Septentrionalis PMAnderson 18:07, 19 July 2011 (UTC)
Agree – This works for me.--Epeefleche (talk) 20:32, 19 July 2011 (UTC)
Agree Like Dick, I think it adds clarity in some cases, and probably more so than with prefixes. And as I’ve said, if a hyphen is OK here, it’s OK in many other cases where we call for an en dash. Be assured, though, that I won’t be running around looking for uses of the hyphen here to correct. I would, however, have the examples show adjectival use (e.g., ex–prime minister Brown) because I think the benefit is more obvious}} (and how should “former prime minister Brown” be handled?). JeffConrad (talk) 05:02, 20 July 2011 (UTC)

Response in the final draft

My analysis of the voting differs from PMAnderson's. Analysing the votes with their associated comments (as everyone accepts that we should), and seeing what the voters were willing or unwilling to accept, I count it this way. Of the 29 who voted on this principle (including PMAnderson, though he did not vote outside the navbox):
- 7 rejected it outright (SarekOfVulcan, Powers, Hullaballoo Wolfowitz, SJ, Headbomb, Nageh, Telpardec)
- 7 accepted it, but asked that it be optional (WFC, A di M, Powers, Enric Naval, Ozob, JN466, PMAnderson)
- 15 accepted it, and did not ask that it be optional (JeffConrad, Kotniski, Armbrust, Dabomb87, Tony, Kwami, ErikHaugen, Dicklyon, CWenger, Jenks24, Courcelles, macwhiz, Finell, InverseHypercube, Noetica )

That's a simple majority (15–14) accepting it without any option; and that's a clear majority accepting it in one way or another (22–7). Only 7 out of 29 favour giving a choice. Nothing in WP:CONSENSUS obliges us to accommodate every minority preference in a manual of style. That's not what manuals of style are for. Last, we don't know what those 7 would say to this question: "Do you want a manual of style to set a simple uniform guideline for everyone?" That number would have been 8, remember: but I gave up my opposition to the principle for the larger good: consistency of style on Misplaced Pages. In fact, I would have held out and maintained opposition; but Jeff was so adamant, and the principle is so widely accepted in America, that I yielded.

I have amended the heading for the section; we voted on prefixes, and it is confined to prefixes.
By an extreme act of contortion, I have amended the guideline in the final draft so that it applies in an acceptable, well-delimited set of cases, and recasting is to be clearly preferred in all other cases. I submit that this is an optimal solution. Noetica 10:42, 20 July 2011 (UTC)

6. In lists

Jeff Conrad wrote: "The usage within items in a list (which I’m still not convinced is a distinct case) should not lend itself to be read as precluding alternatives." And Dick wrote: " 'To separate items in certain lists' is not a separate role, but just another case of using spaced en dash as a dash; same idea in Kotniski's point."

Do editors really care enough about this right now, though? The present draft does the best it can to preserve what the current stable guideline says, but just makes it clearer. I propose that we leave this topic for possible consideration later, also.

Brief discussion

Agree That’s fine too. Going back to serial tweaking later to further flesh this out (like we used to do) will kill no one. Greg L (talk) 05:37, 19 July 2011 (UTC)
Agree. I must say, spaced en dashes in lists look the best to me—far better than most alternatives—but the draft is fine. Tony (talk) 12:34, 19 July 2011 (UTC)
Agree – It's kind of a misfit point, but not doing any real harm; defer adjustments to later. Dicklyon (talk) 14:58, 19 July 2011 (UTC)
Disgree This has never been important; nobody has argued for this at all strongly; Jeff has expressed continued puzzlement as to what this means or why. The provision this has evolved from was a profitless choice between two perfectly reasonable ways to format lists. Take out the whole point, until somebody presents an actual difficulty. Septentrionalis PMAnderson 18:07, 19 July 2011 (UTC)
Agree – This also works for me, for the moment, and agree that further changes could be considered at a later point.--Epeefleche (talk) 20:32, 19 July 2011 (UTC)
Agree that because the proposal includes examples, it’s a big improvement, provided that we don’t see it as precluding other punctuation. I still have doubts about whether this is a distinct usage, but this is a minor issue that can be dealt with later if it’s felt necessary. JeffConrad (talk) 05:06, 20 July 2011 (UTC)

Response in the final draft

Nothing to do; nothing done. Noetica 10:42, 20 July 2011 (UTC)

7. Points to deal with elsewhere, outside the dashes guideline

A di M expressed this view: "Image filenames are even less relevant than recasting or hard spaces or exception would be."

I am happy to take out the mention of dashes and hyphens in filenames, subject to there being no objection here.

Brief discussion

Agree To make progress and break out of the current morass, there is no harm not addressing file names now; that issue can always be addressed in the far, far off future in Misplaced Pages time (next week in real time) if needed. Greg L (talk) 05:37, 19 July 2011 (UTC)
Agree Tony (talk) 12:34, 19 July 2011 (UTC)
Agree – Image filenames are not part of "style", but I don't care if they're in or out at this point. Dicklyon (talk) 14:58, 19 July 2011 (UTC)

Response in the final draft

Done. We must follow up with changes elsewhere in MOS, for this and the other points that were to be moved outside the dash guideline. Noetica 10:42, 20 July 2011 (UTC)

8. Any points that have been missed in the above

None Noetica, you’ve truly done a great job trying to capture the essential elements of everyone’s input to arrive at a distillation around which a general consensus can form. It is a magnificent effort in an all-volunteer, collaborative writing environment. Your heavy lifting here has not gone unnoticed. Greg L (talk) 05:37, 19 July 2011 (UTC)

Brief discussion

Great job, Noetica. Tony (talk) 12:34, 19 July 2011 (UTC)
Thanks – for taking on the brunt of the work, and dealing with the inevitable blowback. I support you, and want to get this done, so will not offer any more new complications at this point. Dicklyon (talk) 14:58, 19 July 2011 (UTC)
Noted. Noetica's draft does not even represent the views of a majority, much less consensus. Those who approve of it approve of ignoring discussion, usage, and sources. Septentrionalis PMAnderson 18:07, 19 July 2011 (UTC)

Quoting you, PMA: Noetica's draft does not even represent the views of a majority, much less consensus. What defines a consensus is being determined now; here. Perhaps the consensus will be that it is a good step. Perhaps the consensus view will be that it smells like a Frenchman’s armpits; we’re not done yet. Whatever you think of Noetica’s effort at consensus-building in light of past water under the bridge is irrelevant now. No one said working in a collaborative writing environment is easy. You had an opportunity here to make compelling oratory to sway group opinion. The tenor of your posts makes me not so sure you exploited the opportunity to the fullest. Greg L (talk) 20:39, 19 July 2011 (UTC)

It does seem odd that PMA picks mainly on the minor "ex–prime minister" provision now, given that the section Wikipedia_talk:Manual_of_Style/dash_drafting#In_compounds_whose_elements_themselves_contain_hyphens_or_spaces was not among those that he disagreed with; he says it "deserves dispute resolution," as if that's not what we're approaching closure on. And unclear what he means by "not even...a majority" if one-third of the people expressed some reservations and disagreements (including Noetica, himself, who is now trying to find a consensus compromise that isn't even his own opinion). And now PMA objects to mentioning the role of en dashes as separators in list items, but he didn't say so when he had the chance at Wikipedia_talk:Manual_of_Style/dash_drafting#To_separate_items_in_a_list (actually, if you "open" the "superceded" bit there, you can see that he said he agreed). Now he says this "has never been important; nobody has argued for this at all strongly," which might be true, but holding up resolution for a point that he said he agrees on, and that he agrees is unimportant, seems like just a stalling tactic. If he wants to propose changing either of these later, I might even agree with him for a change, but that's not where we're at. As for his statement that we "approve of ignoring discussion, usage, and sources," I just don't get what makes him say such things; just trolling, I guess. Also note that on Noetica's draft that we're discussing final changes to, PMA offered neither any criticism nor any suggested changes, but just procedural complaints; so to object now to Noetica's attempts to address all the suggestions seems at least counter-productive, if not in plain bad faith. Dicklyon (talk) 02:07, 20 July 2011 (UTC)

It’s time to stop dumping on PMA. His style tends to be a hard-to-ignore one-man band. We all know that. In the past, too much has been made of his opposition and he has—in my opinion—had influence wildly in excess of head count. There’s been back & forth finger pointing and accusations that the other side has been operating… uhm… *cheatfully*. The Good Ship Major Malfunction has sailed. PMA is just one voice. He’s stated his opinion: fine, thank you very much; time to move on. If a consensus can’t be made here despite his opposition, then there one or more shortcomings in Noetica’s proposal that need to be ironed out in order to get more editors singing from the same sheet of music. Noses back to the grind stone please. Greg L (talk) 05:16, 20 July 2011 (UTC)

Though I still have a couple of very strong disagreements about a few points (and possibly the procedure at arriving at them), I stress again that the overall effort is a great job. JeffConrad (talk) 05:10, 20 July 2011 (UTC)

Response from Noetica

Thanks! Now can we just settle this damn thing? It's been going for months. I don't know about others, but I'm exhausted. Just compromise, yeah? I myself have strong disagreements with the draft I have made. But it works. You will not find a more considered, more complete, more sensitive solution to this hardest of problems in modern punctuation. Not on the web; not anywhere. And we did it together. Noetica 10:42, 20 July 2011 (UTC)

Final draft 1: please endorse, or comment

I present what I am calling "Final draft 1" for the dashes section. It responds to suggestions made in the preceding subsection, where I have now enumerated the changes and responded to all concerns. Changes are marked in this new draft by underlining, and in one case by striking through. To see the new draft, click on "Show", at the right:

Final draft 1
Dashes Shortcuts MOS:DASH WP:DASH Two forms of dash are used on Misplaced Pages: en dash (–) and em dash (—). Type them in as `&ndash` (–) and `&mdash` (—); or click on them to the right of the "Insert" tab under the edit window; or see How to make dashes. ~~Use hyphens, never dashes, in filenames of images, sounds, or other included media.~~ When a dash is used in the title of an article (or any other page), there should be a redirect from a hyphenated version: Eye-hand span redirects to the article Eye–hand span. Sources use dashes in varying ways, but for consistency and clarity Misplaced Pages adopts the following principles. Punctuating a sentence (em or en dashes) Shortcuts MOS:EMDASH MOS:SENTENCEDASH WP:EMDASH WP:MDASH WP:SENTENCEDASH Dashes are often used to mark divisions within a sentence: in pairs (parenthetical dashes, instead of parentheses or pairs of commas); or singly (perhaps instead of a colon). They may also indicate an abrupt stop or interruption, in reporting direct speech. There are two options. Use one or the other consistently in an article. 1. Unspaced em dash Another "planet" was detected—but it was later found to be a moon of Saturn. Or: 2. Spaced en dash Another "planet" was detected – but it was later found to be a moon of Saturn. Do not use spaced em dashes. Another "planet" was detected — but it was later found to be a moon of Saturn. Dashes can clarify the sentence structure when there are already commas or parentheses, or both. We read them in chronological order: Descartes, Locke, Hume—but not his Treatise* (it is too complex)—and Kant. Use dashes sparingly. More than two in a single sentence makes the structure unclear; it takes time for the reader to see which dashes, if any, form a pair. The birds—at least the ones Darwin collected—had red and blue feathers. "Where is the—", she said, but then realized she held it in her hand. First in the procession—and most spectacularly—came the bishops—then the other clergy. En dashes: other uses* Shortcuts MOS:ENDASH MOS:NDASH WP:ENDASH WP:NDASH The en dash (–) has other roles, beyond its use as a sentence-punctuating dash (see immediately above). It is often analogous to the hyphen (see the section above), which joins components more strongly than the en dash; or the slash (see the section below), which separates alternatives more definitely. Consider the exact meaning when choosing between these three. En dashes are used in four ways. 1. In ranges that might otherwise be expressed with to or through pp. 211–19; 64–75%; the 1939–45 war Do not mix en dashes with prepositions like between and from. 450–500 people between 450–500 people; between 450 and 500 people from 450–500 people; from 450 to 500 people If negative values are involved, an en dash might be confusing. Use words instead. −10–10; −10 to 10 the drop in temperature was 5°–−13°; the drop in temperature was from 5° to −13° The en dash in a range is always unspaced, except for times and dates (or similar cases) when the components already include at least one space. 23 July 1790–1 December 1791; 14 May–2 August 2011 23 July 1790 – 1 December 1791; 14 May – 2 August 2011 10:30 pm Tuesday – 1:25 am Wednesday; Christmas Day – New Year's Eve; Christmas 2001 – Easter 2002 1–17 September; February–October 2009; 1492? – 7 April 1556 Best absorbed were wavelengths in the range 28 mm – 17 m. 2. In compounds when the connection might otherwise be expressed with to, versus, and, or between Here the relationship is thought of as parallel, symmetric, equal, oppositional, or at least involving separate or independent elements. The components may be nouns, adjectives, verbs, or any other independent part of speech. Often if the components are reversed there would be little change of meaning. boyfriend–girlfriend problems; the Paris–Montpellier route; a New York–Los Angeles flight iron–cobalt interactions; the components are parallel and reversible; iron and cobalt retain their identity an iron–roof shed; iron* modifies roof, so use a hyphen: an iron-roof shed the poet's mentor–muse; not separate persons, so use a hyphen: the poet's mentor-muse red–green colorblind; red and green are separate independent colors, not mixed blue–green algae; a blended, intermediate color, so use a hyphen: blue-green algae Franco–British rivalry; "Franco", is a combining form, not independent; use a hyphen: Franco-British rivalry France–Britain rivalry; French–British rivalry a 51–30 win; a six–two majority decision; the Lincoln–Douglas debates an Italian–Swiss border crossing; but an Italian-Swiss newspaper, for Italian-speaking Swiss the Uganda–Tanzania War; the Roman–Syrian War; the east–west runway diode–transistor logic; the analog–digital distinction; a carbon–carbon bond a pro-establishment–anti-intellectual alliance Singapore–Sumatra–Java shipping lanes the ballerina's rapid walk–dance transitions; a male–female height ratio of 1.2 A slash or some other alternative may occasionally be better to express a ratio, especially in technical contexts (see Slashes below). the protein–fat ratio or the protein/fat ratio, or even the protein-to-fat ratio An en dash is not used for a hyphenated personal name. Lennard-Jones potential with a hyphen: named after John Lennard-Jones An en dash is used for the names of two or more people in a compound. the Seifert–van Kampen theorem; the Seeliger–Donker-Voet scheme; the Alpher–Bethe–Gamow theory Comet Hale–Bopp or just Hale–Bopp (discovered by Hale and Bopp) Following the dominant convention, a hyphen is used in compounded place names and language names, not an en dash. Guinea-Bissau; Austria-Hungary an old Mon-Khmer dialect; Niger-Congo phonology The en dash in all of the compounds above is unspaced. 3. Instead of a hyphen, when applying a prefix to a compound that includes a space ex–prime minister Thatcher; pre–World War II aircraft Use this punctuation when the construction must be retained—for example in a transcription of a speech, or in a heading that is already chosen as optimal. Otherwise recasting is better. Keep: Post–September 11 anti-war movement (a Misplaced Pages article) Best to recast the two examples above: former prime minister Thatcher; aircraft before World War II Very awkward: the mother had post–difficult birth health problems; recast as the mother had health problems after a difficult birth The en dash in all of the compounds above is unspaced. 4. To separate items in certain lists Spaced en dashes are used within parts of certain lists. Here are two examples: Pairing performers with instruments. James Galway – flute; Anne-Sophie Mutter – violin; Maurizio Pollini – piano. Showing track durations on a CD. The future – 7:21; Ain't no cure for love – 6:17; Bird on the wire – 6:14.

Final draft 1

Dashes

Shortcuts

~~Use hyphens, never dashes, in filenames of images, sounds, or other included media.~~
When a dash is used in the title of an article (or any other page), there should be a redirect from a hyphenated version: Eye-hand span redirects to the article Eye–hand span.

Sources use dashes in varying ways, but for consistency and clarity Misplaced Pages adopts the following principles.

Punctuating a sentence (em or en dashes)

Shortcuts

There are two options. Use one or the other consistently in an article.

1. Unspaced em dash

Another "planet" was detected—but it was later found to be a moon of Saturn.

Or:

2. Spaced en dash

Another "planet" was detected – but it was later found to be a moon of Saturn.

Do not use spaced em dashes.

*Another "planet" was detected — but it was later found to be a moon of Saturn.

Dashes can clarify the sentence structure when there are already commas or parentheses, or both.

We read them in chronological order: Descartes, Locke, Hume—but not his Treatise (it is too complex)—and Kant.

Use dashes sparingly. More than two in a single sentence makes the structure unclear; it takes time for the reader to see which dashes, if any, form a pair.

The birds—at least the ones Darwin collected—had red and blue feathers.
"Where is the—", she said, but then realized she held it in her hand.
*First in the procession—and most spectacularly—came the bishops—then the other clergy.

En dashes: other uses

Shortcuts

The en dash (–) has other roles, beyond its use as a sentence-punctuating dash (see immediately above). It is often analogous to the hyphen (see the section above), which joins components more strongly than the en dash; or the slash (see the section below), which separates alternatives more definitely. Consider the exact meaning when choosing between these three. En dashes are used in four ways.

1. In ranges that might otherwise be expressed with to or through

pp. 211–19; 64–75%; the 1939–45 war

Do not mix en dashes with prepositions like between and from.

450–500 people
*between 450–500 people; between 450 and 500 people
*from 450–500 people; from 450 to 500 people

If negative values are involved, an en dash might be confusing. Use words instead.

*−10–10; −10 to 10
*the drop in temperature was 5°–−13°; the drop in temperature was from 5° to −13°

The en dash in a range is always unspaced, except for times and dates (or similar cases) when the components already include at least one space.

*23 July 1790–1 December 1791; *14 May–2 August 2011
23 July 1790 – 1 December 1791; 14 May – 2 August 2011
10:30 pm Tuesday – 1:25 am Wednesday; Christmas Day – New Year's Eve; Christmas 2001 – Easter 2002
1–17 September; February–October 2009; 1492? – 7 April 1556
Best absorbed were wavelengths in the range 28 mm – 17 m.

2. In compounds when the connection might otherwise be expressed with to, versus, and, or between

Here the relationship is thought of as parallel, symmetric, equal, oppositional, or at least involving separate or independent elements. The components may be nouns, adjectives, verbs, or any other independent part of speech. Often if the components are reversed there would be little change of meaning.

boyfriend–girlfriend problems; the Paris–Montpellier route; a New York–Los Angeles flight
iron–cobalt interactions; the components are parallel and reversible; iron and cobalt retain their identity
*an iron–roof shed; iron modifies roof, so use a hyphen: an iron-roof shed
*the poet's mentor–muse; not separate persons, so use a hyphen: the poet's mentor-muse
red–green colorblind; red and green are separate independent colors, not mixed
*blue–green algae; a blended, intermediate color, so use a hyphen: blue-green algae
*Franco–British rivalry; "Franco", is a combining form, not independent; use a hyphen: Franco-British rivalry
France–Britain rivalry; French–British rivalry
a 51–30 win; a six–two majority decision; the Lincoln–Douglas debates
an Italian–Swiss border crossing; but an Italian-Swiss newspaper, for Italian-speaking Swiss
the Uganda–Tanzania War; the Roman–Syrian War; the east–west runway
diode–transistor logic; the analog–digital distinction; a carbon–carbon bond
a pro-establishment–anti-intellectual alliance
Singapore–Sumatra–Java shipping lanes
the ballerina's rapid walk–dance transitions; a male–female height ratio of 1.2

A slash or some other alternative may occasionally be better to express a ratio, especially in technical contexts (see Slashes below).

the protein–fat ratio or the protein/fat ratio, or even the protein-to-fat ratio

An en dash is not used for a hyphenated personal name.

Lennard-Jones potential with a hyphen: named after John Lennard-Jones

An en dash is used for the names of two or more people in a compound.

the Seifert–van Kampen theorem; the Seeliger–Donker-Voet scheme; the Alpher–Bethe–Gamow theory
Comet Hale–Bopp or just Hale–Bopp (discovered by Hale and Bopp)

Following the dominant convention, a hyphen is used in compounded place names and language names, not an en dash.

Guinea-Bissau; Austria-Hungary
an old Mon-Khmer dialect; Niger-Congo phonology

The en dash in all of the compounds above is unspaced.

3. Instead of a hyphen, when applying a prefix to a compound that includes a space

ex–prime minister Thatcher; pre–World War II aircraft

Use this punctuation when the construction must be retained—for example in a transcription of a speech, or in a heading that is already chosen as optimal. Otherwise recasting is better.

Keep: Post–September 11 anti-war movement (a Misplaced Pages article)

Best to recast the two examples above: former prime minister Thatcher; aircraft before World War II
Very awkward: *the mother had post–difficult birth health problems; recast as the mother had health problems after a difficult birth

The en dash in all of the compounds above is unspaced.

4. To separate items in certain lists

Spaced en dashes are used within parts of certain lists. Here are two examples:

Pairing performers with instruments.
- James Galway – flute; Anne-Sophie Mutter – violin; Maurizio Pollini – piano.
Showing track durations on a CD.
- The future – 7:21; Ain't no cure for love – 6:17; Bird on the wire – 6:14.

Noetica 10:42, 20 July 2011 (UTC)

Suggested procedure

Editors, please review the draft, comparing it with the previous one and checking the comments I make above about changes.
Consider carefully the need to yield on some points; we all have had to do that. Consider the value of this draft for the Project.
Note errors, omissions, or final small fixes in the subsection below, in orderly and considerate brevity.
If you absolutely must object to anything, do so soon and clearly, proposing a precise solution, rather than calling vaguely for something to be redrafted.
Remember that we have been at this for months, and that we are four days overdue already. Eight weeks (effectively) ought to have been enough time to settle all the issues.
Please have your say within 24 hours from now. After 24 hours, I will take whatever next step is appropriate (since I am used to dealing with this, I might as well be the one to carry it through). And we can get a completed version incorporated into WP:MOS.

Endorsements, and final points to fix

Dash confusion

Resolved

I can't make heads or tail out of the blur of words in the two sections above. There appears to be quite a bit of lecturing, and a bunch of arguing in response, but I don't see anything concrete. Cut to the chase: What's the actual proposal? In other words, what is going to change in the MoS?
— V = IR (Talk • Contribs) 17:59, 13 July 2011 (UTC)

Noetica's proposal is behind the green line with the {{show}} button, headed (with improper formatting) The proposal itself; Kotniski's proposal, amended by several hands, is at Misplaced Pages:Manual of Style/Dash draft. As a procedural matter, putting a proposal at a subpage with a clearly marked link seems better. Septentrionalis PMAnderson 18:02, 13 July 2011 (UTC)

Thanks.
— V = IR (Talk • Contribs) 18:05, 13 July 2011 (UTC)

em or en dash for fluorine-fluorine bond?

I am seeing em dashes in the "Fluorine" article. Looking at our guide, it seems that an en dash makes sense. Maybe if one actually uses the letters to write out some formula in text (ala C-H bond), than the em dash makes sense. since you're really writing a structural formula at that point. But I would assume when we are using words, it is just normal usage of a dash to substitute for the word "to". I admit not knowing how this is handled in the real world...and if our Wiki guidance is unclear, than let's just do what most people using English do. But if we have a Wiki rule, just let me know and I will follow. And I looked at MOS-chem and it did not have guidance either.TCO (reviews needed) 07:36, 14 July 2011 (UTC)

En dash, obviously. Headbomb {talk / contribs / physics / books} 07:43, 14 July 2011 (UTC)

Yup, en dash. And when it's a repeated word (like "protein–protein"), it's somehow less likely to be confusing. I'd have thought much easier to read as symbols, too: C–H bond. The musicians use en dashes for chords (C–E–G). Tony (talk) 07:46, 14 July 2011 (UTC)

Agree with Headbomb.--Epeefleche (talk) 08:49, 14 July 2011 (UTC)

It'd be nice for it to be the same length as the = for the double bond and the ≡ for the triple bond... Test:

Hyphen	En dash	Em dash	Minus sign
C-C C=C C≡C	C–C C=C C≡C	C—C C=C C≡C	C−C C=C C≡C

On my system, the hyphen is way too short, the en dash a little too short, the em dash too long, and the minus sign just right; YMMV depending on your font, I suppose. ― A. di M._plé 13:18, 14 July 2011 (UTC)

WAIT! Our minus sign is different from both the hyphen and en dash? Am still getting used to using an endash instead of hyphen. :-) TCO (reviews needed) 14:08, 14 July 2011 (UTC)

It's not "our" minus sign; it's up to whoever designed the font that your browser is using; they're not all sensible. Dicklyon (talk) 14:12, 14 July 2011 (UTC)

Alignment of images in lead

Can someone point me at any discussion that preceded this edit? It's a topic of disagreement at Talk:Joseph Priestley, and since that edit is being cited as a reason for the change at that page I'd like to understand how it came about. Mike Christie (talk - contribs - library) 12:49, 14 July 2011 (UTC)

I have no good idea how that got in the MOS and I hate the rule-pushers, who don't look at how an article really serves a reader, but try to dictate some wiki-uniformity when they don't have the work ethic or brains to really try to layout content and think of readers in the abstract. All that said, I think the image works just ducky on the right side. I think the looking in or out of the page aspect is way over-rated in terms of how it really hits a reader and you should think more of the overall layout (where would you want the pic if you had no idea which way the fellow was looking). That said, if someone is pushing you to stick an infobox in that glorious article...I have your back. Also, there are a shitload of very important (even "vital") articles that can use real work and should be the attention of interlopers...rather than trying to barge in and start arguments on things where there is very evident care and effort going on already.TCO (reviews needed) 13:03, 14 July 2011 (UTC)

Am curious how you find the diff where text changed. I have a little something that is bugging me wrt pushing of (extra) wikilinks in captions which makes no sense given we want clean unformatted prose and that within the rest of the article, we don't require repetition of wlinks.TCO (reviews needed) 13:03, 14 July 2011 (UTC)

I linked to it from the discussion in question (which does not feature "interlopers" trying to force rules down people's throats as so casually implied above; most parties involved have been involved in this particular discussion for two years). Odd that you would claim to have "no good idea how that got in the MOS" when you were directly involved in the last thread discussing the matter before it was changed, TCO. FYI Mike, there have been at least two discussions since that change which reference it. Chris Cunningham (user:thumperward) - talk 14:32, 14 July 2011 (UTC)

A. I'm very capable of forgetting a thread from December, Chris! Although I think if you read the content of my remarks, my views have not evolved much (although sometimes they may). B. I don't see how I am supposed to connect that thread to a certain change in the MOS (don't see the wording mentioned or me opining on it. C. Both versions to my quick read seem pretty similar and besides I don't see where infoboxes were mentioned in the thread you have me in in December. D. I am still interested technically in how we track down "when the text changed". E. I'm concerned after seeing you nominate a bunch of templates for deletion because you disagreed with their style (and got roundly defeated btw) that you are trying to "work the system" or get things in "policy" to support your style views. I'm sure you are a good guy or think you are a good guy (AGF, blabla), but maybe take a step back and consider how much you are helping build things versus how much having Internet battles you try to win.TCO (reviews needed) 15:13, 14 July 2011 (UTC)

This section used to say that the guidance for images was a bunch of desirable things which might not all be possible. That is what common sense should still say; always ignore the rules when they inconvenience an article. Septentrionalis PMAnderson 18:36, 16 July 2011 (UTC)

English Wikpedia in common English language !

After been redirected from "petrol" to "gasoline" (a word that isn't used even across the Atlantic, they just say "gas") I write this in some anger. And I strongly suggest that UK english ("the Queen's english" if You like) should be used in Misplaced Pages, and never any other kind of secondary-language like american-English. For the following reasons:

All English language is descended from the UK.
It's the UK English that is taught in schools worldwide.
For all them who don't have English as first language but can use it, american (mis-)spellings like "color" just causes confusions.

. I'm neither from the UK or any other country were English is the primary language. 83.249.32.242 (talk) 23:46, 14 July 2011 (UTC)

Thank you for your contribution.--Epeefleche (talk) 23:51, 14 July 2011 (UTC)

Really? I'm honestly surprised by this: in my experience, most people who have English as a second language seem to type in American English, or something closer to that than to British English (or maybe it's just that I'm less likely to recognise users of "the Queen's English" as non-native speakers). Unfortunately some confusion is inevitable, but since English Misplaced Pages is based in America and read all over the world, I don't think consensus for one variety of English throughout the encyclopaedia is likely. Contains Mild Peril (talk) 00:21, 15 July 2011 (UTC)

Actually taking Hong Kong as example, even though we're taught British English in school, our English teachers specifically state that both British and American Englishes are acceptable, including mixed usage within one sentence, albeit unencouraged. -- Sameboat - 同舟 (talk) 01:20, 15 July 2011 (UTC)

I think the original poster is right—american is ruining the language. For what it′s worth, the SOED doesn’t seem to have much of a problem with most of the words cited. But perhaps we’ve just managed to corrupt OUP. JeffConrad (talk) 01:00, 15 July 2011 (UTC)

Not a bad piece, for "an ex-American resident", whatever that was intended to mean. Dicklyon (talk) 01:09, 15 July 2011 (UTC)

People think the Americans are ruining the language? Most English speakers these days live in India. Have you seen what THEY are doing to it? Rumiton (talk) 01:13, 15 July 2011 (UTC)

There aren't very many first-language English speakers in India. Most of them learned it in school. That doesn't count as much, as a general rule, though there are exceptions. --Trovatore (talk) 02:47, 15 July 2011 (UTC)

Hilarious. "The Americans imported English wholesale,"? Really? That's an... interesting take on history. lol
The attempted point about baseball phraseology making it's way to England is...overwrought, as well. Brits play Cricket after all, so things like "bases" and "strikes" are hardly foreign concepts. Oh well.
— V = IR (Talk • Contribs) 01:25, 15 July 2011 (UTC)

You're on a bit of a sticky wicket there, Ω, perhaps you're thinking of rounders? . . dave souza, talk 13:02, 15 July 2011 (UTC)

hehe, I was wondering if someone would bring that up as I was typing that sentence.

Yea, to be completely accurate Baseball's direct ancestor is probably rounders, but... the lore generally says Cricket. <shrug>
— V = IR (Talk • Contribs) 02:39, 16 July 2011 (UTC)

There's also the basic lack of research. Anyone who has actually used AOL in the UK in the last, what, fifteen years has been treated to "you have eeee-mail" in the plummy tones of Joanna Lumley. Chris Cunningham (user:thumperward) - talk 06:57, 15 July 2011 (UTC)

Why did the resident change his citizenship? Or did he mean “ex–American resident”? Or “former American resident”? JeffConrad (talk) 03:13, 15 July 2011 (UTC)

Henry Louis Mencken documented the history of this rhetoric, from John Witherspoon, onward, in 1948; one would have expected it to die out by now. The American colonists spoke English when they arrived; they still do - as the Australians do. In many cases the American idiom is older, and the British have changed their language; the fuel the British now call "petrol" was originally called "gasoline" and the OED quotes the Pall Mall Gazette and the Duchess of Sutherland as using it; petrol is a French loan word. Septentrionalis PMAnderson 02:01, 15 July 2011 (UTC)

Whatever. But lots of Americans (the majority, I think) are not of English ancestry; in particular, a sizeable fraction of them is of Irish ancestry, and the Irish pretty much did import English from England. :-) ― A. di M._plé 12:09, 15 July 2011 (UTC)

Quite. Half of Webster's "innovations" were digging up archaic spellings that had gone out of use in the UK. Chris Cunningham (user:thumperward) - talk 06:57, 15 July 2011 (UTC)

While I find the original poster's assertion that American English is less valid than British English is inaccurate and a bit insulting, if Misplaced Pages were to suddenly require only one variety of English throughout (perhaps cosmic rays destroy the part of the human brain capable of dealing with inter-article inconsistency, I'm just sayin') I would vote for British. Darkfrog24 (talk) 02:41, 15 July 2011 (UTC)

I wonder how British media deal with American quote. Will they change the A.E. to B.E. of the original context? -- Sameboat - 同舟 (talk) 04:55, 15 July 2011 (UTC)

As for the specific example by the OP of color, I think even non-native speakers are likely to be familiar with it, being used in all kinds of technical contexts (e.g. HTML and CSS). ― A. di M._plé 12:02, 15 July 2011 (UTC)

Actually, until a few years ago, the most common ancestry in the U.S. was German, and it was since before the Revolutionary War. I think 23% of us had some German ancestry as of 1990. Germany has probably since been surpassed by Mexico. Darkfrog24 (talk) 14:00, 15 July 2011 (UTC)

Re: "Germany has probably since been surpassed by Mexico." It would probably be more accurate to have said instead "... surpassed by Hispanics" instead of "... by Mexico." Many of those who cross the U.S. – Mexico border (both legally and illegally) are from countries in Central and South America who have only traveled through Mexico. (And by "only traveled through," I don't intend to imply that the trip was easy, just that these immigrants aren't originally from Mexico.)

A. di M.: re "the Irish pretty much did import English from England." I should think the Irish (except for descendants of colonists who immigrated to Northern Ireland from the British Isles) have a rather different perspective on how English became the dominant language in their country, not to mention the Scots and Welsh. "Import" probably isn't their first choice for the appropriate descriptive term. ;-) "Compulsory adoption" might be a more accurate term, although like "import," it too has controversial political connotations. (I don't know about the Cornish, and I apologize if I've left out any other national identity within the UK for whom English supplanted a previous language.) --Jackftwist (talk) 18:52, 17 July 2011 (UTC)

I believe the current WP policy on the use of British and American English is imminently sensible because it's by far the most practicable course of action.

There would be insurmountable practical difficulties with trying to enforce either version on those who are either native speakers of or have learned the other. Spelling differences (colour vs. color, etc.) would be the least significant problem! It's often said that English is one of the most difficult languages in the world to learn, partly because there are so many exceptions and other irregularities. (I don't know what the technical linguistic terms are to describe these general types of grammatical differences.)

First, there's the problem of the distinction within the UK itself between "British English" and Oxford English. Which should we use? (JeffConrad's comment above may partly address this point, but most of us Yanks aren't familiar with differences between various British dictionaries, and I don't recognize what "OUP" refers to anyway.)
- Oxford University Press. Septentrionalis PMAnderson 23:10, 17 July 2011 (UTC)
Also, wouldn't it be extremely difficult and time-consuming for users of either version to re-learn significantly different punctuation rules, which are already difficult enough? And the rules for collective nouns are bewildering enough in both variants, e.g., "the Army are ..." or "Manchester United are ..." (British) vs. "the Army is ..." and "Manchester United is ..." (U.S.).

Perhaps it would be more productive for WP's purposes if users instead devoted all that time and effort to contributing WP content, a back-log elimination drive, or other WP project.

Idiomatic expressions would be another difficult area. Would U.S. users have to learn to write the "bonnet" and "boot" vs. "hood" and "trunk" of a car? Or "garden" instead of "yard"? "Forms" vs. "grades" when referring to one's year in school?

I initially thought the original poster was being facetious. I find assertion that American English is less valid than British English is not just inaccurate (see Darkfrog, above), it's intellectually meaningless and absurd. (And I think it's far more than just a bit insulting, contrary to WP policies.)

E.g., is British English less valid than Oxford English? For that matter, is either version of English superior to French, German, etc.? (Our English Mother Tongue itself contains innumerable influences of older French, German, and other dialects, not to mention Latin and ancient Greek.)

Is blue a superior color to green because because green is blue adulterated by yellow? Is tea with milk and sugar inferior to tea with lemon? (Which reminds me, I need another cuppa.)

These are all purely matters of taste, and as the saying goes, there's no arguing about taste. (Just because it's a cliche doesn't mean it isn't correct.)

Finally, the assertion is also blatantly inconsistent with the WP principles cited at the top of this Talk page: be polite, avoid personal attacks (which I take to include attacks on the native languages of other users), and be welcoming. --Jackftwist (talk) 18:52, 17 July 2011 (UTC)

I also thought the original post was not to be taken seriously. For an interesting essay on this topic, see "America is Ruining the English Language," by John Algeo in Laurie Bauer & Peter Trudgill (eds.), Language Myths, 1998. Penguin Books: London. pp. 176–182. This piece provides some reliable observations on this topic. I'm not implying that all of the observations here are useless—only that, like many discussions here, it's sometimes difficult to separate what is unsupported speculation and opinion from what is more generally accepted by those who have extensively studied this area. --Airborne84 (talk) 19:40, 17 July 2011 (UTC)

Airborne 84: Excellent point. My screed was prompted only because some of the subsequent posts seemed to support the original, to a greater or lesser degree, or at least take it seriously. --Jackftwist (talk) 21:37, 17 July 2011 (UTC)

I do indeed mean that Mexico alone, without any assistance from other Spanish-speaking countries, has sent more people to the U.S. than Germany/what is now Germany has.

Ireland is a rather unique case with regard to English. Most conquered countries retain their own languages, and there are a few reasons why Irish did not. The big ones are that Irish Gaelic did not have much of a written culture and that the state had a monopoly on the jobs that poor people wanted their kids to grow up and get, like police officers, mail carriers and other steady-pay public servants. So we have schoolteachers making marks on sticks for the number of times that each student slipped up and spoke Gaelic in school, giving the sticks to the parents, and the parents administering the corporal punishment. The loss of so much spoken Gaelic may be a tragedy, but it is one that the Irish themselves at least had a hand in. Of course, quite a bit has been done since to recover Gaelic. Darkfrog24 (talk) 12:06, 18 July 2011 (UTC)

Perhaps Misplaced Pages should be written in Welsh or Cornish... after all, English descends from "foreign" imports like Anglo-Saxon, Danish and Norman French... each of which was "imposed" on the native peoples after invasion. Or not. Blueboar (talk) 13:13, 18 July 2011 (UTC)

Very droll, Blueboar, and an excellent point: i.e., that English itself is a major exception to Darkfrog24's assertion that "Most conquered countries retain their own languages...." That generalization may in fact be true, but there seem to be numerous notable exceptions, in addition to English in England. (Back to that later.)

Darkfrog24, your example of corporal punishment with the notched sticks seems to be consistent with my term "compulsory adoption," as does being compelled to learn English to get a good job. (And weren't the native Irish discriminated against in those jobs in Ulster, anyway?) As for your contention that "Irish Gaelic did not have much of a written culture," the WP article on Irish Language contradicts that claim:

By the 10th century Old Irish evolved into Middle Irish, which was spoken throughout Ireland and in Scotland and the Isle of Man. It is the language of a large corpus of literature, including the famous Ulster Cycle.

Back to the fate of native languages in "conquered countries": How many "conquered countries" in the Western Hemisphere ("The New World") retained their own languages as the dominant one? (Unless we quibble about whether the various civilizations that existed before they were colonized are equivalent to "countries" in this context.)

(1) According to the WP article on languages of Canada, it has an official bilingual policy at the national level (but not necessarily at the provincial level), and English and French are the first languages for about 80% of the population. So French did survive Britain's conquest of Canada, but only as the first language of about a quarter of the population, concentrated primarily in Quebec. And the "Aboriginal language groups" survive only among a small minority of the population.

(2) According to Languages_of_Bolivia, that country has nearly 3 dozen official languages, but (Castillian) Spanish is spoken by about 75% of the population.

(3) In the U.S. English is the de facto national language, but there is no official language at the federal level. (Four states officially recognize a second language in various legal statuses, although none of them are the language of any of the indigenous Native Americans (American Indians). And two of those languages—Cajun (or Cadien) French and Spanish—themselves aren't strictly the original languages in those states, either, because they displaced the original indigenous Native American Indian languages.

[Usage Note re Native Americans: The issue of the preferred terminology is still controversial in some circles, and there is no officially recognized term, although "Native Americans" is still in wide use. But when the Smithsonian Museum opened its National Museum of the American Indian in 2004, it chose the museum's name only after close consultation with and concurrence by a large number of tribes from throughout North and South America, the Caribbean, and Hawaii, including almost all the tribes in the U.S. (See http://www.nmai.si.edu/subpage.cfm?subpage=about )

Yes, but I was trying to point out that much of the compulsion was performed by the Irish themselves on their own children rather than English directly forcing the Irish to stop speaking Gaelic.

I wouldn't be surprised if there are Welsh English or Cornish English articles in here. I've seen one in South African English. Darkfrog24 (talk) 12:37, 19 July 2011 (UTC)

Translation

There was very little guidance for translators in the MoS, so I've added some recommendations in the article about Misplaced Pages:Translation. Please add links to it in section 1.4 (Clarity) and 1.5 (Global view).--Sylwia Ufnalska (talk) 07:02, 15 July 2011 (UTC)

And/or, etc.

I heartily applaud your objective of encouraging clarity by discouraging use of the slash ( / ) to indicate a relationship or choice between two (or even more) words. Although the slash long ago became accepted by U.S. dictionaries as a legitimate punctuation mark, particularly in the increasingly ubiquitous and/or, this construction is all too often a mark of lazy and/or sloppy writing, in which the writer isn't willing/is too lazy to make up his/her mind ;-) —or, worse still, simply doesn't know exactly what he means. (BTW, among the few in the U.S. who even know the slash has a formal name, it's probably more often called a virgule instead of a solidus.)

One possible exception where there seems to be little ambiguity: in legal documents in the U.S., and/or seems to be generally accepted as meaning "either one, or the other, or both," with little confusion.

And while I agree in general that "sometimes or is ambiguous in another way," I don't think your example, "wild dogs, or dingoes, inhab it this stretch of land," is a particularly good one. At least in U.S. usage, the commas around "or dingoes" clearly set it off as an appositive a parenthetical alternative for wild dogs in this case, with no ambiguity or confusion—at least among those who are reasonably literate in the proper use of commas. Unfortunately, although I've seen much clearer examples of your point, I can't think of or find one right now. I'll try to find one. --Jackftwist (talk) 23:34, 15 July 2011 (UTC)

Good comments, Jack. Now, "wild dogs" and "dingoes" are sometimes taken as equivalent, sometimes not. I take your point: with commas, the sentence might most naturally be taken to mean that dingoes are wild dogs. But this cannot be guaranteed, and there are respectable cases in which the commas would serve merely to distance the genuine alternative scenario from the main assertion. ~~Wild dogs~~Dingoes might have been mentioned as a distinct class, and here be mentioned again as possible inhabitants of the stretch of land; the writer thinks it less likely, and marks it as a secondary hypothesis between commas. You see? Sometimes context will diminish the problem, other times context will worsen it. The reader is the expert on when to get confused! Writers can be relied on not to predict such misreadings; so alternatives more immune to misreading are proposed. Noetica 00:14, 16 July 2011 (UTC)

Wouldn’t “wild dogs (dingoes), inhabit this stretch of land” resolve the ambiguity?

As nearly as I can tell, “and/or” is now almost universally deprecated, even by lawyers who sometimes use it. It certainly finds no support in Garner’s Modern Legal Usage, which recommends “this, the other, or both”—as do many others. JeffConrad (talk) 01:49, 16 July 2011 (UTC)

Jeff, of course "wild dogs (dingoes) inhabit this stretch of land" (omitting your comma!) would resolve the ambiguity in one direction. That's exactly what the current guideline proposes.

(I have amended my text above; I don't think my inadvertence affects this present point directly.)

Noetica 02:01, 16 July 2011 (UTC)

Don’t OUP use the serial comma even when there is no series ;-)? I was just sayin’ . . . my response was more at the deprecation, which goes back at least to MEUF. Fowler seemed to reluctantly tolerate it in legal documents; were he alive today, I’m sure he would not.

Another alternative when there are more than two items: “x, y, z, or combination thereof.” JeffConrad (talk) 03:15, 16 July 2011 (UTC)

Again Jeff, a glance at the current guideline shows that this sort of thing is covered: "Instead of x, y, and/or z, use an appropriate alternative, such as one or more of x, y, and z; some or all of x, y, and z." Personally I find those preferable to "combination thereof", which gets a nod from the wording "such as", anyway. If you think differently, take it further. Myself, I'm happy with the guideline as it stands, except that I would make this change: "With two possibilities, at least the intention ismay be clear; ...". That's more accurate. In fact "and/or" normally does cover the intention (on the default assumption of an inclusive reading for "or"), but with noisome breadth and redundancy. In practice, "and" or "or" alone will usually express the intention better.

Noetica 03:40, 16 July 2011 (UTC)

"and/or" means "and or or", which is equivalent to "or" in Boolean logic, which is one of the first things one learns when learning computer programming, which seems thousands of times simpler than the rest of the megabyte-plus unreadable Manual of Style. "X, Y, or both" strikes me as harder to understand than "X and/or Y" when X and Y are 20 words each. But apparently style manuals are united that "and/or" is too complicated. So whatever ... Art LaPella (talk) 05:14, 16 July 2011 (UTC)

Art, the meaning depends on the audience. If we are to believe Garner (a lawyer), the courts have interpreted “and/or” to mean “one or the other or both”, which is essentially the same as the MOS. A quick perusal suggests that the phrase isn’t quite as deprecated as I had thought, but it finds no support in S&W, MEUF, GMAU, CMOS, and only the most tepid support in TCS; Fowler and Garner are especially hard in rejecting it; MWEU, a more descriptive guide, is more tolerant. MWEU and A Dictionary of Modern Legal Usage caution that courts have made varying interpretations, and the latter cites two appellate cases in which each of three judges on the panel arrived at different interpretations.

We’re all creatures of habit, and my preference for rewording probably stems from that. JeffConrad (talk) 07:18, 16 July 2011 (UTC)

8-O I'm gonna take a look at that... What else could and/or possibly be taken to mean? ― A. di M._plé 12:13, 16 July 2011 (UTC)

Noetica, I was just mentioning a possible additional alternative from Form and Style for ASTM Standards that I’ve used for years (this time, I actually looked at the MOS before commenting . . .); I think the current wording for more than two is fine, and we probably don′t need any more suggestions. JeffConrad (talk) 07:18, 16 July 2011 (UTC)

In sum, we seem to agree that there is no big problem with the guideline for "and/or". Art, yes: of course the explicit "or", if it is read as a default inclusive "or", covers the case of "and". The implicit "or", suggested by the "/", is more interesting. People say "and/or" rather than simply "or" not because of the strict meaning, but rather because of the implicature involved. In other words, the implicit "or" is metalinguistic. The speaker is unsure whether saying "and" or saying "or" would be optimal in the circumstances, and therefore hedges. One plausible paraphrase for some particular utterance of "A and/or B", in which the implicature is forced down into the strict meaning (and keeping the explicit "or" inclusive):

"I am not certain whether it would be better for me to say 'A and B' or 'A or B'. I'm sure that 'A or B' is true, because I'm sure that even if A is false, B is still true, and vice versa; but I'm not sure about 'A and B'. So I should be asserting 'A or B' or I should be asserting 'A and B'; and I'm not going to work hard to determine which."

I leave as an exercise the question whether that metalinguistic "or" is best understood as exclusive or inclusive.

As a harder question, what is the paraphrase of a similar utterance of "A and/or B", in which the explicit "or" is taken as exclusive?

Noetica 10:02, 16 July 2011 (UTC)

Obligatory Language Log link: http://languagelog.ldc.upenn.edu/nll/?p=52 (as well as the one it links to, and the one that one in turn links to). ― A. di M._plé 12:41, 16 July 2011 (UTC)

I started to compose an answer, but A. di M.'s link covers it. Art LaPella (talk) 16:36, 16 July 2011 (UTC)

I'm not very fond of wild dogs (dingoes) inhabit this stretch of land–I'd prefer wild dogs, also known as dingoes, inhabit. (In some contexts, the former might be taken to mean that wild dogs are a subset of dingoes: cf. a beam of muons (unstable elementary particles) is produced which doesn't mean that all unstable elementary particles are muons.) ― A. di M._plé 12:13, 16 July 2011 (UTC)

Jack, the answer is simple. If the wild dogs, dingoes, example isn't good enough, suggest a better one. That's the advantage of an electronic MoS. Even when it's already all right, it can be improved easily. Darkfrog24 (talk) 13:30, 16 July 2011 (UTC)

Well, Darkfrog, as I confessed above, my memory fails me. I can't think of any of the good examples I've seen, and I haven't been able to construct one myself. (I'm often not very good at the latter. Mea maxima culpa.) But as the extensive discussion above illustrates quite clearly IMHO, the wild dogs/dingoes example is open to a number of differing interpretations. More later. --Jackftwist (talk) 16:13, 16 July 2011 (UTC)

Further thoughts and/or musings

{Sound of Jack sighing.} Yet another example of the "Law of Unintended Consequences": what I originally intended as merely a compliment and a request for clarification of an example spawned a discussion that runs for 4 pages in a MS Word document (Arial 10-pt. font, narrow margins, 8.5"×11" page), all within 15 hours of the original post! (You'd think this was a discussion board on the issue of whether the U.S. deficit ceiling should be raised.)

But on the plus side, the "Wisdom of the crowd" has yielded some noteworthy insights on this admittedly minor, pedantic topic, but the various comments have pointed out potential ambiguities in almost all of the suggested constructions. On the other hand, Noetica says, ' "wild dogs" and "dingoes" are sometimes taken as equivalent, sometimes not.' (His user page seems to imply he's Australian, so I guess he should know, because according to MWC9, "dingo" is an Aussie word.) That adds still another level of ambiguity to an example that's already confusing!

IMO, it would be clearer to illustrate how or can sometimes be ambiguous if the example were one where one alternative is unequivocally correct. Assuming for the purpose of illustration that dingoes and wild dogs are identical (that is, neither one is a subset of the other), something along the lines of A. di M.'s suggestion seems clearest: "Wild dogs, also known as dingoes, inhabit...." Unfortunately, this is somewhat wordier, but clarity and brevity are sometimes incompatible.

I still haven't been able to find the example I mentioned in my original post. I've reviewed several of the usual suspects (S&W, MEUF, MAU, etc.), but to no avail. It may well have been in one of the (many) WP tutorials or essays on effective writing where I saw the example(s) I'm thinking of.

Jeff, I readily yield to your superior command of the use of and/or in legal contexts! Thanks for correcting me on that. (Note how carefully I hedged that statement, contrary to WP writing guidelines: "One possible exception where there seems to be little ambiguity....") --Jackftwist (talk) 23:13, 16 July 2011 (UTC)

Jack, I am indeed Australian (how shrewd of you to work that out from the hint at my talkpage!); and it is indeed true that dingo and wild dog have been used to refer to the same animals. Only rarely these days, I think: but still the distinction is blurry, and it is still unclear what the relations are between the two terms. As placental mammals, dingoes are not anciently native to Australia; they of the same species as domestic dogs (Canis lupus), with which they have interbred for two centuries at least. And domestic dogs can stray, and become "wild dogs". See also how wild dog is used at the article Dingo. I don't think that such linguistic background knowledge is needed for the example to be useful. Do you? You might even be at an advantage if you had never encountered dingo before; and Australians too can be unsure what the writer intends by wild dog. It would depend on the context and the register, and the period and ultimately the idiolect of the writer.

Since we're having such fun quibbling, I'll remark on this (with italics removed):

Assuming for the purpose of illustration that dingoes and wild dogs are identical (that is, neither one is a subset of the other), ...

I wonder about your use of that is. Let's work symbolically, for generality; and let's be clearer that we are discussing sets, not individuals. Instead of "the set of dingoes" and "the set of wild dogs", let's have "D" and "W". So what you write becomes, with further trimming and fixing:

Assuming that D and W are identical (that is, D is not a subset of W and W is not a subset of D), ...

A problem. "D and W are identical" is inconsistent with "D is not a subset of W and W is not a subset of D". Every set is a subset of itself: A (which is identical to A) is a subset of A. So let's instead speak of proper subsets (no set is a proper subset of itself):

Assuming that D and W are identical (that is, D is not a proper subset of W and W is not a proper subset of D), ...

Still a problem. If D and W are disjoint sets (they have no common member) or overlapping sets, then "D is not a proper subset of W and W is not a proper subset of D" is true, but "D and W are identical" is false. So what does that is mean? I had thought most people use that is to mean "which is to say the same as" (choose what paraphrase you will), or perhaps "and furthermore". But you seem to have it meaning "and also, as a trivial consequence"; it is trivial and unhelpful because disjoint sets and overlapping sets also satisfy the longer criterion. Two examples that we might think odd:

Assuming that bees and camels are identical (that is, neither one is a subset of the other), ...

Assuming that felines and pets are identical (that is, neither one is a subset of the other), ...

Clearly we need a section on that is in WP:MOS.

Noetica 02:29, 17 July 2011 (UTC)

'et al.'

In the MOS:FOREIGN, can we please document 'et al.' in the "Common usage in English" examples? At present the {{Citation}} template's |display-authors= option causes 'et al.' to be displayed without italics. I would like to be able to use that option, but I have seen the lack of italics raised as an issue in the FAC forum. Thank you. Regards, RJH (talk) 16:25, 16 July 2011 (UTC)

Is somebody disputing that et al. ought to be italicized, or complaining that it has not been?

In the latter case, one solution is simple: don't use the {{citation}} template; it's a crutch to supply italics and punctuation for those who don't know what's needed or how to make italics. I used to use them until I realized that doing my own formating was easier and faster as well as more flexible. Septentrionalis PMAnderson 18:33, 16 July 2011 (UTC)

The opinions I found are mixed on italicizing "et al." And of course your own formatting isn't easier or faster if everyone has to look up things like "et al." on their own. Art LaPella (talk) 18:48, 16 July 2011 (UTC)

Do not use italics for:

foreign phrases and abbreviations common in English (i.e., phrases found as main entries in Merriam-Webster's Collegiate Dictionary, 2005). — Publication Manual of the American Phycological Assocition, 6th edition

et al. in Merriam-Webster's Collegiate Dictionary

---— Gadget850 (Ed) 19:56, 16 July 2011 (UTC)

And now that I look at MOS:FOREIGN, it states "not to italicize words that appear unitalicized in major English-language dictionaries." ---— Gadget850 (Ed) 01:36, 17 July 2011 (UTC)

(Responding to the point of Septentrionalis) There are reasons other than formatting to use templates such as citation. It's easier to mechanically process template invocations than raw text, for example. This is helpful for some uses. Quale (talk) 02:02, 17 July 2011 (UTC)

I don't follow; programs shouldn't be processing our text; they are too prone to error. It is much easier to handle raw text by hand; you don't have to edit out all the attribute calls. Septentrionalis PMAnderson 22:54, 17 July 2011 (UTC)

No. First off, programs "process our text" all the time. What do you think the wikimedia software itself does with wiki markup to produce HTML? As an example of that sort of processing that isn't built into the wikimedia software, it is possible to automatically compile bibliographies and the like by parsing citation templates. Doing that by hand is not easier. I think you are not a programmer, or you would know that editing out "attribute calls" is trivial, infering semantic information from raw text is not. HTML itself provides both a positive and negative example of this. Quale (talk) 01:12, 19 July 2011 (UTC)

Indeed. It's worth pointing out that unsighted readers are wholly reliant on the processing of our text to read articles at all, and if the only semantic information we can give them on a particular bit of text is whether it's italicised or not they're going to have a very hard time parsing references. "Crutch" indeed, in more than one sense. Chris Cunningham (user:thumperward) - talk 13:09, 19 July 2011 (UTC)

Italicization and punctuation are the only information given to sighted readers for parsing references. Any screen reader which does not convey it is not adequate to read our text, let alone our references. Septentrionalis PMAnderson 17:29, 19 July 2011 (UTC)

Edit protection

It doesn't bother me personally if this page can only be edited by people with special privileges. However, the present banner wording, "This page is currently protected from editing until disputes have been resolved", has been in place for as long as I can remember and is starting to look a little tired. Does anyone even know any more exactly which subset of the regular stream of (healthy and to-be-expected) disagreements it refers to? If the intention is to protect indefinitely (which seems to be the present de facto situation), then perhaps a more appropriate message could be found. 86.160.85.2 (talk) 01:29, 17 July 2011 (UTC)

The discussion, which is still going on, is about whether the MoS should have a passage advising editors to consult sources in special cases. The main issue is whether or not such a passage weakens the MoS, whether that's a good thing or a bad thing, etc. etc. Darkfrog24 (talk) 14:09, 17 July 2011 (UTC)

Since the most recent unprotect, the edit war dispute centered on the insertion of a very restrictive section on hyphen usage . Discussion of the "follow the sources" section mentioned above was ongoing, but not involved in any edit warring or protection events, as far as I can tell. Dicklyon (talk) 14:26, 17 July 2011 (UTC)

Punctuation after date

Neither WP:MOS nor WP:MOSNUM appear to define whether a comma is required after the year in cases like the following:

They agreed a ceasefire on April 1, 1873 in order to celebrate April Fools' Day.

They agreed a ceasefire on April 1, 1873, in order to celebrate April Fools' Day.

Which is correct? All examples given for this date format seem to have something like a full stop or right parenthesis after. --Stfg (talk) 10:04, 17 July 2011 (UTC)

MLA Handbook for Writers of Research Papers, 7th ed., §3.5.6: "If you begin with the month, be sure to add a comma after the day and also after the year, unless another punctuation mark goes there..."

Associated Press Stylebook (2007), p. 159 (months entry): "Feb. 14, 1987, was the target date." Jc3s5h (talk) 11:22, 17 July 2011 (UTC)

The comma after date is placed when the date if part of an introductory clause, i.e. "In July 2011, the weather was nice." or "As on July 2011, I will stop drinking." However the first clause in the example you give is not an introductory clause, it is just a regular clause that happens to have a date in it. You could replace it with, say, "They agreed a ceasefire yesterday in order to celebrate April Fools' Day." In this case "in order to celebrate April Fools' Day" is not an independent clause, so a comma is not needed. — HELLKNOWZ ▎TALK 11:56, 17 July 2011 (UTC)

Of course, H3llknOwz's opinion conflicts with the two cited style manuals. Jc3s5h (talk) 12:18, 17 July 2011 (UTC)

No, it doesn't. It is not opinion, I am referring to English language punctuation of introductory phrases. Also, I didn't say you cannot use a comma, I said it is not needed. Both your examples refer to introductory phrases – "If you begin with the month" and "Feb. 14, 1987, was the target date." are both used at the start of sentence. What you are possibly meaning to quote is MLA §3.2.2 "If such a date comes in the middle of a sentence, include a comma after the year." This is a stylebook suggestion, and whether it is used or not on Misplaced Pages is at editor discretion/consensus. I did not say you cannot use it and I believe most editors do. — HELLKNOWZ ▎TALK 13:12, 17 July 2011 (UTC)

The statement from the MLA handbook was an instruction, not an example. Failure to put a comma or other punctuation after the year is an error in applying MLA style. Of course, as you say, any style book only applies to those who choose to follow it. Jc3s5h (talk) 13:46, 17 July 2011 (UTC)

Thank you both for helping with this. I've looked elsewhere on the net and it does appear more common to use the comma. But it is a style question, so the real issue is whether this should be left to individual editors or whether MOS should have a position on it. --Stfg (talk) 13:21, 17 July 2011 (UTC)

Chicago (14th ed.) says "In the alternative style , however, commas must be used before and after the year."--Boson (talk) 13:41, 17 July 2011 (UTC)

I have had discussion on this topic with other editors. I am not saying that these discussions are definitive, as I am sure there are plenty of style books, but feel free to read what was said. User:Chaosdruid/usefullinks/GOCEconv#Year and comma Chaosdruid (talk) 14:48, 17 July 2011 (UTC)

Hellknows' post is correct, if a little unclear. If there is a comma before the year, there must be a punctuation mark after it (usually a comma, or the period after the sentence); the year is parenthetical. If there is no comma before, there may or may not be a following comma, depending on the rest of the sentence. In July 11, 2011, there must be a comma before; in July 2011 or 11 July 2011 there isn't. Septentrionalis PMAnderson 19:24, 17 July 2011 (UTC)

The rule isn't in the Manual of Style, but it is at WP:COPYEDIT, and I cite it so often it needs a shortcut: "... the month day, year, style of writing dates punctuates after the year ..." Art LaPella (talk) 20:21, 17 July 2011 (UTC)

The discussion on Chaosdruid's talk relates to sentences beginning In 2011, the.... That is a short parenthetical phrase, and it is a question of taste whether it needs to be set off, by a single comma, at all. But when you use one comma in July 11, 2001, it is mandatory to use both. Septentrionalis PMAnderson 20:47, 18 July 2011 (UTC)

As Hellknowz and Anderson said. Think of it as a parenthetical: They agreed a ceasefire on April 1 (1873) in order to celebrate April Fools' Day. You couldn't leave out the closing parenthesis. That's the rational for requiring two commas, and two commas is standard punctuation. That said, it is extremely common to leave out the second comma, because the main reason they are needed is to help separate the numerals in the day from those in the year, and the clause is perfectly legible with a single comma between the day and year. I would therefore say that in a colloquial context a single comma is perfectly acceptable. However, in a formal context, such as an encyclopedia, we should stick to formal punctuation. — kwami (talk) 03:59, 19 July 2011 (UTC)

I don't think this additional comma should be the subject of MoS rules, as long as there's article consistency on the matter. Aside from this, both alternatives at the top of this thread are unsatisfactory. "They agreed to a ceasefire on April 1, 1873 ~~in order~~ to celebrate April Fools' Day." Tony (talk) 04:32, 19 July 2011 (UTC)

That comma rule's history at WT:COPYEDIT has ranged from wanting to delete the rule because it's wrong to wanting to delete it because the rule is so well-known we don't need it. As I stated there, if we didn't have the rule written down somewhere, then enforcing it would get me into a crossfire between those who consider the rule to be obvious vs. ridiculous, and I would probably decline to enforce it. WP:COPYEDIT is no longer considered part of the Manual of Style, but so far that hasn't mattered when discussing a particular comma. Art LaPella (talk) 04:59, 19 July 2011 (UTC)

Without suggesting a view as to whether or not this should be part of MOS rules, I will say that personally -- based on whatever guidebooks I've read over the decades -- I do insert a comma after the year, and do view that as appropriate.--Epeefleche (talk) 20:25, 19 July 2011 (UTC)

Identity

I am currently in a dispute with another editor at Talk:Wandering Son#Pronouns on whether or not to refer to fictional transgendered characters by their assigned sex or internal gender. My question is, should the second bullet point at MOS:IDENTITY that refers to the gender of a character apply to fictional characters or works of fiction?--十八 05:57, 19 July 2011 (UTC)

There was a similar issue at Birdo that was solved by applying the "latest gender identity" criteria. I agree that this should be discussed at WT:MOS and that at the very least, the MOS should be updated to make clear that any adopted criteria should be explained within the article or the talk page, and consistently applied. Diego (talk) 09:36, 19 July 2011 (UTC)

The reason used then to justify applying the same guideline to a fictional character, is that the naming issue is nonetheless affected by the same requirements about pronouns for transgender people, which is keeping a neutral point of view. Diego (talk) 09:51, 19 July 2011 (UTC)

But the reason that "latest gender identity" is held to be neutral is that it is presumably the viewpoint of the subject and those who are polite to the subject, and therefore the consensus view; basically BLP. But a fictional character has no point of view. Therefore I would suggest the following, which may well come out to the same result:

How do independent sources (you know, the ones which establish notability) refer to the character?
How does the author refer to the character (in interviews and so on)?
How does the narrative voice refer to the character?
What do the other characters say? Septentrionalis PMAnderson 19:08, 19 July 2011 (UTC)

Point 1) Independent sources, such as reviews given at Anime News Network (1, 2) and Mania use assigned sex pronouns. Point 2) Japanese doesn't use gender specific pronouns, so this isn't applicable. Point 3) The English publisher's website and the translation provided by Crunchroll use pronouns that refer to their assigned sex. Point 4) This is the same as in point 3 and can be verified the same way.--十八 20:26, 19 July 2011 (UTC)

Those might be applicable to Wandering Son, but they can't be generalized to the MOS. The problem found at Birdo was that the existing sources conflicted about the pronoun used, so your point 1) usually won't be helpful. That's why the self-identification either by the fictional character, or the official gender assigned by its author if that exists, would be an unambiguous way to provide a single unified criteria. Diego (talk) 21:13, 19 July 2011 (UTC)

Sometimes - most times I would think - that works, sometimes it doesn't. When a character is crafted from a single set of hands, yes, the comments of the author(s) hold sway. But characters that have gone through multiple creative hands and had a change of gender added or removed by later authors invalidate that criteria. And then there are the cases where the gender element of the character is changed, simplified, or ignored in translation.

From the stand point of purely plot sections, I can see sticking with the character's self identification in the vast majority of cases. (This is a guideline after all and there are going to be exceptions.) But when dealing with critical commentary, stick with the gender used predominately in the secondary sources either used or usable. And in those chases where the gender issues is removed in translation and that is a notable section of its own, treat the character as what it is, an piece of intellectual property - a non-gendered thing.

- J Greb (talk) 21:42, 19 July 2011 (UTC)

But what should be done when secondary sources do not predominately use one gender but they are split roughly evenly? That case is likely more common that the case you refer of several authors changing the character's gender, and in that case the latest one could be preferred. (offtopic - My watchlist informs me that +33,333 characters were added yesterday to this page). Diego (talk) 22:12, 19 July 2011 (UTC)

"He or she" is an option. So is avoiding the pronoun; if it doesn't clearly indicate the character, it risks confusing the reader. Septentrionalis PMAnderson 00:00, 20 July 2011 (UTC)

That would be a start. It would also be nice if English had progressed to a standard, accepted prounun for the situation. As would looking for a bench mark for "predominately" - simple majority or a target percentage. Personally, if it's roughly a 60/40 split, err to the 60 is a pronoun is unavoidable unless using a direct quote. If it's closer to 50/50 and a pronoun is unavoidable look at the history of the article. If it's currently stable continue with what is in use. If it isn't, attempt to find an article level consensus and make it stable.

Remember, we can bang out a rough what to do, but we cannot cover every situation. A lot is going to rely on editors working together on the odd cases.

- J Greb (talk) 06:49, 20 July 2011 (UTC)

"He or she" is not an option, is a cop-out. It would be admissible if used only once to establish the convention used within the article, but when adopted it tends to be used every time the pronoun appears. It would be the equivalent of enumerating every possible POV in every sentence of a controversial topic in order to keep a NPOV. I think the MOS should enumerate the possible options (sticking to the sources if they agree, sticking to the author/copyright owner stances, using it or singular they), and directing the editors to make a decision according to whichever option provides the less ambiguity. Diego (talk) 07:46, 20 July 2011 (UTC)

Point of order: The English publisher and Crunchyroll are not the original source of the manga or anime, and ANN and Mania are essentially fan websites. Any pronouns used by any of them are not necessarily correct (especially since gendered third-person pronouns are rarely used in Japanese). -Nongendered (talk) 03:21, 20 July 2011 (UTC)

The links from ANN and Mania are accepted reviews under WP:ANIME/RS, and seeing as how pronouns are rare in Japanese, then an official English source is the obvious next step, since we're discussing about them in English using English pronouns.--十八 03:29, 20 July 2011 (UTC)

ANN and Mania are still, however, fansites, and if I'm not mistaken then they are run by cisgender people. It's always POV when a cisgender person uses "he" for a trans girl (or "she" for a trans boy). -Nongendered (talk) 05:40, 20 July 2011 (UTC)

Source bias is always going to exist. If all of the usable sources we've got have the same bias it's a moot point.

- J Greb (talk) 06:49, 20 July 2011 (UTC)

"well-known"

Hi, at Hyphen it says:

"... the hyphen is represented by a hyphen-minus ( - ), which is well-known and easy to enter on keyboards."

I don't think "well-known" should be hyphenated here, and my understanding of the Style Guide is that it is of the same opinion. However, since this exact example is not given, and since it would be so incredibly dumb to get this wrong in the opening paragraph of the article on the punctuation mark itself, I would like a second opinion. 86.179.118.35 (talk) 21:00, 19 July 2011 (UTC)

An anglicism, slightly dated, but sound. It distinguishes well as an adverb, closely linked with known, from well as an adjective. Whether to use it, or to rely on the reader rejecting well "healthy" as ruled out by context, is a matter of taste. Septentrionalis PMAnderson 21:54, 19 July 2011 (UTC)

If that is the consensus, then I believe WP:HYPHEN should be changed, because I interpret it as saying "... is well known" should not be hyphenated. "A hyphen is normally used when the adverb well precedes a participle ... even predicatively, if well is necessary to, or alters, the sense of the adjective rather than simply intensifying it (the gesture was well-meaning, the child was well-behaved, but the floor was well polished)." "is well known" makes "well known" a predicate adjective. "well known" isn't known in a different way; "well" intensifies the word "known", as in the guideline's phrase "simply intensifying it", like "well polished" not "well-meaning" or "well-behaved". Art LaPella (talk) 22:29, 19 July 2011 (UTC)

Art, in specifying a condition under which "well-X" should be hyphenated, this provision does not imply exclusively under those conditions. Perhaps also including examples of "well-known Y" and "a Y that is well known" would help clarify? In this case, I think the hyphen is not needed (though some books do it that way ). Dicklyon (talk) 00:46, 20 July 2011 (UTC)

The passage on well does imply exclusiveness, by itself; the correction is the bullet, two points up, on light-blue handbag. Art did not see that because the section is too long now. The solution, therefore, is not to lengthen but to combine those two sections into one, perhaps adding to the earlier bullet that a very light blue handbag need not be hyphenated, but well-behaved is. But again, consult a good dictionary would cover the whole unread thing. Septentrionalis PMAnderson 01:25, 20 July 2011 (UTC)

Sure, more examples would help clarify this specific example, since it evidently wasn't intended to mean what I thought it meant. Of course you've probably read the rest of this section: the main effect of adding more clarity in the MoS to one specific example, is usually to help increase the total MEGO effect of the manual, and ensure that Misplaced Pages's amateurs won't use the Manual enough to affect most articles. Art LaPella (talk) 01:28, 20 July 2011 (UTC)

There is a difference between the well known X and X is well known. In the first, having well as an adjective is grammatically possible, but semantically unlikely; in the second, well as an adjective is ungrammatical. But we are dealing with a third case; well known and easy could be read as three adjectives; again, the absence of a comma could be enough of a signal of the adverb, and it's a question of taste, not of rules, whether it is.

But, yes, WP:HYPHEN should be simplified dramatically; most style guides say "consult a good dictionary," and so should we; it's better advice than the present verbose invention. Most of MOS could be usefully replaced with "don't be confusing" to the great blessing of Misplaced Pages.Septentrionalis PMAnderson 23:16, 19 July 2011 (UTC)

I agree WP:HYPHEN and everything else should be simplified dramatically. I think there would be more benefits than problems with going back several years; such an old version survives largely unchanged at the subpage-free Simple English Manual of Style. Yeah, I know, off topic ... Art LaPella (talk) 23:39, 19 July 2011 (UTC)

It says, for exmaple:

The hyphen (-) is used to form compound words, such as "well-known". The en dash (–) is used to specify numeric ranges, such as “open 9–5”. The em dash (—) can be used to link clauses of a sentence—like this one—as can the spaced en dash ( – ). Other dashes, such as the double-hyphen (--), should not be used.

Covers four sections in as many sentences. A different example ("Austria-Hungary"?) that's always hyphenated, and we'd be set. Oh, well. Septentrionalis PMAnderson 23:56, 19 July 2011 (UTC)

It is well known about the well-known principles of hyphenating “well known”. Greg L (talk) 00:02, 20 July 2011 (UTC)
- But only if you have a known well....Septentrionalis PMAnderson 00:05, 20 July 2011 (UTC)

Black background light text?

Someone has put some tables at Boris Gelfand with black background and light text. I don't like it but can't find a style guide advising against it. Is there one? Adpete (talk) 02:25, 20 July 2011 (UTC)

Even if there's not, following "normal practice" is usually preferred unless there's a good reason to do otherwise; be bold and see if anyone comes up with a reason to object to fixing it. Dicklyon (talk) 02:28, 20 July 2011 (UTC)

It fails color contrast per Misplaced Pages:Manual of Style (accessibility). There are also issues per WP:MOSFLAG in that the icon should be accompanied with the name of the country in text. ---— Gadget850 (Ed) 03:00, 20 July 2011 (UTC)

Thanks, I just decided to be bold. As for the flags, that's an ongoing battle I've given up fighting. Adpete (talk) 03:09, 20 July 2011 (UTC)

It at least needs country names. I kicked around Europe for a while, but I don't know half of those. ---— Gadget850 (Ed) 03:18, 20 July 2011 (UTC)