[RFC] Bazaar internationalization (i18n)

[Alexander Belchenko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Carlos Perelló Marín пишет:
>>>
>>> The worst part of Rosetta for me is the process of import ready *.po file.
>>> I've upload my ru.po for bzr-config, but I have no idea when it will be
>>> imported. Because looking at the page with import queue I see in the beginning
>>> of the list request maiden in January.
>>>
>>> https://launchpad.net/translations/imports?target=products&status=NEEDS_REVIEW&type=po
>>>
>>> And my request has #66. So probably in the August it will be finally imported.
> 
> We are working on improve the import queue handling and displaying to
> clarify it a bit more. There are some entries in NEEDS_REVIEW that
> require manual review by an admin, but there are others, like your ru.po
> that are approved automatically by the system.
> 
> We are adding per project/distribution import queue so you are not
> affected by other imports from other projects.

I don't see ability to copy existing template and translations from trunk
to newly created release series. May be I miss this feature in interface?
Per example: I have bzrconfig.pot ready for translations in trunk.
Then I was create new release series 0.16. And only one way to
copy pot + all po to 0.16 is to upload it again for 0.16, but it again
require full review from Rosetta admins. Despite the fact I've
upload the same data that I download from Rosetta last time.
I think it will be great to use something like branching in Bazaar,
to automatically copy existing translations from trunk to new
release series. Or I'm wrong here?

> Please, if current workflow is not good enough, give us a chance to
> improve it for you filing bugs on https://bugs.launchpad.net/rosetta so
> we have a chance to improve it.

I try it in real tiny project bzr-config and mostly Rosetta workflow
is good enough. And I think we definitely should use it for Bazaar itself.
But I'd like to understand how to deal with release series (see above).

[µ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGPxyfzYr338mxwCURApv0AJ9QDUlMfK+FZSe6KwjQdLtCFnT+RgCfWQB1
EFIWEVxNrH/TKvFRpBSsZc4=
=/1HX
-----END PGP SIGNATURE-----