<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Localization on Personal Site of Tim Child</title>
    <link>/tags/localization/</link>
    <description>Recent content in Localization on Personal Site of Tim Child</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 19 Oct 2010 21:50:07 +0000</lastBuildDate>
    
	<atom:link href="/tags/localization/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Django localization and internationalization</title>
      <link>/2010/10/19/django-localization-and-internationalization/</link>
      <pubDate>Tue, 19 Oct 2010 21:50:07 +0000</pubDate>
      
      <guid>/2010/10/19/django-localization-and-internationalization/</guid>
      <description>We have been using the localization and internationalization ( l10n&amp;amp; i18n ) from Django quite a bit for our translations, and although we haven&amp;#8217;t had to tackle anything difficult like Arabic or Persian yet there are still some shortcomings in the system.
The standard Django module for input of dates and datetime stamps is quite restrictive. It depends on a module, I think written by Simon Willson which uses the PHP notation rather than the Python/C strftime / strptime notation.</description>
    </item>
    
  </channel>
</rss>