----- Original Message -----
> > With libidn2, the LANG trick for disabling IDN mentioned in the man page
> > (LANG=langauage[_terrotory].ASCII) doesn't seem to be working as described;
> > I'm not sure yet why not.  Can you try it out?
> 
> CHARSET=ASCII not working with libidn, either.  In both cases I get:
> 
> dig: convert textname to UTF-8: failure

For the disable IDN I deducted it from the original patch from Adam Tkac for
libidn we had in Fedora. For libidn it can be tested as follows:

$ CHARSET=ASCII dig axfr . @k.root-servers.net | grep '^xn--' | wc -l
576
$ dig axfr . @k.root-servers.net | grep '^xn--' | wc -l
0

It just make dig to display the output in punycode rather than in
the international format.

For libidn2 I was deducting the "workaround" based on the libidn doc [1]
but for libidn2 [2] (look for Environment Variables part).

However I can see now that it does not work for libidn2. Thinking more about it,
the functions that are used for libidn2 compared to libidn don't to the IDN
translation when producing output.

[1] http://www.gnu.org/software/libidn/manual/libidn.html#Invoking-idn
[2] http://www.gnu.org/software/libidn/libidn2/manual/libidn2.html#Invoking-idn2

If you don't have any hint I'll have to investigate it more
thoroughly to be able to fix the man page or source accordingly.

Thanks for finding this and sorry for the mistake.


Regards,
-- 
Tomas Hozza
Software Engineer - EMEA ENG Developer Experience

PGP: 1D9F3C2D
Red Hat Inc.                               http://cz.redhat.com