On 31 mar, 09:34, Mika Sjöman <mikasjo...@gmail.com> wrote: > Hi > > The content of my models have fields that need to be translated in the > django admin in several languages.
How many ? Three or two dozen ? > I found it to be a major hassle to get it working. If you have no more than 2 or 3 languages to support, django- transmetta has been an easy-working solution for us so far. Now I don't think it would scale that well with too many languages - depending on your model, it might add way too many fields to the underlying table. In this case you may prefer another solution using distinct rows for the translated versions (there are quite few django apps doing this one way or another). > Since django is having > internationalization built in, why does it not also allow you to easily mark > model fields for translation? Because i18n is definitly not a simple problem, so there's no good one- size-fits-all solution. The "right" strategy depends too much on your specific application and needs. B. -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
