You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the alphabet you defined uses all printable characters except space. Why is that? Some very problematic chars like backslash or doublequote that will need to be escaped in JSON and many programming languages. Why were they included in the alphabet?
The text was updated successfully, but these errors were encountered:
Basically, this encoding is a solution to a different problem than "convenient embedding in JSON". Base94 uses all printable characters, which have the same ASCII codes in all character sets, which explains why no whitespace is included (you won't see any visible difference between ASCII 32 and 10, for example). So it is limited to 7-bit codes only, excluding all codes that don't have a printable symbol.
The main goal - to extend the alphabet as much as possible, but limit it to the point where it's supported everywhere, all the time. For the case you mentioned, Base64 is widely used, which has the alphabet limited by 6 bits and carefully chosen characters, with a small adjustments https://datatracker.ietf.org/doc/html/rfc4648#page-7 to the original set.
Hello,
I noticed that the alphabet you defined uses all printable characters except space. Why is that? Some very problematic chars like backslash or doublequote that will need to be escaped in JSON and many programming languages. Why were they included in the alphabet?
The text was updated successfully, but these errors were encountered: