>Wouldn't it be a cleaner approach to seperate language dependent
>content completely from the actual models. It's more "DRY" because you
>only define the text fields on one place.
Depends. My idea is to have a situation similar with gettext: you
provide default content that can be translated. If
Wouldn't it be a cleaner approach to seperate language dependent
content completely from the actual models. It's more "DRY" because you
only define the text fields on one place. You could even introduce a
site-wide model for all language dependent content like this:
class Content(meta.Model):
>so 'thing' and 'language' will be unique_together. and to actually
>do the translation, a form which will give side by side areas, one
>displaying the values in 'Thing' and the other giving space to fill
>in the values for 'TranslatedThing'.
>TranslatedThing would only have those fields in Thing
On Wednesday 11 Jan 2006 12:50 pm, hugo wrote:
> class Thing(meta.Model):
> title = ...
> description = ...
>
> class TranslatedThing(meta.Model):
> thing = ForeignKey(Thing)
> language = CharField(... choices=settings.LANGUAGES)
> title = ...
> description = ...
> class META:
>what are the best practices for translating content in the database,
>and storing that?
My current idea runs around just having tables that ForeignKey to the
primary table with the primary table carrying the "default language"
and the dependent table carrying other translatio
Cheng Zhang
On Jan 10, 2006, at 3:00 PM, Kenneth Gonsalves wrote:
hi
what are the best practices for translating content in the database,
and storing that? I feel that for postgres, a separate schema for
each language may be good - that way, just something like
django-admin.py install new language
Cheng Zhang
On Jan 10, 2006, at 3:00 PM, Kenneth Gonsalves wrote:
hi
what are the best practices for translating content in the database,
and storing that? I feel that for postgres, a separate schema for
each language may be good - that way, just something like
django-admin.py install new language
hi
what are the best practices for translating content in the database,
and storing that? I feel that for postgres, a separate schema for
each language may be good - that way, just something like
django-admin.py install new language would just duplicate the
necessary tables in a separate
8 matches
Mail list logo
