Revision as of 09:59, 23 June 2011 editKotniski (talk | contribs)Autopatrolled, Pending changes reviewers, Rollbackers40,317 edits →General comments← Previous edit | Revision as of 20:46, 23 June 2011 edit undoA. di M. (talk | contribs)Extended confirmed users, Pending changes reviewers, Rollbackers7,922 edits →General comments: commentsNext edit → | ||
Line 11: | Line 11: | ||
* (1) Would it not make more sense to use the more common ''parentheses'' rather than ''round brackets'', especially since ''parenthetical'' is already used. | * (1) Would it not make more sense to use the more common ''parentheses'' rather than ''round brackets'', especially since ''parenthetical'' is already used. | ||
**Fine by me (though in Britain, "brackets" is probably more common). | **Fine by me (though in Britain, "brackets" is probably more common). | ||
**:I usually say "round parentheses", "square brackets", and "curly braces" so that I can't be misunderstood on either side of the Atlantic. :-) <span style="white-space: nowrap;">― ]<i lang="ga" xml:lang="ga"><sub>]</sub><sup>]</sup></i></span> 20:46, 23 June 2011 (UTC) | |||
* (2) I think we should allow {{xt|December 1989–March 1990}} as well as {{xt|December 1989 – March 1990}} because there’s little chance for confusion, and every guide I’ve ever read gives it the first way. That doesn’t mean it’s the only way, but to ban a reasonable common practice seems capricious. | * (2) I think we should allow {{xt|December 1989–March 1990}} as well as {{xt|December 1989 – March 1990}} because there’s little chance for confusion, and every guide I’ve ever read gives it the first way. That doesn’t mean it’s the only way, but to ban a reasonable common practice seems capricious. | ||
**OK by me, if that's what comes out of the discussion (this draft isn't intended to pre-empt any decision). | **OK by me, if that's what comes out of the discussion (this draft isn't intended to pre-empt any decision). | ||
*:This could be implemented by changing “is spaced” to “may be spaced”. <span style="white-space: nowrap;">― ]<i lang="ga" xml:lang="ga"><sub>]</sub><sup>]</sup></i></span> 20:46, 23 June 2011 (UTC) | |||
* (4) I think it would help to suggest {{xt|former prime minister}} as an alternative to {{xt|ex–prime minister}}, which would usually not be used as an adjective, and would seem to have less justification for the en dash. | * (4) I think it would help to suggest {{xt|former prime minister}} as an alternative to {{xt|ex–prime minister}}, which would usually not be used as an adjective, and would seem to have less justification for the en dash. | ||
**OK by me. | **OK by me. |
Revision as of 20:46, 23 June 2011
Hyphens in a list
"6. Spaced en dashes are sometimes used as separators, ..." Did you mean to say "but not hyphens"? Art LaPella (talk) 20:56, 22 June 2011 (UTC)
- Yes, I guess that's the intention; maybe it should be said explicitly.--Kotniski (talk) 09:45, 23 June 2011 (UTC)
General comments
- I thought there was reasonable support for eliminating mention of “typewriter approximations”. If the caveat remains, we should use the present tense, and possibly reword to something more contemporary like these are approximations used for ASCII text. If it’s mentioned, there’s a potential confusion between the two-hyphen typewriter convention for em dashes and the TeX coding of two hyphens for en dashes.
- I've no objection to removing that whole sentence (I certainly wouldn't want to make it any longer).--Kotniski (talk) 09:59, 23 June 2011 (UTC)
- Should the {{ndash}} template be mentioned for spaced en dashes? It handles the nonbreaking space with less effort and visual clutter.
- Could be, though I was assuming that methods of entry would be dealt with at WP:How to make dashes, which is linked to.
- (1) Would it not make more sense to use the more common parentheses rather than round brackets, especially since parenthetical is already used.
- Fine by me (though in Britain, "brackets" is probably more common).
- I usually say "round parentheses", "square brackets", and "curly braces" so that I can't be misunderstood on either side of the Atlantic. :-) ― A. di M.plé 20:46, 23 June 2011 (UTC)
- Fine by me (though in Britain, "brackets" is probably more common).
- (2) I think we should allow December 1989–March 1990 as well as December 1989 – March 1990 because there’s little chance for confusion, and every guide I’ve ever read gives it the first way. That doesn’t mean it’s the only way, but to ban a reasonable common practice seems capricious.
- OK by me, if that's what comes out of the discussion (this draft isn't intended to pre-empt any decision).
- This could be implemented by changing “is spaced” to “may be spaced”. ― A. di M.plé 20:46, 23 June 2011 (UTC)
- (4) I think it would help to suggest former prime minister as an alternative to ex–prime minister, which would usually not be used as an adjective, and would seem to have less justification for the en dash.
- OK by me.
- (5) The senses should be in italics rather than quotes for consistency with (3), and so that it’s clear that they are words used as words rather than the sense of so-called.
- Agree; done.
- (6) It’s not clear to me why the en dash is always spaced in something like Harry Potter and the Deathly Hallows – Part 1; this seems like a somewhat arbitrary choice. In a title, would we not normally do a the publisher did (e.g., Henry VI, Part Two)? I think a colon, comma, unspaced en dash, parentheses, or even perhaps an unspaced em dash could work just as well; I think the application to track listings would have almost as many reasonable options. I also think that without a link to an example to the use for track listings, most readers will have no idea what we’re talking about. Though it should be obvious, perhaps it should be mentioned usage within an article should be consistent. I don′t see a problem using different symbols for connecting track numbers to track times and for connecting musicians to instruments, but obviously usage for each should be consistent.
- (6) “ut no hyphens”. Would this not be treated the same way as “typewriter approximations”, however it is decided to handle them. It would seem to me that if we intend to deprecated spaced hyphens we should do so under WP:HYPHEN, and if absolutely necessary, at the beginning of WP:DASH. JeffConrad (talk) 08:03, 23 June 2011 (UTC)
- I think the main reason for this point is to emphasize that we don't use hyphens here (i.e. that if we want a horizontal line, then it ought to be a dash). I don't see a problem with recommending spaced en dashes specifically, since they seem to be the ones that are already most commonly used in these positions, and recommending a single style would encourage consistency and discourage lame arguments.--Kotniski (talk) 09:59, 23 June 2011 (UTC)