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 admin site (in my ModelAdmin or ModelForm subclasses) to change the ordering to the natural language of the translated list? My Country model isn't the only one that has fields that need be translated. Another (dynamic) model has thousands of entries and every entry has a description field that needs to be translated. I've not yet begun working on this, as I'm still looking at possibilities. Are there no cons of using gettext for thousands of descriptions in ten languages? Are there no limits? Using gettext all the way would mean updating the po catalog with every addition, removal or update of an entry. This can be done using polib (http://code.google.com/p/polib/). The edit form on the admin site would have to be enhanced with translation form fields for every translatable model field. Or maybe Rosetta (http://code.google.com/p/ django-rosetta/) is all the tooling I need? Cheers, Wouter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
