David Barr <barr(_at_)visi(_dot_)com> schrieb/wrote:
However, client support for (and active use of) UTF-8 is far more
pervasive than any of the other proposed encoding schemes.
Not the way you need it. Untagged non-UTF-8 charsets will be around for
some time, so you need a newsreader than can switch between UTF-8 and at
least one different 8bit charset automatically. That's only implemented
by very few newsreaders (and the right thing to do even if there was no
draft suggesting it) and all of these newsreaders also support RFC 2047.
This only applies to text for human consumption (i.e. everything where
RFC 2047's encoded-words are allowed). Raw UTF-8 in newsgroup names has
already been proven to cause severe interoperability problems.
Claus
--
------------------------ http://www.faerber.muc.de/ ------------------------
OpenPGP: DSS 1024/639680F0 E7A8 AADB 6C8A 2450 67EA AF68 48A5 0E63 6396 80F0