Well I have just been getting a hang of the AXE language and decided my first project is going to be some kind of text compression for my future projects.  I was thinking if you use A thru Z, <space>, <period>, <question mark>, <comma>, <single quote>, <colon>.  That is 32 characters altogether.  You can use 5 bits instead of the 8 bits and therefore saving about 35% space.  If you had 500 characters (500 bytes) and use this theory your total memory usage would be approximately 313 bytes.   What does everybody think?  Would this benefit anybody in their current projects or future ones?  Input would be appreciated thanks.

I was thinking if you use A thru Z, <space>, <period>, <question mark>, <comma>, <single quote>, <colon>.  That is 32 characters altogether.  You can use 5 bits instead of the 8 bits and therefore saving about 35% space.

You forgot something: There is not only A,B,C,... but also a,b,c,...
But yeah, that would be very useful (don't forget the decompression algorithm )

Well I was also thinking about the lowercase letters, but in reality they just look good and take up more space .  I might implement later another version that does more characters if there is enough support, but it will also be less compression too.  I have almost got the compression engine finished .  It looks pretty solid  ,  I have not had too many bugs in it that were not easily fixable.   Axe is definitilely easier to program in if you look at it like assembly code in a sense but with syntax like basic.

a,b, and c are two byte tokens on-calc. They aren't represented the same as normal ASCII.

Yes they are, because we are talking about character codes, not tokens.  The ASCII chart that the calc uses has 256 characters that are each 1 space long.  Each can be referenced by a single byte number, using the Axe command >Char. 

Looks interesting... I have a project that could benefit from this...

This is way cool!!!
and yes please do include lowercase. <insert puppy dog eyes>

what do you mean by symbols?

Ok i'll see what I can do with the lowercase letters.  Another thing,  what about numbers?  With my current routine and plans on the lowercase,  I can only have about 64 characters.  I could take out some of the symbols if numbers was needed.

Personally, I use numbers 1,2,3,4 and symbols !?.,-':
I think that is all. But yeah, I am not alone in this planet, so do what you think is fair

Another idea, during decompression, you can automatically make the first letter of every sentence uppercase, and the rest lowercase. That way it still looks nice, but it takes up the same amount of space.  You can use other rules too to capitalize things in quotes.  Also, don't forget about characters '0' through '9', those are probably important too.

But if we want to display "Hi Ginny !", then Ginny will be with lowercase
But yeah, that would save space.