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

[guenther <guenther rudersport de>]

> Why can't Evolution simply send out messages specifying that charset in
> the message header which the user selects in the Character Encoding
> menu? Why should Evolution's designers concern themselves with
> non-8859-15 capable mailers? (Is this some kind of American plot to keep
> the Euro from becoming an international reserve currency to compete with
> the dollar? ;))

Uh, in fact I can tell, ximian hackers are _way_ more open minded to
non-US than the average American. And I believe, that applys to all OS
folks out there...


> Evolution's second-guessing the user as to which character set to use
> becomes more problematic under the following scenario. [...]

Sorry, I can't say more on that topic, as I was testing in my previous
mail. It just works for me -- as I don't use non-roman characters, of
course. I can't write in cyrillic... ;-)

Maybe some developers can shed some light on this.

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