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 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 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? > > Advice appreciated! > Brandon > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
