On Wednesday, December 13, 2017 at 5:02:40 AM UTC-6, rog wrote: > > > Looking at > http://philzimmermann.com/docs/human-oriented-base-32-encoding.txt, > it seems that zbase32 allows the encoder and decoder to agree on the > number of bits transmitted, so if you're encoding 5 bits or less, you > can use a single encoded character. >
Yep. I discovered this after making my for NoPadding. zbase32 uses a different packing scheme, so there is no real hope of piggy backing of of encoding/base32. ISTM that this difference is probably justification enough to make a > new zbase32 package rather than using encoding/base32 directly. > Indeed, as Caleb Spare has since pointed out, that has indeed been done. https://github.com/tv42/zbase32 <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Ftv42%2Fzbase32&sa=D&sntz=1&usg=AFQjCNGJAQZzlzQhoiUpVOPJ-lNZOcIWYA> I had actually seen that before starting, but thought why should I import all of that when I can just use base32.NewEncoding() ? Well, now I know. Cheers, -j -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
