KM converts it to UTF in URLbar
but user isn't transferred to the anchor placement on page.
As I found out, it's the whole Gecko problem as newest FF behaves the same way.
And my Comodo Dragon (ie Chrome) handles page correctly.
One amusing thing is that KM handles pure cyrillic links (e.g. http://президент.рф/ ) properly.
But having a look to the DNS server dialog, this is what happens:
Sending request to a.root-servers.net. (184.108.40.206) for A-record for xn--d1abbgf6aiiy.xn--p1ai.
Reply from 220.127.116.11 about A-record for xn--d1abbgf6aiiy.xn--p1ai.:
-> Authority: NS-record for xn--p1ai. = f.dns.ripn.net.
-> Additional: AAAA-record for f.dns.ripn.net. = 2001:0678:0014:0000:0193:0232:0156:0017
-> Additional: A-record for f.dns.ripn.net. = 18.104.22.168
Sending request to f.dns.ripn.net. (22.214.171.124) for A-record for xn--d1abbgf6aiiy.xn--p1ai.
Reply from 126.96.36.199 about A-record for xn--d1abbgf6aiiy.xn--p1ai.:
-> Authority: NS-record for xn--d1abbgf6aiiy.xn--p1ai. = ns.gov.ru.
Or, in other words, is established that the translation that browsers do for non-ascii character in domains, can be resolved as are already registered an routed on the root DNSs servers of internet, so...
I don't think is strange or abnormal behavior. Indeed, the HTML must be coded correctly, so if someone mapped an URL with a name in non-ascii characters... is not a good webmaster. I don't know what W3C has to say here, but I think non-ascii characters are not implemented in HTML, just for these reasons
But, going about K-meleon, why it doesn't show in cyrillic the URL mapping?, I don't know, I find normal bahavior. Or better for Chrome.
Edited 2 time(s). Last edit at 02/08/2012 08:15PM by JohnHell.