Re: What can Git do for translators?
- From: Federico Mena Quintero <federico ximian com>
- To: Simos Xenitellis <simos lists googlemail com>
- Cc: Gnome-i18n List <gnome-i18n gnome org>
- Subject: Re: What can Git do for translators?
- Date: Thu, 08 Jan 2009 18:19:59 -0600
On Tue, 2009-01-06 at 15:24 +0000, Simos Xenitellis wrote:
> The GNOME dev discussion takes place at
> http://mail.gnome.org/archives/desktop-devel-list/2009-January/thread.html#00003
> The discussion is somewhat heated, so it's no place for translators to
> post about.
The "real" discussion about how the migration is being done is in
gnome-infrastructure:
http://mail.gnome.org/archives/gnome-infrastructure/2009-January/thread.html
And our scratchpad is here:
http://live.gnome.org/GitMigration
> If a move eventually takes place, it will require time and effort, so
> it would not happen within the next six months.
We hope to have working repositories, at least for guinea pigs, within
two weeks :) Moving all the repositories over to git will of course
require time --- it's not the conversion that is the biggest problem,
but fixing the infrastructure and writing documentation.
> The big question is, how would a DVCS affect the GNOME localisation workflows?
One of my tasks for the migration to Git is to write a little bunch of
tutorials for various scenarios --- maintainers, contributors,
translators, etc.
However, I'm not 100% sure about the workflows that translators tend to
use. Do people mostly use web tools (and what happens then --- does the
tool commit for them)? Or do they checkout a whole module and simply
commit to the .po files? Or do they checkout a *single* .po file and
then commit it back, or send patches to a language coordinator?
Federico
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]