Re: Internationalization (i18n) of model: request.LANGUAGE_CODE in __unicode__ and ordering?

On 20 mei, 10:19, Kai Kuehne wrote: > I have worked on making django-countries working with > 1.1:http://github.com/kaikuehne/django-countries/tree/master > > There's also a branch which uses django-multilingual which I created > but not published. If you'd need that, I could polish it and put

Re: Internationalization (i18n) of model: request.LANGUAGE_CODE in __unicode__ and ordering?

Hope this subject gets some more exposure. I'm curious to know what is possible in using gettext for all dynamic database translations. Or should I wait till Marc Garcia has finished work on his Google Summer Of Code i18n project (http://vaig.be/2009/04/gsoc- implementation-of-additional-i18n.htm

Re: Internationalization (i18n) of model: request.LANGUAGE_CODE in __unicode__ and ordering?

Hi Tom, Thanks for sharing your thoughts. Indeed, I need ordering based on the translations. If I'd use gettext for database field record translations, then ordering must be done afterwards (after db query). Is that even possible and what would be the performance cost? And how could I tell the a

Internationalization (i18n) of model: request.LANGUAGE_CODE in __unicode__ and ordering?

Hi there, Spent hours trying to find the solution, but no luck. So here goes... Please consider simplified code below: {{{ class Country(models.Model): ... label_en = models.CharField(max_length = 128, blank=True, null=True) label_nl = models.CharField(max_length = 128, blank=True,