[Webkit-unassigned] [Bug 13167] Unescape %-escaped hostnames and convert them to punycode before DNS lookup

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=13167





------- Comment #5 from jungshik.shin at gmail.com  2007-03-23 10:55 PDT -------
(In reply to comment #4)
> As far as I am aware, Safari 2.0 supports IDN correctly too.  Unless I am
> mistaken it is not a recent addition to WebKit.

Thanks a lot for the info. Indeed, Safari 2.0.4 on my Mac supports it well. I
should have tried it before asking. 

> As far as UTF-8 goes, your comment shows up with garbled characters too as
> Bugzilla doesn't specify any character set in its HTTP headers or document
> header.  

Of course, I'm well aware of that. :-) I thought it's obvious that you should
set view | encoding to UTF-8 when reading my comment :-)  In your case,
characters not covered by the encoding in effect (most likely ISO-8859-1 or
Windows-1252) when you submitted comment were converted to NCRs and stored that
way on bugzilla DB so that simply changing the encoding on the browser-side
does not give back the original. In my case, UTF-8 byte sequences are stored in
the DB and 'emitted' to  a browser so that just changing the encoding works. 


> I should look at fixing this on the server side so that all pages are
> served as UTF-8 and forms are submitted as the same.

It took bugzilla.mozilla.org to fix that problem 5+ years !!! WebKit bugzilla
has only 13k bugs and I guess most of them are straight ASCII so that it should
be easier. See http://bugzilla.mozilla.org/show_bug.cgi?id=126266 (and bugs
that were made its dupe and it spun off) about a long and winding road they
took. 


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.