2009/2/10 Stephan Richter <srich...@cosmos.phy.tufts.edu>:
> On Monday 09 February 2009, Dan Korostelev wrote:
>> Nowadays, when we have a fully egg-based setup, the translations in
>> the zope.app.locales package make no sense anymore as it's very hard
>> to maintain them and it just wrong (to me at least) to have a separate
>> centralized translations package for a hundred of eggs.
> I think that while having a centralized translations package make no sense
> anymore, I think we should still maintain a canonical translation memory that
> serves as the authoritative translation for all packages. This provides
> consistency across packages and is the way it is done in the professional
> localization business.
> So basically, option (b) with option (a) as translation memory.
Can you explain that once more? Do you mean that we translate each
package in its own translation domain and then collect messages from
all packages to a global translation domain that is used only as a
translation memory and not for actual i18n of components?
WBR, Dan Korostelev
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -