On Fri, Jun 24, 2011 at 17:06, Stuart MacKay <smac...@flagstonesoftware.com> wrote: > A possible step would be to split the files then simply concatenate them > together, using a custom management command, before calling compilemessages. > That would make it easier to manage the translations but at the cost of an > extra step in preparing for deployment.
It would though, in my opinion, be a good feature to maybe specify which files to compile with compilemessages such that this feature was built into django. E.g. $ ls forms.po models.po translators.po $ django-admin.py compilemessages translators.po models.po $ ls forms.po models.po translators.po django.mo Or something. I'm not a django developer, but I'm sure someone here is, and this may have been a ticket sometime? :) -- With regards, Herman Schistad -- 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.
