AIIN und Reva
Oh, there was one more point I’d completely forgotten—why Reva makes more sense than Eva.
Anyone who’s worked on deciphering knows the problem with “aiin”— aiin ist mostyl at the end of a token. Now, when I write, I need to know in advance what “aiin” is - ain aiin etc. whether I should treat “aiin” as a single atom, or as “ai in,” or as “a iin in,” and so on. I need to know right at the beginning of the token what kind of “aiin” I’m using.
Since “aiin” occurs so frequently, it’s often treated simply as a fixed unit; sometimes this also applies to “daiin.”
As a result, there have been countless attempts to classify “aiin” and “daiin” as words.
It’s much easier when read backward.
Here, the frequency is “niia,” and it usually appears at the beginning of a token.
Now I don't need to know anything else about the Aiin while I'm writing. It’s enough to view “N” as one of the four main entry points for the families (token) (y, n, r, l), and then whatever follows can follow:
na
nia
niia
niiia
And then other glyphs, such as “d.”
So niiad. Structurally, it’s all very clean and built upon one another.
And even the rarer forms (whose spelling is uncertain)—oin and oiin—cease to be a problem.
N remains the starting point,
then comes
no
nio
niio
and then other glyphs follow.
It is only a decision a / o...
That’s the fascinating thing about reading backward: Many of the complicated clusters and tokens dissolve into a very simple, sequentially structured system.
Oh, there was one more point I’d completely forgotten—why Reva makes more sense than Eva.
Anyone who’s worked on deciphering knows the problem with “aiin”— aiin ist mostyl at the end of a token. Now, when I write, I need to know in advance what “aiin” is - ain aiin etc. whether I should treat “aiin” as a single atom, or as “ai in,” or as “a iin in,” and so on. I need to know right at the beginning of the token what kind of “aiin” I’m using.
Since “aiin” occurs so frequently, it’s often treated simply as a fixed unit; sometimes this also applies to “daiin.”
As a result, there have been countless attempts to classify “aiin” and “daiin” as words.
It’s much easier when read backward.
Here, the frequency is “niia,” and it usually appears at the beginning of a token.
Now I don't need to know anything else about the Aiin while I'm writing. It’s enough to view “N” as one of the four main entry points for the families (token) (y, n, r, l), and then whatever follows can follow:
na
nia
niia
niiia
And then other glyphs, such as “d.”
So niiad. Structurally, it’s all very clean and built upon one another.
And even the rarer forms (whose spelling is uncertain)—oin and oiin—cease to be a problem.
N remains the starting point,
then comes
no
nio
niio
and then other glyphs follow.
It is only a decision a / o...
That’s the fascinating thing about reading backward: Many of the complicated clusters and tokens dissolve into a very simple, sequentially structured system.