<?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: Use Your Words, Darling</title>
	<atom:link href="http://www.newslettersinfocus.com/33/feed" rel="self" type="application/rss+xml" />
	<link>http://www.newslettersinfocus.com/33</link>
	<description>Free advice for professionals on newsletter design and how to write a newsletter.</description>
	<lastBuildDate>Wed, 29 Aug 2007 11:31:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Jessica</title>
		<link>http://www.newslettersinfocus.com/33#comment-13</link>
		<dc:creator>Jessica</dc:creator>
		<pubDate>Mon, 14 May 2007 17:58:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.newslettersinfocus.com/33#comment-13</guid>
		<description><![CDATA[There are a lot of email clients in use these days, Meryl--especially when you consider that they&#039;re often different on each platform. That creates a lot of options!

I agree that there&#039;s really no good reason not to have both an HTML and plain text version. Not only do they boost compatibility, but they&#039;re useful in other ways as well (especially with newsletter and article submissions). Plus, it&#039;s so easy to create both that it&#039;s really not a burden.

Thanks for sharing the link to the article. I thought you might also enjoy seeing this piece on the same subject that I wrote back in 2004:
http://www.designdoodles.com/article/50/

Again, thanks so much for weighing in!

All my best,

Jes]]></description>
		<content:encoded><![CDATA[<p>There are a lot of email clients in use these days, Meryl&#8211;especially when you consider that they&#8217;re often different on each platform. That creates a lot of options!</p>
<p>I agree that there&#8217;s really no good reason not to have both an HTML and plain text version. Not only do they boost compatibility, but they&#8217;re useful in other ways as well (especially with newsletter and article submissions). Plus, it&#8217;s so easy to create both that it&#8217;s really not a burden.</p>
<p>Thanks for sharing the link to the article. I thought you might also enjoy seeing this piece on the same subject that I wrote back in 2004:<br />
<a href="http://www.designdoodles.com/article/50/" rel="nofollow">http://www.designdoodles.com/article/50/</a></p>
<p>Again, thanks so much for weighing in!</p>
<p>All my best,</p>
<p>Jes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: meryl</title>
		<link>http://www.newslettersinfocus.com/33#comment-12</link>
		<dc:creator>meryl</dc:creator>
		<pubDate>Wed, 09 May 2007 17:03:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.newslettersinfocus.com/33#comment-12</guid>
		<description><![CDATA[And there are too many email clients in use today, one of which is the awful Lotus that likes to tear newsletters apart. If possible -- offer both HTML and text versions. If not -- I shoot for text since you&#039;re less likely to have problems.  Also posted this article last year covering this topic:

http://meryl.net/2006/10/31/designing-newsletters-for-all-email-kind-2/]]></description>
		<content:encoded><![CDATA[<p>And there are too many email clients in use today, one of which is the awful Lotus that likes to tear newsletters apart. If possible &#8212; offer both HTML and text versions. If not &#8212; I shoot for text since you&#8217;re less likely to have problems.  Also posted this article last year covering this topic:</p>
<p><a href="http://meryl.net/2006/10/31/designing-newsletters-for-all-email-kind-2/" rel="nofollow">http://meryl.net/2006/10/31/designing-newsletters-for-all-email-kind-2/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
