Talk:Always In Between

On 20 November 2022, it was proposed that this article be moved from Always in Between to Always In Between. The result of the discussion was moved.

Requested move 4 July 2018

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: moved as requested per the discussion below and the cited interpretation of the MOS. Dekimasuよ! 18:46, 19 July 2018 (UTC)[reply]

Always in Between Tour → Always In Between Tour

– "in" isn't a preposition here. Unreal7 (talk) 21:22, 4 July 2018 (UTC)[reply]

Support: It's a phrasal particle; "in between" is a unit, like "look up" something in a dictionary. This is more common with phrasal verbs than with a compound adjective [in this particular title] like "in between" (though that phrase can also be, and obviously originated as, a compound preposition, albeit a rather redundant colloquial one: "I left my keys in between the stack of books and the laundry"). In this title, "in between", normally a compound preposition, is clearly serving as a compound adjective describing a state, like "tired" or "hungry"; you can substitute them cleanly. If you substitute just a preposition that can't also act as an adjective, you get incomplete gibberish ("Always with", "Always Toward"). If you substitute an actual prepositional phrase – a preposition+NP construction – you get a very different kind of statement, not describing a state, but a physical position ("Always in Toledo", "Always on Your Face", "Always Alongside Your Ship") or a metaphoric extension thereof ("Always on Top of the World", "Always in the Doldrums").
All that said, it produces inconsistent-looking output, and we should probably consider revising MOS:TITLES to say to lowercase any short preposition-word even when it's not technically used as one, because the average RfC respondent isn't a grammarian, and cases like this sometimes turn into grotesque disputes. Various news publishers do the same thing for consistency over niggling. It's not really necessary that phrasal repurposing of prepositions in titles be upper-cased. What's wrong with a song title like "Look up My Love in Your Encyclopedia" (other than probably indicating an awful song)?
— SMcCandlish ☏ ¢ 😼 05:27, 5 July 2018 (UTC)[reply]
Comment: I note that the second would reverse a very recent move 15:54, 3 July 2018‎ KHBritish (talk | contribs | block)‎ . . (53 bytes) (+53)‎ . . (KHBritish moved page Always In Between Tour to Always in Between Tour) (thank) (Tag: New redirect) Andrewa (talk) 23:08, 12 July 2018 (UTC)[reply]
Oppose. I understand it's not used a preposition here, but I think having it as a capital I is just going to look inconsistent with similar titles and is going to inspire moves and re-capitalisation edits galore. Ss112 15:25, 14 July 2018 (UTC)[reply]
Support. Since in is not a preposition in this title, it must be capitalized as per MOS:TITLECAPS. Darkday (talk) 18:27, 16 July 2018 (UTC)[reply]

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.

Requested move 20 November 2022

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 after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: moved. (non-admin closure) ^Clyde!_Franklin! 21:58, 27 November 2022 (UTC)[reply]

Always in Between → Always In Between – "In" is not a preposition here. Unreal7 (talk) 20:56, 20 November 2022 (UTC)[reply]

Support per nom. Shwcz (talk) 22:16, 20 November 2022 (UTC)[reply]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.