<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Web Design for Developers &#187; Cross-Browser Compatibility</title>
	<atom:link href="http://www.webdesignfordevelopers.com/category/cross-browser-compatibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webdesignfordevelopers.com</link>
	<description>A Programmer's Guide to Design Tools and Techniques</description>
	<lastBuildDate>Mon, 14 Mar 2011 13:58:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Why I chose HTML4 over XHTML Strict</title>
		<link>http://www.webdesignfordevelopers.com/2010/01/06/why-i-chose-html4-over-xhtml-strict/</link>
		<comments>http://www.webdesignfordevelopers.com/2010/01/06/why-i-chose-html4-over-xhtml-strict/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 02:32:11 +0000</pubDate>
		<dc:creator>Brian Hogan</dc:creator>
				<category><![CDATA[Cross-Browser Compatibility]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.webdesignfordevelopers.com/?p=81</guid>
		<description><![CDATA[One thing that may surprise readers of the book is my choice to use HTML4 Strict for the markup in the book. That may seem strange given that the last decade has been devoted towards pushing &#8220;web standards with XHTML.&#8221; After all, experts like Jeffrey Zeldman can&#8217;t be wrong, can they? Of course not. At [...]]]></description>
		<wfw:commentRss>http://www.webdesignfordevelopers.com/2010/01/06/why-i-chose-html4-over-xhtml-strict/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>@font-face Generator</title>
		<link>http://www.webdesignfordevelopers.com/2009/12/02/font-face-generator/</link>
		<comments>http://www.webdesignfordevelopers.com/2009/12/02/font-face-generator/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 14:38:53 +0000</pubDate>
		<dc:creator>Brian Hogan</dc:creator>
				<category><![CDATA[Cross-Browser Compatibility]]></category>
		<category><![CDATA[Typography]]></category>

		<guid isPermaLink="false">http://www.webdesignfordevelopers.com/?p=70</guid>
		<description><![CDATA[More and more browsers are able to handle embedded fonts, but getting the right formats for each browser can be tricky. For example, Internet Explorer requires a proprietary format called EOT, or &#8220;Embedded OpenType&#8221;, but getting fonts in that format isn&#8217;t easy and Microsoft&#8217;s tools don&#8217;t seem to work all that well for some people. [...]]]></description>
		<wfw:commentRss>http://www.webdesignfordevelopers.com/2009/12/02/font-face-generator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Know Your IE CSS</title>
		<link>http://www.webdesignfordevelopers.com/2009/10/14/know-your-ie-css/</link>
		<comments>http://www.webdesignfordevelopers.com/2009/10/14/know-your-ie-css/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 15:28:46 +0000</pubDate>
		<dc:creator>Brian Hogan</dc:creator>
				<category><![CDATA[Cross-Browser Compatibility]]></category>
		<category><![CDATA[CSS]]></category>

		<guid isPermaLink="false">http://www.webdesignfordevelopers.com/2009/10/14/know-your-ie-css/</guid>
		<description><![CDATA[Smashing Magazine has a great article that shows you which standard CSS selectors will and will not work on IE 6, 7, and 8. It doesn&#8217;t show workarounds, but it&#8217;s a very handy cheat sheet if you can&#8217;t remember them all. CSS Differences in Internet Explorer 6, 7 and 8]]></description>
		<wfw:commentRss>http://www.webdesignfordevelopers.com/2009/10/14/know-your-ie-css/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

