<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: FIPP Site Redux: Goodbye HTML Tables Hello XHTML/CSS</title>
	<atom:link href="http://cogdogblog.com/2003/11/26/fipp-site/feed/" rel="self" type="application/rss+xml" />
	<link>http://cogdogblog.com/2003/11/26/fipp-site/</link>
	<description>Alan Levine&#039;s space for barking about and playing with technology</description>
	<lastBuildDate>Mon, 13 Feb 2012 07:01:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Richard Saling</title>
		<link>http://cogdogblog.com/2003/11/26/fipp-site/comment-page-1/#comment-284</link>
		<dc:creator>Richard Saling</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2003/11/26/fipp-site-redux-goodbye-html-tables-hello-xhtmlcss/#comment-284</guid>
		<description>Absolutely dead on!  Since I found how useful css is for layout a few years ago, I was a convert.  I am now exstatic about finally getting rid of tables forever except what they were intended for: tabular data.  As an educational institution it is our foremost responsibility to educate people and give them skills to work in the 21st century and beyond, yet we still hold on to the backward notion of backward compatibility.  We need to lift people up, and enlighten them, not hold them back and keep them in the dark.  I now creating a forward compatible and accessible website for my department which should be launched in the spring.  Visitors will need to use a web standards compliant browser to view the pages.

Here is an article I found on ala that is very usefull in freeing the minds of those chained to obsolescence: &lt;a href=&quot;http://www.alistapart.com/articles/tohell/&quot;&gt;http://www.alistapart.com/articles/tohell/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Absolutely dead on!  Since I found how useful css is for layout a few years ago, I was a convert.  I am now exstatic about finally getting rid of tables forever except what they were intended for: tabular data.  As an educational institution it is our foremost responsibility to educate people and give them skills to work in the 21st century and beyond, yet we still hold on to the backward notion of backward compatibility.  We need to lift people up, and enlighten them, not hold them back and keep them in the dark.  I now creating a forward compatible and accessible website for my department which should be launched in the spring.  Visitors will need to use a web standards compliant browser to view the pages.</p>
<p>Here is an article I found on ala that is very usefull in freeing the minds of those chained to obsolescence: <a href="http://www.alistapart.com/articles/tohell/">http://www.alistapart.com/articles/tohell/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Levine</title>
		<link>http://cogdogblog.com/2003/11/26/fipp-site/comment-page-1/#comment-285</link>
		<dc:creator>Alan Levine</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2003/11/26/fipp-site-redux-goodbye-html-tables-hello-xhtmlcss/#comment-285</guid>
		<description>Yes, Zeldman is dah man for hammering the WebStandards hard, and ALA is a must-read. 



You will face, however, the chorus that says,&quot; There are those who are economically bound to use old technology.&quot; I do not adovcation designing for the less than 1% who use old technology, but it is worth doing what you can to at least provide them some of the content.



By using a mix of linked CSS and @import you can effectively segregate formatting for old and new. It is not easy.



And everything is not the golden grail out there. You will find huge inconsitencies between browsers and versions even with CSS support (IE 5.5, IE 6.0, Opera) and a growing bag of CSS hacks that make things convoluted (Tantek box stuff).



I&#039;ve been watching the browser stats lately on this box- I have about 2% NetScape 4, sometimes a few tiny hits of even NS3 and IE3/4, but even new browsers pass NS4- Firebird (1.4%), Mozilla (2.3%), Safair (3.5%).



The war is pretty much over-

&lt;a href=&quot;http://www.webstandards.org/act/campaign/buc/&quot;&gt;http://www.webstandards.org/act/campaign/buc/&lt;/a&gt;
</description>
		<content:encoded><![CDATA[<p>Yes, Zeldman is dah man for hammering the WebStandards hard, and ALA is a must-read. </p>
<p>You will face, however, the chorus that says,&#8221; There are those who are economically bound to use old technology.&#8221; I do not adovcation designing for the less than 1% who use old technology, but it is worth doing what you can to at least provide them some of the content.</p>
<p>By using a mix of linked CSS and @import you can effectively segregate formatting for old and new. It is not easy.</p>
<p>And everything is not the golden grail out there. You will find huge inconsitencies between browsers and versions even with CSS support (IE 5.5, IE 6.0, Opera) and a growing bag of CSS hacks that make things convoluted (Tantek box stuff).</p>
<p>I&#8217;ve been watching the browser stats lately on this box- I have about 2% NetScape 4, sometimes a few tiny hits of even NS3 and IE3/4, but even new browsers pass NS4- Firebird (1.4%), Mozilla (2.3%), Safair (3.5%).</p>
<p>The war is pretty much over-</p>
<p><a href="http://www.webstandards.org/act/campaign/buc/">http://www.webstandards.org/act/campaign/buc/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

