On Mon, Nov 9, 2009 at 9:34 PM, Kenneth Gonsalves <[email protected]> wrote: > > On Tuesday 10 Nov 2009 8:26:08 am Chris Moffitt wrote: >> Thanks for taking the time to update the German translation. I know that >> Bruce did a lot of work with the module refactoring to split up the PO >> files. Hopefully he can chime in a bit more about the design decisions >> there.
> I do translation - from what I gather there are several .po files. As a > translator, I would prefer to have just one (or two, one for ordinary and the > other for js). These should preferably live in the root. That way I can > concentrate on translation, without worrying about how the application handles > it. Django has it this way, and so do most of the apps I have seen. I did split the .po files, probably messily. However, I'm not in completely sold on the way we are doing it. To be honest, I'd prefer to do it in whatever way will encourage more translators to contribute. However, I think that we must have a split for the .po files for the "very soon to be separate projects." At the moment, that means a separate file for django-livesettings, django-keyedcache, django-bursar, and Satchmo. How does that sound? Is it easy (or close to easy) to use gettext tools to re-merge the other .po files, or should I whip up some Python to do that? -- Bruce Kroeze http://www.ecomsmith.com It's time to hammer your site into shape. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo 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/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
