WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
Yes, sorry about that--I was working on this quite late, and that
was a copy-paste error. schroot-1.5.2.tar.xz is the correct file.
> > - I'm getting a "translated" directory in both the source
> > directory and build directory
> > (man/translated/fr and debian/build/man/translated/fr).
> > It's a bug to dirty the source tree--I really only want
> > them generating in the build tree.
> > I set srcdir and destdir, but I'm not sure if I'm doing the
> > right thing (see: man/Makefile.am update-po rule).
> I can't see what's wrong at first sight, adding the po4a-devel list in
> the loop in case we're missing something. The actual call is:
> [ -n "$(PO4A)" ] && $(PO4A) --package-name $(PACKAGE) --package-version
> $(VERSION) --copyright-holder "Roger Leigh <rleigh@...>"
> "--srcdir=$(srcdir)" "--destdir=$(builddir)" "$(srcdir)/po4a.cfg"
> Indeed, simply running “po4a --destdir=../debian/build/man/ po4a.cfg”
> from the man directory builds everything where expected (even with
> “--srcdir=.”), but when run from the root directory, it builds them in
> both the --srcdir and the --destdir, so it may be a bug in po4a. As a
> workaround, you could remove the sloppy man/translated directory in the
> update-po rule, after the po4a call.
We can do this as a workaround for now. (Actually, for the release
I'm making today, I'll probably temporarily disable it entirely
until the updated translation is ready. It'll be enabled for the
next release release though.)
In general though, it breaks building from a read-only source tree
of building several diffrent builds from a common source tree, so
I would hope to be able to fix it. It should be possible to use
symlinks to work around this by faking that everything is in the
build dir if it really can't be fixed.
> > - The fr manpages are output in UTF-8. The man program results
> > in readable output, but the PDF/PS documentation looks awful
> > due to lots of junk in the output.
> > While UTF-8 is fine in the .po file, would recoding to latin1
> > or into groff symbols for non-ASCII characters be feasible?
> Charset of the files containing the localized documents can be change
> with the -L option of po4a, but, there is better:
> > Or can groff now process UTF-8 input?
> “groff -k -KUTF-8” seems to do the work quite nicely.
Ah, fantastic stuff. The PDF manpage looks great, bar a few
formatting issues (.TH might be broken).
I did see an issue with missing words in some files such as
\*[PROGRAM] at the beginning of the line, but I couldn't see
a reason for it. But I'm sure such minor details are easily
Hopefully in a future release I'll be able to localise all
the output of the program examples, too. But that's quite a
lot more work, and will require writing programs to generate
the output, too, so it might have to wait until after wheezy.