Talk:Morse code

Little mistake at https://en.wikipedia.org/wiki/Morse_code#Alternative_display_of_common_characters_in_International_Morse_code?

Hello, I think there is one little mistake in this (apart from that in my opinion fantastic, clearly arranged and very helpful) Morse code tree, isn't it? '-.--.' leads to 'Ĥ' and '-.--.-' leads to '(' and ')'. But I think '-.--.' means '(' and '-.--.-' means ')'. At https://commons.wikimedia.org/wiki/Morse_code I found '----' media:CH, Ĥ, Š Morse Code.oga. What do you think? But I don't know how to change it. Thanks in advance for your help. Yours, --2A02:810B:8C3F:EA08:70A3:2ED0:4E9B:732F (talk) 23:25, 1 June 2021 (UTC)

I dug into this a little. It looks like it's not technically incorrect but I agree the diagram should be changed.

Ĥ comes from Esperanto, and the chart on Esperanto Morse Code article says either -•--• or ---- can be used for Ĥ. Another random web page[1] also lists both but notes -•--• is only used sometimes because it conflicts with the bracket '('. Esperanto Wikipedia also points out that Esperanto Radio Amateurs often don't even use any of the extended characters, and use a transcription (Zamenhof method or H-system) instead, where Ĥ is written/sent as "hh".

So, Ĥ is sometimes sent as -•--• but it's only found in a constructed language, where it appears to be the least popular encoding out of three alternatives. —Pengo 23:17, 9 September 2021 (UTC)

Separating extensions from standardized codes

Sourcing for non-latin extensions seems weak, and there is no apparent standard as I understand. In the table of codes we list numerous codes that are not part of the International Morris Code standard, some with the footnote "The character or symbol encoding is not in either ITU-R M.1172 or ITU-R M.1677-1 .", and none referenced. The result is a large table that is confusing and unverifiable.

I propose separating the codes actually in the standard from the rest, and those all need some reference or be removed; there is no way to tell if they are incorrect, as demonstrated by the issue @Pengo points out with the characters ż ⇄ ź Strangerpete (talk) 12:57, 29 December 2021 (UTC)

While you are about it, I'm in favour of removing all the audio files from the table. These have been a long standing issue making the page slow to load. The reader is not really getting any more information than already in the visual renderings. It's all just more dits and dahs after all. The file of the complete alphabet is enough. SpinningSpark 17:17, 29 December 2021 (UTC)

I agree with that as well, my only concern would be whether it affects vision impaired users, but I really don't know. Strangerpete (talk) 22:53, 1 January 2022 (UTC)

@Spinningspark I did a test with my browser (Opera/Chrome) and for me, none of the audio was actually loaded until played. Perhaps the audio player itself is part of the issue? But much of the loaded page size seems to come from all the images, totaling 724kB for the whole page, in particular the VFR map is 166kB alone. I will also admit the audio files overall have more views than I was expecting (1 year- A: 3566, X: 1200) -- do page statistics only count a person visiting the 'File:xxx' page, or also when someone clicks 'play'? Strangerpete (talk) 15:07, 8 January 2022 (UTC)

All those unverifiable codes should be removed from the table. This article is highly likely spreading misinformation.220.100.57.58 (talk) 04:57, 30 April 2023 (UTC)

Morse code is a living communication system with more in common with spoken languages than with any data protocol. The "unverifiable" additions are largely from other language cultures, and often do have references or they can be found readily, e.g. in other language Wikipedia Morse code articles. A column identifying which codes exist in which standard would be good, but the suggestion of deleting every addition beyond the published standards is absurd. It would be like if Wikipedia only allowed article text to contain words found in the first edition of Webster's Dictionary from 1828. —Pengo 04:20, 11 May 2024 (UTC)

Semi-protected edit request on 6 January 2022

the line for "K" in the table is malformatted, and needs to be fixed 2603:6080:4E00:AA8:5126:E872:C9AD:C77B (talk) 18:04, 6 January 2022 (UTC)

 Not done for now: It's unclear what is malformatted in that line of the table. Could you please specify what should be changed in the form "please change X to Y"? — Preceding unsigned comment added by Fiwec81618 (talk • contribs) 19:08, 6 January 2022 (UTC)

"Non-Latin" extensions

These are (mostly) not "non-Latin", they are perfectly normal latin characters not used in English. Is this really what they are called in the wider world? Bagunceiro (talk) 17:27, 31 July 2022 (UTC)

I have changed to read "Diacritics and non-Latin extensions". I don't speak Morse, so would a more expert editor please review my change, please? --𝕁𝕄𝔽 (talk) 14:39, 21 January 2023 (UTC)

Semi-protected edit request on 15 September 2023

Suggest to change ‘a through z’ to ‘a to z’. Using ‘through’ this way is not standard/traditional English (this usage is only found in recent American texts and is not widely understood or accepted outside the US). In standard English, using ’through’ in this sense is unnecessary and wrong because the original ‘to’ performs exactly the same function. 2001:E68:5404:44CB:88FD:BCB7:5713:6B54 (talk) 16:21, 15 September 2023 (UTC)

I agree and have changed. I don't believe that this is a MOS:ENGVAR issue. --𝕁𝕄𝔽 (talk) 21:46, 15 September 2023 (UTC)

Semi-protected edit request on 2 October 2023

I would like to request a change of the word "identifcation" to "identification" in both occurrences in the "Aviation" section. Both Wiktionary and web searches suggest that the former is a misspelling, not some technical term that could be mistaken for a misspelling, like "ordnance". 166.181.80.186 (talk) 03:09, 2 October 2023 (UTC)

 Done Tollens (talk) 03:44, 2 October 2023 (UTC)

Semi-protected edit request on 1 June 2024

In the part 'speed in words per minute', they state that the speed for a dit might be 50 milliseconds. I don't know how long it would realistically be, but 1/200th of a second seems really short. It would mean that you could type 100 e's in one second, which seems a lot to me. 2A02:1810:4F27:3A00:5476:75CA:86EB:1B2C (talk) 21:04, 1 June 2024 (UTC)

50ms is 1/20th of a second. Hyphenation Expert (talk) 22:28, 1 June 2024 (UTC)

50 ms "dits" is 24 WPM Morse code, fast but not exceedingly so--it's a professional speed and code faster than that is heard on the amateur bands now. The FCC exam for the First Class Radiotelegraph license required 25 WPM. Dkazdan (talk) 23:13, 1 July 2024 (UTC)

inverted question mark missing from table

The inverted question mark ¿ is missing from the table; it has encoding ..-.- according to the tree diagram. But I don't care to fix it. Jurjen B (talk) 13:50, 15 July 2024 (UTC)

I meant: I don't _dare_ to fix it. Jurjen B (talk) 13:51, 15 July 2024 (UTC)

It is also the prosign for "please repeat" Jurjen B (talk) 13:53, 15 July 2024 (UTC)

I was wrong about the code: it is ..--.-

A dash got lost somewhere Jurjen B (talk) 13:57, 15 July 2024 (UTC)

Missing AR Prosign

The AR (EOM - End of Message) is missing from the Morse code table 181.105.151.204 (talk) 18:57, 13 September 2024 (UTC)

"In addition, applications are now available for mobile phones that enable short messages to be input in Morse Code"

This line doesn't make sense, the citation just talks about Nokia patenting the ability to do that. Source? Dany0 (talk) 17:18, 14 November 2024 (UTC)

and even if true, it's WP:TRIVIA so I will delete. 𝕁𝕄𝔽 (talk) 21:13, 14 November 2024 (UTC)

and would be contrary to WP:NOTDB if I could find it? So I haven't deleted it but I have deleted Some Nokia mobile phones offer an option to alert the user of an incoming text message with the Morse tone "  ▄ ▄ ▄   ▄▄▄ ▄▄▄   ▄ ▄ ▄ ", which is just as trivial. --𝕁𝕄𝔽 (talk) 21:40, 14 November 2024 (UTC)