[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: providing a libidn compatibility API
From: |
Nikos Mavrogiannopoulos |
Subject: |
Re: providing a libidn compatibility API |
Date: |
Fri, 10 Feb 2017 15:29:42 +0100 |
On Fri, Feb 10, 2017 at 10:23 AM, Tim Rühsen <address@hidden> wrote:
> Thanks for the docs !
> idn2_to_ascii_4i has different argument names than the docs - IMO, we should
> amend the arg names of the function to be in sync with the other to_ascii
> functions.
>
> Regarding the flags, I made a different approach yesterday (see 'decode'
> branch, commit 1992f3b171945677d5445f7c91a83d4746aefa04).
[...]
> The advantage would be to not hard-code flags within idn2_to_ascii_*(). That
> seems to be more flexible. If you agree, I'll commit the docs from your patch
> and amend the arg names of idn2_to_ascii_4i.
Replying to list, that this indeed makes sense. One thing I identified
is that libidn2 no longer compiles in mingw environment, or in other
environments where libunistring is missing (i.e., the internal
unistring is not sufficient).
Adding the missing items in bootstrap.conf (were already there in a
fixme block), allows compilation if one performs it as make -C lib &&
make
For some reason lib wouldn't compile, even though the order in Makefile.am is:
SUBDIRS = lib . src doc examples tests po
Example:
$ make
cat ./idna-tables-6.3.0.txt | ./gen-tables-from-iana.pl > data.c.new
mv data.c.new data.c
CC gentr46map.o
gentr46map.c:37:20: fatal error: unistr.h: No such file or directory
#include <unistr.h>
while
$ make -C lib && make
works.
regards,
Nikos
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/02/07
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/10
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/02/10
- Re: providing a libidn compatibility API,
Nikos Mavrogiannopoulos <=
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/02/10
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/13
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/14
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/02/14
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/14
- Re: providing a libidn compatibility API, Simon Josefsson, 2017/02/19