<?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: You do like XSLT? Use it proper!</title>
	<atom:link href="http://sitecore.alexiasoft.nl/2006/11/14/you-do-like-xslt-use-it-proper/feed/" rel="self" type="application/rss+xml" />
	<link>http://sitecore.alexiasoft.nl/2006/11/14/you-do-like-xslt-use-it-proper/</link>
	<description>All about the web, online marketing, Sitecore, .NET and building sites...</description>
	<lastBuildDate>Tue, 07 Feb 2012 08:09:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: JP</title>
		<link>http://sitecore.alexiasoft.nl/2006/11/14/you-do-like-xslt-use-it-proper/comment-page-1/#comment-3434</link>
		<dc:creator>JP</dc:creator>
		<pubDate>Sun, 19 Nov 2006 14:30:30 +0000</pubDate>
		<guid isPermaLink="false">http://sitecore.alexiasoft.nl/2006/11/14/you-do-like-xslt-use-it-proper/#comment-3434</guid>
		<description>First I love XSLT. 
1. Agree, I think Sitecore should do xml output in default template. But I always use UTF-8 insted country specific encoding. Once I had problems with dtSearch (Sitecore 4.1) when I didn&#039;t use UTF-8.
2. I always make my own default template with global variables to labels and frontpage or other.
3. I use comments, comments are good.
4. I don&#039;t really agree on having to write 10-20 lines code in XSL, just write comments :)

Personally I don&#039;t like web controls/user controls so I use code behind only for building XSL helpers. All my presentation is in XSLT&#039;s. I really like XSL but that is probably because I come from different perspective than you. Before I discover XML I worked as a designer and therefore I found XSL great language of templating. I didn&#039;t approach it as a programmer. I do agree if you want to do &quot;programming&quot; in XSL it is a lousy language for that.</description>
		<content:encoded><![CDATA[<p>First I love XSLT.<br />
1. Agree, I think Sitecore should do xml output in default template. But I always use UTF-8 insted country specific encoding. Once I had problems with dtSearch (Sitecore 4.1) when I didn&#8217;t use UTF-8.<br />
2. I always make my own default template with global variables to labels and frontpage or other.<br />
3. I use comments, comments are good.<br />
4. I don&#8217;t really agree on having to write 10-20 lines code in XSL, just write comments <img src='http://sitecore.alexiasoft.nl/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Personally I don&#8217;t like web controls/user controls so I use code behind only for building XSL helpers. All my presentation is in XSLT&#8217;s. I really like XSL but that is probably because I come from different perspective than you. Before I discover XML I worked as a designer and therefore I found XSL great language of templating. I didn&#8217;t approach it as a programmer. I do agree if you want to do &#8220;programming&#8221; in XSL it is a lousy language for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexey Rusakov</title>
		<link>http://sitecore.alexiasoft.nl/2006/11/14/you-do-like-xslt-use-it-proper/comment-page-1/#comment-3396</link>
		<dc:creator>Alexey Rusakov</dc:creator>
		<pubDate>Thu, 16 Nov 2006 21:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://sitecore.alexiasoft.nl/2006/11/14/you-do-like-xslt-use-it-proper/#comment-3396</guid>
		<description>I really don&#039;t like bloated xslt, but most of all it&#039;s the logic bloat. 

Some really tricky xslt combos are trivial to do in .net, so I&#039;d say use extensions object where applicable.</description>
		<content:encoded><![CDATA[<p>I really don&#8217;t like bloated xslt, but most of all it&#8217;s the logic bloat. </p>
<p>Some really tricky xslt combos are trivial to do in .net, so I&#8217;d say use extensions object where applicable.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

