[RFC] Bazaar internationalization (i18n)
Carlos Perelló Marín
carlos.perello at canonical.com
Wed Aug 1 12:10:18 BST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Sorry, this email got lost in my inbox...
Alexander Belchenko escribió:
> Carlos Perelló Marín ?8H5B:
>>>> 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.
>>>> 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?
There is no such feature yet. We have in mind something that would allow
you to do something similar, although we are still discussing whether
will be implemented or not. So for now, yes, you need to do a full
Another thing we are thinking on implement is to auto approve new
templates if there is already one approved before. Anyway, we have a new
procedure that we follow so new requests shouldn't stay unapproved more
than one or two days.
>> 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).
For series we usually encourage people to have just translations for
'trunk', unless you are going to keep two different development
branches. Once you get a 0.16 branch, most people do only bug fixes
there so no new strings are added so the ones from trunk would be the
same. Though, if that's not the case, having two templates is the way to go.
I'm not sure whether this answered your questions.
Carlos Perelló Marín
Ubuntu => http://www.ubuntu.com
mailto:carlos.perello at canonical.com
Alicante - Spain
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar