[Mailman-Developers] Feature Request - Interactive HTML Digests

[Tanstaafl]

On 2010-02-22 12:15 PM, Mark Sapiro wrote:
> What does encapsulation mean to you?

In the context of this discussion, a way of 'wrapping up' the individual
messages in such a way as to be able to be both manipulated by the html
code, and to control how they are displayed/presented.

> Thus, you are reduced to something like HTMLizing the current plain 
> text digest with links to all it's scrubbed attachments and HTML 
> parts. This would be acceptable for lists that accept plain text
> only, but I'm not sure it would work well for other lists.

Honestly, I'd be fine with this new HTML digest being limited to only
plain-text based lists, at least at least and until some python/html
guru came up with the code to make it work reasonably well for HTML
based lists too.

> As I have mentioned in other posts in this thread, the 'reply*'
> buttons are doable with mailto: links provided you don't want any
> special features like quoting selected text.
>
> The mailto: could include a body= fragment that was a quoting of the
> entire (plain text) message being replied to, but if you want to
> quote selected text, you'd have to select the text and then use the
> MUA's 'reply-list' button to generate the reply, but then you don't
> have the proper subject or the in-reply-to and references for
> threading. Anything else requires javascript behind the button.

Wow - I must have missed the significance of it when you said it... if
you are actually saying that grabbing the in-reply-to references would
be doable, then this would be more than enough to make me happy. :)

Grabbing the subject would be an even bigger bonus. ;)

But no, quoting selected text is a very distant second to the Reply
buttons, and something I'd be ok with never being implemented...

> Defaulting to keep the List-Post header in the MIME digest messages is
> easy enough. I can do that if no one comes up with a good reason why
> not. Barry mentioned List-Post for other lists/umbrellas, but
> CookHeaders already removes those.

Thanks a lot Mark, Stephen and Barry for taking the time to respond to
what must be - to you - a very ignorance-based discussion from my side.

-- 

Charles