Posts tagged with i18n

Subscribe to the feed of posts tagged with i18n

If you use a language that's a bit more complex than English (or most western languages, that is), you'll probably have some problems displaying dates that actually don't look like computer-generated.

Django-localdates deals with this problem, and tries to tackle the general problem of internationalizing dates.

March 25, 2008, 2:22 p.m. More (235 words) 7 comments Feed

django-localdates is a django app that brings local date presentation to django, by providing custom date filters that can use local-flavored format strings.

July 17, 2007, 2:18 p.m. More (870 words) 6 comments Feed

Following up to the part 3 of my series about implementing a multilingual interface for this blog, I now present the things to make the language-magic happen: Middleware and context processors.

June 3, 2007, 4:39 p.m. More (630 words) 2 comments Feed

As I wrote in the two previous posts, I wanted the URLs of this site to contain the language the content is in. To do this, I had to write some custom code, including models, managers, middleware and context processors.

May 14, 2007, 3:31 p.m. More (1250 words) 2 comments Feed

Designing URLs for international content can be tricky. I explore the possibilities and use cases, and a clear pattern emerges.

May 13, 2007, 5:43 a.m. More (586 words) 0 comments Feed

From the start, I was interested in making the content posted here available in two languages: Greek and English. This is no small feat, and I thought long and hard on how to make it possible and get it working just the way I like it. So here is a rundown of how internationalization works on this blog.

May 6, 2007, 10:14 p.m. More (816 words) 0 comments Feed