[Mailman-i18n] Using bzr for translation commits (was: Re: Slovak translation of GNU Mailman

Barry Warsaw barry at python.org
Tue Jul 31 02:14:11 CEST 2007

Hash: SHA1

On Jul 28, 2007, at 1:51 AM, Clytie Siddall wrote:

> On 28/07/2007, at 9:58 AM, Barry Warsaw wrote:
>> Here's something I've been thinking about, and I'd like to know what
>> you folks think about this.
>> Short of using a translation service such as Rosetta or Pootle,
> Pootle would definitely make things easier, and gain you more  
> translator participation.

I think Rosetta probably would too, although I don't have a good  
sense of which community is more robust, where mind-share is heading,  
or what the major advantages and disadvantages of both systems are.   
That's a good part of the reason why I don't want to think about  
switching to either yet, although we should start another thread at  
some point to talk about it.  The right time for that is probably  
when we want to get 2.2 and/or 3.0 translated.

> This is my first encounter with bzr. I installed it last night (via  
> MacPorts), and according to the wiki page for bzr, it seems similar  
> enough to svn from the user POV. As long as committing a  
> translation via bzr is as straightforward as committing via svn, it  
> shouldn't be a problem for people accustomed to using source  
> control. (We're still losing the vast majority of linguists, who  
> are not technically minded, so Pootle is still my recommendation.)

bzr should feel pretty natural for svn users, but please let me know  
if anybody hits roadblocks!

> For source control, I still prefer svn. ;)  For one thing, it's  
> embedded into my favourite tools: my translation editor, my text  
> editor and my file manager ― bzr is not.

I know!  Hopefully over time, that stuff will come.  (I recently  
scratched my own itch in writing a bzr plugin for setuptools ;).

- -Barry

Version: GnuPG v1.4.7 (Darwin)


More information about the Mailman-i18n mailing list