From: Michael Smith Date: Fri, 26 Apr 2002 08:37:42 +0000 (+0000) Subject: added links to Daniel Veillard's DocBook page X-Git-Tag: release/1.79.1~6^2~5777 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2fe2b99c83828e79d3d524fc0619c5eafad512dc;p=docbook-dsssl added links to Daniel Veillard's DocBook page --- diff --git a/xsl/docsrc/publishing.xml b/xsl/docsrc/publishing.xml index 7510bd4e8..b5e24de94 100644 --- a/xsl/docsrc/publishing.xml +++ b/xsl/docsrc/publishing.xml @@ -79,17 +79,22 @@ $Id$ Your choice of an XSLT engine may depend a lot on the - environment you'll be running the engine in. Many DocBook - users who need or want to use a non-Java application are using - Daniel Veillard's C-based implementation, xsltproc (the - command line processor packaged with libxslt, the XSLT C - library for Gnome, http://xmlsoft.org/XSLT/). It's very fast, and also a - good choice because Veillard monitors the DocBook mailing - lists to field usage and troubleshooting questions and - responds very quickly to bug reports. But one current - limitation it has is that it doesn't yet support Norm Walsh's - DocBook-specific XSLT extension functions. + environment you'll be running the engine in. Many DocBook + users who need or want to use a non-Java application are using + Daniel Veillard's C-based implementation, xsltproc (the + command line processor packaged with libxslt, the XSLT C + library for Gnome, http://xmlsoft.org/XSLT/). It's very fast, and also a + good choice because Veillard monitors the DocBook mailing + lists to field usage and troubleshooting questions and + responds very quickly to bug reports. (And the libxslt site + features a DocBook page that, among other things, includes a + shell script you can use to automatically generate XML catalogs + for DocBook.) But one current limitation xsltproc has is that + it doesn't yet support Norm Walsh's DocBook-specific XSLT + extension functions. The current Java-based XSLT engine of choice for many DocBook users seems to be Michael Kay's Saxon (