Misplaced Pages

Talk:Morse code: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 15:01, 23 April 2005 editOmegatron (talk | contribs)Administrators35,798 edits Formatting← Previous edit Latest revision as of 19:51, 10 January 2025 edit undoRemsense (talk | contribs)Extended confirmed users, Page movers, New page reviewers, Template editors62,140 edits Accented letters: ReplyTag: Reply 
Line 1: Line 1:
{{not a forum|Morse code}}
==Addition of text from the code article==
{{ArticleHistory
From the ] article:
|action1=GAN
|action1date=06:10, 19 June 2012
|action1link=Talk:Morse code/GA1
|action1result=not listed
|action1oldid=496916709
|currentstatus=FGAN
|topic=Language and literature
}}
{{WikiProject banner shell|class=B|vital=yes|1=
{{WikiProject Amateur radio |importance=High}}
{{WikiProject Writing systems |importance=Mid}}
{{WikiProject Disability }}
{{WikiProject Telecommunications |importance=Low}}
}}


{{User:MiszaBot/config
:In the days when Morse code was widely used, elaborate commercial codes that encoded complete phrases into single words (five-letter groups) were developed, so that telegraphers became conversant with such "words" as BYOXO ("Are you trying to crawl out of it?"), LIOUY ("Why do you not answer my question?"), and AYYLU ("Not clearly coded, repeat more clearly."). The purpose of these codes was to save on cable costs.
|archiveheader = {{aan}}
|maxarchivesize = 100K
|counter = 5
|minthreadsleft = 10
|minthreadstoarchive = 2
|algo = old(365d)
|archive = Talk:Morse code/Archive %(counter)d}}
{{Archivebox|auto=yes|age=1|units=year|bot=Lowercase sigmabot III}}
__TOC__


== Little mistake at https://en.wikipedia.org/Morse_code#Alternative_display_of_common_characters_in_International_Morse_code? ==
Should this be added to the ] article?


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/Morse_code I found '----' ]. What do you think? But I don't know how to change it. Thanks in advance for your help. Yours, --] (]) 23:25, 1 June 2021 (UTC)
----
Probably, but I also put it back into ]; it was a good example of
the data compression use that wasn't otherwise well covered there; I also
gave it a slightly better introduction. --LDC
----
==International morse code different from original Morse code==
This article needs to take into account that the international morse code that is used today is not the same as the telegraphic system that Samuel F. B. Morse created (which was based on numbers). The story is to be found in William Pierpoint's
. Sorry, I don't have time to write it up right now, maybe later. -ARJ


:I dug into this a little. It looks like it's not technically incorrect but I agree the diagram should be changed.
==American railroad code==
it would be nice to have american railroad code here as a table as well as international code. If I get to it I'll add it


:Ĥ comes from Esperanto, and the chart on says either -•--• or ---- can be used for Ĥ. Another random web page also lists both but notes -•--• is only used sometimes because it conflicts with the bracket '('. Esperanto Misplaced Pages 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".
==Trivia==
Just saw - an anagram of "The Morse code" is "Here comes dots". Well, I found it amusing... -- ] 03:17 17 Jul 2003 (UTC)


: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. —] 23:17, 9 September 2021 (UTC)
==Elimination of CW requirement in amateur radio licensing==
WRTC 2003 eliminated the requirement (made optional) for CW in amateur radio licensing. Did a re-write to incorporate this info, fill in some blanks, and otherwise do some light editing - de NG3K ] 10:44 25 Jul 2003 (UTC)


== Separating extensions from standardized codes ==
==Prosigns and abbreviations==
Also added a bunch of commonly used CW abbreviations. ] 18:02 25 Jul 2003 (UTC)


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.
Clarified the difference between prosigns and abbreviations; modified the taxonomy to correspond to this; other tweaks ] 17:01 26 Jul 2003 (UTC)
----
Common cw abbreviations should just list the most important few here. Maybe abreviations could have their own article just like Q-codes. ] 10:34, 16 Nov 2003 (UTC)
----
Actually, experienced CW operators use abbreviations extensively. Most listed here are quite common and important; could be a separate article, I guess. I would tend to NOT include items that are common abbreviations outside the CW-world however (e.g. QCWA). ] 22:58, 31 Dec 2003 (UTC)
----
..--. is given as the code for the exclamation mark, but from some searching it seems there is no official code for it. It's ---. over radio in the USA and Canada according to note 1 at http://homepages.tesco.net/~a.wadsworth/MBcode.htm - ] 2004-02-20t09:48z
----
Somebody who knows about these things should probably edit the prosigns comments by 'Concerned reader' into the body of the text. Looks like the comments really should have been inserted here in the discussion. --] 14:11, 18 May 2004 (UTC)


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 @] points out with the characters ż ⇄ ź ] (]) 12:57, 29 December 2021 (UTC)
===The prosign SN (VE)===
The prosign SN (...-.) is in the international standard, and is actually used by some HF amateurs, though I concede that we have R and QSL for that. See a to confirm this. ] 16:15, 23 Feb 2004 (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. ]] 17:17, 29 December 2021 (UTC)
==Error codes==
::I agree with that as well, my only concern would be whether it affects vision impaired users, but I really don't know. ] (]) 22:53, 1 January 2022 (UTC)
I hear "e e e" for "error" about 80 percent of the time. The remaining is almost always a string of continuous dits. I think that this article should mention all variants that are in use, and clearly indicate which of them is standardized by the ITU - which is the latter (........). ] 16:15, 23 Feb 2004 (UTC)
::@] 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'? ] (]) 15:07, 8 January 2022 (UTC)
:All those unverifiable codes should be removed from the table. This article is highly likely spreading misinformation.] (]) 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 Misplaced Pages 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 Misplaced Pages only allowed article text to contain words found in the first edition of Webster's Dictionary from 1828. —] 04:20, 11 May 2024 (UTC)


== Semi-protected edit request on 6 January 2022 ==
==Binary==
The article says that Morse code has five different "states" unlike binary, but I think it really does have two: on and off. If we call a 'dit' 1 and a roughly equal amount of silence 0, then SOS could be roughly 101010 111011101110 101010 (10 being a full 'dit', 1110 being a full 'dah')...more zeroes would be a longer pause. Hence, Morse code is a binary system depending on how you look at it...


{{edit semi-protected|Morse code|answered=yes}}
I think maybe comparing it with binary in the article isn't so great an idea because, as I demonstrated, the interpretation is a bit subjective. --] 00:23, 27 Feb 2004 (UTC)
the line for "K" in the table is malformatted, and needs to be fixed ] (]) 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"? <!-- Template:Unsigned --><span class="autosigned" style="font-size:85%;">—&nbsp;Preceding ] comment added by ] (] • ]) 19:08, 6 January 2022 (UTC)</span>
If we take the SOS example, you've got 1 representing a dot, 11 representing a dash, 0 representing the period between taps within a letter, and gaps representing the gaps between the letters -- which uses 3 symbols (0,1,gap). If we turn this fully into bianry by reducing this to just 2 symbols (1 and 0) by replacing the gaps by 0s, we get 10101''00''11101110111''00''101010) - but that still uses 4 states (1=dot, 11=dash, 0=period between taps, 00=period between letters). What you've actually done is to ] Morse code and ''code'' it a second time into binary. You can also represent the music from a violin in binay, but that doesn't mean that violin music ''is'' binary.


== "Non-Latin" extensions ==
==Commat==
Someone changed the "commat" to "commercial at". Is this what the official word is? I didn't see it in any of the news stories surrounding this new character.
] 22:05, Mar 8, 2004 (UTC)


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? ] (]) 17:27, 31 July 2022 (UTC)
This is common usage in standards documents such as ASCII and Unicode, though not very much elsewhere. See for instance . ] 10:15, 9 Mar 2004 (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? --] (]) 14:39, 21 January 2023 (UTC)


== Semi-protected edit request on 15 September 2023 ==


{{edit semi-protected|Morse code|answered=yes}}
== Morse code article space rendering problem ==
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. ] (]) 16:21, 15 September 2023 (UTC)
In the ] article, the american (railroad) morse characters need to render with internal spaces.
:I agree and have changed. I don't believe that this is a ] issue. --] (]) 21:46, 15 September 2023 (UTC)


== Semi-protected edit request on 2 October 2023 ==
The code in place is currently
<code>·&amp;nbsp;&amp;nbsp;&amp;nbsp;· · &amp;dagger;</code>
which is rendering as


{{Edit semi-protected|Morse code|answered=yes}}
·&nbsp;&nbsp;&nbsp;· · &dagger; <del>which has no internal spaces.</del>
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". ] (]) 03:09, 2 October 2023 (UTC)
:{{done}}<!-- Template:ESp --> ] (]) 03:44, 2 October 2023 (UTC)


== Semi-protected edit request on 1 June 2024 ==
Why is the & nbsp ; being ignored? How do I fix it? ] 14:27, 15 Jun 2004 (UTC)
:A quick inspection of the HTML code being received by my browser indicates that the &<tt>nbsp</tt>; characters are being stripped out and replaced with ordinary spaces which are then obviously being conflated together when rendered. Possibly a side-effect of the latest round of code updates which IIRC introduced a HTML-tidying stage ('''which might or might not be the cause''' before someone jumps to the erroneous conclusion that I know whereof I speak: I just guess good sometimes :-). --] | ] 14:44, Jun 15, 2004 (UTC)
::I have '''been bold''' and suggested an alternative. See ]. HTH HAND --] | ] 14:56, Jun 15, 2004 (UTC)
:Arggggh Ick. Blech (Phil used an UNDERSCORE character to indicate the space) Phil, that is TRUELY UGLY. :-) Surely there has to be a better answer? ] 15:08, 15 Jun 2004 (UTC)


{{edit semi-protected|Morse code|answered=y}}
:I hate using HTML, but using pre seems to do what I ''think'' you want:
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. ] (]) 21:04, 1 June 2024 (UTC)
:50ms is 1/20th of a second. ] (]) 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. ] (]) 23:13, 1 July 2024 (UTC)


== inverted question mark missing from table ==
·&nbsp;&nbsp;&nbsp;··&dagger;


The inverted question mark ¿ is missing from the table; it has encoding ..-.- according to the tree diagram.
: Urgh. I feel ''dirty'' now. -- ] | ] 18:13, 15 Jun 2004 (UTC)
But I don't care to fix it. ] (]) 13:50, 15 July 2024 (UTC)


:I meant: I don't _dare_ to fix it. ] (]) 13:51, 15 July 2024 (UTC)
Um, this is a bit off topic, but the HTML "tidying" seems to have broken &lt;small&gt; usage in tables--previously you could make the whole table small with one command, now you'd have to add it to every tr. Compare an old version of ] with the one right after 1.3, with now. Or, as of this moment, the table of companies at ], which I believe used to be all small, but now only the first row is. Anyway, my actual question is, can you point me to info about this 'tidy' feature, and/or places to comment about what it has done to existing articles? ] 19:20, 15 Jun 2004 (UTC)
:It is also the prosign for "please repeat" ] (]) 13:53, 15 July 2024 (UTC)
:I was wrong about the code: it is ..--.-
:A dash got lost somewhere ] (]) 13:57, 15 July 2024 (UTC)


== Missing AR Prosign ==
::Well, PRE worked here, but it doesn't work well in the tables in the code in question...
{| border=1 cellspacing=0 cellpadding=2
| C
| - · - ·
| <pre>
·&nbsp;&nbsp;&nbsp;··&dagger;
</pre>
|}
::since (at least in the monoblock skin) it puts that "pre" box around the stuff and looks "wonky" I really think they need to FIX the HTML Tidyer..... This worked GREAT before. ] 21:52, 15 Jun 2004 (UTC)
:::Turns out this is a in . Works fine if it doesn't come across an &amp;nbsp; inside a &lt;pre&gt; (adjusted the first line). Hope it gets fixed soon. -- ] 13:45, 24 Jun 2004 (UTC)
: '''AHA!!!! ''' So, all we have to do is parse the page and dump any &amp;nbsp; inside pre's anywhere on the page. Then the &amp;nbsp; would render correctly inside the code. Got it. Cool. I'll try. ] 16:53, 25 Jun 2004 (UTC)
::Saddly that appears not to be '''EXACLY''' what we're dealing with since there is no &amp;nbsp; inside a PRE anywhere on that page. Darn. ] 15:48, 27 Jun 2004 (UTC)


The AR (EOM - End of Message) is missing from the ] ] (]) 18:57, 13 September 2024 (UTC)
== Vail not inventor of code ==


== "In addition, applications are now available for mobile phones that enable short messages to be input in Morse Code" ==
in Vail's 1845 pamphlet ], Vail says that the alphabet of ''dots, lines and spaces was created on board the packet Sully by Prof Morse.'' -- I think we should take his word for it. The claim that Vail invented the code was pushed after his death by his daughter Amanda who thought that her father's genius had been eclipsed in the public mind by the figure of Morse who was a Glory Hog. Be that as it may, Vail credits Morse. ] 03:03, 1 Jul 2004 (UTC)


This line doesn't make sense, the citation just talks about Nokia patenting the ability to do that. Source? ] (]) 17:18, 14 November 2024 (UTC)
: Okay, that is probably a more reliable source than Bill Pierpoint's ''The Art & Skill of Radio-Telegraphy''. Still, the alphabetic code that Morse (or Vail) invented, is now known as '''American''' Morse code. The present version of the code (previously known as "Contintental" or "International" Morse code) was made by the German and Austrian state telegraphs in 1852, and further modified by Paris International Telegraph Convention in 1865. (This is all according to Pierpoint's book).


:and even if true, it's ] so I will delete. ] (]) 21:13, 14 November 2024 (UTC)
: It also needs to be pointed out that American Morse code (the "original") did not have only a dot and a dash, but '''four''' different element lengths.
: and would be contrary to ] if I could find it? So I haven't deleted it but I have deleted {{tq|Some ] mobile phones offer an option to alert the user of an incoming text message with the Morse tone "{{morse|dot|dot|dot}}{{morse|dash|dash}}{{morse|dot|dot|dot}}"}}, which is just as trivial. --] (]) 21:40, 14 November 2024 (UTC)


== Accented letters ==
: Sorry for not adding this in myself, but it seems to require quite extensive rewriting. Maybe in a few days if no-one have done it by then. ] 16:29, 1 Jul 2004 (UTC)


I want to talk about the "Accented Letters" that are in this article, as it's all a bit of an unsourced mess.
----
I'm moving to this page a comment that I found in the section on prosigns:


To give some background, the very first ITU standard for Morse code (from 1865) contained the accented letters É, Å, Ä, Ö, Ü, Ñ, and the digraph CH. You can see them on pages 48-49 of this pdf file: https://search.itu.int/history/HistoryDigitalCollectionDocLibrary/4.1.43.fr.200.pdf. That document is available from the ITU website (http://handle.itu.int/11.1004/020.1000/4.1).
:NOTE: To prevent propagating possible error, notice the SK and BT - in fact none of the pro-signs are illustrated with an overscore. They should be. The previous paragraph explained ligation (overscore) but this is most often forgotten if not drummed into a students head. The bar (overscore) would tell learners that this character is to be sent as one character, therefore both these pro-signs are often taught erroneously as these examples illustrate. It is easy to understand why SK is often sent from a keyboard but there is no rational reason for mis-sending pro-signs manually. SK means Silent Key. When properly sent, the end of contact sounds like VA sent as one character and the dash (separator) sounds like TV sent as one character. SN is also a mis-illustration. The understood character sounds like VE run together. Morse should taught by the way it sounds and illustrated likewise. As we see above, when pro-signs are taught in an ambiguous manner, they are often mis-sent and this is emulated to the point where it becomes the de-facto norm. Concerned reader


By 1938 (https://search.itu.int/history/HistoryDigitalCollectionDocLibrary/1.35.48.en.100.pdf, p39-41), À has been added (with the same code as Å), and all of the accented letters and digraphs are described as "optional" except for É. Later, the ITU dropped support for all of the optional letters/digraphs, as the most recent ITU standards only contain É.
-- ] 00:10, 21 Jul 2004 (UTC)


Apart from the above letters (and perhaps the Esperanto letters), I don't think there was any sort of international convention when it came to accented letters. I suspect it varied from country to country, and there were probably multiple incompatible conventions. The most common convention was probably to omit accents altogether, although that probably wasn't an equally acceptable solution for all languages.
== Use of morse at Coast Radio Stations ==


By putting non-ITU accented letters into a single table in this article, we're probably implying a level of standardization and uniformity that didn't exist. I'm tempted to remove them, particularly as they're unsourced.
It is mentioned in this article that French radio stations ceased use of radio telegraphy in 1997 and that "Morse code was used as an international standard for maritime communication until 1999". Anyhow I know that Vardoe radio as the last Norwegian coast radio station used telegraphy until 1. Jan. 2003, and that Russian Coast Radio Stations as well as many other coast radio stations around the world most probably still use it. --] 12:27, 18 Aug 2004 (UTC)


I also don't think we can hope to include every possible Latin alphabet in this table (unless it gets much bigger). For example, there was also a Vietnamese Morse code (according to the ] article). Should we include that?


Apart from the ITU letters, the letters in this article seem to fall into five categories: Esperanto, Polish, Icelandic, French, Danish/Norwegian, and Other. I'll discuss each of them below.
== Is SOS a prosign or an abbreviation?==


ESPERANTO
This article says it is an abbreviation, to be sent with letter spacing, while the ] article says the exact opposite. So, please somebody correct the wrong variant. ] 11:03, 7 Oct 2004 (UTC)


The letters Ĉ, Ĝ, Ĥ, Ĵ, Ŝ, Ŭ come from ], the "international" language invented by L. L. Zamenhof in 1887. Esperanto had its heyday around the same time that Morse Code had its heyday, so I expect these letters actually were in use, and they probably were quite standardized due to fact that there was a central organization overseeing the language.
==Swing and its importance==


However, are these letters notable enough to be in this article? The Morse Code codes for these letters are already adequately covered in the ] article, so I think a simple "See Also:" might be enough.
I think the article could usefully mention that experienced operators using straight keys could recognize each other by the "swing" in the sent code - variations in the length of theelements. This was of practical significance during the WWII since sometimes if an agent in enemy territory had been discovered and substituted by an enemy operator, the "swing" of the station's code would change.
The "bandwidth" comment is misleading because it doesn't take into account the very low data rate of a Morse transmission - someone sending 40 WPM Morse is moving right along, but someone only speaking 40 words per minute would sound very odd indeed. For low bandwidth and true QRP DX you can't beat the various NASA deep space probes. --] 21:25, 13 Apr 2005 (UTC)
:First, I thought it was called ''fist'', this is the first I've heard it called ''swing''. Second, 40wpm morse code is a lot more than "words", as the lingo includes lots of two and three letter abbreviations that can represent entire sentences, and can really make a ] fly. This, along with increased accuracy, is what makes morse win in the right situation. Lastly, like morse code, the deep space probes use digital modes. All the advantages of morse stem from it being a digital mode. It just happens to be the only digital mode designed for humans. --] 05:23, 14 Apr 2005 (UTC)
::And now you know why I didn't write about "fist" in the article. Not sure where I've seen "swing", but I agree that "fist" is the more common term. But the "hand-made" quality of transmitted Morse is a significant characteristic to note; for the reasons above and also because it apparently makes machine transcription of hand-sent Morse more difficult. I've been reading up on the history; the original idea was to transcribe Morse off a trace on a paper tape, not by ear. Arguably all digital modes are designed for use by humans, though some need more hardware than others. And per the comment on my talk page, I understand a bug is the same as an iambic keyer.--] 17:32, 14 Apr 2005 (UTC)


POLISH
== Formatting ==


The letters Ą, Ć, Ę, Ł, Ń, Ó, Ś, Ź, and Ż come from Polish. As has been noted before, the encoding of Ź and Ż in this English article are the reverse of what they are in the Polish version of this article. Both are unsourced, so I have no way of knowing which is right, and I'm tempted to remove them. I think we should put in a "See Also:" and let the Poles figure it out.
I cleaned up all the tables a bit. The code examples are in lots of different formats/justifications, though, so I just left them. Which do you like the best?


ICELANDIC
-- --- ·-· ··· ·


This article contains the letters Ð (Eth), Þ (Thorn), and Æ, which come from Icelandic. (Æ is also in other alphabets, like Danish and Norwegian.) The letter Þ is notable for the fact that it is not derived from any Latin letter, so you cannot simply "drop the accent". That is, it requires a distinct representation in Morse Code. Although Eth derives from D, it is considered a distinct letter in Icelandic as the voiced counterpart of Thorn, and thus also demands a distinct representation.
<code>-- --- ·-· ··· ·</code>


The Icelandic version of this article gives codes for all of the Icelandic letters: Á, Ð (eth), É, Í, Ó, Ú, Þ (thorn), Æ, and Ö. The code for É matches the ITU code for É. Curiously, the Icelandic article gives the same code for O, Ó, and Ö, and the code for Ö does not match the ITU code for Ö, and I wonder if that is an error. (The article is unsourced.)
'''<code>-- --- ·-· ··· ·</code>'''


This raises a question. If we include Ð, Þ, and Æ in this article, shouldn't we also include Á, Í, Ó, and Ú? Or are Á, Í, Ó, and Ú omitable while Ð, Þ, and Æ aren't? And if we do include them, does it become a problem that the code for Ó in Icelandic is different from the code for Ó in Polish?
'''-- --- ·-· ··· ·'''


FRENCH
'''&minus;&minus; &minus;&minus;&minus; ·&minus;· ··· ·'''


The letters Ç and È are from French. (The French letters É and À are already ITU letters.) As someone who speaks French myself, I can see why Ç and È would be desirable letters to have, but I can also testify that French is quite legible without them, and I'm skeptical that they were ever widely used in Morse. One of the references cited in the article (https://en.wikipedia.org/Morse_code#cite_note-dik-archive-81) gives a code for Ç that is different from the one in this article, which increases my skepticism.
I guess it doesn't matter as long as the idea gets across. But hey, why not make it pretty, too? Maybe we could add a class to the css or something?


DANISH/NORWEGIAN
Probably all should be centered, too. - ] 00:40, Apr 22, 2005 (UTC)


The letters Æ, Ø, and Å are from the ]. The code for Å is from ITU, while Æ and Ø apparently reuse the ITU codes for Ä and Ö. Not much to say about them except that they're unsourced.
: My vote would definitely go for the last one above - the clearest and easiest to 'read'. --] 14:21, 23 Apr 2005 (UTC)


OTHER (Š and Đ)
::I like the look, too, but it's not easy to read or edit the markup. - ] 15:01, Apr 23, 2005 (UTC)

This article also gives codes for Š and Đ (D with a stroke, not Eth). I'm not even sure what languages these are supposed to be for.

Š could be for Czech, or Serbian, or Sami, but in each case, it's weird that there's no corresponding code for Ž, which is also a letter in all those alphabets.

Đ could be for Czech or Serbian, but again, coverage for those languages would still be incomplete. The code given here for Đ is also not the same as the code for Đ in Vietnamese, according to the the article on the ]. It's also weird that the code for Đ in this article conflicts with the ITU code for É, since É is not an "optional" letter in the standard. And all of this is unsourced.

So, yeah. I'm tempted to remove all the non-ITU codes from the table, and just have a short word about "National variants", with maybe some links to articles about the other alphabets.

] (]) 00:06, 8 January 2025 (UTC)

:'''Support''' as this all makes sense to me. --] (]) 10:26, 8 January 2025 (UTC)
::It turns out that I can't edit the article because it is semi-protected and my account is too new. ] (]) 19:35, 10 January 2025 (UTC)
:::I hate to ask for this, but could you write a condensed list of what specific changes you would like to make? Change X to Y, etc. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff">&nbsp;‥&nbsp;</span>]</span> 19:51, 10 January 2025 (UTC)

Latest revision as of 19:51, 10 January 2025

This page is not a forum for general discussion about Morse code. Any such comments may be removed or refactored. Please limit discussion to improvement of this article. You may wish to ask factual questions about Morse code at the Reference desk.
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
This  level-4 vital article is rated B-class on Misplaced Pages's content assessment scale.
It is of interest to the following WikiProjects:
WikiProject iconAmateur radio High‑importance
WikiProject iconThis article is within the scope of WikiProject Amateur radio, which collaborates on articles related to amateur radio technology, organizations, and activities. If you would like to participate, you can edit the article attached to this page, or visit the project page, where you can join the project and/or contribute to the discussion.Amateur radioWikipedia:WikiProject Amateur radioTemplate:WikiProject Amateur radioamateur radio
HighThis article has been rated as High-importance on the project's importance scale.
To-do list:

Improve to GA-Class:

Expand and improve:

Create:

WikiProject iconWriting systems Mid‑importance
WikiProject iconThis article falls within the scope of WikiProject Writing systems, a WikiProject interested in improving the encyclopaedic coverage and content of articles relating to writing systems on Misplaced Pages. If you would like to help out, you are welcome to drop by the project page and/or leave a query at the project’s talk page.Writing systemsWikipedia:WikiProject Writing systemsTemplate:WikiProject Writing systemsWriting system
MidThis article has been rated as Mid-importance on the project's importance scale.
WikiProject iconDisability
WikiProject iconMorse code is within the scope of WikiProject Disability. For more information, visit the project page, where you can join the project and/or contribute to the discussion.DisabilityWikipedia:WikiProject DisabilityTemplate:WikiProject DisabilityDisability
WikiProject iconTelecommunications Low‑importance
WikiProject iconThis article is within the scope of WikiProject Telecommunications, a collaborative effort to improve the coverage of Telecommunications on Misplaced Pages. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.TelecommunicationsWikipedia:WikiProject TelecommunicationsTemplate:WikiProject TelecommunicationsTelecommunications
LowThis article has been rated as Low-importance on the project's importance scale.

Archiving icon
Archives

1, 2, 3, 4, 5



This page has archives. Sections older than 365 days may be automatically archived by Lowercase sigmabot III when more than 10 sections are present.

Little mistake at https://en.wikipedia.org/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/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 also lists both but notes -•--• is only used sometimes because it conflicts with the bracket '('. Esperanto Misplaced Pages 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 Misplaced Pages 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 Misplaced Pages 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

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

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 (talkcontribs) 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

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

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

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

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

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

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)

Accented letters

I want to talk about the "Accented Letters" that are in this article, as it's all a bit of an unsourced mess.

To give some background, the very first ITU standard for Morse code (from 1865) contained the accented letters É, Å, Ä, Ö, Ü, Ñ, and the digraph CH. You can see them on pages 48-49 of this pdf file: https://search.itu.int/history/HistoryDigitalCollectionDocLibrary/4.1.43.fr.200.pdf. That document is available from the ITU website (http://handle.itu.int/11.1004/020.1000/4.1).

By 1938 (https://search.itu.int/history/HistoryDigitalCollectionDocLibrary/1.35.48.en.100.pdf, p39-41), À has been added (with the same code as Å), and all of the accented letters and digraphs are described as "optional" except for É. Later, the ITU dropped support for all of the optional letters/digraphs, as the most recent ITU standards only contain É.

Apart from the above letters (and perhaps the Esperanto letters), I don't think there was any sort of international convention when it came to accented letters. I suspect it varied from country to country, and there were probably multiple incompatible conventions. The most common convention was probably to omit accents altogether, although that probably wasn't an equally acceptable solution for all languages.

By putting non-ITU accented letters into a single table in this article, we're probably implying a level of standardization and uniformity that didn't exist. I'm tempted to remove them, particularly as they're unsourced.

I also don't think we can hope to include every possible Latin alphabet in this table (unless it gets much bigger). For example, there was also a Vietnamese Morse code (according to the Vietnamese alphabet article). Should we include that?

Apart from the ITU letters, the letters in this article seem to fall into five categories: Esperanto, Polish, Icelandic, French, Danish/Norwegian, and Other. I'll discuss each of them below.

ESPERANTO

The letters Ĉ, Ĝ, Ĥ, Ĵ, Ŝ, Ŭ come from Esperanto, the "international" language invented by L. L. Zamenhof in 1887. Esperanto had its heyday around the same time that Morse Code had its heyday, so I expect these letters actually were in use, and they probably were quite standardized due to fact that there was a central organization overseeing the language.

However, are these letters notable enough to be in this article? The Morse Code codes for these letters are already adequately covered in the Esperanto alphabet article, so I think a simple "See Also:" might be enough.

POLISH

The letters Ą, Ć, Ę, Ł, Ń, Ó, Ś, Ź, and Ż come from Polish. As has been noted before, the encoding of Ź and Ż in this English article are the reverse of what they are in the Polish version of this article. Both are unsourced, so I have no way of knowing which is right, and I'm tempted to remove them. I think we should put in a "See Also:" and let the Poles figure it out.

ICELANDIC

This article contains the letters Ð (Eth), Þ (Thorn), and Æ, which come from Icelandic. (Æ is also in other alphabets, like Danish and Norwegian.) The letter Þ is notable for the fact that it is not derived from any Latin letter, so you cannot simply "drop the accent". That is, it requires a distinct representation in Morse Code. Although Eth derives from D, it is considered a distinct letter in Icelandic as the voiced counterpart of Thorn, and thus also demands a distinct representation.

The Icelandic version of this article gives codes for all of the Icelandic letters: Á, Ð (eth), É, Í, Ó, Ú, Þ (thorn), Æ, and Ö. The code for É matches the ITU code for É. Curiously, the Icelandic article gives the same code for O, Ó, and Ö, and the code for Ö does not match the ITU code for Ö, and I wonder if that is an error. (The article is unsourced.)

This raises a question. If we include Ð, Þ, and Æ in this article, shouldn't we also include Á, Í, Ó, and Ú? Or are Á, Í, Ó, and Ú omitable while Ð, Þ, and Æ aren't? And if we do include them, does it become a problem that the code for Ó in Icelandic is different from the code for Ó in Polish?

FRENCH

The letters Ç and È are from French. (The French letters É and À are already ITU letters.) As someone who speaks French myself, I can see why Ç and È would be desirable letters to have, but I can also testify that French is quite legible without them, and I'm skeptical that they were ever widely used in Morse. One of the references cited in the article (https://en.wikipedia.org/Morse_code#cite_note-dik-archive-81) gives a code for Ç that is different from the one in this article, which increases my skepticism.

DANISH/NORWEGIAN

The letters Æ, Ø, and Å are from the Danish and Norwegian alphabet. The code for Å is from ITU, while Æ and Ø apparently reuse the ITU codes for Ä and Ö. Not much to say about them except that they're unsourced.

OTHER (Š and Đ)

This article also gives codes for Š and Đ (D with a stroke, not Eth). I'm not even sure what languages these are supposed to be for.

Š could be for Czech, or Serbian, or Sami, but in each case, it's weird that there's no corresponding code for Ž, which is also a letter in all those alphabets.

Đ could be for Czech or Serbian, but again, coverage for those languages would still be incomplete. The code given here for Đ is also not the same as the code for Đ in Vietnamese, according to the the article on the Vietnamese alphabet. It's also weird that the code for Đ in this article conflicts with the ITU code for É, since É is not an "optional" letter in the standard. And all of this is unsourced.

So, yeah. I'm tempted to remove all the non-ITU codes from the table, and just have a short word about "National variants", with maybe some links to articles about the other alphabets.

阮阿蘭 (talk) 00:06, 8 January 2025 (UTC)

Support as this all makes sense to me. --𝕁𝕄𝔽 (talk) 10:26, 8 January 2025 (UTC)
It turns out that I can't edit the article because it is semi-protected and my account is too new. 阮阿蘭 (talk) 19:35, 10 January 2025 (UTC)
I hate to ask for this, but could you write a condensed list of what specific changes you would like to make? Change X to Y, etc. Remsense ‥  19:51, 10 January 2025 (UTC)
Categories: