Page semi-protected

Wikipedia:Requested moves

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Closing instructions

Click here to purge this page

Requested moves is a process for requesting the retitling (moving) of an article, template, or project page on Wikipedia. (For retitling files, categories and other items, see When not to use this page.) Please read the article titling policy and the guideline regarding primary topics before moving a page or requesting a page move.

Any autoconfirmed user can use the Move function to perform most moves (see Help:How to move a page). If you have no reason to expect a dispute concerning a move, be bold and move the page. However, it may not always be possible or desirable to do this:

  • Technical reasons may prevent a move: a page may already exist at the target title and require deletion, or the page may be protected from moves. See: § Requesting technical moves.
  • Requests to revert recent, undiscussed, controversial moves may be made at WP:RM/TR. If the new name has not become the stable title, the undiscussed move will be reverted. If the new name has become the stable title, a requested move will be needed to determine the article's proper location.
  • A title may be disputed, and discussion may be necessary to reach consensus: see § Requesting controversial and potentially controversial moves. The requested moves process is not mandatory, and sometimes an informal discussion at the article's talk page can help reach consensus.
  • Unregistered users and new (not yet autoconfirmed) users are unable to move pages.

Requests are generally processed after seven days. If consensus is reached at or after this time, a reviewer will enact the request. If not, the request may be re-listed to allow more time for consensus to develop, or the discussion closed as "no consensus". See Wikipedia:Requested moves/Closing instructions for more details on the process.

Wikipedia:Move review can be used to contest the outcome of a move request as long as all steps are followed. If a discussion on the closer's talk page does not resolve an issue, then a move review will evaluate the close of the move discussion to determine whether or not the contested close was reasonable and consistent with the spirit and intent of common practice, policies, and guidelines.

When not to use this page

Separate processes exist for moving certain types of pages, and for changes other than page moves:

Undiscussed moves

Autoconfirmed editors may move a page without discussion if all of the following apply:

  • No article exists at the new target title;
  • There has been no discussion (especially no recent discussion) about the title of the page that expressed any objection to a new title; and
  • It seems unlikely that anyone would reasonably disagree with the move.

If you disagree with such a move, and the new title has not been in place for a long time, you may revert the move. If you cannot revert the move for technical reasons, then you may request a technical move.

Move wars are disruptive, so if you make a bold move and it is reverted, do not make the move again. Instead, follow the procedures laid out in § Requesting controversial and potentially controversial moves.

Requesting technical moves

If you are unable to complete a technical move, request it below. If this is your first article and you want your draft article published, please submit it for review at Articles for creation, by adding the code {{subst:submit}} to the top of the draft or user sandbox page instead of listing it here.

  • To list a technical request: edit the Uncontroversial technical requests subsection and insert the following code filling in pages and reason:
    {{subst:RMassist| current page title | new page title | reason = reason for move}}
    
    This will automatically insert a bullet and include your signature. Please do not edit the article's talk page.
  • If you object to a proposal listed in the uncontroversial technical requests section, please move the request to the Contested technical requests section, append a note on the request elaborating on why, and sign with ~~~~.
  • If your technical request is contested, or if a contested request is left untouched without reply, create a requested move on the article talk and remove the request from the section here. The fastest and easiest way is to click the "discuss" button at the request, save the talk page, and remove the entry on this page.


Technical requests

Uncontroversial technical requests

Contested technical requests

Requests to revert undiscussed moves

Requesting controversial and potentially controversial moves

The discussion process is used for potentially controversial moves. The move is potentially controversial if any of the following apply:

  • There is an existing article (not just a redirect) at the target title;
  • There has been any past debate about the best title for the page;
  • Someone could reasonably disagree with the move.

Use this process if there is any reason to believe a move would be contested. In particular, use this process before moving any existing page with incoming links to create a disambiguation page at that title. For technical move requests (e.g. spelling and capitalization fixes), see Requesting technical moves.

Do not put more than one open move request on the same talk page, because this is not supported by the bot that handles updates to this page. Multiple closed move requests may be on the same page, but each should have a unique section heading.

Requesting a single page move

To request a single page move, edit at the bottom of the talk page of the article you want moved, without adding a new header, inserting this code:

{{subst:requested move|NewName|reason=Place here your rationale for the proposed page name change, ideally referring to applicable naming convention policies and guidelines, and providing evidence in support where appropriate. If your reasoning includes search engine results, please prioritize searches limited to reliable sources (e.g. books, news, scholarly papers) over other web results. Do not sign this.}}

Replace NewName with the requested new name of the page (or with a question mark, if you want more than one possible new name to be considered). The template will automatically create the heading "Requested move 06 May 2019" and sign the post for you.

Use the code |talk=yes to add separate locations for survey and discussion.

There is no need to edit the article in question. Once the above code is added to the Talk page, a bot will automatically add the following notification at the top of the article:

Note: Unlike other request processes on Wikipedia, such as RfC, nominations need not be neutral. Make your point as best you can; use evidence (such as Ngrams and pageview statistics) and refer to applicable policies and guidelines, especially our article titling policy and the guideline on disambiguation and primary topic.

WikiProjects may subscribe to Article alerts to receive RM notifications, e.g. this page is transcluded to here. RMCD bot notifies many of the other Wikiprojects listed on the talk page of the article to be moved to invite project members to participate in the RM discussion. Requesters should feel free to notify any other Wikiproject or Noticeboard that might be interested in the move request.

Requesting multiple page moves

A single template may be used to request multiple related moves. On one of the talk pages of the affected articles, create a request and format it as below. A sample request for three page moves is shown here (for two page moves, omit the lines for current3 and new3). For four page moves, add lines for current4 and new4, and so on. There is no technical limit on the number of multiple move requests, but before requesting very large multi-moves, consider whether a naming convention should be changed first. Discuss that change on the talk page for the naming convention, e.g., Wikipedia talk:Naming conventions (sportspeople).

To request a multiple page move, edit at the bottom of the talk page of the article you chose for your request, without adding a new header, inserting this code:

{{subst:requested move
| new1 = New title for page 1 with the talk page hosting this discussion
| current2 = Current title of page 2
| new2 = New title for page 2
| current3 = Current title of page 3
| new3 = New title for page 3
| reason = Place here your rationale for the proposed page name change, ideally referring to applicable naming convention policies and guidelines, and providing evidence in support where appropriate. If your reasoning includes search engine results, please prioritize searches limited to reliable sources (e.g. books, news, scholarly papers) over other web results. Do not sign this.}}

For example, to propose moving the articles Wikipedia and Wiki, put this template on Talk:Wikipedia, and replace current2 with Wiki. The discussion for all affected articles is held on the talk page of the article at page 1 (Talk:Wikipedia). Do not sign a request with ~~~~ as the template does this automatically. Do not skip pairs of numbers.

RMCD bot automatically places a notice section on the talk page of the additional pages that are included in your request, advising that the move discussion is in progress, where it is, and that all discussion for all pages included in the request should take place at that one location.

Occasionally the discussions for significant multi-move requests may be hosted on WikiProject talk pages or other pages in Project namespace. For multi-move discussions hosted on a page which is not itself proposed to be moved, specify |current1=Current title of page 1 for the first page to move.

Template usage examples and notes
Talk page tag Text that will be shown (and usage notes)
{{subst:Requested move |new|reason=why}}
links talk edit
Requested move 06 May 2019

Wikipedia:Requested movesNew – why Example (talk) 06:49, 06 May 2019 (UTC)

Use when the proposed new title is given.
Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst:.
This tag should be placed at the beginning of the section containing the relevant discussion.

{{subst:Requested move|?|reason=why}}
Requested move 06 May 2019

Wikipedia:Requested moves → ? – why Example (talk) 06:49, 06 May 2019 (UTC)

Use when the proposed new title is not known.
Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst:.
This tag should be placed at the beginning of the section containing the relevant discussion.

{{subst:Requested move |new|reason=why|talk=yes}}
Requested move 06 May 2019

Wikipedia:Requested movesNew – why Example (talk) 06:49, 06 May 2019‎ (UTC)

Survey
Feel free to state your position on the renaming proposal by beginning a new line in this subsection with *'''Support''' or *'''Oppose''', then sign your comment with ~~~~. Since polling is not a substitute for discussion, please explain your reasons, taking into account Wikipedia's policy on article titles.
Discussion
Any additional comments:



This template adds subsections for survey and discussion.
Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst:
Click the "New Section" tab on the talk page and leave the Subject/headline blank, as the template by default automatically creates the heading.

{{subst:Requested move |new1=x|current2=y|new2=z|reason=why}}
Requested move 06 May 2019

– why Example (talk) 06:49, 06 May 2019 (UTC)

Do not sign this template—this tag is auto-signed when substituted.
Be sure to use the subst: and place this tag at the beginning of the section containing the relevant discussion.
Add additional related move requests in pairs (|current3= and |new3=, |current4= and |new4=, etc.).

{{subst:Requested move |new1=?|current2=y|new2=?|reason=why}}
Requested move 06 May 2019

– why Example (talk) 06:49, 06 May 2019 (UTC)

Commenting in a requested move

All editors are welcome to contribute to the discussion regarding a requested page move. There are a number of standards that Wikipedians should practice in such discussions:

  • When editors recommend a course of action, they write Support or Oppose in bold text, which is done by surrounding the word with three single quotes on each side, e.g. '''Support'''.
  • Comments or recommendations are added on a new bulleted line (that is, starting with *) and signed by adding ~~~~ to the end. Responses to another editor are threaded and indented using multiple bullets.
  • The article itself should be reviewed before any recommendation is made; do not base recommendations solely on the information supplied by other editors. It may also help to look at the article's edit history. However, please read the earlier comments and recommendations, as well as prior move requests. They may contain relevant arguments and useful information.
  • Vested interests in the article should be disclosed per Wikipedia:Conflict of interest#How to disclose a COI.

When participating, please consider the following:

  • Editors should make themselves familiar with the article titling policy at Wikipedia:Article titles.
  • Other important guidelines that set forth community norms for article titles include Wikipedia:Disambiguation, specific naming conventions, and the manual of style.
  • The debate is not a vote; please do not make recommendations that are not sustained by arguments.
  • Explain how the proposed article title meets or contravenes policy and guidelines rather than merely stating that it does so.
  • Nomination already implies that the nominator supports the name change, and nominators should refrain from repeating this recommendation on a separate bulleted line.[a]
  • Do not make conflicting recommendations. If you change your mind, use strike-through to retract your previous statement by enclosing it between <s> and </s> after the bullets, and de-bold the struck words, as in "• Support Oppose".

Please remember that reasonable editors will sometimes disagree, but that arguments based in policy, guidelines, and evidence have more weight than unsupported statements. When an editor offers an argument that does not explain how the move request is consistent with policies and guidelines, a reminder to engage in constructive, on-topic discussion may be useful. On the other hand, a pattern of responding to requests with groundless opinion, proof by assertion, and ignoring content guidelines may become disruptive. If a pattern of disruptive behavior persists after efforts are made to correct the situation through dialogue, please consider using a dispute resolution process.

Closing instructions

Any uninvolved editor in good standing may close a move request. Please read the closing instructions for information on how to close a move request. The Simple guide to closing RM discussions details how to actually close a requested move discussion.

Relisting

Relisting a discussion moves the request out of the backlog up to the current day in order to encourage further input. The decision to relist a discussion is best left to uninvolved experienced editors upon considering, but declining, to close the discussion. In general, discussions should not be relisted more than once before properly closing.[b] Users relisting a debate which has already been relisted, or relisting a debate with a substantial discussion, should write a short explanation on why they did not consider the debate sufficient to close. While there is no consensus forbidding participation in a requested move discussion after relisting it, many editors consider it an inadvisable form of supervote. If you want to relist a discussion and then participate in it, be prepared to explain why you think it was appropriate.

Relisting can be done using {{subst:relisting}}, which also signs it automatically, and is placed at the very end of the initial request (after their signature, and subsequent re-listers signatures). When a discussion has been relisted a bot partially underlines the "Discuss" link in the lists of debates: (Discuss).

When a relisted discussion reaches a resolution, it may be closed at any time according to the closing instructions; there is no required length of time to wait before closing a relisted discussion.

If discussion has become stale, or it seems that discussion would benefit from more input of editors versed in the subject area, consider more widely publicizing the discussion, such as by notifying WikiProjects of the discussion using the template {{RM notification}} or {{Mdn}}. Banners placed at the top of the talk page hosting the move request can often be used to identify WikiProjects suitable for notification.

Notes

  1. ^ A nominator making a procedural nomination with which they may not agree is free to add a bulleted line explaining their actual position. Additional detail, such as sources, may also be provided in an additional bullet point if its inclusion in the nomination statement would make the statement unwieldy. Please remember that the entire nomination statement is transcluded into the list on this page.
  2. ^ Despite this, discussions are occasionally relisted up to three times.

Current discussions

This section lists all requests filed or identified as potentially controversial which are currently under discussion.

This list is also available in a page-link-first format and in table format. 38 discussions have been relisted, indicated by (Discuss)

May 6, 2019

  • (Discuss)Veracity of statements by Donald TrumpFalse statements by Donald Trump – This move was done without RM here, but the guidelines at WP:RM#CM require an RM in this case. No editor can reasonably claim that this move is not "controversial [or] potentially controversial". "Use this process if there is any reason to believe a move would be contested." My starting this RM does not constitute support for the move, and I may !vote later. Per MrX here, please !vote only Support or Oppose for the new title, and propose any other alternatives in separate RMs, bearing in mind that only one RM can be open at a time.Mandruss  12:31, 22 April 2019 (UTC)--Relisting. B dash (talk) 03:10, 6 May 2019 (UTC)

May 5, 2019

  • (Discuss)Kossuth térKossuth square – Per WP:UE. There is a commonly used English name for this square, Kossuth square, so we should prefer that rather than the Hungarian language title. See for example: [12][13][14][15] Note that "Kossuth Lajos square" does seem to be used by some sources too, but I have proposed moving to the shorter one per WP:CONCISE.  — Amakuru (talk) 09:28, 5 May 2019 (UTC)

May 4, 2019

  • (Discuss)Lake Michigan Conference (defunct) → ? – There has to be a better disambiguator than (defunct), but I'm not sure what it is. (Wisconsin) might work except not all the schools were in Wisconsin. (NCAA) or (college conference) probably would work, but I am also not a topic expert so I would like some advice. I caught this oddball while looking for radio stations using this disambiguator. The other article with a similar name, Lake Michigan Conference (Michigan), relates to a conference of high schools; it's probably the primary topic, as it is pulling more than twice the pageviews. Raymie (tc) 02:24, 21 April 2019 (UTC) --Relisting. IffyChat -- 21:17, 4 May 2019 (UTC)
  • (Discuss)Links between Trump associates and Russian officialsLinks between Trump associates and Russians – Dropping "officials" makes sense, as the contacts included many types of Russians, most of whom were not officials. This does not change the scope of the article or any change of content but brings the title into harmony with the existing content.
    The current title sets up a false expectation that Trump campaign members' contacts with "officials" were the only things investigated, when, in fact, their contacts with numerous Russians were investigated, from oligarchs, Russian FSB and GRU agents, professors, politicians, businessmen, etc. BullRangifer (talk) 02:41, 4 May 2019 (UTC)
  • (Discuss)Native American civil rightsNative American rights – Article title "Native American civil rights" violates WP:COMMONNAME for the following reasons: ::Between 1965–2008 :*Google Ngram - The term "Native American rights" is the most dominant term among the terms "Native American rights", "American Indian rights", "Native American civil rights", and "American Indian civil rights". ::Between 2009–2019 :*Google Scholar - "Native American rights": 2,340 hits (custom date range from 2009 to 2019) :*Google Scholar - "American Indian rights": 476 hits (custom date range from 2009 to 2019) :*Google Scholar - "Native American civil rights": 180 hits (custom date range from 2009 to 2019) :*Google Scholar - "American Indian civil rights": 135 hits (custom date range from 2009 to 2019) :*JSTOR - "Native American rights": 319 hits (custom date range from 2009 to 2019) :*JSTOR - "American Indian rights": 72 hits (custom date range from 2009 to 2019) :*JSTOR - "Native American civil rights": 16 hits (custom date range from 2009 to 2019) :*JSTOR - "American Indian civil rights": 15 hits (custom date range from 2009 to 2019) :*Google Books - "Native American rights": 15 books (custom date range from 1/1/2009 to 5/3/2019) :*Google Books - "American Indian rights": 3 books (custom date range from 1/1/2009 to 5/3/2019) :*Google Books - "Native American civil rights": 5 books (custom date range from 1/1/2009 to 5/3/2019) :*Google Books - "American Indian civil rights": 4 books (custom date range from 1/1/2009 to 5/3/2019)
    :Mitchumch (talk) 02:01, 4 May 2019 (UTC)
  • (Discuss)Wikipedia:Follow the leaderUser:Sebwite/Follow the leader – On 4 July 2008, Sebwite created Wikipedia:Follow the leader as a proposed Wikipedia deletion policy (which was summarily rejected above). More than 10 years later, the article has in no way developed past Sebwite's initial contributions. [17] This isn't necessarily a bad thing, but it has numerous contradictions with established Wikipedia consensus which can be... problematic to say the least. For example, it makes a few suggestions that the creator and main contributors of an article are really the ones who can best make a judgment [about its deletion]. Even more odd are phrases like: Therefore, editors who participate in an AfD discussion should not be swayed by how others have commented, which is just... yeah. I get it, right. Sebwite is really making a nuanced point here about WP:!VOTE and WP:NOTDEMOCRACY, but it just comes across as encouraging WP:IDHT.
    Per WP:Essays, Essays that... are found to contradict widespread consensus, belong in the user namespace. This is the case for WP:Template the regulars, and I feel it is a fine solution to userfy this article. –MJLTalk 01:54, 4 May 2019 (UTC)
  • (Discuss)LoudpvckKenny Beats – Kenny Beats is more well known at this stage, having several collaborations and producing for well known artists such as Vince Staples, and Jpegmafia. He has just released an album alongside Rico Nasty under the 'Kenny Beats' moniker. Further, Loudpvck is a group turned solo project, not Kenny's professional name, and so the naming of this page is currently misleading. AM Woody (talk) 19:25, 25 April 2019 (UTC)--Relisting. -- Dane talk 01:05, 4 May 2019 (UTC)

May 3, 2019

  • (Discuss)Stock Yards branchStock Yards Branch – Should "Branch" be capitalized in the title? I don't have an opinion on this and I don't usually edit in this particular topic area. I don't really care whether it's capitalized, but someone might. The outcome might be applicable to similar articles such as Westchester Branch. Jc86035 (talk) 15:31, 3 May 2019 (UTC)
  • (Discuss)Enigma (musical project)Enigma (German band) – This disambiguator is bad. "Musical project" is not listed in WP:MUSICDAB as an option, and in my opinion, it is a pretentious attempt to make a plural neutral description of the "act". More importantly, it is needlessly long and does not actually disambiguate - it is ambiguous with Enigma (British band), which introduces the band as another "musical project". I understand the concept of these "projects": bands that aren't actually bands, they tend to be controlled by a single person but are often referred to as a collective, so WP has to pick between them (eg Owl City). I believe (band) to be a suitable disambiguator, for consistency with the British band, and because M83 (band), another "project", seems to have no problem using it, though (group) would also work, should this be the consensus. (Note: I recently moved (UK band) to (British band) which is the preferred demonym used in examples at WP:MUSICDAB) Lazz_R 13:28, 3 May 2019 (UTC)
  • (Discuss)Jewish vegetarianismJewish Vegetarianism and Veganism – Jewish veganism and vegetarianism are both discussed within this article, and including them both in the title would follow the new scholarly book Jewish Veganism and Vegetarianism: Studies and New Directions, ed. Labendz and Yanklowitz. I don't think that there is enough material for separate Wikipedia articles on Jewish veganism and Jewish vegetarianism, and according to this book veganism and vegetarianism are intertwined. FrankKaplan (talk) 00:24, 3 May 2019 (UTC)

May 2, 2019

  • (Discuss)Central KurdishSorani – Since Kurds speak more than one language, the language name "Sorani" is more suitable and more natural than "Central Kurdish". Also the mostly Wikipedia in other language versions use the term "Sorani" as for example the German Wikipedia[24], the Kurdish Wikipedia[25], the French Wikipedia[26], the Portuguese Wikipedia[27], the Catalan Wikipedia[28], the Danish Wikipedia[29], even the Japanese Wikipedia[30]. This shows that the name Sorani is more widespread than Central Kurdish. 5.18.205.39 (talk) 19:53, 2 May 2019 (UTC)
  • (Discuss)Bosnian nationalismBosniak nationalism – This article discusses Bosniak, not Bosnian, nationalism. All participants on this page agree that those are two different things. Even the lead section of the article itself says that "Bosniak nationalism" "should not be confused with Bosnian nationalism". Vanjagenije (talk) 07:49, 2 May 2019 (UTC)
  • (Discuss)MSGMSG (disambiguation) – "MSG" primarily refers to Monosodium glutamate, and should be a WP:PRIMARYREDIRECT there. (Let's not discuss moving Monosodium glutamate to MSG here; someone can propose that if this succeeds.) I tested the pageviews of the top entries in mid-March, and here are the top five results. As you can see, only Madison Square Garden and Madison Square Garden Company come close to rivaling the chemical compound. Now, with Monosodium glutamate and Madison Square Garden running neck-to-neck in the results, that would normally not be sufficient to make a determination of primary topic. However, as you can see from usage in the respective articles, the compound is referred to as MSG far more frequently than the venue; "MSG" is the default name for the compound in encyclopedic prose, something which is not true for almost all the other entries on the list. Anecdotally, I live in the New York metropolitan area, which if anything should bias me towards the venue, but when I hear the word "MSG" without context it unambiguously refers to the compound for me. Monosodium glutamate will exist for eternity, but the long-term significance of Madison Square Garden is less clear (the original Penn Station which it replaced lasted just 53 years before being demolished). To confirm my suspicions, I did a test by taking the top three entries and setting up special-purpose redirects to measure where people go after reaching the MSG disambiguation page. This is very different from the first pageview test; that one measures the relative popularity of different topics, while this measures how likely it is for MSG to refer to a particular topic, which is a much more accurate test. It's not even a contest, with Monosodium glutamate taking 87% of top-three share. King of ♠ 03:43, 2 May 2019 (UTC)

May 1, 2019

  • (Discuss)DreamWorksDreamWorks Pictures – The move is blocked by a redirect. The correct name of this production company is DreamWorks Pictures. It is inaccurate and confusing to call this company DreamWorks. There are several production companies with DreamWorks in the name, as listed in the DreamWorks disambiguation page, https://en.wikipedia.org/wiki/DreamWorks_(disambiguation) and none of these companies is called just DreamWorks (not even DreamWorks animation, which uses dreamworks.com, is called just "DreamWorks"). Hattiedog (talk) 17:09, 1 May 2019 (UTC)
  • (Discuss)SmilesSmiles (disambiguation)WP:ASTONISH clear PT per PT#2 and Smile got 10,224 views compared to 36 for the film, 5 for the song and 4 for the drug [[31]]. Even though readers and editors are used to things being at the singular it would seem that the primary topic of "Smiles" is still Smile. A Google image search returns results that appear to show nothing but Smiles. Even cases like Cars, Cats and Bones that have topics that are of a similar popularity go to the singular, Smiles doesn't appear to have anything comparable by views. Crouch, Swale (talk) 17:07, 1 May 2019 (UTC)
  • (Discuss)Empress Emerita MichikoMichiko – Aside from the fact that the name for this page is too long, it is also awkward to have their husbands who are the actual monarchs listed only by their given names while the wives appear with the title "Empress X" on Wikipedia. I suggest using the given name for these two pages as well. To those who might say that for consorts we use "Queen" or "Empress" before their given names, I think I need to emphasize that what I'm suggesting here is not unprecedented, especially for Asian and African queens. Examples include Sirikit (instead of Queen Sirikit), Rambai Barni (instead of Queen Rambai Barni), Jetsun Pema (instead of Queen Jetsun Pema), Nefertiti (instead of Queen Nefertiti), etc. Keivan.fTalk 04:42, 1 May 2019 (UTC)

April 30, 2019

  • (Discuss)Fumihito, Prince Akishino → ? – An official statement published by the Imperial Household Agency refers to the couple as His Imperial Highness The Crown Prince and Her Imperial Highness The Crown Princess. Meanwhile, the official biography of the couple refers to them as Their Imperial Highnesses Crown Prince and Crown Princess Akishino (could it be a typo?). Should these two pages be titled "Fumihito, Crown Prince of Japan" and "Kiko, Crown Princess of Japan" or "Fumihito, Crown Prince Akishino" and "Kiko, Crown Princess Akishino"? In my opinion, we should go with the official statement because to me the second set of titles sounds pretty bizarre but that's how they have written it on their website, so now we have two versions to choose from. Keivan.fTalk 23:50, 30 April 2019 (UTC)
  • (Discuss)The American Revolution (film)WBCN and The American Revolution – This article was first written in May 2011 in the early stages of the production of the film, then titled "The American Revolution". More recently the two words "WBCN and..." were appended to the front of the film's title, and the film was released in early 2019 under that title. I suggest moving the article to a new name, retaining the original article name as a redirect. See also the film's own website https://www.theamericanrevolution.fm/ . (This WP article, last updated January 2018, also now needs expansion, possibly including references to announcements and reviews of the film.) Acwilson9 (talk) 21:52, 30 April 2019 (UTC)
  • (Discuss)Robert von WirénRobert Viren – After an undiscussed reversion to the Wiren usage, despite the RM above. Apparently on the justification of his "Ltheran faith and buried in a lutheran cemetery". Which has nothing to do with his WP:COMMONNAME, which as a Russian raised in Russia and who served in Russia his whole life, used the Russian form of his name. He is, as has been pointed out above, exclusively referred to as Viren in reliable sources, such as Evan Mawdsley's The Russian Revolution and the Baltic Fleet and Norman Saul's Sailors in Revolt: Russian Baltic Fleet in 1917. Can list more if required. Spokoyni (talk) 20:44, 30 April 2019 (UTC)
  • (Discuss)Lo-fi (disambiguation)Lo-fiLo-fi was a redirect to Lo-fi music but I converted it into a disambiguation page because there are a number of terms to which "lo-fi" could refer. User:Ilovetopaint moved the disambiguation page Lo-fi to Lo-fi (disambiguation) and redirected Lo-fi to Lo-fi music. I wish to undo that undiscussed move: "Lo-fi music" is not the primary topic for "Lo-fi". "Lo-fi" in the sense of audio reproduction (Lo-fi (audio) redirects to Fidelity#Audio and electronics) is a long-standing term used to describe low-fidelity technical reproduction techniques, not the lo-fi music aesthetic. I don't think either term is WP:PRIMARYTOPIC: the aesthetic may have more popularity but the technical reproduction meaning has a longer-term use. About two-thirds of the ambiguous uses of "lo-fi" that I have fixed mean the aesthetic: about one third mean audio reproduction. Shhhnotsoloud (talk) 13:44, 30 April 2019 (UTC)
  • (Discuss)Chinese white dolphinIndo-Pacific humpback dolphin – The Chinese white dolphin is a subspecies of Sousa chinensis. The Taiwanese population also covered here is another subspecies. Ergo, this page should be moved to describe Sousa chinensis. The linked page refers to a different species of dolphin sometimes referred to as the Indo-Pacific humpbacked dolphin. The IUCN, scientific literature, the Society of Marine Mammalogy, ITIS and others use Indo-Pacific humpbacked dolphin for Sousa chinensis. WhiteArcticWolf (talk) 20:14, 21 April 2019 (UTC) --Relisting. feminist (talk) 04:47, 30 April 2019 (UTC)
  • (Discuss)Daniel Martins (Equatoguinean footballer)Daniel Martins (footballer, born 1972) – And Daniel Martins (Portuguese footballer) to Daniel Martins (footballer, born 1993). First of all, for this type of ambiguities (where the name and profession coincide), the year of birth is used, not the nationality. If not, another way is to include the middle name (if both have) (it applies in this case). Another reason for the move is that Daniel Sabino Martins is not exactly an Equatoguinean footballer despite having some appearances (none of them being official) for the Equatorial Guinea national team. He is a Brazilian national who was already in his final years as an active footballer and only then accepted the proposal to play for the Equatorial Guineans as he never had the opportunity to be an international footballer for Brazil. Also, he had never been to Equatorial Guinea before that nor does he have Equatorial Guinean descent. MonFrontieres (talk) 03:06, 30 April 2019 (UTC)

April 29, 2019

  • (Discuss)AwaynatAl Awaynat – Former article title; moved in 2011. NGA does not list name as variant, names listed are: "Al ‘Uwaynāt" (approved), and "Al Awaynat", "Aouinet", "El-Auénat", "Sardalas", "Sardalīs", "Serdeles" (variants). Google Maps is "Alawenat". All English-language transliterations seem to have have the article "al", and "Al Awaynat" (rather than "Al ‘Uwaynāt") is more consistent to Wikipedia's transliterations of other Libyan placenames. Julia 22:08, 29 April 2019 (UTC)
  • (Discuss)Gehaz El Reyada StadiumMilitary Sport Apparatus Stadium – The stadium's name in Arabic is ستاد جهاز الرياضة العسكري; and by transliterating that name it would be Gehaz El Reyada El Askari Stadium, or simply Gehaz El Reyada Stadium. However, by looking at Category:Football venues in Egypt, I think that the article's name should be changed to a different name per WP:CONSISTENCY. Therefore, I propose moving the article to something like Military Sport Apparatus Stadium if that's the correct translation of the name. Ben5218 (talk) 21:24, 20 April 2019 (UTC) --Relisting. IffyChat -- 12:27, 29 April 2019 (UTC)

Elapsed listings

  • (Discuss)Cardio Infantil (TransMilenio)Calle 161 (TransMilenio) – station renamed"1". 181.53.12.70 05:27, 29 April 2019 (UTC)
  • (Discuss)35mm movie film35 mm movie film – Based on a brief discussion (above) not mentioning our own guidance at MOS:UNITSYMBOLS, spaces were removed from these titles, making them inconsistent with the rest of wikipedia and the advise of standards organization. So let's undo that mistake. The only other place that WP squeezes out the space is in the names of lenses, and it's OK there because those are names as used by their manufacturers. In the case of 35 mm movie film and the other 35 mm topics, it's a measurement, not a name. Dicklyon (talk) 19:28, 28 April 2019 (UTC)

Backlog

  • (Discuss)Battle of PressburgBattle of Brezalauspurc – There are specialists of the history of the period who do not associate Brezalauspurc (as the venue of the battle mentioned in the primary source) with Pressburg, but with Mosaburg, consequently the present name contradicts WP:NPOV. (For further details, I refer to Bowlus, Charles R. (1994). Franks, Moravians and Magyars: The Struggle for the Middle Danube, 788–907. University of Pennsylvania Press. ISBN 0-8122-3276-3., and to Szőke, Béla Miklós (2014). The Carolingian Age in the Carpathian Basin. Hungarian National Museum. ISBN 978-615-5209-17-8.) Borsoka (talk) 03:16, 11 April 2019 (UTC)--Relisting. B dash (talk) 02:17, 20 April 2019 (UTC) --Relisting. SITH (talk) 14:20, 27 April 2019 (UTC)
  • (Discuss)Russian Bible SocietyThe Bible Society in Russia – 1. 'Российское Библейское Общество' (The name of the organization in Russian, the original language) founded in Russia does not translate their own name into English as 'Russian Bible Society', they translate it as 'The Bible Society in Russia'(See official website of the organization: http://www.biblia.ru/en/about/history/ ). The English version of the name 'Russian Bible Society' actually belongs to another unrelated organization called 'Русское Библейское Общество' founded in the United States (see the official website of the organization: https://russianbiblesociety.com/ ). 2. The difference in the names of the organizations in Russian (original language of both) is 'Российское' vs. 'Русское'. While both adjectives are often translated into English as 'Russian', each of the words in Russian language has a distinct denotation . 'Российское' suggests belonging to the country of Russia, while 'Русское' suggests belonging to the Russian people or culture. 'The Bible Society in Russia' is a closer translation of 'Российское Библейское Общество' (which is what the organization calls itself in English) than 'Russian Bible Society' (the name incorrectly chosen by the author of the article). Ivanchenkova (talk) 17:14, 12 April 2019 (UTC)--Relisted. – Ammarpad (talk) 05:56, 20 April 2019 (UTC) --Relisting. SITH (talk) 14:16, 27 April 2019 (UTC)
  • (Discuss)Outlook on the webExchange Online – There are various articles for Outlook: Microsoft Outlook and Outlook.com, all these creates so much confusion. While this current platform was once named "Outlook on the web", I noticed that the current name has already been changed to "Exchange Online" (website inside infobox), while the Exchange Online namespace was linked to a section in Microsoft Exchange Server. I believe it has already become the common name, and it should also be changed to prevent confusion between multiple Microsoft email services. I hope to have everyone's input in case I have mixed up different services or platforms. Cheers. Wefk423 (talk) 11:04, 19 April 2019 (UTC) --Relisting. Dreamy Jazz 🎷 talk to me | my contributions 13:47, 27 April 2019 (UTC)
  • (Discuss)NEXUS (frequent traveler program)Nexus (border control program) – Per MOS:ALLCAPS / MOS:TM / WP:TITLETM, ordinary English formatting should be used rather than promotional all-caps styling. The name is obviously intended to be pronounced as a word, and no unabbreviated form of an initialism is evident. I notice only two independent (i.e., non-government) sources that are cited either in the article or here on the talk page: this and this. Both of them use "Nexus", not "NEXUS". Also, it is a government-operated border control program, not a frequent flyer club. The program is based on filling out an application, passing a background check, and paying a fee – not how frequently someone travels. —BarrelProof (talk) 17:18, 18 April 2019 (UTC)--Relisting. -- Dane talk 05:27, 27 April 2019 (UTC)
  • (Discuss)ABSA Group Limited → ? – Absa's name change in 2018 involved a move from ABSA to Absa, and it is now convention among most media[1], and the company, to have the name as Absa. The name change from ABSA (as reflected in the old logo) to Absa took place last May, and was approved by shareholders at the AGM It also trades as Absa on the JSE. [2]We would appreciate if the name change could be effected. Thanks Nicola Mawson (talk) 10:17, 26 April 2019 (UTC)
  • (Discuss)WLQR (AM) → ? – This one is confusing for people without a background in radio, so let's try and explain it simply. In 2010, Cumulus Media, a large owner of radio stations, sold a station known as WTOD in Toledo, Ohio. It desired to keep the WTOD callsign, so it parked it on the former WHSC in Hartsville, South Carolina, which it owned. In March 2016, the South Carolina station switched callsigns with 1470 AM in Toledo, then known as WLQR, and then a week later surrendered its license, having used the WLQR calls for just a week. Six months later, the Toledo AM station followed suit after trading its calls with an FM station (creating a WLQR AM which went defunct and a WTOD FM which is still around). The result: two defunct stations, including one article with an unusual nonstandard disambiguator. Proposals I'd like to consider: *Proposal 1 :*Defunct Ohio station: WLQR (Ohio) :*Defunct South Carolina station: WLQR (South Carolina) *Proposal 2 :*Defunct Ohio station: WLQR (AM) :*Defunct South Carolina station: WTOD (South Carolina), last callsign used for more than a week *Proposal 3 :*Defunct Ohio station: WLQR (AM) :*Defunct South Carolina station: WHSC (Hartsville, South Carolina), using the station's only callsign until it was used to warehouse calls for Toledo (it was used for 64 of the station's 70 years of broadcasting) I'm not sure which is right, but something has to be better than the current placement. Raymie (tc) 05:49, 27 March 2019 (UTC)--Relisting. B dash (talk) 04:19, 14 April 2019 (UTC)--Relisting. B dash (talk) 04:44, 26 April 2019 (UTC)
  • (Discuss)Lost children of FrancoismStolen children of Francoism – This would make the translated title more into line with the literal translation. It is also factually inaccurate as it stands. The children were not "lost" but were taken over the objections of their mothers as a result of Hispanic eugenics policies that said they if they remained with their mothers, they would become opponents of the regime. The children were kidnapped, and put up for adoption. --LauraHale (talk) 08:30, 13 April 2019 (UTC)--Relisting. B dash (talk) 04:43, 26 April 2019 (UTC)
  • (Discuss)Grorud ValleyGroruddalenGroruddalen (as well as many other Norwegian placenames with -dalen og -dal) is most commonly refered to as an administrative entity or sociogeographical area. It is seldom though of as a valley as landscape shape per se. In english texts of norwegian origin, it is by far most common to refer to this area as Groruddalen or even Groruddalen valley. Translation of the suffix might be used for a distancing effect or to make a comic effect. In Category:Valleys of Norway there are 120+ pages, only one other of them with valley, the other ones with their proper norwegian names. Orland (talk) 15:45, 25 April 2019 (UTC)
  • (Discuss)Faxa BayFaxaflói – Faxaflói or Faxaflói Bay is by far the more common name in English-language sources. "Faxa Bay" exists in some (mainly older and outdated) English sources, but it is incorrectly anglicized and not in common use. The Google Ngram data is not relevant, since no Ngram exists for Faxaflói to compare this with the data on Faxa Bay. A review of the Google Books data shows that the quality of the data is extremely poor. A few results for Faxa Bay do actually refer to the bay in Iceland, but a significant number of these search engine results are also irrelevant. Since 1990, about 258 scholarly articles in English on Google Scholar give the name "Faxaflói Bay" but only 79 "Faxa Bay". Sylgja (talk) 22:08, 24 April 2019 (UTC)

References

See also