CS Fundamentals beginner 8 min

Decode a Morse Message and Check the Spacing

Translate Morse code and verify whether spacing changed letters, words, or the whole message.

Scenario

A puzzle answer arrived as a string of dots and dashes, but it passed through a chat client that may have collapsed whitespace. In Morse, spacing is data: a single space separates letters, and a slash (or triple space) separates words. If the separators were damaged in transit, the decoded text turns into alphabet soup even though every dot and dash is intact.

Broken input

.... . .-.. .-.. --- / .-- --- .-. .-.. -..

Goal

Use Morse Code Translator to decode the message and confirm the word boundaries survived. If the translation reads as one long jumble, the separators — not the symbols — are what needs fixing.

Tool sequence

  1. Open Morse Code Translator.
  2. Paste the sequence with its spacing untouched — normalizing whitespace before decoding destroys the letter boundaries you are trying to verify.
  3. Translate to text and read the output against the separator convention: space between letters, / between words.
  4. The decode produces HELLO WORLD — five letters, a word break at the slash, five more letters.
  5. If a different transcript decodes to nonsense, re-check whether double spaces were collapsed to single ones, then re-insert word breaks and translate again.

Checkpoint output

.... . .-.. .-.. ---  →  HELLO
/                     →  (word break)
.-- --- .-. .-.. -..  →  WORLD

The message decodes cleanly to HELLO WORLD, confirming both the symbols and the word separator came through intact.

Common mistakes

  • Treating every space as a word boundary — single spaces separate letters, not words.
  • Letting an editor or chat app collapse the whitespace that encodes letter and word breaks.
  • Changing dots and dashes while reformatting the message (-- and are not the same character).
  • Assuming a failed decode means the content is not Morse when the separators were simply stripped.

Related tools and lessons