Re: [idn] UTF-8 / RACE

["Eric A. Hall" <ehall@ehsco.com>]

> I don't think it's fair to characterize ACE as a halfway solution.

It requires significant additional computations and presentation
processing for it to be anywhere near seamless for the user. UTF8 encoded
data does not require multiple translations. Maybe "halfway" isn't proper
descriptor for ACE (did I use it? no matter), but it's not a complete
solution either.

> since the vast majority of applications will be using standard APIs
> which convert between native character set and encoding and those
> used on the wire.  For this purpose, the application doesn't care
> whether the format is UTF-8 or ACE.

My guess is that over the next 10 years, the majority of the systems will
be either be native UTF8 or UTF32.

> > It is highly unlikely that those services will ever be fixed until
> > a UTF8 form is developed by us, embraced by the WG, and coded by
> > the vendor community.
> 
> think of it another way - there's no way that the IDN WG can "fix"
> these services

I made a typo, "WG" should have been plural, as in "the appropriate IETF
working groups for each of the protocols".

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/