<?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: Introducing sIFR</title>
	<atom:link href="http://nate.koechley.com/blog/2004/09/10/introducing-sifr/feed/" rel="self" type="application/rss+xml" />
	<link>http://nate.koechley.com/blog/2004/09/10/introducing-sifr/</link>
	<description>Web professional with deep frontend engineering expertise skilled in user experience design and product strategy. Successful team leader, manager, and executive. Sought-after speaker, writer, and trainer.</description>
	<lastBuildDate>Mon, 24 May 2010 15:52:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike D.</title>
		<link>http://nate.koechley.com/blog/2004/09/10/introducing-sifr/comment-page-1/#comment-48</link>
		<dc:creator>Mike D.</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://nate.koechley.com/blog/?p=159#comment-48</guid>
		<description>Ah, but Nate!  The Flash text is invisible in the code and visible on the screen, while the browser text is visible in the code and invisible on the screen.  Hence, it looks exactly the same to search engines.

By the way, yes, I agree that this technique should be mainly used for display type (e.g. headlines) and not body copy.  One line of nice display type can really set a page off nicely and this is what the technique is designed for.</description>
		<content:encoded><![CDATA[<p>Ah, but Nate!  The Flash text is invisible in the code and visible on the screen, while the browser text is visible in the code and invisible on the screen.  Hence, it looks exactly the same to search engines.</p>
<p>By the way, yes, I agree that this technique should be mainly used for display type (e.g. headlines) and not body copy.  One line of nice display type can really set a page off nicely and this is what the technique is designed for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Koechley</title>
		<link>http://nate.koechley.com/blog/2004/09/10/introducing-sifr/comment-page-1/#comment-49</link>
		<dc:creator>Nate Koechley</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://nate.koechley.com/blog/?p=159#comment-49</guid>
		<description>Thanks for the comment Mike. I admit I didn&#039;t look at the guts much before writing my thoughts -- glad to know the text is still there for the engines to gobble up. 

I agree that beautiful typography can contribute immensely to a great design, and I believe this is one of the best -- if not *the* best -- image replacement techniques I&#039;m aware of.

Cheers,
nate



</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Mike. I admit I didn&#8217;t look at the guts much before writing my thoughts &#8212; glad to know the text is still there for the engines to gobble up. </p>
<p>I agree that beautiful typography can contribute immensely to a great design, and I believe this is one of the best &#8212; if not *the* best &#8212; image replacement techniques I&#8217;m aware of.</p>
<p>Cheers,<br />
nate</p>
]]></content:encoded>
	</item>
</channel>
</rss>

