Misplaced Pages

Talk:SAG-AFTRA: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 10:55, 22 July 2023 editSMcCandlish (talk | contribs)Autopatrolled, Extended confirmed users, Page movers, File movers, New page reviewers, Pending changes reviewers, Rollbackers, Template editors201,651 editsm →Requested move 20 July 2023: typ← Previous edit Revision as of 12:19, 22 July 2023 edit undoTheMainLogan (talk | contribs)Extended confirmed users2,788 edits →Requested move 20 July 2023: Apparently my vote/opinion neither counts nor matters and a major author of the Manual of Style has accused me of being addicted to crack cocaine Just forget I ever wrote anything and move the damn page already!Tags: Reverted Mobile edit Mobile web edit Advanced mobile editNext edit →
Line 36: Line 36:
:::I don't think it's a stretch at all. It's the same thing as our formatting convention of not capitalizing short prepositions in titles regardless of what sources do. Whether or not to use a hyphen or a dash is a formatting issue and our formatting rules are what should win out. ] (]) 21:28, 20 July 2023 (UTC) :::I don't think it's a stretch at all. It's the same thing as our formatting convention of not capitalizing short prepositions in titles regardless of what sources do. Whether or not to use a hyphen or a dash is a formatting issue and our formatting rules are what should win out. ] (]) 21:28, 20 July 2023 (UTC)
::::And what exactly is the formatting issue? Why should this use an en dash vice a hyphen? I cannot tell based on the MOS section cited because it does not clearly fall under those sections. -] (]) 21:43, 20 July 2023 (UTC) ::::And what exactly is the formatting issue? Why should this use an en dash vice a hyphen? I cannot tell based on the MOS section cited because it does not clearly fall under those sections. -] (]) 21:43, 20 July 2023 (UTC)
:::...And I agree that it's a stretch. I don't think I've ever seen someone use an en dash for SAG-AFTRA, or ] for that matter. —''']''' (''']'''•''']''') 23:44, 21 July 2023 (UTC)
* '''Comment''' Could someone kindly point out which aspect of ] actually applies here? I do not necessarily oppose (though I lean that way as of now), but pointing to ] is not persuasive in and of itself. It does not appear to be in an attempt to convey a range for "to or through" use; it does not appear to convey a connection that would use {{tq|''to, versus,'' or ''between''}}; it is not a prefix to a compound; it is not a list; and under "other uses" it states a hyphen joins components more strongly. My understanding is that this is not a relationship between SAG and AFTRA (for which an en dash would seem fitting), but in this case neither SAG nor AFTRA exist any longer in order to have a relationship. Those organizations no longer exist, and they have now merged into a single entity. -] (]) 20:05, 20 July 2023 (UTC) * '''Comment''' Could someone kindly point out which aspect of ] actually applies here? I do not necessarily oppose (though I lean that way as of now), but pointing to ] is not persuasive in and of itself. It does not appear to be in an attempt to convey a range for "to or through" use; it does not appear to convey a connection that would use {{tq|''to, versus,'' or ''between''}}; it is not a prefix to a compound; it is not a list; and under "other uses" it states a hyphen joins components more strongly. My understanding is that this is not a relationship between SAG and AFTRA (for which an en dash would seem fitting), but in this case neither SAG nor AFTRA exist any longer in order to have a relationship. Those organizations no longer exist, and they have now merged into a single entity. -] (]) 20:05, 20 July 2023 (UTC)
** '''Oppose''' - Officially opposing now since {{u|Walt Yoder}} pointed out the part of ] that actually argues ''against'' this move in the !vote below. -] (]) 04:50, 21 July 2023 (UTC) ** '''Oppose''' - Officially opposing now since {{u|Walt Yoder}} pointed out the part of ] that actually argues ''against'' this move in the !vote below. -] (]) 04:50, 21 July 2023 (UTC)
Line 49: Line 48:
* '''Oppose''' per the same reason as Walt Yoder. ] (]) 00:56, 21 July 2023 (UTC) * '''Oppose''' per the same reason as Walt Yoder. ] (]) 00:56, 21 July 2023 (UTC)
*'''Support'''. This case is {{em|exactly}} like AFL–CIO, and the full name of the merged organization is "Screen Actors Guild – American Federation of Television and Radio Artists" not "Screen Actors Guild-American Federation of Television and Radio Artists". PS: We do not rely on news journalism to set style on Misplaced Pages; nearly all journalists follow a style guide (''AP Stylebook'', ''Guardian and Observer style guide'' , or some other one) that makes no use of dashes at all except as parenthetical punctuation. They are not examples of how to write encyclopedically; our style manual is derived from academic style guides, which do make appropriate and distinctive use of en dashes, in precisely the way called for here. We did not come up with ] out of nowhere. WP is not written in news style as a matter of policy (]). Otherwise we would not have our own style manual at all and would just follow news style for everything. What is happening in the opposes above is the ]. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 06:28, 21 July 2023 (UTC) *'''Support'''. This case is {{em|exactly}} like AFL–CIO, and the full name of the merged organization is "Screen Actors Guild – American Federation of Television and Radio Artists" not "Screen Actors Guild-American Federation of Television and Radio Artists". PS: We do not rely on news journalism to set style on Misplaced Pages; nearly all journalists follow a style guide (''AP Stylebook'', ''Guardian and Observer style guide'' , or some other one) that makes no use of dashes at all except as parenthetical punctuation. They are not examples of how to write encyclopedically; our style manual is derived from academic style guides, which do make appropriate and distinctive use of en dashes, in precisely the way called for here. We did not come up with ] out of nowhere. WP is not written in news style as a matter of policy (]). Otherwise we would not have our own style manual at all and would just follow news style for everything. What is happening in the opposes above is the ]. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 06:28, 21 July 2023 (UTC)
*:Using that logic, shouldn't it be called "SAG – AFTRA"? —''']''' (''']'''•''']''') 22:06, 21 July 2023 (UTC)
*::No, by your logic shouldn't internal spaces also need to be added whenever a colon or slash is used, we don't write "Space Jam : A New Legacy" instead of "]" or, "Harvard / MIT Cooperative Society" instead of "]". Also, this is covered at the bottom of ]: {{tq|Do not use spaces around the en dash in any of the compounds above}}. ] (]) 01:58, 22 July 2023 (UTC) *::No, by your logic shouldn't internal spaces also need to be added whenever a colon or slash is used, we don't write "Space Jam : A New Legacy" instead of "]" or, "Harvard / MIT Cooperative Society" instead of "]". Also, this is covered at the bottom of ]: {{tq|Do not use spaces around the en dash in any of the compounds above}}. ] (]) 01:58, 22 July 2023 (UTC)
*:::SMcCandlish wrote "Screen Actors Guild-American Federation of Television and Radio Artists" as the "SAG-AFTRA" example. I was simply pointing out that—based on that example—"Screen Actors Guild – American Federation of Television and Radio Artists" should become "SAG – AFTRA", not "SAG–AFTRA". —''']''' (''']'''•''']''') 02:35, 22 July 2023 (UTC)
*::::But this would be incorrect. Taking any of the examples from the section you've referenced, the "Uganda–Tanzania War" is able to be re-written as the "Uganda and Tanzania War" but not "Uganda – Tanzania War", and "Minneapolis–Saint Paul" is able to refer to "Minneapolis and Saint Paul" yet not "Minneapolis – Saint Paul". Basically, just because the acronym doesn't involve spaces doesn't mean the full name can't do so as well. ] (]) 02:51, 22 July 2023 (UTC) *::::But this would be incorrect. Taking any of the examples from the section you've referenced, the "Uganda–Tanzania War" is able to be re-written as the "Uganda and Tanzania War" but not "Uganda – Tanzania War", and "Minneapolis–Saint Paul" is able to refer to "Minneapolis and Saint Paul" yet not "Minneapolis – Saint Paul". Basically, just because the acronym doesn't involve spaces doesn't mean the full name can't do so as well. ] (]) 02:51, 22 July 2023 (UTC)
*'''Support'''—by WP's rules, it's a dash. ] ] 06:47, 21 July 2023 (UTC) *'''Support'''—by WP's rules, it's a dash. ] ] 06:47, 21 July 2023 (UTC)
*'''Support''' per nom ] (]) 07:28, 21 July 2023 (UTC) *'''Support''' per nom ] (]) 07:28, 21 July 2023 (UTC)
*'''Comment:''' There is no presence in ] of a rule supporting the use of an en dash in the union's name. There ''is'', however, a set guideline stating that a hyphen should be used for compound names. I think the people who say "per ]" or something similar to it A) never actually read the page, or B) are fully aware that there is no rule requiring an en dash for compound names and ''that'' is why they keep using "per MOS:DASH" as their reasoning ''without'' specifiying where said rule is written. —''']''' (''']'''•''']''') 11:16, 21 July 2023 (UTC)
*'''Comment'''. It's amazing how much interest there is in discussing the length of a line between two letters. ] (]) 11:18, 21 July 2023 (UTC) *'''Comment'''. It's amazing how much interest there is in discussing the length of a line between two letters. ] (]) 11:18, 21 July 2023 (UTC)
*:I noticed that you're an administrator. While you're still here to notice how pointless this discussion is, may you ''please'' close this and the discussion at ]? —''']''' (''']'''•''']''') 11:25, 21 July 2023 (UTC)
*::There is a policy being discussed here so I don't think the discussion should be summarily closed. I just found it interesting that such a minor point was attracting interest. I don't really see a distinction here but some people do, then they do. ] (]) 11:47, 21 July 2023 (UTC) *::There is a policy being discussed here so I don't think the discussion should be summarily closed. I just found it interesting that such a minor point was attracting interest. I don't really see a distinction here but some people do, then they do. ] (]) 11:47, 21 July 2023 (UTC)
*:331dot, you'd be amazed the lengths some people will go to just to avoid compliance with some MoS point that doesn't agree with their personal style peccadilloes. It's usually motivated by the ] (imitate specialist style), but in this case it's the ] (imitate news-journalism style). <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 20:43, 21 July 2023 (UTC) *:331dot, you'd be amazed the lengths some people will go to just to avoid compliance with some MoS point that doesn't agree with their personal style peccadilloes. It's usually motivated by the ] (imitate specialist style), but in this case it's the ] (imitate news-journalism style). <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 20:43, 21 July 2023 (UTC)
Line 69: Line 64:
*'''Support''' per ], specifically ]: {{tq| In compounds when the connection might otherwise be expressed with to, versus, and, or between}}. As this is the acronym-form of a merged organization (per ]'s comment above), the name could reasonably be rewritten as "Screen Actors Guild '''and''' American Federation of Television and Radio Artists". Therefore, the article title and article should use the en-dash format. There is a clear implied relationship in this name, as it refers to the two union groups which the organization is composed of, satisfying that it is {{tq|involving ''separate or independent elements''}}. ] (]) 13:28, 21 July 2023 (UTC) *'''Support''' per ], specifically ]: {{tq| In compounds when the connection might otherwise be expressed with to, versus, and, or between}}. As this is the acronym-form of a merged organization (per ]'s comment above), the name could reasonably be rewritten as "Screen Actors Guild '''and''' American Federation of Television and Radio Artists". Therefore, the article title and article should use the en-dash format. There is a clear implied relationship in this name, as it refers to the two union groups which the organization is composed of, satisfying that it is {{tq|involving ''separate or independent elements''}}. ] (]) 13:28, 21 July 2023 (UTC)
*'''Support''' – like ], ], ], ], ], ], ], ], where an en dash would be used to signal the parallel relationship in the spelled out version, using an en dash in the initialism similarly provides a useful semantic cue to the reader (at least, to those readers whose fonts show the difference). ] (]) 17:14, 21 July 2023 (UTC) *'''Support''' – like ], ], ], ], ], ], ], ], where an en dash would be used to signal the parallel relationship in the spelled out version, using an en dash in the initialism similarly provides a useful semantic cue to the reader (at least, to those readers whose fonts show the difference). ] (]) 17:14, 21 July 2023 (UTC)
*:Maybe aside from ], the examples you're using are irrelevant. —''']''' (''']'''•''']''') 23:41, 21 July 2023 (UTC)
:'''Comment''': I have merged the move request from ] to here. <small>{{Ping|Wow|Jurisdicta|Tim O'Doherty|Dawkin Verbier|ModernDayTrilobite|Rreagan007|2pou|Freedom4U|Old Naval Rooftops|TheMainLogan|Fjardeson|CAMERAwMUSTACHE|PickleG13|SMcCandlish|Tony1|ReneeWrites|Happily888|Dicklyon|AsteriodX}} Pinging all participants of that discussion in the event they want to add anything here. (My apologies if I'm pinging you and you have already participated in this discussion; there's a chance someone may want to alter their comment(s) based on a discussion merge, so I felt the pings to be appropriate either way.)</small> ] (]) 22:11, 21 July 2023 (UTC) :'''Comment''': I have merged the move request from ] to here. <small>{{Ping|Wow|Jurisdicta|Tim O'Doherty|Dawkin Verbier|ModernDayTrilobite|Rreagan007|2pou|Freedom4U|Old Naval Rooftops|TheMainLogan|Fjardeson|CAMERAwMUSTACHE|PickleG13|SMcCandlish|Tony1|ReneeWrites|Happily888|Dicklyon|AsteriodX}} Pinging all participants of that discussion in the event they want to add anything here. (My apologies if I'm pinging you and you have already participated in this discussion; there's a chance someone may want to alter their comment(s) based on a discussion merge, so I felt the pings to be appropriate either way.)</small> ] (]) 22:11, 21 July 2023 (UTC)
*'''Very strongly oppose''' per ], from which I took this quote: {{tq|Generally, use a hyphen in compounded proper names of single entities.}} And ] also comes into play in this situation.<br />Compound names are supposed to use a hyphen instead of an en dash, and common names should be used. On top of that, seemingly all of the article's sources use "SAG-AFTRA" instead of "SAG–AFTRA", and ''the union's official website'' uses the hyphen as well. Pretty much everybody uses a hyphen in the name, which I feel already outlines a consensus. In other words, '''''nobody writes the name with an en dash because that's <u>not</u> the union's name'''''! —''']''' (''']'''•''']''') 00:00, 22 July 2023 (UTC)
*:Please see ], its a moot point whether or not external sources use a different punctuation. Consensus is made in discussions based on ], not based on what other websites use. Clearly Dicklyon's !vote examples above show that even when external sources use hyphens, the consensus in Misplaced Pages has been to use dashes, in a majority of cases. Maybe these previous discussions (], ]) would be relevant and/or helpful here, as similarly merged organizations. ] (]) 01:58, 22 July 2023 (UTC) *:Please see ], its a moot point whether or not external sources use a different punctuation. Consensus is made in discussions based on ], not based on what other websites use. Clearly Dicklyon's !vote examples above show that even when external sources use hyphens, the consensus in Misplaced Pages has been to use dashes, in a majority of cases. Maybe these previous discussions (], ]) would be relevant and/or helpful here, as similarly merged organizations. ] (]) 01:58, 22 July 2023 (UTC)
*::When I said "consensus", I meant the dictionary definition, ''not'' the Misplaced Pages definition. And I'm pretty sure the en dash is a special character. —''']''' (''']'''•''']''') 02:24, 22 July 2023 (UTC)
*:::Then if you meant the dictionary definition, then this point isn't valid, as titles don't need to be the same as the most common usage outside of Misplaced Pages. {{noping|SMcCandlish}}'s post hoc comment ] quite clearly explains the reasoning for the use of dashes in this instance. ] (]) 02:38, 22 July 2023 (UTC) *:::Then if you meant the dictionary definition, then this point isn't valid, as titles don't need to be the same as the most common usage outside of Misplaced Pages. {{noping|SMcCandlish}}'s post hoc comment ] quite clearly explains the reasoning for the use of dashes in this instance. ] (]) 02:38, 22 July 2023 (UTC)
*::::Where exactly ''is'' that comment? —''']''' (''']'''•''']''') 09:35, 22 July 2023 (UTC)
*:::::It's after the discussion linked above ]. I've copied the comment below: *:::::It's after the discussion linked above ]. I've copied the comment below:
*:::::{{tq|{{lang|la|Post hoc}} comment to forestall any re-RM stuff. It's Brown–Forman, Stitzel–Weller, Dallas–Fort Worth metroplex, etc., because these are {{em|mergers}} of comparable entities. It's Epstein–Barr and Black–Scholes because of a different convention, to use en dashes between surnames of co-discovers/proponents, to get around the problem of hyphenated surnames. But it's Hewlett-Packard and Wilkes-Barre with a hyphen because these are not mergers, and are just entities that happened to have two namesakes (which did not have to have been people's surnames, they just happen to be in this case). In a perfect world, the convention applied to surnames of discoverers and proponents would also be applied to corporations and co-founded towns, when they use surnames. But it just isn't the real-world case. However, you can probably bet money that if Chris Winston-Smyth and Jan van Diesel form a partnership and it uses their surnames that you'll get "Winston-Smyth–van Diesel" not "Winston-Smyth-van Diesel" (or they might use a "not conjoined with a horizontal line" form, like "Winston-Smyth van Diesel", "Winston-Smyth/van Diesel", or whatever some combination of their trademark lawyer and their logo designer come up with – maybe even WinstonSmythVanDiesel the way things are going these days). — ] ] ] 😼 13:31, 8 November 2018 (UTC)}} ] (]) 09:55, 22 July 2023 (UTC) *:::::{{tq|{{lang|la|Post hoc}} comment to forestall any re-RM stuff. It's Brown–Forman, Stitzel–Weller, Dallas–Fort Worth metroplex, etc., because these are {{em|mergers}} of comparable entities. It's Epstein–Barr and Black–Scholes because of a different convention, to use en dashes between surnames of co-discovers/proponents, to get around the problem of hyphenated surnames. But it's Hewlett-Packard and Wilkes-Barre with a hyphen because these are not mergers, and are just entities that happened to have two namesakes (which did not have to have been people's surnames, they just happen to be in this case). In a perfect world, the convention applied to surnames of discoverers and proponents would also be applied to corporations and co-founded towns, when they use surnames. But it just isn't the real-world case. However, you can probably bet money that if Chris Winston-Smyth and Jan van Diesel form a partnership and it uses their surnames that you'll get "Winston-Smyth–van Diesel" not "Winston-Smyth-van Diesel" (or they might use a "not conjoined with a horizontal line" form, like "Winston-Smyth van Diesel", "Winston-Smyth/van Diesel", or whatever some combination of their trademark lawyer and their logo designer come up with – maybe even WinstonSmythVanDiesel the way things are going these days). — ] ] ] 😼 13:31, 8 November 2018 (UTC)}} ] (]) 09:55, 22 July 2023 (UTC)

Revision as of 12:19, 22 July 2023

This is the talk page for discussing improvements to the SAG-AFTRA article.
This is not a forum for general discussion of the article's subject.
Article policies
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL
Archives: 1
This article is rated Start-class on Misplaced Pages's content assessment scale.
It is of interest to multiple WikiProjects.
WikiProject iconFilm: Filmmaking / American
WikiProject iconThis article is within the scope of WikiProject Film. If you would like to participate, please visit the project page, where you can join the discussion and see lists of open tasks and regional and topical task forces. To use this banner, please refer to the documentation. To improve this article, please refer to the guidelines.FilmWikipedia:WikiProject FilmTemplate:WikiProject Filmfilm
Taskforce icon
This article is supported by the Filmmaking task force.
Taskforce icon
This article is supported by the American cinema task force.
WikiProject iconTelevision Low‑importance
WikiProject iconThis article is within the scope of WikiProject Television, a collaborative effort to develop and improve Misplaced Pages articles about television programs. If you would like to participate, please visit the project page where you can join the discussion. To improve this article, please refer to the style guidelines for the type of work.TelevisionWikipedia:WikiProject TelevisionTemplate:WikiProject Televisiontelevision
LowThis article has been rated as Low-importance on the project's importance scale.
WikiProject iconOrganized Labour Low‑importance
WikiProject iconThis article is within the scope of WikiProject Organized Labour, a collaborative effort to improve the coverage of articles related to Organized Labour on Misplaced Pages. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Organized LabourWikipedia:WikiProject Organized LabourTemplate:WikiProject Organized Labourorganized labour
LowThis article has been rated as Low-importance on the project's importance scale.
WikiProject iconUnited States: Cinema / Television Low‑importance
WikiProject iconThis article is within the scope of WikiProject United States, a collaborative effort to improve the coverage of topics relating to the United States of America on Misplaced Pages. If you would like to participate, please visit the project page, where you can join the ongoing discussions. United StatesWikipedia:WikiProject United StatesTemplate:WikiProject United StatesUnited States
LowThis article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Film - American cinema task force (assessed as Low-importance).
Taskforce icon
This article is supported by American television task force (assessed as Low-importance).

There is nothing here

This article really needs some work. Misplaced Pages articles are not simply two sentences with one citation. Anyone who can write a couple of paragraphs here and add some sources would be a great help. Please contribute.Wareditor2013 (talk) 11:46, 29 August 2013 (UTC)

Unite for Strength vs Membership First

Here are a couple of possible sources for expanding these sections:

CapnZapp (talk) 11:57, 3 September 2021 (UTC)

Requested move 20 July 2023

It has been proposed in this section that multiple pages be renamed and moved.

A bot will list this discussion on the requested moves current discussions subpage within an hour of this tag being placed. The discussion may be closed 7 days after being opened, if consensus has been reached (see the closing instructions). Please base arguments on article title policy, and keep discussion succinct and civil.

Please use {{subst:requested move}}. Do not use {{requested move/dated}} directly. Links: current log • target log • direct move

– MOS:DASH Wow (talk) 07:15, 20 July 2023 (UTC)

I don't think it's a stretch at all. It's the same thing as our formatting convention of not capitalizing short prepositions in titles regardless of what sources do. Whether or not to use a hyphen or a dash is a formatting issue and our formatting rules are what should win out. Rreagan007 (talk) 21:28, 20 July 2023 (UTC)
And what exactly is the formatting issue? Why should this use an en dash vice a hyphen? I cannot tell based on the MOS section cited because it does not clearly fall under those sections. -2pou (talk) 21:43, 20 July 2023 (UTC)
  • Comment Could someone kindly point out which aspect of MOS:DASH actually applies here? I do not necessarily oppose (though I lean that way as of now), but pointing to MOS:DASH is not persuasive in and of itself. It does not appear to be in an attempt to convey a range for "to or through" use; it does not appear to convey a connection that would use to, versus, or between; it is not a prefix to a compound; it is not a list; and under "other uses" it states a hyphen joins components more strongly. My understanding is that this is not a relationship between SAG and AFTRA (for which an en dash would seem fitting), but in this case neither SAG nor AFTRA exist any longer in order to have a relationship. Those organizations no longer exist, and they have now merged into a single entity. -2pou (talk) 20:05, 20 July 2023 (UTC)
  • Oppose move. Reliable sources tend to use a hyphen, not a dash. O.N.R.  21:29, 20 July 2023 (UTC)
  • Support per MOS:DASH { } 21:36, 20 July 2023 (UTC)
    Which part of MOS:DASH does this fall under? It is not clear to me. -2pou (talk) 21:44, 20 July 2023 (UTC)
    See my !vote below, the use of a dash falls under MOS:ENBETWEEN. Happily888 (talk) 14:08, 21 July 2023 (UTC)
  • Oppose per MOS:DASH, specifically Generally, use a hyphen in compounded proper names of single entities. Walt Yoder (talk) 22:11, 20 July 2023 (UTC)
    • Thank you for pointing this out. It definitely narrows down such a long MOS guideline to the point that is actually relevant. -2pou (talk) 04:50, 21 July 2023 (UTC)
    This exemption shouldn't apply here because the name isn't referring to a single entity, but rather an organization which involves two entities and therefore falls under MOS:ENBETWEEN; this case pertains more to 'Minneapolis–Saint Paul' rather than to the other examples of 'Guinea-Bissau', 'Wilkes-Barre', and 'John Lennard-Jones'.
Looking through the guideline's page history, it is worth a note that the exemption your quoting initially only pertained to place names prior to August 2011 and only linked to the examples of 'Guinea-Bissau', 'Austria-Hungary' (now in MOS:DUALNATIONALITIES) and 'Poland-Lithuania'. Happily888 (talk) 14:08, 21 July 2023 (UTC)
  • Oppose per the same reason as Walt Yoder. CAMERAwMUSTACHE (talk) 00:56, 21 July 2023 (UTC)
  • Support. This case is exactly like AFL–CIO, and the full name of the merged organization is "Screen Actors Guild – American Federation of Television and Radio Artists" not "Screen Actors Guild-American Federation of Television and Radio Artists". PS: We do not rely on news journalism to set style on Misplaced Pages; nearly all journalists follow a style guide (AP Stylebook, Guardian and Observer style guide , or some other one) that makes no use of dashes at all except as parenthetical punctuation. They are not examples of how to write encyclopedically; our style manual is derived from academic style guides, which do make appropriate and distinctive use of en dashes, in precisely the way called for here. We did not come up with MOS:DASH out of nowhere. WP is not written in news style as a matter of policy (WP:NOT#NEWS). Otherwise we would not have our own style manual at all and would just follow news style for everything. What is happening in the opposes above is the WP:Common-style fallacy.  — SMcCandlish ☏ ¢ 😼  06:28, 21 July 2023 (UTC)
    No, by your logic shouldn't internal spaces also need to be added whenever a colon or slash is used, we don't write "Space Jam : A New Legacy" instead of "Space Jam: A New Legacy" or, "Harvard / MIT Cooperative Society" instead of "Harvard/MIT Cooperative Society". Also, this is covered at the bottom of MOS:ENBETWEEN: Do not use spaces around the en dash in any of the compounds above. Happily888 (talk) 01:58, 22 July 2023 (UTC)
    But this would be incorrect. Taking any of the examples from the section you've referenced, the "Uganda–Tanzania War" is able to be re-written as the "Uganda and Tanzania War" but not "Uganda – Tanzania War", and "Minneapolis–Saint Paul" is able to refer to "Minneapolis and Saint Paul" yet not "Minneapolis – Saint Paul". Basically, just because the acronym doesn't involve spaces doesn't mean the full name can't do so as well. Happily888 (talk) 02:51, 22 July 2023 (UTC)
  • Support—by WP's rules, it's a dash. Tony (talk) 06:47, 21 July 2023 (UTC)
  • Support per nom ReneeWrites (talk) 07:28, 21 July 2023 (UTC)
  • Comment. It's amazing how much interest there is in discussing the length of a line between two letters. 331dot (talk) 11:18, 21 July 2023 (UTC)
    There is a policy being discussed here so I don't think the discussion should be summarily closed. I just found it interesting that such a minor point was attracting interest. I don't really see a distinction here but some people do, then they do. 331dot (talk) 11:47, 21 July 2023 (UTC)
    331dot, you'd be amazed the lengths some people will go to just to avoid compliance with some MoS point that doesn't agree with their personal style peccadilloes. It's usually motivated by the WP:SSF (imitate specialist style), but in this case it's the WP:CSF (imitate news-journalism style).  — SMcCandlish ☏ ¢ 😼  20:43, 21 July 2023 (UTC)
Support,
  • "In article titles, do not use a hyphen (-) as a substitute for an en dash, for example in eye–hand span (since eye does not modify hand)."
  • "Screen Actors Guild – American Federation of Television and Radio Artists"
  • SAG does not modify AFTRA
  • SAG and AFTRA work together like eyes and hands
  • title should use dash.
85.147.66.47 (talk) 12:55, 21 July 2023 (UTC)
Comment: I have merged the move request from Talk:2023 SAG-AFTRA strike#Requested move 20 July 2023 to here. @Wow, Jurisdicta, Tim O'Doherty, Dawkin Verbier, ModernDayTrilobite, Rreagan007, 2pou, Freedom4U, Old Naval Rooftops, TheMainLogan, Fjardeson, CAMERAwMUSTACHE, PickleG13, SMcCandlish, Tony1, ReneeWrites, Happily888, Dicklyon, and AsteriodX: Pinging all participants of that discussion in the event they want to add anything here. (My apologies if I'm pinging you and you have already participated in this discussion; there's a chance someone may want to alter their comment(s) based on a discussion merge, so I felt the pings to be appropriate either way.) Steel1943 (talk) 22:11, 21 July 2023 (UTC)
  • Please see WP:TSC, its a moot point whether or not external sources use a different punctuation. Consensus is made in discussions based on Misplaced Pages policy, not based on what other websites use. Clearly Dicklyon's !vote examples above show that even when external sources use hyphens, the consensus in Misplaced Pages has been to use dashes, in a majority of cases. Maybe these previous discussions (1, 2) would be relevant and/or helpful here, as similarly merged organizations. Happily888 (talk) 01:58, 22 July 2023 (UTC)
    Then if you meant the dictionary definition, then this point isn't valid, as titles don't need to be the same as the most common usage outside of Misplaced Pages. SMcCandlish's post hoc comment here quite clearly explains the reasoning for the use of dashes in this instance. Happily888 (talk) 02:38, 22 July 2023 (UTC)
    It's after the discussion linked above Talk:Brown–Forman#Requested move 28 August 2018. I've copied the comment below:
    Post hoc comment to forestall any re-RM stuff. It's Brown–Forman, Stitzel–Weller, Dallas–Fort Worth metroplex, etc., because these are mergers of comparable entities. It's Epstein–Barr and Black–Scholes because of a different convention, to use en dashes between surnames of co-discovers/proponents, to get around the problem of hyphenated surnames. But it's Hewlett-Packard and Wilkes-Barre with a hyphen because these are not mergers, and are just entities that happened to have two namesakes (which did not have to have been people's surnames, they just happen to be in this case). In a perfect world, the convention applied to surnames of discoverers and proponents would also be applied to corporations and co-founded towns, when they use surnames. But it just isn't the real-world case. However, you can probably bet money that if Chris Winston-Smyth and Jan van Diesel form a partnership and it uses their surnames that you'll get "Winston-Smyth–van Diesel" not "Winston-Smyth-van Diesel" (or they might use a "not conjoined with a horizontal line" form, like "Winston-Smyth van Diesel", "Winston-Smyth/van Diesel", or whatever some combination of their trademark lawyer and their logo designer come up with – maybe even WinstonSmythVanDiesel the way things are going these days). — SMcCandlish ☏ ¢ 😼 13:31, 8 November 2018 (UTC) Happily888 (talk) 09:55, 22 July 2023 (UTC)
    theMainLogan: As one of the principal authors of MOS:DASH, I can tell you unequivocally that you are willfully misinterpreting it, and badly. "Generally, use a hyphen in compounded proper names of single entities" means cases like Wilkes-Barre, Pennsylvania, which is not a merger of a Wilkes and a Barre, but simply named after two namesakes. Similarly, people with "double-barrelled" surnames like Baden-Powell take a hyphen. SAG–AFTRA is the product of a merger (and a very recent one at that, in 2012), and there is absolutely no question that MOS:DASH intends for an en dash to be used here. If you think otherwise you are just smokin' crack.  — SMcCandlish ☏ ¢ 😼  10:54, 22 July 2023 (UTC)
Categories: