[SSSD] [PATCH] Make manual pages translatable

Stephen Gallagher sgallagh at redhat.com
Tue Nov 30 11:51:05 UTC 2010


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

I haven't reviewed or tested this patch yet, but I have some comments on
the summary. See below.

On 11/30/2010 01:42 AM, Jakub Hrozek wrote:
> Utilizes PO4A to extract translatable strings from Docbook XML sources
> and allows translators to submit ordinary .PO files. PO4A then generates
> translated Docbook documents that can be used to generate translated end
> user documentation.
> 
> https://fedorahosted.org/sssd/ticket/297
> 
> The second patch adds a skeleton of Czech translation I used for testing
> -- at least one man page is localized so the whole process is testable.
> 
> The general approach is based on what some of the Debian-based projects do.
> 
> I have two questions about the patch:
> 
>  * the way the patch is written now, the localized manpages (and the
> respective xlm sources) are generated during every "make" invocation --
> so they are always in sync. I couldn't decide it makes more sense to add
> a specialized "docs" and "docsinstall" targets or something
> similar..which would be trivial to do, I'm just not sure whether it's
> better or worse than keeping things done with "make all".
> 

Please use the existing PO files as a guideline. We only regenerate the
.po files during a "make dist", because we don't want them to constantly
be cluttering our git status.

Please make the new targets for updating the po files as a dependency on
the update-pot target in po/Makefile if possible. This way, they're only
generated during "make dist". This will be behaving the same way that
the current translatable files do.

It will be the release engineer's responsibility to build these
translated manpages and commit them at the string freeze.

"make install" should just use whatever previously-generated PO files
are available.


>  * the .po files are distributed, not the localized .xml sources. I
> think it makes more sense since the localized .xml sources are generated
> from the .po files and the original .xml sources anyway, but it would be
> easy to change the distribution to .xml and only regenerate the .xml
> sources when releasing a new upstream
> tarball.

We need to make sure the po files are distributed, otherwise Transifex
won't work.


- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkz05SYACgkQeiVVYja6o6MSYQCgph0PTu474KvlLLqxw/XwEBdm
hIUAoImtGG/vaY5Ae7oujAC3EF9wA4OD
=Lg78
-----END PGP SIGNATURE-----



More information about the sssd-devel mailing list