If you go to the Slashdot page, you'll see some comments that clarify on
the situation:
For "dumb browsers" (not a flame, just an indication of
character-set-awareness), you'd see some crazy domain
like http://www.bq-ag0970ag00ah07h.or.jp/; for "smart browsers,"
it would appear in your own kanji font.
For those URLs that put actual non-ASCII characters in the domain name,
well that's their problem (the cafe24 example below). I'm sure they'll
make sure it works in Netscape 4 and I'm sure Netscape 4 also used char*
for URLs, so we should be alright.
- Oleg
Simon Fraser wrote:
>
> In article <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] (Matthew Thomas) wrote:
>
> > Yung-Fong Tang wrote:
> > >...
> > > 2. in the end there are some sentence include the following URL
> > >
> > > »ý¼ºURL :http://»ç¿ëÀÚID.cafe24.com
> > >
> > > Is this article talk about iDNS in Korea ? Does Korean already start
> > > using non ASCII in host name ?
> > >...
> >
> > See `Registrations Now Accepted For Asian Domain Names'
> > <http://slashdot.org/articles/00/11/10/1357253.shtml>.
>
> Hoo boy. So all the places that we use char* for URLs in the
> code suddenly become wrong?
>
> Simon
>
> --
> Simon Fraser Entomologist
> [EMAIL PROTECTED] http://people.netscape.com/sfraser/
