<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
	<channel>
		<title>Serving XHTML in Zend Framework App</title>
		<description>Discuss Serving XHTML in Zend Framework App</description>
		<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/</link>
		<lastBuildDate>Wed, 08 Sep 2010 02:55:42 +0300</lastBuildDate>
		<generator>FeedCreator 1.7.2 - RUS Patches by AndyR</generator>
		<item>
			<title>W3cvalidation says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-55</link>
			<description>Nice information, I really appreciate the way you presented.Thanks for sharing..</description>
			<author>W3cvalidation</author>
			<pubDate>Fri, 16 Jul 2010 12:12:34 +0300</pubDate>
		</item>
		<item>
			<title>Danila V. says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-36</link>
			<description> What is the advantage of this regular experssion over str_replace alternative? str_replace is always faster...</description>
			<author>Danila V.</author>
			<pubDate>Thu, 28 May 2009 10:30:31 +0300</pubDate>
		</item>
		<item>
			<title>Asher Holley says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-35</link>
			<description> The regular expression didn't show up correctly. Not sure how to make it show up correctly.</description>
			<author>Asher Holley</author>
			<pubDate>Tue, 26 May 2009 01:49:33 +0300</pubDate>
		</item>
		<item>
			<title>Asher Holley says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-34</link>
			<description>Check it out: With the appropriate regex support try replacing . str_replace(' /&gt;', '&gt;', $this-&gt;getResponse()-&gt;getBody()) with . preg_replace( '/]*)\s?\/&gt;/', '', $this-&gt;getResponse()-&gt;getBody()) This'll close the tags as well. Asher</description>
			<author>Asher Holley</author>
			<pubDate>Tue, 26 May 2009 01:48:09 +0300</pubDate>
		</item>
		<item>
			<title>Dan says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-31</link>
			<description>Wouldn't it be more precise to say that WebKit prefers XHTML, not Chrome? Or am I missing something?</description>
			<author>Dan</author>
			<pubDate>Thu, 30 Apr 2009 18:06:05 +0300</pubDate>
		</item>
		<item>
			<title>Sebastian says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-30</link>
			<description>If you run site through CMS forget about serving correct XHTML, there will always be something wrong or badly inserted tag if you use WYSIWYG in your app. With &quot;application/xhtml+xml&quot; browser will display errors. In addition to this post you should write about Tidy to clean up XHTML before sending to browser or other presentation layer techniques such as XML / XSLT served as &quot;application/xhtml+xml&quot;. Tidy cleaning can actually be done in dispatchLoopShutdown but it needs to be installed on the server as pecl extension (http://pl2.php.net/tidy)</description>
			<author>Sebastian</author>
			<pubDate>Fri, 24 Apr 2009 17:53:38 +0300</pubDate>
		</item>
		<item>
			<title>Danila V. says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-28</link>
			<description> Thanks. Added Opera to the list. I belive Opera has a long history of support for XHTML but only recent versions indicate prefferance for XHTML over HTML in the Accept header. :) Forgot to enable comments autopublishing. Fixed.</description>
			<author>Danila V.</author>
			<pubDate>Thu, 23 Apr 2009 17:51:28 +0300</pubDate>
		</item>
		<item>
			<title>Danila V. says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-27</link>
			<description> Thanks, I have corrected the code. The code worked fine with Opera and Chrome for me. Make sure that your layout file looks like this: &amp;lt;head&amp;gt; ... &amp;lt;/head&amp;gt; &amp;lt;body&amp;gt; &amp;lt;span&amp;gt;Some text&amp;gt;/span&amp;gt;... &amp;lt;/body&amp;gt; &amp;lt;/html&amp;gt; If an XHTML validator does not validate the document, it won't be displayed in supporting browsers (just the errors)</description>
			<author>Danila V.</author>
			<pubDate>Thu, 23 Apr 2009 17:45:20 +0300</pubDate>
		</item>
		<item>
			<title>Danila V. says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-26</link>
			<description> XHTML specification was made to bring the power of XML features/tools (for instance document parsing) to HTML. When you simply include the XHTML doctype in a webpage, this is not enough to trigger a supporting browser to actually treat the document as XHTML. With only XHTML doctype, served with text/html (common mistake) it does not render the document as XML (XHTML). XML rendering should be faster than rendering HTML document, because XHTML(XML) has well-defined structure. I referred to gzip in my explanation of content negotiation just for example. It can be used for many things. Compressed pages is one of many. Another example of content negotiation is when you have same resource (URL) serving webpage in different language (depending on the user's browser/operation system locale, it will send appropriate http header to indicate its language preferrance).</description>
			<author>Danila V.</author>
			<pubDate>Thu, 23 Apr 2009 17:30:48 +0300</pubDate>
		</item>
		<item>
			<title>Jiew Meng says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-24</link>
			<description>i don't really understand what u meant by &quot;without actually serving document as XHTML&quot; what u mean by that? what is content negotiation? so that compression can be used?</description>
			<author>Jiew Meng</author>
			<pubDate>Thu, 23 Apr 2009 15:11:35 +0300</pubDate>
		</item>
		<item>
			<title>Mario Guenterberg says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-23</link>
			<description>Ehm, shame on me!!!! My first post is valid! The rest of my output is resulting of a overburn brain.</description>
			<author>Mario Guenterberg</author>
			<pubDate>Thu, 23 Apr 2009 12:43:50 +0300</pubDate>
		</item>
		<item>
			<title>Mario Guenterberg says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-22</link>
			<description>Forget my previous post! You have a false typo: . str_replace(' /&gt;', '&gt;', $this-&gt;getResponse()-&gt;getBody() If I correct this, I become a blank page!</description>
			<author>Mario Guenterberg</author>
			<pubDate>Thu, 23 Apr 2009 12:41:09 +0300</pubDate>
		</item>
		<item>
			<title>Mario Guenterberg says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-21</link>
			<description>If I use MSIE 6 or 7 I become a notice: Notice: Undefined property: Zend_Controller_Response_Http::$getBody in /var/www/htdocs/immogo/library/Smartycode/Controller/Plugin/XhtmlServe.php on line 61</description>
			<author>Mario Guenterberg</author>
			<pubDate>Thu, 23 Apr 2009 12:37:15 +0300</pubDate>
		</item>
		<item>
			<title>Jani Hartikainen says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-20</link>
			<description>Opera also sends Accept header with application/xhtml+xml ps. why doesn't your comment form submit when I press enter in the input boxes?</description>
			<author>Jani Hartikainen</author>
			<pubDate>Thu, 23 Apr 2009 11:26:09 +0300</pubDate>
		</item>
		<item>
			<title>Olagato says:</title>
			<link>http://www.smartycode.com/performance/zend-framework-and-xhtml/#comment-19</link>
			<description>Great work ! A &quot;()&quot; is missing at getBody in this line: . str_replace(' /&gt;', '&gt;', $this-&gt;getResponse()-&gt;getBody) ....should be: . str_replace(' /&gt;', '&gt;', $this-&gt;getResponse()-&gt;getBody()) Although this, http://validator.w3.org/ isn't validating the web I'm applying the plugin. One error and 2 warnings are reported: Error: Line 1, Column 1: end of document in prolog Warning 1: Unable to Determine Parse Mode! Warning 2: No Character encoding declared at document level ....but, maybe other reasons beyond this plugin are the reason of the problem.</description>
			<author>Olagato</author>
			<pubDate>Thu, 23 Apr 2009 11:20:21 +0300</pubDate>
		</item>
	</channel>
</rss>
