Wikipedia:Requested moves/Technical requests
Appearance
If you are unable to complete a move for technical reasons, you can request technical help 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 "The/This page could not be moved, for the following reason:..."
![]() | If you are here because you want an admin to approve of your new article or your proposed page move, you are in the wrong place.
|
- To list a technical request: Uncontroversial technical requests subsection and insert the following code at the bottom of the list, filling in pages and reason:
This will automatically insert a bullet and include your signature. Please do not edit the article's talk page.{{subst:RMassist|current page title|new title|reason=edit summary for the move}}
the - 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.
Technical requests
Uncontroversial technical requests
Requests to revert undiscussed moves
- University Center / Baltimore Street station (currently a redirect to Baltimore Arena station) → Baltimore Arena station (move · discuss) – The station is now called Baltimore Arena and not University Center/Baltimore Street. The article was previously moved back from this new name two years ago according to WP:COMMONNAME per the user who did so, but I'd argue that WP:COMMONNAME now favors this move back to the new and current name, which people would have had time to get used to. OrdinaryScarlett (talk) 17:30, 23 January 2024 (UTC)
- Allegro Non Troppo (currently a redirect to Allegro non troppo) → Allegro non troppo (move) – The film's title is not capitalized except for the 1st letter, neither on the poster nor on IMDB. JackkBrown (talk) 14:33, 24 January 2024 (UTC)
Contested technical requests
- Friend of a Friend (The Smile song) → Friend of a Friend (the Smile song) (currently a redirect back to Friend of a Friend (The Smile song)) (move · discuss) – lowercase "the" per WP:BAND Popcornfud (talk) 11:29, 24 January 2024 (UTC)
- The policy cited by the requester is about a band's notability, not how to capitalize a name. I'm pretty sure the current title of the song article matches spelling/capitalization standards. ---DOOMSDAYER520 (TALK|CONTRIBS) 14:46, 24 January 2024 (UTC)
- Characters of The Legend of Zelda: Ocarina of Time → Characters in The Legend of Zelda: Ocarina of Time (currently a redirect instead to List of The Legend of Zelda characters) (move · discuss) – Better wording Cukie Gherkin (talk) 19:40, 21 January 2024 (UTC)
- Controversial, per above. 162 etc. (talk) 22:00, 21 January 2024 (UTC)
- @Cukie Gherkin would you like to bundle this into the discussion you opened at Talk:Characters_of_the_Legend_of_Zelda_series#Requested_move_21_January_2024 since the argument(s) for the move would likely be largely the same? – robertsky (talk) 23:57, 21 January 2024 (UTC)
- This also seems to be at cross purposes to the other move, which is the capitalize The in the work title, but leave it at "of" instead of "in". To be WP:CONSISTENT, they should be at titles like List of The Legend of Zelda characters and in this case List of The Legend of Zelda: Ocarina of Time characters. — SMcCandlish ☏ ¢ 😼 02:31, 22 January 2024 (UTC)
- It depends on the structure; there are a number of "lists" that are not list-class, like Characters of the Yakuza series, with the basis being whether there is coverage that goes beyond simply listing the characters. Whether it should or should not be at the list, it definitely should not be named "Characters of The Legend of Zelda: Ocarina of Time". - Cukie Gherkin (talk) 05:52, 22 January 2024 (UTC)
- A list article is allowed to have prose at the top... Indeed a FL-class list almost invariably does. It's still basically a list in essence though. That one you mention should be titled "List of Yakuza characters" which solved many issues including removing any need to say "series" at the end and also removing the awkward "Characters of..." construct. — Amakuru (talk) 19:06, 22 January 2024 (UTC)
- It depends on the structure; there are a number of "lists" that are not list-class, like Characters of the Yakuza series, with the basis being whether there is coverage that goes beyond simply listing the characters. Whether it should or should not be at the list, it definitely should not be named "Characters of The Legend of Zelda: Ocarina of Time". - Cukie Gherkin (talk) 05:52, 22 January 2024 (UTC)
- Controversial, per above. 162 etc. (talk) 22:00, 21 January 2024 (UTC)
- 'Abd al-Hamīd ibn Turk (currently a redirect to Ibn Turk) → Ibn Turk (move · discuss) – Make shorter (WP:CONCISE, WP:PRECISE) Aintabli (talk) 19:09, 19 January 2024 (UTC)
- It may be more concise and precise, but is it the WP:COMMONNAME? Some more evidence is required methinks. — Amakuru (talk) 12:01, 21 January 2024 (UTC)
- Ƒ/8 and be there (currently a redirect to F/8 and be there) → F/8 and be there (move · discuss) – Destination for move is a redirect (with edits) to the original. Requesting a swap of destination (F/8 and be there) be the article, with old article Ƒ/8 and be there be a redirect to the new destination. The original article, with 'hooked Ƒ', even when lowercased with DISPLAYTITLE, is merely a stylistic decoration (implying or looking like a mathematical/formula "function" 'f'). The photographic notation "f/8", "F8", etc., is read as 'eff-eight', and the 'f' is just shorthand for "focal length". It's often displayed as a script-f ('𝑓', Unicode letter U+1D453, "Mathematical small f"), but that's just a stylistic display, equivalent to a LaTeX/math font for 'f'. The article uses 'Ƒ' (Unicode U+0191, "Latin Capital Letter F with Hook"), and lowercases it with 'ƒ' (U+0192, "Latin Small Letter F with Hook"). Additionally, at least two screen readers don't actually read the 'f with hook'. It's typographically, syntactically, and accessibility-wise, simply wrong. — sbb (talk) 22:57, 19 January 2024 (UTC)
- Shouldn't the title then be 𝑓/8 and be there, with the commonly-used letter (U+1D453)? 162 etc. (talk) 23:47, 19 January 2024 (UTC)
- I don't suggest that. While '𝑓' is stylistically nice, it's just style. The 'f'/'𝑓'/whatever is really just 'f' for "focal length". Compare to f-number. Most articles, blogs, etc., don't even bother with stylizing it anymore. Primarily I assume because it's just that: style. Several lens manufacturers use "F4" or whatever (capitalizing, not using a slash). I think that Wikipedia should try to specifically _reduce_ the emphasis on sort of "branding style" (c.f., "KoЯn", "Se7ven", etc.), and just go with the simplest lowest-common-denominator, which is just "f/8 and be there". Which is exactly what 99.9% of people would type if trying to convey that. — sbb (talk) 00:17, 20 January 2024 (UTC)
- Adding to my previous comment, without DISPLAYSTYLE "correcting" the article title, "F/8..." is just as correct as "f/8...", whereas with '𝑓', there's no upper-case variant for it. It's only written as script-f because most historical typesetting used serif fonts, and it's referred to as a variable shorthand for 'focal length'. We don't call the denominator, which is N = f/D, ("8", in this case) '𝒩' (U+1D4A9, "Mathematical Script Capital N") because italic N suffices where N (
{{mvar|N}}
) isn't typographically available. Similarly with '𝒟' (U+1D49F, "Mathematical Script Capital D"). Let's not over- or misuse Unicode characters when we don't need to. Especially for article titles. — sbb (talk) 00:35, 20 January 2024 (UTC) - Sorry for 3rd reply to you: also, at least testing with Apple (macOS, iOS) Voiceover, the '𝑓' you suggest isn't read by the screen reader. It just says "[tiny gap] /8 and be there ...". So from an accessibility standpoint, '𝑓' doesn't improve the situation at all. — sbb (talk) 01:02, 20 January 2024 (UTC)
- Shouldn't the title then be 𝑓/8 and be there, with the commonly-used letter (U+1D453)? 162 etc. (talk) 23:47, 19 January 2024 (UTC)
- Cruise Terminal → Cruise terminal (currently a redirect instead to Maritime passenger terminal) (move · discuss) – Move to title with sentence case. —TechnoSquirrel69 (sigh) 04:47, 21 January 2024 (UTC)
- This doesn't seem right. The cruise terminal with lowercase is a primary redirect to passenger terminal (maritime) which seems caorrect. Perhaps Cruise Terminal should also redirect, rather than disambiguation against the obscure light rail station, but either way the page should not be moved as specified. — Amakuru (talk) 08:22, 21 January 2024 (UTC)
- Atanasio Monserrate → Babush Monserrate (currently a redirect back to Atanasio Monserrate) (move · discuss) – WP: COMMONNAME; couldn't move the page since target title page already exists Rejoy2003(talk) 16:24, 22 January 2024 (UTC)
- HMS Sheffield (F96) (currently a redirect to Chilean frigate Almirante Williams (FF-19)) → Almirante Williams (FF-19) (currently a redirect instead to Chilean frigate Almirante Williams (FF-19)) (move · discuss) – This is a warship formerly known as HMS Sheffield, but acquired by the Chilean Navy in 2003 and renamed Almirante Williams. Almirante Williams is her current name and the one she has had during most of her career. This edit had been done, but an user undid in 2018 it for absolutely no reason. Therefore, I'm unable to move the page because the target page already exists. Af1391 (talk) 02:31, 23 January 2024 (UTC)
- HMS Grafton (F80) → Almirante Lynch (FF-07) (currently a redirect back to HMS Grafton (F80)) (move · discuss) – This is a warship formerly known as HMS Grafton, but acquired by the Chilean Navy in 2007 and renamed Almirante Lynch. Almirante Lynch is her current name. I'm unable to move the page because the target page already exists as a redirect. Af1391 (talk) 02:48, 23 January 2024 (UTC)
- HMS Norfolk (F230) → Almirante Cochrane (FF-05) (currently a redirect back to HMS Norfolk (F230)) (move · discuss) – This is a warship formerly known as HMS Norfolk, but acquired by the Chilean Navy in 2006 and renamed Almirante Cochrane. Almirante Cochrane is her current name. I'm unable to move the page because the target page already exists as a redirect. Af1391 (talk) 02:48, 23 January 2024 (UTC)
- HMS Marlborough (F233) → Almirante Condell (FF-06) (currently a redirect back to HMS Marlborough (F233)) (move · discuss) – This is a warship formerly known as HMS Marlborough, but acquired by the Chilean Navy in 2008 and renamed Almirante Condell. Almirante Condell is her current name. I'm unable to move the page because the target page already exists as a redirect. Af1391 (talk) 02:48, 23 January 2024 (UTC)
- @Af1391: This was a reverted undiscussed move, so needs a full RM. I suggest an RM that discusses all these pages at once, see WP:RMPM for instructions. Polyamorph (talk) 08:38, 23 January 2024 (UTC)
Administrator needed
- Amos Nondi (footballer) is invalid. Must create Amos Nondi (footballer) before requesting that it be moved to Amos Nondi.– unnecessary dab, recreation of article salted in 2017 following Wikipedia:Articles for deletion/Amos Nondi. Seven years on, his pro career has moved on, so the article is ineligible for db-G4. Wikishovel (talk) 09:18, 23 January 2024 (UTC)
- @Wikishovel: I'd send it to Draft:Amos Nondi (2) (since there is a Draft:Amos Nondi). The creator of this page, Das osmnezz, is experienced enough that he should know not to evade WP:SALTs by adding unnecessary disambiguation to the title. SilverLocust 💬 22:32, 23 January 2024 (UTC)
- And create a textbook WP:SAMETYPEFORK? I would support moving to Amos Nondi and merging the draft, but would object to Draft:Amos Nondi (2). HouseBlaster (talk · he/him) 02:32, 24 January 2024 (UTC)
- @HouseBlaster: The content fork already exists, since an article and a draft of that article are the same type of content. See WP:CFORK#Temporary subpages. (The section title remains unchanged from before the 2013 creation of draftspace, but it includes drafts.) Draft: ... (2) is a fairly common title to use when an article ought to be draftified but there is an existing draft (either by another user or by a COI editor per WP:DRAFTOBJECT). SilverLocust 💬 06:31, 24 January 2024 (UTC)
- And create a textbook WP:SAMETYPEFORK? I would support moving to Amos Nondi and merging the draft, but would object to Draft:Amos Nondi (2). HouseBlaster (talk · he/him) 02:32, 24 January 2024 (UTC)
- @Wikishovel: I'd send it to Draft:Amos Nondi (2) (since there is a Draft:Amos Nondi). The creator of this page, Das osmnezz, is experienced enough that he should know not to evade WP:SALTs by adding unnecessary disambiguation to the title. SilverLocust 💬 22:32, 23 January 2024 (UTC)
- Template:LinkCatIfExists (currently a redirect to Template:Category link if exists) → Template:Category link if exists (move · discuss) – Expand template name per WP:TPN (
Template names are easiest to remember if they follow standard English spelling, spacing, and capitalization
). HouseBlaster (talk · he/him) 02:32, 24 January 2024 (UTC) - Template:LinkCatIfExists2 (currently a redirect to Template:Category link if exists 2) → Template:Category link if exists 2 (move · discuss) – Expand template name per WP:TPN (
Template names are easiest to remember if they follow standard English spelling, spacing, and capitalization
). HouseBlaster (talk · he/him) 02:32, 24 January 2024 (UTC)