Re: mailto: with Body part broken (was: Re: [Evolution] Three small questions about Evolution)

[guenther <guenther rudersport de>]

> > I never used this before, so I just had a look. You are right, this link
> > is on a line with Preformat style, which probably is a good idea for
> > this line. Anyway, that's about it where the behavior is good. Anything
> > else is broken.
> >
> > a) There is only this line. There should be at least one other line
> > below the link where the use can enter some more text. This line should
> > be Normal by default.
>
> Right.
>
> > b) There is no signature. Even though the Signature dropdown shows my
> > default accounts signature name, there is none. Which is a bug.
>
> Almost never use signatures so I hadn't noticed this.
>
> > Specifically, this is a bug in the mailto: behavior of Evo. Apparently
> > Firefox calls the default MUA with the common parameters, in this case
> >
> >   mailto:?Body=<link>
> >
> > Providing the Body part results in the broken behavior.
>
> I can't say that Evo's behaviour is strictly wrong, since all it's doing
> is what Firefox is telling it, i.e. create a message with a given Body.
> The Evo developers could argue that adding an extra line in Normal
> format is exceeding the spec.

It would be nothing more than adding a newline at the end of the given
Body string.

> It's what I want in this case, but is it
> always what I want? Neither can we ask Firefox to know about Evo's
> formatting features.

True.

> One solution would be an extra Evo command line option to allow callers
> to ask for strict/nonstrict inclusion of the body text.

Don't think this will work, since mailto: is some kind of a standard,
implemented by Browsers and MUAs all over the place.

What's definitely a bug is b), though...

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