Hi Michael,
I have actually hit a further snag with this solution.
It appears to work well when all the content nodes have the same parent node as
in the original question. However, on coming to apply this solution to my real
world scenario each content node is actually a child of it’s own p node. I have
tried - but I cannot work out how to tweak your solution to adjust to this new
revelation. Any thoughts?
The new xml:
<p frequency=“30">
<Content value="0”/>
</p>
<p frequency=“30">
<Content value=”10”/>
</p>
<p frequency=“30">
<Content value=”15”/>
</p>
<p frequency=“30">
<Content value=”18”/>
</p>
<p frequency=“30">
<Content value=”22”/>
</p>
<p frequency=“30">
<Content value=”26”/>
</p>
<p frequency=“30">
<Content value=”34”/>
</p>
<p frequency=“30">
<Content value=”37”/>
</p>
<p frequency=“30">
<Content value=”56”/>
</p>
<p frequency=“30">
<Content value=”99”/>
</p>
<p frequency=“30">
<Content value=”101”/>
</p>
<p frequency=“30">
<Content value="115"/>
</p>
<p frequency=“30">
<Content value="118”/>
</p>
<p frequency=“30">
<Content value="129"/>
</p>
Many thanks,
R
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--