Wow, thanks! Now I have to decide which one to use... :) On Sat, May 3, 2008 at 4:26 PM, Panos Laganakos <[EMAIL PROTECTED]> wrote:
> > Two projects exist: > > http://code.google.com/p/django-multilingual/ > http://code.google.com/p/transdb/ > > DM uses an inner class on the model, to define the translatable > fields. > > TransDB uses custom field types. > > > Hopefully they'll be merged at some point or work on a new uniform way > to do this. > > On May 3, 4:22 pm, dimrub <[EMAIL PROTECTED]> wrote: > > Suppose, you want to have a model, the fields of which are available > > in multiple languages. How would you people go around doing it? The > > most trivial method would be to define as many variations of each text > > field as there are lanugages, and define a function inside the model > > that returns the variation that corresponds to currently chosen > > language, and use this function in all the views instead of the actual > > fields. Are there any other patterns in place? Just don't want to > > invent a wheel here. > > > -- Vale, Dmitry Rubinstein --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
