Re: Using different translation workflow

2010-02-24 Thread Claude Paroz
Le mercredi 24 février 2010 à 23:30 +0200, Debarshi Ray a écrit : > > I suppose we're suggesting this as a temporary solution, right? It > > kinda puts a lot of weight on the developer himself and scalability is > > pretty low. > > I think the extra work of routing translations from Tx.net to > l1

Re: Using different translation workflow

2010-02-24 Thread Debarshi Ray
> I suppose we're suggesting this as a temporary solution, right? It > kinda puts a lot of weight on the developer himself and scalability is > pretty low. I think the extra work of routing translations from Tx.net to l10n.gnome.org manually will be worth the effort in the end. Cheers, Debarshi -

Re: Using different translation workflow

2010-02-24 Thread Dimitris Glezos
On Wed, Feb 24, 2010 at 10:44 PM, Claude Paroz wrote: > 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 l10n.gnome.org. >> >> https://bugzilla.gnome.org/show_bu

Re: Using different translation workflow

2010-02-24 Thread Og Maciel
On Wed, Feb 24, 2010 at 3:44 PM, Claude Paroz wrote: > Transifex.net 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 b

Re: Using different translation workflow

2010-02-24 Thread Claude Paroz
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 l10n.gnome.org. > > https://bugzilla.gnome.org/show_bug.cgi?id=608627 > http://mail.gnome.org/archives/gnome-i18n/2