Talk:2022–23 NHL transactions
 | This article is rated List-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||
| ||||||||
Three Sharks moves
[edit]The sharks have signed Aaron Dell, Andrew Aggozzion, and C.J. Suess: https://www.nhl.com/sharks/news/san-jose-sharks-sign-forward-andrew-agozzino/c-334971406, https://www.nhl.com/sharks/news/sharks-sign-forward-cj-suess/c-334969392, https://www.nhl.com/sharks/news/sharks-sign-goaltender-aaron-dell/c-334971414 Nuggets87 (talk) 19:30, 14 July 2022 (UTC)
Panthers signed del zotto
[edit]They may have mixed del zotto and tierrney up Joshthepanthersfan (talk) 19:27, 17 July 2022 (UTC)
No, the panthers signed both of them Hotpotato1234567890 (talk) 03:38, 18 July 2022 (UTC)
Indenting with emsp
[edit]@Uncleben85: Greetings! Regarding this revert...the use of emsp;s here is not a good way to make the text more readable, as it results in poor word wrapping on narrow screens. (More than half of English Wikipedia traffic is now on mobile phones.) For example, depending on the width of the screen, "or 4th-round pick in 2026" might put "2026" on the next line, not indented (so it's unclear it goes with the "or" clause"), put "or" on a line by itself with the remainder on the next one or two lines, or anything in between. Also consider people who are using text-to-speech systems, which will not read whitespace out loud. My recommendation would be to make these clauses normal sentences that wrap like prose and use standard English punctuation to clarify, or use bulleted lists (which TTS could read aloud). -- Beland (talk) 00:31, 11 December 2024 (UTC)
- I used the format that you previously suggested –uncleben85 (talk) 12:01, 11 December 2024 (UTC)
- Next up will be removing the title span. But that's a larger project that I will get to when I can! –uncleben85 (talk) 14:25, 11 December 2024 (UTC)
- The use of {{in5}} creates the same problems as emsp. For example, in a narrow window, the September entry for Nils Lundkvist has a cell that reads like this:
- Next up will be removing the title span. But that's a larger project that I will get to when I can! –uncleben85 (talk) 14:25, 11 December 2024 (UTC)
conditional 1st-round
pick in 2023
or 1st-round
pick in 2024
conditional 3rd-round
pick in 2025
or 4th-round
pick in 2025
- -- Beland (talk) 15:57, 11 December 2024 (UTC)
- I get the TTS and accessibility concern, so if {{in5}} fixes that, I'm all onboard! My concern is that just leaving it to wrap like prose makes it hard to discern and differentiate the conditional picks from just another piece offered in the trade. That is to say, where this
- -- Beland (talk) 15:57, 11 December 2024 (UTC)
conditional 1st-round pick in 2023
or 1st-round pick in 2024
conditional 3rd-round pick in 2025
or 4th-round pick in 2025
- stands out, something like this,
conditional 1st-round pick in 2023 or 1st-round pick in 2024 conditional 3rd-round pick in 2025 or 4th-round pick in 2025
- the blocking makes it hard to read if scanning and you miss the hanging "or". It simply looks like 4 entries.
- I do wonder if a bulleted list, as you also suggested, is worth experimenting with..! –uncleben85 (talk) 20:48, 11 December 2024 (UTC)
- The problem is that most readers do not see the relatively nice wrapping in your first example, they see something more like what I pasted. Try looking at the article on a phone, or narrow your browser window to phone width, and you can see for yourself. -- Beland (talk) 22:00, 11 December 2024 (UTC)
- I understand what you're saying and not opposing changing it, but the proposed solution of prose wrap has the problem I described regardless of mobile, desktop, or shrunken window.
- What about?
- The problem is that most readers do not see the relatively nice wrapping in your first example, they see something more like what I pasted. Try looking at the article on a phone, or narrow your browser window to phone width, and you can see for yourself. -- Beland (talk) 22:00, 11 December 2024 (UTC)
conditional 1st-round pick in 2023
- or 1st-round pick in 2024
conditional 3rd-round pick in 2025
- or 4th-round pick in 2025
- or 4th-round pick in 2026
Tabled example:
| March 1, 2023 | To Arizona Coyotes conditional 1st-round pick in 2023
conditional OTT 1st-round pick in 2024
2nd-round pick in 2026 |
To Ottawa Senators Jakob Chychrun |
- –uncleben85 (talk) 15:02, 13 December 2024 (UTC)
- That wraps a lot more cleanly. Though "1st-round pick in 2023" is an option just like "1st-round pick in 2024", right? It might make more sense if they both had bullet points, but this example only the second one does? Either way is fine with me if it makes sense to you. -- Beland (talk) 20:56, 13 December 2024 (UTC)
- Yes, exactly, both the lede line and the bulleted point would be options on that pick. We could do something like below. @The Kip: would love to get your opinion on this too.–uncleben85 (talk) 15:55, 17 December 2024 (UTC)
- That looks much cleaner to me. -- Beland (talk) 02:27, 18 December 2024 (UTC)
- Yes, exactly, both the lede line and the bulleted point would be options on that pick. We could do something like below. @The Kip: would love to get your opinion on this too.–uncleben85 (talk) 15:55, 17 December 2024 (UTC)
- That wraps a lot more cleanly. Though "1st-round pick in 2023" is an option just like "1st-round pick in 2024", right? It might make more sense if they both had bullet points, but this example only the second one does? Either way is fine with me if it makes sense to you. -- Beland (talk) 20:56, 13 December 2024 (UTC)
- –uncleben85 (talk) 15:02, 13 December 2024 (UTC)
| March 1, 2023 | To Arizona Coyotes conditional pick[efn1]
conditional[efn2]
2nd-round pick in 2026 |
To Ottawa Senators Jakob Chychrun |