This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: [bug-inetutils] Re: Internationalized domain names teaser
- From: Simon Josefsson <jas at extundo dot com>
- To: "Martin v. Löwis" <martin at v dot loewis dot de>
- Cc: bug-inetutils at gnu dot org, libc-alpha at sources dot redhat dot com
- Date: Wed, 08 Jan 2003 16:00:14 +0100
- Subject: Re: [bug-inetutils] Re: Internationalized domain names teaser
- References: <iluel7n6bmu.fsf@latte.josefsson.org><3E1C2874.7010306@v.loewis.de>
"Martin v. Löwis" <martin@v.loewis.de> writes:
> Simon Josefsson wrote:
>> Is anyone on the GNU Libc list aware of any API standardization in
>> this area? Any thought or input on this is appreciated.
>
> I would suggest that hostnames should be considered to be encoded with
> the encoding of nl_langinfo(CODESET).
This is what libidn does (when the *locale* functions are used), btw.
> All routines taking hostnames should then apply IDNA to their
> parameters; those taking flags (e.g. getaddrinfo) should provide a
> flag to suppress IDNA.
Sounds simple enough. But the IDNA specification says the following:
,----
| Because these resolver libraries today expect only domain names in
| ASCII, applications MUST prepare labels that are passed to the resolver
| library using the ToASCII operation. Labels received from the resolver
| library contain only ASCII characters; internationalized labels that
| cannot be represented directly in ASCII use the ACE form. ACE labels
| always include the ACE prefix.
`----
I think the IDNA specification gives poor recommendations in this
area, an area which doesn't even concern the IDNA protocol itself.