On 22 Mar, 10:22, bruno desthuilliers <bruno.desthuilli...@gmail.com> wrote: > on 22 mar, 09:26, Luca Casagrande <luca.casagra...@gmail.com> wrote: > > > Hello everyone, > > I'm working on the localization of a Django project and I met some > > difficulties. Following the documentation in the section > > "Internationalization ", I could easily translate the contents of the > > templates and the verbose_name of the model's attributes. > > The problem is that one of my models has a notes field (CharField) > > with different text for each entry. > > What is the best way to translate those values, if possible, always > > working with po files? > > gettext / po files are for the "static" text only (that is, text in > your source code). Translations of your application data has to be > handled at the, well, application data level (IOW: in your db). There > are quite a few "multilingual model" solutions around, I've been > mostly happy with transmet so far but didn't have to handle more than > 3 languages at once - not sure how it would scale for a dozen or more. > > http://code.google.com/p/django-transmeta/
Thanks for your answer. Right now the db is full populated, and I have seen that transmeta need to create new columns. Should do thi by hand or there's another approach to this operation (i.e. South) ? Luca -- 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.
