You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the domain business, just few TLDs are based on IDN 2008 punycode conversion:
.be, .ca, .de, .fr, .pm, .re, .swiss, .tf, .wf, .yt
All other TLDs use the IDN 2003 standard.
Just got that information from my team mates (we work in the domain business) and they point out that the npm module "idna-uts46" handles it in the right way. As punycode.js is bundled with node.js the better option IMO is to inform you instead of switching to another library.
In the domain business, just few TLDs are based on IDN 2008 punycode conversion:
.be, .ca, .de, .fr, .pm, .re, .swiss, .tf, .wf, .yt
All other TLDs use the IDN 2003 standard.
Just got that information from my team mates (we work in the domain business) and they point out that the npm module "idna-uts46" handles it in the right way. As punycode.js is bundled with node.js the better option IMO is to inform you instead of switching to another library.
Example:
fußbälle.de -> fussbälle.de (IDN 2003)
fußbälle.de -> fußbälle.de (IDN 2008) <-- the correct one!
fußbälle.org -> xn--fublle-cta5b.org -> fußbälle.org (which is wrong, has to be IDN 2003).
correct one would be: xn--fussblle-4za.org
this is still the case for punycode.js v1.3.2
The text was updated successfully, but these errors were encountered: