On Fri, Nov 4, 2016 at 10:50 AM, Nikos Mavrogiannopoulos <n.mavrogiannopou...@gmail.com> wrote: >> What I need and already do via libunistring API is lowercasing and NFC/NFCK >> (not 100% sure which one to use). >> I think adding two flags to the idn2 API should do it. >> Shouldn't TR#46 be mandatory ? If not, another flag would do it. >>> The idea is that libidn2 should be a usable IDNA2008 library, and that >>> probably involves exposing NFC and TR46 APIs as well. >> Hiding libunistring details is IMO a good idea here. > I'd love that too. That would make migration from libidn to libidn2 > significantly easier.
Another thing that I noticed which makes the combination of the two APIs quite inefficient, is that libunistring assumes and outputs non-null terminated strings, while libidn2 requires null terminated strings. regards, Nikos _______________________________________________ Help-libidn mailing list Help-libidn@gnu.org https://lists.gnu.org/mailman/listinfo/help-libidn
