-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Wednesday 2007-10-03 at 18:08 +0200, Per Jessen wrote:
Carlos E. R. wrote:
I'll have to learn more about how it is supposed to work, first. I
found another link:
<http://en.wikipedia.org/wiki/Internationalized_domain_name>
It's really straight forward - IDNs are primarily for end-user
consumption. In the real world, or rather behind the scenes, they are
ugly looking beasts such as:
www.xn--and-6ma2c.cl
Your email agent and your browser will understand about IDNs, as should
any other GUI, but I doubt if we're likely to see command-line tools
that speak punycode any time soon.
Yes, that's what I read. The wikipedia article is quite easy to read. I
have found webpages doing the conversion to punycode for us to see, but i
haven't found a command line utility that could be used to output names to
'host', for instance.
However, a friend discovered that the man page for host and dig (the
online version) mention that they can be compiled with IDN support, and
thus do the conversion. It appears that the commands supplied by suse were
not enabled; I'd like to know why, whether because they are problematic,
buggy, or what.
Another curiosity is that the whois for .com do support IDN, but others,
like .cl or .es, do not - and they should, as they are interested parties
in this.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFHBCBptTMYHG2NR9URAhvZAJ9P8vX+r551/tUsipIU+BeNeiYqggCeJ81c
VSYtgFWiCv69pSCGOvtyrMo=
=YGhP
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
