In message <[email protected]> on Sat, 2 Jun 2018 14:27:42 -0400, Viktor Dukhovni <[email protected]> said:
openssl-users> > (it would have been smarter to have the PKCS12 routines take wchar_t openssl-users> > strings rather than char strings... hindsight is what it is...) openssl-users> openssl-users> No, wchar_t is not defined to be a 16-bit BMPString compatible openssl-users> encoding. It is AFAIK a platform-specific string representation openssl-users> that is not canonical. Yeah, I just learned that myself. Somehow, I thought wchar_t would be Unicode characters. So ok, with this information, UTF-8 makes sense... Cheers, Richard -- Richard Levitte [email protected] OpenSSL Project http://www.openssl.org/~levitte/ _______________________________________________ openssl-project mailing list [email protected] https://mta.openssl.org/mailman/listinfo/openssl-project
