You need to install po4a (in Fedora) to test this. Subject: [PATCH] Allow manual pages and POD files to be translated. This uses the optional po4a package to split these files into PO files for translation, and reassemble afterwards. Note this creates an extra pot file (po-docs/libguestfs-docs.pot). We don't (yet) combine this with the main po/libguestfs.pot file. The 'libguestfs-docs.pot' file included in this commit is not the real thing, just a short cut down snippet for testing. The real thing is created if you update one of the dependent files and rebuild. Note also the dummy ja.po, for testing the principles.

diff --git a/po-docs/ja/Makefile.am b/po-docs/ja/Makefile.am

+ +# Note that each Makefile.am in po-docs/$lang/Makefile.am should be +# identical. If you create a new $lang.po, create the $lang/ +# subdirectory and copy the Makefile.am from an existing language. + +LINGUA = $(shell basename -- `pwd`) + +CLEANFILES = *.1 *.3 + +# Ship the final translated manpages in the tarball. +MANPAGES = \ + guestfs.3 \ + guestfish.1 \ + libguestfs-test-tool.1 \ + guestmount.1 \ + $(patsubst %.pl,%.1,$(wildcard virt-*.pl)) + +EXTRA_DIST = $(MANPAGES) + +all-local: $(MANPAGES) + +guestfs.3: guestfs.pod guestfs-actions.pod guestfs-availability.pod guestfs-structs.pod + sed \ + -e &#39;/@ACTIONS(a)/rguestfs-actions.pod&#39; \ + -e 's/@ACTIONS@//' \ + -e &#39;/@AVAILABILITY(a)/rguestfs-availability.pod&#39; \ + -e 's/@AVAILABILITY@//' \ + -e &#39;/@STRUCTS(a)/rguestfs-structs.pod&#39; \ + -e 's/@STRUCTS@//' \ + < $< | \ + $(POD2MAN) -u \ + --section 3 \ + -c "Virtualization Support" \ + --name "guestfs" \ + --release "$(PACKAGE_NAME)-$(PACKAGE_VERSION)" \ + > $@-t; mv $@-t $@ + +guestfish.1: guestfish.pod guestfish-actions.pod + sed \ + -e &#39;/@ACTIONS(a)/rguestfish-actions.pod&#39; -e 's/@ACTIONS@//' \ + < $< | \ + $(POD2MAN) -u \ + --section 1 \ + -c "Virtualization Support" \ + --name "guestfish" \ + --release "$(PACKAGE_NAME)-$(PACKAGE_VERSION)" \ + > $@-t; mv $@-t $@ + +guestmount.1: guestmount.pod + $(POD2MAN) -u \ + --section 1 \ + -c "Virtualization Support" \ + --name "guestmount" \ + --release "$(PACKAGE_NAME)-$(PACKAGE_VERSION)" \ + $< > $@-t; mv $@-t $@ + +libguestfs-test-tool.1: libguestfs-test-tool.pod + $(POD2MAN) -u \ + --section 1 \ + -c "Virtualization Support" \ + --release "$(PACKAGE_NAME)-$(PACKAGE_VERSION)" \ + $< > $@-t; mv $@-t $@ + +virt-%.1: virt-%.pl + $(POD2MAN) -u \ + --section 1 \ + -c "Virtualization Support" \ + --release "$(PACKAGE_NAME)-$(PACKAGE_VERSION)" \ + $< > $@-t && mv $@-t $@

+# XXX Can automake do this properly?

# Note that each Makefile.am in po-docs/$lang/Makefile.am should be # identical. If you create a new $lang.po, create the $lang/ # subdirectory and copy the Makefile.am from an existing language.