<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: HTML Mail Revisted</title>
	<atom:link href="http://freepressblog.org/blog/2007/11/29/html-mail-revisted/feed/" rel="self" type="application/rss+xml" />
	<link>http://freepressblog.org/blog/2007/11/29/html-mail-revisted/</link>
	<description>I was syncing my Facebook status here for a while, but now I'm boycotting them over the FriendConnect fiasco...</description>
	<pubDate>Thu, 21 Aug 2008 23:53:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: JB</title>
		<link>http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15804</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Sun, 02 Dec 2007 18:36:53 +0000</pubDate>
		<guid isPermaLink="false">http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15804</guid>
		<description>Yeah, I understand that some people will still insist on sending HTML in e-mail, and for those people, this project is a perfect approach to the issue. We might as well work towards the mail clients supporting standards based HTML if they're going to support HTML at all.

For me, I'd just rather see HTML remain in web pages rendered by the browser, since we've already made so much progress on that front. A text only mail with a single hyperlink is a lot classier to me than HTML embedded in the e-mail itself.

I generally agree with &lt;a href="http://www.zeldman.com/2007/06/08/e-mail-is-not-a-platform-for-design/" rel="nofollow"&gt;Jeffrey's points in his earlier anti-HTML post&lt;/a&gt; (as well as some of the comments there by people like Eric Meyer), and I don't see any reason why those points are not still valid today. </description>
		<content:encoded><![CDATA[<p>Yeah, I understand that some people will still insist on sending HTML in e-mail, and for those people, this project is a perfect approach to the issue. We might as well work towards the mail clients supporting standards based HTML if they&#8217;re going to support HTML at all.</p>
<p>For me, I&#8217;d just rather see HTML remain in web pages rendered by the browser, since we&#8217;ve already made so much progress on that front. A text only mail with a single hyperlink is a lot classier to me than HTML embedded in the e-mail itself.</p>
<p>I generally agree with <a href="http://www.zeldman.com/2007/06/08/e-mail-is-not-a-platform-for-design/" rel="nofollow">Jeffrey&#8217;s points in his earlier anti-HTML post</a> (as well as some of the comments there by people like Eric Meyer), and I don&#8217;t see any reason why those points are not still valid today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mathew Patterson</title>
		<link>http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15767</link>
		<dc:creator>Mathew Patterson</dc:creator>
		<pubDate>Sun, 02 Dec 2007 05:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15767</guid>
		<description>Thanks for the post JB. While we can certainly appreciate your personal opinion on HTML email, that same marketing department is going to send HTML whether designers agree or not - it's not going away.

We just want to work to make sure the HTML they send is lightweight, compliant and accessible.

Sending text+html means that for you, who prefers text, you never even see the HTML so it has no problems at all, apart from the additional (minor) use of bandwidth.</description>
		<content:encoded><![CDATA[<p>Thanks for the post JB. While we can certainly appreciate your personal opinion on HTML email, that same marketing department is going to send HTML whether designers agree or not - it&#8217;s not going away.</p>
<p>We just want to work to make sure the HTML they send is lightweight, compliant and accessible.</p>
<p>Sending text+html means that for you, who prefers text, you never even see the HTML so it has no problems at all, apart from the additional (minor) use of bandwidth.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JB</title>
		<link>http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15732</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Sat, 01 Dec 2007 19:45:18 +0000</pubDate>
		<guid isPermaLink="false">http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15732</guid>
		<description>Maybe I can explain it better: 

The problems I have with HTML mail are mostly related to the issues that e-mail clients have with HTML that usually result in really ugly HTML being written to work around them. And the fact that e-mail was never originally intended to support HTML and I believe it would be better to use things that were (such as web pages), if you want to send HTML.

Adding plain text to that doesn't really help at all, other than to give people who are using text only readers an easier way to read the message. Sure, it's a little better than HTML only, but to me it still has most of the same problems.</description>
		<content:encoded><![CDATA[<p>Maybe I can explain it better: </p>
<p>The problems I have with HTML mail are mostly related to the issues that e-mail clients have with HTML that usually result in really ugly HTML being written to work around them. And the fact that e-mail was never originally intended to support HTML and I believe it would be better to use things that were (such as web pages), if you want to send HTML.</p>
<p>Adding plain text to that doesn&#8217;t really help at all, other than to give people who are using text only readers an easier way to read the message. Sure, it&#8217;s a little better than HTML only, but to me it still has most of the same problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15699</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sat, 01 Dec 2007 07:33:42 +0000</pubDate>
		<guid isPermaLink="false">http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15699</guid>
		<description>Sorry but that makes no sense.</description>
		<content:encoded><![CDATA[<p>Sorry but that makes no sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JB</title>
		<link>http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15697</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Sat, 01 Dec 2007 05:54:23 +0000</pubDate>
		<guid isPermaLink="false">http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15697</guid>
		<description>The problems associated with sending both are most of the problems that you have with sending HTML by itself (inconsistent formatting and/or ugly markup in order to try and achieve consistency). That's my main objection: sending HTML at all in the message.

Trying to make it easier on plain text only users by also including the plain text along with the HTML doesn't go very far (in my book), because it's all still there. It's definitely better than nothing, but it still doesn't look good in a text only reader.</description>
		<content:encoded><![CDATA[<p>The problems associated with sending both are most of the problems that you have with sending HTML by itself (inconsistent formatting and/or ugly markup in order to try and achieve consistency). That&#8217;s my main objection: sending HTML at all in the message.</p>
<p>Trying to make it easier on plain text only users by also including the plain text along with the HTML doesn&#8217;t go very far (in my book), because it&#8217;s all still there. It&#8217;s definitely better than nothing, but it still doesn&#8217;t look good in a text only reader.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Cameron</title>
		<link>http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15695</link>
		<dc:creator>Dan Cameron</dc:creator>
		<pubDate>Sat, 01 Dec 2007 05:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15695</guid>
		<description>Plain text is plain text. It is wasted bandwidth but how can it have problems, since that's what you're saying you prefer anyways?</description>
		<content:encoded><![CDATA[<p>Plain text is plain text. It is wasted bandwidth but how can it have problems, since that&#8217;s what you&#8217;re saying you prefer anyways?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JB</title>
		<link>http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15619</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Fri, 30 Nov 2007 06:31:34 +0000</pubDate>
		<guid isPermaLink="false">http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15619</guid>
		<description>Personally, I really don't like that option; just a bunch of wasted space with most of the same problems associated with HTML mail.</description>
		<content:encoded><![CDATA[<p>Personally, I really don&#8217;t like that option; just a bunch of wasted space with most of the same problems associated with HTML mail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15617</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Fri, 30 Nov 2007 05:57:47 +0000</pubDate>
		<guid isPermaLink="false">http://freepressblog.org/blog/2007/11/29/html-mail-revisted/#comment-15617</guid>
		<description>Or just use HTML and plain text.</description>
		<content:encoded><![CDATA[<p>Or just use HTML and plain text.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
