This Week in Django is a weekly podcast about all things Django.
SPECIAL FEATURE – Internationalisation
This is the first part of a two part series on Internationalisation. This week we are privileged to talk to Malcolm Tredinnick, Django core developer. Malcolm educates us on what internationalisation is all about, how it is implemented in Django, and some of the areas that can be improved in the future.
Additionally, we also discuss a lot of changesets in the Queryset Refactor Branch, and a couple of blog posts from the Django community.
It is our longest show yet, but definitely worth your attention. This is a must listen podcast.
Please see the Show Notes below for all the pertinent information and links
Downloads
AAC Enhanced Podcast (79.3 MB, 1:41:32, AAC)
MP3 Edition (69.8 MB, 1:41:32, MP3)
OGG Edition (56.8 MB, 1:41:32, Vorbis)
The Enhanced Podcast version contains screenshots and easy access links to all of the items we discuss throughout the podcast.
Feeds Available
iTunes Feeds are available. By subscribing using the iTunes feeds the podcasts will automatically be downloaded for you when we release them.
iTunes Feeds
This Week in Django – AAC Edition
This Week in Django – MP3 Edition
Regular RSS Feeds
This Week in Django – AAC Edition
This Week in Django – MP3 Edition
This Week in Django – OGG Edition
Give Us Feedback
Want to give us some feedback on the show? We’re always looking for ideas or suggestions that will help improve each episode. Please contact us at feedback __at__
thisweekindjango.com.
Show Notes
Special Feature – Internationalization (1:39)
Malcolm Tredinnick, Django core developer, joins us to discuss internationalisation. Malcolm has often played the role of expert on internationalization / localization issues, speaks several languages, and works closely with the Django translators.
To learn more about Malcolm Tredinnick, be sure to add his blog, Defying Classification, to your RSS feeds and listen to our interview with Malcolm on This Week in Django 13
- What is the difference between internationalisation and localisation?
- Python 3.0 will feature full unicode support. What does that mean for Django? Will there be any benefits?
- I attended a discussion by Tim Bray, who I suppose is a recognized internationalisation expert, and by the end of the discussion I felt like the idea of creating truly internationlised applications is somewhat hopeless. What are your thoughts about this?
- How does translation support appear to the end-user in something like Django? (how they set which language to use, what Django does, etc).
-
Justin Lilly, a Django user and rabid fan of the show, wanted to ask, “I’m curious how many different ways there are to declare gettext-like things.. ugettext, gettext, (as a commonly used alias).. any more I don’t know?” So what about it? What’s the differences?
- What is the difference between unicode and utf-8? Is there a difference?
- What sort of things do developers need to watch out for when writing code for an international audience?
- What are some areas where Django’s support is a little weak and can be improved?
- What can we do to improve the support in third-party applications for Internationalisation?
- People learn differently so maybe we need to explore as many ways as possible to educate people. We can use things like tutorials or screencasts.
- are internationalised.
- Goal is to get Django to pass the Turkey test yet, but it’s a goal.
- How do you handle sorting in Django?
Tracking Trunk (59:37)
-
Updated Markdown Filter to Support v1.7
(7423)
– From the mailing list, “Additionally, the encoding
argument has been removed from both markdown
and Markdown
. Markdown expects unicode (or ascii) input and it is the users responsibility to ensure that’s what is provided. Therefore, all output is in unicode. Only markdownFromFile
accepts an encoding.”
Branching & Merging (1:01:57)
Community Catchup (1:24:12)
-
The limits of Django – Interesting post by Alberto GarcÃa Hierro where he discusses the process he used to optimize queries. His final solution ended up being a C library. The post received tons of interest and he provided a followup, The limits of Django: the answers, where he addresses some of the questions he received.
Thank You! (1:38:43)