Re: [Evolution] Character set wrong in Composer

[Patrick O'Callaghan <poc usb ve>]

Sorry, I don't know what happened there; maybe a keybounce.

poc

On Wed, 2003-10-29 at 22:06 +0100, guenther wrote:
> Resending does not force faster or more responses. ;-)
>
>
> > I have my options set to use ISO-8859-1 for composing, and
> > it works fine: 
> >
> > However if I Reply to a non-ASCII message the quoted text
> > loses all accented characters (e.g. "da" appears as "da").
> > This didn't used to happen with Evo 1.4.5 but now I'm using
> > the latest snapshot via Red Carpet.
> >
> > It doesn't seem to matter what character set I specify in the
> > Compose options.
> >
> > Any ideas?
>
> Sure. You are running 1.5...
>
> 1.5 is the current *development* version and broken thinks all over the
> place are to be expected. There even was a note by Ettore some days ago,
> that this code just got merged and therefore should be expected to have
> usability issues.
>
> If you want your work to get done, use 1.4.5 or maybe the latest
> snapshot:
>  ftp://ftp.ximian.com/pub/evolution-snapshot/
>
> Do use Evolution 1.5 only, if you wanna help squashing bugs and can
> effort living on the bleeding edge.
>
>
> I am not an Evolution hacker though, so I may be wrong. HTH
>
> ...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; }}}