Morse Code Translators / Trust
Editorial Policy
How we choose topics, check facts, write guides and fix mistakes.
Last reviewed Nov 2, 2026
Everything we publish about Morse code is meant to do one job: answer a real question clearly enough that you can act on it. This page explains the rules we hold ourselves to, so you can judge whether a guide deserves your trust.
The rules in short
- Primary source
- ITU-R Recommendation M.1677-1 for all codes and timing
- Every example
- Tested in the translator before it goes live
- Written by
- The Morse Code Translators editorial team
- Dates
- Each page shows when it was last reviewed
- Mistakes
- Fixed openly. Report them at [email protected]
What we publish
We write about International Morse code: the alphabet, numbers and punctuation, timing and spacing, translation, and how to learn it. A topic earns a page only if it solves a specific problem for the reader. We do not publish a page just because a search term exists, and we do not produce near-identical pages that only swap one word or character for another.
Where our facts come from
For anything technical we start with the primary source. For Morse code that is the International Telecommunication Union, which defines the characters and the timing rules we use. When we need background such as history or how the code is used today, we prefer official documentation, standards bodies and established reference works over blogs or forum posts.
A secondary source can help us explain something, but it never overrides the standard. If two sources disagree about a technical point, the standard wins and we say which convention we are describing.
How we write
- One question per page. The answer comes early, then the detail for readers who want it.
- Plain language. We explain terms like dot, dash and gap the first time they appear and avoid jargon where a simple word works.
- Original explanations. We write our own examples and practice material rather than rewording other sites.
- Honest limits. If the tool does not support something, such as American Morse or non-Latin alphabets, we say so.
Review before publishing
Before a page goes live, an editor checks it against a short list.
- Every character pattern matches the reference table.
- Timing numbers are correct and the dot, dash, letter gap and word gap are never mixed up.
- Each Morse example is typed into the translator and gives the result the page claims.
- Written conventions, such as a space between letters and a slash between words, are described as conventions of this tool and not as part of the standard.
- Any claim about features, accuracy or privacy matches how the site really works today.
- Internal links go to the page they say they go to.
Keeping pages current
Morse code itself changes very little, but our tool and pages do. We review reference pages regularly and whenever the translator changes. The review date at the top of a page tells you when we last confirmed it was accurate. A new date means we checked the content again, not that the page was rewritten.
Corrections
We want to hear about mistakes. Email [email protected] with the page address, the sentence or example you think is wrong, what you expected, and a source if you have one. Please use a harmless sample and not a private message.
We check every report against the standard and the live tool. If it is a real error, we fix it, update the review date and, when the mistake could have misled someone, add a short note explaining what changed. We do not quietly rewrite a page to hide that it was wrong.
Your messages stay yours
We do not use what visitors type into the translator as research for articles. Topic decisions come from questions people send us and from general patterns, never from the content of someone’s message. See the privacy policy for what the site collects.
