Christian Weisgerber <na...@mips.inka.de> writes: > Here's a port of libidn2 for comments. (I thought we might need > this for curl 7.51.0, but we'll take a different direction.)
codesearch.debian.net says that the following debian packages contain the string "idn2_": aptly, libidn2-0, libpsl, php-pecl-http, html-xml-utils The situation is a bit ridiculous. The world hasn't magically moved to libidn2. I'm wondering whether we should actually remove idn1 support. > * Not sure about the category. devel (like libidn)? net? I'd put them in the same category for consistency. > * COMMENT and in particular DESCR are very sparse. > * I have disabled iconv support. Supposedly this is only needed to > convert other locales to UTF-8, so it should not apply to us. This appears to be sufficient given libidn2's API (it takes either UTF-8 encoded strings or locale-encoded strings). I think this is a reasonable choice. > * share/gtk-doc/html/libidn2/... hmm. Is that a problem, as long as gtk-doc isn't needed? I'd suggest we install libidn2.pdf along with libidn2.info. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
