Piotr, I already answered you at Django users, here are some other points.
Sometime you may not need 1-to-1 translations, e.g. each language may have its own independent set of articles. Some parts of the site may exist only in one language. And for some people, like me, it's easier to deal with explicit multiple fields and/or models for each language than with any multilingual 'magic'. IMO Django core should be free from any multilingual magic - most sites have only one language and complex models require custom solutions anyway. On 26 янв, 03:57, Piotr Majewski <[EMAIL PROTECTED]> wrote: > First, sorry for my english. > I think that a very good idea would be having multilingual content. I > searched the google and I found django-multilingual very usefull > (http://code.google.com/p/django-multilingual/), but since it is not > working well with complex models I think that django should nativly > support multilingual content. And by that i mean text fields that are > translation. For me, and people developing multilingual websites this > is very vital feature, and in my mind it would be very helpfull for > developing multilingual websites such as booking.com (where > decriptions of hotels are aviable in every 16 languages). I think that > django developers will consider this ticket (idea) usefull. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
