Re: Using different translation workflow

Le mardi 23 février 2010 à 08:31 +0100, Claude Paroz a écrit :
> Hi,
> For the first time, we have a GNOME Git hosted module that choose to use
> a different translation tool than
> On one side, I would say that freedom is the key, so every module
> maintainer should choose the tool which suited him the best.
> On the other side, this could lead to fragmentation. If GNOME
> translation teams have to use several different platform for their work,
> there is clearly an overhead implied. Considering various comments on
> the bug #608627, coordinators don't like this situation.
> So the question is, should we make it an explicit requirement to use
> as the main translation platform for a module to be
> hosted in GNOME Git?

Thanks for all those who contributed to this discussion. While
discussing privately with Debarshi, we found a sort of compromise. will still be available to translate solang, but po files
will be sent by email from the platform to Debarshi, which will then
submit the files to the corresponding GNOME translation team.
This way, GNOME teams will still be able to quality check the file and
then commit it like any other GNOME module.

Hopefully this solution will be satisfactory to all parts.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]