The Voynich Ninja
A One-Page Ledger Method for Generating Voynich-Like Text - Printable Version

+- The Voynich Ninja (https://www.voynich.ninja)
+-- Forum: Voynich Research (https://www.voynich.ninja/forum-27.html)
+--- Forum: Analysis of the text (https://www.voynich.ninja/forum-41.html)
+--- Thread: A One-Page Ledger Method for Generating Voynich-Like Text (/thread-5752.html)

Pages: 1 2 3 4 5 6 7 8 9 10 11


RE: A One-Page Ledger Method for Generating Voynich-Like Text - oshfdk - 18-05-2026

(17-05-2026, 11:47 PM)Torsten Wrote: You are not allowed to view links. Register or Login to view.Because formalizing the process lets you test it. You can't test "a scribe imitating visual patterns" — it's too vague. You can test "a scribe copying visible words and modifying them by substituting similar glyphs" — it makes specific, falsifiable predictions about word networks, spatial clustering, frequency-connectivity correlation, and positional effects.

I understand that "a scribe imitating visual patterns" can be modeled by listing some specific rules and running some statistical tests to check whether applying these rules can produce something similar to the Voynich MS. But to me this raises two points (would be perfect if this already covered in some of your papers, but it's been a while since I read them, and to be frank I didn't study them deeply, mostly the set up and the conclusions):

1. Matching visual patterns is a much broader process than just modifying words glyph by glyph. The existence of the curve line system may suggest that Voynichese words are visually constrained, and it's possible that the actual self-citation might not work at glyph level at all. For example, maybe it works at stroke level, rearranging strokes according to some rules. Using only glyph-based rules is much easier for testing, but may miss some important part of the visual process. Is it likely that the rules defined using glyph codes may not be a good proxy for how the manuscript was created at all?

   
To give an example of what I'm talking about, this k m f pattern from You are not allowed to view links. Register or Login to view. 4x17 sequence could represent some evolution in shapes, with m looking like a mid point transit character of k and f. When a scribe works on modifying and mixing visual patterns, the process may not involve splitting a word glyph by glyph, but rather working on a different arrangement of similar strokes.

2. While it's easy to devise a test that would show that self-citation is possible, how to tell apart self citation as primary text generation method from actual citation, as in using past words to actually refer to the same or similar concepts in the text, especially in the context of a constructed language? To give a specific fictional example, imagine a constructed language where the vocabulary is expanded as needed while writing the text (similar to how a nomenclator would be populated), where new concepts are introduced by modifying words for already existing concepts according to some loose rules (essentially this is not unlike how many Chinese characters work). Suppose the text is talking about heat and denotes heat as daiin. On the next page a word for fire is needed, so we use a loose rule of adding o- for intensification and call it odaiin. Then if we need a word for scorching, but odaiin is already taken, so we pop on some extra disambiguation prefix like qodaiin. While this looks very much like citation, in fact we don't even look at the past pages, to write a new word we just consult the dictionary and if it's not there we add a new entry. Will this produce essentially the same patterns as the self-citation?


RE: A One-Page Ledger Method for Generating Voynich-Like Text - oshfdk - 18-05-2026

(18-05-2026, 10:22 PM)oshfdk Wrote: You are not allowed to view links. Register or Login to view.To give a specific fictional example, imagine a constructed language where the vocabulary is expanded as needed while writing the text (similar to how a nomenclator would be populated), where new concepts are introduced by modifying words for already existing concepts according to some loose rules (essentially this is not unlike how many Chinese characters work). Suppose the text is talking about heat and denotes heat as daiin. On the next page a word for fire is needed, so we use a loose rule of adding o- for intensification and call it odaiin. Then if we need a word for scorching, but odaiin is already taken, so we pop on some extra disambiguation prefix like qodaiin.

By the way, to make it less anachronistic, we can think of this not as of a constructed language, but as a mnemonic nomenclator. The main problem with the nomenclator ciphers, as I understand it, they are very hard to read and write since there is no connection between the code and the word. However, if new codes are extensions of related existing codes, this provides built in mnemonics (daiin words are all related to heat) and ease of lookup both ways. When writing a word related to heat you have to look it up on the 'daiin' page of the nomenclator and when decoding word 'olchedaiin' you will know to look it up on the 'daiin' page too, instead of keeping two separate word to index and index to word dictionaries. Again, similar to how Chinese character radicals work.


RE: A One-Page Ledger Method for Generating Voynich-Like Text - Torsten - 19-05-2026

(18-05-2026, 10:22 PM)oshfdk Wrote: You are not allowed to view links. Register or Login to view.1. Matching visual patterns is a much broader process than just modifying words glyph by glyph. The existence of the curve line system may suggest that Voynichese words are visually constrained, and it's possible that the actual self-citation might not work at glyph level at all. For example, maybe it works at stroke level, rearranging strokes according to some rules. Using only glyph-based rules is much easier for testing, but may miss some important part of the visual process. Is it likely that the rules defined using glyph codes may not be a good proxy for how the manuscript was created at all?

You're right that the scribe did operate at the stroke level. Currier noted in 1976 that the glyphs are built from shared base strokes — "you can make up almost any of the other letters out of these two symbols." A glyph has a shape but the glyph consists at the same time of strokes. 

For instance the ligature <ch> consists of two <e>-glyphs connected by a dash. But there are also instances of three <e> strokes connected with a dash like in You are not allowed to view links. Register or Login to view. on f82r. My Rule 1 — replace one or more glyphs by similar ones — is a glyph-level formalization of what is often a stroke level modification like the additional stroke changing "ch" into "sh".

Voynich words are also visually constrained. Schwerdtfeger described in 2008 the following four design rules for Voynich words: (1) line-glyphs can follow line-glyphs or <a>; (2) curve-glyphs and <a> can follow curve-glyphs; (3) the <l>-glyph can be used as a curve-glyph or as a line-glyph; and (4) gallows glyphs count as curve glyphs.

(18-05-2026, 10:22 PM)oshfdk Wrote: You are not allowed to view links. Register or Login to view.2. While it's easy to devise a test that would show that self-citation is possible, how to tell apart self citation as primary text generation method from actual citation, as in using past words to actually refer to the same or similar concepts in the text, especially in the context of a constructed language?

Your constructed language scenario — where "daiin" means "heat," "odaiin" means "fire," "qodaiin" means "scorching" — is a genuine alternative that would produce similar word families. But it makes predictions the VMS doesn't satisfy:

A constructed language dictionary produces consistent usage. If "daiin" means "heat," it should appear in consistent semantic contexts. In the VMS, "daiin" appears everywhere — in every section, next to every kind of word. No semantic clustering is detectable.

A constructed language doesn't show a continuous evolutionary gradient. If the dictionary is fixed, the vocabulary shouldn't evolve from section to section. But the VMS shows "chol" dominant in early sections, "chedy" dominant in late sections, with smooth intermediate stages. A dictionary doesn't evolve — a copying process does (see You are not allowed to view links. Register or Login to view.).

Continuous evolution follows from the incremental nature of the modification process. Each new word differs minimally from its source; accumulated modifications over many copying events produce gradual vocabulary drift. The direction of evolution is determined by the asymmetry of the process: new variants can only appear after their source words exist, creating a temporal arrow from early forms to late forms. “Words typical for Currier A also exist in Currier B, but not the other way round,” because late-emerging variants “could not appear on pages written previously” (Timm and Schinner, 2020, pp. 8–9). This is “an automatic side-effect” of the process, not evidence of changing writing strategies.

A constructed language doesn't show line-boundary production effects. If words have fixed meanings, their form shouldn't depend on line position. But some words appear almost exclusively at line starts or line ends. For instance "dsheey" appears at line starts 7 out of 8 times (see You are not allowed to view links. Register or Login to view.). Words looked up in a dictionary don't care about margins. The reason is that "the source for the first word in each line could only be found within the previous lines. Since the first and the last word in each line are easy to spot, the most obvious way is to pick them as a source for the generation of a group at the beginning or at the end of a line. For the second glyph group it is also possible to select the first group as a source. Since the first group in a line usually has a prefix the simplest change is to remove this prefix." (Timm 2014, p. 19). This is the reason that the second glyph group is shorter than the first group in 48% of the lines and longer in only 32% leading to the following statistical observation by Elmar Vogt:
    [You are not allowed to view links. Register or Login to view. 2012: p. 4].

A constructed language doesn't show cross-line independence. If the text carries meaning, that meaning should continue across line breaks — sentences span lines in any meaningful text. But quimqu showed that within-line predictability is strong (~30% top-1) while cross-line predictability drops to near random. A text composed from a dictionary doesn't reset at line boundaries.

A constructed language with semantic prefixes doesn't show prefix-suffix independence. If "o-" means intensification, then prefix choice constrains meaning, which constrains which suffixes co-occur — because you don't intensify every concept equally often. But as you and dashstofsk demonstrated, prefix and suffix are selected nearly independently in the VMS. A semantic prefix system produces dependencies. A copying system produces independence.

See Table 3 in Timm & Schinner 2020, p. 10:
   
Note that this table reproduces the most frequent word types <daiin>, <ol>, and <chedy>.

A constructed language with semantic prefixes also wouldn't produce the frequency hierarchy observed in the VMS. In a semantic system, word frequency reflects how often a concept is discussed — unrelated to the word's visual similarity to other words. In the VMS, frequency and visual similarity are directly correlated. For instance, in most cases, words with "sh" are less frequent than the corresponding variant using "ch". Also words using "p" or "f" instead of "k" and "t" are generally less frequent. The frequency-connectivity correlation arises through a feedback loop inherent in the copying process. Frequent words are more likely to be selected as copying templates, generating more variants; the existence of more variants increases the probability that members of that word family are selected in subsequent copying events. This self reinforcing cycle ensures that the most frequently used words accumulate the most similar neighbors.

Your scenario is testable — and each test distinguishes it from self-citation. The VMS matches the self-citation predictions and fails the constructed-language predictions.


RE: A One-Page Ledger Method for Generating Voynich-Like Text - Dunsel - 19-05-2026

(19-05-2026, 12:49 AM)Torsten Wrote: You are not allowed to view links. Register or Login to view.A constructed language doesn't show a continuous evolutionary gradient. If the dictionary is fixed, the vocabulary shouldn't evolve from section to section. But the VMS shows "chol" dominant in early sections, "chedy" dominant in late sections, with smooth intermediate stages. A dictionary doesn't evolve — a copying process does (see You are not allowed to view links. Register or Login to view.).

I'm not convinced the ho/ed bigram evidence supports a continuous drift model. If ed/Currier B/Scribe 2+ emerged gradually through incremental copy-mutate, I would expect broad transitional zones and smooth redistribution of ed behavior across folios. Instead, the ed distribution appears highly clustered, with long stable low-ed regions written by Scribe 1 followed by abrupt activation zones written by Scribe 2+.  That aligns much more closely with production/scribal boundaries than with lexical drift.

The attached charts are difficult to reconcile with a purely continuous evolution model. ho/Scribe 1/Currier A folios remain remarkably stable and locally reducible, while ED+/Scribe 2 behavior expands abruptly rather than progressively. That looks less like slow drift and more like a regime change in production methods or weighting strategy.

   

   


RE: A One-Page Ledger Method for Generating Voynich-Like Text - dashstofsk - 19-05-2026

(18-05-2026, 01:19 PM)Dunsel Wrote: You are not allowed to view links. Register or Login to view.If this book is a hoax or copy/mutate, someone or some group went out of their way to make it look legitimate.

This is my hypothesis also. The writer wanted to make people believe that this was a rare piece from some distant land where they used a strange alphabet. In order to create the deception he had to give the manuscript a semblance of genuineness, give it some definite structure. Otherwise unstructured random writing would have been quickly dismissed as a fraud. The strange alphabet perpetuates the interest in a way that any local alphabet would not have done. The fact that the manuscript has existed to this day is proof that the writer succeeded.

Today with the assistance of programmable computers we can analyse the text and see something of the way it was done. Humans are not good at mimicking randomness. Psychological tricks have a habit of leading us to make repeats and to reuse text. And we can see this in the writing.

We can only guess how the writer achieved it. Perhaps other people at that time tried to create something similar and failed. And perhaps the writer of the VMS noted those failures and strove to avoid the same mistakes.

For me the actual method is not really important. It is enough to show evidence that the manuscript is artificial, constructed and meaningless.


RE: A One-Page Ledger Method for Generating Voynich-Like Text - Torsten - 19-05-2026

(19-05-2026, 02:07 AM)Dunsel Wrote: You are not allowed to view links. Register or Login to view.I'm not convinced the ho/ed bigram evidence supports a continuous drift model. If ed/Currier B/Scribe 2+ emerged gradually through incremental copy-mutate, I would expect broad transitional zones and smooth redistribution of ed behavior across folios. Instead, the ed distribution appears highly clustered, with long stable low-ed regions written by Scribe 1 followed by abrupt activation zones written by Scribe 2+.  That aligns much more closely with production/scribal boundaries than with lexical drift.

The attached charts are difficult to reconcile with a purely continuous evolution model. ho/Scribe 1/Currier A folios remain remarkably stable and locally reducible, while ED+/Scribe 2 behavior expands abruptly rather than progressively. That looks less like slow drift and more like a regime change in production methods or weighting strategy.

The "ed" bigram frequency is actually a projection of the word-level <chol> to <chedy> evolution onto the character level. <chedy> contains "ed". <shedy> contains "ed". The "ed" frequency per section is the <chedy>-family frequency - just measured at a coarser granularity.

The intermediate forms document the transition step by step: <chol> → <cheol> → <cheo> → <chey> → <chedy>. Each step is a minimal modification of the previous form. The intermediate forms are attested in the text with specific frequencies that trace the gradient across sections (see You are not allowed to view links. Register or Login to view.).

Whether this looks abrupt or gradual depends on whether you view it in the current binding order or in the writing order. In the current binding order, Herbal A and Herbal B bifolia are interleaved within the same quires — early-production and late-production pages sit next to each other. That creates the "abrupt activation zones" you see in your charts. In the reconstructed writing order (Herbal A → Pharma A → Cosmo → Herbal B → Stars (Quire 20) → Biological (Quire 13)), the same data forms a smooth gradient with no abrupt transitions. The first step from <chol> to <cheol> even happens within Currier A. Words like <cheol> are more frequent in the Pharma section than in the Herbal A section.

Your own You are not allowed to view links. Register or Login to view. experiment actually demonstrates this. You showed that starting from one page and expanding incrementally produces viable Voynich-like text — with the vocabulary evolving as the scribe writes. That's continuous evolution from a seed. The <ed> gradient across the manuscript is the same process scaled up. The "abrupt" boundaries disappear when you reorder folios by vocabulary similarity rather than by folio number.


RE: A One-Page Ledger Method for Generating Voynich-Like Text - nablator - 19-05-2026

(19-05-2026, 02:07 AM)Dunsel Wrote: You are not allowed to view links. Register or Login to view.I'm not convinced the ho/ed bigram evidence supports a continuous drift model. If ed/Currier B/Scribe 2+ emerged gradually through incremental copy-mutate, I would expect broad transitional zones and smooth redistribution of ed behavior across folios. Instead, the ed distribution appears highly clustered, with long stable low-ed regions written by Scribe 1 followed by abrupt activation zones written by Scribe 2+.  That aligns much more closely with production/scribal boundaries than with lexical drift.

You are not allowed to view links. Register or Login to view. explains it.


RE: A One-Page Ledger Method for Generating Voynich-Like Text - tavie - 19-05-2026

(18-05-2026, 11:03 AM)dashstofsk Wrote: You are not allowed to view links. Register or Login to view.However the flow of the writing suggests that the writer did not pause after each word to think of what ought to come next. So I am still inclined to believe that the method is more simple, and doesn't involve looking back at previous words.

How do we know this? I feel I've read or heard something about the fluency with which glyphs within each word were written (probably Lisa) but I've not heard about it from word to word. What would we expect to see/not see if there were pauses?


RE: A One-Page Ledger Method for Generating Voynich-Like Text - Dunsel - 19-05-2026

(19-05-2026, 09:50 AM)Torsten Wrote: You are not allowed to view links. Register or Login to view.Your own You are not allowed to view links. Register or Login to view. experiment actually demonstrates this. You showed that starting from one page and expanding incrementally produces viable Voynich-like text — with the vocabulary evolving as the scribe writes. That's continuous evolution from a seed. The <ed> gradient across the manuscript is the same process scaled up. The "abrupt" boundaries disappear when you reorder folios by vocabulary similarity rather than by folio number.

I'm going to have to rethink this.  I ran some new tests with my analyzer and the latter sections are still showing the same basic copy/mutate with source sheets.  It's not quite as neat and clean as herbal pages, but, the mechanism is still there.

q=quire
s=sheet
+=number of words found

Note, many of the RESIDUE pages have words that can be resolved as having come from the CORE or SECONDAY sheet through ED1 or ED2.  Unresolved are words that may or may not have a parent word elsewhere but fall outside the sheet classification.

Note:  Core sheets are classified as having parents for 10 words or more.  Secondary sheets 4-9 parents and residuals <=3.  So, You are not allowed to view links. Register or Login to view. is showing no core or secondary sheet as it only has 3 words. But, those 3 words all resolve to a single sheet which is why it's only showing a residual.

Herbal Pages
FolioCORESECONDARYRESIDUEUnresolved
f1rnonenonenone0
f1vq1s1 +24nonenone0
f2rq1s1 +23nonenone0
f2vq1s1 +15q1s2 +4none0
f3rq1s1 +24q1s2 +5none0
f3vq1s1 +26noneq1s2 +3, q1s3 +10
f4rq1s2 +17noneq1s1 +2, q1s3 +21
f4vq1s1 +19q1s3 +6q1s4 +31
f5rq1s1 +11q1s2 +5q1s3 +32
f5vq1s2 +13noneq1s1 +2, q1s3 +32
f6rq1s4 +17q1s3 +4q1s1 +1, q1s2 +11
f6vq1s1 +24q1s3 +6q1s4 +1, q1s2 +10
f7rq1s4 +20noneq1s3 +3, q1s1 +21
f7vq1s3 +22noneq1s2 +2, q1s1 +13
f8rq1s2 +29q1s1 +6q1s3 +2, q1s4 +10
f8vq1s1 +17noneq1s3 +3, q1s4 +3, q1s2 +33
f9rq1s1 +23noneq1s3 +3, q1s4 +2, q1s2 +12
f9vq1s3 +16noneq1s4 +3, q1s2 +20
f10rq1s4 +21q1s1 +4q1s3 +2, q1s2 +11
f10vq1s1 +13noneq1s2 +3, q2s1 +1, q2s2 +10
f11rq1s3 +14noneq1s1 +21
f11vq1s3 +15noneq1s2 +20
f13rq1s2 +16q2s1 +5q1s1 +10
f13vnoneq2s2 +9q1s1 +30
f14rq1s3 +18noneq1s4 +3, q2s2 +3, q1s1 +2, q1s2 +10
f14vq1s3 +13q2s1 +5q2s3 +3, q1s2 +30
f15rq1s1 +16noneq2s3 +3, q2s1 +2, q1s4 +22
f15vq1s2 +12noneq2s2 +2, q2s1 +31
f16rq1s3 +18q1s1 +5q1s4 +1, q2s2 +2, q2s3 +10
f16vq2s2 +15noneq1s3 +2, q1s1 +2, q2s1 +10
f17rq1s1 +22q3s1 +5none0
f17vq2s1 +17noneq1s4 +2, q2s2 +21
f18rq1s1 +15q2s1 +5q2s2 +20
f18vq1s1 +16q1s3 +5q2s1 +30
f19rq1s2 +18noneq2s2 +2, q3s1 +2, q1s1 +11
f19vq1s3 +19q2s1 +6q1s1 +20
f20rq1s1 +33, q1s3 +11q2s2 +7none0
f20vq1s3 +26q2s1 +5q1s1 +20
f21rq1s3 +19q2s1 +5q1s1 +30
f21vq1s3 +20q3s2 +7q1s2 +30
f22rq1s1 +21q3s1 +6q2s1 +30
f22vq1s3 +22noneq2s1 +3, q3s2 +31
f23rq1s3 +24q2s1 +5q3s2 +31
f23vq1s3 +20q2s1 +6q3s1 +30
f24rq1s3 +21noneq1s1 +3, q3s1 +2, q2s1 +11
f24vq1s3 +16q3s2 +5q2s1 +20
f25rq1s1 +22q2s1 +7q1s3 +21
f25vq1s3 +17q3s2 +7q1s1 +20
f26rq1s2 +25q1s1 +5q3s1 +30
f26vq1s2 +20q2s1 +6q3s1 +20
f27rq1s1 +25q2s1 +7q3s1 +31
f27vq1s3 +21q3s1 +5q2s1 +30
f28rq1s1 +23q2s1 +7q3s2 +30
f28vq1s3 +19q2s1 +6q3s2 +30
f29rq1s3 +22q2s1 +6q3s2 +30
f29vq1s3 +21q2s1 +6q3s1 +20
f30rq1s1 +22q3s1 +6q2s1 +30
f30vq1s3 +18q3s2 +6q2s1 +30
f31rq4s2 +26q1s3 +6q2s1 +30
f31vq4s2 +21q3s2 +5q1s3 +30
f32rq4s2 +20q1s3 +5q3s2 +30
f32vq4s2 +23noneq1s3 +3, q3s1 +22
f33rq4s2 +20q1s3 +7q3s2 +20
f33vq4s2 +21q1s3 +7q3s2 +30
f34rq4s2 +20q1s3 +6q3s2 +20
f34vq4s2 +24q1s3 +5q3s2 +30
f35rq4s2 +23q1s3 +6q3s1 +30
f35vq4s2 +19q1s3 +6q3s1 +20
f36rq4s2 +23q1s3 +5q3s2 +30
f36vq4s2 +24q1s3 +6q3s2 +30
f37rq4s2 +19q1s3 +7q3s2 +20
f37vq4s2 +22q1s3 +5q3s2 +30
f38rq4s2 +20q1s3 +5q3s1 +30
f38vq4s2 +21q1s3 +6q3s2 +30
f39rq5s2 +25q1s3 +6q4s2 +21
f39vq5s1 +22q4s2 +7q1s3 +31
f40rq5s1 +20q4s2 +6q1s3 +32
f40vq5s1 +22q4s2 +7q1s3 +30
f41rq5s1 +23q4s2 +7q1s3 +30
f41vq5s1 +20q4s2 +6q1s3 +30
f42rq5s1 +21q4s2 +6q1s3 +30
f42vq5s1 +23q4s2 +7q1s3 +31
f43rq6s3 +23q4s2 +6q1s3 +30
f43vq6s3 +24q4s2 +7q1s3 +30
f44rq6s3 +22q4s2 +7q1s3 +30
f44vq6s3 +24q4s2 +6q1s3 +30
f45rq6s3 +23q4s2 +7q1s3 +30
f45vq6s3 +22q4s2 +6q1s3 +30
f46rq6s3 +24q4s2 +7q1s3 +30
f46vq6s3 +23q4s2 +6q1s3 +30
f47rq6s3 +23q4s2 +7q1s3 +30
f47vq6s3 +22q4s2 +6q1s3 +30
f48rq6s3 +24q4s2 +7q1s3 +30
f48vq6s3 +23q4s2 +6q1s3 +30
f49rq7s1 +22q6s3 +6q4s2 +30
f49vq7s1 +21q6s3 +7q4s2 +30
f50rq7s1 +23q6s3 +6q4s2 +30
f50vq7s1 +21q6s3 +7q4s2 +30
f51rq7s1 +22q6s3 +6q4s2 +30
f51vq7s1 +21q6s3 +7q4s2 +30
f52rq7s1 +23q6s3 +6q4s2 +30
f52vq7s1 +21q6s3 +7q4s2 +30
f53rq7s3 +25q6s3 +6q4s2 +30
f53vq7s3 +22q6s3 +7q4s2 +30
f54rq7s3 +23q6s3 +6q4s2 +30
f54vq7s3 +22q6s3 +7q4s2 +30
f55rq7s3 +23q6s3 +6q4s2 +30
f55vq7s3 +22q6s3 +7q4s2 +30
f56rq1s3 +16noneq6s2 +2, q4s3 +2, q6s1 +23
f56vq7s1 +13noneq1s2 +3, q5s4 +2, q4s2 +30
f57rq7s3 +15q4s2 +6, q6s1 +4none0
f57vq5s1 +16q5s2 +7q4s2 +30
f58rq6s3 +29, q1s3 +15, q7s3 +10nonenone0
f58vq8s2 +25, q7s3 +10q4s2 +7none0
f65rnonenoneq8s2 +33
f65vq5s1 +16q5s2 +4q8s2 +1, q4s3 +10
f66rq8s2 +36, q6s3 +11q1s1 +9none0
f66vq8s2 +26q6s3 +7, q7s4 +4none0

Post Herbal Pages
FolioCORESECONDARYRESIDUEUnresolved
f67r1q8s1 +32q8s2 +9, q6s2 +7none0
f67r2q8s2 +33q8s1 +9, q1s1 +4none0
f67v1q6s3 +23q8s1 +6q4s2 +20
f67v2q8s2 +19q1s1 +6q1s3 +20
f68r1q9s1 +21q7s4 +6q8s2 +20
f68r2q8s2 +19q9s1 +7, q7s1 +6none0
f68r3q8s1 +21q8s2 +7q7s1 +30
f68v1q8s2 +17q9s1 +6q8s1 +2, q1s1 +1, q4s3 +1, q1s3 +11
f68v2q9s1 +28q6s1 +6q8s1 +30
f68v3q9s1 +32q8s2 +7, q6s3 +4none0
f69rq9s1 +26q8s2 +6q6s3 +20
f69vq9s1 +27q4s2 +4q8s2 +20
f70r1q9s1 +30noneq8s1 +3, q4s2 +2, q7s3 +1, q6s4 +10
f70r2q9s1 +32q8s2 +4, q1s2 +4none0
f70v1q9s1 +27q8s2 +5q8s1 +30
f70v2q9s1 +26q8s1 +7, q8s2 +5none0
f71rq10s1 +23q5s2 +6q9s1 +30
f71vq10s1 +27q9s1 +4q5s1 +3, q6s3 +3, q2s1 +1, q11s1 +10
f72r1q10s1 +26q8s2 +4q1s2 +30
f72r2q9s1 +25q8s2 +7q10s1 +30
f72r3q9s1 +25, q8s2 +10q3s1 +5none0
f72v1q9s1 +26q11s1 +9q10s1 +3, q8s2 +2, q6s1 +1, q5s2 +10
f72v2q9s1 +29q10s1 +6, q11s1 +5none0
f72v3q10s1 +29q8s2 +6q11s1 +30
f73rq9s1 +22q11s1 +5q10s1 +3, q6s3 +3, q8s2 +2, q5s1 +20
f73vq11s1 +29q8s2 +5q8s1 +30
f75rq9s1 +23q6s3 +9, q8s2 +4none0
f75vq5s2 +16q9s1 +7q8s2 +30
f76rq9s1 +21q6s3 +8, q13s1 +4none0
f76vq8s1 +21q9s1 +8, q8s2 +5none0
f77rq13s2 +28q13s1 +5q5s2 +30
f77vq13s2 +22q9s1 +8, q13s1 +4none0
f78rq13s2 +18q9s1 +4, q5s4 +5q8s1 +3, q10s1 +1, q4s3 +20
f78vq9s1 +19q13s1 +9q8s2 +1, q13s3 +2, q4s2 +2, q3s1 +10
f79rq13s2 +26q10s1 +8, q13s1 +4none0
f79vq13s2 +29q5s1 +9q11s1 +30
f80rq13s2 +21q9s1 +9q13s3 +30
f80vq13s5 +24noneq5s2 +1, q9s1 +3, q6s1 +2, q10s1 +2, q11s1 +20
f81rq13s5 +24q13s4 +4q3s1 +2, q11s1 +10
f81vq13s2 +24q8s2 +5q6s2 +20
f82rq13s5 +35q9s1 +5q8s1 +30
f82vq13s5 +29q13s2 +5q13s4 +1, q8s1 +2, q11s1 +10
f83rq13s3 +35q13s4 +5q8s2 +30
f83vq13s2 +32q13s5 +7q8s1 +30
f84rq13s2 +24q13s5 +5, q9s1 +5none0
f84vq13s1 +27noneq13s5 +1, q13s3 +1, q7s2 +1, q4s2 +2, q2s2 +20
f85r1q13s2 +33, q11s1 +15q9s1 +7none0
f85r2q13s5 +22q11s1 +5q13s4 +30
f86v3q9s1 +29, q8s2 +10q14s1 +6none0
f86v4q14s1 +34, q11s1 +11q6s3 +7none0
f86v5q14s1 +39q9s1 +7, q13s2 +4none0
f86v6q14s1 +33, q8s2 +13q11s1 +6none0
f87rq9s1 +24q14s1 +4, q10s1 +4q7s4 +1, q5s2 +1, q3s3 +10
f87vq14s1 +25q9s1 +6q1s3 +30
f88rq14s1 +23q10s1 +6q13s5 +30
f88vq14s1 +33q11s1 +8, q9s1 +4none0
f89r1q14s1 +27q13s3 +5q8s2 +30
f89r2q9s1 +29, q14s1 +11q3s4 +4none0
f89v1q14s1 +24q15s2 +5q13s5 +20
f89v2q9s1 +26q14s1 +5q3s1 +30
f90r1q15s2 +20noneq14s1 +3, q7s1 +20
f90r2q9s1 +12noneq8s1 +3, q13s3 +2, q8s2 +2, q7s3 +10
f90v1q9s1 +25q15s2 +7q14s1 +2, q13s2 +1, q15s1 +1, q4s2 +10
f90v2q14s1 +18q11s1 +6q1s1 +2, q4s2 +2, q3s2 +10
f93rq14s1 +19q9s1 +7q1s1 +30
f93vq14s1 +20q15s2 +6q1s3 +2, q8s1 +3, q3s1 +1, q1s1 +20
f94rq13s2 +16q11s1 +4q13s3 +2, q5s3 +20
f94vq14s1 +19q13s4 +4q8s1 +30
f95r1q13s2 +20q5s1 +6q11s1 +2, q1s1 +2, q7s3 +20
f95r2q5s2 +14noneq6s3 +1, q8s2 +3, q13s2 +1, q7s4 +2, q1s1 +10
f95v1q14s1 +23q6s3 +5q6s4 +20
f95v2q14s1 +16noneq13s1 +1, q4s3 +10
f96rq15s1 +19noneq15s2 +3, q14s1 +3, q17s2 +3, q4s4 +2, q17s1 +10
f96vq9s1 +25noneq8s1 +3, q13s2 +3, q13s3 +30
f99rq14s1 +30q11s1 +7, q15s2 +5none0
f99vq9s1 +30q15s2 +8, q11s1 +6none0
f100rq9s1 +21q14s1 +6, q8s1 +4none0
f100vq9s1 +21q11s1 +7, q17s1 +4none0
f101rq14s1 +28q15s2 +5q9s1 +30
f101vq9s1 +29q15s2 +8, q15s1 +4none0
f102r1q15s2 +29, q14s1 +10q11s1 +4none0
f102r2q19s2 +19q9s1 +7q7s3 +30
f102v1q9s1 +23q14s1 +5q19s1 +2, q10s1 +1, q2s2 +20
f102v2q9s1 +22q14s1 +7, q19s1 +4none0
f103rq14s1 +42, q8s2 +10q13s3 +6none0
f103vq14s1 +32q13s5 +7, q8s2 +5none0
f104rq14s1 +47, q11s1 +15q13s2 +5none0
f104vq14s1 +42, q13s2 +13q9s1 +8none0
f105rq14s1 +44, q19s1 +11q20s2 +6none0
f105vq14s1 +48, q20s2 +12q20s3 +8none0
f106rq14s1 +46, q20s2 +14q20s1 +4none0
f106vq14s1 +34, q20s3 +10q11s1 +4none0
f107rq20s2 +34, q11s1 +15q14s1 +6none0
f107vq9s1 +26, q13s2 +12q20s5 +6none0
f108rq20s2 +36, q8s2 +11q14s1 +6none0
f108vq20s2 +33, q14s1 +13q13s2 +6none0
f111rq20s6 +38q20s5 +9, q11s1 +7none0
f111vq20s6 +35, q13s5 +10q20s1 +4none0
f112rq14s1 +33q13s3 +8, q20s6 +5none0
f112vq20s6 +31, q14s1 +10q11s1 +5none0
f113rq14s1 +45, q20s2 +13q20s3 +6none0
f113vq20s6 +50, q20s4 +12q11s1 +5none0
f114rq20s5 +41, q20s2 +11q8s1 +8none0
f114vq14s1 +44, q20s3 +12q20s6 +6none0
f115rq20s4 +39q20s3 +9, q20s2 +5none0
f115vq20s4 +48, q20s3 +12q13s2 +6none0



RE: A One-Page Ledger Method for Generating Voynich-Like Text - Dunsel - 19-05-2026

(19-05-2026, 09:58 AM)nablator Wrote: You are not allowed to view links. Register or Login to view.You are not allowed to view links. Register or Login to view. explains it.

Fascinating.  I may have to devise a test for this!