Hi,
On Fri, Aug 7, 2009 at 11:25 AM, Stephen Gallagher<sgallagh(a)redhat.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/07/2009 10:40 AM, Miguel P.C. wrote:
> Hi again,
>
>> International testing is always a good thing. On a related note, if you
>> would like to try your hand at translating the SSSD tools to Spanish,
>> feel free to send a patch for the server/po/es.po (you need to first run
>> 'make dist' to have it update the es.po to match the current source
files.
>
> That sounds like something I could add to my TODO list.
> May I suggest that, if we want to multiply the number of people
> translating SSSD, we can use Rosetta in Launchpad to do so. I still
> dont know hot to import ".po" into it or how to get the results from
> there but ... the translating teams behind it (I'm part of one), work
> really nice and are really accurate (although this means terrible
> discussions on one single word in the mailing lists, hehehe).
> I do appreciate the effort you are doing and maybe your policy does
> not let you do so but, I think is something worth considering.
> One thrid option, now that Launchpad is Open/Free Software you can set
> up a "Rosetta" for the project.
>
> Sorry if I'm adding too much noise to this thread but, as I said, I
> think it's worth considering.
>
Well, we're definitely open to expanding out translation community. Our
original plan was to use Fedora's Transifex system, but it doesn't mesh
with our development style. (Transifex requires direct access to our
upstream repository, while we prefer to receive everything in patches
that must be approved by a gatekeeper such as Simo, Sumit or myself).
The latest upstream release of Transifex supposedly has support for
patch-generation instead of repository-integration, but there is no
clear view when the Fedora Infrastructure will upgrade.
Does Rosetta have support for generating patches for upstream, or does
it require repository integration?
Launchpad Translations does not generate patches automatically, but it
allows for translations to be automatically commited to a bzr branch
(
http://blog.launchpad.net/general/exporting-translations-to-a-bazaar-branch),
where they can then be fetched from and integrated to the upstream
project. It seems to me that this could work well with your workflow,
where only the reviewers or gatekeepers can approve the changes.
The main benefit of Launchpad Translations though, is that it allows
building and growing translation communities by lowering the entry
barrier for translators and allowing them to work in a collaborative
way.
--
Mathias Gug
Ubuntu Developer
http://www.ubuntu.com