An unfortunate example. That's TIED HITCH SLOE REIGN RULE MOW? With only two parity bits, you can't even be sure this decoding is invalid.
RFC 1751 [0], from which this example comes, doesn't envisage the encoding being used in oral communication. Instead, it makes codes easier the user to "read, remember, and type in".
For oral transmission among professionals, sticking to the 26 upper case letters and relying on the NATO alphabet for encoding is a reasonable choice. Getting codes from untrained users in a lossy oral environment is still an unsolved problem.
Typing something letter by letter in Latin when neither party is a native speaker of English is very much painful almost half the time it happens
My wife thought it was crazy the first time she heard me use it. Then she realized that they all understand it too.
Some people are going to sound like they’re saying Todd for Tide, and have you heard how Baltimore pronounces Iron?
> These require use of a keyed message-digest algorithm, MD5 [Riv92] […] while sufficiently strong […]
Heh!
> […] is hard for most people to read, remember, and type in.
Ok, go on…
> English words are significantly easier for people to both remember and type.
Most people don’t know English.. But that shouldn’t be a problem since the word list can be changed. Right?
> Because of the need for interoperability, it is undesirable to have different dictionaries for different languages.
Oh. Well the world already learned the 26 characters of the English alphabet so adding a few words is probably fine..
> char Wp[2048][4] = […]
Oh, well at least it’s common words suitable for English beginners?
> WAD, BESS, MERT…
Hold on, these words are tricky even for…
> ORR? AGEE EGAN HAAS!!
…Are you done?
> GAUL FLAM! DRAB!