Description of problem: Unfortunately there doesn't seem to be IDNA 2008 support in jwhois: Version-Release number of selected component (if applicable): $ jwhois straße.de | grep ^Domain: Domain: strasse.de $ Uhm? That is IDNA 2003: $ idn straße.de strasse.de $ However when using IDNA 2008 it looks a bit different: $ idn2 straße.de xn--strae-oqa.de $ $ jwhois xn--strae-oqa.de | grep ^Domain: Domain: straße.de $ How reproducible: Everytime, see above and below. Actual results: Only IDNA 2003 support: $ jwhois straße.de | grep ^Domain: Domain: strasse.de $ Expected results: IDNA 2008 support rather IDNA 2003 support: $ jwhois xn--strae-oqa.de | grep ^Domain: Domain: straße.de $
Created attachment 896779 [details] jwhois-4.0-libidn2.patch Vitezslav, may you review that patch? I think it also should make sense to get this patch upstreamed. I do not think it makes sense to have IDNA 2003 and 2008 support at buildtime thus I replaced it simply.
Hello Robert, the patch looks fine, I'll apply it in Rawhide. Of course it makes sense to have it upstream, but the upstream is unmaintained currently, see [1]. No commit for ~3 years. By the way, it seems that users are moving to whois package [2], do you know/use it? [1] http://savannah.gnu.org/projects/jwhois/ [2] https://github.com/rfc1036/whois
(In reply to Vitezslav Crhonek from comment #2) > [1] http://savannah.gnu.org/projects/jwhois/ Last commit is from 2013: http://git.savannah.gnu.org/cgit/jwhois.git > [2] https://github.com/rfc1036/whois IMHO that implementation does not have the same feature set.
(In reply to Robert Scheck from comment #3) > (In reply to Vitezslav Crhonek from comment #2) > > [1] http://savannah.gnu.org/projects/jwhois/ > > Last commit is from 2013: http://git.savannah.gnu.org/cgit/jwhois.git Thanks, I missed that. But it looks like one-time action. Nevertheless, I'll try to contact them. > > > [2] https://github.com/rfc1036/whois > > IMHO that implementation does not have the same feature set.
Vitezslav, I also will get in touch with upstream and try to get an upstream maintainer there - given that the new nTLDs will cause a lot of updates - and I still have a German translation that also didn't make it upstream yet.