Closed saxbophone closed 6 years ago
I've just thought of a potential work-around for this:
Closing this, as I don't think it's possible to use padding that is compatible with base64, Ascii85, etc... with larger output bases. If a user wants to use a larger output base than input when encoding, they will just have to only pass exact chunk-sized bits of data to it.
Encountered an issue decoding symbols that were encoded from base 128 to base 255. I have a hunch that this is because the ratios are not exact and the output base is larger than the input base.
Currently, for all cases when decoding, empty padding symbols are converted to MAX just before decoding, like in base-85. I think this might only work when the input base is larger than the output base, so a different approach may be needed for when the output base is larger.
Code for Encoder class:
Sample decoding errors: