Jump to content

英文维基 | 中文维基 | 日文维基 | 草榴社区

Talk:New York–style pizza

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
(Redirected from Talk:New York-style pizza)

Requested move 3 May 2023

[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 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. (closed by non-admin page mover) SkyWarrior 00:19, 11 May 2023 (UTC)[reply]


MOS:SUFFIXDASH. The New York-style pizzaNew York–style pizza move was rejected ~4 years ago but it seems like the Manual of Style has been solidified since then. The hyphen in the compound modifier becomes an en dash because of the space in "New York" and other locations. As far as I can tell it's completely analogous to the example given in the Manual of Style Turks and Caicos–based company. CWenger (^@) 23:31, 3 May 2023 (UTC)[reply]

Spacebyte (talk) 17:04, 4 May 2023 (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.

Move

[edit]

The above requested move didn't seem to gain much traction, and I missed it. It looks wrong, and I don't see any analysis of what the reliable sources use. I don't recall ever seeing an en dash like this used to describe pizza styles. I don't really care if the style guide suggests en dashes for similar scenarios (note that it doesn't mention "xyz-style"); what matters is if this is a good way of writing these terms. Do others use this style for these terms? ɱ (talk) 00:25, 11 May 2023 (UTC)[reply]

As far as I know, Wikipedia follows its own style guide on matters like this one, rather than looking to sources for guidance. —⁠ ⁠BarrelProof (talk) 05:14, 11 May 2023 (UTC)[reply]