20-04-2025, 01:06 AM
This system was inspired by the Curve-Line System (CLS). Brain Cham's full work is here - You are not allowed to view links. Register or Login to view..
A key component of CLS is that EVA: "a" is used to transition Voynich text from curves to lines. I thought of it as a switch from curves to lines.
I believe there are more "switches" and that their function can be defined.
Firstly I map glyphs to one of 3 groups dependant on if they are constructed from backslash \, line | or curve c.
If a glyph is a modified version of this shape I call the modification an addition of a curve.
I find it helpful to think of these assignments as blocks, or jigsaw pieces. Some fit, some do not.
(As adding a curve to a curve results in the same shape, I do not modify them further)
Backslash. Backslash-Curve. Curve. Line-Curve.
![[Image: blocks.jpg]](https://i.postimg.cc/gJk6RG0K/blocks.jpg)
# Curve
"e": "c", "g": "c", "b": "c", "s": "c", "h": "c",
# Backslash
"i": "\\",
# Backslash-Curve
"n": "X", "r": "X", "j": "X", "m": "X", "l": "X",
# Line-Curve
"t": "K", "k": "K", "p": "K", "f": "K", "d": "K", "q": "K",
The outlier in the mapping is "d", it belongs in "Line-Curve" due to its functionality in the text but is not constructed from line |.
Double \ is used due to backslash being a functional unit for the software, the eventual processing will consider it a single unit.
I also had to compromise with | and call it "l" due to similar restrictions which you will see below.
"switch"
If you prefer to think of this as a "transition" or "modifier" that is fine, it does not matter.
The core principle is that my "switch" will change what was on the left to a new thing on the right.
# Switch
"o": ">",
# Switch-Backslash
"a": ">\\",
# Switch-Line
"y": ">l", "c": ">l",
In the below image we have a hole in our jigsaw. Filling it is where "switches" come in. From the shape of the hole left, you may be able to guess which switch we need.
"a" ends with the backslash shape, so that would be a perfect fit. "o" would also work as it has no defined end shape. "y" and "c" would not work as they end in a line.
![[Image: blocks-2.jpg]](https://i.postimg.cc/90ShbYYf/blocks-2.jpg)
In order to make the code understand how this works "non-conformances" are defined so that miss-matched building blocks are flagged.
Pairs of letters which do not fit together are defined as so.
# Pairings
r"c\\", r"cX", r"cl", r"cK",
r"K\\", r"KX", r"Kl", r"KK",
r"X\\", r"XX", r"Xl", r"XK",
r"\\K", r"\\l", r"\\c",
r"l\\", r"lX", r"lc",
Glyph sequences where a "switch" was used transition from a shape to the same shape are also flagged as non-conforming. We did not transition/switch.
# Sequences
r"c>c", r"c>>c", r"c>>>c", r"c>>>>c",
r"K>c", r"K>>c", r"K>>>c", r"K>>>>c",
r"X>c", r"X>>c", r"X>>>c", r"X>>>>c",
r"\\>\\", r"\\>>\\", r"\\>>>\\", r"\\>>>>\\",
r"\\>X", r"\\>>X", r"\\>>>X", r"\\>>>>X",
r"l>l", r"l>>l", r"l>>>l", r"l>>>>l",
r"l>K", r"l>>K", r"l>>>K", r"l>>>>K",
r">>>>>",
}
The pairs and sequences list complete our "non-conformances".
Some glyphs/pairs require additional mapping.
"ch" and "sh" have been mapped as "c" plus a curve. As so they are "c" which is ">l" plus a curve, all together, so the result is ">K".
"ih" and "ish" have been mapped as "i" (backslash) plus a curve. Which is Backslash-Curve "X"
"e"+ Line-Curve are allowed in a separate process so that outside of this pairing "e" functions normally. It is an interesting combination, and previously I have said that I think it might be some sort of "half-benched" gallows, as I group "d" in with gallows that explains all the "ed" in Currier B. As the text does it, I incorporate it as part of its system, I'm not trying to "win", if score padding was the aim I could use much better tricks.. which leads me to EVA: "l".
"ld" is allowed as a pairing. This was a compromise. Other work I have seen has described "l" as the "joker" or "wildcard", the glyph that can be any shape. I found that for my work allowing just "ld" was good enough. Allowing "l" to "be anything" does bump scores up, but I feel like for the most part it is fairly rigid and performs a normal Backslash-Curve function.
For testing I used "ZL - The "Zandbergen" part of the LZ transliteration effort. v. 3a"
I decided on ambiguous mapping by eye and logged the results. In total I gained +3 conforming words from my choices which may have otherwise been non-conforming.
For the test I used the whole of Q1 excluding f1r. This is so that all of the text was Q1, Language A, Hand 1, Herbal.
In my work I have had 1 eye on Currier B ("ed" being an example) but this system will not work for it. This is aimed at Q1 currently, however I plan on tackling Currier B if this seems at all useful or of any worth to anyone.
I would just like to touch on two pairings which I feel may get brought up.
"yc" and "ys". In my opinion these common pairings are not part of normal Voynich language (amongst others). My system does not touch on "Line As a Functional Unit" phenomenon or such, but I do believe this is most likely at play in these cases. I think this is very clear.
The results of my test using the above rules is here.
![[Image: conf.jpg]](https://i.postimg.cc/JhQzhJK5/conf.jpg)
The full list of non-conforming words is here.
Finally.
I used AI. This was for writing code only, all mapping was done by myself with no input or analysis by AI. This is around 6 months of "work", mostly just thinking and reading others work, code just isn't a skill I have.
I also asked it to produce its interpretation (+ my system name) from my favourite drawing in the manuscript for something to post here.
![[Image: switch.jpg]](https://i.postimg.cc/y8qdcmg9/switch.jpg)
Thank you for reading, if you have any input I would love to hear it.
If you have written anything even roughly in line with my work, I have probably read it and stolen something. So, thank you! Also specifically to Rene for his transliteration and commenting on my other post where I was trying to put this together along with other ninja members who helped me greatly.
A key component of CLS is that EVA: "a" is used to transition Voynich text from curves to lines. I thought of it as a switch from curves to lines.
I believe there are more "switches" and that their function can be defined.
Firstly I map glyphs to one of 3 groups dependant on if they are constructed from backslash \, line | or curve c.
If a glyph is a modified version of this shape I call the modification an addition of a curve.
I find it helpful to think of these assignments as blocks, or jigsaw pieces. Some fit, some do not.
(As adding a curve to a curve results in the same shape, I do not modify them further)
Backslash. Backslash-Curve. Curve. Line-Curve.
![[Image: blocks.jpg]](https://i.postimg.cc/gJk6RG0K/blocks.jpg)
# Curve
"e": "c", "g": "c", "b": "c", "s": "c", "h": "c",
# Backslash
"i": "\\",
# Backslash-Curve
"n": "X", "r": "X", "j": "X", "m": "X", "l": "X",
# Line-Curve
"t": "K", "k": "K", "p": "K", "f": "K", "d": "K", "q": "K",
The outlier in the mapping is "d", it belongs in "Line-Curve" due to its functionality in the text but is not constructed from line |.
Double \ is used due to backslash being a functional unit for the software, the eventual processing will consider it a single unit.
I also had to compromise with | and call it "l" due to similar restrictions which you will see below.
"switch"
If you prefer to think of this as a "transition" or "modifier" that is fine, it does not matter.
The core principle is that my "switch" will change what was on the left to a new thing on the right.
# Switch
"o": ">",
# Switch-Backslash
"a": ">\\",
# Switch-Line
"y": ">l", "c": ">l",
In the below image we have a hole in our jigsaw. Filling it is where "switches" come in. From the shape of the hole left, you may be able to guess which switch we need.
"a" ends with the backslash shape, so that would be a perfect fit. "o" would also work as it has no defined end shape. "y" and "c" would not work as they end in a line.
![[Image: blocks-2.jpg]](https://i.postimg.cc/90ShbYYf/blocks-2.jpg)
In order to make the code understand how this works "non-conformances" are defined so that miss-matched building blocks are flagged.
Pairs of letters which do not fit together are defined as so.
# Pairings
r"c\\", r"cX", r"cl", r"cK",
r"K\\", r"KX", r"Kl", r"KK",
r"X\\", r"XX", r"Xl", r"XK",
r"\\K", r"\\l", r"\\c",
r"l\\", r"lX", r"lc",
Glyph sequences where a "switch" was used transition from a shape to the same shape are also flagged as non-conforming. We did not transition/switch.
# Sequences
r"c>c", r"c>>c", r"c>>>c", r"c>>>>c",
r"K>c", r"K>>c", r"K>>>c", r"K>>>>c",
r"X>c", r"X>>c", r"X>>>c", r"X>>>>c",
r"\\>\\", r"\\>>\\", r"\\>>>\\", r"\\>>>>\\",
r"\\>X", r"\\>>X", r"\\>>>X", r"\\>>>>X",
r"l>l", r"l>>l", r"l>>>l", r"l>>>>l",
r"l>K", r"l>>K", r"l>>>K", r"l>>>>K",
r">>>>>",
}
The pairs and sequences list complete our "non-conformances".
Some glyphs/pairs require additional mapping.
"ch" and "sh" have been mapped as "c" plus a curve. As so they are "c" which is ">l" plus a curve, all together, so the result is ">K".
"ih" and "ish" have been mapped as "i" (backslash) plus a curve. Which is Backslash-Curve "X"
"e"+ Line-Curve are allowed in a separate process so that outside of this pairing "e" functions normally. It is an interesting combination, and previously I have said that I think it might be some sort of "half-benched" gallows, as I group "d" in with gallows that explains all the "ed" in Currier B. As the text does it, I incorporate it as part of its system, I'm not trying to "win", if score padding was the aim I could use much better tricks.. which leads me to EVA: "l".
"ld" is allowed as a pairing. This was a compromise. Other work I have seen has described "l" as the "joker" or "wildcard", the glyph that can be any shape. I found that for my work allowing just "ld" was good enough. Allowing "l" to "be anything" does bump scores up, but I feel like for the most part it is fairly rigid and performs a normal Backslash-Curve function.
For testing I used "ZL - The "Zandbergen" part of the LZ transliteration effort. v. 3a"
I decided on ambiguous mapping by eye and logged the results. In total I gained +3 conforming words from my choices which may have otherwise been non-conforming.
For the test I used the whole of Q1 excluding f1r. This is so that all of the text was Q1, Language A, Hand 1, Herbal.
In my work I have had 1 eye on Currier B ("ed" being an example) but this system will not work for it. This is aimed at Q1 currently, however I plan on tackling Currier B if this seems at all useful or of any worth to anyone.
I would just like to touch on two pairings which I feel may get brought up.
"yc" and "ys". In my opinion these common pairings are not part of normal Voynich language (amongst others). My system does not touch on "Line As a Functional Unit" phenomenon or such, but I do believe this is most likely at play in these cases. I think this is very clear.
![[Image: ycs.jpg]](https://i.postimg.cc/nzRV4Jys/ycs.jpg)
The results of my test using the above rules is here.
![[Image: conf.jpg]](https://i.postimg.cc/JhQzhJK5/conf.jpg)
The full list of non-conforming words is here.
Converted Text with Non-Conformances Highlighted:
Line <f1v.1,@P0>:
Line <f1v.2,+P0>: lkody -> [XK]>K>l
Line <f1v.3,+P0>: dksheey -> [KK]>Kcc>l
Line <f1v.4,+P0>:
Line <f1v.5,+P0>:
Line <f1v.6,+P0>:
Line <f1v.7,+P0>: choees -> >[K>c]cc, lchiody -> X>[K\]>K>l
Line <f1v.8,+P0>:
Line <f1v.9,+P0>:
Line <f1v.10,+P0>: taor -> K>[\>X]
Line <f2r.1,@P0>:
Line <f2r.2,+P0>: chkar -> >[KK]>\X
Line <f2r.3,+P0>:
Line <f2r.4,+P0>: aiidy -> >\\[\K]>l, chtod -> >[KK]>K
Line <f2r.5,+P0>:
Line <f2r.6,+P0>: dkol -> [KK]>X
Line <f2r.7,+P0>:
Line <f2r.8,+P0>:
Line <f2r.9,+P0>: dls -> [KX]c, daiisol -> K>\\[\c]>X
Line <f2r.10,+P0>:
Line <f2r.11,+P0>: ychain -> >[l>K]>\\X
Line <f2r.12,+P0>:
Line <f2r.13,+P0>:
Line <f2v.1,@P0>: shty -> >[KK]>l
Line <f2v.2,+P0>: loeees -> [X>c]ccc
Line <f2v.3,+P0>:
Line <f2v.4,+P0>:
Line <f2v.5,+P0>:
Line <f2v.6,+P0>: chty -> >[KK]>l
Line <f2v.7,+P0>: chokeos -> >K>K[c>c], chr -> >[KX]
Line <f2v.8,+P0>:
Line <f3r.1,@P0>: tsheos -> K>K[c>c]
Line <f3r.2,+P0>: ycheor -> >[l>K]c>X
Line <f3r.3,+P0>:
Line <f3r.4,+P0>: chag -> >K>[\c]
Line <f3r.5,+P0>:
Line <f3r.6,+P0>: ychtaiin -> >[l>KK]>\\\X
Line <f3r.7,+P0>:
Line <f3r.8,+P0>: ysheor -> >[l>K]c>X, dago -> K>[\c]>
Line <f3r.9,+P0>:
Line <f3r.10,+P0>:
Line <f3r.11,+P0>:
Line <f3r.12,+P0>: okadaiin -> >K>[\K]>\\\X
Line <f3r.13,+P0>:
Line <f3r.14,+P0>:
Line <f3r.15,+P0>:
Line <f3r.16,+P0>:
Line <f3r.17,+P0>: soeom -> [c>c]>X
Line <f3r.18,+P0>:
Line <f3r.19,+P0>: qoeor -> [K>c]>X, qosaiin -> [K>c]>\\\X
Line <f3r.20,+P0>: ycheor -> >[l>K]c>X
Line <f3v.1,@P0>:
Line <f3v.2,+P0>: daiidy -> K>\\[\K]>l
Line <f3v.3,+P0>:
Line <f3v.4,+P0>: een -> c[cX]
Line <f3v.5,+P0>: ychear -> >[l>K]c>\X
Line <f3v.6,+P0>:
Line <f3v.7,+P0>:
Line <f3v.8,+P0>:
Line <f3v.9,+P0>:
Line <f3v.10,+P0>: ochos -> >>[K>c]
Line <f3v.11,+P0>:
Line <f3v.12,+P0>:
Line <f3v.13,+P0>: shkaiin -> >[KK]>\\\X, chky -> >[KK]>l
Line <f3v.14,+P0>:
Line <f4r.1,@P0>: chpady -> >[KK]>[\K]>l
Line <f4r.2,+P0>: shtchy -> >[KK]>K>l, as -> >[\c]
Line <f4r.3,+P0>:
Line <f4r.4,+P0>:
Line <f4r.5,+P0>:
Line <f4r.6,+P0>:
Line <f4r.7,+P0>:
Line <f4r.8,+P0>:
Line <f4r.9,+P0>:
Line <f4r.10,+P0>: shyshol -> >K>[l>K]>X
Line <f4r.11,+P0>:
Line <f4r.12,+P0>:
Line <f4r.13,+P0>:
Line <f4v.1,@P0>: dlod -> [KX]>K
Line <f4v.2,+P0>: shkchor -> >[KK]>K>X
Line <f4v.3,+P0>:
Line <f4v.4,+P0>:
Line <f4v.5,+P0>:
Line <f4v.6,+P0>:
Line <f4v.7,+P0>:
Line <f4v.8,+P0>:
Line <f4v.9,+P0>: cheog -> >K[c>c]
Line <f4v.10,+P0>:
Line <f4v.11,+P0>: shtaiin -> >[KK]>\\\X
Line <f4v.12,+P0>:
Line <f4v.13,+P0>:
Line <f4v.14,+P0>: chtody -> >[KK]>K>l
Line <f5r.1,@P0>: chkoy -> >[KK]>>l, dkshy -> [KK]>K>l
Line <f5r.2,+P0>:
Line <f5r.3,+P0>:
Line <f5r.4,+P0>:
Line <f5r.5,+P0>:
Line <f5r.6,+P0>: qoeeey -> [K>c]cc>l, qoeor -> [K>c]>X
Line <f5r.7,+P0>: qotoeey -> K>[K>c]c>l
Line <f5v.1,@P0>:
Line <f5v.2,+P0>: ychopordg -> >[l>K]>K>[XK]c
Line <f5v.3,+P0>:
Line <f5v.4,+P0>:
Line <f5v.5,+P0>:
Line <f5v.6,+P0>:
Line <f6r.1,@P0>:
Line <f6r.2,+P0>:
Line <f6r.3,+P0>: foeear -> [K>c]c>\X, cheoeees -> >K[c>c]ccc
Line <f6r.4,+P0>: choithy -> >K>[\K]c>l
Line <f6r.5,+P0>:
Line <f6r.6,+P0>:
Line <f6r.7,+P0>:
Line <f6r.8,+P0>: ychol -> >[l>K]>X
Line <f6r.9,+P0>: skaiiodar -> [cK]>\\\>K>\X
Line <f6r.10,+P0>:
Line <f6r.11,+P0>: ychar -> >[l>K]>\X
Line <f6r.12,+P0>:
Line <f6r.13,+P0>:
Line <f6r.14,+P0>: ysho -> >[l>K]>
Line <f6v.1,@P0>: chapchy -> >K>[\K]>K>l
Line <f6v.2,+P0>:
Line <f6v.3,+P0>: rychos -> X>[l>K>c]
Line <f6v.4,+P0>:
Line <f6v.5,+P0>:
Line <f6v.6,+P0>:
Line <f6v.7,+P0>: ychos -> >[l>K>c], ychol -> >[l>K]>X
Line <f6v.8,+P0>: ychor -> >[l>K]>X
Line <f6v.9,+P0>:
Line <f6v.10,+P0>: ychear -> >[l>K]c>\X, kchdy -> K>[KK]>l
Line <f6v.11,+P0>:
Line <f6v.12,+P0>:
Line <f6v.13,+P0>: yodaiin -> >[l>K]>\\\X
Line <f6v.14,+P0>:
Line <f6v.15,+P0>:
Line <f6v.16,+P0>:
Line <f6v.17,+P0>: chaies -> >K>\[\c]c
Line <f6v.18,+P0>: ithor -> [\K]c>X
Line <f6v.19,+P0>: kchos -> K>[K>c]
Line <f6v.20,+P0>:
Line <f6v.21,+P0>: ycheor -> >[l>K]c>X
Line <f7r.1,@P0>: qko -> [KK]>, qoos -> [K>>c]
Line <f7r.2,+P0>:
Line <f7r.3,+P0>:
Line <f7r.4,+P0>: ychey -> >[l>K]c>l, kchos -> K>[K>c]
Line <f7r.5,+P0>:
Line <f7r.6,+P0>: qotoees -> K>[K>c]cc, chkoldy -> >[KK]>>K>l
Line <f7r.7,+P0>:
Line <f7r.8,+P0>:
Line <f7r.9,+P0>:
Line <f7r.10,+P0>:
Line <f8r.1,@P0>:
Line <f8r.2,+P0>: tchty -> K>[KK]>l
Line <f8r.3,+P0>:
Line <f8r.4,+P0>:
Line <f8r.5,+P0>: chky -> >[KK]>l
Line <f8r.6,+P0>: koltoldy -> K>[XK]>>K>l
Line <f8r.7,+P0>:
Line <f8r.10,+P0>:
Line <f8r.11,+P0>: otariin -> >K>\[X\]\X
Line <f8r.12,+P0>:
Line <f8r.15,+P0>: kccs -> K>[l>lc], daiiirihy -> K>\\\\[XX]>l
Line <f8r.16,+P0>: ychey -> >[l>K]c>l
Line <f8r.17,+P0>: chl -> >[KX]
Line <f8r.18,+P0>: cl -> >[lX]
Line <f8r.19,+P0>:
Line <f8r.20,+P0>:
Line <f8v.1,@P0>:
Line <f8v.2,+P0>:
Line <f8v.3,+P0>: dolas -> K>X>[\c]
Line <f8v.4,+P0>:
Line <f8v.5,+P0>:
Line <f8v.6,+P0>:
Line <f8v.7,+P0>:
Line <f8v.8,+P0>: okcholksh -> >K>K>[XK]>K
Line <f8v.9,+P0>: orchl -> >X>[KX]
Line <f8v.10,+P0>:
Line <f8v.11,+P0>:
Line <f8v.12,+P0>:
Line <f8v.13,+P0>: satar -> c>[\K]>\X
Line <f8v.14,+P0>:
Line <f8v.15,+P0>:
Line <f8v.16,+P0>:
Line <f8v.17,+P0>:
Line <f1v.1,@P0>:
Line <f1v.2,+P0>: lkody -> [XK]>K>l
Line <f1v.3,+P0>: dksheey -> [KK]>Kcc>l
Line <f1v.4,+P0>:
Line <f1v.5,+P0>:
Line <f1v.6,+P0>:
Line <f1v.7,+P0>: choees -> >[K>c]cc, lchiody -> X>[K\]>K>l
Line <f1v.8,+P0>:
Line <f1v.9,+P0>:
Line <f1v.10,+P0>: taor -> K>[\>X]
Line <f2r.1,@P0>:
Line <f2r.2,+P0>: chkar -> >[KK]>\X
Line <f2r.3,+P0>:
Line <f2r.4,+P0>: aiidy -> >\\[\K]>l, chtod -> >[KK]>K
Line <f2r.5,+P0>:
Line <f2r.6,+P0>: dkol -> [KK]>X
Line <f2r.7,+P0>:
Line <f2r.8,+P0>:
Line <f2r.9,+P0>: dls -> [KX]c, daiisol -> K>\\[\c]>X
Line <f2r.10,+P0>:
Line <f2r.11,+P0>: ychain -> >[l>K]>\\X
Line <f2r.12,+P0>:
Line <f2r.13,+P0>:
Line <f2v.1,@P0>: shty -> >[KK]>l
Line <f2v.2,+P0>: loeees -> [X>c]ccc
Line <f2v.3,+P0>:
Line <f2v.4,+P0>:
Line <f2v.5,+P0>:
Line <f2v.6,+P0>: chty -> >[KK]>l
Line <f2v.7,+P0>: chokeos -> >K>K[c>c], chr -> >[KX]
Line <f2v.8,+P0>:
Line <f3r.1,@P0>: tsheos -> K>K[c>c]
Line <f3r.2,+P0>: ycheor -> >[l>K]c>X
Line <f3r.3,+P0>:
Line <f3r.4,+P0>: chag -> >K>[\c]
Line <f3r.5,+P0>:
Line <f3r.6,+P0>: ychtaiin -> >[l>KK]>\\\X
Line <f3r.7,+P0>:
Line <f3r.8,+P0>: ysheor -> >[l>K]c>X, dago -> K>[\c]>
Line <f3r.9,+P0>:
Line <f3r.10,+P0>:
Line <f3r.11,+P0>:
Line <f3r.12,+P0>: okadaiin -> >K>[\K]>\\\X
Line <f3r.13,+P0>:
Line <f3r.14,+P0>:
Line <f3r.15,+P0>:
Line <f3r.16,+P0>:
Line <f3r.17,+P0>: soeom -> [c>c]>X
Line <f3r.18,+P0>:
Line <f3r.19,+P0>: qoeor -> [K>c]>X, qosaiin -> [K>c]>\\\X
Line <f3r.20,+P0>: ycheor -> >[l>K]c>X
Line <f3v.1,@P0>:
Line <f3v.2,+P0>: daiidy -> K>\\[\K]>l
Line <f3v.3,+P0>:
Line <f3v.4,+P0>: een -> c[cX]
Line <f3v.5,+P0>: ychear -> >[l>K]c>\X
Line <f3v.6,+P0>:
Line <f3v.7,+P0>:
Line <f3v.8,+P0>:
Line <f3v.9,+P0>:
Line <f3v.10,+P0>: ochos -> >>[K>c]
Line <f3v.11,+P0>:
Line <f3v.12,+P0>:
Line <f3v.13,+P0>: shkaiin -> >[KK]>\\\X, chky -> >[KK]>l
Line <f3v.14,+P0>:
Line <f4r.1,@P0>: chpady -> >[KK]>[\K]>l
Line <f4r.2,+P0>: shtchy -> >[KK]>K>l, as -> >[\c]
Line <f4r.3,+P0>:
Line <f4r.4,+P0>:
Line <f4r.5,+P0>:
Line <f4r.6,+P0>:
Line <f4r.7,+P0>:
Line <f4r.8,+P0>:
Line <f4r.9,+P0>:
Line <f4r.10,+P0>: shyshol -> >K>[l>K]>X
Line <f4r.11,+P0>:
Line <f4r.12,+P0>:
Line <f4r.13,+P0>:
Line <f4v.1,@P0>: dlod -> [KX]>K
Line <f4v.2,+P0>: shkchor -> >[KK]>K>X
Line <f4v.3,+P0>:
Line <f4v.4,+P0>:
Line <f4v.5,+P0>:
Line <f4v.6,+P0>:
Line <f4v.7,+P0>:
Line <f4v.8,+P0>:
Line <f4v.9,+P0>: cheog -> >K[c>c]
Line <f4v.10,+P0>:
Line <f4v.11,+P0>: shtaiin -> >[KK]>\\\X
Line <f4v.12,+P0>:
Line <f4v.13,+P0>:
Line <f4v.14,+P0>: chtody -> >[KK]>K>l
Line <f5r.1,@P0>: chkoy -> >[KK]>>l, dkshy -> [KK]>K>l
Line <f5r.2,+P0>:
Line <f5r.3,+P0>:
Line <f5r.4,+P0>:
Line <f5r.5,+P0>:
Line <f5r.6,+P0>: qoeeey -> [K>c]cc>l, qoeor -> [K>c]>X
Line <f5r.7,+P0>: qotoeey -> K>[K>c]c>l
Line <f5v.1,@P0>:
Line <f5v.2,+P0>: ychopordg -> >[l>K]>K>[XK]c
Line <f5v.3,+P0>:
Line <f5v.4,+P0>:
Line <f5v.5,+P0>:
Line <f5v.6,+P0>:
Line <f6r.1,@P0>:
Line <f6r.2,+P0>:
Line <f6r.3,+P0>: foeear -> [K>c]c>\X, cheoeees -> >K[c>c]ccc
Line <f6r.4,+P0>: choithy -> >K>[\K]c>l
Line <f6r.5,+P0>:
Line <f6r.6,+P0>:
Line <f6r.7,+P0>:
Line <f6r.8,+P0>: ychol -> >[l>K]>X
Line <f6r.9,+P0>: skaiiodar -> [cK]>\\\>K>\X
Line <f6r.10,+P0>:
Line <f6r.11,+P0>: ychar -> >[l>K]>\X
Line <f6r.12,+P0>:
Line <f6r.13,+P0>:
Line <f6r.14,+P0>: ysho -> >[l>K]>
Line <f6v.1,@P0>: chapchy -> >K>[\K]>K>l
Line <f6v.2,+P0>:
Line <f6v.3,+P0>: rychos -> X>[l>K>c]
Line <f6v.4,+P0>:
Line <f6v.5,+P0>:
Line <f6v.6,+P0>:
Line <f6v.7,+P0>: ychos -> >[l>K>c], ychol -> >[l>K]>X
Line <f6v.8,+P0>: ychor -> >[l>K]>X
Line <f6v.9,+P0>:
Line <f6v.10,+P0>: ychear -> >[l>K]c>\X, kchdy -> K>[KK]>l
Line <f6v.11,+P0>:
Line <f6v.12,+P0>:
Line <f6v.13,+P0>: yodaiin -> >[l>K]>\\\X
Line <f6v.14,+P0>:
Line <f6v.15,+P0>:
Line <f6v.16,+P0>:
Line <f6v.17,+P0>: chaies -> >K>\[\c]c
Line <f6v.18,+P0>: ithor -> [\K]c>X
Line <f6v.19,+P0>: kchos -> K>[K>c]
Line <f6v.20,+P0>:
Line <f6v.21,+P0>: ycheor -> >[l>K]c>X
Line <f7r.1,@P0>: qko -> [KK]>, qoos -> [K>>c]
Line <f7r.2,+P0>:
Line <f7r.3,+P0>:
Line <f7r.4,+P0>: ychey -> >[l>K]c>l, kchos -> K>[K>c]
Line <f7r.5,+P0>:
Line <f7r.6,+P0>: qotoees -> K>[K>c]cc, chkoldy -> >[KK]>>K>l
Line <f7r.7,+P0>:
Line <f7r.8,+P0>:
Line <f7r.9,+P0>:
Line <f7r.10,+P0>:
Line <f8r.1,@P0>:
Line <f8r.2,+P0>: tchty -> K>[KK]>l
Line <f8r.3,+P0>:
Line <f8r.4,+P0>:
Line <f8r.5,+P0>: chky -> >[KK]>l
Line <f8r.6,+P0>: koltoldy -> K>[XK]>>K>l
Line <f8r.7,+P0>:
Line <f8r.10,+P0>:
Line <f8r.11,+P0>: otariin -> >K>\[X\]\X
Line <f8r.12,+P0>:
Line <f8r.15,+P0>: kccs -> K>[l>lc], daiiirihy -> K>\\\\[XX]>l
Line <f8r.16,+P0>: ychey -> >[l>K]c>l
Line <f8r.17,+P0>: chl -> >[KX]
Line <f8r.18,+P0>: cl -> >[lX]
Line <f8r.19,+P0>:
Line <f8r.20,+P0>:
Line <f8v.1,@P0>:
Line <f8v.2,+P0>:
Line <f8v.3,+P0>: dolas -> K>X>[\c]
Line <f8v.4,+P0>:
Line <f8v.5,+P0>:
Line <f8v.6,+P0>:
Line <f8v.7,+P0>:
Line <f8v.8,+P0>: okcholksh -> >K>K>[XK]>K
Line <f8v.9,+P0>: orchl -> >X>[KX]
Line <f8v.10,+P0>:
Line <f8v.11,+P0>:
Line <f8v.12,+P0>:
Line <f8v.13,+P0>: satar -> c>[\K]>\X
Line <f8v.14,+P0>:
Line <f8v.15,+P0>:
Line <f8v.16,+P0>:
Line <f8v.17,+P0>:
Finally.
I used AI. This was for writing code only, all mapping was done by myself with no input or analysis by AI. This is around 6 months of "work", mostly just thinking and reading others work, code just isn't a skill I have.
I also asked it to produce its interpretation (+ my system name) from my favourite drawing in the manuscript for something to post here.
![[Image: switch.jpg]](https://i.postimg.cc/y8qdcmg9/switch.jpg)
Thank you for reading, if you have any input I would love to hear it.
If you have written anything even roughly in line with my work, I have probably read it and stolen something. So, thank you! Also specifically to Rene for his transliteration and commenting on my other post where I was trying to put this together along with other ninja members who helped me greatly.