<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[The Voynich Ninja - Analysis of the text]]></title>
		<link>https://www.voynich.ninja/</link>
		<description><![CDATA[The Voynich Ninja - https://www.voynich.ninja]]></description>
		<pubDate>Sat, 12 Sep 2026 15:15:00 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Regimen Sanitatis Salernitanum = Stars?]]></title>
			<link>https://www.voynich.ninja/thread-6058.html</link>
			<pubDate>Sat, 05 Sep 2026 15:32:29 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3052">JoJo_Jost</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-6058.html</guid>
			<description><![CDATA[I don’t know if this has already been discussed here, but could it be that the “Stars” are related to something like the “Regimen Sanitatis Salernitanum” (also known as “Flos medicinae” or “Flores medicinae Salerni”)?<br />
<br />
I came across it in Sir Alexander Croke’s 1830 edition. According to Croke, these are Latin didactic poems associated with the medical school of Salerno that deal primarily with the preservation of health.<br />
<br />
Its subject matter is health in the medieval sense: eating and drinking, sleep, air, the properties of individual foods, wine, and herbs; the four bodily humors (blood, bile, phlegm, and melancholy) and their corresponding temperaments; and an extensive section on the practice of bloodletting.<br />
<br />
Much of the text is written in rhymed hexameter, often in the tradition of Leonine verse, which presumably contributed to its mnemonic character and popularity.<br />
<br />
The work has not been preserved as a single, fixed text. Various manuscripts contain very different numbers of verses, as well as different additions and arrangements. <span style="font-weight: bold;" class="mycode_b">Croke’s base text comprises 363 lines of verse (That's why I thought of the stars first),</span> but then he mentions manuscripts with 183, 664, 1,073, 1,096, and 1,239 verse.<br />
<br />
Modern scholarship generally regards the “Regimen” as a composite and evolving text rather than the work of a clearly identified author. Its exact date of origin and early development are disputed; the core tradition dates to the Middle Ages—roughly the 12th century—and was already widely disseminated long before the 15th century.<br />
<br />
Sources:<br />
You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.<br />
<br />
You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.<br />
<br />
You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">
<br />
<img src="https://www.voynich.ninja/images/attachtypes/txt.png" title="Text Document" border="0" alt=".txt" />
&nbsp;&nbsp;<a href="attachment.php?aid=17547" target="_blank" title="">regimen_salernitanum_thematic_latin_english.txt</a> (Size: 55.25 KB / Downloads: 8)
</span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">Note: </span>It was too time-consuming for me to extract them all, so I had an AI do it, double-checked the results, found some errors, ran it again, and again. I hope it’s at least somewhat correct now—the English translations were also done by the AI. I  include the URL of the original, after all...]]></description>
			<content:encoded><![CDATA[I don’t know if this has already been discussed here, but could it be that the “Stars” are related to something like the “Regimen Sanitatis Salernitanum” (also known as “Flos medicinae” or “Flores medicinae Salerni”)?<br />
<br />
I came across it in Sir Alexander Croke’s 1830 edition. According to Croke, these are Latin didactic poems associated with the medical school of Salerno that deal primarily with the preservation of health.<br />
<br />
Its subject matter is health in the medieval sense: eating and drinking, sleep, air, the properties of individual foods, wine, and herbs; the four bodily humors (blood, bile, phlegm, and melancholy) and their corresponding temperaments; and an extensive section on the practice of bloodletting.<br />
<br />
Much of the text is written in rhymed hexameter, often in the tradition of Leonine verse, which presumably contributed to its mnemonic character and popularity.<br />
<br />
The work has not been preserved as a single, fixed text. Various manuscripts contain very different numbers of verses, as well as different additions and arrangements. <span style="font-weight: bold;" class="mycode_b">Croke’s base text comprises 363 lines of verse (That's why I thought of the stars first),</span> but then he mentions manuscripts with 183, 664, 1,073, 1,096, and 1,239 verse.<br />
<br />
Modern scholarship generally regards the “Regimen” as a composite and evolving text rather than the work of a clearly identified author. Its exact date of origin and early development are disputed; the core tradition dates to the Middle Ages—roughly the 12th century—and was already widely disseminated long before the 15th century.<br />
<br />
Sources:<br />
You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.<br />
<br />
You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.<br />
<br />
You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">
<br />
<img src="https://www.voynich.ninja/images/attachtypes/txt.png" title="Text Document" border="0" alt=".txt" />
&nbsp;&nbsp;<a href="attachment.php?aid=17547" target="_blank" title="">regimen_salernitanum_thematic_latin_english.txt</a> (Size: 55.25 KB / Downloads: 8)
</span><br />
<br />
<span style="font-weight: bold;" class="mycode_b">Note: </span>It was too time-consuming for me to extract them all, so I had an AI do it, double-checked the results, found some errors, ran it again, and again. I hope it’s at least somewhat correct now—the English translations were also done by the AI. I  include the URL of the original, after all...]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Deconstructing the VMS : gallows as lipstick (part 2)]]></title>
			<link>https://www.voynich.ninja/thread-6051.html</link>
			<pubDate>Tue, 01 Sep 2026 14:34:14 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3074">Dunsel</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-6051.html</guid>
			<description><![CDATA[Part 1 can be found here: You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.<br />
<br />
I know there's a lot of data in this post and I tried to summarize as best as I could. I tried to break it down into sections to make it more readable.<br />
<br />
I'll start with the full Voynich ledger which shows the legal letter transitions for the entire corpus, including gallows.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">All scribes: non-stripped gallows + hapax</span></span><br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Prefix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Core midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Rare midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Suffix</strong></th></tr>
<tr class="trowaltern"><td valign="top">a</td><td valign="top">l, r, i</td><td valign="top">a, o, d, ch, sh, e, y, s, m, n, x, c, f, k, p, t</td><td valign="top">d, l, sh, y, s, r, m, n, g, i, p, t</td></tr>
<tr class="trowaltern"><td valign="top">o</td><td valign="top">a, o, d, l, ch, sh, e, s, r, i</td><td valign="top">y, q, h, m, g, x, c, f, k, p, t</td><td valign="top">o, d, l, sh, e, y, s, r, m, n, g, x, c, f, k, p, t</td></tr>
<tr class="trowaltern"><td valign="top">d</td><td valign="top">a, o, ch, sh, e</td><td valign="top">d, l, y, s, r, x, c, i, f, k, p, t</td><td valign="top">a, o, d, l, sh, e, y, s, r, m, g</td></tr>
<tr class="trowaltern"><td valign="top">l</td><td valign="top">a, o, d, ch, sh</td><td valign="top">l, e, y, s, r, q, m, g, x, c, i, f, k, p, t</td><td valign="top">a, o, d, l, sh, e, y, s, r, m, g, k, p</td></tr>
<tr class="trowaltern"><td valign="top">ch</td><td valign="top">a, o, d, e</td><td valign="top">l, ch, sh, y, s, r, h, x, c, i, f, k, p, t</td><td valign="top">a, o, d, l, e, y, s, r, m, g, x, k</td></tr>
<tr class="trowaltern"><td valign="top">sh</td><td valign="top">a, o, d, ch, e</td><td valign="top">l, sh, y, s, h, x, c, f, k, t</td><td valign="top">a, o, d, l, e, y, s, r, x</td></tr>
<tr class="trowaltern"><td valign="top">e</td><td valign="top">a, o, d, e</td><td valign="top">l, ch, sh, y, s, r, h, m, g, c, i, f, k, p, t</td><td valign="top">a, o, d, l, ch, e, y, s, r, m, n, g, f, k, p, t</td></tr>
<tr class="trowaltern"><td valign="top">y</td><td valign="top">a, d, ch, sh</td><td valign="top">o, l, e, s, r, q, h, c, i, f, k, p, t</td><td valign="top">o, d, l, y, s, r, m, k, t</td></tr>
<tr class="trowaltern"><td valign="top">s</td><td valign="top">a, o, ch, sh, e</td><td valign="top">d, y, s, q, c, i, f, k, p, t</td><td valign="top">a, o, d, l, e, y, s, r, m, n</td></tr>
<tr class="trowaltern"><td valign="top">r</td><td valign="top">a, o, ch</td><td valign="top">d, l, sh, e, y, r, x, c, i, f, k, p, t</td><td valign="top">a, o, d, l, ch, e, y, s, r, m, g, k</td></tr>
<tr class="trowaltern"><td valign="top">q</td><td valign="top">o</td><td valign="top">a, l, ch, e, y, s, c, f, k, p, t</td><td valign="top">o</td></tr>
<tr class="trowaltern"><td valign="top">h</td><td valign="top">—</td><td valign="top">a, o, d, ch, e, y, s, h, c, i, k</td><td valign="top">a, o, d, l, y, s, r, h, g</td></tr>
<tr class="trowaltern"><td valign="top">m</td><td valign="top">—</td><td valign="top">a, o, d, ch, sh</td><td valign="top">o, d, y, m, g</td></tr>
<tr class="trowaltern"><td valign="top">n</td><td valign="top">—</td><td valign="top">a, o, d, r</td><td valign="top">o, d, e, y, m, n</td></tr>
<tr class="trowaltern"><td valign="top">g</td><td valign="top">—</td><td valign="top">a, o, e</td><td valign="top">l, y</td></tr>
<tr class="trowaltern"><td valign="top">x</td><td valign="top">—</td><td valign="top">a, o</td><td valign="top">y</td></tr>
<tr class="trowaltern"><td valign="top">c</td><td valign="top">s</td><td valign="top">o, sh, c, f, k, p, t</td><td valign="top">o, y, s, f, t</td></tr>
<tr class="trowaltern"><td valign="top">i</td><td valign="top">d, r, i</td><td valign="top">a, o, l, ch, sh, e, s, h, m, n, c, f, k, p, t</td><td valign="top">o, d, l, y, s, r, m, n, x, i, p, t</td></tr>
<tr class="trowaltern"><td valign="top">f</td><td valign="top">—</td><td valign="top">a, o, d, ch, sh, e, y, s, h, c</td><td valign="top">o, y</td></tr>
<tr class="trowaltern"><td valign="top">k</td><td valign="top">—</td><td valign="top">a, o, d, l, ch, sh, e, y, s, r, h, c, i</td><td valign="top">a, o, d, l, ch, sh, y, h, g</td></tr>
<tr class="trowaltern"><td valign="top">p</td><td valign="top">—</td><td valign="top">a, o, d, ch, sh, e, y, s, h, c, i</td><td valign="top">a, o, ch, y</td></tr>
<tr class="trowaltern"><td valign="top">t</td><td valign="top">—</td><td valign="top">a, o, d, l, ch, sh, e, y, s, h, g, c, i, k</td><td valign="top">a, o, l, ch, sh, e, y, s, h</td></tr>
</table>
<br />
And here's the ledger with gallows stripped from words.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">All scribes: gallows stripped + hapax</span></span><br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Prefix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Core midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Rare midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Suffix</strong></th></tr>
<tr class="trowaltern"><td valign="top">a</td><td valign="top">l, r, i</td><td valign="top">a, o, d, ch, sh, e, y, s, m, n, x, c</td><td valign="top">d, l, sh, y, s, r, m, n, g, i</td></tr>
<tr class="trowaltern"><td valign="top">o</td><td valign="top">a, o, d, l, ch, sh, e, s, r, i</td><td valign="top">y, q, h, m, g, x, c</td><td valign="top">a, o, d, l, ch, sh, e, y, s, r, m, n, g, x, c</td></tr>
<tr class="trowaltern"><td valign="top">d</td><td valign="top">a, o, ch, sh, e</td><td valign="top">d, l, y, s, r, x, c, i</td><td valign="top">a, o, d, l, sh, e, y, s, r, m, g</td></tr>
<tr class="trowaltern"><td valign="top">l</td><td valign="top">a, o, d, ch, sh</td><td valign="top">l, e, y, s, r, q, m, g, x, c, i</td><td valign="top">a, o, d, l, ch, sh, e, y, s, r, m, g</td></tr>
<tr class="trowaltern"><td valign="top">ch</td><td valign="top">a, o, d, e</td><td valign="top">l, ch, sh, y, s, r, h, x, c, i</td><td valign="top">a, o, d, l, ch, e, y, s, r, h, m, g, x, c</td></tr>
<tr class="trowaltern"><td valign="top">sh</td><td valign="top">a, o, d, ch, e</td><td valign="top">l, sh, y, s, h, x, c</td><td valign="top">a, o, d, l, e, y, s, r, x</td></tr>
<tr class="trowaltern"><td valign="top">e</td><td valign="top">a, o, d, e</td><td valign="top">l, ch, sh, y, s, r, h, m, g, c, i</td><td valign="top">a, o, d, l, ch, e, y, s, r, m, n, g</td></tr>
<tr class="trowaltern"><td valign="top">y</td><td valign="top">a, d, ch, sh</td><td valign="top">o, l, e, y, s, r, q, h, c, i</td><td valign="top">a, o, d, l, ch, sh, y, s, r, m</td></tr>
<tr class="trowaltern"><td valign="top">s</td><td valign="top">a, o, ch, sh, e</td><td valign="top">d, y, s, q, c, i</td><td valign="top">a, o, d, l, e, y, s, r, m, n</td></tr>
<tr class="trowaltern"><td valign="top">r</td><td valign="top">a, o, ch</td><td valign="top">d, l, sh, e, y, r, x, c, i</td><td valign="top">a, o, d, l, ch, e, y, s, r, m, g</td></tr>
<tr class="trowaltern"><td valign="top">q</td><td valign="top">o</td><td valign="top">a, l, ch, e, y, s, h</td><td valign="top">o, e</td></tr>
<tr class="trowaltern"><td valign="top">h</td><td valign="top">—</td><td valign="top">a, o, d, ch, e, y, h</td><td valign="top">d, y, g</td></tr>
<tr class="trowaltern"><td valign="top">m</td><td valign="top">—</td><td valign="top">a, o, d, ch, sh</td><td valign="top">o, d, y, m, g</td></tr>
<tr class="trowaltern"><td valign="top">n</td><td valign="top">—</td><td valign="top">a, o, d, r</td><td valign="top">o, d, e, y, m, n</td></tr>
<tr class="trowaltern"><td valign="top">g</td><td valign="top">—</td><td valign="top">a, o, e</td><td valign="top">l, y</td></tr>
<tr class="trowaltern"><td valign="top">x</td><td valign="top">—</td><td valign="top">a, o</td><td valign="top">y</td></tr>
<tr class="trowaltern"><td valign="top">c</td><td valign="top">s</td><td valign="top">a, o, ch, sh, e</td><td valign="top">a, o, y, s</td></tr>
<tr class="trowaltern"><td valign="top">i</td><td valign="top">d, r, i</td><td valign="top">a, o, l, ch, sh, e, s, h, m, n</td><td valign="top">a, o, d, l, y, s, r, m, n, x, i</td></tr>
</table>
<br />
The above ledgers are for the full corpus.  But each scribe had their own subset of this ledger so it became much easier to work with.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Scribe 1 core ledger</span><br />
<br />
Gallows and hapax words do use the core transitions from the ledger, but they also expand the ledger.  So, if we make a simple assumption, that the scribe begins with just the ledger for the core words and adds in transitions as they're needed, Scribe 1 starts with this very simple ledger.<br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Prefix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Core midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Rare midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Suffix</strong></th></tr>
<tr class="trowaltern"><td valign="top">a</td><td valign="top">i, l, r</td><td valign="top">d, m</td><td valign="top">l, m, n, r</td></tr>
<tr class="trowaltern"><td valign="top">o</td><td valign="top">a, ch, d, e, i, l, o, r</td><td valign="top">s, sh</td><td valign="top">d, g, l, m, r, s, y</td></tr>
<tr class="trowaltern"><td valign="top">d</td><td valign="top">a, ch, e, o, sh</td><td valign="top">d</td><td valign="top">y</td></tr>
<tr class="trowaltern"><td valign="top">l</td><td valign="top">a, ch, d, o</td><td valign="top">e, s, sh</td><td valign="top">o, s, y</td></tr>
<tr class="trowaltern"><td valign="top">ch</td><td valign="top">a, d, e, o</td><td valign="top">—</td><td valign="top">a, l, o, r, s, y</td></tr>
<tr class="trowaltern"><td valign="top">sh</td><td valign="top">a, e, o</td><td valign="top">d</td><td valign="top">e, o, y</td></tr>
<tr class="trowaltern"><td valign="top">e</td><td valign="top">a, e, o</td><td valign="top">d</td><td valign="top">e, n, o, s, y</td></tr>
<tr class="trowaltern"><td valign="top">y</td><td valign="top">ch, d</td><td valign="top">o, s, sh</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">s</td><td valign="top">a, ch, o</td><td valign="top">—</td><td valign="top">y</td></tr>
<tr class="trowaltern"><td valign="top">r</td><td valign="top">a</td><td valign="top">d, i, o</td><td valign="top">l, o, y</td></tr>
<tr class="trowaltern"><td valign="top">q</td><td valign="top">o</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">h</td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">m</td><td valign="top">—</td><td valign="top">—</td><td valign="top">o</td></tr>
<tr class="trowaltern"><td valign="top">n</td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">g</td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">x</td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">c</td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">i</td><td valign="top">i</td><td valign="top">d, r</td><td valign="top">m, n, r, s</td></tr>
</table>
<br />
While there isn't enough room to show a ledger for each scribe, this heatmap shows how many scribes use each transition. The scribes clearly share a large common set of transitions, but their ledgers are not identical. Each scribe also uses some transitions that the others do not.<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17510" target="_blank" title="">Codex Image Aug 23, 2026, 06_05_14 PM.png</a> (Size: 31.66 KB / Downloads: 147)
<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Gallows as lipstick - why I chose to strip gallows</span></span><br />
<br />
The gallows-stripping decision was not arbitrary. It came from several independent tests that all pointed in the same direction.  And I'm very likely reproducing some work of others that I'm unaware of, my apologies if I am.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Copies and ED1 from other words</span><br />
<br />
First, if you strip the gallows from words you find these results<br />
<ul class="mycode_list"><li>9,907, or 56.79%, were exact copies of a word already occurring earlier in manuscript order. <br />
</li>
<li>6,784, or 38.89%, were ED1, specifically Damerau-Levenshtein distance 1, from an earlier word. <br />
</li>
<li>Only 754, or 4.32%, were neither.<br />
</li>
</ul>
<br />
95.68% of all  stripped gallows tokens were either an exact earlier word or only one edit away from an earlier word.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Stripping gallows adds almost nothing to the underlying ledger.</span><br />
<br />
With gallows intact, the ledger has 288 midfix transitions and 186 suffix transitions. After stripping f, k, p and t, that drops to 187 midfix transitions and 148 suffix transitions.  More importantly, the core and rare transition inventories don't change at all. The core remains 53 midfix and 40 suffix transitions, and the rare remains 31 midfix and 23 suffix transitions.<br />
<br />
Stripping can create a new transition where a gallows used to sit between two letters, but across the entire ledger it adds only four new ordered pairs: C→A, C→CH, C→E and Q→H. By comparison, leaving the gallows intact requires 185 gallows-specific midfix and suffix transitions.<br />
<br />
So this is what I mean when I say stripping the gallows exposes the underlying ledger. Almost all of the extra transition machinery comes from the gallows themselves. Remove them and nearly all of it disappears while the core and rare ledger remains unchanged.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Gallows swapping</span><br />
<br />
If you look at the ledger above with gallows included, you may notice that the midfix and suffix transitions for K &amp; T and P &amp; F are very similar. So I asked, if I took all gallows words and swapped the gallows with it's 'pair' how many ledger legal words would that create.<br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Swap</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Tested</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Still legal</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Rate</strong></th></tr>
<tr class="trowaltern"><td valign="top">K → T</td><td valign="top">9,608</td><td valign="top">9,599</td><td valign="top">99.91%</td></tr>
<tr class="trowaltern"><td valign="top">T → K</td><td valign="top">6,224</td><td valign="top">6,215</td><td valign="top">99.86%</td></tr>
<tr class="trowaltern"><td valign="top">P → F</td><td valign="top">1,411</td><td valign="top">1,403</td><td valign="top">99.43%</td></tr>
<tr class="trowaltern"><td valign="top">F → P</td><td valign="top">421</td><td valign="top">419</td><td valign="top">99.52%</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Combined</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">17,664</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">17,636</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">99.84%</span></td></tr>
</table>
<br />
The result is about as close to interchangeable as you could expect. Out of 17,664 possible sibling swaps, 17,636 remain legal, or 99.84%.<br />
<br />
It gets even stronger when we look at position. Every initial swap works, 2,377/2,377. Internal swaps work 13,914/13,919 times, or 99.96%. Almost all of the failures are near the end of the word, where suffix restrictions come into play.<br />
<br />
And this isn't just something the ledger allows. ZLZB and TTLI independently disagree on a single gallows 113 times. 102 of those 113 disagreements, 90.27%, are exactly these sibling swaps: 85 K/T and 17 P/F. They occur in both directions, K→T and T→K, P→F and F→P. <br />
<br />
So the ledger says K/T and P/F can almost always occupy the same structural position, and when the two transcriptions disagree over a single gallows, the disagreement is overwhelmingly K/T or P/F.<br />
<br />
One other oddity I noticed in the gallows words is initial i. Across all five scribes there isn't a single retained core word beginning with i. The only six i-initial words are all gallows-bearing. I don't know what that means, but it is another indication that gallows constructions have some peculiarities of their own.<br />
<br />
Now, I do personally tend to think of them as decorative but that's just my opinion and it was convenient for me to think of them as such. But, that doesn't mean gallows are meaningless. It doesn't even tell us whether the gallows were added before or after the rest of the word. And while my use of the word lipstick may be a tad dramatic, there are probably a bunch more tests that should be run before Estée Lauder could claim a trademark.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Scribal Ledger Comparisons</span></span><br />
<br />
Scribes 4 and 5 do have a limited vocabulary compared to the other scribes so that should be noted.  I won't go into extreme depth on these comparisons but suffice it to say that while the scribes did share a large common transition set, they were not identical.<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17511" target="_blank" title="">Codex Image Aug 23, 2026, 06_20_12 PM.png</a> (Size: 34.9 KB / Downloads: 145)
<br />
<br />
This compares the pooled all-scribes ledger with the five individual scribe ledgers. The numbers show how many scribes use each transition. The orange P marks transitions that enter the core + rare inventory only when the scribes are pooled together. Most of the pooled ledger is therefore made up of transitions already present in one or more individual core + rare ledgers, with only a small number changing status through pooling.<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17512" target="_blank" title="">Codex Image Aug 23, 2026, 06_05_31 PM.png</a> (Size: 34.2 KB / Downloads: 144)
<br />
This compares the actual core + rare transition inventories of each scribe using Jaccard similarity. Scribes 1–4 are fairly close to one another, with Scribe 2 and Scribe 3 the most similar at 0.75. Scribe 5 is the clear outlier, sharing only about 0.40–0.53 of its transition inventory with the others. So the scribes are clearly using the same general transition system, but not identical copies of the same ledger.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Hapax</span></span><br />
<br />
Hapax look more irregular than repeated words, but most of that irregularity appears to be local to the individual scribe.<br />
<br />
Across the five scribes there are 1,817 nongallows scribe-specific hapax. Only 664, or 36.54%, are completely covered by that scribe's own core ledger.  But when those same hapax are tested against the pooled all-scribes core, 1,297 of 1,817, or 71.38%, are completely legal.  So in most cases the "new" structure in a hapax isn't actually new to the manuscript. It is simply something that particular scribe only used once.<br />
<br />
There is also a very nice control using gallows words. If you split stripped gallows words according to whether they occur once or repeatedly:<br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Population</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Own-scribe core</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>All-scribe core</strong></th></tr>
<tr class="trowaltern"><td valign="top">Nongallows hapax</td><td valign="top">36.54%</td><td valign="top">71.38%</td></tr>
<tr class="trowaltern"><td valign="top">One-off gallows</td><td valign="top">43.59%</td><td valign="top">69.03%</td></tr>
<tr class="trowaltern"><td valign="top">Repeated gallows</td><td valign="top">73.18%</td><td valign="top">90.32%</td></tr>
</table>
<br />
One-off gallows words behave almost exactly like ordinary hapax, while repeated gallows words behave much more like core words. That suggests rarity is doing more of the work than whether the word contains a gallows.<br />
<br />
Again, I have a good bit more data on this but this is the core of what I'm seeing.<br />
<br />
In the final post on this topic, I'll provide the repo for my python files so you can reproduce any of these findings with Takahashi or Zandbergen/Landini transcriptions.]]></description>
			<content:encoded><![CDATA[Part 1 can be found here: You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.<br />
<br />
I know there's a lot of data in this post and I tried to summarize as best as I could. I tried to break it down into sections to make it more readable.<br />
<br />
I'll start with the full Voynich ledger which shows the legal letter transitions for the entire corpus, including gallows.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">All scribes: non-stripped gallows + hapax</span></span><br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Prefix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Core midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Rare midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Suffix</strong></th></tr>
<tr class="trowaltern"><td valign="top">a</td><td valign="top">l, r, i</td><td valign="top">a, o, d, ch, sh, e, y, s, m, n, x, c, f, k, p, t</td><td valign="top">d, l, sh, y, s, r, m, n, g, i, p, t</td></tr>
<tr class="trowaltern"><td valign="top">o</td><td valign="top">a, o, d, l, ch, sh, e, s, r, i</td><td valign="top">y, q, h, m, g, x, c, f, k, p, t</td><td valign="top">o, d, l, sh, e, y, s, r, m, n, g, x, c, f, k, p, t</td></tr>
<tr class="trowaltern"><td valign="top">d</td><td valign="top">a, o, ch, sh, e</td><td valign="top">d, l, y, s, r, x, c, i, f, k, p, t</td><td valign="top">a, o, d, l, sh, e, y, s, r, m, g</td></tr>
<tr class="trowaltern"><td valign="top">l</td><td valign="top">a, o, d, ch, sh</td><td valign="top">l, e, y, s, r, q, m, g, x, c, i, f, k, p, t</td><td valign="top">a, o, d, l, sh, e, y, s, r, m, g, k, p</td></tr>
<tr class="trowaltern"><td valign="top">ch</td><td valign="top">a, o, d, e</td><td valign="top">l, ch, sh, y, s, r, h, x, c, i, f, k, p, t</td><td valign="top">a, o, d, l, e, y, s, r, m, g, x, k</td></tr>
<tr class="trowaltern"><td valign="top">sh</td><td valign="top">a, o, d, ch, e</td><td valign="top">l, sh, y, s, h, x, c, f, k, t</td><td valign="top">a, o, d, l, e, y, s, r, x</td></tr>
<tr class="trowaltern"><td valign="top">e</td><td valign="top">a, o, d, e</td><td valign="top">l, ch, sh, y, s, r, h, m, g, c, i, f, k, p, t</td><td valign="top">a, o, d, l, ch, e, y, s, r, m, n, g, f, k, p, t</td></tr>
<tr class="trowaltern"><td valign="top">y</td><td valign="top">a, d, ch, sh</td><td valign="top">o, l, e, s, r, q, h, c, i, f, k, p, t</td><td valign="top">o, d, l, y, s, r, m, k, t</td></tr>
<tr class="trowaltern"><td valign="top">s</td><td valign="top">a, o, ch, sh, e</td><td valign="top">d, y, s, q, c, i, f, k, p, t</td><td valign="top">a, o, d, l, e, y, s, r, m, n</td></tr>
<tr class="trowaltern"><td valign="top">r</td><td valign="top">a, o, ch</td><td valign="top">d, l, sh, e, y, r, x, c, i, f, k, p, t</td><td valign="top">a, o, d, l, ch, e, y, s, r, m, g, k</td></tr>
<tr class="trowaltern"><td valign="top">q</td><td valign="top">o</td><td valign="top">a, l, ch, e, y, s, c, f, k, p, t</td><td valign="top">o</td></tr>
<tr class="trowaltern"><td valign="top">h</td><td valign="top">—</td><td valign="top">a, o, d, ch, e, y, s, h, c, i, k</td><td valign="top">a, o, d, l, y, s, r, h, g</td></tr>
<tr class="trowaltern"><td valign="top">m</td><td valign="top">—</td><td valign="top">a, o, d, ch, sh</td><td valign="top">o, d, y, m, g</td></tr>
<tr class="trowaltern"><td valign="top">n</td><td valign="top">—</td><td valign="top">a, o, d, r</td><td valign="top">o, d, e, y, m, n</td></tr>
<tr class="trowaltern"><td valign="top">g</td><td valign="top">—</td><td valign="top">a, o, e</td><td valign="top">l, y</td></tr>
<tr class="trowaltern"><td valign="top">x</td><td valign="top">—</td><td valign="top">a, o</td><td valign="top">y</td></tr>
<tr class="trowaltern"><td valign="top">c</td><td valign="top">s</td><td valign="top">o, sh, c, f, k, p, t</td><td valign="top">o, y, s, f, t</td></tr>
<tr class="trowaltern"><td valign="top">i</td><td valign="top">d, r, i</td><td valign="top">a, o, l, ch, sh, e, s, h, m, n, c, f, k, p, t</td><td valign="top">o, d, l, y, s, r, m, n, x, i, p, t</td></tr>
<tr class="trowaltern"><td valign="top">f</td><td valign="top">—</td><td valign="top">a, o, d, ch, sh, e, y, s, h, c</td><td valign="top">o, y</td></tr>
<tr class="trowaltern"><td valign="top">k</td><td valign="top">—</td><td valign="top">a, o, d, l, ch, sh, e, y, s, r, h, c, i</td><td valign="top">a, o, d, l, ch, sh, y, h, g</td></tr>
<tr class="trowaltern"><td valign="top">p</td><td valign="top">—</td><td valign="top">a, o, d, ch, sh, e, y, s, h, c, i</td><td valign="top">a, o, ch, y</td></tr>
<tr class="trowaltern"><td valign="top">t</td><td valign="top">—</td><td valign="top">a, o, d, l, ch, sh, e, y, s, h, g, c, i, k</td><td valign="top">a, o, l, ch, sh, e, y, s, h</td></tr>
</table>
<br />
And here's the ledger with gallows stripped from words.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">All scribes: gallows stripped + hapax</span></span><br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Prefix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Core midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Rare midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Suffix</strong></th></tr>
<tr class="trowaltern"><td valign="top">a</td><td valign="top">l, r, i</td><td valign="top">a, o, d, ch, sh, e, y, s, m, n, x, c</td><td valign="top">d, l, sh, y, s, r, m, n, g, i</td></tr>
<tr class="trowaltern"><td valign="top">o</td><td valign="top">a, o, d, l, ch, sh, e, s, r, i</td><td valign="top">y, q, h, m, g, x, c</td><td valign="top">a, o, d, l, ch, sh, e, y, s, r, m, n, g, x, c</td></tr>
<tr class="trowaltern"><td valign="top">d</td><td valign="top">a, o, ch, sh, e</td><td valign="top">d, l, y, s, r, x, c, i</td><td valign="top">a, o, d, l, sh, e, y, s, r, m, g</td></tr>
<tr class="trowaltern"><td valign="top">l</td><td valign="top">a, o, d, ch, sh</td><td valign="top">l, e, y, s, r, q, m, g, x, c, i</td><td valign="top">a, o, d, l, ch, sh, e, y, s, r, m, g</td></tr>
<tr class="trowaltern"><td valign="top">ch</td><td valign="top">a, o, d, e</td><td valign="top">l, ch, sh, y, s, r, h, x, c, i</td><td valign="top">a, o, d, l, ch, e, y, s, r, h, m, g, x, c</td></tr>
<tr class="trowaltern"><td valign="top">sh</td><td valign="top">a, o, d, ch, e</td><td valign="top">l, sh, y, s, h, x, c</td><td valign="top">a, o, d, l, e, y, s, r, x</td></tr>
<tr class="trowaltern"><td valign="top">e</td><td valign="top">a, o, d, e</td><td valign="top">l, ch, sh, y, s, r, h, m, g, c, i</td><td valign="top">a, o, d, l, ch, e, y, s, r, m, n, g</td></tr>
<tr class="trowaltern"><td valign="top">y</td><td valign="top">a, d, ch, sh</td><td valign="top">o, l, e, y, s, r, q, h, c, i</td><td valign="top">a, o, d, l, ch, sh, y, s, r, m</td></tr>
<tr class="trowaltern"><td valign="top">s</td><td valign="top">a, o, ch, sh, e</td><td valign="top">d, y, s, q, c, i</td><td valign="top">a, o, d, l, e, y, s, r, m, n</td></tr>
<tr class="trowaltern"><td valign="top">r</td><td valign="top">a, o, ch</td><td valign="top">d, l, sh, e, y, r, x, c, i</td><td valign="top">a, o, d, l, ch, e, y, s, r, m, g</td></tr>
<tr class="trowaltern"><td valign="top">q</td><td valign="top">o</td><td valign="top">a, l, ch, e, y, s, h</td><td valign="top">o, e</td></tr>
<tr class="trowaltern"><td valign="top">h</td><td valign="top">—</td><td valign="top">a, o, d, ch, e, y, h</td><td valign="top">d, y, g</td></tr>
<tr class="trowaltern"><td valign="top">m</td><td valign="top">—</td><td valign="top">a, o, d, ch, sh</td><td valign="top">o, d, y, m, g</td></tr>
<tr class="trowaltern"><td valign="top">n</td><td valign="top">—</td><td valign="top">a, o, d, r</td><td valign="top">o, d, e, y, m, n</td></tr>
<tr class="trowaltern"><td valign="top">g</td><td valign="top">—</td><td valign="top">a, o, e</td><td valign="top">l, y</td></tr>
<tr class="trowaltern"><td valign="top">x</td><td valign="top">—</td><td valign="top">a, o</td><td valign="top">y</td></tr>
<tr class="trowaltern"><td valign="top">c</td><td valign="top">s</td><td valign="top">a, o, ch, sh, e</td><td valign="top">a, o, y, s</td></tr>
<tr class="trowaltern"><td valign="top">i</td><td valign="top">d, r, i</td><td valign="top">a, o, l, ch, sh, e, s, h, m, n</td><td valign="top">a, o, d, l, y, s, r, m, n, x, i</td></tr>
</table>
<br />
The above ledgers are for the full corpus.  But each scribe had their own subset of this ledger so it became much easier to work with.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Scribe 1 core ledger</span><br />
<br />
Gallows and hapax words do use the core transitions from the ledger, but they also expand the ledger.  So, if we make a simple assumption, that the scribe begins with just the ledger for the core words and adds in transitions as they're needed, Scribe 1 starts with this very simple ledger.<br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Prefix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Core midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Rare midfix</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Suffix</strong></th></tr>
<tr class="trowaltern"><td valign="top">a</td><td valign="top">i, l, r</td><td valign="top">d, m</td><td valign="top">l, m, n, r</td></tr>
<tr class="trowaltern"><td valign="top">o</td><td valign="top">a, ch, d, e, i, l, o, r</td><td valign="top">s, sh</td><td valign="top">d, g, l, m, r, s, y</td></tr>
<tr class="trowaltern"><td valign="top">d</td><td valign="top">a, ch, e, o, sh</td><td valign="top">d</td><td valign="top">y</td></tr>
<tr class="trowaltern"><td valign="top">l</td><td valign="top">a, ch, d, o</td><td valign="top">e, s, sh</td><td valign="top">o, s, y</td></tr>
<tr class="trowaltern"><td valign="top">ch</td><td valign="top">a, d, e, o</td><td valign="top">—</td><td valign="top">a, l, o, r, s, y</td></tr>
<tr class="trowaltern"><td valign="top">sh</td><td valign="top">a, e, o</td><td valign="top">d</td><td valign="top">e, o, y</td></tr>
<tr class="trowaltern"><td valign="top">e</td><td valign="top">a, e, o</td><td valign="top">d</td><td valign="top">e, n, o, s, y</td></tr>
<tr class="trowaltern"><td valign="top">y</td><td valign="top">ch, d</td><td valign="top">o, s, sh</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">s</td><td valign="top">a, ch, o</td><td valign="top">—</td><td valign="top">y</td></tr>
<tr class="trowaltern"><td valign="top">r</td><td valign="top">a</td><td valign="top">d, i, o</td><td valign="top">l, o, y</td></tr>
<tr class="trowaltern"><td valign="top">q</td><td valign="top">o</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">h</td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">m</td><td valign="top">—</td><td valign="top">—</td><td valign="top">o</td></tr>
<tr class="trowaltern"><td valign="top">n</td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">g</td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">x</td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">c</td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top">i</td><td valign="top">i</td><td valign="top">d, r</td><td valign="top">m, n, r, s</td></tr>
</table>
<br />
While there isn't enough room to show a ledger for each scribe, this heatmap shows how many scribes use each transition. The scribes clearly share a large common set of transitions, but their ledgers are not identical. Each scribe also uses some transitions that the others do not.<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17510" target="_blank" title="">Codex Image Aug 23, 2026, 06_05_14 PM.png</a> (Size: 31.66 KB / Downloads: 147)
<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Gallows as lipstick - why I chose to strip gallows</span></span><br />
<br />
The gallows-stripping decision was not arbitrary. It came from several independent tests that all pointed in the same direction.  And I'm very likely reproducing some work of others that I'm unaware of, my apologies if I am.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Copies and ED1 from other words</span><br />
<br />
First, if you strip the gallows from words you find these results<br />
<ul class="mycode_list"><li>9,907, or 56.79%, were exact copies of a word already occurring earlier in manuscript order. <br />
</li>
<li>6,784, or 38.89%, were ED1, specifically Damerau-Levenshtein distance 1, from an earlier word. <br />
</li>
<li>Only 754, or 4.32%, were neither.<br />
</li>
</ul>
<br />
95.68% of all  stripped gallows tokens were either an exact earlier word or only one edit away from an earlier word.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Stripping gallows adds almost nothing to the underlying ledger.</span><br />
<br />
With gallows intact, the ledger has 288 midfix transitions and 186 suffix transitions. After stripping f, k, p and t, that drops to 187 midfix transitions and 148 suffix transitions.  More importantly, the core and rare transition inventories don't change at all. The core remains 53 midfix and 40 suffix transitions, and the rare remains 31 midfix and 23 suffix transitions.<br />
<br />
Stripping can create a new transition where a gallows used to sit between two letters, but across the entire ledger it adds only four new ordered pairs: C→A, C→CH, C→E and Q→H. By comparison, leaving the gallows intact requires 185 gallows-specific midfix and suffix transitions.<br />
<br />
So this is what I mean when I say stripping the gallows exposes the underlying ledger. Almost all of the extra transition machinery comes from the gallows themselves. Remove them and nearly all of it disappears while the core and rare ledger remains unchanged.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Gallows swapping</span><br />
<br />
If you look at the ledger above with gallows included, you may notice that the midfix and suffix transitions for K &amp; T and P &amp; F are very similar. So I asked, if I took all gallows words and swapped the gallows with it's 'pair' how many ledger legal words would that create.<br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Swap</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Tested</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Still legal</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Rate</strong></th></tr>
<tr class="trowaltern"><td valign="top">K → T</td><td valign="top">9,608</td><td valign="top">9,599</td><td valign="top">99.91%</td></tr>
<tr class="trowaltern"><td valign="top">T → K</td><td valign="top">6,224</td><td valign="top">6,215</td><td valign="top">99.86%</td></tr>
<tr class="trowaltern"><td valign="top">P → F</td><td valign="top">1,411</td><td valign="top">1,403</td><td valign="top">99.43%</td></tr>
<tr class="trowaltern"><td valign="top">F → P</td><td valign="top">421</td><td valign="top">419</td><td valign="top">99.52%</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Combined</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">17,664</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">17,636</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">99.84%</span></td></tr>
</table>
<br />
The result is about as close to interchangeable as you could expect. Out of 17,664 possible sibling swaps, 17,636 remain legal, or 99.84%.<br />
<br />
It gets even stronger when we look at position. Every initial swap works, 2,377/2,377. Internal swaps work 13,914/13,919 times, or 99.96%. Almost all of the failures are near the end of the word, where suffix restrictions come into play.<br />
<br />
And this isn't just something the ledger allows. ZLZB and TTLI independently disagree on a single gallows 113 times. 102 of those 113 disagreements, 90.27%, are exactly these sibling swaps: 85 K/T and 17 P/F. They occur in both directions, K→T and T→K, P→F and F→P. <br />
<br />
So the ledger says K/T and P/F can almost always occupy the same structural position, and when the two transcriptions disagree over a single gallows, the disagreement is overwhelmingly K/T or P/F.<br />
<br />
One other oddity I noticed in the gallows words is initial i. Across all five scribes there isn't a single retained core word beginning with i. The only six i-initial words are all gallows-bearing. I don't know what that means, but it is another indication that gallows constructions have some peculiarities of their own.<br />
<br />
Now, I do personally tend to think of them as decorative but that's just my opinion and it was convenient for me to think of them as such. But, that doesn't mean gallows are meaningless. It doesn't even tell us whether the gallows were added before or after the rest of the word. And while my use of the word lipstick may be a tad dramatic, there are probably a bunch more tests that should be run before Estée Lauder could claim a trademark.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Scribal Ledger Comparisons</span></span><br />
<br />
Scribes 4 and 5 do have a limited vocabulary compared to the other scribes so that should be noted.  I won't go into extreme depth on these comparisons but suffice it to say that while the scribes did share a large common transition set, they were not identical.<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17511" target="_blank" title="">Codex Image Aug 23, 2026, 06_20_12 PM.png</a> (Size: 34.9 KB / Downloads: 145)
<br />
<br />
This compares the pooled all-scribes ledger with the five individual scribe ledgers. The numbers show how many scribes use each transition. The orange P marks transitions that enter the core + rare inventory only when the scribes are pooled together. Most of the pooled ledger is therefore made up of transitions already present in one or more individual core + rare ledgers, with only a small number changing status through pooling.<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17512" target="_blank" title="">Codex Image Aug 23, 2026, 06_05_31 PM.png</a> (Size: 34.2 KB / Downloads: 144)
<br />
This compares the actual core + rare transition inventories of each scribe using Jaccard similarity. Scribes 1–4 are fairly close to one another, with Scribe 2 and Scribe 3 the most similar at 0.75. Scribe 5 is the clear outlier, sharing only about 0.40–0.53 of its transition inventory with the others. So the scribes are clearly using the same general transition system, but not identical copies of the same ledger.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Hapax</span></span><br />
<br />
Hapax look more irregular than repeated words, but most of that irregularity appears to be local to the individual scribe.<br />
<br />
Across the five scribes there are 1,817 nongallows scribe-specific hapax. Only 664, or 36.54%, are completely covered by that scribe's own core ledger.  But when those same hapax are tested against the pooled all-scribes core, 1,297 of 1,817, or 71.38%, are completely legal.  So in most cases the "new" structure in a hapax isn't actually new to the manuscript. It is simply something that particular scribe only used once.<br />
<br />
There is also a very nice control using gallows words. If you split stripped gallows words according to whether they occur once or repeatedly:<br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Population</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>Own-scribe core</strong></th><th class="thead" valign="middle" style="text-align:center; border-radius:0;"><strong>All-scribe core</strong></th></tr>
<tr class="trowaltern"><td valign="top">Nongallows hapax</td><td valign="top">36.54%</td><td valign="top">71.38%</td></tr>
<tr class="trowaltern"><td valign="top">One-off gallows</td><td valign="top">43.59%</td><td valign="top">69.03%</td></tr>
<tr class="trowaltern"><td valign="top">Repeated gallows</td><td valign="top">73.18%</td><td valign="top">90.32%</td></tr>
</table>
<br />
One-off gallows words behave almost exactly like ordinary hapax, while repeated gallows words behave much more like core words. That suggests rarity is doing more of the work than whether the word contains a gallows.<br />
<br />
Again, I have a good bit more data on this but this is the core of what I'm seeing.<br />
<br />
In the final post on this topic, I'll provide the repo for my python files so you can reproduce any of these findings with Takahashi or Zandbergen/Landini transcriptions.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Textual relationship between matching Herbal and Pharma illustrations]]></title>
			<link>https://www.voynich.ninja/thread-6044.html</link>
			<pubDate>Thu, 27 Aug 2026 10:50:52 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3949">Karlov</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-6044.html</guid>
			<description><![CDATA[Hi everyone,<br />
<br />
First of all, I am an amateur when it comes to both the Voynich Manuscript and historical linguistics. English is also not my first language, so apologies in advance if I misuse some terminology.<br />
<br />
I am <span style="font-weight: bold;" class="mycode_b">not</span> proposing a decipherment, and I am not claiming that Voynichese represents any particular kind of language.<br />
<br />
I would like to ask whether the following kind of controlled experiment has already been attempted, and whether there is an obvious methodological problem with it that I am overlooking.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The basic question is:</span><br />
<blockquote class="mycode_quote"><cite>Quote:</cite>If a Herbal plant and a Pharmaceutical plant fragment are matched independently from the illustrations, does the associated text preserve a statistically detectable relationship between the two?</blockquote>
More specifically, instead of asking whether exactly the same complete Voynich "word" occurs in both places, I am wondering whether one could compare recurring <span style="font-style: italic;" class="mycode_i">sub-word</span> glyph structures — for example bigrams or trigrams — while giving relatively little weight to very common sequences and more weight to comparatively rare ones.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">Why I thought this might be worth testing</span><br />
<br />
As I understand it, one unusual feature of Voynichese is its relatively low conditional entropy. Within a token, the preceding glyphs strongly restrict which glyphs or glyph sequences are likely to follow.<br />
<br />
There also appears to be considerable positional structure within Voynich "words". Glyphs and short recurring glyph sequences have preferred positions: some occur disproportionately near the beginning of a token, others near the middle or end, and many tokens appear to be constructed from a relatively limited repertoire of recurring components.<br />
<br />
I am <span style="font-weight: bold;" class="mycode_b">not</span> assuming that these components are morphemes or that this proves Voynichese represents a synthetic natural language.<br />
<br />
The same surface structure might potentially arise from several very different mechanisms:<ul class="mycode_list"><li>genuine morphology<br />
</li>
<li>phonological or syllabic restrictions<br />
</li>
<li>a cipher or another encoding system<br />
</li>
<li>a system of abbreviations<br />
</li>
<li>an artificial procedure generating word-like forms from a limited set of components<br />
</li>
</ul>
For the experiment I have in mind, the actual meaning of these components would not matter. The only requirement would be that recurring sub-token structures can be identified statistically.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">Herbal–Pharmaceutical correspondences</span><br />
<br />
What made me think about this is the limited number of proposed correspondences between plants in the Herbal section and plant fragments in the Pharmaceutical section.<br />
<br />
Some of these proposed matches seem considerably stronger to me than simply saying that two drawings happen to look vaguely similar.<br />
<br />
One particularly interesting case is You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view. and You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view. in relation to f102r2.<br />
<br />
The two Herbal plants occur on the same physical bifolium, while the plant fragments proposed to correspond to them appear next to each other again on f102r2.<br />
<br />
There are several other proposed Herbal–Pharma correspondences, particularly in the f102 material.<br />
<br />
This also creates an important methodological problem. Several proposed Pharmaceutical matches occur on the same page or panel, so they cannot simply be treated as independent pairs of complete texts.<br />
<br />
For that reason I was thinking of carrying out the experiment on two separate levels.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">1. Individual Pharmaceutical labels</span><br />
<br />
First, the strongest Herbal–Pharma correspondences would have to be selected using <span style="font-weight: bold;" class="mycode_b">only the illustrations</span>, before looking at textual similarity.<br />
<br />
Where a particular Pharmaceutical fragment has a sufficiently localized label that can reasonably be associated with that object, that label could then be compared with the text on the corresponding Herbal page.<br />
<br />
Instead of searching only for an identical complete word, the label could be decomposed into shorter recurring glyph sequences — for example sequences of two or three glyphs.<br />
<br />
By this I mean sequences of actual transcribed glyphs, rather than arbitrary groups of two or three ASCII characters produced as an accidental consequence of the EVA transcription system.<br />
<br />
For each such label, one could then ask:<ul class="mycode_list"><li>How strongly are its characteristic short glyph sequences represented on the visually corresponding Herbal page?<br />
</li>
<li>How frequently do the same sequences occur on other comparable Herbal pages?<br />
</li>
</ul>
A sequence that is extremely common throughout Voynichese would tell us relatively little. Potentially more informative would be comparatively rare sequences that occur unusually often on the Herbal page selected <span style="font-style: italic;" class="mycode_i">in advance from the illustration</span>.<br />
<br />
So the test would not simply be:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>Does the exact same word occur in both places?</blockquote>
It would be closer to:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>Does the visually corresponding Herbal page contain an unusually high concentration of the same relatively rare sub-word elements that occur in this Pharmaceutical label?</blockquote>
This would provide an object-level test wherever sufficiently well-localized Pharmaceutical labels exist.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">2. The f102 Pharmaceutical material as a larger textual unit</span><br />
The second level would use the larger textual context rather than individual labels.<br />
<br />
Several of the most interesting proposed Herbal–Pharma correspondences occur together in the f102 Pharmaceutical material.<br />
<br />
Since several matching plant fragments may share the same Pharmaceutical page or panel, it may be more useful to compare the complete text of a relevant f102 panel — or eventually the f102 material as a whole — with the group of Herbal pages whose plants are visually represented there.<br />
<br />
For example, if one part of f102 contains plant fragments apparently corresponding to several particular Herbal pages, the combined textual profile of those Herbal pages could be compared with the text of the relevant f102 panel.<br />
<br />
The question would then be:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>Is the text in this part of f102 statistically more similar to the group of Herbal pages visually associated with its plant fragments than it is to other comparable Herbal pages or groups of pages?</blockquote>
The same principle could eventually be applied at a broader level to the f102 Pharmaceutical material as a whole.<br />
<br />
In simplified form:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>textual profile of the relevant f102 material
            vs.
combined textual profile of the Herbal pages
selected independently from the illustrations
            vs.
comparable alternative groups of Herbal pages</code></div></div><br />
Again, I would expect extremely common Voynichese components to carry relatively little information, while comparatively rare and informative glyph sequences would be more useful.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">Why use both levels?</span><br />
The two tests seem to me to answer slightly different questions.<br />
<br />
The label-level test asks whether a particular illustrated object has a detectable textual fingerprint.<br />
<br />
The f102-level test asks whether a whole group of visually associated Herbal entries leaves a detectable statistical fingerprint in the Pharmaceutical material where those objects reappear.<br />
<br />
Several of the correspondences that interest me also appear to belong to Currier A and to the same proposed scribal hand. I would hope that restricting comparisons appropriately might reduce the risk of simply rediscovering already known differences between Currier A and B, or between different scribes.<br />
<br />
Suitable control pages would presumably also need to be matched as closely as possible for these factors, as well as for text length and section.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">What would a positive result actually mean?</span><br />
<br />
I would <span style="font-weight: bold;" class="mycode_b">not</span> interpret such a result as a decipherment, and I would not claim that a particular sequence means "root", "plant", or anything else.<br />
<br />
The narrower question is simply:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>Does the text contain statistical information about relationships between objects that can be identified independently from the illustrations?</blockquote>
<br />
Suppose that visually corresponding Herbal and Pharmaceutical objects consistently shared more rare sub-word components than unrelated combinations, and that the same effect could also be detected when comparing the f102 Pharmaceutical material with the group of Herbal pages represented there.<br />
<br />
I can think of at least several possible explanations.<br />
<ol type="1" class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Meaningful text.</span><br />
If both entries concern the same plant, some lexical, morphological, or otherwise object-specific component might survive in both contexts even if the rest of the text is completely different.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Artificial or self-referential pseudo-text.</span><br />
Some form of artificially generated text would still be possible. However, the generation procedure would apparently have to be more complicated than simply producing locally similar words or drawing from a general "plant vocabulary".<br />
It would somehow have to preserve object-specific relationships across different parts of the manuscript.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">A common source or exemplar.</span><br />
Both the illustrations and some of the associated textual elements might have been copied from a common source.<br />
In that case, the person producing the Voynich Manuscript would not necessarily even have to understand the repeated textual elements. It would be sufficient to reproduce information that was consistently associated with the same object in the exemplar.<br />
</li>
</ol>
In all of these cases, I think a positive result would still be interesting.<br />
<br />
At minimum, it would suggest that the textual system contains information statistically associated with particular recurring visual objects, even if we remained completely unable to read a single word.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">What would a negative result mean?</span><br />
Probably much less.<br />
<br />
Failure to find such an effect would obviously not demonstrate that Voynichese is meaningless.<br />
<br />
A plant name might not occur in the Pharmaceutical section at all. Different abbreviations might be used. The Herbal and Pharmaceutical texts might discuss completely different properties of the same object. A Pharmaceutical label might refer to something other than the nearby plant fragment. While the absence of such a correspondence does reduce the likelihood of the text being meaningful, as we know, absence of evidence is not evidence of absence.<br />
<br />
So I would interpret a negative result only as:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>This particular method failed to detect an object-specific textual relationship.</blockquote>
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">My questions</span><br />
Has anyone already carried out this particular kind of controlled comparison?<br />
<br />
I have found discussions comparing identical labels or complete words, as well as broader studies of vocabulary similarity between the Herbal and Pharmaceutical sections. However, so far <br />
<br />
I have not found an analysis that combines all of the following:<br />
<ol type="1" class="mycode_list"><li>Selects Herbal–Pharma correspondences in advance using only the illustrations, without looking at the text when deciding which objects match.<br />
</li>
<li>Tests object-level relationships by comparing individual Pharmaceutical labels with rare or informative sub-word structures on the corresponding Herbal pages, rather than only searching for identical complete words.<br />
</li>
<li>Separately tests the f102 material at the page, panel, or section level against the group of Herbal pages visually represented there.<br />
</li>
<li>Compares the observed similarities against suitable alternative Herbal pages or groups, rather than simply identifying interesting matches after the fact.<br />
</li>
<li>Takes into account the fact that several corresponding Pharmaceutical fragments may occur on the same page or panel and therefore should not necessarily be treated as statistically independent observations.<br />
</li>
</ol>
If something like this has already been done, I would be very grateful for a reference.<br />
<br />
If it has not, I would be equally interested in hearing whether there is some methodological problem that makes either of these tests less informative than they appear to me.<br />
<br />
In particular, I would appreciate criticism concerning the choice of sub-word features, suitable control groups, statistical independence, or anything else I may be overlooking.<br />
As mentioned above, I am very much an amateur here, so corrections are very welcome.]]></description>
			<content:encoded><![CDATA[Hi everyone,<br />
<br />
First of all, I am an amateur when it comes to both the Voynich Manuscript and historical linguistics. English is also not my first language, so apologies in advance if I misuse some terminology.<br />
<br />
I am <span style="font-weight: bold;" class="mycode_b">not</span> proposing a decipherment, and I am not claiming that Voynichese represents any particular kind of language.<br />
<br />
I would like to ask whether the following kind of controlled experiment has already been attempted, and whether there is an obvious methodological problem with it that I am overlooking.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The basic question is:</span><br />
<blockquote class="mycode_quote"><cite>Quote:</cite>If a Herbal plant and a Pharmaceutical plant fragment are matched independently from the illustrations, does the associated text preserve a statistically detectable relationship between the two?</blockquote>
More specifically, instead of asking whether exactly the same complete Voynich "word" occurs in both places, I am wondering whether one could compare recurring <span style="font-style: italic;" class="mycode_i">sub-word</span> glyph structures — for example bigrams or trigrams — while giving relatively little weight to very common sequences and more weight to comparatively rare ones.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">Why I thought this might be worth testing</span><br />
<br />
As I understand it, one unusual feature of Voynichese is its relatively low conditional entropy. Within a token, the preceding glyphs strongly restrict which glyphs or glyph sequences are likely to follow.<br />
<br />
There also appears to be considerable positional structure within Voynich "words". Glyphs and short recurring glyph sequences have preferred positions: some occur disproportionately near the beginning of a token, others near the middle or end, and many tokens appear to be constructed from a relatively limited repertoire of recurring components.<br />
<br />
I am <span style="font-weight: bold;" class="mycode_b">not</span> assuming that these components are morphemes or that this proves Voynichese represents a synthetic natural language.<br />
<br />
The same surface structure might potentially arise from several very different mechanisms:<ul class="mycode_list"><li>genuine morphology<br />
</li>
<li>phonological or syllabic restrictions<br />
</li>
<li>a cipher or another encoding system<br />
</li>
<li>a system of abbreviations<br />
</li>
<li>an artificial procedure generating word-like forms from a limited set of components<br />
</li>
</ul>
For the experiment I have in mind, the actual meaning of these components would not matter. The only requirement would be that recurring sub-token structures can be identified statistically.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">Herbal–Pharmaceutical correspondences</span><br />
<br />
What made me think about this is the limited number of proposed correspondences between plants in the Herbal section and plant fragments in the Pharmaceutical section.<br />
<br />
Some of these proposed matches seem considerably stronger to me than simply saying that two drawings happen to look vaguely similar.<br />
<br />
One particularly interesting case is You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view. and You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view. in relation to f102r2.<br />
<br />
The two Herbal plants occur on the same physical bifolium, while the plant fragments proposed to correspond to them appear next to each other again on f102r2.<br />
<br />
There are several other proposed Herbal–Pharma correspondences, particularly in the f102 material.<br />
<br />
This also creates an important methodological problem. Several proposed Pharmaceutical matches occur on the same page or panel, so they cannot simply be treated as independent pairs of complete texts.<br />
<br />
For that reason I was thinking of carrying out the experiment on two separate levels.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">1. Individual Pharmaceutical labels</span><br />
<br />
First, the strongest Herbal–Pharma correspondences would have to be selected using <span style="font-weight: bold;" class="mycode_b">only the illustrations</span>, before looking at textual similarity.<br />
<br />
Where a particular Pharmaceutical fragment has a sufficiently localized label that can reasonably be associated with that object, that label could then be compared with the text on the corresponding Herbal page.<br />
<br />
Instead of searching only for an identical complete word, the label could be decomposed into shorter recurring glyph sequences — for example sequences of two or three glyphs.<br />
<br />
By this I mean sequences of actual transcribed glyphs, rather than arbitrary groups of two or three ASCII characters produced as an accidental consequence of the EVA transcription system.<br />
<br />
For each such label, one could then ask:<ul class="mycode_list"><li>How strongly are its characteristic short glyph sequences represented on the visually corresponding Herbal page?<br />
</li>
<li>How frequently do the same sequences occur on other comparable Herbal pages?<br />
</li>
</ul>
A sequence that is extremely common throughout Voynichese would tell us relatively little. Potentially more informative would be comparatively rare sequences that occur unusually often on the Herbal page selected <span style="font-style: italic;" class="mycode_i">in advance from the illustration</span>.<br />
<br />
So the test would not simply be:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>Does the exact same word occur in both places?</blockquote>
It would be closer to:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>Does the visually corresponding Herbal page contain an unusually high concentration of the same relatively rare sub-word elements that occur in this Pharmaceutical label?</blockquote>
This would provide an object-level test wherever sufficiently well-localized Pharmaceutical labels exist.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">2. The f102 Pharmaceutical material as a larger textual unit</span><br />
The second level would use the larger textual context rather than individual labels.<br />
<br />
Several of the most interesting proposed Herbal–Pharma correspondences occur together in the f102 Pharmaceutical material.<br />
<br />
Since several matching plant fragments may share the same Pharmaceutical page or panel, it may be more useful to compare the complete text of a relevant f102 panel — or eventually the f102 material as a whole — with the group of Herbal pages whose plants are visually represented there.<br />
<br />
For example, if one part of f102 contains plant fragments apparently corresponding to several particular Herbal pages, the combined textual profile of those Herbal pages could be compared with the text of the relevant f102 panel.<br />
<br />
The question would then be:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>Is the text in this part of f102 statistically more similar to the group of Herbal pages visually associated with its plant fragments than it is to other comparable Herbal pages or groups of pages?</blockquote>
The same principle could eventually be applied at a broader level to the f102 Pharmaceutical material as a whole.<br />
<br />
In simplified form:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>textual profile of the relevant f102 material
            vs.
combined textual profile of the Herbal pages
selected independently from the illustrations
            vs.
comparable alternative groups of Herbal pages</code></div></div><br />
Again, I would expect extremely common Voynichese components to carry relatively little information, while comparatively rare and informative glyph sequences would be more useful.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">Why use both levels?</span><br />
The two tests seem to me to answer slightly different questions.<br />
<br />
The label-level test asks whether a particular illustrated object has a detectable textual fingerprint.<br />
<br />
The f102-level test asks whether a whole group of visually associated Herbal entries leaves a detectable statistical fingerprint in the Pharmaceutical material where those objects reappear.<br />
<br />
Several of the correspondences that interest me also appear to belong to Currier A and to the same proposed scribal hand. I would hope that restricting comparisons appropriately might reduce the risk of simply rediscovering already known differences between Currier A and B, or between different scribes.<br />
<br />
Suitable control pages would presumably also need to be matched as closely as possible for these factors, as well as for text length and section.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">What would a positive result actually mean?</span><br />
<br />
I would <span style="font-weight: bold;" class="mycode_b">not</span> interpret such a result as a decipherment, and I would not claim that a particular sequence means "root", "plant", or anything else.<br />
<br />
The narrower question is simply:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>Does the text contain statistical information about relationships between objects that can be identified independently from the illustrations?</blockquote>
<br />
Suppose that visually corresponding Herbal and Pharmaceutical objects consistently shared more rare sub-word components than unrelated combinations, and that the same effect could also be detected when comparing the f102 Pharmaceutical material with the group of Herbal pages represented there.<br />
<br />
I can think of at least several possible explanations.<br />
<ol type="1" class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Meaningful text.</span><br />
If both entries concern the same plant, some lexical, morphological, or otherwise object-specific component might survive in both contexts even if the rest of the text is completely different.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Artificial or self-referential pseudo-text.</span><br />
Some form of artificially generated text would still be possible. However, the generation procedure would apparently have to be more complicated than simply producing locally similar words or drawing from a general "plant vocabulary".<br />
It would somehow have to preserve object-specific relationships across different parts of the manuscript.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">A common source or exemplar.</span><br />
Both the illustrations and some of the associated textual elements might have been copied from a common source.<br />
In that case, the person producing the Voynich Manuscript would not necessarily even have to understand the repeated textual elements. It would be sufficient to reproduce information that was consistently associated with the same object in the exemplar.<br />
</li>
</ol>
In all of these cases, I think a positive result would still be interesting.<br />
<br />
At minimum, it would suggest that the textual system contains information statistically associated with particular recurring visual objects, even if we remained completely unable to read a single word.<br />
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">What would a negative result mean?</span><br />
Probably much less.<br />
<br />
Failure to find such an effect would obviously not demonstrate that Voynichese is meaningless.<br />
<br />
A plant name might not occur in the Pharmaceutical section at all. Different abbreviations might be used. The Herbal and Pharmaceutical texts might discuss completely different properties of the same object. A Pharmaceutical label might refer to something other than the nearby plant fragment. While the absence of such a correspondence does reduce the likelihood of the text being meaningful, as we know, absence of evidence is not evidence of absence.<br />
<br />
So I would interpret a negative result only as:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>This particular method failed to detect an object-specific textual relationship.</blockquote>
<hr class="mycode_hr" />
<span style="font-weight: bold;" class="mycode_b">My questions</span><br />
Has anyone already carried out this particular kind of controlled comparison?<br />
<br />
I have found discussions comparing identical labels or complete words, as well as broader studies of vocabulary similarity between the Herbal and Pharmaceutical sections. However, so far <br />
<br />
I have not found an analysis that combines all of the following:<br />
<ol type="1" class="mycode_list"><li>Selects Herbal–Pharma correspondences in advance using only the illustrations, without looking at the text when deciding which objects match.<br />
</li>
<li>Tests object-level relationships by comparing individual Pharmaceutical labels with rare or informative sub-word structures on the corresponding Herbal pages, rather than only searching for identical complete words.<br />
</li>
<li>Separately tests the f102 material at the page, panel, or section level against the group of Herbal pages visually represented there.<br />
</li>
<li>Compares the observed similarities against suitable alternative Herbal pages or groups, rather than simply identifying interesting matches after the fact.<br />
</li>
<li>Takes into account the fact that several corresponding Pharmaceutical fragments may occur on the same page or panel and therefore should not necessarily be treated as statistically independent observations.<br />
</li>
</ol>
If something like this has already been done, I would be very grateful for a reference.<br />
<br />
If it has not, I would be equally interested in hearing whether there is some methodological problem that makes either of these tests less informative than they appear to me.<br />
<br />
In particular, I would appreciate criticism concerning the choice of sub-word features, suitable control groups, statistical independence, or anything else I may be overlooking.<br />
As mentioned above, I am very much an amateur here, so corrections are very welcome.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Do Split Gallows have rules?]]></title>
			<link>https://www.voynich.ninja/thread-6043.html</link>
			<pubDate>Wed, 26 Aug 2026 21:40:39 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3215">Grove</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-6043.html</guid>
			<description><![CDATA[<span style="font-size: large;" class="mycode_size"><span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Paragraph initial words primarily, but not always, begin with a plain gallows (K, F, T, P) and almost never a benched gallows - but…</span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">When a paragraph does start with a benched gallows it is most often going to be a split gallows.</span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Bear with my slight variation of transliteration for the peculiarities of a split gallows.</span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Not split:</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F1r cpho</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F65v cphy </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F76v cphdar </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F101r cphoar </span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Split:</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F8r ctho-cthey </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F8v cthod-soocth </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F30v: cthscthain </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F35r cthoo-r-choly-cthy</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F42r stho-ofaiin-cthaihcthy </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F80r: cthcthey </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F86v6: ctholcthy</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F90v2 cphdaithy </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F100v: cthdeecthy </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F102r2: cthol-dcthody </span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Not quite a bench:</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F101r: etolctheol </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F111v: psalar (not split either)</span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Non-bench split <span style="font-size: large;" class="mycode_size">gallows:</span></span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F56r: Otchal-chchsty </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F68r1: poeeodcthy (label)</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F68r2: opol-chcthy (label)</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F95v1: polteedy-ctho</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F99v: oteol-socthey </span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">The other ‘decorative’ paragraph initials where a P extends over one or more words before returning to cross the leg might also wrap those words into one highlighted segment. Of course, we may never know if they mean something at all, but I still like to think there’s more to these markers than just decoration.</span></span></span>]]></description>
			<content:encoded><![CDATA[<span style="font-size: large;" class="mycode_size"><span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Paragraph initial words primarily, but not always, begin with a plain gallows (K, F, T, P) and almost never a benched gallows - but…</span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">When a paragraph does start with a benched gallows it is most often going to be a split gallows.</span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Bear with my slight variation of transliteration for the peculiarities of a split gallows.</span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Not split:</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F1r cpho</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F65v cphy </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F76v cphdar </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F101r cphoar </span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Split:</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F8r ctho-cthey </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F8v cthod-soocth </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F30v: cthscthain </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F35r cthoo-r-choly-cthy</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F42r stho-ofaiin-cthaihcthy </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F80r: cthcthey </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F86v6: ctholcthy</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F90v2 cphdaithy </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F100v: cthdeecthy </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F102r2: cthol-dcthody </span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Not quite a bench:</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F101r: etolctheol </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F111v: psalar (not split either)</span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">Non-bench split <span style="font-size: large;" class="mycode_size">gallows:</span></span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F56r: Otchal-chchsty </span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F68r1: poeeodcthy (label)</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F68r2: opol-chcthy (label)</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F95v1: polteedy-ctho</span></span><br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">F99v: oteol-socthey </span></span><br />
<br />
<span style="color: #000000;" class="mycode_color"><span style="font-family: UICTFontTextStyleBody;" class="mycode_font">The other ‘decorative’ paragraph initials where a P extends over one or more words before returning to cross the leg might also wrap those words into one highlighted segment. Of course, we may never know if they mean something at all, but I still like to think there’s more to these markers than just decoration.</span></span></span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Deconstructing the VMS : A positionless ledger (part 1)]]></title>
			<link>https://www.voynich.ninja/thread-6040.html</link>
			<pubDate>Mon, 24 Aug 2026 03:57:01 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3074">Dunsel</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-6040.html</guid>
			<description><![CDATA[So, some of you may remember my work where I created a 'statistical' generator using what I called a ledger.  You can find it here: You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.<br />
<br />
Well, I have discovered why it didn't exactly inspire anyone. My logic was way off.  I have since been improving on my methods and digging deeper into the possibilities of the ledger and I believe I have something that works MUCH better.  Before I bury you in data I'll have to state that I have a LOT of information to impart so it will take several posts to explain all of this.  I'll start with the big news first then the explanations.<br />
<br />
Before I go any further, I want to give credit where it is due. This work follows and expands on the work of Torsten Timm and Andreas Schinner.  Their self-citation model proposes that Voynich words were produced by copying existing words and modifying them. This is the foundation of what I have been calling “copy and mutate.”  So if you're hoping for a decoding, TLDR; it's not here.<br />
<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Positionless ledger</span></span><br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Prefix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Core midfix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Rare midfix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Suffix</span></td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">A</span></td><td valign="top">L, R, I</td><td valign="top">D, M</td><td valign="top">L, S, R, M, N</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">O</span></td><td valign="top">A, O, D, L, CH, SH, E, S, R, I</td><td valign="top">—</td><td valign="top">D, L, Y, S, R, M, G</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">D</span></td><td valign="top">A, O, CH, SH, E</td><td valign="top">D, L, Y</td><td valign="top">O, L, Y, R</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">L</span></td><td valign="top">A, O, D, CH, SH</td><td valign="top">L, E, Y, S</td><td valign="top">O, D, L, Y, S, R, G</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">CH</span></td><td valign="top">A, O, D, E</td><td valign="top">L, CH, SH, S</td><td valign="top">A, O, D, L, E, Y, S, R, G</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">SH</span></td><td valign="top">A, O, D, CH, E</td><td valign="top">L, S</td><td valign="top">O, D, L, E, Y, S, R</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">E</span></td><td valign="top">A, O, D, E</td><td valign="top">CH, Y, S</td><td valign="top">O, D, E, Y, S, R, N, G</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Y</span></td><td valign="top">A, D, CH, SH</td><td valign="top">O, L, S</td><td valign="top">S, R</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">S</span></td><td valign="top">A, O, CH, SH, E</td><td valign="top">D</td><td valign="top">O, E, Y</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">R</span></td><td valign="top">A, O, CH</td><td valign="top">D, SH, E, I</td><td valign="top">O, L, Y</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Q</span></td><td valign="top">O</td><td valign="top">E</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">H</span></td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">M</span></td><td valign="top">—</td><td valign="top">—</td><td valign="top">O</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">N</span></td><td valign="top">—</td><td valign="top">D</td><td valign="top">O, Y</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">G</span></td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">X</span></td><td valign="top">—</td><td valign="top">A</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">C</span></td><td valign="top">S</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">I</span></td><td valign="top">D, R, I</td><td valign="top">L, N</td><td valign="top">L, S, R, M, N</td></tr>
</table>
<br />
This simple ledger is capable of creating and verifying any word in the Voynich, written by any scribe, with the exception of gallows words and hapax. I have intentionally removed those two categories in order to hopefully simplify and explain how this ledger works.<br />
<br />
The first thing you'll notice in that table is likely that I have combined CH and SH into one atomic unit.  There's also reasons for that which I'll explain later.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">How to use the ledger:</span></span><br />
<br />
Let's assume you want to create the word daiin.<br />
<br />
<ol type="1" class="mycode_list"><li>Look at the prefix column for the row that contains D.<br />
</li>
<li>In the core midfix column you'll see you can choose A.  You now have D→A<br />
</li>
<li>Now look in the prefix column for the row that contains A.<br />
</li>
<li>Look in the core midfix column and you'll see you can choose I. You now have D→A→I<br />
</li>
<li>Look in the prefix column for the row that contains I. <br />
</li>
<li>Look in the core midfix column and you'll see that you can also choose I as a midfix. You now have D→A→I→I<br />
</li>
<li>You'd again look in the I prefix row and in the suffix column you can choose N<br />
</li>
<li>You now have the word D→A→I→I→N<br />
</li>
</ol>
<br />
The ledger contains everything needed to reproduce:<br />
<ul class="mycode_list"><li>393 core word types<br />
</li>
<li>412 rare word types<br />
</li>
<li>805 total word types<br />
</li>
<li>12,564 manuscript tokens<br />
</li>
</ul>
<br />
That is around 36% of the total Voynich tokens.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Prefix Stacking.</span></span><br />
<br />
Consider these Voynich words<br />
<ul class="mycode_list"><li>aiin<br />
</li>
<li>daiin<br />
</li>
<li>odaiin<br />
</li>
<li>chodaiin<br />
</li>
</ul>
<br />
All four appear in the manuscript.<br />
<br />
What immediately stands out is that they share the same ending: <span style="font-weight: bold;" class="mycode_b">aiin</span>. The difference is what has been added in front of it:<br />
<ul class="mycode_list"><li>aiin<br />
</li>
<li>d + aiin<br />
</li>
<li>od + aiin<br />
</li>
<li>chod + aiin<br />
</li>
</ul>
<br />
This is what I mean by <span style="font-weight: bold;" class="mycode_b">prefix stacking</span>. Instead of creating five completely unrelated words, the system appears to reuse the same base while building a longer structure to its left.<br />
<br />
The longest word can be written as:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>CH → O → D → A → I → I → N</code></div></div><br />
The shorter words reuse parts of that same chain. This gives us transitions such as:<br />
<ul class="mycode_list"><li>CH→O <br />
</li>
<li>O→D<br />
</li>
<li>D→A <br />
</li>
<li>A→I <br />
</li>
<li>I→I <br />
</li>
<li>I→N<br />
</li>
</ul>
<br />
If you look how the ledger works, each time you pick a new midfix, you go back to the prefix column.  It is essentially stacking prefixes in front of each new midfix you choose. <br />
<br />
The ledger does not need a separate rule for every complete word. The same transitions are reused as prefixes are added to familiar words.  This does not prove that the words were created in this exact order. It shows that the words form a clear family built around the same ending, with progressively larger prefixes.<br />
<br />
And for those of you who suspect that the Voynich has Hebrew roots, I have good news: the ledger also works from right to left.<br />
<br />
Start with a suffix. Find a prefix row that permits that suffix, then continue working backward by adding permitted midfixes until you reach the prefix where you want to stop.<br />
<br />
For example:<br />
<ul class="mycode_list"><li>N<br />
</li>
<li>I → N<br />
</li>
<li>I → I → N<br />
</li>
<li>A → I → I → N<br />
</li>
<li>D → A → I → I → N<br />
</li>
</ul>
<br />
You have now built <span style="font-style: italic;" class="mycode_i">daiin</span> backward.  Every word covered by this ledger can be reconstructed in this direction. Naturally, this proves absolutely nothing about Hebrew. But the joke was sitting there, and I was not going to waste it.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Another example of prefix stacking</span></span><br />
<br />
Consider this family:<br />
<ul class="mycode_list"><li>chedy 500 occurrences<br />
</li>
<li>lchedy 108 occurrences<br />
</li>
<li>olchedy 34 occurrences<br />
</li>
<li>dolchedy 3 occurrences<br />
</li>
</ul>
<br />
All four words appear in the manuscript. None is a hapax or gallows word.  At each step, one new atom is placed in front of the previous word:<br />
<ul class="mycode_list"><li>chedy<br />
</li>
<li>L + chedy = lchedy<br />
</li>
<li>O + lchedy = olchedy<br />
</li>
<li>D + olchedy = dolchedy<br />
</li>
</ul>
<br />
In ledger form:<br />
<ul class="mycode_list"><li>CH → E → D → Y<br />
</li>
<li>L → CH → E → D → Y<br />
</li>
<li>O → L → CH → E → D → Y<br />
</li>
<li>D → O → L → CH → E → D → Y<br />
</li>
</ul>
<br />
The complete chain requires only:<br />
<ul class="mycode_list"><li>D→O <br />
</li>
<li>O→L <br />
</li>
<li>L→CH <br />
</li>
<li>CH→E <br />
</li>
<li>E→D <br />
</li>
<li>D→Y<br />
</li>
</ul>
<br />
Every one of those transitions appears in the core ledger.  This is a particularly clear example of prefix stacking. The word <span style="font-style: italic;" class="mycode_i">chedy</span> remains intact while L, then O, then D are stacked in front of it.<br />
<br />
Thats is exactly the kind of nested word family that prefix stacking would produce and the word families everyone keeps seeing in the Voynich.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Missing Letters?</span></span><br />
<br />
<span style="font-size: small;" class="mycode_size">You may have noticed some dashes in the ledger and some letters with no midfix or suffix and, that is correct.  H for example. It has no midfix as it never appears as a prefix.  And it has no suffix as it's never the letter before the suffix.  Now you would think that choldy would give it a midfix of o.  However, H never appears without a C or an H in front of it (keep in mind, no gallows and no hapax tokens).  But, it's included because in the full ledger, which I'll describe in the next post, that is going to change.</span><br />
<br />
<span style="font-size: small;" class="mycode_size">Which brings me to the next section:</span><br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Why I treat CH and SH as atoms</span></span><br />
<span style="font-size: small;" class="mycode_size"><br />
In my earlier ledgers, I treated every transcription character separately. That meant CH was represented as C followed by H, and SH was represented as S followed by H.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
For example:</span><br />
<ul class="mycode_list"><li><span style="font-size: small;" class="mycode_size">chedy = C → H → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">lchedy = L → C → H → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">olchedy = O → L → C → H → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">dolchedy = D → O → L → C → H → E → D → Y</span><br />
</li>
</ul>
<span style="font-size: small;" class="mycode_size"><br />
This created a problem in my original table. Every time another prefix was stacked onto the word, C and H were pushed one position farther into the midfix:</span><br />
<ul class="mycode_list"><li><span style="font-size: small;" class="mycode_size">chedy H in the first midfix position</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">lchedy H in the second midfix position</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">olchedy H in the third midfix position</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">dolchedy H in the fourth midfix position</span><br />
</li>
</ul>
<span style="font-size: small;" class="mycode_size"><br />
I therefore had to keep track of first midfix, second midfix, third midfix and so forth. The ledger became larger and more complicated as words became longer.  Eventually I realized that much of this apparent midfix depth was being created by the way I had divided CH and SH. I was splitting units that behaved more cleanly when kept together.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
I changed the atomization so that CH and SH are each handled as one ledger atom:</span><br />
<ul class="mycode_list"><li><span style="font-size: small;" class="mycode_size">chedy = CH → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">lchedy = L → CH → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">olchedy = O → L → CH → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">dolchedy = D → O → L → CH → E → D → Y</span><br />
</li>
</ul>
<span style="font-size: small;" class="mycode_size"><br />
Now the same word family can be described with a few reusable transitions:</span><br />
<ul class="mycode_list"><li><span style="font-size: small;" class="mycode_size">D→O </span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">O→L </span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">L→CH </span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">CH→E</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">E→D </span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">D→Y</span><br />
</li>
</ul>
<br />
<span style="font-size: small;" class="mycode_size">The ledger no longer needs to know whether CH is in the first, second, third or fourth midfix position. It only needs to know which atoms can follow CH and which atoms can lead into it.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
SH works the same way.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
This does not mean that C, S and H have been removed. They remain separate atoms when they occur separately. Only the exact sequences CH and SH are kept together.  “Atom” here simply means that the ledger handles the sequence as one unit. The important result is that once CH and SH are treated this way, the positional midfix columns are no longer necessary. The same information can be represented by a much smaller positionless ledger. </span> What had looked like complicated midfix depth was, in large part, the same units being pushed farther to the right by added prefixes.<br />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Eliminating the first argument: </span></span><span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Wouldn't any language look like this?</span></span><br />
<br />
<span style="font-size: small;" class="mycode_size">Yes, a positionless ledger can be constructed from any language. For comparison, I chose Finnish. Finnish is an agglutinative language: it commonly builds words by joining smaller elements together. That makes it a useful control for the kind of word-building process I am proposing for Voynichese.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
I used the first 12,564 non-hapax Finnish tokens, the same number of tokens represented by the Voynich ledger above.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Ledger</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Word types</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Core midfix transitions</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Rare midfix transitions</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Suffix transitions</span></td></tr>
<tr class="trowaltern"><td valign="top">Voynich</td><td valign="top">805</td><td valign="top">53</td><td valign="top">31</td><td valign="top">63</td></tr>
<tr class="trowaltern"><td valign="top">Finnish</td><td valign="top">3,919</td><td valign="top">277</td><td valign="top">20</td><td valign="top">140</td></tr>
</table></span><br />
<span style="font-size: small;" class="mycode_size"><br />
So yes, Finnish can be placed into the same kind of ledger. But it requires far more word types and far more transitions to describe the same number of tokens. The ledger format itself is not unique to the Voynich Manuscript. What is unusual is how much of the Voynich vocabulary can be described by such a small set of reusable transitions.<br />
</span><br />
<span style="font-weight: bold;" class="mycode_b">Finnish positionless ledger: Seitsemän veljestä</span><br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Prefix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Core midfix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Rare midfix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Suffix</span></td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">A</span></td><td valign="top">A, D, E, H, I, J, K, L, M, N, P, R, S, T, U, V</td><td valign="top">—</td><td valign="top">A, I, N, R, S, T</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">D</span></td><td valign="top">A, E, I, O, Ä</td><td valign="top">—</td><td valign="top">A, E, O, U, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">E</span></td><td valign="top">A, D, E, H, I, K, L, M, N, O, P, R, S, T, U, V, Y, Ä</td><td valign="top">J</td><td valign="top">A, E, H, I, N, R, S, T, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">F</span></td><td valign="top">R</td><td valign="top">L, Ö</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">G</span></td><td valign="top">A, I, O</td><td valign="top">E</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">H</span></td><td valign="top">A, D, E, H, I, J, K, L, M, N, O, T, U, V, Y, Ä, Ö</td><td valign="top">—</td><td valign="top">A, E, I, O, T, U, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">I</span></td><td valign="top">A, D, E, H, I, J, K, L, M, N, O, P, R, S, T, U, V, Ä</td><td valign="top">—</td><td valign="top">A, E, H, I, N, O, S, T, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">J</span></td><td valign="top">A, E, I, O, U, Y, Ä</td><td valign="top">—</td><td valign="top">A, U, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">K</span></td><td valign="top">A, E, I, K, M, O, R, S, U, Y, Ä, Ö</td><td valign="top">N</td><td valign="top">A, E, I, K, O, S, U, Y, Ä, Ö</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">L</span></td><td valign="top">A, E, H, I, J, K, L, M, O, P, S, T, U, V, Y, Ä, Ö</td><td valign="top">—</td><td valign="top">A, E, I, L, O, U, Y, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">M</span></td><td valign="top">A, E, I, M, O, P, S, U, Y, Ä, Ö</td><td valign="top">—</td><td valign="top">A, E, H, I, O, U, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">N</span></td><td valign="top">A, E, G, H, I, K, L, N, O, P, S, T, U, Y, Ä</td><td valign="top">J, M, V</td><td valign="top">A, E, I, O, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">O</span></td><td valign="top">A, D, E, H, I, J, K, L, M, N, O, P, R, S, T, U, V</td><td valign="top">—</td><td valign="top">A, H, I, N, O, S, T</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">P</span></td><td valign="top">A, E, I, O, P, S, U, Y, Ä, Ö</td><td valign="top">L, R</td><td valign="top">A, I, O, U, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">R</span></td><td valign="top">A, E, H, I, J, K, M, N, O, P, R, S, T, U, V, Y, Ä</td><td valign="top">Ö</td><td valign="top">A, I, O, S, Y, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">S</span></td><td valign="top">A, E, I, K, O, P, S, T, U, V, Y, Ä, Ö</td><td valign="top">M, N</td><td valign="top">A, E, I, O, S, T, U, Y, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">T</span></td><td valign="top">A, E, H, I, K, O, P, R, S, T, U, Y, Ä, Ö</td><td valign="top">V</td><td valign="top">A, E, I, O, U, Y, Ä, Ö</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">U</span></td><td valign="top">A, D, E, H, I, J, K, L, M, N, O, P, R, S, T, U, V</td><td valign="top">—</td><td valign="top">A, E, I, N, O, S, T, U</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">V</span></td><td valign="top">A, E, I, O, U, Ä</td><td valign="top">Y, Ö</td><td valign="top">A, E, I, O, U, Ä, Ö</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Y</span></td><td valign="top">D, E, H, I, K, L, M, N, P, R, S, T, V, Y, Ä, Ö</td><td valign="top">—</td><td valign="top">I, N, S, T, Y, Ä, Ö</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Ä</span></td><td valign="top">D, E, H, I, J, K, L, M, N, P, R, S, T, V, Y, Ä</td><td valign="top">—</td><td valign="top">E, H, I, N, R, S, T, Y, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Ö</span></td><td valign="top">H, I, J, K, M, N, R, S, T, Y, Ö</td><td valign="top">D, L, P, V</td><td valign="top">I, N, S, T, Ä</td></tr>
</table>
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">The hook to read the next post: Gallows are lipstick!</span></span><br />
<br />
And, I'll also present the full ledger, explain why gallows words and hapax words are omitted from the ledger above and hopefully, give some convincing evidence as to why they were omitted.<br />
<br />
Thanks. I have donned my flame retardant clothing, fire away.]]></description>
			<content:encoded><![CDATA[So, some of you may remember my work where I created a 'statistical' generator using what I called a ledger.  You can find it here: You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.<br />
<br />
Well, I have discovered why it didn't exactly inspire anyone. My logic was way off.  I have since been improving on my methods and digging deeper into the possibilities of the ledger and I believe I have something that works MUCH better.  Before I bury you in data I'll have to state that I have a LOT of information to impart so it will take several posts to explain all of this.  I'll start with the big news first then the explanations.<br />
<br />
Before I go any further, I want to give credit where it is due. This work follows and expands on the work of Torsten Timm and Andreas Schinner.  Their self-citation model proposes that Voynich words were produced by copying existing words and modifying them. This is the foundation of what I have been calling “copy and mutate.”  So if you're hoping for a decoding, TLDR; it's not here.<br />
<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Positionless ledger</span></span><br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Prefix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Core midfix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Rare midfix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Suffix</span></td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">A</span></td><td valign="top">L, R, I</td><td valign="top">D, M</td><td valign="top">L, S, R, M, N</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">O</span></td><td valign="top">A, O, D, L, CH, SH, E, S, R, I</td><td valign="top">—</td><td valign="top">D, L, Y, S, R, M, G</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">D</span></td><td valign="top">A, O, CH, SH, E</td><td valign="top">D, L, Y</td><td valign="top">O, L, Y, R</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">L</span></td><td valign="top">A, O, D, CH, SH</td><td valign="top">L, E, Y, S</td><td valign="top">O, D, L, Y, S, R, G</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">CH</span></td><td valign="top">A, O, D, E</td><td valign="top">L, CH, SH, S</td><td valign="top">A, O, D, L, E, Y, S, R, G</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">SH</span></td><td valign="top">A, O, D, CH, E</td><td valign="top">L, S</td><td valign="top">O, D, L, E, Y, S, R</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">E</span></td><td valign="top">A, O, D, E</td><td valign="top">CH, Y, S</td><td valign="top">O, D, E, Y, S, R, N, G</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Y</span></td><td valign="top">A, D, CH, SH</td><td valign="top">O, L, S</td><td valign="top">S, R</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">S</span></td><td valign="top">A, O, CH, SH, E</td><td valign="top">D</td><td valign="top">O, E, Y</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">R</span></td><td valign="top">A, O, CH</td><td valign="top">D, SH, E, I</td><td valign="top">O, L, Y</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Q</span></td><td valign="top">O</td><td valign="top">E</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">H</span></td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">M</span></td><td valign="top">—</td><td valign="top">—</td><td valign="top">O</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">N</span></td><td valign="top">—</td><td valign="top">D</td><td valign="top">O, Y</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">G</span></td><td valign="top">—</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">X</span></td><td valign="top">—</td><td valign="top">A</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">C</span></td><td valign="top">S</td><td valign="top">—</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">I</span></td><td valign="top">D, R, I</td><td valign="top">L, N</td><td valign="top">L, S, R, M, N</td></tr>
</table>
<br />
This simple ledger is capable of creating and verifying any word in the Voynich, written by any scribe, with the exception of gallows words and hapax. I have intentionally removed those two categories in order to hopefully simplify and explain how this ledger works.<br />
<br />
The first thing you'll notice in that table is likely that I have combined CH and SH into one atomic unit.  There's also reasons for that which I'll explain later.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">How to use the ledger:</span></span><br />
<br />
Let's assume you want to create the word daiin.<br />
<br />
<ol type="1" class="mycode_list"><li>Look at the prefix column for the row that contains D.<br />
</li>
<li>In the core midfix column you'll see you can choose A.  You now have D→A<br />
</li>
<li>Now look in the prefix column for the row that contains A.<br />
</li>
<li>Look in the core midfix column and you'll see you can choose I. You now have D→A→I<br />
</li>
<li>Look in the prefix column for the row that contains I. <br />
</li>
<li>Look in the core midfix column and you'll see that you can also choose I as a midfix. You now have D→A→I→I<br />
</li>
<li>You'd again look in the I prefix row and in the suffix column you can choose N<br />
</li>
<li>You now have the word D→A→I→I→N<br />
</li>
</ol>
<br />
The ledger contains everything needed to reproduce:<br />
<ul class="mycode_list"><li>393 core word types<br />
</li>
<li>412 rare word types<br />
</li>
<li>805 total word types<br />
</li>
<li>12,564 manuscript tokens<br />
</li>
</ul>
<br />
That is around 36% of the total Voynich tokens.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Prefix Stacking.</span></span><br />
<br />
Consider these Voynich words<br />
<ul class="mycode_list"><li>aiin<br />
</li>
<li>daiin<br />
</li>
<li>odaiin<br />
</li>
<li>chodaiin<br />
</li>
</ul>
<br />
All four appear in the manuscript.<br />
<br />
What immediately stands out is that they share the same ending: <span style="font-weight: bold;" class="mycode_b">aiin</span>. The difference is what has been added in front of it:<br />
<ul class="mycode_list"><li>aiin<br />
</li>
<li>d + aiin<br />
</li>
<li>od + aiin<br />
</li>
<li>chod + aiin<br />
</li>
</ul>
<br />
This is what I mean by <span style="font-weight: bold;" class="mycode_b">prefix stacking</span>. Instead of creating five completely unrelated words, the system appears to reuse the same base while building a longer structure to its left.<br />
<br />
The longest word can be written as:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>CH → O → D → A → I → I → N</code></div></div><br />
The shorter words reuse parts of that same chain. This gives us transitions such as:<br />
<ul class="mycode_list"><li>CH→O <br />
</li>
<li>O→D<br />
</li>
<li>D→A <br />
</li>
<li>A→I <br />
</li>
<li>I→I <br />
</li>
<li>I→N<br />
</li>
</ul>
<br />
If you look how the ledger works, each time you pick a new midfix, you go back to the prefix column.  It is essentially stacking prefixes in front of each new midfix you choose. <br />
<br />
The ledger does not need a separate rule for every complete word. The same transitions are reused as prefixes are added to familiar words.  This does not prove that the words were created in this exact order. It shows that the words form a clear family built around the same ending, with progressively larger prefixes.<br />
<br />
And for those of you who suspect that the Voynich has Hebrew roots, I have good news: the ledger also works from right to left.<br />
<br />
Start with a suffix. Find a prefix row that permits that suffix, then continue working backward by adding permitted midfixes until you reach the prefix where you want to stop.<br />
<br />
For example:<br />
<ul class="mycode_list"><li>N<br />
</li>
<li>I → N<br />
</li>
<li>I → I → N<br />
</li>
<li>A → I → I → N<br />
</li>
<li>D → A → I → I → N<br />
</li>
</ul>
<br />
You have now built <span style="font-style: italic;" class="mycode_i">daiin</span> backward.  Every word covered by this ledger can be reconstructed in this direction. Naturally, this proves absolutely nothing about Hebrew. But the joke was sitting there, and I was not going to waste it.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Another example of prefix stacking</span></span><br />
<br />
Consider this family:<br />
<ul class="mycode_list"><li>chedy 500 occurrences<br />
</li>
<li>lchedy 108 occurrences<br />
</li>
<li>olchedy 34 occurrences<br />
</li>
<li>dolchedy 3 occurrences<br />
</li>
</ul>
<br />
All four words appear in the manuscript. None is a hapax or gallows word.  At each step, one new atom is placed in front of the previous word:<br />
<ul class="mycode_list"><li>chedy<br />
</li>
<li>L + chedy = lchedy<br />
</li>
<li>O + lchedy = olchedy<br />
</li>
<li>D + olchedy = dolchedy<br />
</li>
</ul>
<br />
In ledger form:<br />
<ul class="mycode_list"><li>CH → E → D → Y<br />
</li>
<li>L → CH → E → D → Y<br />
</li>
<li>O → L → CH → E → D → Y<br />
</li>
<li>D → O → L → CH → E → D → Y<br />
</li>
</ul>
<br />
The complete chain requires only:<br />
<ul class="mycode_list"><li>D→O <br />
</li>
<li>O→L <br />
</li>
<li>L→CH <br />
</li>
<li>CH→E <br />
</li>
<li>E→D <br />
</li>
<li>D→Y<br />
</li>
</ul>
<br />
Every one of those transitions appears in the core ledger.  This is a particularly clear example of prefix stacking. The word <span style="font-style: italic;" class="mycode_i">chedy</span> remains intact while L, then O, then D are stacked in front of it.<br />
<br />
Thats is exactly the kind of nested word family that prefix stacking would produce and the word families everyone keeps seeing in the Voynich.<br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Missing Letters?</span></span><br />
<br />
<span style="font-size: small;" class="mycode_size">You may have noticed some dashes in the ledger and some letters with no midfix or suffix and, that is correct.  H for example. It has no midfix as it never appears as a prefix.  And it has no suffix as it's never the letter before the suffix.  Now you would think that choldy would give it a midfix of o.  However, H never appears without a C or an H in front of it (keep in mind, no gallows and no hapax tokens).  But, it's included because in the full ledger, which I'll describe in the next post, that is going to change.</span><br />
<br />
<span style="font-size: small;" class="mycode_size">Which brings me to the next section:</span><br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Why I treat CH and SH as atoms</span></span><br />
<span style="font-size: small;" class="mycode_size"><br />
In my earlier ledgers, I treated every transcription character separately. That meant CH was represented as C followed by H, and SH was represented as S followed by H.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
For example:</span><br />
<ul class="mycode_list"><li><span style="font-size: small;" class="mycode_size">chedy = C → H → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">lchedy = L → C → H → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">olchedy = O → L → C → H → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">dolchedy = D → O → L → C → H → E → D → Y</span><br />
</li>
</ul>
<span style="font-size: small;" class="mycode_size"><br />
This created a problem in my original table. Every time another prefix was stacked onto the word, C and H were pushed one position farther into the midfix:</span><br />
<ul class="mycode_list"><li><span style="font-size: small;" class="mycode_size">chedy H in the first midfix position</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">lchedy H in the second midfix position</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">olchedy H in the third midfix position</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">dolchedy H in the fourth midfix position</span><br />
</li>
</ul>
<span style="font-size: small;" class="mycode_size"><br />
I therefore had to keep track of first midfix, second midfix, third midfix and so forth. The ledger became larger and more complicated as words became longer.  Eventually I realized that much of this apparent midfix depth was being created by the way I had divided CH and SH. I was splitting units that behaved more cleanly when kept together.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
I changed the atomization so that CH and SH are each handled as one ledger atom:</span><br />
<ul class="mycode_list"><li><span style="font-size: small;" class="mycode_size">chedy = CH → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">lchedy = L → CH → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">olchedy = O → L → CH → E → D → Y</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">dolchedy = D → O → L → CH → E → D → Y</span><br />
</li>
</ul>
<span style="font-size: small;" class="mycode_size"><br />
Now the same word family can be described with a few reusable transitions:</span><br />
<ul class="mycode_list"><li><span style="font-size: small;" class="mycode_size">D→O </span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">O→L </span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">L→CH </span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">CH→E</span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">E→D </span><br />
</li>
<li><span style="font-size: small;" class="mycode_size">D→Y</span><br />
</li>
</ul>
<br />
<span style="font-size: small;" class="mycode_size">The ledger no longer needs to know whether CH is in the first, second, third or fourth midfix position. It only needs to know which atoms can follow CH and which atoms can lead into it.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
SH works the same way.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
This does not mean that C, S and H have been removed. They remain separate atoms when they occur separately. Only the exact sequences CH and SH are kept together.  “Atom” here simply means that the ledger handles the sequence as one unit. The important result is that once CH and SH are treated this way, the positional midfix columns are no longer necessary. The same information can be represented by a much smaller positionless ledger. </span> What had looked like complicated midfix depth was, in large part, the same units being pushed farther to the right by added prefixes.<br />
<br />
<span style="font-size: large;" class="mycode_size"><span style="font-weight: bold;" class="mycode_b">Eliminating the first argument: </span></span><span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">Wouldn't any language look like this?</span></span><br />
<br />
<span style="font-size: small;" class="mycode_size">Yes, a positionless ledger can be constructed from any language. For comparison, I chose Finnish. Finnish is an agglutinative language: it commonly builds words by joining smaller elements together. That makes it a useful control for the kind of word-building process I am proposing for Voynichese.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
I used the first 12,564 non-hapax Finnish tokens, the same number of tokens represented by the Voynich ledger above.</span><br />
<span style="font-size: small;" class="mycode_size"><br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Ledger</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Word types</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Core midfix transitions</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Rare midfix transitions</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Suffix transitions</span></td></tr>
<tr class="trowaltern"><td valign="top">Voynich</td><td valign="top">805</td><td valign="top">53</td><td valign="top">31</td><td valign="top">63</td></tr>
<tr class="trowaltern"><td valign="top">Finnish</td><td valign="top">3,919</td><td valign="top">277</td><td valign="top">20</td><td valign="top">140</td></tr>
</table></span><br />
<span style="font-size: small;" class="mycode_size"><br />
So yes, Finnish can be placed into the same kind of ledger. But it requires far more word types and far more transitions to describe the same number of tokens. The ledger format itself is not unique to the Voynich Manuscript. What is unusual is how much of the Voynich vocabulary can be described by such a small set of reusable transitions.<br />
</span><br />
<span style="font-weight: bold;" class="mycode_b">Finnish positionless ledger: Seitsemän veljestä</span><br />
<br />
<table class="tborder tfixed clear" cellspacing="0" cellpadding="5"  style="border:0; radius:0;">
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Prefix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Core midfix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Rare midfix</span></td><td valign="top"><span style="font-weight: bold;" class="mycode_b">Suffix</span></td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">A</span></td><td valign="top">A, D, E, H, I, J, K, L, M, N, P, R, S, T, U, V</td><td valign="top">—</td><td valign="top">A, I, N, R, S, T</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">D</span></td><td valign="top">A, E, I, O, Ä</td><td valign="top">—</td><td valign="top">A, E, O, U, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">E</span></td><td valign="top">A, D, E, H, I, K, L, M, N, O, P, R, S, T, U, V, Y, Ä</td><td valign="top">J</td><td valign="top">A, E, H, I, N, R, S, T, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">F</span></td><td valign="top">R</td><td valign="top">L, Ö</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">G</span></td><td valign="top">A, I, O</td><td valign="top">E</td><td valign="top">—</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">H</span></td><td valign="top">A, D, E, H, I, J, K, L, M, N, O, T, U, V, Y, Ä, Ö</td><td valign="top">—</td><td valign="top">A, E, I, O, T, U, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">I</span></td><td valign="top">A, D, E, H, I, J, K, L, M, N, O, P, R, S, T, U, V, Ä</td><td valign="top">—</td><td valign="top">A, E, H, I, N, O, S, T, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">J</span></td><td valign="top">A, E, I, O, U, Y, Ä</td><td valign="top">—</td><td valign="top">A, U, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">K</span></td><td valign="top">A, E, I, K, M, O, R, S, U, Y, Ä, Ö</td><td valign="top">N</td><td valign="top">A, E, I, K, O, S, U, Y, Ä, Ö</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">L</span></td><td valign="top">A, E, H, I, J, K, L, M, O, P, S, T, U, V, Y, Ä, Ö</td><td valign="top">—</td><td valign="top">A, E, I, L, O, U, Y, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">M</span></td><td valign="top">A, E, I, M, O, P, S, U, Y, Ä, Ö</td><td valign="top">—</td><td valign="top">A, E, H, I, O, U, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">N</span></td><td valign="top">A, E, G, H, I, K, L, N, O, P, S, T, U, Y, Ä</td><td valign="top">J, M, V</td><td valign="top">A, E, I, O, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">O</span></td><td valign="top">A, D, E, H, I, J, K, L, M, N, O, P, R, S, T, U, V</td><td valign="top">—</td><td valign="top">A, H, I, N, O, S, T</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">P</span></td><td valign="top">A, E, I, O, P, S, U, Y, Ä, Ö</td><td valign="top">L, R</td><td valign="top">A, I, O, U, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">R</span></td><td valign="top">A, E, H, I, J, K, M, N, O, P, R, S, T, U, V, Y, Ä</td><td valign="top">Ö</td><td valign="top">A, I, O, S, Y, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">S</span></td><td valign="top">A, E, I, K, O, P, S, T, U, V, Y, Ä, Ö</td><td valign="top">M, N</td><td valign="top">A, E, I, O, S, T, U, Y, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">T</span></td><td valign="top">A, E, H, I, K, O, P, R, S, T, U, Y, Ä, Ö</td><td valign="top">V</td><td valign="top">A, E, I, O, U, Y, Ä, Ö</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">U</span></td><td valign="top">A, D, E, H, I, J, K, L, M, N, O, P, R, S, T, U, V</td><td valign="top">—</td><td valign="top">A, E, I, N, O, S, T, U</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">V</span></td><td valign="top">A, E, I, O, U, Ä</td><td valign="top">Y, Ö</td><td valign="top">A, E, I, O, U, Ä, Ö</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Y</span></td><td valign="top">D, E, H, I, K, L, M, N, P, R, S, T, V, Y, Ä, Ö</td><td valign="top">—</td><td valign="top">I, N, S, T, Y, Ä, Ö</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Ä</span></td><td valign="top">D, E, H, I, J, K, L, M, N, P, R, S, T, V, Y, Ä</td><td valign="top">—</td><td valign="top">E, H, I, N, R, S, T, Y, Ä</td></tr>
<tr class="trowaltern"><td valign="top"><span style="font-weight: bold;" class="mycode_b">Ö</span></td><td valign="top">H, I, J, K, M, N, R, S, T, Y, Ö</td><td valign="top">D, L, P, V</td><td valign="top">I, N, S, T, Ä</td></tr>
</table>
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="font-size: large;" class="mycode_size">The hook to read the next post: Gallows are lipstick!</span></span><br />
<br />
And, I'll also present the full ledger, explain why gallows words and hapax words are omitted from the ledger above and hopefully, give some convincing evidence as to why they were omitted.<br />
<br />
Thanks. I have donned my flame retardant clothing, fire away.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[[split] Measure uncertain spaces?]]></title>
			<link>https://www.voynich.ninja/thread-6037.html</link>
			<pubDate>Sat, 22 Aug 2026 15:22:51 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=68">Koen G</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-6037.html</guid>
			<description><![CDATA[<blockquote class="mycode_quote"><cite><span> (22-08-2026, 03:59 PM)</span>pfeaster Wrote:  You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.</cite>But they also report finding that "certain" spaces tend to fall between their study's learned units, while "uncertain" spaces tend to fall within them. That seems potentially more meaningful in terms of supporting the idea of a hierarchy of "strong" and "weak" spaces.</blockquote><br />
Thank you for your contributions in clear language, Patrick, I find this very informative. <br />
<br />
About these uncertain spaces: the phenomenon you describe here could still be attributed to subconscious split-second decisions by the transcriber, right? The manuscript trains your brain to recognize certain patterns, and as soon as something deviates from those patterns, you have to mark it as uncertain. In my opinion, there is a good chance this effect influenced the results. When transcribing regular medieval handwriting, we need to rely on expected sequences to determine spacing all the time, especially in kind of chopped-up scripts like these. Only, in regular MSS this is non-controversial because we understand the meaning of the words.<br />
<br />
So I wonder: let's say we take this crucial sequence of [r] followed by [a], and plot them all according to the distance (pixels?) between the [r] and [a]. Will the no-space variants be all on the left, and the space variants on the right, and the uncertain ones neatly in between? How much overlap is there? Is it a continuum? If this could be measured objectively somehow, we would have a better idea of what space, no space and uncertain space actually stand for.<br />
<br />
(Edit: this would actually be informative for other reasons as well, like when we split up by scribe).]]></description>
			<content:encoded><![CDATA[<blockquote class="mycode_quote"><cite><span> (22-08-2026, 03:59 PM)</span>pfeaster Wrote:  You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view.</cite>But they also report finding that "certain" spaces tend to fall between their study's learned units, while "uncertain" spaces tend to fall within them. That seems potentially more meaningful in terms of supporting the idea of a hierarchy of "strong" and "weak" spaces.</blockquote><br />
Thank you for your contributions in clear language, Patrick, I find this very informative. <br />
<br />
About these uncertain spaces: the phenomenon you describe here could still be attributed to subconscious split-second decisions by the transcriber, right? The manuscript trains your brain to recognize certain patterns, and as soon as something deviates from those patterns, you have to mark it as uncertain. In my opinion, there is a good chance this effect influenced the results. When transcribing regular medieval handwriting, we need to rely on expected sequences to determine spacing all the time, especially in kind of chopped-up scripts like these. Only, in regular MSS this is non-controversial because we understand the meaning of the words.<br />
<br />
So I wonder: let's say we take this crucial sequence of [r] followed by [a], and plot them all according to the distance (pixels?) between the [r] and [a]. Will the no-space variants be all on the left, and the space variants on the right, and the uncertain ones neatly in between? How much overlap is there? Is it a continuum? If this could be measured objectively somehow, we would have a better idea of what space, no space and uncertain space actually stand for.<br />
<br />
(Edit: this would actually be informative for other reasons as well, like when we split up by scribe).]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Is that normal?]]></title>
			<link>https://www.voynich.ninja/thread-6035.html</link>
			<pubDate>Fri, 21 Aug 2026 18:06:27 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3052">JoJo_Jost</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-6035.html</guid>
			<description><![CDATA[I was looking for a pattern in the LAAFU effects. To do this, I arranged with an AI all the glyphs in a grid and removed the spaces without changing the order of the glyphs in a line. This produced some lovely images! <br />
<br />
Letters were highlighted if they accounted for more than 40 per cent of the characters in a column.<br />
<hr class="mycode_hr" /><br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17323" target="_blank" title="">14.png</a> (Size: 144.43 KB / Downloads: 137)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17318" target="_blank" title="">10.png</a> (Size: 121.38 KB / Downloads: 140)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17319" target="_blank" title="">9.png</a> (Size: 130.09 KB / Downloads: 137)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17320" target="_blank" title="">8.png</a> (Size: 153.31 KB / Downloads: 138)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17310" target="_blank" title="">2.png</a> (Size: 115.43 KB / Downloads: 141)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17311" target="_blank" title="">1.png</a> (Size: 137.42 KB / Downloads: 140)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17322" target="_blank" title="">6.png</a> (Size: 122.23 KB / Downloads: 137)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17321" target="_blank" title="">7.png</a> (Size: 107.26 KB / Downloads: 137)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17316" target="_blank" title="">6.png</a> (Size: 122.23 KB / Downloads: 140)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17308" target="_blank" title="">4.png</a> (Size: 117.36 KB / Downloads: 141)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17307" target="_blank" title="">5.png</a> (Size: 96.87 KB / Downloads: 140)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17309" target="_blank" title="">3.png</a> (Size: 104.95 KB / Downloads: 140)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17324" target="_blank" title="">13.png</a> (Size: 148.48 KB / Downloads: 135)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17325" target="_blank" title="">12.png</a> (Size: 127.03 KB / Downloads: 135)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17326" target="_blank" title="">11.png</a> (Size: 123.83 KB / Downloads: 135)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17327" target="_blank" title="">15.png</a> (Size: 96.61 KB / Downloads: 135)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17328" target="_blank" title="">16.png</a> (Size: 139.27 KB / Downloads: 135)
]]></description>
			<content:encoded><![CDATA[I was looking for a pattern in the LAAFU effects. To do this, I arranged with an AI all the glyphs in a grid and removed the spaces without changing the order of the glyphs in a line. This produced some lovely images! <br />
<br />
Letters were highlighted if they accounted for more than 40 per cent of the characters in a column.<br />
<hr class="mycode_hr" /><br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17323" target="_blank" title="">14.png</a> (Size: 144.43 KB / Downloads: 137)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17318" target="_blank" title="">10.png</a> (Size: 121.38 KB / Downloads: 140)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17319" target="_blank" title="">9.png</a> (Size: 130.09 KB / Downloads: 137)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17320" target="_blank" title="">8.png</a> (Size: 153.31 KB / Downloads: 138)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17310" target="_blank" title="">2.png</a> (Size: 115.43 KB / Downloads: 141)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17311" target="_blank" title="">1.png</a> (Size: 137.42 KB / Downloads: 140)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17322" target="_blank" title="">6.png</a> (Size: 122.23 KB / Downloads: 137)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17321" target="_blank" title="">7.png</a> (Size: 107.26 KB / Downloads: 137)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17316" target="_blank" title="">6.png</a> (Size: 122.23 KB / Downloads: 140)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17308" target="_blank" title="">4.png</a> (Size: 117.36 KB / Downloads: 141)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17307" target="_blank" title="">5.png</a> (Size: 96.87 KB / Downloads: 140)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17309" target="_blank" title="">3.png</a> (Size: 104.95 KB / Downloads: 140)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17324" target="_blank" title="">13.png</a> (Size: 148.48 KB / Downloads: 135)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17325" target="_blank" title="">12.png</a> (Size: 127.03 KB / Downloads: 135)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17326" target="_blank" title="">11.png</a> (Size: 123.83 KB / Downloads: 135)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17327" target="_blank" title="">15.png</a> (Size: 96.61 KB / Downloads: 135)
<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=17328" target="_blank" title="">16.png</a> (Size: 139.27 KB / Downloads: 135)
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[cTh is a eTe?]]></title>
			<link>https://www.voynich.ninja/thread-6020.html</link>
			<pubDate>Sat, 15 Aug 2026 17:50:49 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3690">ololololo</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-6020.html</guid>
			<description><![CDATA[On f10v, I found one word that seems quite interesting to me.<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
&nbsp;&nbsp;<a href="attachment.php?aid=17159" target="_blank" title="">Снимок экрана 2026-08-15 203102.jpg</a> (Size: 17.8 KB / Downloads: 166)
<br />
Takahashi has this <span style="font-family: Eva;" class="mycode_font">ShcTHey</span>. But for some reason, it seems to me that interpreting the word here is more difficult. It could be <span style="font-family: Eva;" class="mycode_font">sheTchy</span>, <span style="font-family: Eva;" class="mycode_font">sheTHHy</span>, or<span style="font-family: Eva;" class="mycode_font"> sheTeey</span>.<br />
Given the possible relationship between the symbols <span style="font-family: Eva;" class="mycode_font">e</span> and <span style="font-family: Eva;" class="mycode_font">c</span>, as well as <span style="font-family: Eva;" class="mycode_font">ee</span> and <span style="font-family: Eva;" class="mycode_font">ch</span>, I would suggest that <span style="font-family: Eva;" class="mycode_font">cTh</span> (like other gallows on the pedestal) is simply a stylistic embellishment of the spelling <span style="font-family: Eva;" class="mycode_font">ete</span>, with the addition of a line crossing the gallows.<br />
<br />
Interesting cases of spelling e and hangings can be found on f67r1:<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
&nbsp;&nbsp;<a href="attachment.php?aid=17161" target="_blank" title="">Снимок экрана 2026-08-15 204631.jpg</a> (Size: 17.24 KB / Downloads: 166)
<br />
In two cases, <span style="font-family: Eva;" class="mycode_font">ep</span> stands before <span style="font-family: Eva;" class="mycode_font">a</span>. If <span style="font-family: Eva;" class="mycode_font">a</span> = <span style="font-family: Eva;" class="mycode_font">ei</span>, then a good combination of <span style="font-family: Eva;" class="mycode_font">epe</span> would result.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">What do you think?</span>]]></description>
			<content:encoded><![CDATA[On f10v, I found one word that seems quite interesting to me.<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
&nbsp;&nbsp;<a href="attachment.php?aid=17159" target="_blank" title="">Снимок экрана 2026-08-15 203102.jpg</a> (Size: 17.8 KB / Downloads: 166)
<br />
Takahashi has this <span style="font-family: Eva;" class="mycode_font">ShcTHey</span>. But for some reason, it seems to me that interpreting the word here is more difficult. It could be <span style="font-family: Eva;" class="mycode_font">sheTchy</span>, <span style="font-family: Eva;" class="mycode_font">sheTHHy</span>, or<span style="font-family: Eva;" class="mycode_font"> sheTeey</span>.<br />
Given the possible relationship between the symbols <span style="font-family: Eva;" class="mycode_font">e</span> and <span style="font-family: Eva;" class="mycode_font">c</span>, as well as <span style="font-family: Eva;" class="mycode_font">ee</span> and <span style="font-family: Eva;" class="mycode_font">ch</span>, I would suggest that <span style="font-family: Eva;" class="mycode_font">cTh</span> (like other gallows on the pedestal) is simply a stylistic embellishment of the spelling <span style="font-family: Eva;" class="mycode_font">ete</span>, with the addition of a line crossing the gallows.<br />
<br />
Interesting cases of spelling e and hangings can be found on f67r1:<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
&nbsp;&nbsp;<a href="attachment.php?aid=17161" target="_blank" title="">Снимок экрана 2026-08-15 204631.jpg</a> (Size: 17.24 KB / Downloads: 166)
<br />
In two cases, <span style="font-family: Eva;" class="mycode_font">ep</span> stands before <span style="font-family: Eva;" class="mycode_font">a</span>. If <span style="font-family: Eva;" class="mycode_font">a</span> = <span style="font-family: Eva;" class="mycode_font">ei</span>, then a good combination of <span style="font-family: Eva;" class="mycode_font">epe</span> would result.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">What do you think?</span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[This damn EVA z]]></title>
			<link>https://www.voynich.ninja/thread-6006.html</link>
			<pubDate>Fri, 07 Aug 2026 18:22:33 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3690">ololololo</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-6006.html</guid>
			<description><![CDATA[The symbol <span style="font-family: Eva;" class="mycode_font">z</span> looks like a small version of<span style="font-family: Eva;" class="mycode_font"> k</span> and appears very rarely in the manuscript. I counted it 3 times; only 2 are present in the transcription by Tahakasi.<br />
It appears once in Botany (f17r), f58r–f58v, and on the diagram f67v1, and it is repeated twice in the word.<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
&nbsp;&nbsp;<a href="attachment.php?aid=17040" target="_blank" title="">Снимок экрана 2026-08-07 211611.jpg</a> (Size: 31.81 KB / Downloads: 234)
<br />
And this is definitely not <span style="font-family: Eva;" class="mycode_font">k</span>, since the scribe of Astrology has no problem writing this gallows. This is also not a distorted <span style="font-family: Eva;" class="mycode_font">ch</span> à la <span style="font-family: Eva;" class="mycode_font">Ih</span>, because there is a loop there.<br />
However, this sign does not appear on f57v, where <span style="font-family: Eva;" class="mycode_font">x</span> is featured.<br />
Of course, <span style="font-family: Eva;" class="mycode_font">ch</span> doesn’t appear there either, but still…<br />
<br />
I suggest that this letter is similar to <span style="font-family: Eva;" class="mycode_font">i</span>/<span style="font-family: Eva;" class="mycode_font">n</span> or <span style="font-family: Eva;" class="mycode_font">r</span>, because in all cases (except for f17r) it comes after <span style="font-family: Eva;" class="mycode_font">a</span>.<br />
<br />
What do you think about this letter? What can it tell us about the manuscript’s cipher?]]></description>
			<content:encoded><![CDATA[The symbol <span style="font-family: Eva;" class="mycode_font">z</span> looks like a small version of<span style="font-family: Eva;" class="mycode_font"> k</span> and appears very rarely in the manuscript. I counted it 3 times; only 2 are present in the transcription by Tahakasi.<br />
It appears once in Botany (f17r), f58r–f58v, and on the diagram f67v1, and it is repeated twice in the word.<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
&nbsp;&nbsp;<a href="attachment.php?aid=17040" target="_blank" title="">Снимок экрана 2026-08-07 211611.jpg</a> (Size: 31.81 KB / Downloads: 234)
<br />
And this is definitely not <span style="font-family: Eva;" class="mycode_font">k</span>, since the scribe of Astrology has no problem writing this gallows. This is also not a distorted <span style="font-family: Eva;" class="mycode_font">ch</span> à la <span style="font-family: Eva;" class="mycode_font">Ih</span>, because there is a loop there.<br />
However, this sign does not appear on f57v, where <span style="font-family: Eva;" class="mycode_font">x</span> is featured.<br />
Of course, <span style="font-family: Eva;" class="mycode_font">ch</span> doesn’t appear there either, but still…<br />
<br />
I suggest that this letter is similar to <span style="font-family: Eva;" class="mycode_font">i</span>/<span style="font-family: Eva;" class="mycode_font">n</span> or <span style="font-family: Eva;" class="mycode_font">r</span>, because in all cases (except for f17r) it comes after <span style="font-family: Eva;" class="mycode_font">a</span>.<br />
<br />
What do you think about this letter? What can it tell us about the manuscript’s cipher?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[VMS stats: YT video]]></title>
			<link>https://www.voynich.ninja/thread-5974.html</link>
			<pubDate>Tue, 28 Jul 2026 06:00:23 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3873">elemental</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-5974.html</guid>
			<description><![CDATA[I'm not a Voynich researcher per se, but I do like statistics in general. I uploaded a YT video with statistical info about VMS, such as solutions by language (incl. from this forum), plus I've re-done some stats about the corpus itself. Some stats may be known, others may be new <img src="https://www.voynich.ninja/images/smilies/smile.png" alt="Smile" title="Smile" class="smilie smilie_1" /> Enjoy. <br />
<br />
<iframe width="560" height="315" src="//www.youtube-nocookie.com/embed/WyOw5pbnqCU" frameborder="0" allowfullscreen="true"></iframe>]]></description>
			<content:encoded><![CDATA[I'm not a Voynich researcher per se, but I do like statistics in general. I uploaded a YT video with statistical info about VMS, such as solutions by language (incl. from this forum), plus I've re-done some stats about the corpus itself. Some stats may be known, others may be new <img src="https://www.voynich.ninja/images/smilies/smile.png" alt="Smile" title="Smile" class="smilie smilie_1" /> Enjoy. <br />
<br />
<iframe width="560" height="315" src="//www.youtube-nocookie.com/embed/WyOw5pbnqCU" frameborder="0" allowfullscreen="true"></iframe>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Paragraph layout]]></title>
			<link>https://www.voynich.ninja/thread-5970.html</link>
			<pubDate>Mon, 27 Jul 2026 20:20:04 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=1">davidjackson</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-5970.html</guid>
			<description><![CDATA[The formatting of the text is quite simple for the era. I am not interested here in the text analysis but in the way it is presented on the page.<br />
If we look at standard manuscripts or incunabula (usually agreed to be visually the same as their hand written equivalents) from, say, 1450 - 1500 we see text written in blocks, not paragraphs. <br />
Many manuscripts will have clear paragraph markers -pilcrows-, usually distinguishable by a different colour or size, to break up information units, rather than the modern usage of using a line break, as I am doing in this post. You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view..<br />
<br />
The Voynich, from the very first page, uses the line break format accompanied by a pilcrow.<br />
<img src="https://www.voynich.ninja/extractor/image.jpg?ref=f1r&amp;q=f1r-256-202-1027-1232&amp;w=1027&amp;h=1232&amp;resize=0.5&amp;output=jpg&amp;padding=0&amp;border=0&amp;paddingColor=white&amp;borderColor=black&amp;caption=1" loading="lazy"  alt="[Image: image.jpg?ref=f1r&amp;q=f1r-256-202-1027-123...&amp;caption=1]" class="mycode_img" /><br />
<br />
This habit is clear throughout the manuscript and all scribes follow the same layout instruction<br />
<img src="https://www.voynich.ninja/extractor/image.jpg?ref=f43v&amp;q=f43v-417-164-982-608&amp;w=982&amp;h=608&amp;resize=0.5&amp;output=jpg&amp;padding=0&amp;border=0&amp;paddingColor=white&amp;borderColor=black&amp;caption=1" loading="lazy"  alt="[Image: image.jpg?ref=f43v&amp;q=f43v-417-164-982-60...&amp;caption=1]" class="mycode_img" /><br />
<br />
It is striking that the same layout instructions were applied by all scribes across all sections of the manuscript. A template, even if only verbal instructions, was given for layout and this was applied across the manuscript. The same layout was used for page after page, this indicates a conscience decision and even a group instruction issued if indeed multiple scribes were used<br />
<img src="https://www.voynich.ninja/extractor/image.jpg?ref=f115r&amp;q=f115r-101-66-1181-949&amp;w=1181&amp;h=949&amp;resize=1&amp;output=jpg&amp;resize=0.5&amp;padding=0&amp;border=0&amp;paddingColor=white&amp;borderColor=black&amp;caption=1" loading="lazy"  alt="[Image: image.jpg?ref=f115r&amp;q=f115r-101-66-1181-...&amp;caption=1]" class="mycode_img" /><br />
<br />
<span style="font-weight: bold;" class="mycode_b">How did paragraphs work?</span><br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>But while distinction of words was disregarded in early literary texts, distinction of important pauses in the sense was recognized from the first. The papyrus of the Persae of Timotheus of Miletus, the oldest MS. of a Greek classic in existence, of the end of the 4th century B.C., is written in independent paragraphs. This is a natural system, the simplicity of which has caused it to be the system of modern times. But, in addition, the Greek scribe also separated paragraphs by inserting a short horizontal stroke, παράγραφος, between them at the commencement of the lines of writing. It should be noted that this stroke indicated the close of a passage, and therefore belonged to the paragraph just concluded, and did not stand for an initial sign for the new paragraph which followed. The dividing stroke was also used to mark off the different speeches of a play. Besides the stroke, a wedge-shaped sign or tick might be used. But to make every paragraph stand distinctly by itself would have entailed a certain loss of space. If the concluding line were short, there would remain a long space unfilled. Therefore, when this occurred, it became customary to leave only a short space blank to mark the termination of the paragraph, and then to proceed with the new paragraph in the same line, the παράγραφος at the same time preventing possible ambiguity. The next step was to project the first letter of the first full line of the new paragraph slightly into the margin, as a still further distinction; and lastly to enlarge it. The enlargement of the letter gave it so much prominence that the dividing stroke could then be dispensed with, and in this form the new paragraph was henceforward indicated in Greek MSS., it being immaterial whether the enlarged letter was the initial or a medial letter of a word. As early as the 5th century there is evidence that the παράγραφος was losing its meaning with the scribes, for in the Codex Alexandrinus of the Bible it is not infrequently found in anomalous positions, particularly above the initial letters of different books, as if it were a mere ornament.<br />
<span style="font-style: italic;" class="mycode_i">Encyclopedia Britannica - Manuscript entry </span></blockquote>
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>The paragraph mark, enlarged initial, and disposition of text on the page formed part of an integrated system for indicating textual articulation. Medieval scribes indicated divisions in a text by combining graphic devices such as enlarged initials, paragraph signs, and the arrangement of lines on the page. These visual cues enabled readers to recognise the structure of the text without relying solely on punctuation. Malcolm B. Parkes — Pause and Effect p.65</blockquote>
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite><span style="font-weight: bold;" class="mycode_b">Colometry</span>. A modification of the practice of writing the text continuously was allowed in the case of certain works. Rhetorical texts, such as the orations of Demosthenes and Cicero, and the text of the Bible, might be broken up into short clauses or sense-lines, apparently with the view of assisting reading aloud. Instances of MSS. so written are still extant. This system, to which the name of “colometry” has been given, is the arrangement by cola and commata referred to by St Jerome in his preface to Isaiah. It will be found more fully explained under the heading of Stichometry; where also is described the mechanical computation of the length of a text by measured lines, for the purpose or calculating the pay of the scribe. <span style="font-style: italic;" class="mycode_i">Encyclopedia Britannica - Manuscript entry</span></blockquote>
<br />
Medieval scribes were extremely reluctant to waste expensive parchment, so paragraph identification was almost always redundant. They combined several cues:<br />
<ul class="mycode_list"><li>new line,<br />
</li>
<li>enlarged initial,<br />
</li>
<li>rubrication,<br />
</li>
<li>paragraph mark,<br />
</li>
<li>marginal projection.<br />
</li>
</ul>
<br />
A new line by itself was generally considered "too subtle" unless for the reason of Colometry.<br />
<br />
The Voynich often signals a paragraph by:<br />
<ul class="mycode_list"><li>beginning on a fresh line,<br />
</li>
<li>using an enlarged "gallows" glyph,<br />
</li>
<li>leaving a visibly short final line in the previous paragraph without bothering about justification or waste of parchment.<br />
</li>
</ul>
<br />
Notably, it does not employ coloured initials or rubricated pilcrows, which were among the commonest medieval paragraph markers and which would have been instantly identifiable to any medieval reader. That makes its paragraphing <span style="font-weight: bold;" class="mycode_b">visually simpler </span>than many contemporary manuscripts while still conforming to the broader medieval practice of marking new textual units through line breaks and paragraph-initial emphasis.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">What am I getting at?</span><br />
<br />
If we discard the idea that the Voynich was designed to be read aloud - clearly most of it was not - then what influence caused the authors to choose and stay with this particular layout throughout the whole of the book?<br />
<br />
I think the closest structural comparators are not illuminated or library books but plain working manuscripts—medical recipe books, university notebooks, and practical handbooks copied between about 1400 and 1450. We often see new-line paragraphing with minimal decoration and no attempt at justification.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">What style could the scribes have been influenced by?</span><ul class="mycode_list"><li>Medical recipe books (Receptaria) <br />
</li>
<li>Astrological almanacs with prognostications <br />
</li>
<li>Practical herbals – especially those copied by working physicians rather than produced as luxury manuscripts<br />
</li>
</ul>
<br />
These genres routinely consist of dozens or hundreds of short, self-contained entries beginning on a new line, and they are among the closest surviving medieval layouts to the Voynich's "recipe" section. We also see many clues to the Voynich being influenced by these working books, for example, many years ago we chased down examples of the Zodiac being influenced by the German hausbach calendar tradition, especially the crossbowman. This forum contains many examples.<br />
<br />
In short, the layout and visual clues in the Voynich points to the authors being influenced more by working books than by library books. <br />
<br />
However, in many ways the Voynich has a much higher "production value" than these working books. It is much longer than most working books, many of which would have been produced by just one scribe. <br />
<br />
The images are of a higher quality. The layout of the text is much clearer and more professional. There appear to have been a team of production scribes working on the book. The quality of the parchment is higher and there is no real attempt to maximise the use of the parchment real estate. Multiple colour inks are used with care and attention to detail.<br />
<br />
We are, once again, faced with a paradox. The Voynich layout and style is influenced by working books; its use of materials and multiple scribes suggests high end resources were available for its production.]]></description>
			<content:encoded><![CDATA[The formatting of the text is quite simple for the era. I am not interested here in the text analysis but in the way it is presented on the page.<br />
If we look at standard manuscripts or incunabula (usually agreed to be visually the same as their hand written equivalents) from, say, 1450 - 1500 we see text written in blocks, not paragraphs. <br />
Many manuscripts will have clear paragraph markers -pilcrows-, usually distinguishable by a different colour or size, to break up information units, rather than the modern usage of using a line break, as I am doing in this post. You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view..<br />
<br />
The Voynich, from the very first page, uses the line break format accompanied by a pilcrow.<br />
<img src="https://www.voynich.ninja/extractor/image.jpg?ref=f1r&amp;q=f1r-256-202-1027-1232&amp;w=1027&amp;h=1232&amp;resize=0.5&amp;output=jpg&amp;padding=0&amp;border=0&amp;paddingColor=white&amp;borderColor=black&amp;caption=1" loading="lazy"  alt="[Image: image.jpg?ref=f1r&amp;q=f1r-256-202-1027-123...&amp;caption=1]" class="mycode_img" /><br />
<br />
This habit is clear throughout the manuscript and all scribes follow the same layout instruction<br />
<img src="https://www.voynich.ninja/extractor/image.jpg?ref=f43v&amp;q=f43v-417-164-982-608&amp;w=982&amp;h=608&amp;resize=0.5&amp;output=jpg&amp;padding=0&amp;border=0&amp;paddingColor=white&amp;borderColor=black&amp;caption=1" loading="lazy"  alt="[Image: image.jpg?ref=f43v&amp;q=f43v-417-164-982-60...&amp;caption=1]" class="mycode_img" /><br />
<br />
It is striking that the same layout instructions were applied by all scribes across all sections of the manuscript. A template, even if only verbal instructions, was given for layout and this was applied across the manuscript. The same layout was used for page after page, this indicates a conscience decision and even a group instruction issued if indeed multiple scribes were used<br />
<img src="https://www.voynich.ninja/extractor/image.jpg?ref=f115r&amp;q=f115r-101-66-1181-949&amp;w=1181&amp;h=949&amp;resize=1&amp;output=jpg&amp;resize=0.5&amp;padding=0&amp;border=0&amp;paddingColor=white&amp;borderColor=black&amp;caption=1" loading="lazy"  alt="[Image: image.jpg?ref=f115r&amp;q=f115r-101-66-1181-...&amp;caption=1]" class="mycode_img" /><br />
<br />
<span style="font-weight: bold;" class="mycode_b">How did paragraphs work?</span><br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>But while distinction of words was disregarded in early literary texts, distinction of important pauses in the sense was recognized from the first. The papyrus of the Persae of Timotheus of Miletus, the oldest MS. of a Greek classic in existence, of the end of the 4th century B.C., is written in independent paragraphs. This is a natural system, the simplicity of which has caused it to be the system of modern times. But, in addition, the Greek scribe also separated paragraphs by inserting a short horizontal stroke, παράγραφος, between them at the commencement of the lines of writing. It should be noted that this stroke indicated the close of a passage, and therefore belonged to the paragraph just concluded, and did not stand for an initial sign for the new paragraph which followed. The dividing stroke was also used to mark off the different speeches of a play. Besides the stroke, a wedge-shaped sign or tick might be used. But to make every paragraph stand distinctly by itself would have entailed a certain loss of space. If the concluding line were short, there would remain a long space unfilled. Therefore, when this occurred, it became customary to leave only a short space blank to mark the termination of the paragraph, and then to proceed with the new paragraph in the same line, the παράγραφος at the same time preventing possible ambiguity. The next step was to project the first letter of the first full line of the new paragraph slightly into the margin, as a still further distinction; and lastly to enlarge it. The enlargement of the letter gave it so much prominence that the dividing stroke could then be dispensed with, and in this form the new paragraph was henceforward indicated in Greek MSS., it being immaterial whether the enlarged letter was the initial or a medial letter of a word. As early as the 5th century there is evidence that the παράγραφος was losing its meaning with the scribes, for in the Codex Alexandrinus of the Bible it is not infrequently found in anomalous positions, particularly above the initial letters of different books, as if it were a mere ornament.<br />
<span style="font-style: italic;" class="mycode_i">Encyclopedia Britannica - Manuscript entry </span></blockquote>
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>The paragraph mark, enlarged initial, and disposition of text on the page formed part of an integrated system for indicating textual articulation. Medieval scribes indicated divisions in a text by combining graphic devices such as enlarged initials, paragraph signs, and the arrangement of lines on the page. These visual cues enabled readers to recognise the structure of the text without relying solely on punctuation. Malcolm B. Parkes — Pause and Effect p.65</blockquote>
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite><span style="font-weight: bold;" class="mycode_b">Colometry</span>. A modification of the practice of writing the text continuously was allowed in the case of certain works. Rhetorical texts, such as the orations of Demosthenes and Cicero, and the text of the Bible, might be broken up into short clauses or sense-lines, apparently with the view of assisting reading aloud. Instances of MSS. so written are still extant. This system, to which the name of “colometry” has been given, is the arrangement by cola and commata referred to by St Jerome in his preface to Isaiah. It will be found more fully explained under the heading of Stichometry; where also is described the mechanical computation of the length of a text by measured lines, for the purpose or calculating the pay of the scribe. <span style="font-style: italic;" class="mycode_i">Encyclopedia Britannica - Manuscript entry</span></blockquote>
<br />
Medieval scribes were extremely reluctant to waste expensive parchment, so paragraph identification was almost always redundant. They combined several cues:<br />
<ul class="mycode_list"><li>new line,<br />
</li>
<li>enlarged initial,<br />
</li>
<li>rubrication,<br />
</li>
<li>paragraph mark,<br />
</li>
<li>marginal projection.<br />
</li>
</ul>
<br />
A new line by itself was generally considered "too subtle" unless for the reason of Colometry.<br />
<br />
The Voynich often signals a paragraph by:<br />
<ul class="mycode_list"><li>beginning on a fresh line,<br />
</li>
<li>using an enlarged "gallows" glyph,<br />
</li>
<li>leaving a visibly short final line in the previous paragraph without bothering about justification or waste of parchment.<br />
</li>
</ul>
<br />
Notably, it does not employ coloured initials or rubricated pilcrows, which were among the commonest medieval paragraph markers and which would have been instantly identifiable to any medieval reader. That makes its paragraphing <span style="font-weight: bold;" class="mycode_b">visually simpler </span>than many contemporary manuscripts while still conforming to the broader medieval practice of marking new textual units through line breaks and paragraph-initial emphasis.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">What am I getting at?</span><br />
<br />
If we discard the idea that the Voynich was designed to be read aloud - clearly most of it was not - then what influence caused the authors to choose and stay with this particular layout throughout the whole of the book?<br />
<br />
I think the closest structural comparators are not illuminated or library books but plain working manuscripts—medical recipe books, university notebooks, and practical handbooks copied between about 1400 and 1450. We often see new-line paragraphing with minimal decoration and no attempt at justification.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">What style could the scribes have been influenced by?</span><ul class="mycode_list"><li>Medical recipe books (Receptaria) <br />
</li>
<li>Astrological almanacs with prognostications <br />
</li>
<li>Practical herbals – especially those copied by working physicians rather than produced as luxury manuscripts<br />
</li>
</ul>
<br />
These genres routinely consist of dozens or hundreds of short, self-contained entries beginning on a new line, and they are among the closest surviving medieval layouts to the Voynich's "recipe" section. We also see many clues to the Voynich being influenced by these working books, for example, many years ago we chased down examples of the Zodiac being influenced by the German hausbach calendar tradition, especially the crossbowman. This forum contains many examples.<br />
<br />
In short, the layout and visual clues in the Voynich points to the authors being influenced more by working books than by library books. <br />
<br />
However, in many ways the Voynich has a much higher "production value" than these working books. It is much longer than most working books, many of which would have been produced by just one scribe. <br />
<br />
The images are of a higher quality. The layout of the text is much clearer and more professional. There appear to have been a team of production scribes working on the book. The quality of the parchment is higher and there is no real attempt to maximise the use of the parchment real estate. Multiple colour inks are used with care and attention to detail.<br />
<br />
We are, once again, faced with a paradox. The Voynich layout and style is influenced by working books; its use of materials and multiple scribes suggests high end resources were available for its production.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Word boundaries "dl"]]></title>
			<link>https://www.voynich.ninja/thread-5957.html</link>
			<pubDate>Sat, 25 Jul 2026 12:03:51 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3690">ololololo</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-5957.html</guid>
			<description><![CDATA[In You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view., I noticed a peculiar feature when comparing words with You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view. with the text of f104r.28: sometimes the boundary between words was the combination of <span style="font-family: Eva;" class="mycode_font">dl</span>. Of course, my work is still somewhat questionable, but I found this observation interesting.<br />
I decided to test the behavior of this combination in a manuscript. It appears in both Currier A and Currier B. In both cases, the combinations behave in the same way - either they stand alone or they are combined with words like <span style="font-family: Eva;" class="mycode_font">ch</span> (e.g., <span style="font-family: Eva;" class="mycode_font">chdlety </span><span style="font-family: Arial;" class="mycode_font">f47v</span>).<br />
In the recipe section, this combination is often found next to <span style="font-family: Eva;" class="mycode_font">d</span>. Examples: <span style="font-family: Eva;" class="mycode_font">daindl, dlchd, opcheddl, ckhddl, oteeodl.</span><br />
Before <span style="font-family: Eva;" class="mycode_font">dl</span>, there may be an <span style="font-family: Eva;" class="mycode_font">o</span>, and in one case they form one word together (<span style="font-family: Eva;" class="mycode_font">odl</span>, also often in the recipe section), while in the other case the previous word ends with <span style="font-family: Eva;" class="mycode_font">o</span> (examples:<span style="font-family: Eva;" class="mycode_font"> tocheo dlchy</span>; <span style="font-family: Eva;" class="mycode_font">oteeodl</span>)<br />
Of course, these observations are not enough to draw any conclusions, but we can make some assumptions.<br />
It is possible that the combination of <span style="font-family: Eva;" class="mycode_font">dl</span> carries the meaning of distinguishing between words. It is also possible that this combination arises from the division of text into combinations of letters (as in many classical ciphers, the text is first divided into bigrams or trigrams).<br />
<br />
<span style="font-weight: bold;" class="mycode_b">What do you think?</span>]]></description>
			<content:encoded><![CDATA[In You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view., I noticed a peculiar feature when comparing words with You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view. with the text of f104r.28: sometimes the boundary between words was the combination of <span style="font-family: Eva;" class="mycode_font">dl</span>. Of course, my work is still somewhat questionable, but I found this observation interesting.<br />
I decided to test the behavior of this combination in a manuscript. It appears in both Currier A and Currier B. In both cases, the combinations behave in the same way - either they stand alone or they are combined with words like <span style="font-family: Eva;" class="mycode_font">ch</span> (e.g., <span style="font-family: Eva;" class="mycode_font">chdlety </span><span style="font-family: Arial;" class="mycode_font">f47v</span>).<br />
In the recipe section, this combination is often found next to <span style="font-family: Eva;" class="mycode_font">d</span>. Examples: <span style="font-family: Eva;" class="mycode_font">daindl, dlchd, opcheddl, ckhddl, oteeodl.</span><br />
Before <span style="font-family: Eva;" class="mycode_font">dl</span>, there may be an <span style="font-family: Eva;" class="mycode_font">o</span>, and in one case they form one word together (<span style="font-family: Eva;" class="mycode_font">odl</span>, also often in the recipe section), while in the other case the previous word ends with <span style="font-family: Eva;" class="mycode_font">o</span> (examples:<span style="font-family: Eva;" class="mycode_font"> tocheo dlchy</span>; <span style="font-family: Eva;" class="mycode_font">oteeodl</span>)<br />
Of course, these observations are not enough to draw any conclusions, but we can make some assumptions.<br />
It is possible that the combination of <span style="font-family: Eva;" class="mycode_font">dl</span> carries the meaning of distinguishing between words. It is also possible that this combination arises from the division of text into combinations of letters (as in many classical ciphers, the text is first divided into bigrams or trigrams).<br />
<br />
<span style="font-weight: bold;" class="mycode_b">What do you think?</span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[The o's in VMS]]></title>
			<link>https://www.voynich.ninja/thread-5947.html</link>
			<pubDate>Wed, 22 Jul 2026 01:11:57 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3823">bvanheu</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-5947.html</guid>
			<description><![CDATA[Hi!<br />
<br />
I can't help but notice there are different kind of ways O's are drawn in VMS. I always starts my O from the top going counterclockwise. I've exagerated the traits in KolourPaint to show the starting point and direction. There doesn't seem to be a pattern (e.g. whole page written with O from bottom). The most common O seems to be starting from the top.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Starting from the top</span><br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16702" target="_blank" title="">top_o_1.png</a> (Size: 28.79 KB / Downloads: 228)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16701" target="_blank" title="">top_o_2.png</a> (Size: 19.39 KB / Downloads: 337)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16700" target="_blank" title="">top_o_3.png</a> (Size: 78.94 KB / Downloads: 227)
<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Starting from bottom</span><br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16705" target="_blank" title="">bottom_o_1.png</a> (Size: 16.52 KB / Downloads: 335)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16704" target="_blank" title="">bottom_o_2.png</a> (Size: 62.33 KB / Downloads: 224)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16703" target="_blank" title="">bottom_o_3.png</a> (Size: 38.59 KB / Downloads: 228)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16699" target="_blank" title="">bottom_o_4.png</a> (Size: 25.67 KB / Downloads: 337)
<br />
<br />
<span style="font-weight: bold;" class="mycode_b">In two quill traits</span><br />
<br />
These could be EVA a though?<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16698" target="_blank" title="">weird_o_1.png</a> (Size: 26.28 KB / Downloads: 334)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16697" target="_blank" title="">weird_o_2.png</a> (Size: 37.41 KB / Downloads: 231)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16696" target="_blank" title="">weird_o_3.png</a> (Size: 21.59 KB / Downloads: 337)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16695" target="_blank" title="">weird_o_4.png</a> (Size: 25.55 KB / Downloads: 336)
]]></description>
			<content:encoded><![CDATA[Hi!<br />
<br />
I can't help but notice there are different kind of ways O's are drawn in VMS. I always starts my O from the top going counterclockwise. I've exagerated the traits in KolourPaint to show the starting point and direction. There doesn't seem to be a pattern (e.g. whole page written with O from bottom). The most common O seems to be starting from the top.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Starting from the top</span><br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16702" target="_blank" title="">top_o_1.png</a> (Size: 28.79 KB / Downloads: 228)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16701" target="_blank" title="">top_o_2.png</a> (Size: 19.39 KB / Downloads: 337)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16700" target="_blank" title="">top_o_3.png</a> (Size: 78.94 KB / Downloads: 227)
<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Starting from bottom</span><br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16705" target="_blank" title="">bottom_o_1.png</a> (Size: 16.52 KB / Downloads: 335)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16704" target="_blank" title="">bottom_o_2.png</a> (Size: 62.33 KB / Downloads: 224)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16703" target="_blank" title="">bottom_o_3.png</a> (Size: 38.59 KB / Downloads: 228)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16699" target="_blank" title="">bottom_o_4.png</a> (Size: 25.67 KB / Downloads: 337)
<br />
<br />
<span style="font-weight: bold;" class="mycode_b">In two quill traits</span><br />
<br />
These could be EVA a though?<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16698" target="_blank" title="">weird_o_1.png</a> (Size: 26.28 KB / Downloads: 334)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16697" target="_blank" title="">weird_o_2.png</a> (Size: 37.41 KB / Downloads: 231)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16696" target="_blank" title="">weird_o_3.png</a> (Size: 21.59 KB / Downloads: 337)
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16695" target="_blank" title="">weird_o_4.png</a> (Size: 25.55 KB / Downloads: 336)
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Non-linear line ordering]]></title>
			<link>https://www.voynich.ninja/thread-5943.html</link>
			<pubDate>Sun, 19 Jul 2026 15:41:08 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3823">bvanheu</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-5943.html</guid>
			<description><![CDATA[I think this was discussed in the past (i.e. in the "gallow intrusion" thread), but in You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view. and f58v, there seem to be evidence that some lines were written after the immediate bottom line, with glyph from the top line being written over the glyph from the bottom line?<br />
<br />
If the gallow was written after the top line, why make it so big that it extends over the above glyph?<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16671" target="_blank" title="">f58v_2.png</a> (Size: 136.83 KB / Downloads: 202)
<br />
<br />
Why start the gallow line so that it's *over* the glyph above?<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16672" target="_blank" title="">20260719_11h20m51s_grim.png</a> (Size: 105.36 KB / Downloads: 204)
<br />
<br />
It seems to me the tail has been made in one continuous trait?<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16673" target="_blank" title="">20260719_11h19m26s_grim.png</a> (Size: 113.14 KB / Downloads: 201)
<br />
<br />
Is there a concensus around line ordering, beside that "block of text" were written before/after others?<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16674" target="_blank" title="">20260719_11h35m25s_grim.png</a> (Size: 121.22 KB / Downloads: 184)
]]></description>
			<content:encoded><![CDATA[I think this was discussed in the past (i.e. in the "gallow intrusion" thread), but in You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view. and f58v, there seem to be evidence that some lines were written after the immediate bottom line, with glyph from the top line being written over the glyph from the bottom line?<br />
<br />
If the gallow was written after the top line, why make it so big that it extends over the above glyph?<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16671" target="_blank" title="">f58v_2.png</a> (Size: 136.83 KB / Downloads: 202)
<br />
<br />
Why start the gallow line so that it's *over* the glyph above?<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16672" target="_blank" title="">20260719_11h20m51s_grim.png</a> (Size: 105.36 KB / Downloads: 204)
<br />
<br />
It seems to me the tail has been made in one continuous trait?<br />
<br />

<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16673" target="_blank" title="">20260719_11h19m26s_grim.png</a> (Size: 113.14 KB / Downloads: 201)
<br />
<br />
Is there a concensus around line ordering, beside that "block of text" were written before/after others?<br />
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
&nbsp;&nbsp;<a href="attachment.php?aid=16674" target="_blank" title="">20260719_11h35m25s_grim.png</a> (Size: 121.22 KB / Downloads: 184)
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[m on side for Michał f42v, W on side for Wojnicz 1r]]></title>
			<link>https://www.voynich.ninja/thread-5926.html</link>
			<pubDate>Thu, 16 Jul 2026 04:08:46 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://www.voynich.ninja/member.php?action=profile&uid=3820">conlangyalesbaby</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.voynich.ninja/thread-5926.html</guid>
			<description><![CDATA[
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
&nbsp;&nbsp;<a href="attachment.php?aid=16617" target="_blank" title="">M for Michal.JPG</a> (Size: 6.79 KB / Downloads: 259)
<br />
<br />
The <span style="font-family: Eva;" class="mycode_font">sh</span> glyph has an m on its side You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view..  Is the evidence for <span style="font-weight: bold;" class="mycode_b"><span style="color: #202122;" class="mycode_color"><span style="font-family: sans-serif;" class="mycode_font">Michał Habdank-Wojnicz?</span></span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="color: #202122;" class="mycode_color"><span style="font-family: sans-serif;" class="mycode_font">
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
&nbsp;&nbsp;<a href="attachment.php?aid=16618" target="_blank" title="">W for x.JPG</a> (Size: 25.17 KB / Downloads: 258)
</span></span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="color: #202122;" class="mycode_color"><span style="font-family: sans-serif;" class="mycode_font">Also for You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view. there is a w on it's side for Pi upside down. Could it be Wojnicz?  That would be the </span><span style="font-family: Eva;" class="mycode_font">x</span><span style="font-family: sans-serif;" class="mycode_font"> glyph!</span></span></span>]]></description>
			<content:encoded><![CDATA[
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
&nbsp;&nbsp;<a href="attachment.php?aid=16617" target="_blank" title="">M for Michal.JPG</a> (Size: 6.79 KB / Downloads: 259)
<br />
<br />
The <span style="font-family: Eva;" class="mycode_font">sh</span> glyph has an m on its side You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view..  Is the evidence for <span style="font-weight: bold;" class="mycode_b"><span style="color: #202122;" class="mycode_color"><span style="font-family: sans-serif;" class="mycode_font">Michał Habdank-Wojnicz?</span></span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="color: #202122;" class="mycode_color"><span style="font-family: sans-serif;" class="mycode_font">
<br />
<img src="https://www.voynich.ninja/images/attachtypes/image.png" title="JPG Image" border="0" alt=".jpg" />
&nbsp;&nbsp;<a href="attachment.php?aid=16618" target="_blank" title="">W for x.JPG</a> (Size: 25.17 KB / Downloads: 258)
</span></span></span><br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="color: #202122;" class="mycode_color"><span style="font-family: sans-serif;" class="mycode_font">Also for You are not allowed to view links. <a href="https://www.voynich.ninja/member.php?action=register">Register</a> or <a href="https://www.voynich.ninja/member.php?action=login">Login</a> to view. there is a w on it's side for Pi upside down. Could it be Wojnicz?  That would be the </span><span style="font-family: Eva;" class="mycode_font">x</span><span style="font-family: sans-serif;" class="mycode_font"> glyph!</span></span></span>]]></content:encoded>
		</item>
	</channel>
</rss>