<?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: How we built our GSA XSLT stylesheet with 100% external CSS</title>
	<atom:link href="http://webdogs.org/2008/10/27/how-we-built-our-gsa-xslt-stylesheet-with-100-external-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://webdogs.org/2008/10/27/how-we-built-our-gsa-xslt-stylesheet-with-100-external-css/</link>
	<description>site sentient since 2006</description>
	<lastBuildDate>Tue, 26 Apr 2011 20:57:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Brian Lawlor</title>
		<link>http://webdogs.org/2008/10/27/how-we-built-our-gsa-xslt-stylesheet-with-100-external-css/comment-page-1/#comment-19664</link>
		<dc:creator>Brian Lawlor</dc:creator>
		<pubDate>Wed, 12 Nov 2008 22:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.webdogs.org/findability/?p=266#comment-19664</guid>
		<description>Dan, point taken and totally on the mark about the need to enclose the xhtml in &lt;code&gt;xsl:text&lt;/code&gt; tags. But not to worry. At least with the current version 5.04 GSA, when you initially &quot;process&quot; the xhtml through the GSA page layout helper, as described at step 2, the GSA editor automatically adds those tags, exactly as you detail. But one needs to be careful to keep those tags in place when adding the so-called &quot;processed&quot; xhtml back in via the GSA stylesheet editor, as described at step 5.</description>
		<content:encoded><![CDATA[<p>Dan, point taken and totally on the mark about the need to enclose the xhtml in <code>xsl:text</code> tags. But not to worry. At least with the current version 5.04 GSA, when you initially &#8220;process&#8221; the xhtml through the GSA page layout helper, as described at step 2, the GSA editor automatically adds those tags, exactly as you detail. But one needs to be careful to keep those tags in place when adding the so-called &#8220;processed&#8221; xhtml back in via the GSA stylesheet editor, as described at step 5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://webdogs.org/2008/10/27/how-we-built-our-gsa-xslt-stylesheet-with-100-external-css/comment-page-1/#comment-19663</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Wed, 12 Nov 2008 19:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.webdogs.org/findability/?p=266#comment-19663</guid>
		<description>Actually I just verified, at line 244 and line 248, you will have to add:

 xsl:text disable-output-escaping=&quot;yes&quot;

/xsl:text

tags around your *processed* xhtml</description>
		<content:encoded><![CDATA[<p>Actually I just verified, at line 244 and line 248, you will have to add:</p>
<p> xsl:text disable-output-escaping=&#8221;yes&#8221;</p>
<p>/xsl:text</p>
<p>tags around your *processed* xhtml</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://webdogs.org/2008/10/27/how-we-built-our-gsa-xslt-stylesheet-with-100-external-css/comment-page-1/#comment-19662</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Wed, 12 Nov 2008 19:43:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.webdogs.org/findability/?p=266#comment-19662</guid>
		<description>Is there any reason why the processed (encoded) html actually displays instead of being parsed?

I reviewed our old frontend and it uses  to display the encoded html.

Am I missing something?</description>
		<content:encoded><![CDATA[<p>Is there any reason why the processed (encoded) html actually displays instead of being parsed?</p>
<p>I reviewed our old frontend and it uses  to display the encoded html.</p>
<p>Am I missing something?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

