On 13 ene, 01:24, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On Jan 12, 2008 11:04 PM, Grupo Django <[EMAIL PROTECTED]> wrote: > > > > > IMHO Internationalization is useless if there is no support for > > multilingual translations in the database. I've seen different > > approaches like Django Multilingual > > (http://code.google.com/p/django-multilingual/ > > ) and transdb (http://code.google.com/p/transdb/), but I have no > > idea which I should use if I should use one of those. Is there any > > plan to include this feature before django 1.0? I think this is the > > biggest lack in the django framework, and it's a very important > > problem especially for non English speakers. > > I18n of the database isn't on the v1.0 plan. > > The fact that there are multiple approaches should give you a hint as > to why this is the case - there isn't a consensus on how the problem > can be solved in a generic fashion (or even if it can be solved in a > generic fashion at all). The needs for a content i18n system will > depend very much on your own local site requirements. > > Yours, > Russ Magee %-)
Is there any place where I can find a discussion about this? I'm really interested in this feature. I'd like to help as much as I can. Thank you. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
