<?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: Where web standards are at.</title>
	<atom:link href="http://twoseven.co.nz/2007/02/28/where-web-standards-are-at/feed/" rel="self" type="application/rss+xml" />
	<link>http://twoseven.co.nz/2007/02/28/where-web-standards-are-at/</link>
	<description>...is Dan Willis blogging about web design and development, usability, standards and pretty much anything!</description>
	<lastBuildDate>Tue, 31 May 2011 01:13:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2-bleeding</generator>
	<item>
		<title>By: Dan</title>
		<link>http://twoseven.co.nz/2007/02/28/where-web-standards-are-at/comment-page-1/#comment-4</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Thu, 01 Mar 2007 03:34:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.twoseven.co.nz/2007/02/28/where-web-standards-are-at/#comment-4</guid>
		<description>Hmm.

It&#039;s a different story if you&#039;re developing for other people - clients, readers, etc. - over whose browsers you have no control. You can&#039;t dump IE.

With a bit of experience, you become familiar with the quirks of the various browsers and can learn to design/develop around them.

Keeping it simple helps too. If you&#039;re trying to do something in particular but find the mark-up/CSS/work-arounds/hacks are getting too complicated or out of hand, then perhaps the design should be re-worked to enable simpler coding.</description>
		<content:encoded><![CDATA[<p>Hmm.</p>
<p>It&#8217;s a different story if you&#8217;re developing for other people &#8211; clients, readers, etc. &#8211; over whose browsers you have no control. You can&#8217;t dump IE.</p>
<p>With a bit of experience, you become familiar with the quirks of the various browsers and can learn to design/develop around them.</p>
<p>Keeping it simple helps too. If you&#8217;re trying to do something in particular but find the mark-up/CSS/work-arounds/hacks are getting too complicated or out of hand, then perhaps the design should be re-worked to enable simpler coding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allan</title>
		<link>http://twoseven.co.nz/2007/02/28/where-web-standards-are-at/comment-page-1/#comment-3</link>
		<dc:creator>Allan</dc:creator>
		<pubDate>Thu, 01 Mar 2007 03:24:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.twoseven.co.nz/2007/02/28/where-web-standards-are-at/#comment-3</guid>
		<description>When I was starting to learn html I figured I&#039;d learn standards. Reason: I wanted it to work.

Then there was IE. Which I promptly dumped. And as you saw with my blog the other day I don&#039;t care to test with it. I&#039;m not a professional web designer. I know enough to do what I want only.
And I don&#039;t want IE.

I try to use standards, but as we know, it&#039;s not always possible. I&#039;m not strict to the point of dumping other people&#039;s code (haloscan) if it breaks the validation.</description>
		<content:encoded><![CDATA[<p>When I was starting to learn html I figured I&#8217;d learn standards. Reason: I wanted it to work.</p>
<p>Then there was IE. Which I promptly dumped. And as you saw with my blog the other day I don&#8217;t care to test with it. I&#8217;m not a professional web designer. I know enough to do what I want only.<br />
And I don&#8217;t want IE.</p>
<p>I try to use standards, but as we know, it&#8217;s not always possible. I&#8217;m not strict to the point of dumping other people&#8217;s code (haloscan) if it breaks the validation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

