For multilingual sites, is it not easier to maintain and keep all the translations in .po files? The idea of splitting up the required translations would mean that translators must use two different interfaces. There are frameworks for translating .po files that keep revisions, suggestions etc. These would not be available. Do you think it would be possible to have the contents of flatpages parsed by the template parser before being displayed? If the scripts that generate the .po files could also parse these, translations could be maintained at a single point. I have never looked at the django code before so I don't know what's viable.
On second thoughts it seems what I'm proposing is to store flat pages as templates in a database so they are easily editable. Hmmm, maybe that's not such a good idea after all. What are your opinions on this? Cheers, Tim On Nov 9, 3:19 pm, DvD <[EMAIL PROTECTED]> wrote: > That's what i am about to do, but if guys from the development team > agree we could implement it in the official django code > > On Nov 9, 3:34 pm, Eugene Morozov <[EMAIL PROTECTED]> wrote: > > > I've implemented similar system. Only I have used MyFlatPage and > > MyFlatPageTranslation models, because it makes easier to locate and > > translate pages in the admin interface. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
