Re: [idn] I fear I cannot use IDN in the next 10 years

[David Hopwood <david.hopwood@zetnet.co.uk>]

-----BEGIN PGP SIGNED MESSAGE-----

DougEwell2@cs.com wrote:
> In a message dated 2001-10-05 0:39:39 Pacific Daylight Time, ehall@ehsco.com
> writes:
> 
> >  Clearly the world wants a UCS. While it is true that nobody can guarantee
> >  that this will be 10646/Unicode, we can all be certain that it absolutely
> >  WON'T be ASCII. What we can also be sure of is that UTF-8 will be the
> >  favored encoding for the future that we can see.
> 
> You can't be sure about UTF-8 unless you can guarantee 10646/Unicode.

ACE also relies on 10646/Unicode, so any speculation about hypothetical
UCSs other than 10646/Unicode isn't relevant to the arguments about the
merits of ACE and/or UTF-8.

It's perfectly clear that UTF-8 is the favoured charset for both new
IETF protocols and revisions of existing IETF protocols: [BCP18] says so,
and [BCP18] has widespread support among designers and implementors.
If anyone seriously disputes this, they must not be looking at the same
Internet that the rest of us are looking at.


[BCP18] IETF Policy on Character Sets and Languages. H. Alvestrand.
        January 1998. Also RFC2277.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO72R6jkCAxeYt5gVAQErggf/aN04/J0qbzCQlGSSinNPUU0L+jApiOeu
l0wIf8b0zdOu3RdzerlSnG0YzE/RE3jmPnpsN2bCLJFzElggZRzS7Hn8HwA1qpyy
N3UNuRoWSAa8ezLpv5AFwhCpPz1o4NJOL5xzQNgt8vkXtJ5BtpVVjN+sBGQ19rtx
PV/QY7iuy62T2KQjg9C4jcf/S4U1kEYs9WGYCOwZEntUnQWtSTz4+heTGSFwdYI7
o8rhO5hlH05oknIanpooSlkDjmHy7bvqA9g8Uq+EIIWdN+btzJ4Otvdo3w2zpVdI
Jy9SopNM9EOk0NulM1HUjNLF6XLNcayrP+tBdwBWi6g2ur3+PkZQNg==
=zwNP
-----END PGP SIGNATURE-----