An Eye for an Eye, and a… Letter for a Letter…?

When one follows the developments around the VM, research into it seems to be like a stream, where new ideas and theories appear somewhere upstream in the distance to come closer, and let themselves be examined more fully while they drift by you, before they follow the water downstream and finally vanish in the dusk of forgetableness. Rarely one of them will leave so much as a beacon behind.

One repeated pattern that seems to crop up time after time, and goes mostly unnoticed by even the old-time and seasoned Voynicheros, is the more or less explicit assumption that one VM letter is the equivalent to one plaintext letter, and that one VM word corresponds to one plaintext word.

Now, I can see where this would come from: Of course it’s natural to assume, it’s the most simple and straightforward way to do it (Which, in itself ought to be a warning sign: If the VM was enciphered “simply and straightforward”, it would have been solved long ago…), it’s the way ciphers were done in period, and it lends itself readily to easy analysis.

Unfortunately, in all probability this is not the way the VM was cooked up. Let’s look at a few of the arguments against this case:

  • The main body of the VM consists of a rather limited character set. Depending on your choice of transcription, you’ll arrive at somewhat around 17 different characters, which make up the better part of the VM. Admittedly, there is a large number of “minor” characters, but these are fairly rare. Now, assuming that the VM has a European medieval background, the character sets which are conceivable for the plaintext are latin, greek, cyrillic and perhaps arab or hebrew letters. But unfortunately all of these writing systems sport more than 20 different characters, plus possibly numerals, interpunction and other special characters. The VM character set simply appears to be too small to accomodate a complete alphabet.
  • Words show a very strong internal structure. VM words are far from random, au contraire: While nobody has as yet been able to completely determine which rules are underlying their composition, it’s pretty obvious that there are rules which are followed fairly coherently. To my knowledge, there are no European languages and only very few at all in the world which have such a determined set of rules for word composition, whether they are being written in their original alphabet or in that of the VM. What is worse: If in addition to switching to a new alphabet the author has employed an enciphering system (which he obviously has, because if the VM was a simple substitution cipher, we would have solved it), this would contribute to reducing the word structure and make it appear more random. (The only schemes which might increase the word regularity would be something like a transposition cipher with alphabetical sorting, which is conceivable, but wouldn’t exactly render the task of deciphering easier even for the intended audience.)
  • One could argue that the VM author dropped eg the vowels from the plaintext before enciphering, hence reducing the number of different VM characters required. But this in turn would have reduced the word regularity. Bear in mind that the EVA transcription allows the better part of the VM to be read out aloud, which shows that there is in the VM ciphertext a structure retained which assigns to the VM letters functions comparable (but probably not identical) to “consonants” and “vowels”.
  • All of the above work together to render an information content in the VM of roughly 2 characters/ciphertext word; obviously far too little for any natural languages.
  • No words in the VM have been identified which seem to have the function of particles in natural languages, like articles, “and”, “or” and similar.
  • On a more subtle level, there also appear to be things going on with decreasing average word length towards the end of a line, which don’t sit well with a 1:1 correspondence.

So, all in all this is why I’m convinced that the VM is something different than a simple substition or even a transposition cipher. Something else is going on, and the enciphered information is categorized in letters and grouped in words, but these ciphertext letters are not plaintext letters, and the ciphertext words are not plaintext words.

Strokes, anyone?

7 thoughts on “An Eye for an Eye, and a… Letter for a Letter…?

  1. Well put, Elmar. Once and then it seems necessary to take a bath from known “regularities” in the VMs in order to reorient thinking just along possible lines. On those grounds, I would reread Currier, DImperio, Stolfi…; any proposed solution should be able to contain and explain that, in full.
    Wherefrom did you get the “2 chars/ciphertext word ” parameter? That may be of much interest for myself.

  2. As embarrassing as it is, Jorge, your comment forced me to look up where I got my statement from and, even more embarrassing, it turned out I was talking (partly) nonsense.

    I remembered having read about the 10-bit-per-word value*), but forgot where, and the best claim to this value I could find now comes from a recent paper by René Zandbergen. Alas, while he confirms the value of 10 bit/word, he also maintains that this is “just like normal language.” (And I believe him.)

    Apparently I confused something here. In any case, René goes on to show that it actually is very well possible that each VM word represents one plaintext word. While VM word beginnings are somewhat more “limited” and schematic as in Latin (which René used as a plaintext reference), word endings in the VM seem to be more variable than in natural language. Which, at least, seems to support my statement that plaintext letters do not map 1:1 to ciphertext letters.

    *) and jumped to the conclusion that, if we start with a 32 character set for the plaintext, then 5 bit per letter would be needed for enciphering

    1. Elmar, then “just like normal language”, in that respect a VMS word seems to be a possible bet for a plaintext word, that is a valuable piece of info. Thanks for the correction, your remarks came apropos all the same.

      1. I think my confusion came about by assuming that an information content of 10 bit would be expressed by a 10 bit character sequence, ie that there would be no redundancy in the encoded text. Which, of course, is erroneous.
        (I still don’t think 1 VM word = 1 plaintext word, but I don’t hold this as strongly anymore.)

  3. I have been researching the Kolbrin Bible and 2012 issues. I believe that page 70r may very well predict this years transit of Venus and combustion with the sun. In the inner circle is the transit, the outer circle the orbit and conjunction of Venus. It should be noted that Venus was considered the ruler of Pisces in ancient times. Could this be related to the ‘Fiery Dragon’ prophesies and the Mouth of the Sea Creature below the Ecliptic which Venus traverses? Perhaps scientifically the alignment of the Planets including Jupiter, the active phase of the Sun, would it be possible for the Sun’s (LEO) surface “turning around” and consequently releasing a CME or multiples directly towards Earth and the results aggravated by the Polar shift that has occurred due to recent earthquakes?

  4. Well, as far as we know Kepler was the first person to predict a Venus transit, and that was well after what is generally considered the period of creation of the VM.
    How do you draw the connection between Venus and f70r?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s