So sprach �Jeffrey Stedfast� am 2002-01-05 um 15:10:30 -0500 :
> There's really no use arguing over this because it's not an issue, it is
> completely valid according to the rfcs and it also "Just Works".
Okay, you're right. Technically it's allowed. However, can we agree
that the way Evo encodes header fields is suboptimal? If I type "w�rter
�uro" in the subject, Evo will use 2 charsets: iso-8859-1 and
windows-1251. This makes the subject unnecessary big, when using
nothing but iso-8859-15 would be sufficient.
Compare the way Evolution encodes "Test Subject with W�rter �uro �ent
�en � � �" to the way mutt does it:
Evo:
Subject: Test Subject with =?ISO-8859-1?Q?W=F6rter?=
=?windows-1251?Q?_=88uro?= =?ISO-8859-1?Q?_=A2ent?= =?ISO-8859-1?Q?_=A5en?=
=?ISO-8859-1?Q?_=E4?= =?ISO-8859-1?Q?_=F6?= =?ISO-8859-1?Q?_=FC?=
mutt:
Subject: Test Subject with =?iso-8859-15?Q?W=F6rter?=
=?iso-8859-15?B?IKR1cm8gomVudCClZW4g5CD2IPw=?=
It shouldn't be too hard to "inspire" yourself with the way mutt handels
this, should it?
Alexander Skwar
--
How to quote: http://learn.to/quote (german) http://quote.6x.to (english)
Homepage: http://www.iso-top.de | Jabber: [EMAIL PROTECTED]
iso-top.de - Die g�nstige Art an Linux Distributionen zu kommen
Uptime: 22 days 1 hour 36 minutes
_______________________________________________
evolution maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution
