<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Why you should be using HTML powered E-mails</title>
	<atom:link href="http://www.robinjamesyu.com/blog/2009/08/18/why-should-using-html-powered-e-mails/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.robinjamesyu.com/blog/2009/08/18/why-should-using-html-powered-e-mails/</link>
	<description>A Blog about Design on any medium, Web development and life in general.</description>
	<lastBuildDate>Thu, 12 Jan 2012 02:47:46 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dude</title>
		<link>http://www.robinjamesyu.com/blog/2009/08/18/why-should-using-html-powered-e-mails/comment-page-1/#comment-551</link>
		<dc:creator>dude</dc:creator>
		<pubDate>Tue, 23 Mar 2010 04:35:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.robinjamesyu.com/?p=85#comment-551</guid>
		<description>很好很强大</description>
		<content:encoded><![CDATA[<p>很好很强大</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Writing HTML powered E-mails › Robin James Yu: Design &#38; Development</title>
		<link>http://www.robinjamesyu.com/blog/2009/08/18/why-should-using-html-powered-e-mails/comment-page-1/#comment-24</link>
		<dc:creator>Writing HTML powered E-mails › Robin James Yu: Design &#38; Development</dc:creator>
		<pubDate>Tue, 25 Aug 2009 17:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.robinjamesyu.com/?p=85#comment-24</guid>
		<description>[...] already talked about two things that make HTML powered E-mails essential to businesses and freelancers alike. Today, I&#8217;m going to discuss actually diving in and [...]</description>
		<content:encoded><![CDATA[<p>[...] already talked about two things that make HTML powered E-mails essential to businesses and freelancers alike. Today, I&#8217;m going to discuss actually diving in and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rj</title>
		<link>http://www.robinjamesyu.com/blog/2009/08/18/why-should-using-html-powered-e-mails/comment-page-1/#comment-23</link>
		<dc:creator>Rj</dc:creator>
		<pubDate>Tue, 18 Aug 2009 10:00:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.robinjamesyu.com/?p=85#comment-23</guid>
		<description>Yep good point Loki. You are very correct that plain e-mails are absolutely essential before you even think of making an HTML one due to the uncertainty of the destination user&#039;s client, I&#039;ll discuss that in the next article and how easy it is to do this. 

I also agree that sometimes HTML e-mails are overdone and it hurts the user more than help them. But I believe a carefully crafted HTML e-mail can boost readability, usability and present intent as I tried to show above. Again, it must not be overdone lest the benefits outweigh the costs. :)</description>
		<content:encoded><![CDATA[<p>Yep good point Loki. You are very correct that plain e-mails are absolutely essential before you even think of making an HTML one due to the uncertainty of the destination user&#8217;s client, I&#8217;ll discuss that in the next article and how easy it is to do this. </p>
<p>I also agree that sometimes HTML e-mails are overdone and it hurts the user more than help them. But I believe a carefully crafted HTML e-mail can boost readability, usability and present intent as I tried to show above. Again, it must not be overdone lest the benefits outweigh the costs. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loki</title>
		<link>http://www.robinjamesyu.com/blog/2009/08/18/why-should-using-html-powered-e-mails/comment-page-1/#comment-22</link>
		<dc:creator>Loki</dc:creator>
		<pubDate>Tue, 18 Aug 2009 09:28:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.robinjamesyu.com/?p=85#comment-22</guid>
		<description>Emails in HTML are nice but sometimes viewing them on a mobile device or plain-text client can be troublesome. 

I think it&#039;s best to at least have a plain-text email, and if you want, complement it with an HTML version. This way, non-HTML enabled clients have something to read aside from HTML code.

If not, there&#039;s always the option for people to choose whether or not they like their email in HTML.

--

Sometimes, there are times when there are just too much HTML involved that it&#039;s difficult to for the recipients to reply to or forward emails because of formatting. This is precisely the reason why I personally prefer traditional emails over their &quot;enhanced&quot; version [I think both are HTML, but the latter is formatted with two columns.].

I guess what I&#039;m saying that it&#039;s also important to factor in the the end-user/recipient -- so overall, it would be readability, usability and the intent of the email.</description>
		<content:encoded><![CDATA[<p>Emails in HTML are nice but sometimes viewing them on a mobile device or plain-text client can be troublesome. </p>
<p>I think it&#8217;s best to at least have a plain-text email, and if you want, complement it with an HTML version. This way, non-HTML enabled clients have something to read aside from HTML code.</p>
<p>If not, there&#8217;s always the option for people to choose whether or not they like their email in HTML.</p>
<p>&#8211;</p>
<p>Sometimes, there are times when there are just too much HTML involved that it&#8217;s difficult to for the recipients to reply to or forward emails because of formatting. This is precisely the reason why I personally prefer traditional emails over their &#8220;enhanced&#8221; version [I think both are HTML, but the latter is formatted with two columns.].</p>
<p>I guess what I&#8217;m saying that it&#8217;s also important to factor in the the end-user/recipient &#8212; so overall, it would be readability, usability and the intent of the email.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

