09-09-2016, 02:56 AM
(This post was last modified: 09-09-2016, 03:01 AM by ThomasCoon.)
You're definitely right that a constructed language could account for the changes (and patterns of changes) between similar-looking vords. That thought has also occurred to me, and I definitely understand why you believe it.
Just to mention, I theorized a different difficulty for encoding Voynichese with contrived spaces:
In my units chart from the other thread, let's say for example that /d/ is encoded in Voynichese as unit 22 (ke), /e/ is unit 6 (ee) and /r/ is unit 17 (ey). If you want to write the word "der" in this setup, you would get keeeey. If you wanted to connect two <e>s with a bar, you could make kcheey (an actual VMS vord, by the way).
Now the difficulty is figuring out where one "unit" ends and the other begins. I believe this is why we have so many <eee> or <che> clusters in the VMS; I believe it is intentionally done to make the script harder to crack. Contrived spaces may help the scribe who knows the cipher system, but it doesn't help an outsider who is confused why <qo> is always at the front of a word and <aiin> is almost always at the end
.
Just to mention, I theorized a different difficulty for encoding Voynichese with contrived spaces:
In my units chart from the other thread, let's say for example that /d/ is encoded in Voynichese as unit 22 (ke), /e/ is unit 6 (ee) and /r/ is unit 17 (ey). If you want to write the word "der" in this setup, you would get keeeey. If you wanted to connect two <e>s with a bar, you could make kcheey (an actual VMS vord, by the way).
Now the difficulty is figuring out where one "unit" ends and the other begins. I believe this is why we have so many <eee> or <che> clusters in the VMS; I believe it is intentionally done to make the script harder to crack. Contrived spaces may help the scribe who knows the cipher system, but it doesn't help an outsider who is confused why <qo> is always at the front of a word and <aiin> is almost always at the end
.