<?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: Utf8 in web perl application (LAMP) &#8211; binmode, charset</title>
	<atom:link href="http://perl.baczynski.com/work/utf8-web-perl-application-charse/feed" rel="self" type="application/rss+xml" />
	<link>http://perl.baczynski.com/work/utf8-web-perl-application-charse</link>
	<description>Perl, CPAN, YAPC... et ceatera</description>
	<lastBuildDate>Thu, 28 Jul 2011 08:50:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://perl.baczynski.com/work/utf8-web-perl-application-charse/comment-page-1#comment-168</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 18 Dec 2009 11:18:55 +0000</pubDate>
		<guid isPermaLink="false">http://perl.baczynski.com/?p=158#comment-168</guid>
		<description>&gt; Use the strict document type.

And what benefit will this give to me? :)</description>
		<content:encoded><![CDATA[<p>> Use the strict document type.</p>
<p>And what benefit will this give to me? <img src='http://perl.baczynski.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anon</title>
		<link>http://perl.baczynski.com/work/utf8-web-perl-application-charse/comment-page-1#comment-167</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Wed, 16 Dec 2009 07:32:32 +0000</pubDate>
		<guid isPermaLink="false">http://perl.baczynski.com/?p=158#comment-167</guid>
		<description>Not &quot;and/or&quot;. Definitely &quot;and&quot;. The correct Content-Type is a MUST. On the other hand, the meta element can be left out. - Avoid the transitional document types for new documents! As the name says, it is for transitioning up from HTML 3 or untyped HTML. When generating documents, you are completely under control. Use the strict document type.</description>
		<content:encoded><![CDATA[<p>Not &#8220;and/or&#8221;. Definitely &#8220;and&#8221;. The correct Content-Type is a MUST. On the other hand, the meta element can be left out. &#8211; Avoid the transitional document types for new documents! As the name says, it is for transitioning up from HTML 3 or untyped HTML. When generating documents, you are completely under control. Use the strict document type.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

