[RFC] i18n/l10n pam_winbind for samba 3.x

[Christian Perrier]

Quoting Volker Lendecke (Volker.Lendecke at SerNet.DE):

> While there --- I'd *love* to get rid of the XML file for at
> least smb.conf.5. This manpage was broken so many times in
> the past that I'd consider XML just a big mistake for what
> we need.

What's actually puzzling in samba, indeed, is that the XML sources of
documentation are *not* provided along with the source code, making it
impossible to regenerate the manpages, etc at build time.

I suspect this could become a problem if the documentation is i18n'ed
because you would actually never distribute something containing a POT
file and PO files, which is what translators need to work. Having
those "only" in an "obscure" git repository wouldn't help that much in
getting this material translated.

> black art than I like. It's like Java: Write once, run
> everywhere, until you decide to run apt-get upgrade and
> debian gives you a different jvm. Then you can start from

If you use Debian as it's recommended when seeking for stability (ie
use Debian stable), this cannot happen. Of course, you'll not get the
latest shiny JVM (the one that will be obsoleted by another one the
week after), but you'll get something stable (well, as stable as Java
can be...).

But I'm sure you know that and you were just trolling...:-)