<?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: XSLT Tips for Cleaner Code and Better Performance</title>
	<atom:link href="http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance/feed" rel="self" type="application/rss+xml" />
	<link>http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance</link>
	<description>A blog on web standards, accessibility, css, javascript, xslt, and more</description>
	<lastBuildDate>Mon, 09 Jan 2012 03:47:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Två stycken nya filmer - Webbteknik II - Webbteknik II</title>
		<link>http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance/comment-page-1#comment-14948</link>
		<dc:creator>Två stycken nya filmer - Webbteknik II - Webbteknik II</dc:creator>
		<pubDate>Thu, 10 Nov 2011 14:25:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance#comment-14948</guid>
		<description>[...] Jag vill också rekommendera en intressant artikel om hur man skriver effektivare XSLT. http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance [...]</description>
		<content:encoded><![CDATA[<p>[...] Jag vill också rekommendera en intressant artikel om hur man skriver effektivare XSLT. <a href="http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance" rel="nofollow">http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Francois Bernard</title>
		<link>http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance/comment-page-1#comment-14721</link>
		<dc:creator>Francois Bernard</dc:creator>
		<pubDate>Thu, 09 Sep 2010 15:47:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance#comment-14721</guid>
		<description>Hi Anup,
sorry for the delay, lot of work in my job.  Thanks for the advice, when I&#039;ll find some free time I&#039;ll try it.

Thanks once more,
Regards.</description>
		<content:encoded><![CDATA[<p>Hi Anup,<br />
sorry for the delay, lot of work in my job.  Thanks for the advice, when I&#8217;ll find some free time I&#8217;ll try it.</p>
<p>Thanks once more,<br />
Regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anup Shah</title>
		<link>http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance/comment-page-1#comment-14100</link>
		<dc:creator>Anup Shah</dc:creator>
		<pubDate>Tue, 13 Jul 2010 23:18:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance#comment-14100</guid>
		<description>Hi, I assume you mean HTML in the description element? It looks like it has been escaped with things like &amp;. Instead of that, if you are able to, can you have the HTML be in XML format rather than escaped? If you need to, you could write the HTML as well formed XML and put it in the XHTML namespace. Your XSLT could then match those elements and copy them out. 

This approach also lets you write XSLT templates to do things like filter out code you don&#039;t want, e.g. font tags, or more importantly script tags.

Hope that helps!</description>
		<content:encoded><![CDATA[<p>Hi, I assume you mean HTML in the description element? It looks like it has been escaped with things like &amp;. Instead of that, if you are able to, can you have the HTML be in XML format rather than escaped? If you need to, you could write the HTML as well formed XML and put it in the XHTML namespace. Your XSLT could then match those elements and copy them out. </p>
<p>This approach also lets you write XSLT templates to do things like filter out code you don&#8217;t want, e.g. font tags, or more importantly script tags.</p>
<p>Hope that helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Francois Bernard</title>
		<link>http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance/comment-page-1#comment-14099</link>
		<dc:creator>Francois Bernard</dc:creator>
		<pubDate>Tue, 13 Jul 2010 21:02:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance#comment-14099</guid>
		<description>I have a problem with this process - how to maintain HTML code in the XML elements content?  I&#039;ve tried to parse XML from http://refsbook.com  (i.e. http://refsbook.com/xml/taniafoto ), and some of the elements contain HTML code!!!  Is there a tag, attribute or a special tool for that in XSLT transormation?   Thank you for any help!</description>
		<content:encoded><![CDATA[<p>I have a problem with this process &#8211; how to maintain HTML code in the XML elements content?  I&#8217;ve tried to parse XML from <a href="http://refsbook.com" rel="nofollow">http://refsbook.com</a>  (i.e. <a href="http://refsbook.com/xml/taniafoto" rel="nofollow">http://refsbook.com/xml/taniafoto</a> ), and some of the elements contain HTML code!!!  Is there a tag, attribute or a special tool for that in XSLT transormation?   Thank you for any help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorraine</title>
		<link>http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance/comment-page-1#comment-14091</link>
		<dc:creator>Lorraine</dc:creator>
		<pubDate>Wed, 16 Jun 2010 19:18:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance#comment-14091</guid>
		<description>Thank you so much for the code advice! Its much cleaner</description>
		<content:encoded><![CDATA[<p>Thank you so much for the code advice! Its much cleaner</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajendra Joshi</title>
		<link>http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance/comment-page-1#comment-14048</link>
		<dc:creator>Rajendra Joshi</dc:creator>
		<pubDate>Fri, 08 Jan 2010 11:01:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance#comment-14048</guid>
		<description>Informative article....</description>
		<content:encoded><![CDATA[<p>Informative article&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajit</title>
		<link>http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance/comment-page-1#comment-14046</link>
		<dc:creator>Ajit</dc:creator>
		<pubDate>Tue, 05 Jan 2010 11:25:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance#comment-14046</guid>
		<description>Nice article...</description>
		<content:encoded><![CDATA[<p>Nice article&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anup Shah</title>
		<link>http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance/comment-page-1#comment-14014</link>
		<dc:creator>Anup Shah</dc:creator>
		<pubDate>Fri, 30 Oct 2009 12:37:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance#comment-14014</guid>
		<description>@Joshua Hewitt:

Good point. In XSLT 1.0 I can&#039;t think of a way. I think you would have to use xsl:if under the element and then that means using xsl:attribute in that scenario.

I believe (though have not had any experience in it) that XSLT 2.0 has additional capabilities and syntax to allow that kind of thing.</description>
		<content:encoded><![CDATA[<p>@Joshua Hewitt:</p>
<p>Good point. In XSLT 1.0 I can&#8217;t think of a way. I think you would have to use xsl:if under the element and then that means using xsl:attribute in that scenario.</p>
<p>I believe (though have not had any experience in it) that XSLT 2.0 has additional capabilities and syntax to allow that kind of thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Hewitt</title>
		<link>http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance/comment-page-1#comment-14008</link>
		<dc:creator>Joshua Hewitt</dc:creator>
		<pubDate>Wed, 28 Oct 2009 09:37:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance#comment-14008</guid>
		<description>I understand that avoiding  and using attrib=&quot;{A}&quot; is cleaner and faster, but is it possible to avoid outputting empty attributes (attrib=&quot;&quot; if A is empty)? Basically this without all the bloat:


  
    
  
</description>
		<content:encoded><![CDATA[<p>I understand that avoiding  and using attrib=&#8221;{A}&#8221; is cleaner and faster, but is it possible to avoid outputting empty attributes (attrib=&#8221;" if A is empty)? Basically this without all the bloat:</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rajesh kumar parbat</title>
		<link>http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance/comment-page-1#comment-13911</link>
		<dc:creator>rajesh kumar parbat</dc:creator>
		<pubDate>Fri, 26 Jun 2009 12:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.onenaught.com/posts/23/xslt-tips-for-cleaner-code-and-better-performance#comment-13911</guid>
		<description>Nice article .......
I appreciate</description>
		<content:encoded><![CDATA[<p>Nice article &#8230;&#8230;.<br />
I appreciate</p>
]]></content:encoded>
	</item>
</channel>
</rss>

