(26-03-2025, 11:03 PM)oshfdk wrote: You are not allowed to view links. Register or Login to view.I think I got confused by 26/26/26 mapping as if it was something set in stone. As I understand now, there are lots of ways to split these words into three chunks, especially if there are additional code points for uppercase letters and punctuation (and spaces?). I'm not sure it makes sense to optimize for 26 specifically. I think this would imply that each English letter is present in each of three positions in the text, and there are no spaces, and the system is case-insensitive.
There are lots of ways to split these words into three chunks but few partitions are 1) not ambiguous (needed for reversibility, you get a lot of cases like "ab" + "c" = "a" + "bc" in almost all partitions) and 2) compatible with the size of the alphabet + 1 maybe for space. Punctuation is possible but unlikely in a ciphertext, so it makes sense to optimize for 27 or less, because all letters don't have to be present in all three positions in such a short text.
Getting the size of all three sets close to 27 is extremely hard so I was happy to find a 26-26-26 partition, but it is not completely unambiguous. I'll try to improve it.
I hoped that getting close enough to the correct partition would make it possible to identify a few of the most frequent letters or spaces.