Re: [Evolution] Character encoding specified in Content-Type field of outgoing messages

[guenther <guenther rudersport de>]

On Sun, 2003-04-06 at 01:49, Alex Viskovatoff wrote:
> I have not seen this problem discussed on the list. I am using Evolution
> 1.2.4.
>
> When composing a message, specifying a character encoding other than
> "Western European (ISO-8859-1)" seems to have no effect on the MIME
> field "Content Type" that is included in the message that is sent. No
> matter what character encoding one specifies (I have tried ISO-8859-15
> (my default) and KOI8-R), the "Content Type" field remains
>
>   text/plain; charset=ISO-8859-1
>
> I am surprised no one has brought up this problem before. That would
> suggest that not many people use Evolution for languages other than
> English.

I just tested it and it seems, that Evo guesses what charset to use --
taking the smallest matching to avoid conflicts with not 8859-15 capable
mailers.
(Developers: Slap me, if I am wrong here.)

test mail / plain text:      Content-Type: text/plain
test mail / 'äöü €' string:  Content-Type: text/plain; charset=ISO-8859-15

8859-15 is my preferred charset. Works for me...

btw: If you see a _ there, you should change your font settings to
8859-15 too.

...guenther


-- 
char *t="\10pse\0r\0dtu\0  ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}