https://csiph.com/group/alt.flashback/a/11cnl7j%24377an%241@paganini.bofh.team

@conlang@soc.octade.net
@8@star.octade.net
@abbey@ars-cotidiana.eu

Ideas for Hexlish improvement

In my initial off-the cuff idea the 'spacing characters that don't belong' can just be filtered out or parser-inserted where spaces are found in the text just prior to encoding.

Use the space character as a stream shift register or top-bit range toggle in the encoding logic. Then any punctuation character can be placed after the space. The parser will pick up the characters, re-encode them, and toggle back at the next space. A checker would need to look for double toggle characters in sequence.

This would necessitate swapping out one alphabet character and it would require slightly more complex logic for simple ciphers to use. But it goes in a doable direction.

Abbey Schnabel suggested using the dot (.) as a character and marker and rendering Hexlish as all lower-case. These are sound improvements to legibility.

At first glance, I can't help but think spaces would be better. As for rendering it all lower-case, it could actually be case insensitive, and every letter could be treated as lowercase or uppercase regardless, using a shift or toggle nybble in the encoding stream.

It is too complex for me to wrap my brain around all the potential quirks right now, so maybe the first week of next month I'll sit down and really brainstorm it on paper.

#Hexlish #Conlang #Alphabets #English #Hexadecimal #Encoding
#Cryptography #Ciphers #Crypto #Encryption #Compression #Papers
#Preprints #Orthography #Language #Linguistics #Writing #Glyphs
#Alphabetology #Technology