<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: ascii</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/ascii.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2007-07-04T14:41:24+00:00</updated><author><name>Simon Willison</name></author><entry><title>UnicodeBranch: Porting Applications</title><link href="https://simonwillison.net/2007/Jul/4/unicodebranch/#atom-tag" rel="alternate"/><published>2007-07-04T14:41:24+00:00</published><updated>2007-07-04T14:41:24+00:00</updated><id>https://simonwillison.net/2007/Jul/4/unicodebranch/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist"&gt;UnicodeBranch: Porting Applications&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
A checklist for porting Django applications to handle the new unicode changes. If your application only handles ASCII text at the moment you shouldn’t have to change a thing.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/ascii"&gt;ascii&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/django"&gt;django&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/porting"&gt;porting&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/unicode"&gt;unicode&lt;/a&gt;&lt;/p&gt;



</summary><category term="ascii"/><category term="django"/><category term="porting"/><category term="unicode"/></entry></feed>