| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 621 online users.
» 12 Member(s) | 604 Guest(s)
Applebot, Baidu, Bing, Google, Yandex, Aga Tentakulus, asteckley, evandrunen, KERITY, magnesium, oeesordy, quimqu, Rafal, ReneLueth
|
|
|
| f3v |
|
Posted by: don of tallahassee - 25-09-2016, 06:24 AM - Forum: Imagery
- Replies (19)
|
 |
f3v is probably ramsthorn, Rhamnus catharticus, also known as buckthorn. The code attribution is the first four glyphs in the 5th word, 2nd line, 1st paragraph and is sounded r-t-h-n.
The mnemonic is in the leaves. They seem to show a top view of six rams all facing outward with their huge horns in herd defensive stance. The leaves also resemble somewhat the leaves of the herb. I don't know if the mnemonic is only the rams or if it is rams plus horns - I favor the first choice.
Thank you.
Don of Tallahassee
[admin: restored from backup]
|
|
|
| Voynichese Phonotactics |
|
Posted by: Emma May Smith - 22-09-2016, 02:29 PM - Forum: Analysis of the text
- Replies (39)
|
 |
In another thread a discussion was started about the phonotactics of Voynichese. Basically, where do characters occur within words and syllables and how might this reflect an underlying language. There was particular reference to that fact that [k, t] seldom occur at the end of words (the same can be said for [ch, sh]) and whether that might be a realistic linguistic feature. I've reposted my response below, and am keen to discus the matter broadly and fully.
Ok, let's get a little technical.
You can think of a syllable as having three parts:
1) onset: this is everything which comes before a vowel;
2) nucleus: this is the vowel or any sound which acts as a vowel;
3) coda: this is everything which comes after a vowel.
Now, in terms of consonants, these will typically appear in the onset or coda (though they can form the nucleus). Most languages have both a) restrictions on how many consonants can be in an onset or coda, and b) the order in which they appear. Some languages completely forbid clusters—that is, more than one consonant in either onset or coda position—but if they allow more than one they have a tendency to order them in the same way. Basically, certain sounds must be nearer the vowel than others. It's based on a quality known as sonority, but we shan't bother with explaining that except to acknowledge it exists.
There is a tendency to allow onsets to be more complex than codas. Typically all or most consonants can appear there and some clusters are allowed. Codas are more often either empty or have one of a restricted set of consonants, with clusters forbidden. Of course, many languages which flout these rules do exist, for example English, which allows clusters of three consonants in the onset and four in the coda, but it is not typical. (Indeed, Indo-European languages as a whole are typically more complex in their syllable structure than the average language.)
So, when we look at the structure of Voynich words and see that [r, l] are very commonly found at the end but [k, t] are not, what we are observing (ASSUMING the surface patterns are linguistic) is a fact about what the underlying language permits in syllable codas. We can explain this by saying that [r, l] must have some phonological difference to [k, t]. Were you to suggest that [r, l] were nasals and [k, t] plosives, then you would have a similar situation to a number of languages which forbid obstruents but permit sonorants in codas.
Likewise, the observation that [k, t] often appear at or near the beginning of words can be explained in a similar way. If you believe that [k, t] are plosives, then they have low sonority and typically always appear at the beginning of an onset before sounds with a higher sonority (sibilants are sometimes exceptional, so /s/ can appear in places like in English 'skip' and 'stone'). Those strings which appear before [k, t] in Voynich words: [o, qo, cho, che, cheo, etc] can be explained as separate syllables. The task of researchers is then not one of explaining how [k, t] work, but why the syllables within a word are structured as they are.
Sorry if this answer is a bit long-winded, but hopefully it is helpful to thinking about the possible linguistic features of Voynich words. It is my belief that a linguistic analysis, ignoring the origins of the script, the illustrations, and even the potential meaning of the text, could well solve the Voynich manuscript. At the very least it provides us with a framework for assessing both the text and potential solutions.
|
|
|
|
| Voynichese: a forgotten turkic-aramaic-persian language? |
|
Posted by: escape - 21-09-2016, 07:19 PM - Forum: Analysis of the text
- Replies (50)
|
|
Hello all! I'd started my research in Voynichese 2 years ago and have got some results!
I've chosen the different way to crack this cipher, although it wasn't a cipher...
I've found the five basic elements on the upper of f77r page - there was 5 images of them, blowing out of their fittings and inscription of each. Then I've started to finding and comparing words with the same meaning and sounding in the languages of all over the world.
And what came into result - just see below:
![[Image: X_J5QvzSVZ8.jpg]](https://pp.vk.me/c636122/v636122792/2e0da/X_J5QvzSVZ8.jpg)
Then, a very hard work with a letter-sound combinations and a pile of dictionaries allow me to obtain an approximate sounding of the almost all voynichese symbols:
![[Image: VuvQbZg196Q.jpg]](https://pp.vk.me/c636122/v636122792/2e0c7/VuvQbZg196Q.jpg)
The next thing i've found - the moon-calendar on a page f67r2:
1. 4o*H*oca2 - [ FOTOI[font=sans-serif]ӘR / ФОТОИӘР ] - foto + year. Täz[font=sans-serif]äyil in Turkmenian means 'pure year'' - new year;[/font][/font]
2. 8rco8a2 - [ [font=sans-serif]ĞIO[font=sans-serif]Ƣ[font=sans-serif]ӘR / [/font][/font]ҖӨҒӘР ] - ??;[/font]
3. 9Sax8ax - [ AB[font=sans-serif]ӘŞ[font=sans-serif]Ƣ[font=sans-serif]Ә[font=sans-serif]Ş / [/font][/font][/font][/font]АБӘШҒӘШ ] - the word derived from Turkmen/Uzbek 'beshgesh' that means 'a gift'. There are a variants in another Turkic: peshgesh, peshkesh (Chagatai);
4. 9*H*o8ax - [ ATO[font=sans-serif][font=sans-serif]Ƣ[/font][font=sans-serif][font=sans-serif]Ә[/font][/font]Ş / АТОҒӘШ ] - ??;[/font]
5. *H*ox8aiiU - [ TO[font=sans-serif]Ş[font=sans-serif]Ƣ[font=sans-serif]ӘÑD /[/font][/font][/font] ТОШҒӘҢД ] - Probably, from a city named Tashkent (Uzbek's capital). This word in Uzbek means 'a stone city' and sounds like Toshkänt.
6. o*H*a289 - [ OT[font=sans-serif]ӘRƢA / ОТӘРҒА ] - ??;[/font]
7. rco8axcj - [ JIO[font=sans-serif]Ƣ[font=sans-serif][font=sans-serif][font=sans-serif]Ә[/font][/font][/font][/font]Ş* / ХӨҒӘШ* ] - ??;
8. 9*H*rco8x9 - [ ATHIO[font=sans-serif]ƢŞA / АЦӨҒША ] - ??;[/font]
9. or*H*c9S - [ OJTIAB / ОХТИАБ ] - Clear here. But none the calendar have a 9th month - october in the world. Russian "oktiabr' ";
10. 9*H*oH*a2 - [ ATOK[font=sans-serif]ӘR / АТОКӘР ] - ??;[/font]
11. o*H*oxo2 - [ OTO[font=sans-serif]ŞOR / ОТОШОР ] - derived from word o*H*ox - [ OTOŞ / ОТОШ ] - Fire, warm, hot. Atash, otash, atish, atesh, etc in other Turkic;[/font]
12. oH*o8a2 - [ OKO[font=sans-serif]Ƣ[font=sans-serif]ӘR / [/font]ОКОҒӘР ] - probably - ukuger. Google gave me a phrase "yal takibasu ukuger-un siinesiin tiilebesii" with no translation;[/font]
|
|
|
|
|
![[Image: 65262]](http://www.charbase.com/images/glyph/65262)
![[Image: 08B1.png]](http://rishida.net/rishida/c/Arabic%20Extended-A/large/08B1.png)
![[Image: numerologychart15.jpg?w=840]](https://voynichnumerology.files.wordpress.com/2016/09/numerologychart15.jpg?w=840)
![[Image: alchemy2.jpg?w=840]](https://voynichnumerology.files.wordpress.com/2016/09/alchemy2.jpg?w=840)