Re: Best Practice for translating db-stored values

2007-07-15 Thread Collin Grady
I like this method: http://code.google.com/p/i18ndynamic/ --~--~-~--~~~---~--~~ 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

Re: Best Practice for translating db-stored values

2007-07-15 Thread Tim Chase
> Is there some general suggestion we're to follow, for translating > values stored in the db? Unless your project's grand vision only supports a fixed number of languages ("we will only support English, Spanish, French, and German...ever"), then you'll need a translation table. class Translati

Re: Best Practice for translating db-stored values

2007-07-15 Thread Jökull
Have you looked at django-multilingual? http://code.google.com/p/django-multilingual/ I'm about to have a go at implementing this. It looks great for multilingual content sites. On Jul 14, 5:27 pm, Panos Laganakos <[EMAIL PROTECTED]> wrote: > Using gettext_lazy, is the way to go, for marking mo

Best Practice for translating db-stored values

2007-07-14 Thread Panos Laganakos
Using gettext_lazy, is the way to go, for marking models and fields for translation. Is there some general suggestion we're to follow, for translating values stored in the db? ie, let's say it's a model: class Furniture(models.Model): name = models.CharField(_('name'), maxlength=25) If the