[buildd-tools-devel] Bug#588962: Bug#588962: schroot: Please include po4a material for translated documentation

[Roger Leigh]

On Wed, Jul 28, 2010 at 11:05:14PM -0400, David Prévot wrote:
> tag 588962 patch
> thanks
> 
> Hi Roger, Thomas,
> 
> Le 19/07/2010 13:24, David Prévot a écrit :
> > Le 13/07/2010 18:23, Roger Leigh a écrit :
> >> On Tue, Jul 13, 2010 at 10:00:03PM +0200, Thomas Blein wrote:
> 
> >>> [...] I saw that the documentation of the schroot package is not translated
> >>> in any language. I would like to translate it French. For this, there is a 
> >>> need to change the source organisation so the documentation use po4a to
> >>> allow us to translate it. 
> >>>
> >>> I would like to know if such changes could be me made.
> > 
> >> I'd be happy to make this sort of change, or accept patches to do this.
> 
> Please find attached a patch against the current git repository in order
> to provide POT files to translators, and build translated documentation.
> 
> 1. You first want to run "po4a man/po4a/po4a.cfg" in order to populate
> the POT file (man/po4a/po/schroot-man.pot here, the name is arbitrary).
> 
> 2. The POT file should then be proposed to translators. Once you
> received one (fr.po for example), you just have to put it in
> man/po4a/po/. If you receive an addendum (fr.add for example), just put
> it a the new sub-directory man/po4a/add_fr/.
> 
> 3. If there are some translations, run "po4a man/po4a/po4a.cfg" in order
> to update PO and POT files and build the translated documentation (for
> example, French translation of man/schroot.1.in will be build in
> man/translated/fr/schroot.1.in).
> 
> 4. You also probably want to add a clean rule in order to delete the
> directory man/translated (which will contain, in subdirectories, the
> translated documentation build by "po4a man/po4a/po4a.cfg"): it doesn't
> need to be saved in your VCS, just keep the PO and POT files.
> 
> I'm not sure of how you want to configure stuff with Autotools, but:
> point 1: just need to be done once you've applied the patch.
> point 2: just need to be done once you receive a translation.
> point 3: it should be done before creating the tarball, thus the
>  	proposed rule added in the dist-hook target.
> point 4: you should add a clean rule somewhere.
> 
> You also off course need to actually build and install the translated
> manual pages (from man/translated/$lang/manpages.#.in), but it can wait
> until you actually receive some translation. translated pdf and ps can
> also be provided.

Many thanks for all your help with this.  I'm afraid I'm quite
busy with my PhD at the moment, but I hope to get this included
soon, hopefully for Squeeze but that might not be possible.


Thanks again,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20100815/f7618ea7/attachment-0001.pgp>