| Revision as of 14:09, 1 January 2024 editJohn Smith Ri (talk | contribs)283 edits →About the county equivalent in Connecticut and possible influence in naming convention: new sectionTag: New topic← Previous edit | Latest revision as of 17:34, 23 October 2024 edit undoBlueboar (talk | contribs)Extended confirmed users, Pending changes reviewers53,079 edits →Primary topics and WP:USPLACE: ReplyTags: Mobile edit Mobile web edit Reply | ||
| (48 intermediate revisions by 20 users not shown) | |||
| Line 2: | Line 2: | ||
| | algo = old(180d) | | algo = old(180d) | ||
| | archive = Misplaced Pages talk:Naming conventions (geographic names)/Archive %(counter)d | | archive = Misplaced Pages talk:Naming conventions (geographic names)/Archive %(counter)d | ||
| | counter = |
| counter = 8 | ||
| | maxarchivesize = 150K | | maxarchivesize = 150K | ||
| | archiveheader = {{Automatic archive navigator}} | | archiveheader = {{Automatic archive navigator}} | ||
| Line 16: | Line 16: | ||
| • ] • ] • ]; ]; ]; ]; ]; ] | • ] • ] • ]; ]; ]; ]; ]; ] | ||
| :<small>''']:''' ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ]</small> | :<small>''']:''' ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ] • ]</small> | ||
| <inputbox> | <inputbox> | ||
| bgcolor=transparent | bgcolor=transparent | ||
| Line 33: | Line 33: | ||
| Consensus is sought as to the correct way to refer and link to major American cities such as ] and ]. The discussion is being held at ]. | Consensus is sought as to the correct way to refer and link to major American cities such as ] and ]. The discussion is being held at ]. | ||
| == Capitalisation of "oblast" when used as the name of a Ukrainian administrative division == | |||
| == Consensus for Pennsylvania townships? == | |||
| I have made an ngram review of "X O|oblast" for the oblasts listed at ]. While many of these do not give an ngram result, where they do, they do not show that ''oblast'' is consistently capitalised in sources (per ] and ]) that would lead us to a conclusion that we should cap these names on WP. See , , , , (no result for Kyiv Oblast), , and - others retured no result. A cursory look at Google Scholar results would confirm mixed capitalisation - , and . For these names in Cyrillic, oblast (о́бласть) is not capitalised. There is therefore no to argument that capitalisation from the native language gives rise to a need to capitalise the term in English. The same would be true for other administrative divisions (eg raion). The same is likely true where the same terms are used for other nations (eg Russia). ] (]) 02:35, 28 January 2024 (UTC) | |||
| Has any consensus emerged for the naming of ]? I see two nonconclusive discussions from 2011 (] and ]). A breakdown of how it stands now: | |||
| :I agree, but see ], ], and especially ]. — ] (]) 06:28, 2 February 2024 (UTC) | |||
| *1472 with county disambiguator: | |||
| ::RM results that boil down to "capitalize because the sources I prefer and cherrypicked like to do so" are pretty common when people deeply involved in some topic show up in force to dogpile an RM (or one or two bloviate at tremendous length with their personal ] about why something "is" a "proper name" despite numerous RS not treating it as one by capitalizing it). As our editorial pool shrinks, the entire RM process is starting to fail because too few editors pay any attention to it at all, and those who show up to comment too often have a "screw the guidelines and policies, I want capitalization in {{em|my}} topic else" attitude with no regard to sourcing and guidelines. The way to get around this is to do a bunch of source research beforehand showing that the capitalization level is nowhere near what we'd expect for WP to be capitalizing. Not just n-grams but Google News and Google Scholar and IA Scholar results – e.g. showing that lowercase "oblast" clearly dominates in journals, but do more such searches for all these terms so the evidence is unassailable. Then do a mass RM that is "advertised" at various higher profile venues like ] and here and ] and even ] and ] if it seems to warrant that. Make it clear that the earlier RMs were based on false claims about the capitalization level in the source material and that you can prove it. This is basically the same situation as all that sports raft stuff: topic-devoted editors are hell-bent on over-capitalizing, but do not have the sourcing to justify it. Same with the state panhandles (an RM saga that still continues). <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 06:59, 2 February 2024 (UTC) | |||
| **719 necessary for disambiguation | |||
| :::I'm not sure practices in other languages should be used to decide what to do in English; different languages just have different conventions. French, for example, capitalizes noun forms (like ''Amérique'' for America) but definitely not demonyms (like ''américain'' for American). French does ''Amérique centrale'' for Central America but ''Amérique du Sud'' for South America, though that may be similar to the difference between "North America" and "northern America". | |||
| **753 unnecessary for disambiguation, at least currently (surely some share names with former and/or renamed townships, but with rare exceptions, a hatnote would suffice) | |||
| :::I guess in English there's disagreement or uncertainty over whether the type descriptor is part of a proper noun or a separate noun being modified by a proper ]. ] says "station" is lowercase except where "Station" is already part of the name, leaving that question up to sourcing. Conductors say ] and not "South", and "Penn Station" not "Penn" (which means the university). But they might say "Back Bay" or "Yonkers", so we have ] and ]. But many people write e.g. "Back Bay Station" as if "Back Bay" is a short version of the full proper name, just as "New York" is a short version of "New York City", which is never written "New York city". This is somewhat unsatisfying, but so is the difference in pronunciation between "Kansas" and "Arkansas", so ''c'est la vie''. | |||
| *75 without county disambiguator: | |||
| :::Given sometimes the type descriptor is incorporated into the name and sometimes it's not, and given that capitalization of type descriptors in general seems to be common in English though not always universal, I think declaring as a style choice that English Misplaced Pages always capitalizes would be acceptable as an arbitrary choice between two common conventions, and also safer in that we'd never mistakenly lowercase a name where the descriptor ''has'' been incorporated, which seems to happen over time or for words where the short version is already taken. | |||
| **72 in form 'X Township, Pennsylvania' | |||
| :::It looks like ] already favors the capitalized version, and given that ''some'' professional English sources use that convention, it's not wrong for Misplaced Pages to choose it arbitrarily. Especially given that the short versions of these names are already taken by city names, it seems likely that the type descriptors have or will some day be firmly incorporated by English speakers. -- ] (]) 19:11, 13 March 2024 (UTC) | |||
| **3 ] that questionably self-classify as different forms of municipality: | |||
| ::::To be fair, the naming convention page is silent on capitalisation except for the usage. Weirdly the Ukrainian English-language newspapers I can find use the word "region" instead of oblast in their reporting... ] ''<span style="font-size:small; vertical-align:top;">]</span>''·''<span style="font-size:small; vertical-align:bottom;">]</span>'' 21:15, 13 March 2024 (UTC) | |||
| ***] | |||
| ***] | |||
| ***] | |||
| I don't have a particular preference between including the county by default, as with most other states (NJ being the only exception?), vs. excluding the county when possible, as Pennsylvania townships are somewhat unique and are used more in common parlance than those of other states. But I do see both options as vastly preferable to the current status quo (non-uniform, unilateral moves, often back-and-forth, while proposed moves get rejected due to the language on this page), in line with this page's language ("Any change in convention should be determined on a statewide basis."). ] (]) 21:07, 7 September 2023 (UTC) | |||
| == Region-specific guidance for Turkish cities == | |||
| :I agree that (because of "Any change in convention should be determined on a statewide basis." and ]) we need to settle this. I guess I would lean to laving the county off per ], except where it is required for disambiguation from a non-township place of the same name (or another township of the same name in another PA county for that matter). Looking at how this sort of thing is handled elsewhere (e.g. placenames in Ireland, which may represent towns/cities, "townlands", parishes, civil parishes, baronies, or something else), we are not disambiguating them except as necessary. The average reader doesn't know what classification a place is or what county it's in before they get to our article about it, so "pre-disambiguating" them all by such a name is dubiously helpful. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 21:34, 7 September 2023 (UTC) | |||
| Can we add some specific guidance for Turkish cities? For some cities, this is almost getting to ridiculous levels. For example, count how many Smyrna's are in the lead of ] in this version (there's one extra in the footnote as well). Btw, there's also ] and ] articles. Historic names should usually be presented in "Names" or "Etymology" sections, except significant ones such as Constantinople in the lead of Istanbul for example. However, non-English alphabet versions should also be in "Names" or "Etymology" sections. Turkish is spoken by 85-90% of the population. The rest is mostly Kurdish. Except Arabic, other languages would be less than 0.1% ] (]) 16:41, 27 March 2024 (UTC) | |||
| :For new township articles in Kansas, I use "'''NAME#1 Township, NAME#2 County, Kansas'''" for new township articles that I create, but what works best for Kansas may not be what works best for another state, because each state has different types of entities that were defined by each state government, per this U.S. Census Bureau . My preference is townships and counties should have the word "Township" or "County" in their articles names to make it obvious they aren't a community (city / town / unincorporated community / ...), but I really don't know what's best for Pennsylvania thus is why I'm just passing along what I do and my thoughts, but I'm not going to vote nor mandate something for your state. • ] • ] • 22:05, 7 September 2023 (UTC) | |||
| ::{{ping|Sbmeirow}}: That's great you're working on Kansas townships! I made quite a few of the base articles about 15 years ago but ran out of steam before getting through all of them. I think your pattern is the correct one for Kansas. ] <span style="font-size:smaller"><nowiki>]<nowiki>]</nowiki></span> 13:31, 12 September 2023 (UTC) | |||
| == Türkiye == | |||
| {{ping|Orlady|ErikHaugen|Huwmanbeing|LtPowers|Dohn joe|Born2cycle|Bkonrad|Dicklyon|InvadingInvader}} Pinging the active editors from the discussion 12 years ago and a few others that have shown interest in an attempt to generate discussion at least. I also just saw that a ] occurred last month showing pretty broad support for a blanket change to the township-naming policy here. ] (]) 06:00, 12 September 2023 (UTC) | |||
| :As noted above, I would prefer concision over a long-winded form of consistency (i.e., don't add county unless necessary for disambiguation). And it would be better for PA and other jurisdictions to be treated similarly rather than doing something "magically special" for one US state. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 06:37, 12 September 2023 (UTC) | |||
| ::Agreed. Disambiguate only when necessary. Everywhere. Always. Simple. Consistent. —] ] 06:46, 12 September 2023 (UTC) | |||
| :Yes, I agree that for townships the contrived consistency of always including the county name is not needed and these should only be further disambiguated beyond state name where needed. ] ≠ ] 10:14, 12 September 2023 (UTC) | |||
| :Disambiguate only when necessary. Omit the county name if there is only one township of such name in the state. This is probably what will come about anyways because of the current state of affairs open the VPPR discussion, whichwould override the discussion here since it's a much broader consensus (see ]). <b><span style="color:#0080FB">Invading</span><span style="color:#0668E1">Invader</span></b> (], ]) 14:31, 12 September 2023 (UTC) | |||
| :Include the county name only when necessary to avoid ambiguity, but also make generous use of disambiguation pages. A large share of the Pennsylvania township names that are used more than once are used in several counties, so a relatively small set of disambiguation pages (such as the ones for names like Jefferson, Jackson, and Washington Township) covers many of the dab instances and should effectively guide folks to the right place (assuming there's a disambiguation hatnote on each of the individual pages). Regarding disambiguation pages for PA, I think the Pennsylvania situation where the same unusual name is applied to a variety of different kinds of places makes it desirable to have generic disambiguation pages like ]. I am bothered to see that ] has a hatnote pointing only to ] and not to a dab page that also covers the townships whose names incorporate "St. Clair" (Upper St. Clair Township, East St. Clair Township, West St. Clair Township, and possibly others). - ] (]) 00:28, 17 September 2023 (UTC) | |||
| ::Agreed with all that. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 09:07, 17 September 2023 (UTC) | |||
| {{ping|Star Garnet}}: Thanks for raising this for discussion; I definitely agree that having each state follow an agreed-upon pattern for its townships is far better than having them hodge-podge. Since ] vary so much from state to state (both in function and in how sources identify them), a single blanket rule for all probably wouldn't be successful, which is one reason ] advises that they be handled on a state-by-state basis.<p>I think ] is probably the most relevant factor to consider. Like you said, townships in some places may be identified as ''X Township, State'', or sometimes ''X Town, State'', little different in practice from how populated places like towns and cities are known. This seems most common in parts of the northeast. In such cases the townships also tend to be named more like actual towns: mostly unique across the state with only limited repetition. (In New Jersey, for instance, name repetition is only about 11%, or 28 out of 241.) Pennsylvania may fall into this category, but I haven't looked at it in detail; have you seen what sources tend to do?</p><p>On the flip side, there are a number of states where sources almost ''never'' identify townships without reference to their county, unlike the state's cities and towns. In part this seems to be because the townships are less prominent, to the point that many residents may not even know what township they live in, so when they're referred to at all it's as mere subdivisions of their counties. It's also due to the fact that using a township name without the county name simply wouldn't make sense due to the extremely high proportion of repeated names. In ] 65% are duplicated (884 of 1362); in ] it's over 70% (707 of 1008). If most need the county added no matter what, then it makes sense to add it for all as a ], particularly if that's how they're commonly identified anyway. ] <span style="font-size:smaller"><nowiki>]<nowiki>]</nowiki></span> 13:23, 12 September 2023 (UTC)</p> | |||
| Could we get a section addressing users adding Türkiye or replacing Turkey with Türkiye? I usually revert those edits and point to ] or another MOS-related guideline, but it would be helpful to point here. ] (])<span style="font-size:85%;"> If you reply here, please ].</span> 05:54, 2 May 2024 (UTC) | |||
| :After reviewing the older discussions, I'm not sure I have any strong feelings either way. Including the county name for all townships seems to create unnecessarily long titles, but it does have the advantage of consistency given the number that need disambiguating. There are good arguments both ways and I don't know if there's any compelling logical way to decide between the two. ] <sup><small><small>]</small></small></sup> 21:12, 14 September 2023 (UTC) | |||
| :Probably easier to have a generic “use the main articles title”; we may eventually move the article to Türkiye, and even we do we will have the problem in the opposite direction. ] (]) 06:13, 2 May 2024 (UTC) | |||
| ==]", ] or an English exonym, if there is one ?== | |||
| == There is an ongoing discussion on ] re level of disambiguation in article titles == | |||
| A discussion at ], regarding a mountain on the Polish—Czech border, may be of interest. —] <small>] • ]</small> 17:44, 18 July 2024 (UTC) | |||
| == Primary topics and ] == | |||
| We have had a long-running debate on Misplaced Pages for almost 20 years over the level of disambiguation to include in article titles. My understanding of WP community consensus is that we currently do not include unnecessary detail. This is why New York City, Chicago, Los Angeles, and others were shortened over my objections (and the objections of many other American editors who are accustomed to seeing the state name along with the city name in formal written American English). The current issue on Apple Campus is that if we go to "Infinite Loop campus," whether "Apple" is necessary because no other corporation has an "Infinite Loop campus". ] (]) 15:21, 28 September 2023 (UTC) | |||
| :Please don't jump up on extraneous soapboxes. "Come see this other discussion" notices like this are supposed to be neutral, not "join my title-styling holy war" canvassing. Any time you bring up a bogus and nationalistic argument like "and ... many other American editors ... are accustomed to seeing the state name along with the city name in formal written American English" you're just going to get people to ignore you as tendentious. It's obvious to pretty much everyone in the Anglosphere (since they're all exposed to lots of American media) that American media, including "formal" publications, {{em|routinely}} refer to New York , Chicago, and Los Angeles without appending "New York ", "Illinois", or "California", respectively. And plenty of us were around for those old debates and know entirely well that they had nothing to do with alleged "formal written American English" expectations; the argument for putting these articles at ], etc., was based on a ]-policy reasoning that all the American city and town names should have exactly the same format, which ran up against ] policy which says not to have titles be longer than necessary, and ] guidelines which say the same thing more narrowly with regard to adding disambiguators. {{em|And}} no one is fooled by "many other ... editors" claims; if lots and lots of users agreed with you, there would be a hue and cry to change the guidelines and policies, and they probably never would have said what they say in the first place. " long-running debate on Misplaced Pages for almost 20 years over the level of disambiguation to include in article titles" is not actually happening; what there is in reality is set of well-accepted and stable policy and related guidelines, about which a vanishingly small number of editors are unhappy and refuse to drop the stick. The implication that there is a lack of consensus to be leveraged is simply false. If you think otherwise, feel free to open a ] proposal to change the relevant policy and guidelines (I predict a ] of opposition.){{pb}}To get to the on-topic matter: The RM discussion buried in the above "call to arm" has already closed in favor of ] primarily on grounds of ] (there are very few sources that refer to just "Infinite Loop campus" without also specifying "Apple".) It is important that these micro-policies within ] are in a particular order: recognizability generally trumps concision, which in turn is usually considered more important that consistency. We run through the CRITERIA tests in series, top to bottom; we don't pick them at random and apply only, or particularly favor, the ones that only lean toward the name we might invididually like better.<br /><span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 14:36, 25 October 2023 (UTC) | |||
| How should we decide the primary topics of "{{xt|Placename, Country}}", "{{xt|Placename (city)}}", "{{xt|Placename (town)}}", etc., especially for some countries (like the ]) whose cities cannot have articles named {{xt|Placename, Country}}? ] may be useful references. ] (]) 15:20, 13 September 2024 (UTC) | |||
| == Clarity on the spelling policy == | |||
| :{{ping|John Smith Ri}} There is a difference between naming conventions and eligibility as a primary topic, i.e. a page name does not need to be eligible to be the preferred title of an article in order to be in contention for primary topic; it is sufficient for the page name to be eligible either for preferred title or redirect. For example, ] is the primary topic of ] even though the latter would never be allowed as the title of the article. And so ] is a primary redirect to ] even though ] exist in the US. (Note that ], England, is not in contention for primary topic since ] is neither a valid title nor redirect to that topic.) -- ]]]] 16:58, 23 October 2024 (UTC) | |||
| ::However, ], England is the primary article for “Birmingham”. ] (]) 17:34, 23 October 2024 (UTC) | |||
| The current text states: | |||
| : ''In some cases it is not the local name but the spelling of the name in English that has changed over time. For example, ], as the contemporary pinyin spelling, is used for the name of the article rather than Nanking. However, the article on the ] spells the city as was customary in 1842, because modern English scholarship still does.'' | |||
| However, based on the given example: while the article refers to "the Treaty of Nanking", it refers to the city as "Nanjing". If my reading of the policy is correct, then historic events, objects, quotes, etc, which refer to the old spelling should use the old spelling, but if the place itself is mentioned in such an article, then the place should use the modern spelling. Is this correct? | |||
| And just to clarify, what about institutions that have existed through a spelling change? For example, would the article on the Treaty of Nanking write "The Nanking City Administration decided to..." or would it say "The Nanjing City Administration decided to..."? My read is the latter, but again, clarity is desired. -- ] (]) 12:04, 25 October 2023 (UTC) | |||
| :On the first question, that's generally up to editorial judgment on a per-article basis. I think in most cases, we continue using the historical name for the historical place. It can become very confusing to readers to veer back and forth, and can be confusing to apply a modern name when it is significantly different from the historical one. In this case, the names are so similar it probably doesn't make a real difference. On the second question, it should probably be "Nanking City Administration" because that's a proper name, and no such entity as the "Nanjing City Administration" yet existed (if any such entity exists today by that name in English, for that matter). If that's not the actual proper name of the entity, then it shouldn't be capitalized, and should be rendered "Nanking city administration" or "Nanjing city administration", whichever agrees with the rest of the usage in the article. I would lean twoard consistently using ''Nanking'' in this historical article, to avoid confusing readers with the idea that ''Nanjing'' was the conventional spelling so early. By way of proper-name analogy, if something called the Manks Cat Fanciers' Society existed as such from 1870 to 1901, and later became the ] Fanciers' Society, if referring to their publication of 1894 they'd be called the Manks Cat Fanciers' Society. In general, avoid rewriting history just for the sake of imposing a modern name on something. Our readers are perfectly capable of understanding something like "(modern-day Nanjing)" or "(today spelled ''Nanjing'')". <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 14:03, 25 October 2023 (UTC) | |||
| ::I wouldn't agree that the degree of difference makes much difference - there are plenty of place names differing by only one letter from other places. So better to avoid possible confusion in such historical articles by using relevant consistent spelling with, as you suggest, "(today spelled ''Nanjing'')" or similar - and at first mention (in this case sentence 2 in the Lead). ] (]) 22:23, 28 October 2023 (UTC) | |||
| :::Yeah, that makes sense. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 17:53, 1 November 2023 (UTC) | |||
| :That paragraph is subordinate. But both the lead paragraph and that one make it clear that old names are not preferred by default, but only when they are preferred by reliable sources. Both the respective paragraphs clearly qualify it: | |||
| :* {{tq|Older names should be used in appropriate historical contexts ''when a substantial majority of reliable modern sources do the same''}} | |||
| :* {{tq|However, the article on the Treaty of Nankingspells the city as was customary in 1842, ''because modern English scholarship still does.''}} | |||
| :There’s a problem with the wording of the lead paragraph, in that part of the intent has to be read between the lines. It says “For articles discussing the present, use the modern English name . . . rather than an older one. Older names should be used in appropriate historical contexts when a substantial majority of reliable modern sources do the same; this includes the names of articles relating to particular historical periods.” | |||
| :But what about when discussing the past and reliable modern sources use the modern name? Obviously, we should follow sources and use the main article’s title and modern name. But this is not unambiguously stated in a literal reading of the naming convention. | |||
| :I propose a fix: “For {{hl|most}} articles, {{hl|especially those}} discussing the present, . . .” This makes it clearer that the exception applies when following sources, and doesn’t automatically overrule the rules of COMMONNAME and using the main-article title. —''] ].'' 21:22, 16 November 2023 (UTC) | |||
| == Should ] apply to US territories? == | |||
| I would like to initiate a discussion on whether USPLACE should apply to US territories as well as US states. I will not propose anything on places in US states since the discussions of those have been exhausted with no consensus to change. There didn't seem to be much discussion on whether US territories should be included in the guideline as well. I would like to discuss the applicability of the guideline for US territories. The question I would like to answer is "Should the guideline apply to US territories?" Please discuss here. ] (]) 14:06, 1 November 2023 (UTC) | |||
| *Well, yes, since they are places and are US ones. Is there some kind of concrete example you have in mind with a clear rationale for some kind of divergence? <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 17:53, 1 November 2023 (UTC){{pb}}More to the point, to quote someone else below: {{tq|if the drafters of USPLACE did not intend for it to include territories, it would not have mentioned Placename, Territory as a model to follow.}} <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 09:09, 3 November 2023 (UTC) | |||
| *:Sometimes, US territories are treated like it’s their own country. For example, in statistics, the US usually includes the 50 states and DC, but not the territories. They usually treat them as independent countries despite being part of the US. I think it would beneficial if we treat them in the same way we treat other Oceanian and Caribbean countries. ] (]) 00:08, 2 November 2023 (UTC) | |||
| *::National statistics and such don't have anything to do with our article naming patterns. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 08:24, 2 November 2023 (UTC) | |||
| * I would also say yes, here. Territories fall under the federal governance of the United States, and typically are assigned to the jurisdiction of a U.S. court. ] ] 00:52, 2 November 2023 (UTC) | |||
| * '''No'''. The (arguable) basis for using the comma convention for US cities is that including the state name in the name of the city is the COMMONNAME for cities in US states. I know of no reason to believe that is the case for cities within US territories. This is relevant to, for example, the village of ]. | |||
| **On July 1, 2017, {{U|Number 57}} properly moved ] to ] because "unnecessary disambiguation". | |||
| **Then, more than three years later, on October 28, 2020, {{U|Reywas92}} moved it to ], dubiously citing USPLACE. | |||
| : Now, the ngram viewer (which can't search for commas but omitting it find all occurrences) shows us that Barrigada is far more commonly used than "Barrigada, Guam" , so I think {{U|Number 57}} was clearly correct in saying the ", Guam" is unnecessary disambiguation, and I see no basis for applying the USPLACE comma convention by default, even when disambiguation is not necessary, for this or any other US territory cities (] redirects to ]). Of course, if a city's name is actually ambiguous, then the comma convention is appropriate disambiguation, as in ] (see the ] dab page for other uses), but that falls out of general ] and ] policy, not USPLACE. As a reminder, the only way to justify the USPLACE default comma convention for US cities as not contradicting ]/] is, again, by the claim that including the ", state" is simply reflecting COMMONNAME, because "City, State" is so commonly used for (non-AP) cities. The claim that "City, Territory" is as commonly used cannot be made for cities in US territories. --] ] 04:23, 2 November 2023 (UTC) | |||
| ::The basis of USPLACE is widespread adherence to the AP Stylebook (or its reflection of widespread usage), which for non-independent territories prescribes the use of "the commonly accepted territory name after a city name." Regarding your Barrigada example, additional context is necessary. Taking, for example, newspapers.com results and excluding "Barrigada Heights," "Mount Barrigada," and "Mt. Barrigada," the 2229 results outside of Guam break down as 1322 (59%) including the phrase "Barrigada, Guam" or "Barrigada, GU"; 842 (38%) excluding those phrases but including Guam or GU elsewhere on the page, providing context; and 65 (3%) without Guam or GU (and most of those either refer to a horse or are transcription errors). ] (]) 07:32, 2 November 2023 (UTC) | |||
| :::I'm also sketpical that random off-site usage is more often just "Barrigada" than "Barrigada, Guam", since hardly anyone knows where Barrigada is. Tooling around in Google News results, use of "Barrigada" alone seem to be mostly confined to news sources in Guam or nearby. Use of it alone appears in plenty of headlines that aren't from the region, but their actual article texts tend to specify that it's in Guam. At any rate, the argument that Barrigada by itself is not ambiguous and is in popular enough use to stand alone isn't really an argument against USPLACE at all, since it just has "Foo, Bar" {{em|as a default}}; we have lots of places at article titles like ], ], ], etc., when an overwhelming commonness and pattern of undisambiguated usage justifies it. But there is no such overwhelming pattern for Barrigada. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 08:23, 2 November 2023 (UTC) | |||
| *'''No''' per ] on ] in Guam. We should not be adding disambiguation where it's unnecessary. ] ]] 08:21, 2 November 2023 (UTC) | |||
| *'''Yes'''. They're places in the US, so USPLACE is the convention to follow. I see no good reason why it shouldn't be applied consistently throughout. ] <span style="font-size:smaller"><nowiki>]<nowiki>]</nowiki></span> 11:05, 2 November 2023 (UTC) | |||
| *:The good reason USPLACE shouldn't be applied consistently to the territories as it is applied to places in the US is that the territories aren't places '''in''' the US; they are only places that '''belongs''' to the US. This is like your wallet: it '''belongs''' to you, but it is not '''in''' you, nor is it '''part of''' you. Your lungs and throat. on the other hand, are '''in''' you, so they are '''part of''' you. The territories are like your wallet: they '''belong''' to the US; the states and DC are like your lungs and throat, they are '''in''' the US. ] (]) 03:54, 7 November 2023 (UTC) | |||
| *::But the guidelines make no such distinction. It's one you're trying to impose, not a rationale for why the current guideance shouldn't apply. "I want to change {{var|X}} to {{var|Y}}" isn't an argument that {{var|Y}} applies now. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 17:41, 7 November 2023 (UTC) | |||
| *'''Yes''' USPLACE applies to US territories. ]<sup>]</sup> 13:35, 2 November 2023 (UTC) | |||
| *'''Yes'''—per SMcCandlish's well-reason comments and the common sense idea that a place in the US should follow USPLACE as a naming convention. <span style="background:#006B54; padding:2px;">'''] ]'''</span> 19:15, 2 November 2023 (UTC) | |||
| *'''Comment''' - the territories are not in the US. See the Encyclopedia Britannica entry for the which has a map and explains that the US is 50 states and DC. ] (]) 23:36, 2 November 2023 (UTC) | |||
| *:''Our'' article literally says "The United States of America...consist of 50 states, a federal district, five major unincorporated territories, and nine Minor Outlying Islands." ]<sup>]</sup> 00:28, 3 November 2023 (UTC) | |||
| *::Which article is incorrect, and which is one reason we don't use Misplaced Pages as a source of reliable information in discussions like this. The United States consists of the 50 States and DC, not the territories or, more, accurately, not the <u>'''un'''</u>incorporated territories. Unincorporated territories are possessions, so they aren't a part of the US and, thus, places in the unincorporated territories aren't places <u>'''in'''</u> the United States, which is why ] should not apply to the unincorporated territories, but only to the 50 States and DC. ] (]) 03:55, 3 November 2023 (UTC) | |||
| *:They don't need to be "in" the US to still be US places. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 09:06, 3 November 2023 (UTC) | |||
| *:]: Per ]: {{tq|The term "United States," when used in the geographical sense, refers to the contiguous United States (sometimes referred to as the Lower 48), the state of Alaska, the island state of Hawaii, the five insular territories of Puerto Rico, Northern Mariana Islands, U.S. Virgin Islands, Guam, and American Samoa, and minor outlying possessions."}} Since we're here to discuss ], that seems pretty clear. ] <span style="font-size:smaller"><nowiki>]<nowiki>]</nowiki></span> 09:40, 3 November 2023 (UTC) | |||
| *'''No.''' As it currently reads, that ''"According to the comma convention, articles on populated places <u>'''IN'''</u> the United States are typically titled "Placename, State" when located within a state or "Placename, Territory" in US territories"'', ] uses "territories" implying ], yet '''UN'''incorporated territories are, by definition, not '''IN''' the United States, making the statement at ] self-contradictory. For a territory to be '''IN''' the United States it has to be part of it, i.e., it has to be '''IN'''corporated into the United States, which the territories are not.<ref>], 182 U.S. 244, pp. 141-142.</ref> The United States consists only of the 50 States and DC.<ref> USGS. Retrieved 2 November 2023.</ref> The territories (or, more precisely, the "'''UN'''incorporated" territories) are possessions of the United States but aren't part of it.<ref>Balzac v. Porto Rico, 258 U.S. 298 (1922)</ref><ref>Downes v. Bidwell, 182 U. S. 244.</ref><ref>Dorr v. United States, 195 U. S. 138.</ref><ref>Christina Duffy Bernett. ''Foreign in a Domestic Sense''. Duke University Press. 2001. p.1</ref> ] (]) 00:15, 3 November 2023 (UTC) | |||
| *:Your USGS link starts with "Geographically (and as a general reference), the United States of America includes all areas considered to be under the sovereignty of the United States, but does not include leased areas." ] makes clear that "American territories are under American sovereignty." I'm not even going to touch the racist Insular Cases. ]<sup>]</sup> 00:43, 3 November 2023 (UTC) | |||
| *::The link is from the US <u>'''''Geographical'''''</u> Survey so, naturally, it points out that they do <u>'''''geographical'''''</u> work that includes the unincorporated territories, and not just the 50 states and DC. You need to read further down to locate their definition for "United States", namely '''''"The 50 States and the District of Columbia."''''' This definition is in agreement with the definition the SCOTUS has used since 1901 (and for which I already included 4 references above) and with the definition of other reliable sources, such as the US Department of State.<ref>US Department of State. ''Foreign Affairs Manual.'' Vol. 7. Section 1121.1.</ref> ] (]) 03:32, 3 November 2023 (UTC) ] (]) 03:32, 3 November 2023 (UTC) | |||
| *:I believe the question asked is "should it apply", not "does it apply". You are answering the latter question, which is besides the point. (And the answer to that question is in fact obviously yes, because if the drafters of USPLACE did not intend for it to include territories, it would not have mentioned Placename, Territory as a model to follow. You're essentially saying, because they worded it slightly incorrectly, we should throw out whatever they had to say about territories, instead of making small adjustments to technical definitions in order to interpret it in line with their intent.) | |||
| *:But the purpose of this discussion is to argue whether or not the guideline should be modified to say "no, it does not apply to territories". And for that we want to study common practice in those territories, rather than pore over what "in the United States" means. -- ]]]] 04:39, 3 November 2023 (UTC) | |||
| *::USPLACE didn't used to include reference to territories. Mention of them without any consensus I can see shortly after the Dededo RM (which decreed the disambiguation wasn't necessary) by an editor who had fiercely opposed removing the disambiguation from that page. It was quite rightly some time after by ], but was subsequently by the same editor, although with reference to "some" usage, which they to "most". IMO its inclusion has no legitimacy – it was added in a response to an RM not going the way someone wanted – and should be removed until there is shown to be consensus for it. ] ]] 16:15, 3 November 2023 (UTC) | |||
| *:::This is true, but it is also clear that the RM should have been closed as 'no consensus' (further, roughly two-thirds of non-local mentions refer to it as "Dededo, Guam," so even the COMMONNAME argument fails). This discussion is, I believe, effectively to determine whether that inclusion stays in an edited form or goes. ] (]) 17:53, 3 November 2023 (UTC) | |||
| *:::Number 57: The convention currently states, {{tq|"articles on populated places in the United States are typically titled "Placename, State" when located within a state or "Placename, Territory" in US territories."}} That is accurate, ]. (A quick tally suggests around 80% of populated places in US territories are so titled.) ] <span style="font-size:smaller"><nowiki>]<nowiki>]</nowiki></span> 18:21, 3 November 2023 (UTC) | |||
| *:::Number 57's ] objection to changing the guideline text without consensus after the Dededo RM seems to be valid. (And I think there's a more narrow shortcut to something about changing policy/guideline pages without consensus to "win" a content dispute, but I don't remember what it is.) <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 07:59, 4 November 2023 (UTC) | |||
| *::::I was pointing out that the specific language Number 57 mentions is , and either way simply notes the form that's typically used. ] have done so since their creation. (Incidentally, I for input on the very thing we're now discussing: how we define what's included in a country for the purposes of applying our geographic naming conventions.) ] <span style="font-size:smaller"><nowiki>]<nowiki>]</nowiki></span> 10:54, 4 November 2023 (UTC) | |||
| *:::::That's fine, I guess, but I wasn't replying to you (note the indentation level) and what you said isn't really responsive to what I wrote. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 11:59, 4 November 2023 (UTC) | |||
| *'''No''' As demonstrated above, this is neither the original intent nor something that has been added via consensus later. --] (]) 18:03, 3 November 2023 (UTC) | |||
| *'''Yes''', while they may not be "in" the United States, they are certainly "of the United States." USGS, which determines official names in the territories, considers them part of the United States, they participate in the same postal system that has made "city, state/territory" so ubiquitous, their governments are thoroughly intertwined with the larger United States, and the vast majority of non-local media coverage of the territories is in the United States. ] (]) 18:13, 3 November 2023 (UTC) | |||
| *:I am not sure where you got that the USGS "considers them part of the US". Did you not read the USGS link included herein? The USGS considers the territories part of their geographical work, but it's a stretch of the imagination to imply that means the territories are "part of the US" -- especially when the USGS is already saying the US is composed of the 50 states and DC plus nothing else. Likewise, the USPS and non-local media coverage operating in the territories doesn't make them part of the US, simply makes them part of their operational territory. I suggest the read the SCOTUS court cases: they have all established the territories aren't part of the US... that's why they are called "UNincorporated territories". ] (]) 03:40, 7 November 2023 (UTC) | |||
| *::You continue to focus on and emphasize irrelevant points. Whether or not the constitution extends in full to the territories has little bearing here, particularly with congress having granted birthright citizenship to 4/5 and SCOTUS determining that the territories ] their own, separate sovereignty. All that matters here is whether the United States' naming practices have extended to them, which extends largely from whether or not they are functionally part of the United States. For two of the most relevant agencies, and (along with plenty of others), they functionally are. That the vast majority of American media coverage of the territories is non-local for the territories is also irrelevant; that's simply how American media works. Media in the Chicago Metro doesn't need to specify a state when they refer to Naperville, Kenosha, or Waukegan, but 95%+ of other American media will specify a state(/territory) if it's not made clear by context. ] (]) 07:09, 7 November 2023 (UTC) | |||
| *Yes, per SMcCandlish. --] (]) (]) 13:40, 7 November 2023 (UTC) | |||
| *'''Yes''' - AFAIK, "city, province" & "city, territory" is used for Canadian places. Therefore why not the same idea for US "city, state" <u>&</u> "city, territory". I believe roughly the same is done for post-1707 British places. ] (]) 18:36, 7 November 2023 (UTC) | |||
| *:] and ] are very different concepts. ] and ] are not interchangeable. ] (]) 19:36, 15 December 2023 (UTC) | |||
| *::They should be interchangeable, as they're all parts that make up a sovereign state. ] (]) 19:42, 15 December 2023 (UTC) | |||
| *:::The sovereignty of U.S. Territories is open to question -- they are considered to be ] and not an integral part of the nation. The uninhabited places are for the most part treated as if the federal government were the sole proprietor. But the inhabited territories occupy a gray-ish area between fully independent and an administrative subdivision. ] ≠ ] 20:36, 15 December 2023 (UTC) | |||
| *::::On the federal level: ], ], ], ] & ], can't vote in US presidential elections, but they can vote for delegates to national party conventions. They don't have voting members in the US House or US Senate, but do have non-voting members in the US House. So there'en lays the question - Is this enough to call them Americans? ] (]) 20:53, 15 December 2023 (UTC) | |||
| <!--Keep this template at the bottom of the discussion-->{{reflist talk}} | |||
| Since there are no comments recently, do you think we are ready to close the discussion? ] (]) 19:18, 15 December 2023 (UTC) | |||
| == Listing large US cities by state in broadcasting article leads == | |||
| {{Discussion top|1={{Moved discussion to|Misplaced Pages talk:Manual of Style/Lead section#Listing large US cities by state in broadcasting article leads|2=<span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 04:11, 19 November 2023 (UTC)}}}} | |||
| I've had this come up in an FAC (]) and wanted some clarity on the topic. Some broadcasting articles are on stations located in and licensed to very large, undisambiguated-title-by-state-per-AP Stylebook US cities. Which of these should be preferred? | |||
| * Option A: '''KAAA-TV''' is a television station in San Francisco ... | |||
| * Option B: '''KBBB-TV''' is a television station in San Francisco, California, United States, ... | |||
| Pinging for visibility: {{u|Mvcg66b3r}} and {{u|MaranoFan}}. ] (she/her • ] • ]) 03:51, 19 November 2023 (UTC) | |||
| :This is really the wrong page for this discussion, since ] is only about how to title articles. This really should be brought up at ]. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 03:59, 19 November 2023 (UTC) | |||
| :: {{ping|SMcCandlish}} Going to move. ] (she/her • ] • ]) 04:03, 19 November 2023 (UTC) | |||
| {{discussion bottom}} | |||
| == ] or ] == | |||
| I just closed a dispute at ] concerning the name of the nationality of ]. One editor had changed it from ] to ]. Other editors had changed it back. It appears that we do not have a place-specific guideline in the East Asian guidelines that says to use ]. So my question is: Should we have a guideline that says to use ] rather than ]? If so, a ] is in order. If this is the wrong talk page because this guideline only has to do with titles, please advise me where we should discuss. | |||
| ] (]) 01:21, 12 December 2023 (UTC) | |||
| :] seems to take "Taiwanese" as a given under the Ethnicity section, although that is not exactly the same as "nationality" (and I note the field in question is "Citizenship" rather than nationality, which may again be subtly different). That said, this falls under existing broader guidelines (likely why it is taken as a given). Per ] alternative names should be used in prose when specific context suggests it. For Taiwan, there were discussions around the period when the current conventions were put into place that this was mostly limited to specific state institutions (eg. ]) and national politics (eg. ]), but not to the place (]) or the people/demonym (]). The page on citizenship is at ]. There may be specific exceptions based on reasons of personal identity which would be worth taking into consideration on a case-by-case basis as they are for other citizenships, but that does not appear to be the case here. ] (]) 02:16, 12 December 2023 (UTC) | |||
| ::In my experience, ] is not the most fleshed-out page yet, useful as it is. To the best of my understanding, "Taiwanese" is not used to represent an ethnicity, especially when one is confronted with the numerous ethnic identities of the island. This is directly analogous to Han Chinese people in mainland China not being ethnically "Chinese"—Han Chinese people in Taiwan are not ethnically "Taiwanese", either. "Taiwanese" is a nationality—the reason that passage in under that section has to do with treatment of various social divisions in Taiwanese society. | |||
| ::Moreover, "Taiwan" is absolutely the existing consensus per ], as presented on every relevant article, with "Republic of China" being reserved for when contrasting with the PRC per-se, or when speaking about the period before the state's relocation to Taiwan in 1949. To change this existing consensus would be what requires an RfC, in my view. ]] 03:02, 12 December 2023 (UTC) | |||
| :::I certainly agree with your point regarding MOS:CHINA as a whole, it has never felt that firm or that clearly supported by the community. Some parts do reflect wider discussions though, and one is the use of China and Taiwan as common names for both polities, which as you say is the existing consensus. ] (]) 04:11, 12 December 2023 (UTC) | |||
| ::::I have been paying some attention to both it and ] (which seemingly do not need to be different pages), but it's hard to unilaterally improve a policy page without potentially amplifying the chance of stepping on toes a hundred-fold. ]] 04:17, 12 December 2023 (UTC) | |||
| :::::I have read ] again, looking for where it states, as ] says, that there is a consensus that "Taiwan" is the ]. I didn't find a statement to that effect. I agree that it is the common name, and I agree that in Misplaced Pages we should use the common name, but I was asked in good faith by an editor where it says that, and I can't answer the question. I agree that there is an unstated consensus, but an unstated consensus is less than satisfactory because new ] editors may disagree. Can someone please show me where this consensus is documented, or do we have an undocumented consensus? If the latter, why, and how are new editors supposed to learn about it? ] (]) 08:25, 12 December 2023 (UTC) | |||
| ::::::Agreed whole-heartedly. I did not say that ] stated the consensus, and I should've made my gesturing to the idea of a working, unstated, but ultimately pretty solid consensus clear. I simply do not feel comfortable being the one to enshrine it in text or potentially "rock the boat", as it were—not so much because I don't think there is that consensus in the end, but because the due discussion may be long, messy, and ultimately dull (the last point being more selfish than the others) ]] 08:30, 12 December 2023 (UTC) | |||
| ::::::The Common name consensus was established through ]. The practice of continued use of Republic of China in various cases comes from later discussions and failed move requests after that. On the point of new editors and documentation, the default assumption should be that the article title is itself documentation, being for the majority of our articles an expression of ] consensus. Changing the name elsewhere without strong ] reasons is time-wasting and likely disruptive, desire for name changes should occur through an RM at the relevant page. ] (]) 11:52, 12 December 2023 (UTC) | |||
| How about ''deleting'' the 'nationality' parameter from the infobox. If not? then seeing as the main page is named ], perhaps we should use "Taiwan". ] (]) 14:19, 12 December 2023 (UTC) | |||
| :Agree with the approach of using “Taiwan” as default. I think the field can be relevant for bios in the 1930-1950s era where Taiwanese politicians may have switched nationality from the Empire of Japan to the ROC, though I can’t think of an example right now. ] (]) 15:50, 12 December 2023 (UTC) | |||
| == CIA World Factbook for country names == | |||
| At present, we list the ], produced by the US government, as a "disinterested, authoritative reference work" as establishing a widely-accepted name "for modern country names". I would note that: | |||
| *The US government cannot credibly be described as "disinterested" in global affairs | |||
| *Works of the US government reflect the US government POV, which is not NPOV. For example, there are only two countries in the world that would accept as a current map of Morocco without qualification - it just happens that the US is one of them. | |||
| *In terms of modern country names it tends to promote ] over ] - as is common from government sources (from all governments). | |||
| In terms of modern country names, our consensus - often longstanding and repeatedly litigated - routinely differs from CIA names in contentious (or potentially contentious) cases: | |||
| *We use {{tq|]}}, they use {{tq|Cabo Verde}} | |||
| *We use {{tq|]}}, they use {{tq|Czechia}} | |||
| *We use {{tq|]}}, they use {{tq|Timor-Leste}} | |||
| *We use {{tq|]}}, they use {{tq|Falkland Islands (Islas Malvinas)}} | |||
| *We use {{tq|]}}, they use {{tq|Cote d'Ivoire}} | |||
| *We use {{tq|]}}, they use {{tq|Burma}} | |||
| *We use {{tq|]}}, they use {{tq|Turkey (Turkiye)}} | |||
| *We use {{tq|]}}, they use {{tq|Virgin Islands}} (even though they need to disambiguate from the ] just as we do). | |||
| I'm actually struggling to find genuinely controversial cases where we use the same name as they do - other than ]. But in all of those cases the case for using the names we do should be pretty clear from other sources without having to rely on US government POV. | |||
| I contend that the CIA World Factbook is not being taken as authoritative in these disputes, because it is not a good source for common usage. I therefore propose that it be removed from the list . ''''']''''' <small>'']''</small> 22:28, 12 December 2023 (UTC) | |||
| :Support removal, it is not a bad source, but it is also in no way "disinterested". The WIAN list is interesting as a whole, the "nationalistic, religious or political reasons" caution for news surely applies to all of them. ] (]) 02:08, 13 December 2023 (UTC) | |||
| :I don't think it should be removed, but I think it should be presented more accurately instead. Obviously, it is not disinterested, but it is in some sense an authoritative reference work.<span id="Remsense:1702433400052:Wikipedia_talkFTTCLNNaming_conventions_(geographic_names)" class="FTTCmt"> ]] 02:10, 13 December 2023 (UTC)</span> | |||
| ::Government publications are not independent by definition. Is there a simple alternative source? ] (]) 05:15, 13 December 2023 (UTC) | |||
| :::I never said it was independent. Franky—if there's a comprehensive, independently sourced world atlas, thinking of all that entails to assemble and publish, it's not going to be independent of {{em|anybody}}. ]] 11:41, 13 December 2023 (UTC) | |||
| ::::There is a big difference between how sources published by reputable independent publishers are received at RM, and how sources published by national governments are received. In the realm of geographic names - and particularly for country and major city names - the former type of sources tend to be considered significantly more persuasive in terms of judging a widely accepted ''common'' (as opposed to ''official'') name than the latter. | |||
| ::::In practice, though, the most persuasive evidence on usage comes not from atlases but from independent newspapers and other independent media - particularly mainstream English-language media from English-speaking countries. ''''']''''' <small>'']''</small> 17:30, 14 December 2023 (UTC) | |||
| :::::Right—and there's also a big difference between the CIA World Factbook and other things we can associate with the organization. I think it's reasonable that it can be treated the same way we treat any other state-sponsored source of information—appreciating the benefits made possible by the institutional support, but with several grains of salt when it comes to information related to geographical areas or topics we think might be especially biased ]] 17:38, 14 December 2023 (UTC) | |||
| ::::::This isn't about the World Factbook's general reliability. This is about it's specific suitability for a list of sources to be taken as {{tq|disinterested, authoritative reference works}} to be used to decide what names we should give to our articles about modern countries. | |||
| ::::::You seem to accept that it is ''not'' a disinterested reference work, and even that it should be taken {{tq|with several grains of salt}}. You also seem to accept that it is ''not'' considered persuasive when it actually comes to determining the widely-accepted names of modern countries. But you also seem to argue that it ''should'' be included on a list of sources that are considered persuasive for this purpose. | |||
| ::::::Perhaps I have misunderstood something, but this seems inconsistent. Perhaps you could clarify? ''''']''''' <small>'']''</small> 19:16, 14 December 2023 (UTC) | |||
| :::::::I think no single source can be considered persuasive on this matter by itself: I see the purpose of the list as to provide a body of sources that may collectively establish one option over another. Is that fair? ]] 02:01, 18 December 2023 (UTC) | |||
| :I don't see any need to remove. Your examples all look like correct applications of COMMONNAME instead of unthinking use of the ''Factbook'''s form, so I don't think there's an actual problem here. We could make a modest change, though: instead of giving the ''Factbook'' its own line, we could append the same text to the previous bullet point about government agencies. | |||
| :The point that the ''Factbook'' is not disinteresed is well taken, but any source has its bias. That's more a case for tweaking the general language in that section. --] (]) 19:48, 14 December 2023 (UTC) | |||
| ::To be clear, are we saying the common name is what RSSs use or what the man in the street uses? They are not always the same. ] (]) 20:05, 14 December 2023 (UTC) | |||
| :::Fair question, but IMO a general one rather than one central to this discussion. --] (]) 03:15, 18 December 2023 (UTC) | |||
| :'''Remove and do not replace''' with anything else. I think the purpose of this section is to suggest authoritative references when information is sparse. But there is a limited number of countries in the world and every controversial case has already been discussed ad nauseum (with arguments unique to each country regarding what the best title is), so I don't see a need to recommend any particular source for country names. -- ]]]] 22:44, 14 December 2023 (UTC) | |||
| * I don't believe it should be removed. If it has 5, 8, 10 or whatever number of bullets that may be objectionable to some, so what?....No source is infallible nor absolutely neutral - this is why we demand that articles provide several sources, and why we demand that even single "facts" that are questionable to some or objectionable to other also be sourced from several reliable sources. If the book doesn't present a NPOV to some, again, so what?...we are used to that -- it simply gets balanced by equally non-NPOV but opposing POVs. ] (]) 00:35, 15 December 2023 (UTC) | |||
| *:The issue is not that the source is fallible or does not present as NPOV. The issue is that the list supposedly lists "Disinterested" sources, and the source in question is specifically created for the US diplomatic corps rather than as a disinterested perspective. ] (]) 01:36, 18 December 2023 (UTC) | |||
| == About the county equivalent in Connecticut and possible influence in naming convention == | |||
| From 2024, the county equivalent in Connecticut is not "county" itself, but "council of governments". Maybe we should clarify whether "county" or "council of governments" in Connecticut should be used for disambiguation one day (but not now, because I have not found any two cities/towns in Connecticut with the same name). ] (]) 14:09, 1 January 2024 (UTC) | |||
Latest revision as of 17:34, 23 October 2024
- Please post discussions about Railway station names at Misplaced Pages talk:Naming conventions (stations).
 view · edit Frequently asked questions
Why is the article on Georgia named Georgia (country), and Georgia is instead a disambiguation page?
The consensus is that there is no primary topic for the term "Georgia". Supporters of that position successfully argued that since the country is not significantly more commonly searched for than the US state of the same name, it cannot have primary topic over the US state. Opponents argued that internationally recognized countries should take precedence over sub-national units like the US state. Some opponents argued that the current setup conveys a US-centric bias. Attempts to rename the articles to a natural disambiguation title like "Republic of Georgia" or "State of Georgia" have not reached any consensus (see the list of archived discussions).
Why is the Ireland article about the island, while the article on the country is named Republic of Ireland?
The naming of Ireland articles dates back to 2002. Previously, content for both the island and country appeared on the same page, but it was then decided to move content and the page history about the country to its official "Republic of Ireland" description, while keeping content about the island at "Ireland". Ever since, this issue has been heavily disputed, but there has not been any consensus to change this status quo. Previous failed proposals have included making the country the primary topic of "Ireland" instead, or using parenthetical disambiguation titles like "Ireland (island)" and "Ireland (country)". According to an ArbCom ruling in 2009, discussions relating to the naming of these Ireland articles had to occur at Misplaced Pages talk:WikiProject Ireland Collaboration. In 2023 this requirement was withdrawn so discussions can take place on the talk pages as normal.
Why do articles on populated places in the United States primarily use the ] "comma convention" format? Why is there an exemption for cities listed in the AP Stylebook as not requiring a state?
This is an issue where different rules of Misplaced Pages:Article titles can conflict with each other, thus consensus determines which ones to follow. Most of these articles were created by User:Rambot, a Misplaced Pages bot, back in 2002 based on US Census Bureau records. When creating these pages, Rambot used the "Placename, State" naming format, initially setting a consistent naming convention for these articles. Supporters of keeping the "Placename, State" format argue that this is generally the most common naming convention used by American reliable sources. Opponents argue that this format is neither precise nor concise, and results in short titles like Nashville redirecting to longer titles like Nashville, Tennessee. After a series of discussions since 2004, a compromise was reached in 2008 that established the Associated Press Stylebook exception rule for only those handful of cities listed in that style guide (the dominant US newswriting guide) as not requiring the state modifier. There has been since no consensus to do a massive page move on the other articles on US places (although individual requested move proposals have been initiated on different pages from time to time).
|
Archive 1 • Archive 2 • Archive (settlements) • Archive (places) • September 2012 archives • September 2013 archives • October 2013 archives; February 2014 archives; Archive 3; Archive 4; Archive 5; Archive 6
- WP:USPLACE: May 2004 discussion • June 2004 discussion • July 2005 proposal (not passed) • December 2005 proposal (not passed) • August 2006 proposals (not passed) • Aug 2006 proposal to use one international convention (not passed) • September 2006 proposals (not passed) • October 2006 proposal to use the AP Stylebook for major US cities (not passed) • November 2006 proposal to mirror Canadian city conventions (not passed) • November 2006 straw poll • December 2006 proposal (not passed) • January 2007 proposal to use the AP Stylebook for major US cities (not passed) • January 2007 discussion • July 2007 discussion • July 2007 proposal to use one international convention (not passed) • October 2008 decision to use the AP Stylebook for major US cities (passed) • March 2010 discussion • June 2010 discussion • January 2011 RFC (consensus to maintain status quo) • April 2012 discussion • October 2012 discussion on whether to initiate another RFC • December 2012 Collaborative Workspace • December 2012 RFC (consensus to maintain status quo) • February 2013 RFC (no consensus) • June 2013 discussion • January 2014 discussion • February 2014 moratorium discussion • 2018 discussion on state capitals • 2019 discussion on subpages • November 2019 discussion • August 2020 discussion • February 2023 RFC (no consensus to change)
 Archives | ||||||||
Index
|
||||||||
|
This page has archives. Sections older than 180 days may be automatically archived by Lowercase sigmabot III when more than 6 sections are present. |
Need for clarity on linking major American cities
Consensus is sought as to the correct way to refer and link to major American cities such as Los Angeles and Boston. The discussion is being held at Misplaced Pages talk:Manual of Style/Linking#Need for clarity on linking major American cities.
Capitalisation of "oblast" when used as the name of a Ukrainian administrative division
I have made an ngram review of "X O|oblast" for the oblasts listed at Oblasts of Ukraine#List. While many of these do not give an ngram result, where they do, they do not show that oblast is consistently capitalised in sources (per WP:NCCAPS and MOS:CAPS) that would lead us to a conclusion that we should cap these names on WP. See Chernivtsi Oblast, Donetsk Oblast, Kharkiv Oblast, Kherson Oblast, Kiev Oblast (no result for Kyiv Oblast), Lviv Oblast, Poltava Oblast and Sumy Oblast - others retured no result. A cursory look at Google Scholar results would confirm mixed capitalisation - Sumy Oblast, Donetsk Oblast and Kharkiv Oblast. For these names in Cyrillic, oblast (о́бласть) is not capitalised. There is therefore no to argument that capitalisation from the native language gives rise to a need to capitalise the term in English. The same would be true for other administrative divisions (eg raion). The same is likely true where the same terms are used for other nations (eg Russia). Cinderella157 (talk) 02:35, 28 January 2024 (UTC)
- I agree, but see Talk:Russian occupation of Kherson Oblast/Archive 1#Requested move 29 April 2022, Talk:Russian occupation of Kherson Oblast/Archive 1#Requested move 11 June 2022, and especially Talk:Cherkasy Oblast#Requested move 12 May 2022. — BarrelProof (talk) 06:28, 2 February 2024 (UTC)
- RM results that boil down to "capitalize because the sources I prefer and cherrypicked like to do so" are pretty common when people deeply involved in some topic show up in force to dogpile an RM (or one or two bloviate at tremendous length with their personal WP:OR about why something "is" a "proper name" despite numerous RS not treating it as one by capitalizing it). As our editorial pool shrinks, the entire RM process is starting to fail because too few editors pay any attention to it at all, and those who show up to comment too often have a "screw the guidelines and policies, I want capitalization in my topic else" attitude with no regard to sourcing and guidelines. The way to get around this is to do a bunch of source research beforehand showing that the capitalization level is nowhere near what we'd expect for WP to be capitalizing. Not just n-grams but Google News and Google Scholar and IA Scholar results – e.g. here showing that lowercase "oblast" clearly dominates in journals, but do more such searches for all these terms so the evidence is unassailable. Then do a mass RM that is "advertised" at various higher profile venues like WT:MOSCAPS and here and WT:NCCAPS and even WT:AT and WP:VPPOL if it seems to warrant that. Make it clear that the earlier RMs were based on false claims about the capitalization level in the source material and that you can prove it. This is basically the same situation as all that sports raft stuff: topic-devoted editors are hell-bent on over-capitalizing, but do not have the sourcing to justify it. Same with the state panhandles (an RM saga that still continues). — SMcCandlish ☏ ¢ 😼 06:59, 2 February 2024 (UTC)
- I'm not sure practices in other languages should be used to decide what to do in English; different languages just have different conventions. French, for example, capitalizes noun forms (like Amérique for America) but definitely not demonyms (like américain for American). French does Amérique centrale for Central America but Amérique du Sud for South America, though that may be similar to the difference between "North America" and "northern America".
- I guess in English there's disagreement or uncertainty over whether the type descriptor is part of a proper noun or a separate noun being modified by a proper noun adjunct. Misplaced Pages:Naming conventions (US stations) says "station" is lowercase except where "Station" is already part of the name, leaving that question up to sourcing. Conductors say South Station and not "South", and "Penn Station" not "Penn" (which means the university). But they might say "Back Bay" or "Yonkers", so we have Back Bay station and Yonkers station. But many people write e.g. "Back Bay Station" as if "Back Bay" is a short version of the full proper name, just as "New York" is a short version of "New York City", which is never written "New York city". This is somewhat unsatisfying, but so is the difference in pronunciation between "Kansas" and "Arkansas", so c'est la vie.
- Given sometimes the type descriptor is incorporated into the name and sometimes it's not, and given that capitalization of type descriptors in general seems to be common in English though not always universal, I think declaring as a style choice that English Misplaced Pages always capitalizes would be acceptable as an arbitrary choice between two common conventions, and also safer in that we'd never mistakenly lowercase a name where the descriptor has been incorporated, which seems to happen over time or for words where the short version is already taken.
- It looks like Misplaced Pages:Naming conventions (Ukrainian places) already favors the capitalized version, and given that some professional English sources use that convention, it's not wrong for Misplaced Pages to choose it arbitrarily. Especially given that the short versions of these names are already taken by city names, it seems likely that the type descriptors have or will some day be firmly incorporated by English speakers. -- Beland (talk) 19:11, 13 March 2024 (UTC)
- To be fair, the naming convention page is silent on capitalisation except for the usage. Weirdly the Ukrainian English-language newspapers I can find use the word "region" instead of oblast in their reporting... SportingFlyer T·C 21:15, 13 March 2024 (UTC)
- RM results that boil down to "capitalize because the sources I prefer and cherrypicked like to do so" are pretty common when people deeply involved in some topic show up in force to dogpile an RM (or one or two bloviate at tremendous length with their personal WP:OR about why something "is" a "proper name" despite numerous RS not treating it as one by capitalizing it). As our editorial pool shrinks, the entire RM process is starting to fail because too few editors pay any attention to it at all, and those who show up to comment too often have a "screw the guidelines and policies, I want capitalization in my topic else" attitude with no regard to sourcing and guidelines. The way to get around this is to do a bunch of source research beforehand showing that the capitalization level is nowhere near what we'd expect for WP to be capitalizing. Not just n-grams but Google News and Google Scholar and IA Scholar results – e.g. here showing that lowercase "oblast" clearly dominates in journals, but do more such searches for all these terms so the evidence is unassailable. Then do a mass RM that is "advertised" at various higher profile venues like WT:MOSCAPS and here and WT:NCCAPS and even WT:AT and WP:VPPOL if it seems to warrant that. Make it clear that the earlier RMs were based on false claims about the capitalization level in the source material and that you can prove it. This is basically the same situation as all that sports raft stuff: topic-devoted editors are hell-bent on over-capitalizing, but do not have the sourcing to justify it. Same with the state panhandles (an RM saga that still continues). — SMcCandlish ☏ ¢ 😼 06:59, 2 February 2024 (UTC)
Region-specific guidance for Turkish cities
Can we add some specific guidance for Turkish cities? For some cities, this is almost getting to ridiculous levels. For example, count how many Smyrna's are in the lead of İzmir in this version (there's one extra in the footnote as well). Btw, there's also Smyrna and Old Smyrna articles. Historic names should usually be presented in "Names" or "Etymology" sections, except significant ones such as Constantinople in the lead of Istanbul for example. However, non-English alphabet versions should also be in "Names" or "Etymology" sections. Turkish is spoken by 85-90% of the population. The rest is mostly Kurdish. Except Arabic, other languages would be less than 0.1% Bogazicili (talk) 16:41, 27 March 2024 (UTC)
Türkiye
Could we get a section addressing users adding Türkiye or replacing Turkey with Türkiye? I usually revert those edits and point to wp:commonname or another MOS-related guideline, but it would be helpful to point here. Classicwiki (talk) If you reply here, please ping me. 05:54, 2 May 2024 (UTC)
- Probably easier to have a generic “use the main articles title”; we may eventually move the article to Türkiye, and even we do we will have the problem in the opposite direction. BilledMammal (talk) 06:13, 2 May 2024 (UTC)
Sněžka", Śnieżka or an English exonym, if there is one ?
A discussion at Talk:Sněžka#Requested move 17 July 2024, regarding a mountain on the Polish—Czech border, may be of interest. —Roman Spinner (talk • contribs) 17:44, 18 July 2024 (UTC)
Primary topics and WP:USPLACE
How should we decide the primary topics of "Placename, Country", "Placename (city)", "Placename (town)", etc., especially for some countries (like the United States) whose cities cannot have articles named Placename, Country? The existing rules applied to Canada may be useful references. John Smith Ri (talk) 15:20, 13 September 2024 (UTC)
- @John Smith Ri: There is a difference between naming conventions and eligibility as a primary topic, i.e. a page name does not need to be eligible to be the preferred title of an article in order to be in contention for primary topic; it is sufficient for the page name to be eligible either for preferred title or redirect. For example, Barack Obama is the primary topic of Obama even though the latter would never be allowed as the title of the article. And so Birmingham, United States is a primary redirect to Birmingham, Alabama even though other Birminghams exist in the US. (Note that Birmingham, England, is not in contention for primary topic since Birmingham, United States is neither a valid title nor redirect to that topic.) -- King of ♥ ♦ ♣ ♠ 16:58, 23 October 2024 (UTC)
- However, Birmingham, England is the primary article for “Birmingham”. Blueboar (talk) 17:34, 23 October 2024 (UTC)