| Domain name registration Complaints and conflicts Policy for the .no domain Look up domains Statistics and analysis FAQ Glossary Publications | Technical information about Norid's ACE solutionIntroductionThis page presents a more technical description of the functionality and background of the Norid ACE conversion tool, plus some information about other IDN libraries and tools available on the net. References
All Norwegian under .no Description of the .no Policy, including the upcoming new IDN Policy DescriptionLibidn is implemented according to the RFC's above. Libidn offers a huge amount of various IDN functions to a programmer.
Norid's ACE conversion tool is written entirely in perl. Internally it mainly uses two of the IDNA functions from libidn:
Libidn offers general functions which complies the the RFC's. To enforce the local .no Domain Name Policy, the ACE Conversion tool also uses some additional perl functions developed by Norid. From version 0.4.0, libidn also offer support to check for restricted TLD character sets. Support for '.no' and '.fr' is an integral part of the distribution, whilst character set tables for some other TLDs can be downloaded from http://tldchk.berlios.de and compiled into libidn as needed. Net::LibIDN were publish on CPAN in January 2005 and provides the necessary perl bindings for libidn. Why Unicode/UTF-8 and not some ISO-8859-xx?Norid's ACE conversion tool offers its service to the user through a Unicode/UTF-8 coded web page. Why have we chosen UTF-8? To understand that, we need to study the obvious solution; why not just choose the ISO-8859 character set that covers the 23 necessary IDN characters? A good link with detailed information on ISO-8859 characters sets is The ISO 8859 family. If we compare the characters in the various ISO-8859 character tables with the 23 required ones, we find that no single table contains them all. Reading Note X confirms that ISO-8859 cannot be used, since the required Sami characters are not covered by any single ISO-8859 character set. So, the conclusion was simple, to support all new IDN characters for .no we had to choose the general Unicode/UTF-8 to be able to represent them all. You will also meet that conclusion if you want to apply for a .no IDN Domain Name. If the Domain Name contains only the IDN characters "æøå", you can send the application E-mail coded in either ISO-8859-1 or UTF-8. Some alternative IDN/ACE tools aroundIf you need to build your own IDN/ACE tool, a number of libraries based on different programming languages can be found on the net.Libidn is worth a try if you run on a *nix platform. When you build and install libidn, you also get a command line 'idn' program for free. The 'idn' program can be used to perform general IDNA/ACE conversions. For example:
If you find this a bit tedious, or you run on Windows or some other platforms not supported by libidn, or you just don't want to (or know how to) install libidn, you can still access all the 'idn' functionality as a web-service at Try GNU Libidn. The "IDNA ToASCII" operation performs the "ToASCII" ('idn -a') operation. For proper Domain Name checking, remember to also check the 'UseSTD3ASCIIRules' option. Various other IDN/IDNA/ACE related links:
|
| UNINETT Norid AS • NO-7465 TRONDHEIM • Phone +47 07355 • Fax +47 73 55 79 99 • info@norid.no |