<?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: Using non-ascii in Django templates</title>
	<atom:link href="http://djangodays.com/2008/11/10/using-non-ascii-in-django-templates/feed/" rel="self" type="application/rss+xml" />
	<link>http://djangodays.com/2008/11/10/using-non-ascii-in-django-templates/</link>
	<description>A growing collection of all things Django</description>
	<lastBuildDate>Sun, 18 Apr 2010 06:31:10 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Malcolm Tredinnick</title>
		<link>http://djangodays.com/2008/11/10/using-non-ascii-in-django-templates/comment-page-1/#comment-349</link>
		<dc:creator>Malcolm Tredinnick</dc:creator>
		<pubDate>Fri, 28 Nov 2008 04:16:23 +0000</pubDate>
		<guid isPermaLink="false">http://djangodays.com/?p=82#comment-349</guid>
		<description>Assuming you&#039;re using Django 1.0 or later (well, anything since the unicode merge landed in Django, which was just after 0.96), you can use non-ASCII characters in templates. It would be a bit short-sighted if we supported non-ASCII everywhere except in templates!

You must be doing something a bit unusual here. The most likely thing I can think of is your files aren&#039;t saved as UTF-8. Django assumes the template files are in UTF-8 (it has to assume something, since auto-character set detection is unreliable in many cases) and if you have saved the files in some other encoding, you&#039;ll need to set the FILE_CHARSET setting appropriately. Have a look at the ref/unicode.txt documentation file for information.

I just rechecked this with the exact example you&#039;re using and it loads from a template file and renders without problems.</description>
		<content:encoded><![CDATA[<p>Assuming you&#8217;re using Django 1.0 or later (well, anything since the unicode merge landed in Django, which was just after 0.96), you can use non-ASCII characters in templates. It would be a bit short-sighted if we supported non-ASCII everywhere except in templates!</p>
<p>You must be doing something a bit unusual here. The most likely thing I can think of is your files aren&#8217;t saved as UTF-8. Django assumes the template files are in UTF-8 (it has to assume something, since auto-character set detection is unreliable in many cases) and if you have saved the files in some other encoding, you&#8217;ll need to set the FILE_CHARSET setting appropriately. Have a look at the ref/unicode.txt documentation file for information.</p>
<p>I just rechecked this with the exact example you&#8217;re using and it loads from a template file and renders without problems.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
