Following UTF-8 links

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a serious problem with IE not encoding links with double byte
characters correctly. If I follow a link encoded in UTF-8 and the link
contains characters that are encoded as two bytes I get a DNS error or a http
404 error from the webserver. I have checked the option to alwasy send links
as UTF-8, but I still have the same problem.
See this example http://pi.cr.yp.to/
Anyone that have the same problem or is it just me ?

/ marcus
 
Marcus said:
I have a serious problem with IE not encoding links with double byte
characters correctly. If I follow a link encoded in UTF-8 and the link
contains characters that are encoded as two bytes I get a DNS error or a http
404 error from the webserver. I have checked the option to alwasy send links
as UTF-8, but I still have the same problem.

I think you are misinterpreting what that option is meant for.
AFAIK it is not intended to support UTF-8 at the subdomain level
of a URL but at the path and filename level only.

In order to get support for Internationalized names at the subdomain
level you need to use a third-party program. Do a Google web search
for "Internationalized Domain names" "PunyCode", especially the latter.
There was a brief discussion in this newsgroup earlier this year about that.
Apparently you can get a plugin from Verisign (e.g.) called iNav
which would convert your UTF-8 subdomain name to PunyCode.
Otherwise you would have to do that conversion yourself.

See this example http://pi.cr.yp.to/
Anyone that have the same problem or is it just me ?

/ marcus

<extract>
http://p.cr.yp.to/
</extract>

Out of curiosity let's try to figure out how to convert that.
According to CharMap "Greek Small Letter Pi" is U+03C0.

This looks like more work than I want to try by hand!
http://ietf.org/rfc/rfc3492.txt?number=3492

However, according to two online converters the punycode
equivalent of U+03C0 is xn--1xa.
So supposedly you could retype your URLs,
substituting your pi with that.
Unfortunately I have my doubts about the reliability of those
converters...

FWIW I tried using nslookup on your nameserver
(a.ns.yp.to) with xn--1xa.cr.yp.to but results were
inconclusive as the request timed out. YMMV.


Good luck

Robert Aldwinckle
---
 
Back
Top