Dagobert Michelsen <[email protected]> writes: > Hello Simon, > > Am 24.03.2009 um 08:25 schrieb Simon Josefsson: >> Thanks for the pointer. As far as I can tell, you do agree that >> nl_langinfo(CODESET) passed as an argument to iconv_open should >> work, at >> least internally on each platform. Is that right? If so, I don't see >> anything we can do about this in libidn (except to fix the >> segmentation >> fault above, but that is already done). Or is there a better way to >> find out what string to pass to iconv_open for the locale charset than >> using nl_langinfo(CODESET)? I have been worried about nl_langinfo not >> being thread safe, and thus inappropriate for use in a library; it >> is a >> minor problem that I haven't been able to solve. If there is a better >> approach than nl_langinfo, libidn could use it. > > Can I safely deploy libidn 1.13 on Solaris or do I need to wait on > an enhanced libiconv before doing so? I didn't have the problem with > the 1.9 version, so is it best to deploy an older version on Solaris > then?
I'm surprised that there would be a difference between libidn 1.9 and libidn 1.13 here. I don't recall any code changed in this area between these versions. Maybe you could try to pin-point in which version it stopped working? /Simon _______________________________________________ Help-libidn mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-libidn
