Re: [Audacity-translation] enough is enough. Re: French Translation for "28 janvier 2009: Audacity 1.3.7 released" on first page

[Arturo 'B. B. <bu...@bu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Cleber Tavano wrote:
> This project is suffering from serious lack of attention from the
> developers to the translators.

Actually, that might be true. I joined this list days ago, even though I'm in charge of getting the
PO files and test-merging them and uploading them to CVS.

Why? Lack of time. Many of you had to send me a po files twice so I could SEE it. Sorry for that,
everybody. Also, I've been travelling a LOT this past year, something I didn't see coming! I hadn't
been in USA or Europe in my life, and one of my projects caught attention, and I found myself being
invited to talk in lots of places. Sorry for that.

Taking that into consideration, if there were a mechanism to ease everyone's lives a little bit
more, then I'd take it! :)

> It's not the first time it happens: is quite common to have released
> versions without a notice here in the list,  nobody tells us when the
> pot files are changed, and we have an absolute dependence to a couple
> of developers that can publish our files.

Problem is: pot files change all the time, as code is added. POT is automatically created out of
source code. I can get a daily-POT file up on a web site everyday if you want it. I can automate that.

> - We need a tool to publish our own files and stop this dependence to
> someone being kind to upload our POs.

The wiki is out there for you to use it for this purpose if you want. http://www.audacityteam.org/wiki

Problem is, we still need to upload the PO files to CVS to make them part of the application. And we
can't give everyone CVS write access.

> - We need a script to tell us that a pot file is changed

It would make noise in everyone's mailboxes if we published that every day. I'm actually not sure
how often the POT file REALLY changes, but if I deployed the auto-POT upload daily, then I might be
able to send an email to this list automatically, only and only if the previous POT file differs
from the freshly-generated one.

Sounds good?

> - We need a way to work collaboratively with our po files. It's
> ridiculous that in 2009 we need to work with offlione files that need
> to go back-and-forth by email just like we used to do 10 years ago.

I'm open to suggestions, really. If I missed any important ideas that were discussed in this list,
feel free to contact me privately or again.

> - And we need a little more respect to tell us *in advance* when
> performing a string-freeze.

That's related to a lot other issues, but we'll discuss it in the team.

> And everybody here know me quite well, as I was one of the first to
> ask Dominic for a way to get this software translated. And brazilian
> portuguese was one of the first languages to be available.

Thanks for your continuous support!

> Why have nobody ever took a position when adopting Pootle is mentioned
> in this list? A guy offered to test that service so many times that I
> can't even count, and nobody ever gave him a answer.

Never heard of it. I'll do my research.

> Cleber
> ps: and *no*, I'm not leaving the project. butm as we say here in
> Brazil, patience has a limit.

We say the same in Argentina :P


- --
Arturo "Buanzo" Busleiman / Arturo Busleiman @ 4:900/107
Independent Linux and Security Consultant - SANS - OISSG - OWASP
http://www.buanzo.com.ar/pro/eng.html
Mailing List Archives at http://archiver.mailfighter.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJjD6cAlpOsGhXcE0RCuxtAJ9K2RpGFJ3SPLU9gvXU+ZdMp0GQ7ACdGaEQ
cCp/DJeNaVNlBo3jFl1Ymko=
=JRsP
-----END PGP SIGNATURE-----