-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =?iso-8859-1?q?J=F6rg=20Walter?= <[EMAIL PROTECTED]> writes:
> That's what Matt meant: XSLT works differently. There is no Perl whatsoever > involved with XSLT. But don't be fooled by the Syntax. XSLT is > turing-complete, and using EXSLT-Functions (see www.exslt.org) you have most > of the stuff you need and can do quite complex things. Not that you need to, > since often you just don't need to go programming with XSLT. OK. Transforming sections from docbook structures should be ok then. > Taglibs belong to XSP and have nothing to do with XSLT. XSP doesn't compare > well to XPathScript or XSLT since it works more like HTML::Mason or > PHP. Including document titles from other documents, remote or local, or reading from a database should then be prepared in an xsp processing stage, right? And performance? Still better than with on XPathScript Stylesheet doing "all in one"? Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard <http://www.gnupg.org/> iD8DBQE9/em5xxUzQSse11ARAm4IAJ47+dNu7df7IJUGioH2uWZh72OTugCffFFo ZOXQL5CnRRgCusiHnpCRXMw= =3UjT -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
