2009/10/21 Wagner Bruna
<wagner.bruna+...@gmail.com<wagner.bruna%2b...@gmail.com>
>
> Hello,
>
> Peer Sommerlund wrote:
>
>> 2009/10/20 Wagner Bruna
>> <wagner.bruna+...@gmail.com <wagner.bruna%2b...@gmail.com><
>> wagner.bruna%2b...@gmail.com <wagner.bruna%252b...@gmail.com>>
>>
>> [reasons to skip launchpad]
>>>
>>
>> So, there would be three reasons to skip Launchpad
>> a) No danger of reusing a translation with another license (so
>> we can find the same translation by our self). In my mind, this
>> is plain silly - but then I'm no lawyer.
>>
>
> Agreed :-(
>
> b) the cset would show who contributed the translation
>> c) people would be discouraged from contributing small
>> translations out of context
>>
>> I did most of the Danish translation, and I also found that
>> offline translating with source-in-hand was faster and gave
>> better translations. On the other hand, I would never have
>> started on translating it if I hadn't started translating on
>> Launchpad.
>>
>
> We could keep Launchpad for starting or still uncoordinated translations,
> and change to a translation repository if/when the translation is
> complete/coordinated enough.
>
> It may be a good idea to state on the translation page that contributions
> to Launchpad won't be recorded individually. We could also list manually all
> contributors at the beginning of the .po file.
>
> It was me that set up the Launchpad translation, mostly to do
>> something with very little time. I'm a very low contributing
>> resource, not like Steve or Yuki. I feel some kind of
>> responsibility for making sure translations work, and do the
>> janitor work required to keep Rosetta (Launchpad translation)
>> running. If you would take the task of nudging the translation
>> infrastructure I would be more than happy to hand it over to
>> you. I will give you all the little help I can and I'm sure
>> Yuki will too.
>>
>
> I don't have much (read: any) experience with Launchpad administrative
> tasks, but I'd love to help you with that. Please let me know how and when
> to start.
>
Welcome to the club of translation drivers :-)
As long as we keep Launchpad around, there will be the job of generating and
uploading POT files. This can be done via the web interface or via a bzr
repository. Anybody is welcome to do this, but I suppose it is just the
translation drivers that have a reason to do it.
The job is simple: As often as possible, generate a POT file, if it contains
new stuff, upload it to Launchpad. This should be done for both stable and
unstable, but stable is not supposed to change a lot. Except now, as we are
close to a release.
This is step 1 and 2 described here
http://bitbucket.org/tortoisehg/stable/wiki/developers/Translation
This does not address how to accept .po files. Since we still use Launchpad
it must also be the master of PO files. Thus, we can accept PO files in some
repo, but at the same time have to upload the file to Launchpad.
One way to do this could be:
(a) translators must have push rights somewhere, e.g. directly to
http://bitbucket.org/tortoisehg/stable/ (which holds both stable and
unstable branches) or maybe to an intermediate repository somewhere.
(b) a yet-to-be-written server script must check for comitted PO files, and
upload them to bitbucket as soon as possible. For example via a bzr
repository
(c) Another yet-to-be-written script could pull PO files from Launchpad via
a bzr repo. Launchpad will push strings once a day. Any changes goes into
the hg repo with "launchpad" as user. Or maybe an even more clever script
could find the last contributer and use that as user name.
(d) of course we also need a server to run the scripts.
If you could tackle the points above that would be a big help. You might
recycle some of the bits from a small .bat I wrote to do some of the bzr
scripting -- http://bitbucket.org/peso/thg-launchpad/src/tip/translate.bat
Regards,
Peer
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Tortoisehg-develop mailing list
Tortoisehg-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
