----- Original Message -----
From: "John Stracke" <jstracke(_at_)incentivesystems(_dot_)com>
Fine. But you were talking about the complexity on the client side. A
UTF-8 transition would add complexity on the client, not reduce it,
because the client would then have two cases to consider: servers that
support UTF-8, and those that don't.
You are right if you are talking about end-end-user apps. But think about
the apps required for managing DNS / email servers / registries / ... etc.
Any app EXCEPT the end-end-user apps (such as the browser or nslookup tools)
will NOT have to do ACE. If they are trying to access an old server which
have no IDN support, it will use ASCII, be it ACE or regular English
alphanumeric. If they connect to IDN aware servers, they will use
IDN(UTF8). If the receive information from IDN servers they simply use the
UTF8 data (or ACE data) as is without any further encoding/decoding.
Which mean http servers / smtp servers / etc. will only deal with IDNs as
IDNs if they were IDN(UTF8) and continue to treat ACE as ASCII just as if
they were encountering an English alphanumeric domain.