different XSL processors {RE: XSL to handle display mutiple pages }

Subject: different XSL processors {RE: XSL to handle display mutiple pages }
From: "Xu, Xiaocun" <XXu@xxxxxxxxxxxxxxxxxx>
Date: Sat, 4 Nov 2000 16:28:22 -0500
Hi, Jeni:

  Agreed.  If it is not broken, don't fix it :)
  Just a related question regarding XSL processor.  I am using eXcelon
Stylus XSL editor, which had a choice of either Stylus native processor
(standard syntax) or IE processor (Microsoft syntax).  When I use the native
processor, the XSL works.  When use the IE processor, it does not.  Also,
running the XML/XSL in standalone IE, it does not work.
  So my question is, what processors are out there and which one I should
use if my target display is IE?  and how to convert the XSL to work in IE?

Much thanks,

-----Original Message-----
From: Jeni Tennison
To: Xu, Xiaocun
Cc: xsl-list@xxxxxxxxxxxxxxxx
Sent: 11/4/00 11:27 AM
Subject: Re[2]: [newbie]use of xsl:if {RE: XSL to handle display mutiple
page s}


>         The only minor thing is, with:
>                 ". | following::item[position() &lt; $maxItemsPage]"
> it was displaying one extra item on each page (1-51, 51-101, etc.).
As I
> understand the logic, it should have worked.  But instead I had to
>                 ". | following::item[position() &lt; ($maxItemsPage -
> to get what I wanted (1-50,51-100, etc.)
>         Why this is the case?

Err... no idea.  I tried the following in Saxon 5.5.1:

--- XML File ---
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="test.xsl" ?>

--- Stylesheet ---
<?xml version="1.0"?>
<xsl:stylesheet version="1.0"

<xsl:output indent="yes" />

<xsl:variable name="maxItemsPage" select="3" />

<xsl:template match="/">
   <xsl:apply-templates select="//item[(position() mod $maxItemsPage) =
1]" />

<xsl:template match="item">
      <xsl:for-each select=". | following::item[position() &lt;
         <item><xsl:value-of select="." /></item>


and got, as expected:

--- Result ---
<?xml version="1.0" encoding="utf-8"?>

So *perhaps* it's the processor - you could try out the above to see
what you get - or perhaps it's something about the context in which
you're using the expression, or perhaps I've overlooked something
somewhere.  Feel free to send me your stylesheet if it's bothering
you, although as you've found a way that works I'd just stick with
that if I were you ;)

I hope that helps,


Jeni Tennison

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

Current Thread