28-10-2020, 01:57 PM
The problem of 'high Ascii'.
For all transliterations, see here:
You are not allowed to view links. Register or Login to view.
Both the GC and ZL transliterations include characters whose representations are in the 'high Ascii' area (Ascii code between 128 and 255).
From a present-day point of view, this is an old-fashioned way of doing things, but there is no Unicode area for Voynich characters yet, and at least it results in having a single byte per character.
Since these high-Ascii codes cannot be visualised in a standard way, and can cause issues with tools expecting Unicode, there is an IVTFF convention to represent them as @nnn; for Ascii code nnn. That makes the file standard Ascii, but more difficult to process by quickly-patched-together tools.
Both in Eva and in v101, all these characters are rare. They don't appear in the Takahashi transliteration, and the are very rare in the ZL transliteration. In v101 they are numerous, but still well under 1% of the text (quick guess).
ivtt has an option to easily swap between the 1-byte high-Ascii representation and the extended @nnn; representation:
-a1 goes from single-byte high-Ascii to @nnn;
-a2 goes from @nnn; to single-byte high-Ascii
For all transliterations, see here:
You are not allowed to view links. Register or Login to view.
Both the GC and ZL transliterations include characters whose representations are in the 'high Ascii' area (Ascii code between 128 and 255).
From a present-day point of view, this is an old-fashioned way of doing things, but there is no Unicode area for Voynich characters yet, and at least it results in having a single byte per character.
Since these high-Ascii codes cannot be visualised in a standard way, and can cause issues with tools expecting Unicode, there is an IVTFF convention to represent them as @nnn; for Ascii code nnn. That makes the file standard Ascii, but more difficult to process by quickly-patched-together tools.
Both in Eva and in v101, all these characters are rare. They don't appear in the Takahashi transliteration, and the are very rare in the ZL transliteration. In v101 they are numerous, but still well under 1% of the text (quick guess).
ivtt has an option to easily swap between the 1-byte high-Ascii representation and the extended @nnn; representation:
-a1 goes from single-byte high-Ascii to @nnn;
-a2 goes from @nnn; to single-byte high-Ascii