non-US-ASCII characters in IETF documents

[stanislav shalunov <shalunov at internet2.edu>]

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

Dave Crocker <dhc2 at dcrocker.net> writes:

> Equally, it is clear that the strongly international quality to the
> IETF requires permitting at least SOME encoding of non-ASCII.

I would say that to the contrary, the strongly international nature of
IETF (with different default character sets, different sets of fonts,
various national conventions, etc.), dictates using a lowest common
denominator of US-ASCII for the documents (in much the same way that
diversity of computing environments encourages plain text documents).

> As you note, at least being able to encode a person's name properly
> would seem more than appropriate.

The "proper" encoding of my name is óÔÁÎÉÓÌÁ× ûÁÌÕÎÏ× (in KOI8-R; the
Russian language has at least four character sets in active use).  Can
you read that?  I thought so.  That's why I write it in US-ASCII in
English-language documents (such as I-Ds).

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia

iQCVAwUBO7Ehs5RUn1EgN49xAQFbzQP7BOzifCePHptkEi85ueXuOM+BE1wMvHbY
i/2EEyGG/ls/9eAAEnQ+tK4+i7/o3jeAcf2S9TCTAKImac/ifh2zHrlbsqbWXt7L
O3qq6ydO88ZPpSg8iejCCr1PqgE49XiNk64fMkHWqxgf/NtzXkbmripXSxlRXrD5
Wv0Y64As9fM=
=uGkA
-----END PGP SIGNATURE-----

-- 
Stanislav Shalunov		http://www.internet2.edu/~shalunov/

Beware of Programmers who carry screwdrivers.    -- Leonard Brandwein