Am Donnerstag 05 März 2009 14:30:04 schrieb Debian Bug Tracking System: > Am Dienstag, den 03.03.2009, 23:08 +0100 schrieb Hendrik Sattler: > > using saxon to create manpages from docbook files is VERY slow in > > comparison to xsltproc. > > Additionally, the results don't match as the locally installed docbook > > XSL files (package docbook-xsl) do not get used and the current upstream > > version doesn't create fully correct manpages. > > > > Can it be patched to use the local files like xsltproc does? > > Install and use libxml-commons-resolver1.1-java to use the catalog > system. See http://www.sagehill.net/docbookxsl/UseCatalog.html.
Any chance to depend or recommend this? Do packages build-depend on libsaxon- java without using the resolver from above? Is it possible to build-depend on xsltproc || (docbook-xsl-saxon && libxml-commons-resolver1.1-java) in a debian/control file? If not, how is it possible to allow saxon as alternative to the other working docbook XSLT processors and still not using network resources? HS _______________________________________________ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
