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

[guenther <guenther rudersport de>]

> The fact that users ever have to know about character encodings is a
> bug.

LOL -- I do agree with that. Is there already filed a bug? ;-)


> The menu exists because things don't
> always work that nicely in the real world, but it's only there as a
> hint. "*IF* you can send this message in iso-8859-15, then please do so,
> rather than using iso-8859-1". But if the message can't be encoded in
> 8859-15, there's absolutely no reason why Evolution would want to try,
> since that can't possibly do the right thing.

Nope, than at least that part is broken (no harm done, though).

In both, Mail Preferences/General and Composer Preferences/General my
default character set is set to ISO-8859-15.

So I am begging Evo on my knees to send it as ISO-8859-15. However, Evo
does not answer my prayers -- and the test mail got sent as
 Content-Type: text/plain
 Content-Transfer-Encoding: 7bit

So what is wrong with my usual signature and the string "wird gesendet
als 8859-1 ?\n\n", that it _must_ be 7 bit and does _not_ fit into 8
bit? ;-))

...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; }}}