<?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: EPiPattern: How to render valid xhtml (part 1/2)</title>
	<atom:link href="http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/</link>
	<description>Chatter about EPiServer, ASP.NET, CSS and Web Development.</description>
	<lastBuildDate>Wed, 08 Sep 2010 10:48:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Fredrik Haglund</title>
		<link>http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/comment-page-1/#comment-3357</link>
		<dc:creator>Fredrik Haglund</dc:creator>
		<pubDate>Wed, 09 Dec 2009 15:58:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fredrikhaglund.se/?p=182#comment-3357</guid>
		<description>Hmm... ToWebString will allow some well known HTML-tags to stay unchanged. You specify what tags this in siteSettings in your web.config.

I prefer to use HtmlEncode myself. It feels a little bit safer...</description>
		<content:encoded><![CDATA[<p>Hmm&#8230; ToWebString will allow some well known HTML-tags to stay unchanged. You specify what tags this in siteSettings in your web.config.</p>
<p>I prefer to use HtmlEncode myself. It feels a little bit safer&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans</title>
		<link>http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/comment-page-1/#comment-3356</link>
		<dc:creator>Hans</dc:creator>
		<pubDate>Wed, 09 Dec 2009 14:29:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fredrikhaglund.se/?p=182#comment-3356</guid>
		<description>You mention .ToWebString() and I prefer that over using HttpUtility.HtmlEncode. HttpUtility.HtmlEncode encodes to much I think, å, ä and ö for example.
/Hans</description>
		<content:encoded><![CDATA[<p>You mention .ToWebString() and I prefer that over using HttpUtility.HtmlEncode. HttpUtility.HtmlEncode encodes to much I think, å, ä and ö for example.<br />
/Hans</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fredrik Haglund</title>
		<link>http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/comment-page-1/#comment-3172</link>
		<dc:creator>Fredrik Haglund</dc:creator>
		<pubDate>Wed, 18 Feb 2009 10:59:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fredrikhaglund.se/?p=182#comment-3172</guid>
		<description>Yes, I agree that a library would be usefull... more of a ASP.NET MVC approach where you have better control of rendered html!

Look at Relate+ templates where they use extension methods a lot. It could also be a good complement...</description>
		<content:encoded><![CDATA[<p>Yes, I agree that a library would be usefull&#8230; more of a ASP.NET MVC approach where you have better control of rendered html!</p>
<p>Look at Relate+ templates where they use extension methods a lot. It could also be a good complement&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fredrik Haglund</title>
		<link>http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/comment-page-1/#comment-3171</link>
		<dc:creator>Fredrik Haglund</dc:creator>
		<pubDate>Wed, 18 Feb 2009 10:55:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fredrikhaglund.se/?p=182#comment-3171</guid>
		<description>Hi Magnus!

1) PropertyPageReferenceControl is rendering PageReferences using a HyperLink component and the Text property is assigned page.Property[&quot;PageName&quot;].ToWebString() which should encode it. If this does not work as expected you might found a defect - so please send more details!

2) Yes, xhtmlString should not be encoded since it should be valid. The messy html from the text editor is washed before it is saved. I guess there is flaws in the process. Could you share a few example what comes through?</description>
		<content:encoded><![CDATA[<p>Hi Magnus!</p>
<p>1) PropertyPageReferenceControl is rendering PageReferences using a HyperLink component and the Text property is assigned page.Property["PageName"].ToWebString() which should encode it. If this does not work as expected you might found a defect &#8211; so please send more details!</p>
<p>2) Yes, xhtmlString should not be encoded since it should be valid. The messy html from the text editor is washed before it is saved. I guess there is flaws in the process. Could you share a few example what comes through?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Magnus Paulsson</title>
		<link>http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/comment-page-1/#comment-3169</link>
		<dc:creator>Magnus Paulsson</dc:creator>
		<pubDate>Wed, 18 Feb 2009 06:41:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fredrikhaglund.se/?p=182#comment-3169</guid>
		<description>It seems that EPiServer:Property does not emit valid xhtml in all cases. For example, if the property rendered is a PageReference, the link text will not be HtmlEncoded. The same thing goes for links inside XhtmlString properties. The first one is probably easy to solve by using something other than a Property control, but the second one is much more tricky since it will contain xhtml so it can&#039;t just be HtmlEncoded. Any other suggestions on how to handle these problems?</description>
		<content:encoded><![CDATA[<p>It seems that EPiServer:Property does not emit valid xhtml in all cases. For example, if the property rendered is a PageReference, the link text will not be HtmlEncoded. The same thing goes for links inside XhtmlString properties. The first one is probably easy to solve by using something other than a Property control, but the second one is much more tricky since it will contain xhtml so it can&#8217;t just be HtmlEncoded. Any other suggestions on how to handle these problems?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Search in EPiServer can generate invalid html &#124; Fredrik Haglund's blog</title>
		<link>http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/comment-page-1/#comment-3127</link>
		<dc:creator>Search in EPiServer can generate invalid html &#124; Fredrik Haglund's blog</dc:creator>
		<pubDate>Fri, 16 Jan 2009 17:05:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fredrikhaglund.se/?p=182#comment-3127</guid>
		<description>[...] Read more about pitfalls that can cause invalid html in EPiServer. [...]</description>
		<content:encoded><![CDATA[<p>[...] Read more about pitfalls that can cause invalid html in EPiServer. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Ek</title>
		<link>http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/comment-page-1/#comment-3110</link>
		<dc:creator>Andreas Ek</dc:creator>
		<pubDate>Sat, 20 Dec 2008 20:23:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fredrikhaglund.se/?p=182#comment-3110</guid>
		<description>A lot of page errors in a EPiServer site relates to missing or corrupt data in EPiServer properties. I think that EPiServer should have a lot to win by providing a common static library for property handling.</description>
		<content:encoded><![CDATA[<p>A lot of page errors in a EPiServer site relates to missing or corrupt data in EPiServer properties. I think that EPiServer should have a lot to win by providing a common static library for property handling.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fredrik Haglund</title>
		<link>http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/comment-page-1/#comment-3091</link>
		<dc:creator>Fredrik Haglund</dc:creator>
		<pubDate>Tue, 09 Dec 2008 08:42:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fredrikhaglund.se/?p=182#comment-3091</guid>
		<description>Thanks, Eric! 
Will continue with web controls and code behind and more common pitfalls...
/Fredrik</description>
		<content:encoded><![CDATA[<p>Thanks, Eric!<br />
Will continue with web controls and code behind and more common pitfalls&#8230;<br />
/Fredrik</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus Lindblom</title>
		<link>http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/comment-page-1/#comment-3090</link>
		<dc:creator>Marcus Lindblom</dc:creator>
		<pubDate>Tue, 09 Dec 2008 08:41:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fredrikhaglund.se/?p=182#comment-3090</guid>
		<description>Great post, and don&#039;t forget that semantics is equally important when producing valid x/html.</description>
		<content:encoded><![CDATA[<p>Great post, and don&#8217;t forget that semantics is equally important when producing valid x/html.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric PEttersson</title>
		<link>http://blog.fredrikhaglund.se/blog/2008/12/08/epipattern-how-to-render-valid-xhtml-part-12/comment-page-1/#comment-3089</link>
		<dc:creator>Eric PEttersson</dc:creator>
		<pubDate>Mon, 08 Dec 2008 20:58:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fredrikhaglund.se/?p=182#comment-3089</guid>
		<description>Great post! :)

/Eric</description>
		<content:encoded><![CDATA[<p>Great post! <img src='http://blog.fredrikhaglund.se/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>/Eric</p>
]]></content:encoded>
	</item>
</channel>
</rss>
