Hello Dan, In short, a good translation is consistent. That means the same sentences are translated to the same foreign sentence. A so-called translation memory is used for that. Also terms (specific words or expressions of the domain) are translated to the same foreign term. I think that's the idea of Stephan. There are proprietary tools to enforce this. I think launchpad translation is somehow also a translation memory as it pulls in previous translations. Though no idea how the above could be solved with FOSS tools. Tuesday, February 10, 2009, 2:36:28 AM, you wrote: DK> 2009/2/10 Stephan Richter <srichter@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.
DK> Can you explain that once more? Do you mean that we translate each DK> package in its own translation domain and then collect messages from DK> all packages to a global translation domain that is used only as a DK> translation memory and not for actual i18n of components? -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: She is descended from a long line that her mother listened to. - Gypsy Rose Lee