On Friday, January 8, 2016 at 2:56:36 PM UTC-5, [email protected] wrote: > > This question has been asked and answered several times. I've looked at > all the old answers and looked at the source code, but I am not able to get > base32 to work with an alternative alphabet. I would like to use the > RFC4648 alphabet rather than the DUDE alphabet. >
I'm thinking one of the easiest things to do would be good old copy/paste. That is, copy Base32Encoder, paste it as Base32AltEncoder in the same header file, replace the alphabet, do the same in the source file, and you are ready to go. We did the same at https://github.com/weidai11/cryptopp/commit/ea75b3ae5fabc1c5a01a71ab395ac99a4946c818. But don't let me dissuade you... If you can provide details on what's going wrong with IsolatedInitialize(), then maybe we can help you work through it. > The alt_base32 files that Jeffrey Walton placed on the Cryptopp wiki > have been removed from this URLhttp://www.cryptopp.com/wiki/File:RFC4648 > Hmmm.... I wonder if it was deleted, or if the migration over the summer lost it... I'm betting it was migration related. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
