Talk:Arm (disambiguation)
![]() | This disambiguation page does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||
|
ARM
[edit]Any ideas where ARM should redirect to? --Bxj (talk) 06:03, 25 February 2011 (UTC)
Here: — Preceding unsigned comment added by Some Gadget Geek (talk • contribs) 00:35, 24 March 2015 (UTC)
Requested move 24 March 2015
[edit]- The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.
The result of the move request was: No move. Cúchullain t/c 16:32, 1 April 2015 (UTC)
Arm (disambiguation) → ARM – Arm has wider contexts when used as an acronym. When used as a word, it almost always refers to our upper limbs. <<< SOME GADGET GEEK >>> (talk) 00:35, 24 March 2015 (UTC)
- Oppose. This page serves as a disambiguation for both arm and ARM. It is better to have the acronyms listed under arm than have everything listed under ARM. And the body part is already the primary topic for arm; I'm not sure what the nominator is trying to improve. kennethaw88 • talk 21:47, 24 March 2015 (UTC)
- Oppose. No justification for moving to all upper-case. --David Biddulph (talk) 22:30, 24 March 2015 (UTC)
- Oppose. No need for a move at all. -- Necrothesp (talk) 15:15, 25 March 2015 (UTC)
- Oppose per WP:DABNAME; ironically, this page is the example used at WP:DABNAME. Steel1943 (talk) 20:58, 26 March 2015 (UTC)
- The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.
merge of arm and ARM
[edit]From my 2024 comments in Wikipedia talk:Disambiguation/Archive 57#Capitalization of a disambiguation page title with both all-caps and lowercase senses:
Mediawiki forces us to combine arm and Arm, but it doesn't force us to combine Arm and ARM. If we have:
- 9 known meanings of Arm,
- 3 known meanings of both Arm/arm and ARM not because of laziness in typing (company, software, language),
- 34 known meanings of ARM
...it's neither trivial nor obvious to assume these need to be one list of 46 items.
I doubt that we actually analyzed the outcomes of navigating this merged list compared to having them split.
Do we see distinct usage patterns based on capitalization here? (For example, are most uses of "ARM" actually pronounced the same as "arm", or does the average reader pronounce them as "ey-are-em" and in turn do they consider these a different word?)
Would it make navigation more efficient if the reader didn't have to wade through both lists together?
One thing that wasn't said before is that there's a distinctly different disambiguation experience on desktop and on mobile views. On desktop, the reader sees a table of contents, but also the entirety of the list. On mobile, because there are many sections, the entire list is collapsed by default, so the reader has to tap the section title to expand each small portion. --Joy (talk) 06:17, 23 July 2025 (UTC)