Re: New PO Template file for `gnuash'
- From: martin v loewis de (Martin v. Loewis)
- To: Carlos Perelló Marín <carlos gnome-db org>
- Cc: Karl Eichwalder <ke suse de>,Christian Stimming <stimming tuhh de>,GNOME i18n list <gnome-i18n gnome org>,tp - Translation Project <translation IRO UMontreal CA>
- Subject: Re: New PO Template file for `gnuash'
- Date: 30 Oct 2002 21:59:52 +0100
Carlos PerellÃ³ MarÃn <email@example.com> writes:
> will you update both list the one at cvs.gnome.org and the other at TP ?
No. I cannot modify cvs.gnome.org. Someone at the Gnome translation
project would have to do that.
> what happens if a translation does not exist and a gnu translator
> starts the translation and at the same time a gnome translator do
> the same?
Coordination is required. You cannot simply start translating without
The same coordination is required *within* a project: What if two
gnome translators simultaneously start a translation?
> I'm not telling the problems with the GNOME way and the GNU way, I'm
> talking about the problems we can have if we use both teams for the
> same module. I's more easy that a GNOME translator joins the GNU
> team or GNU translator joins the GNOME team that we try to work
> together with our own tools.
It might be the easier way, but not necessarily the better way. It
should be possible to define operational procedures and technical
measures to allow translators from both projects to contribute to some
software - if we, as the managers of these projects, are encouraging
> I will only agree to work together if we look a way to integrate the
> robot and our cvs (the robot gets a file do all checks and then commit
> it to cvs.gnome.org and automaticly fetchs .pot snapshots. The robot
> should be able to manage dated versions).
If you think this is a procedure that can be implemented: sure?
] [Thread Prev