Re: [idn] URL encoding in html page

["David Leung \(Neteka Inc.\)" <david@neteka.com>]

> ----- Original Message -----
> From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
> > "David Leung (Neteka Inc.)" <david@neteka.com> wrote:
> > > So now IDN is a larger scope than we expected, not just browser
> > > software needs to upgrade, even html editor like Dreamweaver, etc
> > > needs to upgrade...
> >
> > It should not be surprising that any software that deals with domain
> > names as such (as opposed to text in general) might need to be upgraded
> > in order to allow characters in domain names that used to be forbidden.
> >
> (the keyword in this extract is "ANY".  ANY software that deal with domain
> names in a "human friendly form" will need to be upgraded.  That means
> almost all applications that use domain names isnt it? cause domain names
> were supposedly devised to be a "human friendly" name)
Edmon... I think it means every "human readable" UI has to be downgrade not
upgrade... we should have something readable that converts to something
unreadable so that web-designer dont know what they are putting in as URL
: )

> This is a revealing point you have pointed out Adam.  While you and some
ACE
> "everywhere" advocates maintain that ACE "everywhere" requires the least
> upgrade, this seems to jump back out at yourselves that afterall, it is
not
> as small a job as it was advertised.
>
> This and that together, if we are going to need an overhaul what is the
> point of going back to ASCII and not move forward to a more advanced
schema?
I always think of IDN this way, we need to upgrade software anyways but
there is two approach...
ACE or UTF8...

ACE will work with "EXISTING" systems but ALL client end(browser, MUA, etc)
and SOME server(Apache, etc) end software actually needs to upgrade in order
to be able to recognize IDN and convert it to ACE back and forth, unless we
want to say that www.ietf.org that we are using nowadays is IDN already : )

On the other hand, we see a lot of applications is moving towards the
support of UTF8/Unicode on the client side, and this is going to be the
future anyways... so why not just upgrade the server software, with one
server software upgraded it will serve many many users... I dont understand
why no one see this simple math : )