Bug#588962: po4a using both builddir and srcdir
Hi Roger, Quoting Roger Leigh rle...@codelibre.net: - 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? Or can groff now process UTF-8 input? (./configure make pdf to test) For me I can do the both (latin1 and groff symbols). After I don't know how it should be for long term integration. - There have been several manpage changes since the translation was done. Thomas, would it be possible to update the translation? No problem. I take care of it. Regards, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588962: [buildd-tools-devel] Bug#588962: po4a using both builddir and srcdir
On Tue, May 15, 2012 at 04:48:29PM +0200, Thomas Blein wrote: Hi Roger, Quoting Roger Leigh rle...@codelibre.net: - 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? Or can groff now process UTF-8 input? (./configure make pdf to test) For me I can do the both (latin1 and groff symbols). After I don't know how it should be for long term integration. I would definitely prefer the text to remain as plain UTF-8 in the .po file--it will make it easier all around to both work on and use. Ideally I'd just like to be able to ask po4a to recode it to latin1 when it comes to generating the translation, and/or replace accented characters with groff escapes. Hopefully this is doable with po4a. If not, I can always just recode the documentation before processing it with groff. BTW, I could, if it made translation easier, switch to a different format than troff, for example DocBook. My only issue with DocBook was that all the tools to convert to manpage format were awful. But if there are alternatives I should consider, I'll be happy to do so. - There have been several manpage changes since the translation was done. Thomas, would it be possible to update the translation? No problem. I take care of it. Much appreciated, thanks! It will look really nice when complete. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588962: po4a using both builddir and srcdir
Hi, Le 14/05/2012 19:50, Roger Leigh a écrit : I've been working on #588962 to implement po4a for the schroot documentation. Thanks Roger! http://people.debian.org/~rleigh/schroot_1.5.1.orig.tar.xz I guess you actually meant: http://people.debian.org/~rleigh/schroot-1.5.2.tar.xz - 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 rle...@debian.org --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. - 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. Regards David signature.asc Description: OpenPGP digital signature
Bug#588962: [buildd-tools-devel] Bug#588962: po4a using both builddir and srcdir
On Tue, May 15, 2012 at 12:46:08PM -0400, David Prévot wrote: Hi, Le 14/05/2012 19:50, Roger Leigh a écrit : I've been working on #588962 to implement po4a for the schroot documentation. Thanks Roger! http://people.debian.org/~rleigh/schroot_1.5.1.orig.tar.xz I guess you actually meant: http://people.debian.org/~rleigh/schroot-1.5.2.tar.xz 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 rle...@debian.org --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). http://people.debian.org/~rleigh/schroot-fr.pdf http://people.debian.org/~rleigh/schroot-en.pdf 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 fixable though. 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. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588962: [buildd-tools-devel] Bug#588962: po4a using both builddir and srcdir
Le 15/05/2012 15:33, Roger Leigh a écrit : On Tue, May 15, 2012 at 12:46:08PM -0400, David Prévot wrote: 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. […] 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. I thought about a bit less ugly workaround: “cd man po4a $stuff” since this issue is not triggered if po4a is run with --srcdir=. (or implied). Another workaround could be to rewrite man/po4a.cfg to document the files path from the root directory (attached, but I haven't tested it: it may need extra care about $(builddir) in the Makefile call since it should now point the debian/build/ directory instead of debian/build/man/). I also took the liberty to simplify the addenda handling (they should now be added as man/addenda/$lang.add, Thomas should be able to provide one for his translation (and I will be happy to help if needed). Regards David [po_directory] man/po/ [po4a_alias:man] man opt:-M UTF-8 -L UTF-8 [type: man] man/authors.man $lang:man/translated/$lang/authors.man \ add_$lang:?man/addenda/$lang.add [type: man] man/copyright.man $lang:man/translated/$lang/copyright.man \ add_$lang:?man/addenda/$lang.add [type: man] man/schroot.1.man $lang:man/translated/$lang/schroot.1.man \ add_$lang:?man/addenda/$lang.add [type: man] man/schroot-setup.5.man $lang:man/translated/$lang/schroot-setup.5.man \ add_$lang:?man/addenda/$lang.add [type: man] man/schroot.conf.5.man lang:man/translated/$lang/schroot.conf.5.man \ add_$lang:?man/addenda/$lang.add [type: man] man/schroot-script-config.5.man $lang:man/translated/$lang/schroot-script-config.5.man \ add_$lang:?man/addenda/$lang.add [type: man] man/schroot-faq.7.man $lang:man/translated/$lang/schroot-faq.7.man \ add_$lang:?man/addenda/$lang.add [type: man] man/dchroot.1.man $lang:man/translated/$lang/dchroot.1.man \ add_$lang:?man/addenda/$lang.add [type: man] man/dchroot-dsa.1.man $lang:man/translated/$lang/dchroot-dsa.1.man \ add_$lang:?man/addenda/$lang.add # The following files could also be offered for translation, maybe separately #[type: man] csbuild.1.man $lang:man/translated/$lang/csbuild.1.man \ # add_$lang:?man/addenda/$lang.add signature.asc Description: OpenPGP digital signature
Bug#588962: po4a using both builddir and srcdir
Hi folks, I've been working on #588962 to implement po4a for the schroot documentation. However, I'm running into a few difficulties which I hope some old hands can provide some guidance on fixing. I have added Thomas' fr translation, and got it to produce fr manpages and PDF documentation. This is in a prerelease version at http://people.debian.org/~rleigh/schroot_1.5.1.orig.tar.xz The main issues are: - 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). - 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? Or can groff now process UTF-8 input? (./configure make pdf to test) - There have been several manpage changes since the translation was done. Thomas, would it be possible to update the translation? It's in man/po/fr.po of the above source archive, though I can send you the file if you need. Other than these hopefully minor issues, the translated manpages look beautiful, and I'll be happy to install them into the .deb once they are fixed. Thanks everyone, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588962: po4a using both builddir and srcdir
Hi folks, I've been working on #588962 to implement po4a for the schroot documentation. However, I'm running into a few difficulties which I hope some old hands can provide some guidance on fixing. I have added Thomas' fr translation, and got it to produce fr manpages and PDF documentation. This is in a prerelease version at http://people.debian.org/~rleigh/schroot_1.5.1.orig.tar.xz The main issues are: - 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). - 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? Or can groff now process UTF-8 input? (./configure make pdf to test) - There have been several manpage changes since the translation was done. Thomas, would it be possible to update the translation? It's in man/po/fr.po of the above source archive, though I can send you the file if you need. Other than these hopefully minor issues, the translated manpages look beautiful, and I'll be happy to install them into the .deb once they are fixed. Thanks everyone, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
