Jump to content

Talk:Morse code

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 2603:6080:4e00:aa8:5126:e872:c9ad:c77b (talk) at 18:04, 6 January 2022 (Semi-protected edit request on 6 January 2022: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Template:Vital article

Former good article nomineeMorse code was a Language and literature good articles nominee, but did not meet the good article criteria at the time. There may be suggestions below for improving the article. Once these issues have been addressed, the article can be renominated. Editors may also seek a reassessment of the decision if they believe there was a mistake.
Article milestones
DateProcessResult
June 19, 2012Good article nomineeNot listed

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)[reply]

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)[reply]

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)[reply]

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)[reply]
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)[reply]

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)[reply]