[buildd-tools-devel] Bug#588962: Bug#588962: [Was: Bug#588962: schroot: Please provide documentation as po4a for translation]
David Prévot
david at tilapin.org
Sun Nov 27 23:23:36 UTC 2011
Hi Roger, Thomas,
On 27/11/2011 18:37, Roger Leigh wrote:
> Sorry for the long delay--I had to finish my PhD, and this got
> pushed to the back of my TODO list.
Well, if this imply you've finished your PhD, let me just congratulate you!
> […] we can probably
> even generate localised examples automatically this way,
> providing that we have the appropriate locales available on
> the system.
Good idea, a Build-Depends on locales-all is not that expensive ;-).
> I'm having some difficulty in initially getting things working;
> […] I'm not sure if your patch includes the needed
> logic for actually generating the .pot file or if that needs
> doing in addition.
It indeed needs an empty POT file in the accurate directory (my patch
aimed to contain this empty file, but I obviously missed it):
mkdir man/po4a/po
touch man/po4a/po/schroot-man.pot
po4a --force man/po4a/po4a.cfg
You can either choose to ship the POT file in the the Git repository, or
to remove it at clean time, and regenerate it using “touch” and “po4a
--force …”, as you prefer.
> Some pointers would be much appreciated.
po4a(1) gives some information (see EXAMPLE section),
/usr/share/doc/po4a/README.maintainers.gz is also useful, and I tried to
point the needed stuff on my patch message [0].
0: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588962#25
Since then, I've learned a few more stuff on po4a, so I may offer more
accurate advices now.
> I'm also unsure of how to generate the localised manpages and
> include them in the build infrastructure.
If Thomas is still willing to translate the pages, I think the best
approach is to let him begin, and once an initial (incomplete and even
not reviewed yet) PO file will be available, we'll try to provide a few
more patches (or direction of things to do, since I'm still not really
aware of the Makefile stuff). We've recently succeeded with that
approach in grep-dctrl and packaging-tutorial.
Regards
David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20111127/6bfd8449/attachment.pgp>
More information about the Buildd-tools-devel
mailing list