[Evolution] =?ISO-8859-15?Q?Re[2]:=20[Evolution]=20Euro=20(=88)=20suppor?= =?ISO-8859-15?Q?t=20in=201.0?=
- From: Nerijus Baliunas <nerijus users sourceforge net>
- To: Evolution List <evolution ximian com>
- Subject: [Evolution] Re[2]: [Evolution] Euro (?) support in 1.0
- Date: Tue, 8 Jan 2002 01:13:18 +0200 (EET)
On 07 Jan 2002 13:10:05 -0500 Jeffrey Stedfast <fejj ximian com> wrote:
JS> We try to keep things QP encoded if at all possible because this way if
JS> the receiving end doesn't have a MIME compliant mailer, the recipient
JS> can still "read" (mostly) what the text actually says. If we base64
JS> encoded the subject, then you'd *have* to have a MIME mailer on the
JS> receiving end.
I think you missed the point here - it is not about QP/BASE64, but about
Evolution using 2 charsets for subject, when 1 would be enough
(although mutt could encode 2nd part as QP also, but it does not matter
in this case).
BTW, charsets like windows-1251 or KOI8 should really be BASE64 encoded, as
there usually are very little latin letters in russian mail messages,
so recipient could "read" only very little text...
JS> > Compare the way Evolution encodes "Test Subject with Wörter €uro ¢ent
JS> > ¥en ä ö ü" to the way mutt does it:
JS> >
JS> > Evo:
JS> > Subject: Test Subject with =?ISO-8859-1?Q?W=F6rter?=
JS> > =?windows-1251?Q?_=88uro?= =?ISO-8859-1?Q?_=A2ent?= =?ISO-8859-1?Q?_=A5en?=
JS> > =?ISO-8859-1?Q?_=E4?= =?ISO-8859-1?Q?_=F6?= =?ISO-8859-1?Q?_=FC?=
JS> >
JS> > mutt:
JS> > Subject: Test Subject with =?iso-8859-15?Q?W=F6rter?=
JS> > =?iso-8859-15?B?IKR1cm8gomVudCClZW4g5CD2IPw=?=
Regards,
Nerijus
P.S. BTW, why only you put your text ABOVE quoted, when netiquette suggests
(and almost everybody else seems to do) otherwise?
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]