<?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: 12 tips to help you build robust emails for all clients</title>
	<atom:link href="http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/</link>
	<description>Blog, What?</description>
	<pubDate>Wed, 10 Mar 2010 01:06:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Imran &#124; IT Buzz</title>
		<link>http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/#comment-766</link>
		<dc:creator>Imran &#124; IT Buzz</dc:creator>
		<pubDate>Sat, 05 Sep 2009 20:49:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfasani.com/?p=17#comment-766</guid>
		<description>Thanks for sharing these useful tips.</description>
		<content:encoded><![CDATA[<p>Thanks for sharing these useful tips.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dennis</title>
		<link>http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/#comment-763</link>
		<dc:creator>dennis</dc:creator>
		<pubDate>Wed, 22 Jul 2009 21:16:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfasani.com/?p=17#comment-763</guid>
		<description>@james: 

1) never use characters same color as background. people will be using screenreaders to consume their emails ... what then?

take a loo around what html-entities you could use instead. dont be shy, just leave a blank space between &#160; when this extra space is needed, no breaking will occure ;-)

2) ID-Property on Tables, like in the code example here, are often used for anchors linking Paragraphs (here Tables) for easy access by the user, ... in case you offer a content summary :-)

3) Font-Tags: See, any Client will have a "backward" compability, even for HTML 3. Of course we no longer want no tag soup. Please note: You dont need/have to use -Tags for Newsletters ... I never used them.

But for one reason they are great: think of a client (mobile device) that cant interpret CSS .... or simply people use their own CSS.

You can keep formating in this case by HTML not CSS. So you can, if urgentlx neccessary, bypass locked User-CSS :-)

In very rare cases this could be a fine opportunity.

4) Yes, Sadly coding for HTML-Newsletters is about forgetting any standard complience we have worked so hard for :-(

But hey, once M$ will drop their poor HTML-support foor Outlook 2007 with a new Version, we can go back to normal ... in 3 or 4 Years :-)

BTW: Hotmail/MS Live and Outlook 2007 have the very same rendering characteristics. Guess why? MS stated themselves they want to make no difference in appearence when people are using MS online-services or local applications.

It is absolutly and willingly decided by MS, that Hotmail has same poor render qualities likewise Outlook 2007...


sincere
dennis &#124; screenlabor.de</description>
		<content:encoded><![CDATA[<p>@james: </p>
<p>1) never use characters same color as background. people will be using screenreaders to consume their emails &#8230; what then?</p>
<p>take a loo around what html-entities you could use instead. dont be shy, just leave a blank space between &nbsp; when this extra space is needed, no breaking will occure <img src='http://blog.michaelfasani.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>2) ID-Property on Tables, like in the code example here, are often used for anchors linking Paragraphs (here Tables) for easy access by the user, &#8230; in case you offer a content summary <img src='http://blog.michaelfasani.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>3) Font-Tags: See, any Client will have a &#8220;backward&#8221; compability, even for HTML 3. Of course we no longer want no tag soup. Please note: You dont need/have to use -Tags for Newsletters &#8230; I never used them.</p>
<p>But for one reason they are great: think of a client (mobile device) that cant interpret CSS &#8230;. or simply people use their own CSS.</p>
<p>You can keep formating in this case by HTML not CSS. So you can, if urgentlx neccessary, bypass locked User-CSS <img src='http://blog.michaelfasani.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>In very rare cases this could be a fine opportunity.</p>
<p>4) Yes, Sadly coding for HTML-Newsletters is about forgetting any standard complience we have worked so hard for <img src='http://blog.michaelfasani.com/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
<p>But hey, once M$ will drop their poor HTML-support foor Outlook 2007 with a new Version, we can go back to normal &#8230; in 3 or 4 Years <img src='http://blog.michaelfasani.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>BTW: Hotmail/MS Live and Outlook 2007 have the very same rendering characteristics. Guess why? MS stated themselves they want to make no difference in appearence when people are using MS online-services or local applications.</p>
<p>It is absolutly and willingly decided by MS, that Hotmail has same poor render qualities likewise Outlook 2007&#8230;</p>
<p>sincere<br />
dennis | screenlabor.de</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tiago Pimentel</title>
		<link>http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/#comment-760</link>
		<dc:creator>Tiago Pimentel</dc:creator>
		<pubDate>Thu, 18 Jun 2009 19:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfasani.com/?p=17#comment-760</guid>
		<description>Hey, very useful post. Thanks!</description>
		<content:encoded><![CDATA[<p>Hey, very useful post. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ^^</title>
		<link>http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/#comment-757</link>
		<dc:creator>^^</dc:creator>
		<pubDate>Mon, 18 May 2009 11:59:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfasani.com/?p=17#comment-757</guid>
		<description>Man, I recognise that structure... and even the html comments, I think I even know all the people that came together and contributed to it :¬) nice to see you posted it to help others as it is nice, I know none of us ever had the time too... whoever those people may be ey? ;¬)</description>
		<content:encoded><![CDATA[<p>Man, I recognise that structure&#8230; and even the html comments, I think I even know all the people that came together and contributed to it :¬) nice to see you posted it to help others as it is nice, I know none of us ever had the time too&#8230; whoever those people may be ey? ;¬)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James W. Friedman</title>
		<link>http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/#comment-755</link>
		<dc:creator>James W. Friedman</dc:creator>
		<pubDate>Fri, 10 Apr 2009 08:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfasani.com/?p=17#comment-755</guid>
		<description>I observe that all structural properties, heights and such, are placed in structural elements, td's, and the font properties are placed in font elements.  From coding to XHTML 1.0 Strict my habit is to consider the font tag deprecated.  HTML emails are a different world entirely.  Do you wish to comment on the use of font elements?  Also, in your example you have used the id property for the tables.  How is the id property utilized in HTML emails? Same question for the title element. On websites I have created spaces by adding a character whose color is that of the background, this in place of using a non-breaking space.  Perhaps this technique can be used here too. Wonderful post - thank you so very much...</description>
		<content:encoded><![CDATA[<p>I observe that all structural properties, heights and such, are placed in structural elements, td&#8217;s, and the font properties are placed in font elements.  From coding to XHTML 1.0 Strict my habit is to consider the font tag deprecated.  HTML emails are a different world entirely.  Do you wish to comment on the use of font elements?  Also, in your example you have used the id property for the tables.  How is the id property utilized in HTML emails? Same question for the title element. On websites I have created spaces by adding a character whose color is that of the background, this in place of using a non-breaking space.  Perhaps this technique can be used here too. Wonderful post - thank you so very much&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlotte Coleman</title>
		<link>http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/#comment-754</link>
		<dc:creator>Charlotte Coleman</dc:creator>
		<pubDate>Mon, 23 Mar 2009 17:12:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfasani.com/?p=17#comment-754</guid>
		<description>So pleased you found that display: block fix - helped me no end.

Thanks!

Charlotte</description>
		<content:encoded><![CDATA[<p>So pleased you found that display: block fix - helped me no end.</p>
<p>Thanks!</p>
<p>Charlotte</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Almada</title>
		<link>http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/#comment-750</link>
		<dc:creator>Almada</dc:creator>
		<pubDate>Fri, 06 Feb 2009 13:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfasani.com/?p=17#comment-750</guid>
		<description>Love the advice. Thank you.</description>
		<content:encoded><![CDATA[<p>Love the advice. Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave P</title>
		<link>http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/#comment-747</link>
		<dc:creator>Dave P</dc:creator>
		<pubDate>Fri, 09 Jan 2009 22:30:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfasani.com/?p=17#comment-747</guid>
		<description>Cheers for that mate, loads of useful information.</description>
		<content:encoded><![CDATA[<p>Cheers for that mate, loads of useful information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EmailsAnnon</title>
		<link>http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/#comment-746</link>
		<dc:creator>EmailsAnnon</dc:creator>
		<pubDate>Tue, 06 Jan 2009 23:40:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfasani.com/?p=17#comment-746</guid>
		<description>Good summary. Re: Rule #8. I've found a need for &#160; to be contained within tds if the cell needs to have some sort of border applied in styling or horizontal width applied to it. The caveat is that you have to be careful what text-style is applied to that space. If you don't specify it is generally defaults to whatever the default is for that client. To which point you need to explicitly set the style for the text-size.

Of course table/cell borders are not always well supported across all clients.</description>
		<content:encoded><![CDATA[<p>Good summary. Re: Rule #8. I&#8217;ve found a need for &nbsp; to be contained within tds if the cell needs to have some sort of border applied in styling or horizontal width applied to it. The caveat is that you have to be careful what text-style is applied to that space. If you don&#8217;t specify it is generally defaults to whatever the default is for that client. To which point you need to explicitly set the style for the text-size.</p>
<p>Of course table/cell borders are not always well supported across all clients.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Fasani</title>
		<link>http://blog.michaelfasani.com/2008/07/12-tips-to-help-you-build-robust-emails/#comment-207</link>
		<dc:creator>Michael Fasani</dc:creator>
		<pubDate>Fri, 19 Sep 2008 09:40:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.michaelfasani.com/?p=17#comment-207</guid>
		<description>Hi Chinaman,

Yes this is my own findings from building many HTML emails for different clients over the last few years.

-M</description>
		<content:encoded><![CDATA[<p>Hi Chinaman,</p>
<p>Yes this is my own findings from building many HTML emails for different clients over the last few years.</p>
<p>-M</p>
]]></content:encoded>
	</item>
</channel>
</rss>
