Re: No subset for email

I'm inclined to agree. part of the problem is that the issue has been cast in the wrong terms. Instead of looking for a subset (focusing on the technical solution) that will solve the problem, shouldn't we start out by trying to clearly state what it is we are trying to do? As an aside, are we really so sure that the technical solution is going to be a subset? I would rather expect that a solution for e-mail will include some features not needed in standard HTML, and omit other features that are not really needed mail. That being said, I think it's very important to avoid developing a solution that users will find inferior to the capabilities offered by e-mail. Anything that feels watered down is likely to be rejected.
 
===
Gregory Woodhouse <gregory.woodhouse@sbcglobal.net>

"Mathematics is the science of patterns."
--Lynn Arthur Steen, 1988



----- Original Message ----
From: Pierre Saslawsky <pierre@photobiker.com>
To: public-html-mail@w3.org
Sent: Tuesday, March 13, 2007 12:58:03 PM
Subject: Re: No subset for email



Scoped stylesheets would not address the most pressing issues:
- When composing a reply, they are of no help to identify the user- 
generated content within its template in order to extract what will  
become the quoted content.
- Their main use, as I see it, would be the preservation of the  
quoted content's style. Even though it might be appealing in some  
situations, it still is the least desirable case (with the exception  
of some minor attributes maybe, such as font weight or text decoration).

Pierre