Re: Alternatives to apply-imports which allow params

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At 16:22 5-12-2001, Sasha Haghani wrote:
>The XSLT 1.1 candidate recommendation

The who what now?

>appears to allow nested
><xsl:with-param> elements but I don't think my XSLT processor (Apache Xalan)
>supports 1.1.

No, I don't think it does.  "XSLT 1.1" was a working draft that has since 
been abandoned by the XSL Working Group, as its status section 
indicates.  It has no official status whatsoever, and should not be relied 
upon in any way.

As to your actual problem, I'm afraid that you have to design each template 
to understand an incoming parameter and explicitly pass it around in every 
template application.

~Chris
- -- 
Christopher R. Maden, Principal Consultant, HMM Consulting Int'l, Inc.
DTDs/schemas - conversion - ebooks - publishing - Web - B2B - training
<URL: http://www.hmmci.com/ > <URL: http://crism.maden.org/consulting/ >
PGP Fingerprint: BBA6 4085 DED0 E176 D6D4  5DFC AC52 F825 AFEC 58DA
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.8

iQA/AwUBPA8i0qxS+CWv7FjaEQL8BQCfZgD5jT78DMRoJF/+DhgtwuGumIYAoMyq
+avxg+DmCzhIOrZcC9HJXriG
=n33j
-----END PGP SIGNATURE-----


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list