RE: [xsl] fallback, saxon and MSXSL

Subject: RE: [xsl] fallback, saxon and MSXSL
From: DPawson@xxxxxxxxxxx
Date: Wed, 9 Oct 2002 11:53:14 +0100

> -----Original Message-----
> From: DPawson@xxxxxxxxxxx [mailto:DPawson@xxxxxxxxxxx]
> Sent: Wednesday, October 09, 2002 10:51 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: [xsl] fallback, saxon and MSXSL
> Trying to get a template to work with both processors (don't ask).

Funny that. each thinks the other ns is a function in their 'own' language.
  Is there any way the XSLT spec could be tightened up to stop this
  happening please? It appears to be when the processor tries to
  get more out of the namespace than is warranted.
Saxon says:
    The URI urn:schemas-microsoft-com:xslt does not identify an external
Java class
  which whilst true, relates more to extensions than my use, in fallback

I didn't have the microsoft prefix as an extension element prefix.

Only solution I could find was to use the processor string in a choose.

    <xsl:when test="contains($processor,'SAXON')">


 <xsl:when test="contains($processor,'Microsoft')">




NOTICE: The information contained in this email and any attachments is 
confidential and may be legally privileged. If you are not the 
intended recipient you are hereby notified that you must not use, 
disclose, distribute, copy, print or rely on this email's content. If 
you are not the intended recipient, please notify the sender 
immediately and then delete the email and any attachments from your 

RNIB has made strenuous efforts to ensure that emails and any 
attachments generated by its staff are free from viruses. However, it 
cannot accept any responsibility for any viruses which are 
transmitted. We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email 
and any attachments are those of the author and do not necessarily 
represent those of RNIB.

RNIB Registered Charity Number: 226227


 XSL-List info and archive:

Current Thread