# # This file is: http://www.voynich.nu/software/000_README.txt # Latest update: 20/03/2023 # The files in all of the (presently two) subdirectories are related to general-purpose software that is able to process transliteration files. The software is written in C, and all source code is included in a single file for each tool. At present there are two subdirectories: bitrans ivtt For general information see: http://www.voynich.nu/transcr.html For more specific information see: http://www.voynich.nu/extra/sp_transcr.html#software -------------------------------- Contents of subdirectory bitrans -------------------------------- bitrans.c --------- Source code of bitrans, that reads and processes plain text files, but also files in IVTFF format of any version. This is software version 1.4. (Version 1.2 had an important bug and cannot be used) It is a versatile tool to convert files from one transliteration alphabet into another. Files for the standard alphabets are provided with the tool. The user may define his own alphabets. The tool is also very well suited for general text substitutions and manipulations. It can be built with standard libraries as follows: cc -o bitrans bitrans.c Bitrans_manual.pdf ------------------ A user guide for bitrans. The document is version 1.4, and is valid for software version 1.4. Curr-Eva_def.bit ---------------- Bitrans table ('rules file') to convert from Currier to Basic Eva and back. The "def" suffix of the file name indicates that this is the exact defition file, and it contains only those Basic Eva codes that are defined by the Currier alphabet. Eva-Cuva.bit ------------ Bitrans table ('rules file') to convert from Basic Eva to the Cuva analysis alphabet. Note that this conversion is not reversible. EvaT.bit -------- Bitrans table ('rules file') to convert Takahashi-style Eva to standard Eva. (See also STA-EvaT_def.bit further below). FSG-Eva_def.bit --------------- Bitrans table ('rules file') to convert from FSG to Basic Eva and back. The "def" suffix of the file name indicates that this is the exact defition file, and it contains only those Basic Eva codes that are defined by the FSG alphabet. STA_L0-1.bit, STA_L0-2.bit -------------------------- Bitrans tables ('rules files') to convert from STA1 Level-0 to Level-1, or from Level-0 to Level-2 respectively. Note that this conversion is not reversible. This is only useful for STA files that were converted from Currier (up to Level-1) or v101 (up to Level-2). STA-Curr_def.bit ---------------- Bitrans table ('rules file') to convert from Currier to STA1 and back. The "def" suffix of the file name indicates that this is the exact definition file, and it contains only those STA codes that are defined by the Currier alphabet. It generates STA level 0 output, and conversion to STA level 1 is recommended. Note: Currier to STA is translation direction 2 (right to left). STA-Eva_Bint.bit ---------------- Bitrans table ('rules file') to convert (=approximate) from STA1 to Basic Eva. Note that this conversion is not reversible. It supports the full STA alphabet definition. STA-Eva_def.bit --------------- Bitrans table ('rules file') to convert from extended Eva to STA1 and back. The "def" suffix of the file name indicates that this is the exact defniition file, and it contains only those STA codes that are defined by the extended Eva alphabet (238 rules). The file can (of course) also be used for Basic Eva. Note: Eva to STA is translation direction 2 (right to left). STA-Eva_Eint.bit ---------------- Bitrans table ('rules file') to convert (=approximate) from STA1 to Extended Eva. Note that this conversion is not reversible. It supports the full STA alphabet definition. The approximation applies only to those STA codes that are defined for v101 but not for extended Eva. STA-EvaT_def.bit ----------------- Bitrans table ('rules file') to convert from the style of Eva used in the transliteration file of Takeshi Takahashi to STA1 and back. The "def" suffix of the file name indicates that this is the exact defition file, and it contains only those STA codes that are defined by the particular set of Eva alphabet. Note: Eva to STA is translation direction 2 (right to left). STA-FSG_def.bit --------------- Bitrans table ('rules file') to convert from FSG to STA1 and back. The "def" suffix of the file name indicates that this is the exact definition file, and it contains only those STA codes that are defined by the FSG alphabet. Note: FSG to STA is translation direction 2 (right to left). STA-v101_def.bit ----------------- Bitrans table ('rules file') to convert from v101 to STA1 and back. The "def" suffix of the file name indicates that this is the exact definition file, and it contains only those STA codes that are defined by the v101 alphabet (192 rules). It generates STA Level-0 output, and conversion to STA Level 1-is recommended. Note: v101 to STA is translation direction 2 (right to left). Subdirectory: manual_examples ----------------------------- This subdirectory includes the example text files and rules files that are used in the bitrans user manual, collected in a single Zip file: examples.zip -------------------------------- Contents of subdirectory ivtt -------------------------------- IVTFF_format.pdf ---------------- This document at issue 1.7 provides a complete description of the Intermediate Voynich Transcription File Format (IVTFF), format definition v.1.7. All main transliteration files in the directory $HOME/data use this version of the format. Some older files may use format definition 1.5 or 1.6, but these only differ from 1.7 in the sense that some options are not yet used. IVTT_manual.pdf --------------- A user guide for IVTT version 1.3 ivtt.c ------ Source code of the IVTT tool, that reads and processes files in IVTFF format versions 1.5 to 1.7. This is version 1.3 which can process text tags, which are used for the new hands identification by Lisa Fagin Davis, and which are available in all the latest transliteration files. Version 1.2 had a bug, which caused hash comment lines not to be removed when any of the shortcut codes (-x) was used. That version should therefore not be used. It has been tested on Linux (Ubuntu), and seems safe to use. It can be built with standard libraries as follows: cc -o ivtt ivtt.c There are no known issues with the tool.