<?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: Email Client Comparisons</title>
	<atom:link href="http://architexture.ca/wp/2010/01/email-client-comparisons/feed/" rel="self" type="application/rss+xml" />
	<link>http://architexture.ca/wp/2010/01/email-client-comparisons/</link>
	<description>The Land of Milk and Honey</description>
	<lastBuildDate>Thu, 09 Sep 2010 03:28:16 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Jamie</title>
		<link>http://architexture.ca/wp/2010/01/email-client-comparisons/comment-page-1/#comment-730</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Wed, 13 Jan 2010 19:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://architexture.ca/wp/?p=416#comment-730</guid>
		<description>Good video by Mathew Patterson – Delivering user experience to the inbox: designing for email. A presentation given at at Web Directions User Experience, Melbourne Town Hall, May 16 2008.

http://www.webdirections.org/resources/mathew-patterson/</description>
		<content:encoded><![CDATA[<p>Good video by Mathew Patterson – Delivering user experience to the inbox: designing for email. A presentation given at at Web Directions User Experience, Melbourne Town Hall, May 16 2008.</p>
<p><a href="http://www.webdirections.org/resources/mathew-patterson/" rel="nofollow">http://www.webdirections.org/resources/mathew-patterson/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://architexture.ca/wp/2010/01/email-client-comparisons/comment-page-1/#comment-729</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Sun, 10 Jan 2010 23:29:39 +0000</pubDate>
		<guid isPermaLink="false">http://architexture.ca/wp/?p=416#comment-729</guid>
		<description>I came across a Facebook group &quot;Lotus Notes Sucks&quot;. Pretty funny!

http://www.facebook.com/group.php?gid=2236028379

My workflow would be to try and keep the HTML and CSS as lean and simple as possible. My newsletter designs are fairly straight forward and tend to stick to a relatively simple grid to avoid needing extra code. 

The campaign monitor site says it well &quot;Designing an HTML email that renders consistently across the major email clients can be very time consuming. Support for even simple CSS varies considerably between clients, and even different versions of the same client.&quot;

Campaign Monitor also offers a CSS cheatsheet to help reduce further problems and save time (I&#039;m sure you know). http://www.campaignmonitor.com/css 

Once the designs are coded I generally test them on various browsers and email clients. When I feel confident I&#039;ll either send it or if its a more complex design I&#039;ll run a Campaign Monitor design test for $5. The tests can really speed up the process and ensure quality delivery.

However as with all things online there is still lots to learn. As the industry starts to adopt better and more consistent standards it will make our job easier but it&#039;s not going to happen overnight.

How about yourself? Do you have testing preferences?</description>
		<content:encoded><![CDATA[<p>I came across a Facebook group &#8220;Lotus Notes Sucks&#8221;. Pretty funny!</p>
<p><a href="http://www.facebook.com/group.php?gid=2236028379" rel="nofollow">http://www.facebook.com/group.php?gid=2236028379</a></p>
<p>My workflow would be to try and keep the HTML and CSS as lean and simple as possible. My newsletter designs are fairly straight forward and tend to stick to a relatively simple grid to avoid needing extra code. </p>
<p>The campaign monitor site says it well &#8220;Designing an HTML email that renders consistently across the major email clients can be very time consuming. Support for even simple CSS varies considerably between clients, and even different versions of the same client.&#8221;</p>
<p>Campaign Monitor also offers a CSS cheatsheet to help reduce further problems and save time (I&#8217;m sure you know). <a href="http://www.campaignmonitor.com/css" rel="nofollow">http://www.campaignmonitor.com/css</a> </p>
<p>Once the designs are coded I generally test them on various browsers and email clients. When I feel confident I&#8217;ll either send it or if its a more complex design I&#8217;ll run a Campaign Monitor design test for $5. The tests can really speed up the process and ensure quality delivery.</p>
<p>However as with all things online there is still lots to learn. As the industry starts to adopt better and more consistent standards it will make our job easier but it&#8217;s not going to happen overnight.</p>
<p>How about yourself? Do you have testing preferences?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://architexture.ca/wp/2010/01/email-client-comparisons/comment-page-1/#comment-728</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sun, 10 Jan 2010 08:26:42 +0000</pubDate>
		<guid isPermaLink="false">http://architexture.ca/wp/?p=416#comment-728</guid>
		<description>That 4% share of Lotus Notes is scary stuff.  Nothing mangles HTML quite like IBM software; they make Microsoft look standards compliant.

With these disparate results, what&#039;s your testing workflow?</description>
		<content:encoded><![CDATA[<p>That 4% share of Lotus Notes is scary stuff.  Nothing mangles HTML quite like IBM software; they make Microsoft look standards compliant.</p>
<p>With these disparate results, what&#8217;s your testing workflow?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
