Can bzr team host my branch for translation target until i18n is merged? (Re: i18n test environment on Lauchpad staging.

[vila]

>>>>> INADA Naoki <songofacandy at gmail.com> writes:

    > On Sat, May 14, 2011 at 5:58 PM, vila <v.ladeuil+lp at free.fr> wrote:
    >>>>>>> INADA Naoki <songofacandy at gmail.com> writes:
    >> 
    >>    > The project I registered is removed maybe because hosting test-purpose branch is
    >>    > not allowed.
    >> 
    >> Hmm, you may have misunderstood how staging works, it's a sandbox and is reset
    >> periodically.

    > Firstly, my test project on staging is removed after one day I've
    > created it.  So I've created lp:bzr-i18n on Launchpad (not
    > staging), but it is removed too.

https://launchpad.net/bzr-i18n exists (at the time of this writing) but
is marked inactive 8-/

We have a bzr sprint starting this Monday so I'll make sure things are
ok.

Ohhh, 
https://launchpad.net/bzr-i18n/+review-license mentions:

  2011-05-12 Curtis Hovey: Project disabled and INADA Naoki (INADA
  Naoki) notified.

Did you get some related email ?

Anyway, we'll sort this out. We probably want indeed to make it owned by
bzr-core and set the approrpiate policies for translations.

<snip/>

    > Sorry, I've miswrote. What I want to do is that testing
    > translation on Launchpad, autoimport and autoexport.  This allows
    > me to test whole workflow works fine before I make merge request.

It seems fine (to me) to use this project for early tests but may be
Curtis has good reasons against it.

    > I've implemented exporting pot, building mo from po and runtime
    > translating in lp:~songofacandy/bzr/i18n already. Launchpad may be
    > able to import pot file automatically like qbzr, bzr-explorer and
    > TortoiseBZR. But I haven't play with Launchpad's autoexport
    > feature. So I cannot decide how to import translated messages from
    > Launchpad.

It's still unclear to me how all the pieces work together, shouldn't the
translated files be part of the bzr project itself so they can be used
while building the packages and the installers ?

Do we have a document explaining the various parts and how they interact
or is there some guide on launchpad for that ?

In any case, even a short draft we can add under doc/developers will be
good to have. We can then update it as things become clearer[1].

    > But this is not necessary if someone in bzr-core team works on it.
    > May someone works on it?

I try to help you getting started but I'm not doing more than that so
far :-/

    Vincent

[1]: At least for me, may be they already are for others ;)