+- 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: Transliteration-related information (/thread-3933.html)
RE: Transliteration-related information - ReneZ - 23-05-2025
Files moving, entire web sites moving or disappearing, is unfortunately one of the realities of the web.
In the particular case addressed above, the move was deliberate as the file in question was no longer the 'state of the art'. Internal links have been updated and in fact I sent a notification message here.
RE: Transliteration-related information - davidd - 23-05-2025
(23-05-2025, 01:10 AM)ReneZ Wrote: You are not allowed to view links. Register or Login to view.Files moving, entire web sites moving or disappearing, is unfortunately one of the realities of the web.Voynich.nu is the most comprehensive treasure trove of information about the VMS. It is a central pinning point of the community.
In the particular case addressed above, the move was deliberate as the file in question was no longer the 'state of the art'. Internal links have been updated and in fact I sent a notification message here.
RE: Transliteration-related information - davidd - 04-06-2025
I was looking at ZL3b-n.txt today, I get these errors about character encoding conversion error and it seems to start on f116r
RE: Transliteration-related information - ReneZ - 05-06-2025
Thanks!
You are right - the file seems to have gotten corrupted during a transfer.
It is fixed now. The other files that were updated at the same time were not affected.
RE: Transliteration-related information - ReneZ - 26-06-2025
The following is just for completeness and not likely to affect many users.
The issue of the 'invalid' label (locus) on f89v2 (shine through from the other side) has now also been addressed in transliteration files from other authors, specifically the ones with codes GC, IT and VT.
In these files, the locus in question has been marked using a dedicated code in a largely unused field of the IVTFF format, namely the 'locator' as defined in the format definition You are not allowed to view links. Register or Login to view., (see table 8). This also implies a trivial change to the format definition, reflected in the aforementioned table 8.
The version numbers of the files were not increased - the files were simply modified, because the contents are unchanged.
A new version (2.2) of ivtt has been created You are not allowed to view links. Register or Login to view., with the only difference that it will never write any locus with such a code to the output file. The old version will work just fine, but will not recognise the 'invalid' field.