0

In Ubuntu 20.04 and older (And Debian 11, 10 and 9) I can convert Puny code domains with idn to UTF-8 / IDN format:

idn -t --quiet -a "xxx-tést.eu"

Works fine or the other way around:

idn -t --quiet -u "xn--xxx-tst-fya.eu"

Also the conversion back from IDN to puny code works as expected:
idn -u "xn--xxx-tst-fya.eu" returns me the correct domain.

Now I'm currently working on Ubuntu 22.04 / Jammy support:

idn -a "xxx-tést.eu"
idn: could not convert from ASCII to UTF-8

And:

idn -u "xn--xxx-tst-fya.eu"
idn: could not convert from UTF-8 to ASCII

On Ubuntu 20.04 I was able to resolve the similar issues when I had issues by setting: export LC_ALL=C.UTF-8. However on Ubuntu 22.04 I am not able to solve the issue.

Please note I am also experiencing this issue with other IDN domains

Description:    Ubuntu 22.04 LTS
Release:    22.04

root@test:~# apt list idn 
Listing... Done
idn/jammy,now 1.38-4build1 amd64 [installed]

Any idea how to solve this issue?

James Risner
  • 5,451
  • 11
  • 25
  • 47
Jaap Marcus
  • 11
  • 2
  • FYI: https://unix.stackexchange.com/questions/538122/what-is-the-difference-between-idn-and-idn2 – Orphans Dec 06 '22 at 12:47

2 Answers2

0
apt remove idn -y
apt install idn2 -y
ln -sf /usr/bin/idn2 /usr/bin/idn

Test ok with acme.sh.

James Risner
  • 5,451
  • 11
  • 25
  • 47
ra x
  • 1
-1
idn2 -d "xn--xxx-tst-fya.eu"

seems to be working

Jeremy Caney
  • 7,102
  • 69
  • 48
  • 77
Jaap Marcus
  • 11
  • 2
  • Remember that Stack Overflow isn't just intended to solve the immediate problem, but also to help future readers find solutions to similar problems, which requires understanding the underlying code. This is especially important for members of our community who are beginners, and not familiar with the syntax. Given that, **can you [edit] your answer to include an explanation of what you're doing** and why you believe it is the best approach? – Jeremy Caney May 09 '22 at 00:51