The idea is to have a sequence of numbers defining the length of “on” and “off” state.
Make mass addiction > partial results and then evaluate length to get parameters, and shatter with those parameters. Then doing a dispatch will let you keep/see only the “on” state.
This part is actually the simplest, just 4 components.
To achieve your sequence of numbers you can smartly insert characters and then “translate” them using unicode.
Reverse-engineering this will explain more than words.
PS1 i wrote brown as BOWN …
PS2 the space character, i’ve translated to ‘_’ but it could have just been translated into itself in the first translation, making it " = " in the first dictionary and " =7" in the second dictionary…
Yes, many morse code tables are shown in 2 or more columns and selecting them mess up the order.
In that page the <div>s are probably in an order which made the selecting easy.
Then removing the spaces with notepad++ is a 30 sec task, using ALT+drag to edit many rows at once:
(I’m saying this just for who don’t know this … notepad++ should be built-in on windows!)
whoa!
Please double… triple check if the dictionary i’ve used is correct! (I’ve just copy-pasted from a random google result).
Check that everything is correct and translate back to counter proof the correct-ness of everything.
Just as an aside, there’s a great book “The Victorian Internet” by Tom Standage that makes the case the telegraph was a more world-shaking development than the WWW. I tend to agree.
you said it!
… notepad++ should be built-in on windows!)