Dear All,

I can able to get the unique page numbers but they are getting
displayed in the beginning of the document. My requirement is that
they have to be displayed where they appear along with the text. Is
there any way for this.

My XSL is like below:

<xsl:key name="page" match="*" use="@page-num"/>

<xsl:template match="/">
   <xsl:for-each select="//*">
      <xsl:if test="generate-id(.) = generate-id(key('page',@page-num)[1])">
           <xsl:variable name="num" select="key('page',@page-num)"/>
           <b><xsl:value-of select="$num/@page-num"/>, </b>
      </xsl:if>
   </xsl:for-each>
<xsl:apply-templates/>
</xsl:template>

On 10/7/08, Ganesh Babu N <nbabuganesh@xxxxxxxxx> wrote:
> Hai All,
>
> My input is in the first thread of this post. However i will explain
> the thing here. Each and every element is having page-num attribute.
> Suppose if 10 elements are there in the first page, all ten tags will
> have page-num="1". the 11th element will have page-num="2". I want to
> display page-num value in the browser where it is changing from the
> previous value. In other words I have to display unique page numbers
> when they occur first
>
> this is not bound with any element. because all the elements have
> page-num attribute. I will write templates to match with specific
> requirements of elements. This i do not know how to write it. I have
> tried with some <xsl:if> but it is not working.
>
> Please help me in this regard.
>
> Regards,
> Ganesh
>
>
>
> On 10/6/08, Michael Kay <mike@xxxxxxxxxxxx> wrote:
>>> Dear Mike,
>>
>> It's not a good idea to ask for help from a specific individual.
>>>
>>> I have tried with other elements as well but I am unable to
>>> get the result. Please help me.
>>>
>>>
>>> <xsl:template match="section/title">
>>> <h1><xsl:if
>>> test="generate-id(.)=generate-id(key('page',@page-num)[1])"><x
>>> sl:value-of
>>> select="generate-id(key('page',@page-num)[1])"/></xsl:if></h1>
>>> <h2><font color="red"><xsl:apply-templates/></font></h2>
>>> </xsl:template>
>>>
>>
>> I can't see what's wrong with this without seeing it in context. What's
>> the
>> input, what's in the rest of the stylesheet, how does the output differ
>> from
>> what's required?
>>
>> Michael Kay
>> http://www.saxonica.com/