-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An alternative that does not use control characters #8
Comments
Seconded. Control characters make it impossible to copy & paste, which is an important usage given certain circumstances. |
BasE91 -- http://base91.sourceforge.net/ already with C libraries. Base122 needs some C libraries. |
@sijanec is this better or worse than B122? |
In terms of data overhead, it is worse than base122, because it has a
smaller character set to display the same amount of data.
Roughly speaking, the higher the "base-number" in base-n binary-to text
encoding, the less data is required to represent a specific amount of
binary data. If you - for example - need an even "better" encoding, you can
go with Base128, that still remains in the ASCII range 0x00-0x7F, but
includes even more control characters and even null char, which may not be
an option.
V V pet., 21. avg. 2020 ob 04:00 je oseba Don Tsang <
[email protected]> napisala:
… @sijanec <https://github.com/sijanec> is this better or worse than B122?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKFM2EQWUY5MU2EZKODU4K3SBXIKZANCNFSM4H5CF6UA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since this is made to be UTF-8 compatible, why not make it such that it renders all text normally?
The text was updated successfully, but these errors were encountered: