Wikiwand AI

Wikipedia:Requested moves/Technical requests

From Wikipedia, the free encyclopedia

Welcome to Requested moves/Technical requests

If you are unable to complete a move for technical reasons, you can request a technical move below. This is the correct method if you tried to move a page, but you got an error message saying something like "You do not have permission to move this page, for the following reasons:..." or "This page could not be moved, for the following reason:..."


If you are here because you want an experienced editor to approve of your new article or proposed rename, you are in the wrong place.

To list a technical request: edit the Uncontroversial technical requests subsection or click the big blue button and insert the following code at the bottom of the list, filling in pages and reason:

{{subst:RMassist|current page title|new title|reason=edit summary for the move}}

This will automatically insert a bullet and include your signature. Do not edit the article's talk page, just click the button below.

To request a reversion of a recent undiscussed move: Review the guidelines at WP:RMUM of whether a reversion of an undiscussed move qualifies as uncontroversial and if so, edit the Requests to revert undiscussed moves subsection or click the big blue button and insert the following code at the bottom of the list, filling in pages and reason:

{{subst:RMassist|current page title|new title|reason=edit summary for the move}}

Note that in some cases, clerks, such as administrators or page movers may determine that your request for a reversion does not pass the criteria and may move the request to the contested section or open a formal requested move discussion for potentially controversial moves on your behalf.

  • 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 ~~~~. Consider pinging the requester to let them know about the objection.
  • 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. A bot will automatically remove contested requests after 72 hours of inactivity.
Administration needed

If your request requires an administrator. Usually, do so if the page has been fully protected or move protected (see this guide to which moves need administrators).

Request a move requiring an administrator

Technical requests

Uncontroversial technical requests

Requests to revert undiscussed moves

Contested technical requests

  • Simon I Gurieli  Simon II GurieliSimon II Gurieli (currently a redirect instead to Simon III Gurieli) (move · discuss) – Correcting regnal number. There was a prince of the Gurieli family named Simon in the 14th century, and his regnal number, according to the Georgian Soviet Encyclopedia, is Simon I Gurieli. Georgian Wikipedia also uses the same numbering. Therefore, Simon (son of Mamia II Gurieli) should be numbered as Simon II Gurieli, while Simon (son of George V Gurieli) should be numbered as Simon III Gurieli. Gergos10 (talk) 16:14, 15 August 2026 (UTC)
I agree that this change would agree with what is currently in the Georgian Soviet Encyclopedia, but another wiki is not a reliable source. Rayfield's scholarly book 'Edge of Empires', already cited in the article, has this Simon (that is, the one who died in 1672) listed as 'Simon I' on page 439. Which would imply that the page should not be moved. So this move is, in my opinion, not uncontroversial. EdJohnston (talk) 17:13, 15 August 2026 (UTC)
@Gergos10 Need more sources EdJohnston (talk) 17:14, 15 August 2026 (UTC)
and . These sources focus on the Principality of Guria and provide more information about its princes, giving Simon (1606–1672) the regnal number II. Simon (14th century) was a duke (eristavi) before him, and historian Rayfield probably did not include him because he was not an independent prince, or for another reason, as there is not much information about him. Rayfield also gives different years for the reign of Simon (1606–1672), which other historians do not agree with. Gergos10 (talk) 21:51, 15 August 2026 (UTC)
  • Genjo Sanzo  Genjyo SanzoGenjyo Sanzo (currently a redirect instead to Xuanzang) (move · discuss) – "Genjyo Sanzo" is the romanization used in Studio Pierrot's official English-language material for the character (Studio Pierrot) and in Kodansha's official English-language edition of the manga (Kodansha). "Genjo Sanzo" is an alternative romanization, but "Genjyo Sanzo" is the form used by the anime's official English-language material and the current English-language publisher. M.A.LasTroniN910 (talk) 19:36, 15 August 2026 (UTC)
    It looks mixed whether the alternative romanisation is used, I think the MOS:JA compliant title should be used until it's determined that there's more sources leaning towards Genjyo Sanzo. Tenshi! (Talk page) 21:13, 15 August 2026 (UTC)
    I think Genjyo Sanzo is a reasonable title based on the source evidence. It is not only used by fan sites. The spelling appears in tokyopop's archived official Saiyuki character guide, Studio Pierrot's official English website, and a number of independent reviews and anime news sites. For example, Eduardo M. Chavez's 2004 AnimeOnDVD review repeatedly uses Genjyo Sanzo, and Sandra Dozier's DVD Verdict review also uses the same spelling. Crunchyroll and other English-language anime news sources have used it as well. TOKYOPOPStudio PierrotAnimeOnDVDDVD Verdict[Anime UK News[Anime Superhero NewsDVD Verdict[Crunchyroll NewsThe Outerhaven These sources show that Genjyo Sanzo has longstanding use in published English-language material, including publisher, official anime, critical, and news sources. For that reason, I think it should be retained as the article title. M.A.LasTroniN910t@lk 23:18, 15 August 2026 (UTC)

M.A.LasTroniN910t@lk 22:32, 15 August 2026 (UTC)

Administrator needed

Related Articles

Timelines

Top Qs

Fact Checks