03-11-2017, 04:43 PM
(This post was last modified: 03-11-2017, 04:53 PM by voynichbombe.
Edit Reason: P.s.
)
As @Psillycyber writes above about his riddle, the curve/line system is used to write (obfuscate) morse code. Technical language gets fuzzy here, we'd rather say encoding instead of cipher.
What I meant is: if you have a cipher/code character representing either a dot or a dash (or supplemental interpunctuation), your encoded text will consist of many more characters than the decoded/clear text will. Like in:
...---... you will have 9 coded characters representing 3 cleartext ones, SOS. This is the ratio I was mentioning, and it does not apply to simple substitution ciphers.
Baconian needs 15 characters to encode 3 cleartext characters, like in:
ThE VoyNIch BoMbE
Here the spaces are nulls. Let me know if you figure that one out
P.s.: of course the curve/line system could also be used to obfuscate baconian, along with some pitfalls like nulls, encoded bi- & trigraphs etc. But surely this has been tried before and did not yield any results.
What I meant is: if you have a cipher/code character representing either a dot or a dash (or supplemental interpunctuation), your encoded text will consist of many more characters than the decoded/clear text will. Like in:
...---... you will have 9 coded characters representing 3 cleartext ones, SOS. This is the ratio I was mentioning, and it does not apply to simple substitution ciphers.
Baconian needs 15 characters to encode 3 cleartext characters, like in:
ThE VoyNIch BoMbE
Here the spaces are nulls. Let me know if you figure that one out
P.s.: of course the curve/line system could also be used to obfuscate baconian, along with some pitfalls like nulls, encoded bi- & trigraphs etc. But surely this has been tried before and did not yield any results.