[PATCH] .po files for pam_winbind for v3-3-test

Christian Perrier bubulle at debian.org
Thu May 14 16:23:28 GMT 2009

(CC'ing me on replies is not needed as I read the list...or is that a
common practice on samba mailign lists?)

Quoting Volker Lendecke (Volker.Lendecke at SerNet.DE):
> On Thu, May 14, 2009 at 06:51:56AM +0200, Christian Perrier wrote:
> > That could be a Pootle server dedicated to localization of samba (at
> > least the part that exists now for pam_winbind and maybe later the
> > localization of net...or the manpages localization, etc....).
> Okay, never heard of Pootle before.

Pootle originated as part of the translate.org project
(translate.sourceforge.net). It is now used, among others, for some
Mozilla l10n efforts, as well as some OOo l10n work.

It is mostly meant to prove translators and translation teams a
convenient framework to handle the workflow involved in
translation/review processes as well as team work.

Another goal is also making access to localization material easier to
people contributing on it. 

Transifex, mentioned by Simo, is not directly a concurrent project but
more somethign that can be seen as complementary. Here the main goal
is simplifying the methods to access l10n material without offering an
online translation tool. From talks I had (quite some time ago,
already) with Dimitris Gleizos, both can indeed be complementary and
not concurrent.

> > In order to start with something, one could imagine having a git
> > branch for localization work, branched form the master branch, on
> > which a Pootle server  would be "hooked". At this time, it would allow
> > volunteers to work on source/locale/pam_winbind material (the only
> > place where we have PO files).
> Hmmm. I think I need to learn a lot more about Pootle
> before. Why does it need to hook on a branch? Do we give
> away checkin privs to the world there?

Actually, we could imaging hooking up Pootle directly on an existing
branch such as the master branch in git. However, that means some kind
of automated commits, which upstream developers are generally not
comfortable with..:-)... We are doing this on some Debian projects
(mostly the installer localization work) but only when we have some
possible methods to recover from possibly broken commits (for
installer localization, I'm also part of the installer dev team and I
closely monitor what's done through Pootle).

When this is not possible, what we did for instance for the
FusionForge project on pootle.debian.net was having the upstream
developer create a specific branch for localization in his VCS
(bzr). The Pootle server then pushes its commits there and they are
pulled by upstream when they prepare releases. Of course, they also
push updates when they feel them as needed.

> > I think I can setup something like this on pootle.debian.net where we
> > have the whole thing ready, as a kind of demo of what's feasible.
> I think a demo would be great!

It's probably fairly easy to create a "Samba" project there, just
pulling changes from git, without pushing them back. Then I could ring
some bells in the Debian l10n community to have people work on these
translations....or maybe have some Samba contributors work on them (a
small call for help on the samba at lists.s.o mailing list could bring
some fairly easily, imho). Then, the individual files could be (for a
first try) just picked up manually by the crazy guy who proposed this
(aka me) and pushed back to Karolin for inclusion in a release.

More information about the samba-technical mailing list