We have used both multilingual and transmeta in a project and feel multilingual is much simpler to use. Both have its own pros and cons though.
Both of them pose certain limitations on your model. You can develop your own translation process best fit your needs. You can refer the translation used on FeinCMS. I forget the url , just google and the required file is translations.py On Sep 16, 3:32 pm, andreas schmid <[email protected]> wrote: > why do you think its simpler? > at a first look i really feel transmeta is the simpler one. > specially to integrate with an already working project with front end > editing and forms in the templates which are not written manually and > with use of uni-form. > > and what if i have a custom save on the add_mycontent view... ?? > > can you (or someone else) give me a feedback on this?! > > Anish wrote: > > You can use django-multilingual. > > It's simplest of the two. > > You can have the complete installation and usage on the django- > > multilingual wiki > > > On Sep 16, 12:45 pm, aschmid <[email protected]> wrote: > > >> so i checked a few apps and im between django-transmeta and django- > >> multilingual, not sure yet what i should use. i have only one field > >> for every model which i want to be multilingual. the easier approach > >> would be the transmeta package at a first look... > > >> is there anybody with a bit of experience using those apps which could > >> me point to the right choice? > > >> thx > > >> On Sep 14, 1:54 pm, andreas schmid <[email protected]> wrote: > > >>> hi list, > > >>> i have to develop a multilingual site and it works well on a single > >>> language now... but i have to do it for 3 languages translating some > >>> fields of the models. > > >>> can you give me some tips for good available apps? > > >>> my usecase is very simple. if a model has fields > > >>> * title > >>> * description > >>> * body > > >>> i need to translate description and body, title (==slug) will remain > >>> the same. the fact is that only one language should be required, the > >>> others are optional and if a visitor looks at a content thats not > >>> translated in the current language it should output a link to the > >>> canonical language. > > >>> what is actually the best app to achieve that? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
