On Thu, Aug 16, 2012 at 4:38 PM, Russell Keith-Magee <russ...@keith-magee.com> wrote: > I agree that this is certainly one way that we could address the > problem. However, localflavor isn't just forms. Some of the packages > (US in particular; and I think there's also a patch lurking for AU) > have database models as well. I'd be inclined to keep the > 'localflavor' moniker.
Ah, yes, the packages should be django-localflavor-* -- good point. > Also, from a project management point of view, there's the issue of > translations. At present, there's a single locale directory that > contains all the translations for all the localflavors. If we break > out localflavor into separate installable directories, we probably > don't want to break them into 40 different locale directories. I won't > profess any particular expertise on translations, so there might be an > obvious and elegant solution that I'm missing, but I wanted to flag it > so that it's kept in mind. I'm hoping Jannis or somebody else with translation expertise will chime in on this -- I have no idea what the repercussions/solutions could be. Adrian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
