![]() |
The Naibbe cipher - Printable Version +- The Voynich Ninja (https://www.voynich.ninja) +-- Forum: Voynich Research (https://www.voynich.ninja/forum-27.html) +--- Forum: Theories & Solutions (https://www.voynich.ninja/forum-58.html) +--- Thread: The Naibbe cipher (/thread-4848.html) |
RE: The Naibbe cipher - quimqu - 14-08-2025 (14-08-2025, 12:25 AM)davidma Wrote: You are not allowed to view links. Register or Login to view.As i recall from your post quimqu no other cipher had that distinctive bump that the VM has, but the naibbe one does. No, syllabic substitution made the trick of the bump also. RE: The Naibbe cipher - bi3mw - 14-08-2025 Addendum to You are not allowed to view links. Register or Login to view.: You can also create a heat map in which the labels are displayed in Voynichese. This requires that the font (usually “eva1.ttf”) be installed on your PC. In the following line in the Python script, the path to the font must be adjusted (line 59): custom_font_path = "/home/me/.local/share/fonts/eva1.ttf" The call is made as already described, where 25 is the variable number of listed pairs: python heatmap_prefix_suffix.py parsed.txt 25 Code: #!/usr/bin/env python3 Here are the text files for parsing: ![]() ![]() RE: The Naibbe cipher - RobGea - 05-09-2025 You are not allowed to view links. Register or Login to view. qokchy tched qokeody alar qokaiin shedy qolcheody shg ain GRATIASTIBIAGO RE: The Naibbe cipher - magnesium - 05-09-2025 (05-09-2025, 07:52 PM)RobGea Wrote: You are not allowed to view links. Register or Login to view.You are not allowed to view links. Register or Login to view. We have a winner! RE: The Naibbe cipher - nablator - 05-09-2025 About the scripts posted by Magnesium in the other thread: You are not allowed to view links. Register or Login to view. I tried naibbe.py and decrypt_naibbe.py on a Latin text (1000 short lines) with default settings: no problem. ![]() Despite this setting in naibbe.py: UNAMBIGUOUS=True #True means bigram token generation avoids accidentally creating unigram word types. Strongly recommend True I had an ambiguity at decryption every few lines, for example: ep(ma|it)aphium 20250724 Naibbe Cipher Paper Wrote:2.7 Minimizing ambiguities during encryption and decryption naibbe.py Wrote:Total ambiguity retries due to prefix+suffix collisions with unigrams: 798 No issue, but I'm just wondering: if these retries do not eliminate ambiguities completely, should there be more retries? After 4 attempts I got a non-ambiguous ciphertext for "epitaphium", so it is possible: chedy dchdy qokaiin yte shy qokedy sheedy qokar. RE: The Naibbe cipher - magnesium - 05-09-2025 (05-09-2025, 10:08 PM)nablator Wrote: You are not allowed to view links. Register or Login to view.I tried naibbe.py and decrypt_naibbe.py on a Latin text (1000 short lines) with default settings: no problem. In principle yes, there should be a loop that checks bigram-bigram ambiguity. I haven’t gotten there yet; I am working on it. As an interim solution I included the ambiguous decryption formatting under the UNAMBIGUOUS condition so that bigram-bigram ambiguity is at least visible. RE: The Naibbe cipher - magnesium - 06-09-2025 (05-09-2025, 10:08 PM)nablator Wrote: You are not allowed to view links. Register or Login to view.About the scripts posted by Magnesium in the other thread: You are not allowed to view links. Register or Login to view. I have added "naibbe_v2.py" to the Dropbox folder, along with an associated Jupyter notebook. Its version of the unambiguous loop should take care of bigram-bigram ambiguity without too much drag on performance. |