![]() |
It is not Chinese - Printable Version +- The Voynich Ninja (https://www.voynich.ninja) +-- Forum: Voynich Research (https://www.voynich.ninja/forum-27.html) +--- Forum: Voynich Talk (https://www.voynich.ninja/forum-6.html) +--- Thread: It is not Chinese (/thread-4746.html) |
RE: It is not Chinese - tavie - 15-06-2025 (Yesterday, 09:56 AM)Jorge_Stolfi Wrote: You are not allowed to view links. Register or Login to view.This seems unlikely. Material like the Rosetta Stone and the Bankes obelisk were crucial for the decipherment. Quote:Some of the "bumpiness" features listed by Nick seem to affect a relatively small fraction of the text, and (like transcription errors, or missing fragments on clay tablets) should not be a big obstacle to decipherment. I don't see what on Nick's list affects a small fraction of the text, except maybe the right justified titles on a minority of folios. The rest of the issues - repetitions and word types varying across different positions of the text - are chronic problems, so chronic it seems something has been done to the plaintext, if there is one. And we can also add the You are not allowed to view links. Register or Login to view. that I've been looking at to the list. Whether it is encryption, shorthand, or a combination of the two with changes for cosmetic reasons chucked into the mix, the result is a cacophony of noise. I do not see how natural reasons (e.g. subject matter or linguistic features) can be responsible for all this. It is just too bumpy and noisy throughout. Quote:It is almost certain now that one-leg gallows are variants of the two-leg gallows, possibly combined with e or other letters, that are used mostly on the first line of a paragraph -- a convention that the Author picked up from the typical European manuscript style. I don't see reason to ascribe any other meaning to single-leg gallows, just as I don't think that split two-leg gallows or fancy decoration on gallows have any linguistic or semantic value. My feverish ramble in that other thread was not terribly coherent but my point was that no simple explanation works with the ornamental gallows, since there is a fundamental mismatch between the Top Rows and the lines below them in a paragraph. Something far more complex is going on. We start with: Problem 1: Top Rows* have too many /p/ and too few /k/ in comparison to the lower lines. We don't see this in natural language.
Problem 2: But in the lower lines, k is frequently followed by e. If p = k, where is pe in the Top Row?
Problem 3: But in Top Row, p is frequently followed by ch. Over 50% of times, usually! If p = ke, then pch = kech, but where are all the many kech we should see in the lower lines?
We are now looking at having to mutate most if not all of the word type in order to find an equivalence. There is no neat exchange that allows us to match a Top Row word type with a word type in the below paragraph. It's more than just exchanging a few letters. The initials are often different, the middles are often different, and the finals are often different. Why do we see more /sh/ at Top Row? Is this an ornamental form as well? Why are there so many missing initial ch at Top Row and so many word-middle ch? My idea is that initial ch has been shunted into middle position by adding /op/ or /qop/ to the ch words, but to make it work, I also have to mutate the glyphs after /ch/ because they don't match as expected. This is becoming highly complex and does not seem natural. Quote:The peculiar features at the "margins" of the pages can have banal explanations too. For one thing, on many languages the final letters or words of a sentence may be strongly affected by the topic. In a narrative of past events, sentences are more likely to end with "-ed" in English, with "-ta" in Japanese; whereas in a herbal the sentences should be mostly in the present tense, hence more likely to end with "-desu" or "-masu" in Japanese. Others have pointed out the increased use of abbreviations at end of lines in European manuscripts. I'm Team Abbreviation too, but if it is going on, it is in a highly complex way. We have the same issue here as with top rows: the mismatch between expected words and actual words at line start and line end is more complex than a change of ending by itself at the line end, or a change of initials at line start. If at line end, it was only daiin becoming dam, or kaiin becoming kam, this would work. But it isn't. Initials and word-middles are often different as well. The same is true for line start. Line patterns at different positions of the text are serious problems for any idea that we are only seeing a natural language. Quote:When single-leg gallows occur inside a parag, I would guess that the Scribe failed to see a parag break in the Author's draft and thus started the first line of the second parag as continuation of the last line of the previous one. I'm not convinced by this but I find it interesting in that it could imply that if we have copying scribes following a layout by an "Author", they have agency in terms of how they lay out the text: they are not obliged to match their line starts with the Author's line starts, nor their line ends with the Author's line ends by cramming in text or widening spaces between words to make the ends match. So a word that is line start for a scribe may be a mid-line word for the author in their original text, and word that is line end for a scribe may also be a mid-line word for the author. Given how word types seem to undergo complex mutations at these positions, this implies to me that the scribe has an understanding of the system and how to mutate the word: they are not blind copyists. * by Top Row, I mean the first line of each paragraph but with its first word and last word omitted so as to isolate a top row effect from separate paragraph/line start effects and line end effects. RE: It is not Chinese - Jorge_Stolfi - 16-06-2025 (14-06-2025, 09:36 PM)oshfdk Wrote: You are not allowed to view links. Register or Login to view.It's not just about recurring. It's about creating numerous (on the order of thousands in the text of the size of the Voynich Manuscript) repeating patterns, where certain substrings change while surrounding text remains the same. "Take this medicine for fever or bloating, one spoon two times daily", "take this medicine for cough or migraine, one spoon three times daily", etc. I am looking again at this conjecture (Starred Parags section = some version of the SBJ). Data files:
The paragraph breaks in sparags.eva are a bit different from those in the 1.6e6 interlinear, because the stars in the margin are not consistent with the hints in the text itself. A parag is assumed to have the following properties
Here are the parag and word counts: Code: bengcao 370 parags 10930 words Considering the missing bifolio in the SPS quire, the coincidence of both counts seems quite remarkable. However we must take into account that
More to follow... RE: It is not Chinese - Jorge_Stolfi - 16-06-2025 (Yesterday, 01:18 PM)tavie Wrote: You are not allowed to view links. Register or Login to view.(Yesterday, 09:56 AM)Jorge_Stolfi Wrote: You are not allowed to view links. Register or Login to view.Some of the "bumpiness" features listed by Nick seem to affect a relatively small fraction of the text, and (like transcription errors, or missing fragments on clay tablets) should not be a big obstacle to decipherment.I don't see what on Nick's list affects a small fraction of the text, except maybe the right justified titles on a minority of folios. The rest of the issues - repetitions and word types varying across different positions of the text - are chronic problems, so chronic it seems something has been done to the plaintext, if there is one. What I mean is this. The computer transcriptions we have all contain some number of explicit 'unreadable' glyph codes ('*') and must have an unknown number of unmarked transcription errors. The VMS itself surely has an unknown number of errors that the Author committed while writing the draft (where he meant to write one glyph but skipped, doubled, or wrote the wrong glyph) and more when the draft was copied to vellum (by him or by a distinct Scribe). But as long as those gaps and errors are less than 90% of all glyphs, they will only make the decipherment harder, not impossible. It seems pretty certain that the one-leg gallows are just alternatives to the two-leg ones, possibly in combination with other letters, that are used almost only on the first line of each paragraph. Until we figure out exactly what the rules are, we can replace all one-leg gallows, anywhere, by '*'. Ditto for the m and g glyphs that seem to be extra common at the ends of lines and/or paragraphs. Maybe they are features of the language, like "-す" and "-た" in Japanese. Maybe they are abbreviations that the Scribe was allowed to use when he got close to the right margin and there was only one or two words remaining in the paragraph. Whatever. Just replace every 'm' and 'g' by '*'. Then replace all weirdos and very rare characters by '*'. Then discard all labels, and isolated glyph tables and sequences. Those changes will add '*' to a relatively small percentage of the text, say 10% of all words. What remains still has hundreds of stretches of several dozen consecutive words without any '*'. Even if the text uses some fancy encryption and/or is in some "exotic" language, those fragments should be enough to decipher it. I cannot imagine an encryption scheme that would be viable for a text of that size and could have been conceived in that epoch, but cannot be deciphered without knowing every character of the text. And in fact we know that the Zipf plot and word entropy of the text are similar to those of natural languages. Even if the text is encrypted, these results indicate that the encryption is one-to-one on the lexicon (the set of all words). That would exclude Vigenère-type ciphers, unless the key is synchronized at each word boundary. So, are those fragments still "bumpy"? Quote:Line patterns at different positions of the text are serious problems for any idea that we are only seeing a natural language. Considering the above conjectures for one-leg gallows and m/g, I don't think they are a significant problem. Quote:I find it interesting in that it could imply that if we have copying scribes following a layout by an "Author", they have agency in terms of how they lay out the text: they are not obliged to match their line starts with the Author's line starts, nor their line ends with the Author's line ends by cramming in text or widening spaces between words to make the ends match. This is almost certainly the case, even if the text was encrypted. The parag breaks would (usually) be clear in the draft, and the Scribe would have to respect them. However, within each parag, the line breaks in the draft would be determined by the width of the paper and the size of the Author's handwriting, and would not be significant. The line breaks in the vellum version would be expected to be different, and neither would have any significance (except that they would count as word spaces). Said another way: if line breaks were significant (as in a poem, song, list, etc.) we would expect the lines to have variable lengths. The fact that they are all of about the same length, except at the ends of paragraphs, is strong evidence that the line breaks were chosen "on the fly" wherever the writing reached the right margin. Quote: Given how word types seem to undergo complex mutations at these positions I question whether there are "bumps" at line breaks. If we look only at line breaks within a parag, excluding the parag breaks, do we still see such anomalies? Are they statistically significant? Quote:By Top Row, I mean the first line of each paragraph but with its first word and last word omitted so as to isolate a top row effect from separate paragraph/line start effects and line end effects. This is not sufficient, since the second word on the first line of a parag may have one-leg gallows, or may be special in some other way. To look for line break anomalies, one should exclude the first line of the parag entirely, and look only at internal breaks. |