From: Claus Färber (list-ietf-wg-apps-usefor@faerber.muc.de)
Date: Sun Aug 25 2002 - 15:24:00 CDT
Erland Sommarskog <sommar-usefor@algonet.se> schrieb/wrote:
> =?ISO-8859-1?Q?Claus_F=E4rber?= (list-ietf-wg-apps-usefor@faerber.muc.de) writes:
>> Further, most newsreader support only one display charset at once. With
>> the dumb newsreader you describe, you won't be able to read any messages
>> which use the 8bit charsets currently in use if you set your TTY charset
>> to UTF-8.
> Yes, I can handle this. It was the same thing when we went from 7-bit to
> 8-bit in the Swedish hierachies. That included a frequent changing of
> the CRT settings.
On a per-posting basis? Probably not.
> Note, by the way, that the same issue applies to RFC2047.
No.
(RFC 2047-enabled newsreaders exist today and can handle -- i.e. display
the characters displayable on the current terminal -- multiple charsets.
Newsreaders that automatically detect UTF-8 and a leagacy encoding may
exist, too. But these are not those newsreaders for which you claim UTF-
8 has advantages -- these newsreaders don't understand RFC 2047 nor can
they detect different charsets.)
Please note that this has nothing to do with the encoding of the
Newsgroups header. Sending raw UTF-8 in text fields has no advantages
over RFC 2047 but it does not create severe compatibility problems as
UTF-8 in Newsgroups headers does.
Claus
-- ------------------------ http://www.faerber.muc.de/ ------------------------ OpenPGP: DSS 1024/639680F0 E7A8 AADB 6C8A 2450 67EA AF68 48A5 0E63 6396 80F0