Are there any best practices or experiences dealing with
internationalized sites? Most importantly with URL structure and
crawling effects (The DB i18n is not an issue at the moment).
In some sites I've worked I've added a switch language button which
changes the language but the URLs remain the s
> Should I:
>
> 1. Make a separate field for each translation and add a method in the
> model to return the correct translation to use in templates?
>
> 2. Make a separate table for translations in general with a foreign
> key to the original record and look up the translation that way?
I think y
to quote the django internationizaton documentation...
"Using ugettext_lazy() and ungettext_lazy() to mark strings in models
and utility functions is a common operation. "
Getting data from your models requires you to place
django.utils.translation.ugettext_lazy() functions within the
arguments
The is an existing db internalization application -
http://code.google.com/p/django-multilingual/. Try to look at it.
On Thu, Nov 6, 2008 at 11:20, Brandon Taylor <[EMAIL PROTECTED]>wrote:
>
> Hi everyone,
>
> I'm tasked with translating a mostly database-driven site into
> Spanish. I'm familiar
Hi everyone,
I'm tasked with translating a mostly database-driven site into
Spanish. I'm familiar with how to use Django's internationalization on
static strings in templates, but not with text coming from a database,
so I'm looking for some best practices advice...
Should I:
1. Make a separate
5 matches
Mail list logo
