18-02-2026, 10:35 PM
(18-02-2026, 08:30 PM)rikforto Wrote: You are not allowed to view links. Register or Login to view.I had some time to actually dig into this this morning
Thank you very much for taking the time to do this verification!
I will look carefully into it, but I have two quick comments:
1. Apologies for the mix of traditional and simplified characters. As it says in the comments at the head of my file, it is derived mainly from You are not allowed to view links. Register or Login to view. that uses mixed character set, presumably because it was created piecemeal by users from the two "characterlands". I was not quite aware of the problem at the time, and assumed that the mixing was okay. There is You are not allowed to view links. Register or Login to view. that lets the user choose the character set, and I used it to check and complete that Wikisource file. The contents if the two files seemed to be mostly the same, but there were a few differences and bugs.
For one thing, they were in different orders. The Wikisource had six sections, each with three subsections, whereas the other one was the other way around; which IIUC is the "classical" order. I reordered the file according to the latter.
And there were a few recipes classified as different "grades" by the two files. And two cases in one file where two recipes had been joined into one. And each file had a few recipes that were missing in the other.
Even after fixing those bugs, I had only 359 recipes instead of the 365 which was supposed to be the classical number.
These difficulties should be familiar to anyone who has tried to prepare a book as a digital file suitable for analysis. Ask @MarcoP. I faced them 20 years ago when I was collecting my language samples. (When my students complained that I was too picky on their theses, I would boast that, oh yeah, I also had to fix quite a few errors in the Torah and the Quran.)
One further problem that I discovered when trying to typeset that Rooster recipe in LaTeX is that some characters in the SBJ are so rare that they are missing in both the "traditional" and "simplified" font packages. A couple of them occur in that "Rooster" recipe. That is why Google AI insisted that I switch from pdflatex to xetex, which can typeset any Unicode character, including mixed text and those rare characters.
I will try to uniformize the file to either one of the two sets, to the extent possible. (I lean towards the simplified one because I can read and recognize its characters better. But I understand that scholars will find them kinda blasphemous --- like typesetting Shakespeare in Helvetica.)
2. That repeated character 膠 = "gelatin, glue" you spotted in the "donkey hide gelatin" recipe 阿膠 is in the last sentence 一名傳致膠 which means "Also known as" (literally "one name") "Chuán Zhì glue".
Like the "taste and warmth" and "grows in..." fields of the Rooster recipe, that is the sort of information that seems to have been omitted in the SPS version -- presumably because the VMS Author thought that it was nonsensical or would be useless to him.
3. You write:
Quote:I would like to reiterate: a spurious correlation between those 7 instances of 主 in the rooster paragraph and the loose family of words daiin/dain/laiin in the SPS still adequately explains the difficulties extending the match. There is no need to appeal to undiscovered versions of the SBJ, translators, dictators, L2 scribes, retracers, or any other person or force frustrating our efforts. The null hypothesis, that the SPS does not match the SBJ, is perfectly capable of explaining why we are having such difficulty mapping Voynichese to the SBJ, even if it is not uniquely capable.
Sure, the difficulties of finding further matches would be perfectly explained by the "null hypothesis" that the match between f105v.32-28 and the Rooster recipe is spurious, just six random coincidences.
But what this "null hypothesis" cannot explain is that match itself.
All the best, --stolfi
