This is the mail archive of the
mailing list for the glibc project.
Re: RFC: IDN support in getaddrinfo().
- From: Simon Josefsson <jas at extundo dot com>
- To: libc-alpha at sources dot redhat dot com
- Date: Mon, 08 Mar 2004 18:07:48 +0100
- Subject: Re: RFC: IDN support in getaddrinfo().
- References: <firstname.lastname@example.org> <3FC41F79.email@example.com><firstname.lastname@example.org> <3FC47A3B.email@example.com><firstname.lastname@example.org> <3FC4E691.email@example.com><firstname.lastname@example.org> <3FC4F244.email@example.com><firstname.lastname@example.org><email@example.com> <3FC50672.firstname.lastname@example.org><email@example.com><firstname.lastname@example.org> <404BF3EF.email@example.com>
Compiling current CVS gives:
make -C manual subdir_install
make: Entering directory `/home/jas/src/libc/manual'
make: *** No rule to make target `../libidn/libidn.texi', needed by `chapters .texi'. Stop.
make: Leaving directory `/home/jas/src/libc/manual'
make: *** [manual/subdir_install] Error 2
make: Leaving directory `/home/jas/src/libc'
make: *** [install] Error 2
I suspect the fix is simple, but I don't know what it is.
But it raises another question: how should we document the IDN
extension of getaddrinfo? Libidn standalone contain a libidn.texi
that, I like to believe, cover most things about libidn. Except the
libc-specific integration, of course, which is perhaps the only part
that would be interesting to libc users.
Perhaps the most appropriate would be to briefly describe the AI_IDN
(and eventually AI_CANONIDN) flags where getaddrinfo is documented,
and add some paragraphs, or an entire section, about general IDN
issues? I can suggest a starting pointer for this, but English isn't
my native tongue and I'm not a good writer, so if someone better
inclined could do it, that would be good...